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@discuss.tchncs.de
    11·
    11 months ago

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

    • SuperSpruce@lemmy.zipOP
      3·
      11 months 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.

        • SuperSpruce@lemmy.zipOP
          1·
          11 months ago

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

          • SpaceCadet@feddit.nlEnglish
            2·
            11 months 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@lemmy.world
        8·
        11 months 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.

  • seaQueue@lemmy.world
    5·
    11 months ago

    Shit’s broke yo.

    Sleep/wake issues with AMD gpu and platform drivers are super, super, super common. Fish back through your kernel journal after a reboot (journalctl -kb -1 should do it) and look for the driver errors immediately after the wake event. If this has been fixed in a later kernel release then update your kernel, if not go report it to either the Ubuntu folks or on the amdgpu gitlab.

  • ∟⊔⊤∦∣≶@lemmy.nz
    3·
    11 months ago

    Can you remove the GPU and use onboard?

    It is mentioning gpu in the errors, so it would be the first thing I would try, to see if the errors change, because I have no idea what’s going on here

  • governorkeagan@lemdro.idEnglish
    31·
    11 months ago

    Have you tried booting in with a live usb? You might be able to do some sort of recovery from there.

    Having said, I’m still very much a Linux noob.

  • Endorkend@kbin.social
    2·
    11 months ago

    Before doing anything, if your screen allows it, swap DP to HDMI or HDMI to DP as output, that may fix this to the point of being able to actually boot and further fix the issue.

    I’ve had this before with drivers where suddenly it would fail on either port but would still run on one of the others.

      • djtech@lemmy.world
        2·
        11 months ago

        The Shell where you typed “systemctl reboot” and “exit”.

        If you are running KDE neon, try “apt update” and “apt upgrade”. If It doesn’t work do “sudo apt update” and “sudo apt upgrade”

        • SuperSpruce@lemmy.zipOP
          3·
          11 months ago

          I ran apt update and some index files failed to download. It was just a warning though.

          But systemctl reboot and exit still fail the same way.

          • djtech@lemmy.world
            2·
            11 months ago

            Before the “systemctl” command: try removing the GPU and booting it up without the GPU If it works, you can skip the “systemctl” commands

          • djtech@lemmy.world
            2·
            11 months ago

            Run “journalctl --lines 200” and send photos of output.

            NOTE: This is all of the logging of the computer, and it’s long (that command select the last 200 entries), so you might have to scroll down using the PageDown key (or arrow down) in order make the photos of everything

            • SuperSpruce@lemmy.zipOP
              2·
              11 months ago

              Note: The computer has an SSD where the OS lives and two HDDs, sda and sdb, set up in RAID 1 because the computer is 3.5 years old.

              • chameleon@kbin.social
                1·
                11 months ago

                The RAID1 seems to be failing according to that screenshot. That breaks the “Local File Systems” task and since quite a lot of things tend to depend on that, many things usually end up failing in an annoying cascade failure. It’s also failing with a timeout instead of a strict error, which is odd.

                Either way, I’d try commenting that line for /mnt/raid in /etc/fstab for now and seeing if that makes the system boot. It’s possible that journalctl -u dev-md0.service or systemctl status dev-md0.service might tell you more, but it’s 50/50 if it’ll be anything useful.

                • SuperSpruce@lemmy.zipOP
                  1·
                  11 months ago

                  How do I edit /etc/fstab if I’m not even able to boot the system? Or am I already booted in the system, just in a CLI environment?