• kenkenkenEnglish
    arrow-up
    84
    arrow-down
    2
    ·
    4 months ago
    link
    fedilink

    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_RoseEnglish
    arrow-up
    76
    arrow-down
    0
    ·
    4 months ago
    link
    fedilink

    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
      arrow-up
      20
      arrow-down
      0
      ·
      4 months ago
      link
      fedilink

      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.

  • 𝕸𝖔𝖘𝖘English
    arrow-up
    59
    arrow-down
    0
    ·
    4 months ago
    link
    fedilink

    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.

  • verstra
    arrow-up
    51
    arrow-down
    1
    ·
    4 months ago
    link
    fedilink

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

    • jinwk00English
      arrow-up
      79
      arrow-down
      0
      ·
      4 months ago
      link
      fedilink

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

    • bishop
      arrow-up
      44
      arrow-down
      0
      ·
      4 months ago
      link
      fedilink

      Direct Rendering Manager

      • grueEnglish
        arrow-up
        5
        arrow-down
        1
        ·
        4 months ago
        link
        fedilink

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

    • macniel
      arrow-up
      21
      arrow-down
      0
      ·
      4 months ago
      link
      fedilink

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

      • potatopotato
        arrow-up
        17
        arrow-down
        0
        ·
        4 months ago
        link
        fedilink

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

        • Xephonian
          arrow-up
          6
          arrow-down
          0
          ·
          4 months ago
          link
          fedilink

          It was made by Hollywood for Hollywood.

      • 5714English
        arrow-up
        1
        arrow-down
        0
        ·
        4 months ago
        link
        fedilink

        How do they handle the naming confusion?

    • ffhein
      arrow-up
      11
      arrow-down
      0
      ·
      4 months ago
      link
      fedilink

      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.

  • JulianEnglish
    arrow-up
    48
    arrow-down
    2
    ·
    4 months ago
    link
    fedilink

    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
        arrow-up
        13
        arrow-down
        0
        ·
        4 months ago
        edit-2
        4 months ago
        link
        fedilink

        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 linuxEnglish
          arrow-up
          7
          arrow-down
          2
          ·
          4 months ago
          link
          fedilink

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

          • kitnaht
            arrow-up
            18
            arrow-down
            2
            ·
            4 months ago
            link
            fedilink

            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
            arrow-up
            2
            arrow-down
            0
            ·
            4 months ago
            link
            fedilink

            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 linuxEnglish
              arrow-up
              1
              arrow-down
              0
              ·
              4 months ago
              link
              fedilink

              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
                arrow-up
                3
                arrow-down
                0
                ·
                4 months ago
                link
                fedilink

                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
          arrow-up
          1
          arrow-down
          0
          ·
          4 months ago
          link
          fedilink

          How would a kernel that has already crashed handle keypresses?

          • Sekoia
            arrow-up
            1
            arrow-down
            0
            ·
            4 months ago
            link
            fedilink

            I’m not an OS dev, I have no idea how stuff this low-level works.

  • kbal
    arrow-up
    28
    arrow-down
    0
    ·
    4 months ago
    link
    fedilink

    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 linuxEnglish
      arrow-up
      23
      arrow-down
      0
      ·
      4 months ago
      link
      fedilink

      How about black on white with a clear stack trace visible

    • mindbleach
      arrow-up
      11
      arrow-down
      0
      ·
      4 months ago
      link
      fedilink

      Guru Meditation red.

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

  • cmnyboEnglish
    arrow-up
    26
    arrow-down
    0
    ·
    4 months ago
    link
    fedilink

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

    • boonhet
      arrow-up
      10
      arrow-down
      0
      ·
      4 months ago
      link
      fedilink

      Direct Rendering Manager I believe

  • biribiri11
    arrow-up
    7
    arrow-down
    0
    ·
    4 months ago
    link
    fedilink

    Also see: systemd-bsod. Generates QR codes, too. I think blue for userspace boot-time errors and black for kernel stuff might be nice.

  • SavvyWolfEnglish
    arrow-up
    8
    arrow-down
    1
    ·
    4 months ago
    link
    fedilink

    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
      arrow-up
      5
      arrow-down
      0
      ·
      4 months ago
      link
      fedilink

      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
      arrow-up
      3
      arrow-down
      0
      ·
      4 months ago
      edit-2
      4 months ago
      link
      fedilink

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

  • navordar
    arrow-up
    7
    arrow-down
    0
    ·
    4 months ago
    link
    fedilink

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

  • AutoTL;DRBEnglish
    arrow-up
    6
    arrow-down
    0
    ·
    4 months ago
    link
    fedilink

    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
    arrow-up
    3
    arrow-down
    0
    ·
    4 months ago
    link
    fedilink

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

  • yesman
    arrow-up
    7
    arrow-down
    20
    ·
    4 months ago
    link
    fedilink

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

    • phoenixz
      arrow-up
      13
      arrow-down
      0
      ·
      4 months ago
      link
      fedilink

      Not sure if you’re coming or simping M$

    • smileyhead
      arrow-up
      3
      arrow-down
      0
      ·
      4 months ago
      link
      fedilink

      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.