In my opinion backwards incompatible changes to legacy hardware kept in production for legacy applications should be communicated ahead of time and include information how to fix the legacy images so they work. Note in this context legacy means valuable as well as old.Thanks for your reply DougieLawson. However, a clean image of Stretch OS with updated boot files does work on the hardware, so the OS should not be an issue. As I said, there are limitations that prevent our img to be updated to a major release.You're running an OS that's too old for the hardware. Use Bookworm (V12) from 2023 which is three versions ahead of Stretch (V9) from 2017.Does anyone know what could be causing the issue?
Do you what could be causing our img to fail?
If you put the legacy image in an original Pi 3B+ where it's boots and run the usual updates. Does the image subsequently boot correctly in the revised hardware as well?
Statistics: Posted by ejolson — Wed Jul 31, 2024 4:33 pm