I installed today on my rspi5 mounted in the Pironman5 PINN on the nvme with a partition to boot the regular Raspberry OS bookworm and the. Other partition Ubuntu as I would like to go experiment with ROS2.
All was working fine with the initial installation of PINN and both OS’s.
Then I installed the prinonman5 software on the bookworm including the updates done to the rpi-eeprom-config. Again all was working fine.
The in the Ubuntu OS I checked the eeprom-config and while not updating anything it messaged me there was a change and reboot was required.
from there… all wrong. The rpi keeps booting back into PINN and can’t boot into the any of the OS’s anymore. PINN just keeps coming back.
This is a bit new to me. Is there any thing I can try other than start over from scratch?
(From scratch also means to disassemble the Pironman as well so I can boot directly from the sd card slot as the extender doesn’t work to boot from anymore)
Thanks for the feedback. Done that many times already.
Tried to ‘Fix’ even reinstalled from the PINN menus both the Os’es but nothing seems to work. You can also look in each OS the config.txt and also those all look perfectly fine.
Something went wrong with the eeprom and of course that is something unreachable unfortunately…. Without….disassembly LOL
Yeah, PINN is not perfect, many problems when I install rasbian, batocera, Ubuntu, Lineage. I just give up. Now I have many 64gb SD card with differents OS. I don’t know if there’s alternative to PINN…
Well, I just got things going again… without disassembly LOL
I used the imager to load bookworm onto an usb stick.
Removed the nvme and could get it going again.
Then I was able to update the rpi firmware and eeprom correctly and PINN worked again.
The interesting thing on top was what I also read in another thread, that after the firmware update the pironman5 rgb fans kept turning. I experienced the same. However, when I booted the raspbian bookworm from the nvme again via PINN, there they were working as expected again.
During my tries yesterday in getting it going I reloaded the Ubuntu 24 where it didn’t work. After the fix today it turns out there is a kernel issues with Ubuntu 24 on initial install though so I had to replaced it again with 23 and once that was running I could upgrade to 24 with no problem.
Seems I’m back in action now …. And learning a lot as I go
Only the Ubuntu 24 system is experiencing this issue; other compatible systems are working normally, right?
It is possible that after the official system update, the kernel version was also updated, which may have caused the pironman5 software to be partially incompatible.
Our pironman5 software has not been updated or changed.
We need time to reproduce.Appreciate your patient.
When I was updating stuff logged into Ubuntu 24 the first time I was probably doing something wrong from where PINN acted weird and didn’t let me boot into any OS anymore.
Besides the fact indeed I also now had problems with the SD Card extender to boot from, I was able to do it from an USB stick without the need to disassemble the Piroman 5.
So nothing wrong with the Pironman5 besides the extender and I got everything running again fine
Figured out also that initial install directly within PINN of Ubuntu 24 fails due to a kernel bug of Ubuntu itself. Deploying Ubuntu 23 and then upgrading to 24 works also fine. So nothing to do with SunFounder at all.
Is your SD expansion board connected to the PI5, and is the SD card with the system not being recognized for booting?
1.Please remove the fixed copper pillars and screws from the SD expansion board, insert the SD card with the system into the expansion board, and then ensure that the expansion board is fully inserted into the Raspberry Pi interface. Start the PI5 to see if the system can boot normally. This will help verify if the issue is related to insufficient insertion depth of the SD expansion board.
2.After removing the fixed copper pillars and screws from the SD expansion board, try gently pressing on the expansion board to check if the contact points are loose, which could cause the SD card not to be detected.
3.If these methods have been tried and the SD card is still not recognized, we will arrange to send you a replacement SD expansion board.
probably different people are using the same account from SunFounder_Moderator.
The tihng is that without the extender it is booting perfectly fine. It was actually me in the other thread that suggested the extender wasn’t going deep enough.
That resolved at least I can use the extender as a drive bay, but booting from it doesn’t work. Please check that thread.
So if nothing substantial in the design of the extender has been changed then it will not make sense to send me a new one either. I was able to resolve my actual issue though. And I simply do not use the sd card extender at all.
We have made modifications and upgrades to the SD expansion board. Once we done the production, we will send you the upgraded version of the SD expansion board if you need.
…. And learning a lot as I go