After being talked about for years of DRM panic handling and coming with a “Blue Screen of Death” solution for DRM/KMS drivers, Linux 6.10 is introducing a new DRM panic handler infrastructure for being able to display a message when a panic occurs.
With Linux 6.10 the initial DRM Panic code has landed as well as wiring up the DRM/KMS driver support for the SimpleDRM, MGAG200, IMX, and AST drivers.
For those curious what DRM Panic can look like in action, Red Hat engineer Javier Martinez Canillas shared a photo of the DRM Panic “Blue Screen of Death” in action.
A BeaglePlay single board computer was used and Javier posted to Mastodon of an example implementation:
It could be extended in the future with some operating systems having looked at QR codes for kernel error messages and other efforts for presenting more technical information while still being user-friendly.
On Linux 6.10+ with platforms having the DRM Panic driver support, this “Blue Screen of Death” functionality can be tested via a route such as echo c > /proc/sysrq-trigger.
The original article contains 231 words, the summary contains 177 words. Saved 23%. I’m a bot and I’m open source!
Been following the wiki, but when I try to flash for root partition, I get “data too large” . I’ve tried to wipe everything with TWRP, but it still shows the same error. Not sure how to proceed next.
Glad you found it easily. It’s not hard to do but you need to follow the guide exactly and be cautious. Unless it changed, the script was taking care of almost everything as I remember.
It’s not just about the verification/reproducibility, these random ass .deb files sometimes don’t have proper dependency information and/or repository support. So it may work for now and might stop working on the future when some library upgrades on your system. Or even worse, they may fucking block system library upgrades leaving you insecure at worst and out of support at best.
It is not informative yet, but I like that it’s blue. It’s a quite recognizable color. Windows made it recognizable by having a lot of BSODs. People are asking why it couldn’t be just black, but with non-black BSOD one can recognize it instantly without reading the text.
Just for reference, a few years back, (ex-Microsoft) David Plummer had this historical dive into the (MIPS) origin of the blue color, and how Windows is not blue anymore: youtu.be/KgqJJECQQH0?t=780
it’s so annoying that these repositories are so ancient that debs are necessary at all . but it comes in handy for things like lutris, which Ubuntu and mint shipped a broken version for at least a year
It ought to be mandatory to write this out whenever talking about Linux. I’ve seen more than one person bash Linux in a public forum “because it has digital rights management built into the kernel” after they’ve misinterpreted some news headline.
Of all the things to take from windows, this is one of the better ones. Especially if it gets more info in the future. For less tech-literate users, a screen like this is a lot better than a hard to read dump to a terminal.
I’d suggest some kind of “press this key to view debug information” text (or make it documented but not visible, to avoid people just pressing whatever button is written on the screen)
People aren’t idiots. If they don’t know what it means they can look it up or ask for help.
Flip that. People are idiots. If they don’t know what something means, they won’t look it up. Not Desktop Linux users today but, definitely normies if Linux ever comes on a system they buy in the future.
How are you going to use your computer when the kernel panics. That’s kind of the problem, it panicked. It would be nice if it rebooted after a minute or two
Any information given would obviously be for use with another device.
QR code, for example. These are instructions or information about the crash, not links (except the QR code, which would obviously be read by another device).
I can’t believe people construed the lack of this feature in a brand new software as bad Canonical want to kill deb! It’s a brand new software. Features need work. Either go and write them or wait for someone else to do it.
That would definitely be valid for a smaller community supported distro like mint, but canonical is a big company that already has kind of a bad reputation for things like that so I think it was reasonable for people to complain
A big company eh? They’re about 20 times smaller than Red Hat. They very much depend on Debian and the larger FOSS community to get their OS built.
I’ve been on this train since 2004 and I’ve been paying attention. Not all but a lot of the flak they’ve been getting over the years has been based on misinformation and ignorance. But trying to get things objective and correct doesn’t make for a good flame war.
I can’t believe people construed the lack of this feature in a brand new software as bad Canonical want to kill deb!
Most loud mouth open source enthusiasts are often toxic entitled choosing beggars. If any of their desires are not met, the project is dying or dead even though the statistics say otherwise.
Fork it and fix things you want to make it better?
No way bro. I want someone else to work on the feature I requested one year ago.
They removed installing another package that did this by default in the same version where they introduced the App Center. Ubuntu Software never handled installing third-party debs, gdebi did. And in the version where they introduced the App Center, they stopped bundling gdebi by default.
Also, the old behavior was that you double click on a deb file and App Center just hangs. This was shipped in the LTS.
This has been false for a while. The Ubuntu Software Center has been handling deb installs for a while on my machines. I just checked on my oldest machine - 20.04 - and the Ubuntu Software app launches on double clicking a deb file. I do not have gdebi installed. I don’t recall when it replaced gdebi, whether it was in 16.04, 18.04 or 20.04 but it’s definitely the case in 20.04. So check your info before getting worked up.
The kernel art department really failed us here. Instead of a blue screen of death we could've had, I don't know, literally any other colour. I'd have gone with the Puce Screen of Panic.
linux
Oldest
This magazine is from a federated server and may be incomplete. Browse more on the original instance.