Always nice to be greeted by this unlock screen:
Ever since upgrading to the latest NVIDIA driver, my Linux system has had a weird quirk with resuming from suspend/hibernate. All the applications and services that were running pick up right where I left them, but anything drawn by Gnome shell — including the unlock screen, the top bar and the dock — has corrupted text and icons. Sometimes it’ll be missing every few letters (Firefox is often captioned “ire ox”). And sometimes all the letters and icons will just show static.
It clears up if I log out and back in, or reset the display with Ctrl+Alt+Backspace. And I recently learned about another useful shortcut for Gnome: Typing “r” in the Alt-F2 “Run Command” box (whether I can read it or not!) will reset Gnome Shell without closing the session, so I can keep all the applications running and actually use suspend for what it’s meant to do — though with an extra step.
After a brief stint at distributed computing early in the pandemic, I came back first to Folding@Home, then BOINC, with the following goals:
- Use some spare computing power to help with worthwhile research.
- Not drastically increase my power usage.
- Mainly run projects when my computer would be on anyway, not start running a full desktop power supply full blast 24/7.
- Avoid damaging my primary system, and especially not have to replace a fried CPU or GPU in a hurry during the ongoing chip shortage! (I’ve had heating problems with graphics-intensive games on this box.)
Folding@Home only seemed worth doing with the GPU, and the tasks took long enough that it only seemed worth doing if I was going to keep the computer on, which tripped up on my targets for power usage, uptime, and overheating risk. And their ARM version had dropped 64-bit support, so I couldn’t put it on the Raspberry Pi either. Well, not without installing a new OS and setting everything up again.
I tossed BOINC on an old Android phone (via F-Droid) to start with, using Science United as a manager to automatically choose projects based on areas of research instead of having to dig into each project one at a time. After a week or so, that seemed to be working out pretty well, so I looked into expanding.
- Put Folding@Home on my desktop.
- It’s using too much power.
- Can I put it on my Raspberry Pi 3B?
- The software is 64-bit. The OS on there right now is 32-bit.
- Specs show the 3B has a 64-bit processor.
- /proc/cpuinfo shows it has a 32-bit processor.
- Specs show it should have BCM2837
- /proc/cpuinfo shows it has BCM2835
- Magnifying glass shows BCM2837 stamped on the chip.
It turns out all Raspberry Pi CPUs appear as 2835 in the kernel?!?!?
I decided to put BOINC on an old phone instead. I don’t feel like installing a new OS on the Pi. *sigh*
At first I thought this was related to Windows losing drives on wake. It started happening around the same time, it also involved waking up from sleep, and the CD/DVD drive was disappearing in Windows along with the vanishing hard drive.
But while moving the cables fixed that problem, it didn’t fix this one.
It was only mildly annoying, especially compared to regularly losing access to a large chunk of local storage, so I figured I’d come back to it later.
Other people are seeing this too and it’s a recent bug in the Linux kernel. At least with Fedora’s rapid kernel updates I probably won’t have to wait too long between when the patch lands and when it hits my desktop. It’s been years since I compiled my own kernel, and I don’t feel like starting that up again now!
Whenever I visit a Dreamwidth journal and leave it open in a tab, I always find myself wondering why I was looking at the Debian GNU/Linux website. For possibly obvious reasons:
I can’t imagine how I keep mixing up a dark red 1½-turn counterclockwise spiral with a dark red 1½-turn clockwise spiral! 😀