I have no idea what the QR-code might reveal (I could not read it from this picture), so I pixelised it just to be sure.

FWIW I know exactly what happened. To reproduce, boot your device with init=/bin/sh, then type exit.

Kinda neat.

CachyOS

    • LeLachs@lemmy.ml
      link
      fedilink
      arrow-up
      0
      ·
      16 days ago

      The most important info is at the bottom of the screen. I also believe you can turn this feature off if you prefer plain text

      • SteveTech@aussie.zone
        link
        fedilink
        arrow-up
        0
        ·
        16 days ago

        Switching ttys wouldn’t have done anything. The kernel logs are usually saved to efi_pstore (or sometimes erst) by default though.

        Edit: you can also set drm.panic_screen=kmsg as a kernel parameter to print the logs instead of the QR.

        • A_norny_mousse@piefed.zipOP
          link
          fedilink
          English
          arrow-up
          0
          ·
          15 days ago

          👍

          Drm panic provides different panic screens. The default is “user” which will display a simple friendly message telling the user to reboot the computer. But for kernel developers, you can also set it to “kmsg”, to see the last kmsg lines (so this is equivalent to the current fbcon). You can select the panic screen in Kconfig, or as a module parameter (drm.panic_screen=user) or at runtime with “echo -n kmsg > /sys/module/drm/parameters/panic_screen”

          (source)

          In other words, cat /sys/module/drm/parameters/panic_screen will show you what the current status is.