Open mattie47 opened 6 days ago
Why are you running an armhf 32-bit OS on a Pi5? It's 64-bit hardware so run the full 64-bit OS.
That said, I was definitely able to repro your scenario running armhf on a Pi5 and just doing a --explore
into a 32-bit OS. Impressive failure mode, to say the least!
The problem does NOT repro when exploring a 64-bit OS on that same 32-bit system.
My suggestion: Install the 64-bit OS. on your Pi5 If you need to operate on 32-bit IMGs, add kernel=kernel8.img
to your /boot/firmware/config.txt
You'll be able to operate on both 32 and 64 bit IMGs on it.
Someday I'll have a look into what's going on with 32 on 32 (at least) on a Pi5 (need to test others as well) but I consider this a low priority issue unless you can 100% convince me otherwise.
Why are you running an armhf 32-bit OS on a Pi5? It's 64-bit hardware so run the full 64-bit OS.
Because the docs say it's supported:
Running on 32-bit RasPiOS sdm can also perform all functions.
https://github.com/gitbls/sdm/blob/master/Docs/Compatibility.md?plain=1#L19
I opted for 32bit to stick with the same environment I'm running on actual Pis (In an attempt to minimize variables).
Why 32bit for the clients? Hardware issues on x64 and I don't have time to address. Because I already have Pis running 32bit in production, I don't want a mix-match without any major benefit for our scenario.
My suggestion: Install the 64-bit OS. on your Pi5 If you need to operate on 32-bit IMGs, add kernel=kernel8.img to your /boot/firmware/config.txt
I see. Thanks for suggesting that. I will try that now.
Someday I'll have a look into what's going on with 32 on 32 (at least) on a Pi5 (need to test others as well) but I consider this a low priority issue unless you can 100% convince me otherwise.
Fair enough. In absence, a doc update would be helpful.
Thanks,
Matt
Now YOU know, and in the year since the Pi5 was released, you're the only person to run into this, so my motivation to doc it is pretty low. Sorry.
Also FYI, here is a strong recommendation from one of the RPL devs on the subject: https://forums.raspberrypi.com/viewtopic.php?p=2167385#p2167385
Hi @gitbls,
I decided to follow your suggestion of using a pi5 to build an image, but I can't seem to get SDM working on a fresh install of a Pi5.
Instead, I get the following whenever it attempts to mount the image:
And trying explore (yes, different vanilla image, I tried downloading the two latest ones):
This leaves the Pi in a bad state, and I physically have to hotswap power to the Pi to get out of this state.
Reproduction steps
curl -L https://raw.githubusercontent.com/gitbls/sdm/master/EZsdmInstaller | bash
curl -c -O https://downloads.raspberrypi.org//raspios_armhf/images/raspios_armhf-2024-11-19/2024-11-19-raspios-bookworm-armhf.img.xz
xz -v -d 2024-11-19-raspios-bookworm-armhf.img.xz
Log of results from above reproduction (Note, Apt failed to install a couple things from the SDM install, however I ran this manually as per logs, prior to running SDM)
Is this something you've seen before?
I also tried going back to V13.0 (thinking perhaps a recent regression had occurred, but found no difference).
Thanks,
Matt