• MentalEdge@sopuli.xyz
        2·
        8 days ago

        The panic screen gives me a QR code containing the last few pages of journalctl. Something about amdgpu.

        I haven’t looked into it yet. It’s only been occuring after my system sleeps over night, meaning when I sit down to use my PC and it happens, I’m not in a mood to start tinkering first thing, so I’ve just been rebooting and getting on with my day.

        Didn’t happen when I went to wake my machine just now though.

        • green_copper@kbin.earth
          2·
          8 days ago

          Hmm, I can’t really help you remote-diagnosing it (but you can PM me if you want help decoding the logs).

          If the problem started not long ago, it might be a kernel-regression.

          • MentalEdge@sopuli.xyz
            2·
            8 days ago

            This wont be my first rodeo. I’m confident I’ll figure it out even if it doesn’t go away with either an update or downgrade, I’m just putting it off since it isn’t really interfering with use.

            I just brought it up because it was a relevant thing which would funny to mention :D

    • iknowitwheniseeit@lemmynsfw.com
      6·
      9 days ago

      I find editing systemd files less error prone and generally easier than editing shell scripts, which is how systems used to boot.

      It’s easy to disable (for example) the time sync and DNS bits of it and just use it for the init functionality.

      I’m not super thrilled by journalctl, but logging wasn’t great before that either.¯\_(ツ)_/¯

  • green_copper@kbin.earth
    2·
    9 days ago

    As much as it hurts to disappoint Hu Tao, I just migrated all my Podman containers from Podman-Compose to Quadlets and I like this setup better; not going back.