7
ArchLinux doesn't boot past the bootloader (lemmy.ca)
submitted 1 year ago by to c/archlinux@discuss.tchncs.de
16 comments fedilink hide all child comments
 

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.

you are viewing a single comment's thread
view the rest of the comments
[–] [S] 1 point 1 year ago* (last edited 1 year ago) (10 children)

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)

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 10 child comments
    •
  • [–] 1 point 1 year ago (9 children)

    Your AMD card isn't getting initialized properly.

    What kernel are you on?

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 9 child comments
    •
  • [–] [S] 1 point 1 year ago (8 children)

    6.17.5-arch1-1

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 8 child comments
    •
  • [–] 2 points 1 year ago (7 children)

    Just to rule out a hardware problem, could you boot a LiveUSB of another distro like Fedora to see if that works as expected?

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 7 child comments
    •
  • [–] [S] 1 point 1 year ago (2 children)

    Fedora is causing the same problem now.

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

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 1 point 1 year ago (1 child)

    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.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] [S] 1 point 1 year ago (3 children)

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

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 3 child comments
    •
  • [–] 1 point 1 year ago (2 children)

    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?

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] [S] 1 point 1 year ago* (last edited 1 year ago) (1 child)

    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

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] 1 point 1 year ago

    Try going into your CMOS and making sure that onboard graphics are disabled, as well as HDMI. It may only be there in case you have an APU and automatically disabled when one isn't present.

    Also, check and see if your motherboard has any firmware updates. That could be hugely important here.

  • permalink
  • fedilink
  • source
  • parent