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
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
Okay, great. I don’t have a smartphone. So I cannot see the error log anymore.
let’s submit a patch to display error log as text too on the bluescreen
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
I should’ve tried to switch ttys, might have helped.
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=kmsgas a kernel parameter to print the logs instead of the QR.👍
(source)
In other words,
cat /sys/module/drm/parameters/panic_screenwill show you what the current status is.