It was Debian 11 64-bit. That was some time ago, though it might have been upgraded to Debian 12 eventually; I can't remember. I had followed a setup here:vanilla Debian: 32-bit or 64-bit and what release? And what bootloader (config.txt contents basically).
Raspberry Pi OS bookworm: Raspbian 32-bit or Debian 64-bit?
viewtopic.php?f=50&t=249449
It worked for some time, until one day it didn't. I thought my 3b+ hardware was dead, but putting raspberry pi os on it revived it.
My RPi3B running 64-bit Debian Testing (set it to Trixie last week) did not show issues w.r.t. python. So I guess it is something where RPIOS diverts from Debian and breaking it. Also in-place upgrades of x86-64 of Bookworm->Testing/Trixie no issues, and several things rely heavily on python.
It is a bit strange that you use lgio which I understand is (more) generic Linux but use RPIOS.
It is possible to go in-place to vanilla Debian, it is essentially 2 packages and 2 files (kernel firmware cmdline.txt config.txt). I have flipped between RPIOS64 and Debian via ssh remote in the past. But w.r.t. python, maybe do a check on your installation:I get to 794 on 1 of my RPI4. only thing left is 1-wire, but I will move that to an ESP or else sometime I think as I am getting quite tired of all those specific rpt changes that I don't need for a headless server.Code:
sudo apt list | grep rpt | wc -l
Code:
sudo apt list | grep rpt | wc -lI'm not using lgpio directly, but it was a dependency. I think it was for gpiozero, and maybe some others.
Statistics: Posted by david3 — Tue Aug 19, 2025 4:46 pm