Not a dumb question, I have seen my Deck carry some weird bugs across a reboot. I don’t even bother with the reboot command anymore, it takes about the same time to shut down and turn back on.

AMD should stop making Intel chips unalive themselves with overvoltage transients. It is terribly rude.

At least Windows has more precise monitoring, it will tell you whether the process is “Windows Telemetry” or “SVCHOST.EXE”.

The OOM killer always, invariably starts off with killing the display server. Any side effects such as “the notification daemon loses its connection and closes” or “every single thing that you were working on loses its connection and closes” is incidental.

I have an early Deck, so I know that pulling the battery* is going to be a huge pita.

*without setting it and myself on fire.

I don’t need any special advances in batteries, I just need “it’s possible to replace them” and “it’s possible to get them”.

Anybody that claims to know what they’re doing with grub is a fool or a liar.

“Drivers” are only when you do ring 2 message passing in a hurd microkernel. Everything else is just “late-bound function call steering that happens to satisfy hardware-specific device communication and control”.

/s

Disable “Fast Startup” so that Windows actually shuts down when it shuts down.

“Two pointers” makes a lot of sense if you actually have the ability to pay attention to two things simultaneously. Most froods are not hoopy enough for this.

Nouveau or Nvidia’s own drivers? X11 or Wayland?

Looks like you need winetricks to install CJK_fonts.

*journalctl

Is anything going down in the system log when you mount a drive, or trigger an access error? If it’s (one of the many) security systems clamping down, they tend to log that.

Considering how poorly “the remarkably well supported ARM” Raspberry Pi is at playing video, I am shocked.

It’s fucking crazy how much work goes into shitting out thousands and thousands of slightly different models of android phone and tablet and chromebook. Slap together a board design based on buying two trays of some SOC. Open up the Android source, slap some NDA drivers in, build an image, burn it into a production run. Don’t bother saving your changes, these devices will never get an update. Two weeks later, change out the whole design for a different chip, repeat.

The vast majority of xz’s blobs are accounted for, too.

I thought this was pretty solid talk on SElinux https://www.youtube.com/watch?v=_WOKRaM-HI4

If you think it’s hard to figure out GPG for yourself, well good luck finding and communicating with someone else who has also figured it out.

I think the flatpak is still up.

Fuck Nintendo.