I’m not sure if this is the best community to post in, but I just bought a used computer and slotted in an RX480 as the GPU. I installed KDE Neon 5.27 on it, and it worked flawlessly for 2 days.

Then, even though it was working earlier today, it slept and then would not wake up. So I turned off the power and turned it back on again, and was greeted with this error screen:

The only prior error message I’d gotten from the system was when I tried to install wine for one application, it told me some packages weren’t up to date, without a way to fix it. I can enter the BIOS just fine.

What is going on? How do I fix this?

  • MadMaurice
    19•1 year ago

    None of what’s visible helps identifying the error. Try journalctl -xb as suggested it might show more relevant information

    Edit: oops should’ve been joirnalctl instead of journal

    • @[email protected]OP
      9•1 year ago

      I tried to do that, and it couldn’t find the journal package. So I tried to install it, but apt, flatpak, nor snap could find the package to install.

      • @Penta
        26•1 year ago

        This was probably supposed to say “journalctl -xb”

        • @[email protected]OP
          4•1 year ago

          Okay, that command works for me. The last line says that /etc/hosts:7: hostname “SuperSpruce_Iron_3900X” is not valid, ignoring.

          • DefederateLemmyMlEnglish
            13•1 year ago

            Not sure if this is the root cause of your boot failure, but underscores in hostnames are not allowed. A- Z, 0-9 and - are the only allowed characters.

      • @pivot_root
        22•1 year ago

        You’re welcome to use whatever init system you want, but Systemd solves a lot of the bullshit problems and limitations that come from init.d init scripts. Systemd also has a lot of its own bullshit and bloat, but it does an excellent job at actually being an init system and service manager if you know how to properly use it.

        • @[email protected]
          7•1 year ago

          solves a lot of the bullshit problems and limitations that come from init.d init scripts.

          So do the other ~7 init systems developed since then. And, as far as i know, all of them print their relevant trouble directly to stderr. Who cares about SysV still?

          Hey guys, why all the downvotes? Systemd is known for throwing all the irrelevant stuff at you, making it troublesome to debug. Which is why i switched. And i can confirm: Runit, S6, OpenRC and even simple Dinit are way better in that regard (and they do make less trouble generally).

        • @[email protected]
          -1•1 year ago

          Almost everything you said is mere brochureware perpetuated by a tribe stronger than the vi mafia.

          Sysvinit starts fast, starts well, and doesn’t try to control mounts, cron, Getty, and everything else.

          The"but it retries things" whine was a solved problem in 2001. So easy.

          The EL6 machines I have in storage start faster than the el7 machines joining them. PCLinuxOS is a very valid non-systemd system that only lacks a documented kickstart emulant.

      • MadMaurice
        2•1 year ago

        I doubt other init systems can make the screen bigger so that the vital part of the kernel log is still on screen, but be my guest to prove me wrong 🙄