klangcola

Yeah that was my assumption. But I hadn't considered WOL being broadcast, so now I'm not so sure. I would assume it's broadcast on both IP and Ethernet layer. It's time to do some wiresharking :)

Maybe something else going on then, but ive never gotten WOL to work after a blackout when there's two switches between sender and receiver. After powering up the receiver once, WOL works again

If you're already using node-red, the Wake On Lan node works well, and with node-red it's easy to trigger the magic packet based on whatever trigger condition you want.

The only limitation I know is WOL doesn't work after a power outage, because the switch and RPI doesn't know where to find the target machine

Thanks for the tips on reusable enterprise cards btw

My gut reaction too. But their readme/faq makes a lot of sound points. Also Nextcloud is one of the main contributors, so you know it's serious. Also Proton and Ionos (which I admit I'd never heard of, but they seem big)

You might be interested in an immutable distro. Like Bazzite or other Silverblue / Ublue flavoured system. They are recent but not bleeding edge, deploy well tested images that apply as all-or-nothing. Very stable, very featurful :)

For actual advice:

• run memtest to verify RAM. Do multiple passes, at least overnight.
• Check cooling? RAM and other things can overheat and cause locks, not just CPU.
• Can you throw a couple of different distros on there, to try different permutations of kernel and drivers, old and new.
• journalctl --follow (with sudo), dmesg -w. I ran these over ssh from a remote machine. Even better if you can run it on a local 2nd monitor. The point is to have them open the whole time since it's too late to change once the system is locked up

I had / have a similar issue that started at some point on my Ryzen 7 laptop with Kubuntu 24.04. I haven't tried REISUB yet, but otherwise same symptoms.

RAM is the usual suspect. I ran memtest for 24h++ with no errors Also tailed dmesg and journalctl to a remote machine, and checked journalctl after reboot. No errors reported. Presumably because the system hard locked before it had a chance to log the error.

I never found a root cause, but after I changed the KDE Power Profile from Eco to either Balanced or Power (I don't remember which) the random freezing reduced from 1-3 times per day to once every few weeks of continuous uptime.

So my guess is some kernel driver bug relating to power states of the CPU ( or GPU nVidia 3060 with 590 drivers)

Doesn't work in my experience, or I'm typing it wrong. I can use the journalctl boot filter to show the current boot, the 2 boots ago, but not the previous boot where the system crashed.

So I end up filtering by time instead with --since

There's strong Farquaad vibes here..

Some of you may die, but that's a sacrifice I'm willing to make

You can subscribe to a peertube channel with a Mastodon account if you want

Good catch, that licence does not look very Libre =\

That's neat :) I like the concept of a collection of warm&fuzzies symbols

How are you making the stickers? It looks like each sticker is composite of multiple snippets of art?