- cross-posted to:
- linux@programming.dev
- cross-posted to:
- linux@programming.dev
- verstra ( @verstra@programming.dev ) 39•3 months ago
What’s DRM in this context? Surely linux kernel doesn’t do digital rights management?
- jinwk00 ( @jinwk00@lemm.ee ) English59•3 months ago
Direct Rendering Manager. Part of Linux kernel to communicate with GPUs.
- Possibly linux ( @possiblylinux127@lemmy.zip ) English25•3 months ago
DRM came before DRM
- macniel ( @DmMacniel@feddit.de ) 17•3 months ago
Actually there is DRM in the kernel thanks to the HDMI blobs.
- 5714 ( @5714@lemmy.dbzer0.com ) English1•3 months ago
How do they handle the naming confusion?
- 𝕸𝖔𝖘𝖘 ( @01189998819991197253@infosec.pub ) English39•3 months ago
A QR code created from the actual fault text would be super helpful. That way we can scan it and get the full error message (details and all) on another device without having to snap a picture or something. But not like windows does it, where it’s a link to a defunct page. I’m taking about the actual text transcoded into a QR code.
- SteveTech ( @SteveTech@programming.dev ) English28•3 months ago
I believe the main contributor for drm_panic wants to add one eventually. Here’s what it might look like:
https://gitlab.com/kdj0c/panic_report/-/issues/1
Also it looks like the colours are configurable at compile time (with white on black default).
- Brickardo ( @Brickardo@feddit.nl ) 5•3 months ago
Ah man, I was hoping I’d be rickrolled
- 𝕸𝖔𝖘𝖘 ( @01189998819991197253@infosec.pub ) English4•3 months ago
This looks EXACTLY as I imagined!
- kurumin ( @kurumin@linux.community ) English10•3 months ago
And windows shows it for a few seconds, never enough time to pick the phone.
- 𝕸𝖔𝖘𝖘 ( @01189998819991197253@infosec.pub ) English2•3 months ago
Agreed. Probably the only
One of thegood thing about the win98 BSOD is that it crashed/froze along with the computer, and the PC required a hard reboot. Yeah, I know, not intentional, but it allowed me to fully read the message.Edit: crossout
- Julian ( @julianh@lemm.ee ) English37•3 months ago
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.
- Possibly linux ( @possiblylinux127@lemmy.zip ) English17•3 months ago
They should still include more debugging into.
- Sekoia ( @Sekoia@lemmy.blahaj.zone ) 11•3 months ago
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)
- Possibly linux ( @possiblylinux127@lemmy.zip ) English6•3 months ago
Why? People aren’t idiots. If they don’t know what it means they can look it up or ask for help.
- bastion ( @bastion@feddit.nl ) 2•3 months ago
Because for the bulk of users, unless they are power users, all they need to know is that things didn’t work.
Things actually useful to have on the BSOD:
- distro-specific instructions for submitting a bug report
- option to reboot
- option to show debug info
- option to show a qr code that submits a bug report
- and, if configured by the distro or system admin, debug info
- Possibly linux ( @possiblylinux127@lemmy.zip ) English1•3 months ago
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
- bastion ( @bastion@feddit.nl ) 2•3 months ago
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).
- MondayToFriday ( @MondayToFriday@lemmy.ca ) 1•3 months ago
How would a kernel that has already crashed handle keypresses?
- Sekoia ( @Sekoia@lemmy.blahaj.zone ) 1•3 months ago
I’m not an OS dev, I have no idea how stuff this low-level works.
- kbal ( @kbal@fedia.io ) 22•3 months ago
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.
- Possibly linux ( @possiblylinux127@lemmy.zip ) English16•3 months ago
How about black on white with a clear stack trace visible
- The Doctor ( @drwho@beehaw.org ) English1•3 months ago
That would be far too helpful.
- QuazarOmega ( @QuazarOmega@lemy.lol ) English10•3 months ago
Puce Screen of Panic
That’s class
- cmnybo ( @cmnybo@discuss.tchncs.de ) English18•3 months ago
It needs more information about what went wrong. That’s about as useful as a windows BSOD.
- navordar ( @nawordar@lemmy.ml ) 5•3 months ago
I thought for a minute that Linux now panics when trying to play DRM’d content
- SavvyWolf ( @savvywolf@pawb.social ) English5•3 months ago
Did they have to go with such a loud shade of blue? It would look so much better on the eyes if it was a nice deep dark blue.
Tbh I don’t even know why it needs to be blue or any colour at all.
- ShortN0te ( @ShortN0te@lemmy.ml ) 3•3 months ago
Everyone knows what the blue screen is. This makes the implication when the screen does appear really obvious.
No need to reinvent the wheel.
- Possibly linux ( @possiblylinux127@lemmy.zip ) English1•3 months ago
Exactly
Black with big white text would be nice
This is the best summary I could come up with:
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!
- biribiri11 ( @biribiri11@lemmy.ml ) 4•3 months ago
Also see: systemd-bsod. Generates QR codes, too. I think blue for userspace boot-time errors and black for kernel stuff might be nice.
- Avid Amoeba ( @avidamoeba@lemmy.ca ) 3•3 months ago
It’s beautiful. I assume they’ll dump the kernel oops log if there’s any.
- Possibly linux ( @possiblylinux127@lemmy.zip ) English2•3 months ago
They should make it black instead.
- e8d79 ( @e8d79@discuss.tchncs.de ) 2•3 months ago
I would prefer purple.
- Possibly linux ( @possiblylinux127@lemmy.zip ) English1•3 months ago
Maybe purple with yellow text
- ryannathans ( @ryannathans@aussie.zone ) 2•3 months ago
I would have gone with red… red = error
- Possibly linux ( @possiblylinux127@lemmy.zip ) English5•3 months ago
That would make it just as hard to read. Black on white offers the most contrast
- ryannathans ( @ryannathans@aussie.zone ) 2•3 months ago
Gold on purple offers more iirc