• @kenkenken@sh.itjust.works
    link
    fedilink
    English
    826 months 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.

  • @Thorned_Rose@sh.itjust.works
    link
    fedilink
    English
    766 months 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!” 😂

    • @ramble81@lemm.ee
      link
      fedilink
      206 months 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.

  • 𝕸𝖔𝖘𝖘
    link
    fedilink
    English
    576 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.

  • Julian
    link
    fedilink
    English
    466 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.

      • @Sekoia@lemmy.blahaj.zone
        link
        fedilink
        13
        edit-2
        6 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
          link
          fedilink
          English
          56 months ago

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

          • @kitnaht@lemmy.world
            link
            fedilink
            166 months 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.

          • @bastion@feddit.nl
            link
            fedilink
            26 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
              link
              fedilink
              English
              16 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@feddit.nl
                link
                fedilink
                36 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).

  • kbal
    link
    fedilink
    286 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.

  • SavvyWolf
    link
    fedilink
    English
    76 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@lemmy.ml
      link
      fedilink
      56 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.

    • @KrapKake@lemmy.world
      link
      fedilink
      3
      edit-2
      6 months ago

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

  • navordar
    link
    fedilink
    76 months ago

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

  • AutoTL;DRB
    link
    English
    66 months 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!

  • Avid Amoeba
    link
    fedilink
    36 months ago

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

  • @yesman@lemmy.world
    link
    fedilink
    -136 months ago

    Once again, Linux is late with a feature that Microsoft not only has had for years, but is famous for.

    • @smileyhead@discuss.tchncs.de
      link
      fedilink
      36 months ago

      It’s normal for things to implement stuff from each other? 🤷

      Microsoft is late with many things too. And I don’t nessesarly think a feature here and there is what makes a good OS, the base stuff is more important.