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.

Continue reading

  1. Put Folding@Home on my desktop.
  2. It’s using too much power.
  3. Can I put it on my Raspberry Pi 3B?
  4. The software is 64-bit. The OS on there right now is 32-bit.
  5. Specs show the 3B has a 64-bit processor.
  6. /proc/cpuinfo shows it has a 32-bit processor.
  7. Specs show it should have BCM2837
  8. /proc/cpuinfo shows it has BCM2835
  9. Magnifying glass shows BCM2837 stamped on the chip.

A close-up view of a circuit board with Raspberry Pi 3 written on it and a Broadcom chip partially hidden by plastic spacers.

WTF?

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*