I spent a bunch fo time yesterday trying to get the 2.799 release to work on my existing Raspberry Pi 3B+. From what I can tell, 2.799 is just not bootable on that hardware.
I started with the in place upgrade which would not boot. I then re-imaged the SD card multiple times without success. I tried to a new SD card and had the same result.
I imaged the SD with 2.779 which did boot. I then tried the upgrade again and it would not boot.
I attached the Pi to a monitor and there’s no bios/boot output at all.
I would appreciate any help. Also, let me know if there are other steps I can take to help debug.
I’m not sure why that would be happening.
I’m running a 3B+ too and the upgrade worked and mine has been running 2.799 for a while.
My update was from 2.779 the same as you’ve tried.
Yeah, when I didn’t see other folks reporting the same problem I assumed it was probably just me, but I’ve yet to find an explanation or a work around.
I have tried two different SD cards, and I’m back on the original card running 2.779 without any issue.
I’ll try the early release 2.802 today for the sake of argument. I’l also try 2.799 on a different 3B+.
The boot process fails so early, I don’t imagine it would have to do with the DAC, but I’m running the original NanoSound DAC with OLED screen.
Ok, I tested my second SD card with 2.799 on a different 3B+ and it does boot correctly.
This might imply that the issue is with the NanoSound DAC. I’ll try pulling the DAC and see if the original device will boot 2.799 without it installed.
Continuing to test. I took the card with 2.799, booted it in the 3B+, enabled testmode and upgraded to 2.806. Rebooted, confirmed it was still working in the 3B+.
Then I put the card in the 3B and once again: it will not boot. There is one flash of the green activity light and then only the red power light stays lit.
I don’t know what else I can offer. I can keep trying the beta releases until one boots on this 3B, but I have no explanation for why this Pi is different.