Bosbeetle
Terminally lost
Oh must try this, at some point!
@aTc could likely roll these changes eventually to a new build.This is awesome thanks Johnic. My question is: is there eg an apt command I can run to pull in these enhancements?
Would a script help? I'm preparing one now.This is awesome thanks Johnic. My question is: is there eg an apt command I can run to pull in these enhancements?
chmod +x suspendFix.sh
Not sure. I definitely had Buster on my eMMC, still. Turns out the Debian version doesn't matter, anyway. After some more investigation, it seems that this just doesn't work with eMMC installs.Does anyone use Buster still? Haven't we migrated to Bookworm fully yet?
Gave up waiting for root filesystem device. Common problems:
- boot args (cat /proc/cmdline)
- Check rootdelay= (did the system wait long enough?)
- missing modules (cat /proc/modules; ls /dev)
ALERT! PARTUUID=84dod9b1-02 does not exist. Dropping to a shell!
I installed bookworm on my eMMC, and had the same issue, where it doesn't boot. It can't find the eMMC:
Gave up waiting for root filesystem device. Common problems: - boot args (cat /proc/cmdline) - Check rootdelay= (did the system wait long enough?) - missing modules (cat /proc/modules; ls /dev) ALERT! PARTUUID=84dod9b1-02 does not exist. Dropping to a shell!
You don't block one SD card slot. That is an advantage for me...Maybe a stupid question, but is there a real advantage of having the OS on the eMMC? Obviously the eMMC is much faster, but I have the latest OS on the SD and an old one on eMMC. I assume people put their applications on an SD-card, so impact on loading would only be when turning on the Pyra, right? And I'm not really worried about the current boot time.
3D acceleration is somewhat half baked on Bookworm, so I keep going back to Buster.Does anyone use Buster still? Haven't we migrated to Bookworm fully yet?