[SOLVED] PC won't boot if slotting in new GPU

realitaetsverlust · 2022-12-17 10:08:51

So I bought the new RX 7900 XTX and planned on slotting it into my PC. Sadly, it hasn't quite worked as flawlessly as I would expect.

When slotting in the new GPU, my linux distro boots until "Triggering uevents". One second later, a lot of small colored dots appear on the top right and nothing happens. It's a bit hard to explain, so I made a picture of the error, you can view that below.

Anyways, at first I thought it's because I haven't updated my PC in a while, I was gone for 2 weeks and just arrived at home. So I grabbed my arch linux boot stick, flashed an up-to-date ISO on it and booted it up. However, I ran into the exact same problem. That made me a bit nervous and I thought the card is broken. So I booted into my windows partition that I needed for work, and it worked perfectly fine. Then I booted into a gparted live ISO, which worked fine aswell. Booting into the arch linux boot stick still didn't work, so I slotted in my old GPU (an RX 6800 XT) and it worked fine. I updated my system via `pacman -Syu` and thought that would do it. So again, old GPU out, new GPU in, turn on - still nothing, still same error. So I switched GPUs again and checked the boot log and I found this error message:

10:15:30 exodus kernel: amdgpu 000:2f:00.0: Direct firmware load for amdgpu/psp_13_0_0_sos.bin failed with error -2
10:15:30 exodus kernel: amdgpu 000:2f:00.0: amdgpu: failed to init sos firmware
10:15:30 exodus kernel: [drm:psp_sw_init [amdgpu]] *ERROR* Failed to load psp firmware!
10:15:30 exodus kernel: [drm:amdgpu_device_init.cold [amdgpu]] *ERROR* sw_init of IP block <psp> failed -2
10:15:30 exodus kernel: amdgpu 000:2f:00.0: amdgpu: amdgpu_device_ip_init failed
10:15:30 exodus kernel: amdgpu 000:2f:00.0: amdgpu: Fatal error during GPU init
10:15:30 exodus kernel: amdgpu 000:2f:00.0: amdgpu: amdgpu: finishing device.
10:15:30 exodus kernel: amdgpu: probe of 000:2f:00.0 failed with error -2

I've also attached this error message as an image down below.

The card also is not damaged or broken as it works on another OS on the same system. It also works on a different system that uses ZorinOS.

Here is the link to the two images: https://imgur.com/a/EXcCcVY

I kinda expected it to go smoothly as I'ved used an AMD GPU before, but that sadly was not the case. If anyone knows what to do here, I'd be grateful.

Last edited by realitaetsverlust (2022-12-25 18:58:31)

Slithery · 2022-12-17 11:45:30

The new linux-firmware package that card requires hasn't made it to the main repos yet, it is in testing though so you can install it by doing...

sudo pacman -U https://repo.slithery.uk/testing/os/x86_64/linux-firmware-20221214.f3c283e-1-any.pkg.tar.zst

https://www.phoronix.com/news/RDNA3-AMD … ware-Added
https://archlinux.org/packages/?sort=&q … =&flagged=

realitaetsverlust · 2022-12-17 12:15:47

It sounds like it absolutely makes sense, however, it doesn't do anything. I still have the exact same behavior when booting up. Do I have to rebuild grub or something in order for it to work?

Slithery · 2022-12-17 12:20:59

You may also have to rebuild your intramfs...

sudo mkinitcpio -P

realitaetsverlust · 2022-12-17 12:29:48

Okay, awesome, that worked.

But now, my mouse cursor disappeared. It still works and I can hover over stuff, but it's invisible. I assume that's more of a KDE issue, right?

Last edited by realitaetsverlust (2022-12-17 12:30:09)

seth · 2022-12-17 14:30:50

Wayland or X11?
xf86-video-amdgpu or modesetting?
You probably don't want to use the amdgpu driver, but can otherwise https://man.archlinux.org/man/extra/xf8 … .en#Option

realitaetsverlust · 2022-12-17 16:42:27

seth wrote:

Wayland or X11?
xf86-video-amdgpu or modesetting?
You probably don't want to use the amdgpu driver, but can otherwise https://man.archlinux.org/man/extra/xf8 … .en#Option

X11
xf86-video-amdgpu from what I can tell

I basically did everything as explained in the wiki here https://wiki.archlinux.org/title/AMDGPU. I installed the mesa package and all the vulkan related stuff.

seth · 2022-12-17 16:51:12

xf86-video-amdgpu from what I can tell

xorg log?
https://wiki.archlinux.org/title/Xorg#General
Also

pacman -Qs xf86-video

And as mentioned, try without.

realitaetsverlust · 2022-12-17 16:59:15

Log: https://bpa.st/RI5EU

$ pacman -Qs xf86-video
local/xf86-video-amdgpu 22.0.0-1 (xorg-drivers)
    X.org amdgpu video driver

So ye, I am using that driver.

Trying without would be simply uninstalling it, right?

seth · 2022-12-17 17:02:02

Yes, but after removing it make sure that nothing explicitly references it:

grep -ri amdgpu /{etc,usr/share}/X11/xorg.conf*

Otherwise X11 will fail to start.

realitaetsverlust · 2022-12-17 17:18:32

Okay, so I got my cursor back, that's good. However, the system is still unbelievable sluggish and unresponsive. Moving my mouse between my monitors (only between my monitors, funny enough) or trying to open windows takes several seconds of screen freeze to actually happen (I ran `glxgears` in the top left corner to see if the desktop freezes). It also seems to affect anything like a window, for example, opening the "start menu" or hovering over tabs in steam which basically opens a dropdown causes the same delay. As if there was some fuckery with the compositor.

In the Xorg-Log, I see a whole lot of those:

[   528.703] (II) event8  - ASUS ROG SPATHA: SYN_DROPPED event - some input events have been lost.
[   529.658] (II) event8  - ASUS ROG SPATHA: SYN_DROPPED event - some input events have been lost.
[   532.488] (II) event8  - ASUS ROG SPATHA: SYN_DROPPED event - some input events have been lost.
[   533.440] (II) event8  - ASUS ROG SPATHA: SYN_DROPPED event - some input events have been lost.
[   551.237] (II) event8  - ASUS ROG SPATHA: SYN_DROPPED event - some input events have been lost.
[   551.237] (II) event8  - ASUS ROG SPATHA: WARNING: log rate limit exceeded (5 msgs per 30s). Discarding future messages.
[   587.290] (II) event8  - ASUS ROG SPATHA: SYN_DROPPED event - some input events have been lost.
[   588.307] (II) event8  - ASUS ROG SPATHA: SYN_DROPPED event - some input events have been lost.
[   596.024] (II) event8  - ASUS ROG SPATHA: SYN_DROPPED event - some input events have been lost.
[   597.158] (II) event8  - ASUS ROG SPATHA: SYN_DROPPED event - some input events have been lost.
[   598.140] (II) event8  - ASUS ROG SPATHA: SYN_DROPPED event - some input events have been lost.
[   598.140] (II) event8  - ASUS ROG SPATHA: WARNING: log rate limit exceeded (5 msgs per 30s). Discarding future messages.
[   623.609] (II) event8  - ASUS ROG SPATHA: SYN_DROPPED event - some input events have been lost.
[   624.675] (II) event8  - ASUS ROG SPATHA: SYN_DROPPED event - some input events have been lost.
[   639.893] (II) event8  - ASUS ROG SPATHA: SYN_DROPPED event - some input events have been lost.
[   641.910] (II) event8  - ASUS ROG SPATHA: SYN_DROPPED event - some input events have been lost.
[   642.923] (II) event8  - ASUS ROG SPATHA: SYN_DROPPED event - some input events have been lost.
[   642.923] (II) event8  - ASUS ROG SPATHA: WARNING: log rate limit exceeded (5 msgs per 30s). Discarding future messages.

That basically happens every time I move my mouse between monitors.

Full log here: It's kinda massive. https://pastebin.com/25Qt8ksj

Last edited by realitaetsverlust (2022-12-17 17:19:46)

seth · 2022-12-17 21:24:52

Looks like the output connected to DP-2 ("SAM") is flaky, how does the system behave if you detach it?

realitaetsverlust · 2022-12-17 23:00:52

Yep, that was it. The lags are completely gone now and I can open and close windows without much trouble. However, it still feels really sluggish. Even "simple" tasks like writing this text are not very nice.

Something that's also notworthy is that I'm running glxgears and it looks laggy and not very smooth, but in the console, it displays a constant 3800 - 4000 FPS.

Also, I can barely use any of the applications that I used to be able to use. Most games won't run and those that do run with a godawful performance. Even stuff like rimworld, which has barely any requirements, will run at like 15 - 20 FPS. Even after reinstalling the xf86-video-amdgpu driver, the performance is really really really bad.

Here, another Xorg log, I hope it helps: https://pastebin.com/QpxddkCw

Sorry that I'm bothering with all these problems but I'm kinda at a loss when it comes to these low level issues.

At this point, I'm wondering if a fresh install of the OS might be able to fix these issues?

Last edited by realitaetsverlust (2022-12-17 23:04:35)

seth · 2022-12-18 08:45:06

There's more going on - at least now the GSM output bounces (but we might have just missed that in the previous log) and there's

[     5.295] (II) modeset(0): Not using default mode "3840x2160" (bad mode clock/interlace/doublescan)
[     5.295] (II) modeset(0): Not using default mode "2560x1440" (bad mode clock/interlace/doublescan)

Then

I'm running glxgears and it looks laggy and not very smooth, but in the console, it displays a constant 3800 - 4000 FPS.

1. what window manager/compositor/desktop session is this?
2. what's the output of "xrandr -q"

realitaetsverlust · 2022-12-18 11:47:24

seth wrote:

There's more going on - at least now the GSM output bounces (but we might have just missed that in the previous log) and there's
[     5.295] (II) modeset(0): Not using default mode "3840x2160" (bad mode clock/interlace/doublescan)
[     5.295] (II) modeset(0): Not using default mode "2560x1440" (bad mode clock/interlace/doublescan)
Then
I'm running glxgears and it looks laggy and not very smooth, but in the console, it displays a constant 3800 - 4000 FPS.
1. what window manager/compositor/desktop session is this?
2. what's the output of "xrandr -q"

1. I'm using KDE with the "default" setup. Meaning, I just installed the plasma group and have not done anything to the setup apart from adding a few widgets to the taskbar.

2.

$ xrandr -q
Screen 0: minimum 320 x 200, current 3840 x 2160, maximum 16384 x 16384
DP-1 connected primary 3840x2160+0+0 (normal left inverted right x axis y axis) 600mm x 340mm
   3840x2160     60.00*+  50.01    48.01    59.97    30.00
   3200x1800     59.96    59.94
   2880x1620     59.96    59.97
   2560x1600     59.99    59.97
   2560x1440     59.99    59.96    59.95
   2048x1536     60.00
   1920x1440     60.00
   1856x1392     60.01
   1792x1344     60.01
   2048x1152     59.99    59.98    59.90    59.91
   1920x1200     60.00    59.88    59.95
   1920x1080     60.01    59.97    59.96    60.00    59.94    59.93
   1600x1200     60.00    60.00
   1680x1050     60.00    59.95    59.88
   1400x1050     59.98
   1600x900      59.99    59.94    59.95    60.00    59.82
   1280x1024     60.02
   1440x900      60.00
   1400x900      59.96    59.88
   1280x960      60.00
   1440x810      60.00    59.97
   1368x768      59.88    59.85
   1280x800      59.99    59.97    59.81    59.91
   1152x864      59.97
   1280x720      60.00    59.99    59.86    60.00    59.94    59.74
   1024x768      60.04    60.00
   960x720       60.00
   928x696       60.05
   896x672       60.01
   1024x576      59.95    59.96    59.90    59.82
   960x600       59.93    60.00
   960x540       59.96    59.99    59.63    59.82
   800x600       60.00    60.32    56.25
   840x525       60.01    59.88
   864x486       59.92    59.57
   700x525       59.98
   800x450       59.95    59.82
   720x480       60.00    59.94
   640x512       60.02
   700x450       59.96    59.88
   640x480       60.00    60.00    59.94
   720x405       59.51    58.99
   684x384       59.88    59.85
   640x400       59.88    59.98
   640x360       59.86    59.83    59.84    59.32
   512x384       60.00
   512x288       60.00    59.92
   480x270       59.63    59.82
   400x300       60.32    56.34
   432x243       59.92    59.57
   320x240       60.05
   360x202       59.51    59.13
   320x180       59.84    59.32
DP-2 disconnected (normal left inverted right x axis y axis)
DP-3 disconnected (normal left inverted right x axis y axis)
HDMI-1 disconnected (normal left inverted right x axis y axis)

Last edited by realitaetsverlust (2022-12-18 11:50:46)

seth · 2022-12-18 16:21:30

I'm using KDE with the "default" setup.

Try an openbox session (not KDE w/ openbox as WM, but just an openbox session, an xterm and glxgears to keeps things as simple as possible)

If that doesn't exhibit the problem, try to
a) suspend the KWin compositor (SHIFT+alt+F12)
b) disable the kscreen daemon in "kcmshell5 kded"

realitaetsverlust · 2022-12-18 18:13:48

Installed openbox, added "exec openbox-session" into my .xinitrc and launched it, however, I had similar issues in openbox as I have in KDE. So not really anything changes.

I still tried to suspend the compositor and disable the daemon, but nothing changed here either.

seth · 2022-12-18 20:51:00

https://wiki.archlinux.org/title/Intel_ … on_(VSYNC)
(ignore that this is the intel wiki page, dri is from mesa)

realitaetsverlust · 2022-12-18 21:29:45

I added that snippet to the ~/.drirc but nothing changed.

RecursiveG · 2022-12-19 03:23:03

Can you try

glxinfo | grep 'OpenGL renderer'

and see if it says "llvmpipe"? If so, your rendering is not hardware accelerated. Also shown on my side:

journalctl -ab | grep -i gfx

says

LLVM doesn't support gfx1100, bailing out...

Looks like we need to wait for LLVM 15 to get in the repo.

realitaetsverlust · 2022-12-19 08:45:40

RecursiveG wrote:

Can you try
glxinfo | grep 'OpenGL renderer'
and see if it says "llvmpipe"?

It does indeed:

$ glxinfo | grep 'OpenGL renderer'
OpenGL renderer string: llvmpipe (LLVM 14.0.6, 256 bits)

I don't see that string you mentioned about "bailing out" tho:

$ journalctl -ab | grep -i gfx
Dec 19 09:42:50 exodus kernel: [drm] add ip block number 6 <gfx_v11_0>
Dec 19 09:42:50 exodus kernel: amdgpu 0000:2f:00.0: amdgpu: ring gfx_0.0.0 uses VM inv eng 0 on hub 0
Dec 19 09:42:50 exodus kernel: [drm] ring gfx_32768.1.1 was added
Dec 19 09:42:50 exodus kernel: [drm] ring gfx_32768.1.1 test pass
Dec 19 09:42:50 exodus kernel: [drm] ring gfx_32768.1.1 ib test pass

HCF · 2022-12-20 06:03:59

I believe you'll need to install a sufficiently new version of mesa/llvm/linux-firmware. If it's any one of them but not all, you'll keep running into these issues.

According to a post on /r/archlinux, this combination should work:

# pacman -Sl | grep mesa-git | grep installed
mesa-git lib32-llvm-libs-git 16.0.0_r446039.10539ec2cf69-1 [installed: 16.0.0_r444736.8a900f2438b4-1]
mesa-git lib32-mesa-git 1:23.0.0_devel.164432.e66df0d3620-1 [installed]
mesa-git lib32-vulkan-radeon-git 1:23.0.0_devel.164432.e66df0d3620-1 [installed]
mesa-git llvm-libs-git 16.0.0_r446039.10539ec2cf69-1 [installed: 16.0.0_r444733.6a35815c73ec-1]
mesa-git mesa-git 1:23.0.0_devel.164432.e66df0d3620-1 [installed]
mesa-git vulkan-radeon-git 1:23.0.0_devel.164432.e66df0d3620-1 [installed]
# pacman -Qs linux-firmware                  
local/linux-firmware-git 20221216.52261d0-1
    Firmware files for Linux

Note that llvm needs to be at least v15 by the looks of it, and you have v14.

Let me know how you go, my 7900 is on its way and I'll be going through the same adventure soon enough

Last edited by HCF (2022-12-20 06:05:35)

johndoe1337 · 2022-12-20 14:21:56

Just for the reference: I got my 7900xtx running using linux-firmware from testing, mesa-git+llvm-git (and other support libs) from the mesa-git unofficial repo and finally setting "SWcursor" in my xorg.conf to fix the mouse pointer issue.
Tested a few games: CS Go, Cyberpunk, Baldurs Gate 3. Everything looks good so far.

Last edited by johndoe1337 (2022-12-20 14:25:16)

realitaetsverlust · 2022-12-20 16:54:08

HCF wrote:

I believe you'll need to install a sufficiently new version of mesa/llvm/linux-firmware. If it's any one of them but not all, you'll keep running into these issues.
According to a post on /r/archlinux, this combination should work:
# pacman -Sl | grep mesa-git | grep installed
mesa-git lib32-llvm-libs-git 16.0.0_r446039.10539ec2cf69-1 [installed: 16.0.0_r444736.8a900f2438b4-1]
mesa-git lib32-mesa-git 1:23.0.0_devel.164432.e66df0d3620-1 [installed]
mesa-git lib32-vulkan-radeon-git 1:23.0.0_devel.164432.e66df0d3620-1 [installed]
mesa-git llvm-libs-git 16.0.0_r446039.10539ec2cf69-1 [installed: 16.0.0_r444733.6a35815c73ec-1]
mesa-git mesa-git 1:23.0.0_devel.164432.e66df0d3620-1 [installed]
mesa-git vulkan-radeon-git 1:23.0.0_devel.164432.e66df0d3620-1 [installed]
# pacman -Qs linux-firmware                  
local/linux-firmware-git 20221216.52261d0-1
    Firmware files for Linux
Note that llvm needs to be at least v15 by the looks of it, and you have v14.
Let me know how you go, my 7900 is on its way and I'll be going through the same adventure soon enough

I'm not quite sure how that is supposed to work. mesa-git requires llvm on version 14.0.6, so it will ask to remove llvm-libs-git from my system as it's a higher version and in conflict.

$ makepkg -sirc
==> Making package: mesa-git 23.0.0_devel.164561.aace38c2d83.5269a95f00c4d6964d487d9dbd94f62b-1 (Tue 20 Dec 2022 05:54:55 PM CET)
==> Checking runtime dependencies...
==> Installing missing dependencies...
resolving dependencies...
looking for conflicting packages...
:: llvm-libs and llvm-libs-git are in conflict. Remove llvm-libs-git? [y/N]
error: unresolvable package conflicts detected
error: failed to prepare transaction (conflicting dependencies)
:: llvm-libs and llvm-libs-git are in conflict
==> ERROR: 'pacman' failed to install missing dependencies.
==> Missing dependencies:
  -> llvm-libs=14.0.6
==> Checking buildtime dependencies...
==> Installing missing dependencies...
resolving dependencies...
looking for conflicting packages...
:: llvm and llvm-git are in conflict. Remove llvm-git? [y/N]
error: unresolvable package conflicts detected
error: failed to prepare transaction (conflicting dependencies)
:: llvm and llvm-git are in conflict
==> ERROR: 'pacman' failed to install missing dependencies.
==> Missing dependencies:
  -> python-mako
  -> wayland-protocols
  -> meson
  -> ninja
  -> directx-headers
  -> llvm=14.0.6
  -> clang=14.0.6
==> ERROR: Could not resolve all dependencies.

How can I still install mesa-git after llvm-libs-git? I'm pretty sure I fucked my system beyond recognition at this point anyways so even the hackiest solutions are welcome.

Last edited by realitaetsverlust (2022-12-20 16:55:39)

walmartshopper · 2022-12-20 19:55:02

johndoe1337 wrote:

Just for the reference: I got my 7900xtx running using linux-firmware from testing, mesa-git+llvm-git (and other support libs) from the mesa-git unofficial repo and finally setting "SWcursor" in my xorg.conf to fix the mouse pointer issue.
Tested a few games: CS Go, Cyberpunk, Baldurs Gate 3. Everything looks good so far.

Same here, I installed linux-firmware-git from AUR plus switched everything over to mesa-git packages. I also had the missing cursor with xorg, but i switched to wayland and it works there (besides being black which is a separate issue). So far games and everything else seems to work fine. The only thing missing so far seems to be the overclocking controls. On windows I was able to push the core up around 3ghz and memory around 2700 with an undervolt of -80mv. amdgpu-clocks only allows me to set the power limit, but even then it doesn't seem to actually change it.

Arch Linux

#1 2022-12-17 10:08:51

[SOLVED] PC won't boot if slotting in new GPU

#2 2022-12-17 11:45:30

Re: [SOLVED] PC won't boot if slotting in new GPU

#3 2022-12-17 12:15:47

Re: [SOLVED] PC won't boot if slotting in new GPU

#4 2022-12-17 12:20:59

Re: [SOLVED] PC won't boot if slotting in new GPU

#5 2022-12-17 12:29:48

Re: [SOLVED] PC won't boot if slotting in new GPU

#6 2022-12-17 14:30:50

Re: [SOLVED] PC won't boot if slotting in new GPU

#7 2022-12-17 16:42:27

Re: [SOLVED] PC won't boot if slotting in new GPU

#8 2022-12-17 16:51:12

Re: [SOLVED] PC won't boot if slotting in new GPU

#9 2022-12-17 16:59:15

Re: [SOLVED] PC won't boot if slotting in new GPU

#10 2022-12-17 17:02:02

Re: [SOLVED] PC won't boot if slotting in new GPU

#11 2022-12-17 17:18:32

Re: [SOLVED] PC won't boot if slotting in new GPU

#12 2022-12-17 21:24:52

Re: [SOLVED] PC won't boot if slotting in new GPU

#13 2022-12-17 23:00:52

Re: [SOLVED] PC won't boot if slotting in new GPU

#14 2022-12-18 08:45:06

Re: [SOLVED] PC won't boot if slotting in new GPU

#15 2022-12-18 11:47:24

Re: [SOLVED] PC won't boot if slotting in new GPU

#16 2022-12-18 16:21:30

Re: [SOLVED] PC won't boot if slotting in new GPU

#17 2022-12-18 18:13:48

Re: [SOLVED] PC won't boot if slotting in new GPU

#18 2022-12-18 20:51:00

Re: [SOLVED] PC won't boot if slotting in new GPU

#19 2022-12-18 21:29:45

Re: [SOLVED] PC won't boot if slotting in new GPU

#20 2022-12-19 03:23:03

Re: [SOLVED] PC won't boot if slotting in new GPU

#21 2022-12-19 08:45:40

Re: [SOLVED] PC won't boot if slotting in new GPU

#22 2022-12-20 06:03:59

Re: [SOLVED] PC won't boot if slotting in new GPU

#23 2022-12-20 14:21:56

Re: [SOLVED] PC won't boot if slotting in new GPU

#24 2022-12-20 16:54:08

Re: [SOLVED] PC won't boot if slotting in new GPU

#25 2022-12-20 19:55:02

Re: [SOLVED] PC won't boot if slotting in new GPU

Board footer