226
submitted 1 week ago by [email protected] to c/[email protected]
top 50 comments
sorted by: hot top controversial new old
[-] [email protected] 82 points 1 week ago

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.

[-] [email protected] 36 points 1 week ago

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: https://youtu.be/KgqJJECQQH0?t=780

[-] [email protected] 6 points 1 week ago

Oh, thanks! I don't know much about the current state of Windows.

[-] [email protected] 2 points 1 week ago

Here is an alternative Piped link(s):

https://piped.video/KgqJJECQQH0?t=780

Piped is a privacy-respecting open-source alternative frontend to YouTube.

I'm open-source; check me out at GitHub.

[-] [email protected] 2 points 1 week ago

Hey @[email protected] the last chapter of this video is called redscreen, are you David Plummer? lol

[-] [email protected] 76 points 1 week ago

Reminds me of my Windows XP days when I used to customise the hell out of everything I could... custom boot screen... and yes custom BSOD. Which I switched to red 🟥❗ One day my PC RSODs in front of a family member and he said, "Oh shit, that must be really bad if it's red instead of blue!" 😂

[-] [email protected] 20 points 1 week ago

VMware went with Purple for their hypervisors so you get a PSOD instead. Always was fun when you’d hit the console for a server and get greeted by that instead of the yellow and black split screen.

[-] [email protected] 3 points 1 week ago

Ahh, that sweet yellow and black split screen 😌

[-] [email protected] 58 points 1 week 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.

[-] [email protected] 34 points 1 week ago* (last edited 1 week ago)

I believe the main contributor for drm_panic wants to add one eventually. Here's what it might look like:

DRM panic handler panic screenshot https://gitlab.com/kdj0c/panic_report/-/issues/1

Link if you can't scan

Also it looks like the colours are configurable at compile time (with white on black default).

[-] [email protected] 8 points 1 week ago

Ah man, I was hoping I'd be rickrolled

[-] [email protected] 4 points 1 week ago

This looks EXACTLY as I imagined!

[-] [email protected] 11 points 1 week ago

And windows shows it for a few seconds, never enough time to pick the phone.

[-] [email protected] 4 points 1 week ago* (last edited 1 week ago)

Agreed. Probably the only ~~One of the~~ good 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

[-] [email protected] 3 points 1 week ago

You have to disable auto reboot on bsod

load more comments (2 replies)
[-] [email protected] 50 points 1 week ago

What's DRM in this context? Surely linux kernel doesn't do digital rights management?

[-] [email protected] 79 points 1 week ago

Direct Rendering Manager. Part of Linux kernel to communicate with GPUs.

[-] [email protected] 44 points 1 week ago

Direct Rendering Manager

[-] [email protected] 28 points 1 week ago
[-] [email protected] 4 points 1 week ago

Doesn't matter; I still get triggered by it every time anyway.

[-] [email protected] 21 points 1 week ago

Actually there is DRM in the kernel thanks to the HDMI blobs.

[-] [email protected] 17 points 1 week ago

Fuck HDMI. The committee makes doing custom hardware near impossible unless you're a mega corp

[-] [email protected] 6 points 1 week ago

It was made by Hollywood for Hollywood.

load more comments (1 replies)
[-] [email protected] 11 points 1 week ago

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.

load more comments (1 replies)
[-] [email protected] 46 points 1 week 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.

[-] [email protected] 22 points 1 week ago

They should still include more debugging into.

[-] [email protected] 13 points 1 week ago* (last edited 1 week 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)

[-] [email protected] 5 points 1 week ago

Why? People aren't idiots. If they don't know what it means they can look it up or ask for help.

[-] [email protected] 16 points 1 week ago

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.

load more comments (3 replies)
load more comments (2 replies)
[-] [email protected] 28 points 1 week 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.

[-] [email protected] 23 points 1 week ago

How about black on white with a clear stack trace visible

load more comments (1 replies)
[-] [email protected] 12 points 1 week ago

Puce Screen of Panic

That's class

[-] [email protected] 11 points 1 week ago

Guru Meditation red.

Alternately: yellow-and-black ASCII approximating Evangelion's ALART.

[-] [email protected] 26 points 1 week ago

It needs more information about what went wrong. That's about as useful as a windows BSOD.

[-] [email protected] 7 points 1 week ago

What does drm mean in this context?

[-] [email protected] 10 points 1 week ago

Direct Rendering Manager I believe

[-] [email protected] 7 points 1 week ago

I thought for a minute that Linux now panics when trying to play DRM'd content

[-] [email protected] 7 points 1 week 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.

[-] [email protected] 7 points 1 week 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.

[-] [email protected] 5 points 1 week 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.

[-] [email protected] 3 points 1 week ago* (last edited 1 week ago)

Agree, the old windows blue screen would sear your retinas, could definitely be tuned down a bit.

load more comments (1 replies)
[-] [email protected] 6 points 1 week ago

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!

[-] [email protected] 3 points 1 week ago

It's beautiful. I assume they'll dump the kernel oops log if there's any.

load more comments
view more: next ›
this post was submitted on 16 Jun 2024
226 points (98.7% liked)

Linux

45352 readers
994 users here now

From Wikipedia, the free encyclopedia

Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).

Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.

Rules

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 5 years ago
MODERATORS