final edit: You want real logs instead? add this to your kernel command: drm.panic_screen=kmsg

Kinda funny, kinda neat.

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 and did not panic. To reproduce, boot your device with init=/bin/sh, then type exit.

CachyOS

The picture above is generated by Drm panic which is part of the kernel itself, or maybe a separate module. The data in the QR code is the kmsg log.

Not systemd, which wasn’t running when that happened.

And it’s been around for years; I guess I haven’t had a kernel panic in a long time.

  • Ephera@lemmy.ml
    1·
    22 hours ago

    Did you maybe try to press Esc?
    When it shows the pretty boot logo, you can do that to see the logs, so maybe it works here as well…

    • SteveTech@aussie.zone
      3·
      14 hours ago

      Nah, when a kernel panic hits then everything’s screwed.

      Pressing ESC does work for systemd-bsod (which is different) and as you mentioned Plymouth; but not drm_panic.