Elektrine lite

← Feed

@A_norny_mousse@piefed.zip

2026-09-26 07:56 UTC

BSOD 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

Replies (7)

  • @ark3@lemmy.dbzer0.com 2026-09-26 08:53

    github.com/systemd/systemd/issues/38098

    Open ##4853645

  • @Dirk@lemmy.ml 2026-09-26 09:11

    Okay, great. I don’t have a smartphone. No I cannot see the error log anymore.

    Open ##4853725

  • @black0ut@pawb.social 2026-09-26 09:46

    The QR code contains the panic stack trace text, directly encoded into a URL and a parameter. When you scan it, it goes to the website, which takes the parameter, decodes it and displays it as plain text. Personally, I think it’s a terrible idea compared to just showing the logs, because now you need internet and a phone with a camera to read a kernel panic log.

    Open ##4853952

  • @Sanguine@lemmy.dbzer0.com 2026-09-26 12:04

    I never scan, just check the journal for errors from previous boot after restart. Most recent was my pcie low power shenanigans with my onboard WiFi. Simple fix and now its working /no bsod since.

    Open ##4855621

  • @Ephera@lemmy.ml 2026-09-26 14:54

    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…

    Open ##4857307

  • @hexagonwin@lemmy.today 2026-09-26 17:05

    can that dense code be scanned with a phone? pretty sure mine can’t

    Open ##4859096

  • @mactan@lemmy.ml 2026-09-28 10:21

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

    Open ##4882548