cross-posted from: https://lemmy.ca/post/54075197

ArchLinux doesn’t boot past the bootloader

I’m able to get to the BIOS on my desktop. But when greeted by the boot loader to choose between Arch or Arch fallback, after choosing, I lose display.

Sometimes I can get display, but its not consistent. Draining my computers power by unplugging the power cord and holding the power button works sometimes. Sometimes a simple reboot will work.

I have an Asus b550m-plus motherboard. It was working great with Arch until recently.

Edit: it uses by press e at the boot loader then putting nomodeset at the end, but the display is choppy compared to when its able to boot without it.

I’m using the systemd-boot loader.

I have a 6900xt GPU. The post I cross posted has more information in the comments. One common error I’m getting is:

probe with driver amdgpu failed with error -22

Here is what my GPU is:

lspci -k | grep -EA3 'VGA|3D|Display'

09:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Navi 21 [Radeon RX 6800/6800 XT / 6900 XT] (rev c0) Subsystem: Gigabyte Technology Co., Ltd Device 232c Kernel modules: amdgpu 09:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Navi 21/23 HDMI/DP Audio Controller

This is my systemd-boot /boot/loader/entries/ – conf file:

# Created by: archinstall
# Created on: 2025-07-06_15-37-58
title   Arch Linux (linux)
linux   /vmlinuz-linux
initrd  /initramfs-linux.img
options cryptdevice=PARTUUID=fg45ehg45-uj675-j76-j76-56756uj56j6:root root=/dev/mapper/root zswap.enabled=0 rootflags=subvol=@ rw rootfstype=btrfs splash
  • heatseat@lemmy.world
    link
    fedilink
    arrow-up
    2
    ·
    2 days ago

    ive had this issue with some dells. using the fallback initramfs works for me for some reason.

      • anon5621@lemmy.ml
        link
        fedilink
        arrow-up
        3
        ·
        3 days ago

        Try to downgraded Linux kernel version or better install linux-lts and use it for now

        • dudesss@lemmy.caOP
          link
          fedilink
          arrow-up
          3
          ·
          3 days ago

          This worked so easily.

          1. installed linux-lts alongside already installed linux.
          2. Updating my bootloader (systemd-boot instead of grub) to use linux-lts instead by changing 2 lines in /boot/loader/entries/my-entry.conf.
          3. Reboot.

          KDE is too slow to be useable now. Should I try reinstalling it?

          Opening another TTS, the terminal runs fast and fine. No process is above 1% CPU and 2℅ memory. Barely any ram space used. A lot of storage space available.

          • dudesss@lemmy.caOP
            link
            fedilink
            arrow-up
            3
            ·
            edit-2
            3 days ago

            Uninstalling all desktop environments and KDE related stuff, then reinstalling kde-desktop and sddm worked.

            It looks better and runs faster than it ever did before!

        • dudesss@lemmy.caOP
          link
          fedilink
          arrow-up
          2
          ·
          2 days ago

          linux-lts is causing the same problem for me. When booting I need to press e and add nomodeset at the end of boot loader.

          sudo modprobe amdgpu modprobe: ERROR: could not insert ‘amdgpu’: Invalid argument

          And the following is blank sudo ls /lib/firmware/amdgpu/ | grep navi21

          • anon5621@lemmy.ml
            link
            fedilink
            arrow-up
            6
            ·
            2 days ago

            Nomodeset is disabling all DRI kernel modules related to videocard so no surprise that u cannot modprobe it .just for test to u have windows somewhere on second disk to test if problem repeating there too to exclude hardware problem

            • dudesss@lemmy.caOP
              link
              fedilink
              arrow-up
              3
              ·
              2 days ago

              Fedora is causing the same problem now.

              I just tried booting into Windows instead, and no problems.

              • anon5621@lemmy.ml
                link
                fedilink
                arrow-up
                3
                ·
                2 days ago

                The only my possible suppose that there are something wrong with current driver of and amd team fucked possibly. Can u load on arch and using ssh to collect logs from dmesg about amdgpu module