BSOD (thelemmy.club)
submitted 3 days ago* (last edited 2 days ago) by to c/linux@lemmy.ml
 

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.

you are viewing a single comment's thread
view the rest of the comments
[–] 1 point 1 day ago*

when your boot doesn't get far enough to use termbin this is the next next best thing . remember, nobody wants a smartphone picture of a monitor with logs on it

  • source