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: https://youtu.be/KgqJJECQQH0?t=780
Hey @Thorned_Rose@sh.itjust.works the last chapter of this video is called redscreen, are you David Plummer? lol
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.
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!” 😂
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.
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.
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).
And windows shows it for a few seconds, never enough time to pick the phone.
This should be the default option when the blue screen happened, giving users chance to scan the QR and find out about the causes before they can try restarting their PC
What’s DRM in this context? Surely linux kernel doesn’t do digital rights management?
Fuck HDMI. The committee makes doing custom hardware near impossible unless you’re a mega corp
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)
Why? People aren’t idiots. If they don’t know what it means they can look it up or ask for help.
