you have firmware.bak, so I can more or less with 100% certainty answer the question that trejan asks you; maybe you don't remember, but this issue has been seen many times on this forum. And RPL does nothing to rename rpi-update, so people think that that is the way to update an RPi.The build running on this pi 5 was, at the time the board came out, a clean install of bookworm.
What I tried now is :
sudo apt reinstall linux-image-6.12.34+rpt-rpi-2712
reboot
uname -r
6.12.34+rpt-rpi-2712
Now the board is running with the latest SW.
I still would like to know why the boot process (before the reinstall) isn't selecting the most recent kernel always.
But it ruins the normal Debian update process via apt quite often. Maybe we should just wait until someone or many (a whole fleet of Pis) get hacked with the help of that script and used for DDOS attacks. It is very easy, even for script-kiddies.
You also have 2 critical files (config.txt cmdline.txt) in /boot
Those should not be there, the ones used are on the FAT formatted 1st partition where a Pi boots from. So double, that is confusing. You might have edit-ting the wrong files or/and tools have also done it wrong. Make them symlinks or better remove them.
Statistics: Posted by redvli — Mon Jul 28, 2025 2:04 pm