Librem 5 not working after recent apt update && apt upgrade (Byzantium)

I just ran apt update && apt upgrade a few minutes ago. The command seemed to finish without error. However immediately after upgrade I noticed my external keyboard wasn’t working. I rebooted only to find that wifi/4g/bluetooth items in the swipedown are grayed out (all HKS are up through entire boot and after). External keyboard is still not working, though no wireless is clearly a bigger issue.

When booting up, I can press volume down to see boot sequence logs, and I notice the following errors:
“failed to load kernel modules” (prints twice)

Then following seem to hang and eventually time out after 90 seconds
“a start job is running for X”, where X switches between: “/dev/zram”, “/dev/ttyGS0”, “ Configured”

Finally it prints

“failed to start librem 5 usb gadget”

I don’t know if any of these were present before this issue.

Only thing unique about my setup is that I mount home from an SD card. However, the problem persists when I remove the SD card. (previously, I have had no issue switching between SD and no SD)

Any idea what the problem could be? Are others having this issue? Is there a way to recover without flashing the device again? (Maybe boot into previous version? Not sure how to on L5)

1 Like

Can / have you booted without usb attached? I remember having some problem that with booting when having usb attached and then had to re attach keyboard to get it to work. This may not be the same, but let’s start there.

2 Likes

Thanks for the response. I have tried with nothing plugged in as well as with a hub and power plugged in. Result is the same.

1 Like

If you’d have a previous disc image to flash to, that would be the easiest step back but I doubt you do. Take this incident a as a reminder that taking backups is always handy.

Losing wireless is inconvenient but can you get online otherwise with it - via usb-lan or mobile data? Then you could try update again, if something is missing.

The first troubleshooting option is of course looking at logs to see what they tell you. Teke a look via journalctl -b or less -r /var/log/boot.log*, maybe systemctl list-units --failed and dmesg too about kernel issues (use something like | grep "error" after the commands if needed to look for errors (or other relevant words)). Paste here at least the relevant rows of (boot, kernel or usb related) errors, failures and warnings (if you don’t spot the problem outright yourself). You can add >> capturedlog.txt after the commands to get the texts piped from console directly added to the end of a text file, if that helps to gather all relevant lines (if you want to use text editor for instance). [combined example: sudo journalctl -b | grep "error" >> journalctllog.txt (note that it does not capture any other lines than errors, but it’s a start)]

[edit to add: If you can’t get online, can you use an USB stick to move log texts? If not, this may be slow going to analyse (is it worth the time and trouble to fix)]

2 Likes

No mobile data (I mentioned no 4g, but I suppose that wasn’t entirely specific). No risk of data loss (entire home folder sync’d with syncthing). Just annoying to have to reflash my device. Luckily I have a backup L5 I can swap my sim to when I get home to still get calls/texts in the meantime.

Looking at the logs, I see:
unknown kernel command line parameters “splash uboot_version=2022.10-g956aa590c9” …
direct firmware load for imx/sdma/sdma-imx7d.bin failed …
eternol firmware not found, using ROM firmware
<^ x2>

I also see the same errors that are printed in the plymouth boot screen. I think I’ll just reflash it later…

2 Likes

Ay, may be simplest to do so with that set up.
It’s still good to know what went wrong, if it repeats.

2 Likes

Since there’s no wireless and no USB, any debugging has to go through the OSK, which too much effort. Reflashed and it seems to boot. Seems to be working fine now. Strange that I’m the only one experiencing it. Maybe I updated at just barely the wrong time…

2 Likes