Sleep/wake issues with AMD gpu and platform drivers are super, super, super common. Fish back through your kernel journal after a reboot (journalctl -kb -1 should do it) and look for the driver errors immediately after the wake event. If this has been fixed in a later kernel release then update your kernel, if not go report it to either the Ubuntu folks or on the amdgpu gitlab.
All kinds of small electronics and components, thermal putty, thermal tapes, heatsinks, antennas, plastic cases, replacement customized cases for specific electronics (handheld consoles, etc.)
I’m pretty tempted to just buy a steam deck and run yuzu to play my switch games. Between vita3k, yuzu and whatever emulates a 3ds I’m thinking I could consolidate all of my handhelds pretty effectively at this point.
Start by playing with subvolumes and snapshots so you can get a feel for how they work. Once you’ve got that down you can break down your root filesystem into sensible subvolume chunks (/, /home, /var/log, /var/cache etc) so that you only snapshot relevant content during each update. I wrote a btrbk config at that point, tested it a few times and then wrote a pacman hook to fire it on install, update or package remove events and went from there.
Here’s what I use to take snapshots - you’ll need to write an appropriate btrbk config file for your subvolume layout but it’s otherwise feature complete. gitlab.com/arglebargle-arch/btrbk-autosnap
Like I mentioned above, I haven’t actually needed to roll the system back in ages but I get a lot of mileage out of being able to reach back in time and grab old versions of files for comparison.
Time shift is a lot easier if you’re just starting out but it also requires a specific subvolume structure and isn’t very flexible.
Edit: pro tip: don’t make /var a separate subvolume from /, it’s way, way, way too easy to roll one or the other (/ or /var) back without the other. If you do that by accident pacman’s state becomes out of sync with the running system and everything breaks. Stick to splitting frequently rewritten data like /var/cache and /var/log off, leave /var itself in the root subvolume.
I’m not. I’m asking how we can navigate this conundrum in order to reach a common ground where we do NOT have to give up our precious privacy in exchange for security.
That’s easy. You tell the people who want you to give up your right to privacy to go fuck themselves. The common ground is when they go fuck themselves, problem solved.
It’s not so bad if you’re running a major distro kernel and they do some prerelease testing before cutting new kernel packages. But if you’re using the latest release from the kernel.org stable tree WiFi driver regressions happen somewhat regularly.