kernel upgrade via apt 5.11.0.1015-raspi kills the OS on Raspberry Pi4B
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux-raspi (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
OK, so I've already killed three RPi4B Ubuntu installs (1 Ubuntu Server, 2 Xubuntu Desktops) by installing the recommended apt package(s) for the firmware and especially the kernel into version 5.11.0.1015 -- I've already written a comprehensive summary on the issue on AskUbuntu's side @ https:/
The Ubuntu Server one was a fresh one and I literally did nothing else except apt update and apt upgrade straight out of the box from an image that I etched using the latest version of 'rpi-imager'. I ran the OS from a never-before-used, fresh USB stick as my attempt to get some sort of a working boot loader that I could then try to rsync/copy to the boot parts of the other Ubuntu builds that were broken by this very same update. No such luck! I would expect a _lot_ of broken OS installs headed your way; I did try to contact the devs two weeks ago when my first system got fried due to getting the update from the 'hirsute-proposed' repository ... Geez.
Under the /var/log/ of my first fried OS, I have absolutely no errors or warnings, and I've included i.e. my 'dmesg' output as for the installed stuff here: https:/
I'm really in a tough spot due to this because now I've got two dead systems and no apparent solution to fix it! :(
affects: | linux-meta-raspi (Ubuntu) → linux-raspi (Ubuntu) |
I tried swapping different setups that I have, I've now tried it with two different firmware versions, one from May and the other from 6th of July (which is the most current version). It's either the "cursor of doom"-screen (on two of the Xubuntu desktop installs) or the "rainbow screen of death" (on the fresh 64-bit Ubuntu Server).
On the one that boots into the blinking cursor, none of low level boot bypass keys work. The disk utilization led stays.
RPiOS and other OS's work just fine, and both of those systems that had been working previously, had been running without much troubles since 21.04 hirsute came out.
Please advice, as, like I just noticed, this has the possibility to affect every single user installing the 5.11.0.1015-raspi update from the apt packages.
I'd need all the help restoring my bootloader to those two of my systems, they worked perfectly well and I wouldn't want to ditch and rebuild them. :(