Seems I fixed it with a boot ROM update. A pretty recent one, not even a month old.
Note that updating the bootrom is not an obvious thing.
1. No, it is not good enough to run.
2. No, it is not good enough to run.
3. No, it is not good enough to run text GUI and navigate to the right spot to download an updated bootrom.
I needed to do #3 and then #2 and then a reboot. (Possibly had I let "raspi-config" do a reboot for me I wouldn't have needed the extra steps, I'm not sure and I wasn't ready for a reboot at that point.)
I did futz with my a bit more and it is now:…though I don't think any of that fixed things. However, that watchdog might now have some effect. Documentation suggests that that feature wasn't present in the previous version of the bootrom.
I did a series of reboots, carefully watching the machine's monitor, and they all worked. Several seemed to do a retry behavior that I have never noticed before and I suspect is new.
Looks solved. (I hope.)
Thanks for everyone's patience,
-kb
Note that updating the bootrom is not an obvious thing.
1. No, it is not good enough to run
Code:
apt upgrade2. No, it is not good enough to run
Code:
rpi-eeprom-update -a3. No, it is not good enough to run text GUI
Code:
raspi-configI needed to do #3 and then #2 and then a reboot. (Possibly had I let "raspi-config" do a reboot for me I wouldn't have needed the extra steps, I'm not sure and I wasn't ready for a reboot at that point.)
I did futz with my
Code:
rpi-eeprom-configCode:
[all]BOOT_UART=0WAKE_ON_GPIO=1POWER_OFF_ON_HALT=0USB_MSD_PWR_OFF_TIME=10000USB_MSD_STARTUP_DELAY=15000USB_MSD_DISCOVER_TIMEOUT=35000BOOT_WATCHDOG_TIMEOUT=180BOOT_ORDER=0xf41I did a series of reboots, carefully watching the machine's monitor, and they all worked. Several seemed to do a retry behavior that I have never noticed before and I suspect is new.
Looks solved. (I hope.)
Thanks for everyone's patience,
-kb
Statistics: Posted by kentborg — Fri Sep 19, 2025 7:14 pm