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?

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.

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.

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

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?

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.

Fedora is causing the same problem now.

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

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

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

Thanks, but I don't like using distros other than from the main providers.

Good to know. But I'm not a first time user.I have had problems with BTRFS as well.. its reminder to use XFS or ext4.

6.17.5-arch1-1

Your AMD card isn't getting initialized properly.

What kernel are you on?

just try some out via live boot? cachyOS seems like a solid choice if you're into gaming

I don't recommend it for first time users. Going through the install process is basically the tutorial level for Arch. The arch install scripts are for shortcutting an install process you're already familiar with. If you want arch with a no pain installer use something like EndeavourOS.

For example, I've used Arch for years, and tried experiment with BTRFS using the archinstall script. I deeply regretted it because it didn't configure SWAP correctly so my laptop couldn't hibernate. I had to rip out zram and put in a swapfile.

You must have an idea of what its going to do before using it. In the case of you're bloated KDE install, it installed the full kde package group, which almost no one wants. You could use the archinstall script to install everything but the graphical environment and then do that yourself, post install.

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.

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)

Have you checked if there's journalctl logs for the erroneous boots?

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.

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?

They'd probably go after more than just Arch, right? Like, if it was some sort of op to disrupt Linux adoption, there'd be more targets I think.

Microsoft and Apple

Like who?

I wonder if a competitor would stoop this low…

Damn, still going? Who the fuck wants to take down Arch?