@sleepyD - I installed PINN 3.9.2 with Raspberry Pi OS 64 standard desktop. I let Raspios update to the latest version. I then git cloned the pironman5 repos and executed the pironman5 install script with 'sudo python install.py'.
Pironman5 seemed to install ok and so I rebooted when prompted, which took me back into PINN. I then booted into Raspios again without any problem.
NOTE: I did this on an SD card without NVME and without any actual pironman5 hardware.
So I don't see a problem with the pironman5 script as yet. Maybe it was something else.
It sounds like it is PINN that is rebooting back into itself, which means either there is something seriously wrong with your partitions, or something unexpected with PINN. You have a number of options:
1. If you don't have much on your drive, you could just start again and reinstall everything, starting with PINN.
2. If you want to preserve your drive contents, then we can try and debug what's going on. I suggest you open a ticket on my github page (https://github.com/procount/pinn/issues) where we can discuss this in more depth, as this seems to be peculiar to you. You could post some files there so I can see what is going on.
3. You could try replacing PINN by deleting the contents of the RECOVERY partition and unzipping the latest version (https://sourceforge.net/projects/pinn/f ... p/download)
4. You could try reinstalling Raspberry Pi OS from PINN.
5. There were problems with early Pi5 firmwares that didn't support multiboot and ended up rebooting into PINN no matter which OS was chosen. Sounds like the same thing as your problem, but I think you had it working, so I'm not sure this would help. But anyway, try making sure your eeprom firmware is up to date.
The above is quite brief. If you need help on any of these, feel free to ask for more detail on your github issue.
Pironman5 seemed to install ok and so I rebooted when prompted, which took me back into PINN. I then booted into Raspios again without any problem.
NOTE: I did this on an SD card without NVME and without any actual pironman5 hardware.
So I don't see a problem with the pironman5 script as yet. Maybe it was something else.
It sounds like it is PINN that is rebooting back into itself, which means either there is something seriously wrong with your partitions, or something unexpected with PINN. You have a number of options:
1. If you don't have much on your drive, you could just start again and reinstall everything, starting with PINN.
2. If you want to preserve your drive contents, then we can try and debug what's going on. I suggest you open a ticket on my github page (https://github.com/procount/pinn/issues) where we can discuss this in more depth, as this seems to be peculiar to you. You could post some files there so I can see what is going on.
3. You could try replacing PINN by deleting the contents of the RECOVERY partition and unzipping the latest version (https://sourceforge.net/projects/pinn/f ... p/download)
4. You could try reinstalling Raspberry Pi OS from PINN.
5. There were problems with early Pi5 firmwares that didn't support multiboot and ended up rebooting into PINN no matter which OS was chosen. Sounds like the same thing as your problem, but I think you had it working, so I'm not sure this would help. But anyway, try making sure your eeprom firmware is up to date.
The above is quite brief. If you need help on any of these, feel free to ask for more detail on your github issue.
Statistics: Posted by procount — Mon Jul 01, 2024 10:30 am