Shdwdrgn

joined 2 years ago
[–] Shdwdrgn@mander.xyz 1 points 1 day ago

Since OP's link is paywalled, here's another article on the same storm (I'm sure there are several others as well)...

https://www.kxnet.com/news/local-news/national-weather-service-confirms-multiple-tornadoes/

[–] Shdwdrgn@mander.xyz 2 points 1 day ago (1 children)

What kind of crops are you going to grow at 125°? That's still within OP's specification of triple digits and with temps getting hotter we're likely to see a lot more of this happening within our lifetime.

[–] Shdwdrgn@mander.xyz 0 points 1 day ago (1 children)

Yeah I think there's some good ideas that have been built up with the ABL devices over the years, and that mesh leveling seems great. However I also feel like more people should take the time to get their beds physically as flat as possible first, because otherwise your printer spends a lot of time micro-stepping the Z, and I've seen some mesh maps that looked absolutely horrible.

Playing around with arduino devices, I have some laser rangefinders that seem like they could work well for an ABL. That might also be a good way to map out the idea I mentioned about creating a thin full-bed shim to get a truly flat bed, and after that perhaps you would only need to do a fast four-corner calibration with the ABL to make sure nothing has changed.

[–] Shdwdrgn@mander.xyz 2 points 1 day ago (3 children)

I've never had auto-leveling on my own printer, but the one at work has it and I wouldn't want it. It was great for the first couple years, then the sensors started suffering from corrosion and now it just doesn't work for crap.

So on my own printer (fully manual) I have always treated the paper test as nothing more than an initial step to make sure the nozzle doesn't plow your bed during the leveling process. It will get you close, but not close enough. To really dial in your bed, you need at least a 5-point 1st-layer print test so you can really get that initial layer adhering nicely at all points, and this of course performs the calibration with the bed at full heat so it matches conditions during actual prints.

The biggest problem I had was my aluminum bed was badly warped when I got it, but fortunately just bowl-shaped. I cut CD-sized discs of aluminum foil to build up the center -- 13 layers in total, then put a glass or G10 bed over that to really get a flat surface. I finished mine with a PEI sticker on top of the G10.

Another problem is that all beds will be completely unique from each other. I have one of the original Ender 3 Pro printers, and purchased a Creality glass bed with it. There was nothing that wouldn't stick to that bed, and I used a 10mm calicat (which has 4mm feet pads) as my tests for all new filament. Clean the surface occasionally with 91% ISO, and life was good... but after a few years the surface wore out and I was forced to get a new bed. Ordered directly from Creality again, and man, nothing at all would stick to that piece of glass, even for large prints. I tried everything down to brake cleaner to solve the problem and finally gave up on it. That's when I started working with the G10. The point of this is that you can tell someone a particular bed will solve all their problems, and you will be wrong. The reality is that sellers use different manufacturers to make their product and you never know what you'll get.

Your observations about the bed warping from the tightness of the screws is interesting, I never thought about that part before. I have heavy springs under my bed, and I have always suggested people get those springs as tight as possibly without being completely closed, then adjust the Z-switch to that point before you start your leveling process. Tight springs means the screws should never wander. It's been around 3 years since the last time I even touched my leveling screws, and I just fired up the printer and ran some new pieces last week without any issues. A good tool is one that you can ignore for a year, then use it without having to recalibrate. Anything else is just frustrating!

There are a lot of suggestions we can make to help newcomers get their bed leveling correct, and there are a lot of variables that we simply can't account for including manufacturer defects. One idea I had years ago but never got around to trying is to print a thin sheet of filament the size of the entire bed, ironed to create a top surface perfectly flat to the nozzle but taking up any imperfections in the aluminum plate. Then put a thin bed over the top of that, and you should have a perfect surface that lasts nearly the life of the printer. Seems like a good idea, but how do you figure out where to fill in those first layers until you have a final layer that covers the full bed?

[–] Shdwdrgn@mander.xyz 1 points 1 week ago

Oh I have a pretty good idea about that... But I was actually referring to the fact that Trump's platform was the first thing attacked after he bombed the country. Yeah it would be great if we had a government that was focused on letting the various agencies do their jobs rather than dismantling everything that keeps us safe and healthy.

[–] Shdwdrgn@mander.xyz 0 points 1 week ago (6 children)

When they're talking about "poorly secured US networks", they're referring to Truth Social, right?

[–] Shdwdrgn@mander.xyz 12 points 2 weeks ago (1 children)

Now if only Sony would get their shit together and start making a compact version of the Xperia line again.

[–] Shdwdrgn@mander.xyz 4 points 3 weeks ago

Yes! One of my most favorite Johnny Depp roles.

[–] Shdwdrgn@mander.xyz 1 points 3 weeks ago

That's a good point, although flashing does help to grab attention, but it can also be annoying when the person is driving with their foot on the brake pedal.

[–] Shdwdrgn@mander.xyz 1 points 3 weeks ago

Wow that's got to be almost worthless. As you say, it just takes some idiot with a load obscuring the vehicle lights and suddenly nobody behind them knows what's going on. What's next, are we going to make tail lights optional?

[–] Shdwdrgn@mander.xyz 2 points 3 weeks ago (2 children)

Does your state not require good lights on the trailers? I just built a new trailer last year, I was required to have full working brake and turn signals along with running lights, but I went the extra step and included more brake/turn lights on the front and rear of the fenders, along with reverse lights plus four marker lights along each side. Trailers are hard enough to see, I didn't want to make it harder for anyone by just sticking with the bare minimum.

[–] Shdwdrgn@mander.xyz 4 points 3 weeks ago

I suspect a lot of that has to do with the entitled way people are driving these days. If you leave a car length gap, some kid will wrecklessly attempt to cram their way in because your lane momentarily moved slightly faster.

 

I built a new firewall under Debian 12. The machine has eight network ports, and during configuration I accidentally used the same name for a couple of the ports in the files under /etc/systemd/network/*.link. I ended up with two link files referencing two different MAC addresses but naming each of them as WAN0, and once systemd got that configuration it wouldn't let it go.

From what I could find online, normally I would just issue systemctl daemon-reload followed by a update-initramfs -u and after a reboot systemd should have had the updated information... but no dice this time. The way I finally discovered the problem was when I noticed under ifconfig that my wan0 port was pointing to the wrong MAC address (even though the link files had been corrected).

After several hours of fighting with it, I finally managed to get it to work by renumbering all of my link files, and now the information for each port matches up correctly. But my real question here is WHY did systemd refuse to read updated link files? Is there another step I should have taken which was mysteriously never mentioned in any of the dozens of web pages I looked at trying to fix this? I really need to understand the proper process for getting it to correctly use these files so I can maintain the machine in the future.

(God I miss the reliability of udev already)

 

I'm building a new rack server (Poweredge R620) and am using the option "consoleblank=600" in the GRUB_CMDLINE_LINUX setting. During the setup I used the wrong memory stick and installed Bullseye, and screen blanking was working correctly there. Since I had already finished nearly all the configuration this week, I thought it would be easier to just do a regular dist upgrade than reloading the whole system.

After upgrading to Bookworm and rebooting, I notice that now when the screen blanking is supposed to kick in (which normally just turns off the display), I am instead getting what looks like rolling static on the screen. I have several other R620 racks running Buster so I know the screen blanking should work with this hardware, but this appears to be an issue specific to Bookworm.

Note that even when I try something like setterm -blank 1 or setterm -powerdown 1 I get the same resulting static after 1 minute. To be clear, this is specifically for the command line, I do not run desktops on my servers.

A google search for the problem has been unsuccessful so I'm hoping someone can point me to a solution or help with the proper search terms.

 

I'm wondering if anyone has found (free) sources of data to use for live elections results, specifically the Presidential race? I've been building a map of poll results but would also like to put something together to watch the race tomorrow night.

 

A 1930s-era breakthrough is helping physicists understand how quantum threads could weave together into a holographic space-time fabric.

 

I would love to have them light up like a scoreboard as each representative takes the floor, showing all of the commandments they have broken. If people want so badly to bring religion into politics then lets just show them exactly who they've been voting for. Maybe we can get the news networks in on this too, displaying it on the side of the screen similar to a sporting event.

 

Marjorie Taylor Greene, the bastion of factual information, has once again shown the nature of her character by claiming that peaceful protestors at the Capitol are in fact an "insurrection of terrorists". Don't you see all the violence and mayhem being caused in this video clip? No, me either...

If you want to make such bold comparisons, lets start out by checking how many people are running for their lives or the number of deaths involved between these two events. Or maybe we should be asking why MTG thought it was an "honor" to meet with the people responsible for murder and the attempt to destroy our democracy?

 

I've seen the occasional blip here, but this is the first time I've seen a complete outage of this instance. Hoping @Salamander wanders through and gives us the scoop?

 

I have an annoying problem on my server and google has been of no help. I have two drives mirrored for the OS through mdadm, and I recently replaced them with larger versions through the normal process of replacing one at a time and letting the new drive re-sync, then growing the raids in place. Everything is working as expected, with the exception of systemd... It is filling my logs with messages of timing out while trying to locate both of the old drives that no longer exist. Mdadm itself is perfectly happy with the new storage space and has reported no issues, and since this is a server I can't just blindly reboot it to get systemd to shut the hell up.

So what's the solution here? What can I do to make this error message go away? Thanks.

[Update] Thanks to everyone who made suggestions below, it looks like I finally found the solution in systemctl daemon-reload however there is a lot of other great info provided to help with troubleshooting. I'm still trying to learn the systemd stuff so this has all been greatly appreciated!

 

Just in case there are others like myself who rarely check reddit any more, I thought it would be helpful to cross-post this. It won't look like much unless you have the solar eclipse glasses, but I plan to break out my tracker and camera (with solar filters!) to try and get some pics.

view more: next ›