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
[–] 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