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.

Edit: Installing linux-lts and directing my bootloader to it worked. I didn’t even need to install linux.

    • dudesssOPEnglish
      1·
      25 days ago

      Some errors I’m getting in the journalctl logs:

      gl: failed to create dri2 screen

      ZINK: failed to choose pdev

      Failed to initialize glamor, falling back to sw

      And on my boot screen if I have set nomodeset beforehand, the sreen where I put my password to decrypt LUKS, the console says:

      :: running early hook (udev)

      Starting systemd-udevd version 250.1-1-arch

      amdgpu 0000:09:00.0: probe with driver amdgpu failed with error -22

      :: running hook (udev)

      :: Triggering uevents…

      :: running hook (keymap)

      :: Loading keymap…done.

      :: running hook (encrypt)

            • dudesssOPEnglish
              1·
              23 days ago

              Fedora is causing the same problem now.

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

              • just_another_person@lemmy.worldEnglish
                1·
                23 days ago

                Interesting. It would suggest there is an issue with your card.

                Are you dual booting Windows as well? Any way you could check power and heat measurements on the card with Windows tools? A Linux Kernel is not so easy to just topple like this with a normally behaving piece of hardware. Windows should be the first to have issues. Also check if the Catalyst logs show any similar kind of warnings.

                • dudesssOPEnglish
                  1·
                  23 days ago

                  I’m not sure what Catalyst. I have Adrenaline instead. Its something similar maybe?

                  Also, I ran 3Dmark on Windows, and my GPU had very good stress test results.

            • dudesssOPEnglish
              1·
              23 days ago

              Fedora is able to modprobe amdgpu, which my current installed Arch cannot.

              • just_another_person@lemmy.worldEnglish
                1·
                23 days ago

                Fedora should just be picking it up in boot, so I’m sensing there is something up with that card.

                The way hardware detection works on boot is by getting the deviceIDs and paths first, then loading the driver. From your logs it seems that the first part is done, but then on loading the driver’s the card “goes away” when engaged by the drive being loaded. I would guess a possible power issue.

                Are you running an APU at all, and does your motherboard also have video output, or just the GPU card?

                • dudesssOPEnglish
                  1·
                  23 days ago

                  The motherboard does have an onboard graphics for HDMI, but I never seem to get it working. I’m not sure what to do to get it working. Remove the GPU and reset the CMOS?

                  Already, I ran 3dmark on Windows, and my success rate was very high.

                  I’m running a Ryzen 9 5900x CPU

  • TootSweet@lemmy.worldEnglish
    2·
    26 days ago

    If I’m understanding, you can get into BIOS using the delete key (or whatever key your motherboard uses to get into BIOS). You can also get the bootloader to display a choice of boot entries that you can choose between. (Incidentally, which bootloader are you using? Grub? Syslinux? rEFInd? Something else? And are you booting in EFI or legacy BIOS mode?) But if you choose an option, you sometimes get a solid black screen with nothing on it and sometimes get… what? Completely normal operation?

    • dudesssOPEnglish
      2·
      26 days ago

      All you said was correct. And I’m using systemd.

      If I press e on the boot loader choice, then put nomodeset at the end of the entry, I’m able to have display, but it looks pretty choppy compared to when it boots normally without issues without nomodeset.

      I have a 6900xt GPU, and

      /lib/firmware/amdgpu/

      Is missing a driver for the “navi 21” codename / family series. I don’t see it in the full Git downloads either.

  • dudesssOPEnglish
    1·
    22 days ago

    I would like to try the amdgpu-pro-installer package, but yay - v amdgpu-pro-installer with or without verbose gives me a blank response right away.

    If I use a fake package name, it does the same. If I use another existing one, it works.

    From my understanding, I may be able to use PKGBUILD instead of yay?

  • dudesssOPEnglish
    1·
    23 days ago

    I’m also having problems with the flatpak Discover center where I can’t install nor update packages. I might reformat my operating system like I sadly have to do a few times a year to fix bugs (Whether Arch, Ubuntu, or any Linux).

    However my operating system is encrypted with LUKS. And I have other drives connected via raid mirroring, and I don’t want to lose access to anything saved.