AMD 7900 XT not working properly after kernel and mesa update

[Cykyrios]

Hi, I just got myself an AMD 7900 XT and followed this guide by SMG to update the kernel and drivers, however this doesn't seem to solve my issues. Specifically, using kisak's PPA seems to leave me with LLVM13 and Mesa 22; on the other hand, Oibaf's PPA does give me access to LLVM15 and Mesa 23, but then I cannot install Steam (held packages for i386, which only happens with this PPA), so I can't really test the GPU in games (as a side note, a Unigine benchmark leads me to believe things are working fine).

Here's a summary of what I did (this time at least, I've tried multiple times, with kisak's PPA, Oibaf's PPA, tried and failed to compile myself, also had a go on Manjaro, where the driver seemed to work, but the GPU still didn't do anything in game (probably software rendering)):

Code: Select all

timeshift back to Mint 21.1 fresh install
sudo apt update
sudo apt upgrade
sudo apt install linux-oem-22.04c
sudo add-apt-repository ppa:oibaf/graphics-drivers
sudo apt update
sudo apt upgrade
cd Downloads/linux-firmware-20230117/
sudo cp -R * /lib/firmware/
sudo update-initramfs -u -k all
sudo nano /usr/share/X11/xorg.conf.d/10-amdgpu.conf -> add Option "SWcursor" "true"
reboot

After this, inxi -Fxxxrz outputs the following:

Code: Select all

System:
  Kernel: 6.1.0-1004-oem x86_64 bits: 64 compiler: N/A
    Desktop: Cinnamon 5.6.7 tk: GTK 3.24.33 wm: muffin vt: 7 dm: LightDM 1.30.0
    Distro: Linux Mint 21.1 Vera base: Ubuntu 22.04 jammy
[...]
CPU:
  Info: 12-core model: AMD Ryzen 9 7900X bits: 64 type: MT MCP smt: enabled
    arch: Zen 3 rev: 2 cache: L1: 768 KiB L2: 12 MiB L3: 64 MiB
[...]
Graphics:
  Device-1: AMD vendor: Sapphire driver: amdgpu v: kernel pcie:
    speed: 16 GT/s lanes: 16 ports: active: DP-1 empty: DP-2,HDMI-A-1,HDMI-A-2
    bus-ID: 03:00.0 chip-ID: 1002:744c class-ID: 0300
  Device-2: AMD driver: amdgpu v: kernel pcie: speed: 16 GT/s lanes: 16
    ports: active: none empty: DP-3,HDMI-A-3 bus-ID: 13:00.0 chip-ID: 1002:164e
    class-ID: 0300
  Display: x11 server: X.Org v: 1.21.1.3 driver: X: loaded: amdgpu,ati
    unloaded: fbdev,modesetting,radeon,vesa gpu: amdgpu display-ID: :0

And here is glx info | grep OpenGL:

Code: Select all

OpenGL vendor string: AMD
OpenGL renderer string: AMD Radeon RX 7900 XT (gfx1100, LLVM 15.0.5, DRM 3.49, 6.1.0-1004-oem)
OpenGL core profile version string: 4.6 (Core Profile) Mesa 23.1.0-devel (git-0594b3c 2023-01-23 jammy-oibaf-ppa)
OpenGL core profile shading language version string: 4.60
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile
OpenGL core profile extensions:
OpenGL version string: 4.6 (Compatibility Profile) Mesa 23.1.0-devel (git-0594b3c 2023-01-23 jammy-oibaf-ppa)
OpenGL shading language version string: 4.60
OpenGL context flags: (none)
OpenGL profile mask: compatibility profile
OpenGL extensions:
OpenGL ES profile version string: OpenGL ES 3.2 Mesa 23.1.0-devel (git-0594b3c 2023-01-23 jammy-oibaf-ppa)
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20
OpenGL ES profile extensions:

Then I try to install Steam with sudo apt install steam-installer, and get the following:

Code: Select all

The following packages have unmet dependencies:
 libglx0:i386 : Depends: libglx-mesa0:i386 but it is not going to be installed
 steam:i386 : Depends: libgl1-mesa-dri:i386 (>= 17.3) but it is not going to be installed
              Recommends: libegl1:i386 but it is not installable
              Recommends: libgbm1:i386 but it is not going to be installed
              Recommends: libsdl2-2.0-0:i386 but it is not installable
              Recommends: mesa-vulkan-drivers:i386 but it is not going to be installed
E: Unable to correct problems, you have held broken packages.

When I'm not using oibaf's PPA (and therefore I am on Mesa 22.x), Steam installs with no problem at all. I can install the Flatpak version, which "works", except games don't seem to use the GPU (I have only tried Portal, but Elden Ring refuses to start at all (it worked on my previous machine)).
Also, using nvtop to try and monitor the GPU tells me "No GPU to monitor".

Apologies if this thread belong in Gaming instead, but since the GPU quite clearly isn't working properly, I decided to put this here.
Any help would be greatly appreciated! And by the way, a big thank you already to the community, as I've been lurking here over the past few years whenever problems arise.

[Rua]

I'm running into this as well. The kisak PPA doesn't seem to have i386 versions of the packages?

Code: Select all

rua@rua-desktop ~ $ apt show -a mesa-vulkan-drivers:i386
Package: mesa-vulkan-drivers:i386
Version: 22.0.5-0ubuntu0.3
[...]

Package: mesa-vulkan-drivers:i386
Version: 22.0.1-1ubuntu2
[...]

rua@rua-desktop ~ $ apt show -a mesa-vulkan-drivers
Package: mesa-vulkan-drivers
Version: 22.3.3~kisak1~j
[...]

Package: mesa-vulkan-drivers
Version: 22.0.5-0ubuntu0.3
[...]

Package: mesa-vulkan-drivers
Version: 22.0.1-1ubuntu2
[...]

[SMG]

Apologies if this thread belong in Gaming instead, but since the GPU quite clearly isn't working properly, I decided to put this here.

Welcome to the forum, Cykyrios.

Usually, if the operating system is seeing the GPU, but the game/software program is not recognizing it, then the issue is with the game/software. However, because this GPU is new it's hard to say at this point.

I do not game so I am unlikely to be able to help with specific issues in the game, but I want to make a couple of observations about how the operating system sees the GPUs and maybe they will help you in troubleshooting this issue.

You did not supply your complete inxi output so your motherboard is unknown (to us) at this point. I mention the motherboard because it (and its firmware) usually decide which GPU(s) are seen by the operating system. Some mobos give the option to only use onboard graphics or only use the discrete GPU (one or the other, but not both simultaneously). Other mobos permit both to be used and there is an option to set priority of which is the primary in the BIOS/UEFI.

It appears yours is currently set to use both GPUs. That is the only way of which I know that both would show in inxi.

Graphics:
Device-1: AMD vendor: Sapphire driver: amdgpu v: kernel pcie:
speed: 16 GT/s lanes: 16 ports: active: DP-1 empty: DP-2,HDMI-A-1,HDMI-A-2
bus-ID: 03:00.0 chip-ID: 1002:744c class-ID: 0300
Device-2: AMD driver: amdgpu v: kernel pcie: speed: 16 GT/s lanes: 16
ports: active: none empty: DP-3,HDMI-A-3 bus-ID: 13:00.0 chip-ID: 1002:164e
class-ID: 0300

In cases where that happens, it is likely the display drivers and renderers for both GPUs are loaded. The first one which loads shows in the inxi output and usually that is the one showing when you run glxinfo commands. However, if you check the Xorg log, you will likely find both are loaded. The renderers for each of your GPUs is different. The GFX1100 is the renderer for the 7900 XT and I believe the GFX1036 is the renderer for your Ryzen 7900X, so you should be able to see when each loads in the Xorg log. (Let us know if you want/need help understanding the Xorg log output.)

So if both renderers are loaded, then it is possible for the game/software you run to use the onboard rather than the discrete. That is where the game/software program code comes into play with regards to what it uses.

When you install a flatpak, it loads all the runtime dependencies it needs to work properly. You can run flatpak list --app to see what is installed. I would expect that output to include mesa parts as well as possibly other graphics-related parts. Perhaps from that list you can tell what is being used when you use Steam flatpak to game.

sudo nano /usr/share/X11/xorg.conf.d/10-amdgpu.conf -> add Option "SWcursor" "true"

To me (my personal opinion which could be wrong), the fact this needs to be done seems to indicate the amdgpu driver still needs some work for it to work properly with this GPU on X Server. I have no idea if this might be a factor with regards to ability to game.

Then I try to install Steam with sudo apt install steam-installer, and get the following:

Code: Select all

The following packages have unmet dependencies:
 libglx0:i386 : Depends: libglx-mesa0:i386 but it is not going to be installed
 steam:i386 : Depends: libgl1-mesa-dri:i386 (>= 17.3) but it is not going to be installed
              Recommends: libegl1:i386 but it is not installable
              Recommends: libgbm1:i386 but it is not going to be installed
              Recommends: libsdl2-2.0-0:i386 but it is not installable
              Recommends: mesa-vulkan-drivers:i386 but it is not going to be installed
E: Unable to correct problems, you have held broken packages.

When I'm not using oibaf's PPA (and therefore I am on Mesa 22.x), Steam installs with no problem at all.

You are able to get Steam to install when using kisak-ppa? It's only when going to Mesa 23 there are problems with the i386 packages?

Also, using nvtop to try and monitor the GPU tells me "No GPU to monitor".

I did a search and here is someone with an Nvidia 3070 getting that same message 4 months ago nvtop is saying no gpu to monitor.. I am not familiar with how nvtop works to know what the issue might be.

When checking for problems with GPUs, I usually have people run the following:

Code: Select all

journalctl -b | grep -i "drm\|amdgpu\|03:00.0\|13:00.0"

That provides information on your current boot cycle. Bus ID 3 is your 7900XT while bus ID 13 is your onboard GPU.

If you have any questions about what I've written or want help reviewing logs, just ask.

[roblm]

Then I try to install Steam with sudo apt install steam-installer, and get the following:

The following packages have unmet dependencies:
libglx0:i386 : Depends: libglx-mesa0:i386 but it is not going to be installed
steam:i386 : Depends: libgl1-mesa-dri:i386 (>= 17.3) but it is not going to be installed
Recommends: libegl1:i386 but it is not installable
Recommends: libgbm1:i386 but it is not going to be installed
Recommends: libsdl2-2.0-0:i386 but it is not installable
Recommends: mesa-vulkan-drivers:i386 but it is not going to be installed
E: Unable to correct problems, you have held broken packages.

That's strange because the mesa update from the oibaf PPA lists these packages will be affected, which includes the two packages highlighted above:

This update affects the following installed packages:
• libegl-mesa0
• libegl-mesa0:i386
• libgbm1
• libgbm1:i386
• libgl1-mesa-dri
• libgl1-mesa-dri:i386
• libglapi-mesa
• libglapi-mesa:i386
• libglx-mesa0
• libglx-mesa0:i386
• libxatracker2
• mesa-va-drivers
• mesa-vdpau-drivers
• mesa-vdpau-drivers:i386
• mesa-vulkan-drivers
• mesa-vulkan-drivers:i386

What is the output of this command: apt policy libglx-mesa0:i386 libgl1-mesa-dri:i386

[Cykyrios]

Thank you very much for your detailed answer, SMG.

I did skip a bit of the inxi -Fxxxrz as I didn't really think it was relevant, but the motherboard part is a good point, so here's the full output:

Code: Select all

System:
  Kernel: 6.1.0-1004-oem x86_64 bits: 64 compiler: N/A
    Desktop: Cinnamon 5.6.7 tk: GTK 3.24.33 wm: muffin vt: 7 dm: LightDM 1.30.0
    Distro: Linux Mint 21.1 Vera base: Ubuntu 22.04 jammy
Machine:
  Type: Desktop System: ASUS product: N/A v: N/A serial: <superuser required>
  Mobo: ASUSTeK model: TUF GAMING X670E-PLUS v: Rev 1.xx
    serial: <superuser required> UEFI: American Megatrends v: 0613
    date: 09/22/2022
CPU:
  Info: 12-core model: AMD Ryzen 9 7900X bits: 64 type: MT MCP smt: enabled
    arch: Zen 3 rev: 2 cache: L1: 768 KiB L2: 12 MiB L3: 64 MiB
  Speed (MHz): avg: 3515 high: 5625 min/max: 3000/5733 boost: enabled
    cores: 1: 3735 2: 3616 3: 3000 4: 3000 5: 3000 6: 3000 7: 2807 8: 5291
    9: 2812 10: 2818 11: 5062 12: 3000 13: 4700 14: 3000 15: 4700 16: 4700
    17: 3000 18: 2870 19: 2824 20: 5625 21: 2808 22: 3000 23: 3000 24: 3000
    bogomips: 225185
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Graphics:
  Device-1: AMD vendor: Sapphire driver: amdgpu v: kernel pcie:
    speed: 16 GT/s lanes: 16 ports: active: DP-1,DP-2 empty: HDMI-A-1,HDMI-A-2
    bus-ID: 03:00.0 chip-ID: 1002:744c class-ID: 0300
  Device-2: AMD driver: amdgpu v: kernel pcie: speed: 16 GT/s lanes: 16
    ports: active: none empty: DP-3,HDMI-A-3 bus-ID: 13:00.0 chip-ID: 1002:164e
    class-ID: 0300
  Display: x11 server: X.Org v: 1.21.1.3 driver: X: loaded: amdgpu,ati
    unloaded: fbdev,modesetting,radeon,vesa gpu: amdgpu display-ID: :0
    screens: 1
  Screen-1: 0 s-res: 3840x1080 s-dpi: 96 s-size: 1016x286mm (40.0x11.3")
    s-diag: 1055mm (41.6")
  Monitor-1: DisplayPort-0 mapped: DP-1 pos: primary,right
    model: Acer RG240Y serial: <filter> res: 1920x1080 dpi: 93
    size: 527x296mm (20.7x11.7") diag: 604mm (23.8") modes: max: 1920x1080
    min: 720x400
  Monitor-2: DisplayPort-1 mapped: DP-2 pos: primary,left
    model: Acer RG240Y serial: <filter> res: 1920x1080 hz: 60 dpi: 93
    size: 527x296mm (20.7x11.7") diag: 604mm (23.8") modes: max: 1920x1080
    min: 720x400
  OpenGL: renderer: AMD Radeon RX 7900 XT (gfx1100 LLVM 15.0.5 DRM 3.49
  6.1.0-1004-oem)
    v: 4.6 Mesa 23.1.0-devel (git-159edf7 2023-01-24 jammy-oibaf-ppa)
    direct render: Yes
Audio:
  Device-1: AMD driver: snd_hda_intel v: kernel pcie: speed: 16 GT/s
    lanes: 16 bus-ID: 03:00.1 chip-ID: 1002:ab30 class-ID: 0403
  Device-2: AMD driver: snd_hda_intel v: kernel pcie: speed: 16 GT/s
    lanes: 16 bus-ID: 13:00.1 chip-ID: 1002:1640 class-ID: 0403
  Device-3: AMD Family 17h HD Audio vendor: ASUSTeK driver: snd_hda_intel
    v: kernel pcie: speed: 16 GT/s lanes: 16 bus-ID: 13:00.6 chip-ID: 1022:15e3
    class-ID: 0403
  Device-4: Logitech Yeti X type: USB
    driver: hid-generic,snd-usb-audio,usbhid bus-ID: 1-2:2 chip-ID: 046d:0aaf
    class-ID: 0300 serial: <filter>
  Sound Server-1: ALSA v: k6.1.0-1004-oem running: yes
  Sound Server-2: PulseAudio v: 15.99.1 running: yes
  Sound Server-3: PipeWire v: 0.3.48 running: yes
Network:
  Device-1: Realtek RTL8125 2.5GbE vendor: ASUSTeK driver: r8169 v: kernel
    pcie: speed: 5 GT/s lanes: 1 port: e000 bus-ID: 0b:00.0 chip-ID: 10ec:8125
    class-ID: 0200
  IF: eno1 state: up speed: 2500 Mbps duplex: full mac: <filter>
Drives:
  Local Storage: total: 2.73 TiB used: 87.17 GiB (3.1%)
  ID-1: /dev/nvme0n1 vendor: Kingston model: SFYRS1000G size: 931.51 GiB
    speed: 63.2 Gb/s lanes: 4 type: SSD serial: <filter> rev: EIFK31.6
    temp: 11.8 C scheme: GPT
  ID-2: /dev/nvme1n1 vendor: Crucial model: CT2000P3SSD8 size: 1.82 TiB
    speed: 31.6 Gb/s lanes: 4 type: SSD serial: <filter> rev: P9CR30A
    temp: 19.9 C scheme: GPT
Partition:
  ID-1: / size: 81.95 GiB used: 21.57 GiB (26.3%) fs: ext4
    dev: /dev/nvme0n1p2
  ID-2: /boot/efi size: 974.1 MiB used: 5.2 MiB (0.5%) fs: vfat
    dev: /dev/nvme0n1p1
  ID-3: /home size: 817.36 GiB used: 65.6 GiB (8.0%) fs: ext4
    dev: /dev/nvme0n1p4
Swap:
  ID-1: swap-1 type: partition size: 15.26 GiB used: 0 KiB (0.0%)
    priority: -2 dev: /dev/nvme0n1p3
Sensors:
  System Temperatures: cpu: N/A mobo: N/A
  Fan Speeds (RPM): N/A
  GPU: device: amdgpu temp: 27.0 C mem: 40.0 C fan: 0 watts: 23.00
    device: amdgpu temp: 29.0 C
Repos:
  Packages: 2593 apt: 2579 flatpak: 14
  No active apt repos in: /etc/apt/sources.list
  Active apt repos in: /etc/apt/sources.list.d/brave-browser-release.list
    1: deb [signed-by=/usr/share/keyrings/brave-browser-archive-keyring.gpg] https://brave-browser-apt-release.s3.brave.com/ stable main
  Active apt repos in: /etc/apt/sources.list.d/official-package-repositories.list
    1: deb http://packages.linuxmint.com vera main upstream import backport
    2: deb http://archive.ubuntu.com/ubuntu jammy main restricted universe multiverse
    3: deb http://archive.ubuntu.com/ubuntu jammy-updates main restricted universe multiverse
    4: deb http://archive.ubuntu.com/ubuntu jammy-backports main restricted universe multiverse
    5: deb http://security.ubuntu.com/ubuntu/ jammy-security main restricted universe multiverse
  Active apt repos in: /etc/apt/sources.list.d/oibaf-graphics-drivers-jammy.list
    1: deb [arch=amd64 signed-by=/etc/apt/keyrings/oibaf-graphics-drivers-jammy.gpg] https://ppa.launchpadcontent.net/oibaf/graphics-drivers/ubuntu jammy main
Info:
  Processes: 499 Uptime: 4m wakeups: 0 Memory: 30.5 GiB
  used: 3.51 GiB (11.5%) Init: systemd v: 249 runlevel: 5 Compilers:
  gcc: 11.3.0 alt: 11 Shell: Bash v: 5.1.16 running-in: gnome-terminal
  inxi: 3.3.13

I just had a look at the ASUS website, and I should be able to upgrade the firmware from 0613 to 0821.
In the BIOS settings, priority is given to the 7900 XT instead of the CPU's integrated graphics.

I also had a look at the Xorg log, here's what I believe is the relevant part:

Code: Select all

[     8.186] (II) systemd-logind: logind integration requires -keeptty and -keeptty was not provided, disabling logind integration
[     8.186] (II) xfree86: Adding drm device (/dev/dri/card0)
[     8.186] (II) Platform probe for /sys/devices/pci0000:00/0000:00:01.1/0000:01:00.0/0000:02:00.0/0000:03:00.0/drm/card0
[     8.213] (II) xfree86: Adding drm device (/dev/dri/card1)
[     8.213] (II) Platform probe for /sys/devices/pci0000:00/0000:00:08.1/0000:13:00.0/drm/card1
[     8.216] (--) PCI:*(3@0:0:0) 1002:744c:1da2:471e rev 204, Mem @ 0xf000000000/34359738368, 0xf800000000/268435456, 0xfcb00000/1048576, I/O @ 0x0000f000/256, BIOS @ 0x????????/131072
[     8.216] (--) PCI: (19@0:0:0) 1002:164e:1002:164e rev 194, Mem @ 0xf820000000/268435456, 0xf830000000/2097152, 0xfca00000/524288, I/O @ 0x0000d000/256
[     8.216] (II) LoadModule: "glx"
[     8.216] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[     8.218] (II) Module glx: vendor="X.Org Foundation"
[     8.218] 	compiled for 1.21.1.3, module version = 1.0.0
[     8.218] 	ABI class: X.Org Server Extension, version 10.0
[     8.218] (II) Applying OutputClass "AMDgpu" to /dev/dri/card0
[     8.218] 	loading driver: amdgpu
[     8.218] (II) Applying OutputClass "AMDgpu" to /dev/dri/card1
[     8.218] 	loading driver: amdgpu
[     8.218] (==) Matched amdgpu as autoconfigured driver 0
[     8.218] (==) Matched ati as autoconfigured driver 1
[     8.218] (==) Matched modesetting as autoconfigured driver 2
[     8.218] (==) Matched fbdev as autoconfigured driver 3
[     8.218] (==) Matched vesa as autoconfigured driver 4
[     8.218] (==) Assigned the driver to the xf86ConfigLayout
[     8.218] (II) LoadModule: "amdgpu"
[     8.218] (II) Loading /usr/lib/xorg/modules/drivers/amdgpu_drv.so
[     8.219] (II) Module amdgpu: vendor="X.Org Foundation"
[     8.219] 	compiled for 1.21.1.3, module version = 22.0.0
[     8.219] 	Module class: X.Org Video Driver
[     8.219] 	ABI class: X.Org Video Driver, version 25.2
[     8.219] (II) LoadModule: "ati"
[     8.219] (II) Loading /usr/lib/xorg/modules/drivers/ati_drv.so
[     8.219] (II) Module ati: vendor="X.Org Foundation"
[     8.219] 	compiled for 1.21.1.3, module version = 19.1.0
[     8.219] 	Module class: X.Org Video Driver
[     8.219] 	ABI class: X.Org Video Driver, version 25.2
[     8.298] (II) LoadModule: "radeon"
[     8.298] (II) Loading /usr/lib/xorg/modules/drivers/radeon_drv.so
[     8.299] (II) Module radeon: vendor="X.Org Foundation"
[     8.299] 	compiled for 1.21.1.3, module version = 19.1.0
[     8.299] 	Module class: X.Org Video Driver
[     8.299] 	ABI class: X.Org Video Driver, version 25.2
[     8.299] (II) LoadModule: "modesetting"
[     8.299] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so
[     8.299] (II) Module modesetting: vendor="X.Org Foundation"
[     8.299] 	compiled for 1.21.1.3, module version = 1.21.1
[     8.299] 	Module class: X.Org Video Driver
[     8.299] 	ABI class: X.Org Video Driver, version 25.2
[     8.299] (II) LoadModule: "fbdev"
[     8.299] (II) Loading /usr/lib/xorg/modules/drivers/fbdev_drv.so
[     8.299] (II) Module fbdev: vendor="X.Org Foundation"
[     8.299] 	compiled for 1.21.1.3, module version = 0.5.0
[     8.299] 	Module class: X.Org Video Driver
[     8.299] 	ABI class: X.Org Video Driver, version 25.2
[     8.299] (II) LoadModule: "vesa"
[     8.299] (II) Loading /usr/lib/xorg/modules/drivers/vesa_drv.so
[     8.299] (II) Module vesa: vendor="X.Org Foundation"
[     8.299] 	compiled for 1.21.1.3, module version = 2.5.0
[     8.299] 	Module class: X.Org Video Driver
[     8.299] 	ABI class: X.Org Video Driver, version 25.2
[     8.299] (II) AMDGPU: Driver for AMD Radeon:
	All GPUs supported by the amdgpu kernel driver
[     8.299] (II) RADEON: Driver for ATI/AMD Radeon chipsets:
[...]
[     8.300] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
[     8.300] (II) FBDEV: driver for framebuffer: fbdev
[     8.300] (II) VESA: driver for VESA chipsets: vesa
[     8.317] (WW) Falling back to old probe method for modesetting
[     8.317] (WW) Falling back to old probe method for fbdev
[     8.317] (II) Loading sub module "fbdevhw"
[     8.317] (II) LoadModule: "fbdevhw"
[     8.317] (II) Loading /usr/lib/xorg/modules/libfbdevhw.so
[     8.318] (II) Module fbdevhw: vendor="X.Org Foundation"
[     8.318] 	compiled for 1.21.1.3, module version = 0.0.2
[     8.318] 	ABI class: X.Org Video Driver, version 25.2
[     8.320] (II) AMDGPU(0): Creating default Display subsection in Screen section
	"Default Screen Section" for depth/fbbpp 24/32
[     8.320] (==) AMDGPU(0): Depth 24, (--) framebuffer bpp 32
[     8.320] (II) AMDGPU(0): Pixel depth = 24 bits stored in 4 bytes (32 bpp pixmaps)
[     8.320] (==) AMDGPU(0): Default visual is TrueColor
[     8.320] (II) Applying OutputClass "AMDgpu" options to /dev/dri/card0
[     8.320] (**) AMDGPU(0): Option "SWcursor" "true"
[     8.320] (==) AMDGPU(0): RGB weight 888
[     8.320] (II) AMDGPU(0): Using 8 bits per RGB (8 bit DAC)
[     8.320] (--) AMDGPU(0): Chipset: "AMD Radeon RX 7900 XT" (ChipID = 0x744c)
[     8.320] (II) Loading sub module "fb"
[     8.320] (II) LoadModule: "fb"
[     8.320] (II) Module "fb" already built-in
[     8.320] (II) Loading sub module "dri2"
[     8.320] (II) LoadModule: "dri2"
[     8.320] (II) Module "dri2" already built-in
[     8.384] (II) Loading sub module "glamoregl"
[     8.384] (II) LoadModule: "glamoregl"
[     8.384] (II) Loading /usr/lib/xorg/modules/libglamoregl.so
[     8.385] (II) Module glamoregl: vendor="X.Org Foundation"
[     8.385] 	compiled for 1.21.1.3, module version = 1.0.1
[     8.385] 	ABI class: X.Org ANSI C Emulation, version 0.4
[     8.392] (II) AMDGPU(0): glamor X acceleration enabled on AMD Radeon RX 7900 XT (gfx1100, LLVM 15.0.5, DRM 3.49, 6.1.0-1004-oem)
[     8.392] (II) AMDGPU(0): glamor detected, initialising EGL layer.
[...]
[     8.431] (II) Module glamoregl: vendor="X.Org Foundation"
[     8.431] 	compiled for 1.21.1.3, module version = 1.0.1
[     8.431] 	ABI class: X.Org ANSI C Emulation, version 0.4
[     8.433] (II) AMDGPU(G0): glamor X acceleration enabled on AMD Radeon Graphics (gfx1036, LLVM 15.0.5, DRM 3.49, 6.1.0-1004-oem)
[     8.433] (II) AMDGPU(G0): glamor detected, initialising EGL layer.

As for journalctl -b | grep -i "drm\|amdgpu\|03:00.0\|13:00.0", here is the output:

Code: Select all

janv. 25 20:34:37 cyril-home kernel: pci 0000:03:00.0: [1002:744c] type 00 class 0x030000
janv. 25 20:34:37 cyril-home kernel: pci 0000:03:00.0: reg 0x10: [mem 0xf000000000-0xf7ffffffff 64bit pref]
janv. 25 20:34:37 cyril-home kernel: pci 0000:03:00.0: reg 0x18: [mem 0xf800000000-0xf80fffffff 64bit pref]
janv. 25 20:34:37 cyril-home kernel: pci 0000:03:00.0: reg 0x20: [io  0xf000-0xf0ff]
janv. 25 20:34:37 cyril-home kernel: pci 0000:03:00.0: reg 0x24: [mem 0xfcb00000-0xfcbfffff]
janv. 25 20:34:37 cyril-home kernel: pci 0000:03:00.0: reg 0x30: [mem 0xfcc00000-0xfcc1ffff pref]
janv. 25 20:34:37 cyril-home kernel: pci 0000:03:00.0: BAR 0: assigned to efifb
janv. 25 20:34:37 cyril-home kernel: pci 0000:03:00.0: PME# supported from D1 D2 D3hot D3cold
janv. 25 20:34:37 cyril-home kernel: pci 0000:13:00.0: [1002:164e] type 00 class 0x030000
janv. 25 20:34:37 cyril-home kernel: pci 0000:13:00.0: reg 0x10: [mem 0xf820000000-0xf82fffffff 64bit pref]
janv. 25 20:34:37 cyril-home kernel: pci 0000:13:00.0: reg 0x18: [mem 0xf830000000-0xf8301fffff 64bit pref]
janv. 25 20:34:37 cyril-home kernel: pci 0000:13:00.0: reg 0x20: [io  0xd000-0xd0ff]
janv. 25 20:34:37 cyril-home kernel: pci 0000:13:00.0: reg 0x24: [mem 0xfca00000-0xfca7ffff]
janv. 25 20:34:37 cyril-home kernel: pci 0000:13:00.0: enabling Extended Tags
janv. 25 20:34:37 cyril-home kernel: pci 0000:13:00.0: PME# supported from D1 D2 D3hot D3cold
janv. 25 20:34:37 cyril-home kernel: pci 0000:03:00.0: vgaarb: setting as boot VGA device
janv. 25 20:34:37 cyril-home kernel: pci 0000:03:00.0: vgaarb: bridge control possible
janv. 25 20:34:37 cyril-home kernel: pci 0000:03:00.0: vgaarb: VGA device added: decodes=io+mem,owns=none,locks=none
janv. 25 20:34:37 cyril-home kernel: pci 0000:13:00.0: vgaarb: bridge control possible
janv. 25 20:34:37 cyril-home kernel: pci 0000:13:00.0: vgaarb: VGA device added: decodes=io+mem,owns=none,locks=none
janv. 25 20:34:37 cyril-home kernel: pci 0000:03:00.1: D0 power state depends on 0000:03:00.0
janv. 25 20:34:37 cyril-home kernel: pci 0000:13:00.1: D0 power state depends on 0000:13:00.0
janv. 25 20:34:37 cyril-home kernel: pci 0000:03:00.0: Adding to iommu group 14
janv. 25 20:34:37 cyril-home kernel: pci 0000:13:00.0: Adding to iommu group 23
janv. 25 20:34:37 cyril-home kernel: ACPI: bus type drm_connector registered
janv. 25 20:34:37 cyril-home kernel: [drm] amdgpu kernel modesetting enabled.
janv. 25 20:34:37 cyril-home kernel: amdgpu: vga_switcheroo: detected switching method \_SB_.PCI0.GP17.VGA_.ATPX handle
janv. 25 20:34:37 cyril-home kernel: amdgpu: Ignoring ACPI CRAT on non-APU system
janv. 25 20:34:37 cyril-home kernel: amdgpu: Virtual CRAT table created for CPU
janv. 25 20:34:37 cyril-home kernel: amdgpu: Topology: Add CPU node
janv. 25 20:34:37 cyril-home kernel: amdgpu 0000:03:00.0: vgaarb: deactivate vga console
janv. 25 20:34:37 cyril-home kernel: amdgpu 0000:03:00.0: enabling device (0006 -> 0007)
janv. 25 20:34:37 cyril-home kernel: [drm] initializing kernel modesetting (IP DISCOVERY 0x1002:0x744C 0x1DA2:0x471E 0xCC).
janv. 25 20:34:37 cyril-home kernel: [drm] register mmio base: 0xFCB00000
janv. 25 20:34:37 cyril-home kernel: [drm] register mmio size: 1048576
janv. 25 20:34:37 cyril-home kernel: [drm] add ip block number 0 <soc21_common>
janv. 25 20:34:37 cyril-home kernel: [drm] add ip block number 1 <gmc_v11_0>
janv. 25 20:34:37 cyril-home kernel: [drm] add ip block number 2 <ih_v6_0>
janv. 25 20:34:37 cyril-home kernel: [drm] add ip block number 3 <psp>
janv. 25 20:34:37 cyril-home kernel: [drm] add ip block number 4 <smu>
janv. 25 20:34:37 cyril-home kernel: [drm] add ip block number 5 <dm>
janv. 25 20:34:37 cyril-home kernel: [drm] add ip block number 6 <gfx_v11_0>
janv. 25 20:34:37 cyril-home kernel: [drm] add ip block number 7 <sdma_v6_0>
janv. 25 20:34:37 cyril-home kernel: [drm] add ip block number 8 <vcn_v4_0>
janv. 25 20:34:37 cyril-home kernel: [drm] add ip block number 9 <jpeg_v4_0>
janv. 25 20:34:37 cyril-home kernel: [drm] add ip block number 10 <mes_v11_0>
janv. 25 20:34:37 cyril-home kernel: amdgpu 0000:03:00.0: amdgpu: Fetched VBIOS from VFCT
janv. 25 20:34:37 cyril-home kernel: amdgpu: ATOM BIOS: 113-D70401XT-P09
janv. 25 20:34:37 cyril-home kernel: [drm] VCN(0) encode/decode are enabled in VM mode
janv. 25 20:34:37 cyril-home kernel: [drm] VCN(1) encode/decode are enabled in VM mode
janv. 25 20:34:37 cyril-home kernel: amdgpu 0000:03:00.0: [drm:jpeg_v4_0_early_init [amdgpu]] JPEG decode is enabled in VM mode
janv. 25 20:34:37 cyril-home kernel: amdgpu 0000:03:00.0: amdgpu: Trusted Memory Zone (TMZ) feature not supported
janv. 25 20:34:37 cyril-home kernel: amdgpu 0000:03:00.0: amdgpu: MEM ECC is not presented.
janv. 25 20:34:37 cyril-home kernel: amdgpu 0000:03:00.0: amdgpu: SRAM ECC is not presented.
janv. 25 20:34:37 cyril-home kernel: [drm] vm size is 262144 GB, 4 levels, block size is 9-bit, fragment size is 9-bit
janv. 25 20:34:37 cyril-home kernel: amdgpu 0000:03:00.0: amdgpu: VRAM: 20464M 0x0000008000000000 - 0x00000084FEFFFFFF (20464M used)
janv. 25 20:34:37 cyril-home kernel: amdgpu 0000:03:00.0: amdgpu: GART: 512M 0x0000000000000000 - 0x000000001FFFFFFF
janv. 25 20:34:37 cyril-home kernel: [drm] Detected VRAM RAM=20464M, BAR=32768M
janv. 25 20:34:37 cyril-home kernel: [drm] RAM width 320bits GDDR6
janv. 25 20:34:37 cyril-home kernel: [drm] amdgpu: 20464M of VRAM memory ready
janv. 25 20:34:37 cyril-home kernel: [drm] amdgpu: 15617M of GTT memory ready.
janv. 25 20:34:37 cyril-home kernel: [drm] GART: num cpu pages 131072, num gpu pages 131072
janv. 25 20:34:37 cyril-home kernel: [drm] PCIE GART of 512M enabled (table at 0x00000084FEB00000).
janv. 25 20:34:37 cyril-home kernel: [drm] Loading DMUB firmware via PSP: version=0x07000A01
janv. 25 20:34:37 cyril-home kernel: amdgpu 0000:03:00.0: amdgpu: CP RS64 enable
janv. 25 20:34:37 cyril-home kernel: [drm] Found VCN firmware Version ENC: 1.9 DEC: 5 VEP: 0 Revision: 1
janv. 25 20:34:37 cyril-home kernel: amdgpu 0000:03:00.0: amdgpu: Will use PSP to load VCN firmware
janv. 25 20:34:37 cyril-home kernel: [drm] max_doorbell_slices=32767
janv. 25 20:34:37 cyril-home kernel: [drm] reserve 0x1300000 from 0x84fc000000 for PSP TMR
janv. 25 20:34:37 cyril-home kernel: amdgpu 0000:03:00.0: amdgpu: RAP: optional rap ta ucode is not available
janv. 25 20:34:37 cyril-home kernel: amdgpu 0000:03:00.0: amdgpu: SECUREDISPLAY: securedisplay ta ucode is not available
janv. 25 20:34:37 cyril-home kernel: amdgpu 0000:03:00.0: amdgpu: smu driver if version = 0x00000032, smu fw if version = 0x00000034, smu fw program = 0, smu fw version = 0x004e4b00 (78.75.0)
janv. 25 20:34:37 cyril-home kernel: amdgpu 0000:03:00.0: amdgpu: SMU driver if version not matched
janv. 25 20:34:37 cyril-home kernel: amdgpu 0000:03:00.0: amdgpu: SMU is initialized successfully!
janv. 25 20:34:37 cyril-home kernel: [drm] Display Core initialized with v3.2.207!
janv. 25 20:34:37 cyril-home kernel: [drm] DMUB hardware initialized: version=0x07000A01
janv. 25 20:34:37 cyril-home kernel: [drm] kiq ring mec 3 pipe 1 q 0
janv. 25 20:34:37 cyril-home kernel: [drm] VCN decode and encode initialized successfully(under DPG Mode).
janv. 25 20:34:37 cyril-home kernel: amdgpu 0000:03:00.0: [drm:jpeg_v4_0_hw_init [amdgpu]] JPEG decode initialized successfully.
janv. 25 20:34:37 cyril-home kernel: kfd kfd: amdgpu: Allocated 3969056 bytes on gart
janv. 25 20:34:37 cyril-home kernel: amdgpu: sdma_bitmap: fff0
janv. 25 20:34:37 cyril-home kernel: amdgpu: HMM registered 20464MB device memory
janv. 25 20:34:37 cyril-home kernel: UBSAN: array-index-out-of-bounds in /build/linux-oem-6.1-2N3I2n/linux-oem-6.1-6.1.0/drivers/gpu/drm/amd/amdgpu/../amdkfd/kfd_crat.c:1391:24
janv. 25 20:34:37 cyril-home kernel:  fill_in_l2_l3_pcache+0x23f/0x390 [amdgpu]
janv. 25 20:34:37 cyril-home kernel:  kfd_fill_gpu_cache_info+0x122/0x8a0 [amdgpu]
janv. 25 20:34:37 cyril-home kernel:  kfd_create_vcrat_image_gpu.constprop.0+0x28f/0x4c0 [amdgpu]
janv. 25 20:34:37 cyril-home kernel:  kfd_create_crat_image_virtual+0x130/0x170 [amdgpu]
janv. 25 20:34:37 cyril-home kernel:  kfd_topology_add_device+0x560/0x6f0 [amdgpu]
janv. 25 20:34:37 cyril-home kernel:  kgd2kfd_device_init.cold+0x3a0/0x515 [amdgpu]
janv. 25 20:34:37 cyril-home kernel:  amdgpu_amdkfd_device_init+0x168/0x210 [amdgpu]
janv. 25 20:34:37 cyril-home kernel:  amdgpu_device_ip_init+0x845/0x88e [amdgpu]
janv. 25 20:34:37 cyril-home kernel:  amdgpu_device_init.cold+0x2bf/0x7c3 [amdgpu]
janv. 25 20:34:37 cyril-home kernel:  amdgpu_driver_load_kms+0x1a/0x120 [amdgpu]
janv. 25 20:34:37 cyril-home kernel:  amdgpu_pci_probe+0x16d/0x3a0 [amdgpu]
janv. 25 20:34:37 cyril-home kernel:  amdgpu_init+0x6a/0x1000 [amdgpu]
janv. 25 20:34:37 cyril-home kernel: UBSAN: array-index-out-of-bounds in /build/linux-oem-6.1-2N3I2n/linux-oem-6.1-6.1.0/drivers/gpu/drm/amd/amdgpu/../amdkfd/kfd_crat.c:1393:24
janv. 25 20:34:37 cyril-home kernel:  fill_in_l2_l3_pcache+0x284/0x390 [amdgpu]
janv. 25 20:34:37 cyril-home kernel:  kfd_fill_gpu_cache_info+0x122/0x8a0 [amdgpu]
janv. 25 20:34:37 cyril-home kernel:  kfd_create_vcrat_image_gpu.constprop.0+0x28f/0x4c0 [amdgpu]
janv. 25 20:34:37 cyril-home kernel:  kfd_create_crat_image_virtual+0x130/0x170 [amdgpu]
janv. 25 20:34:37 cyril-home kernel:  kfd_topology_add_device+0x560/0x6f0 [amdgpu]
janv. 25 20:34:37 cyril-home kernel:  kgd2kfd_device_init.cold+0x3a0/0x515 [amdgpu]
janv. 25 20:34:37 cyril-home kernel:  amdgpu_amdkfd_device_init+0x168/0x210 [amdgpu]
janv. 25 20:34:37 cyril-home kernel:  amdgpu_device_ip_init+0x845/0x88e [amdgpu]
janv. 25 20:34:37 cyril-home kernel:  amdgpu_device_init.cold+0x2bf/0x7c3 [amdgpu]
janv. 25 20:34:37 cyril-home kernel:  amdgpu_driver_load_kms+0x1a/0x120 [amdgpu]
janv. 25 20:34:37 cyril-home kernel:  amdgpu_pci_probe+0x16d/0x3a0 [amdgpu]
janv. 25 20:34:37 cyril-home kernel:  amdgpu_init+0x6a/0x1000 [amdgpu]
janv. 25 20:34:37 cyril-home kernel: UBSAN: array-index-out-of-bounds in /build/linux-oem-6.1-2N3I2n/linux-oem-6.1-6.1.0/drivers/gpu/drm/amd/amdgpu/../amdkfd/kfd_crat.c:1395:24
janv. 25 20:34:37 cyril-home kernel:  fill_in_l2_l3_pcache+0x2cc/0x390 [amdgpu]
janv. 25 20:34:37 cyril-home kernel:  kfd_fill_gpu_cache_info+0x122/0x8a0 [amdgpu]
janv. 25 20:34:37 cyril-home kernel:  kfd_create_vcrat_image_gpu.constprop.0+0x28f/0x4c0 [amdgpu]
janv. 25 20:34:37 cyril-home kernel:  kfd_create_crat_image_virtual+0x130/0x170 [amdgpu]
janv. 25 20:34:37 cyril-home kernel:  kfd_topology_add_device+0x560/0x6f0 [amdgpu]
janv. 25 20:34:37 cyril-home kernel:  kgd2kfd_device_init.cold+0x3a0/0x515 [amdgpu]
janv. 25 20:34:37 cyril-home kernel:  amdgpu_amdkfd_device_init+0x168/0x210 [amdgpu]
janv. 25 20:34:37 cyril-home kernel:  amdgpu_device_ip_init+0x845/0x88e [amdgpu]
janv. 25 20:34:37 cyril-home kernel:  amdgpu_device_init.cold+0x2bf/0x7c3 [amdgpu]
janv. 25 20:34:37 cyril-home kernel:  amdgpu_driver_load_kms+0x1a/0x120 [amdgpu]
janv. 25 20:34:37 cyril-home kernel:  amdgpu_pci_probe+0x16d/0x3a0 [amdgpu]
janv. 25 20:34:37 cyril-home kernel:  amdgpu_init+0x6a/0x1000 [amdgpu]
janv. 25 20:34:37 cyril-home kernel: UBSAN: array-index-out-of-bounds in /build/linux-oem-6.1-2N3I2n/linux-oem-6.1-6.1.0/drivers/gpu/drm/amd/amdgpu/../amdkfd/kfd_crat.c:1397:24
janv. 25 20:34:37 cyril-home kernel:  fill_in_l2_l3_pcache+0x311/0x390 [amdgpu]
janv. 25 20:34:37 cyril-home kernel:  kfd_fill_gpu_cache_info+0x122/0x8a0 [amdgpu]
janv. 25 20:34:37 cyril-home kernel:  kfd_create_vcrat_image_gpu.constprop.0+0x28f/0x4c0 [amdgpu]
janv. 25 20:34:37 cyril-home kernel:  kfd_create_crat_image_virtual+0x130/0x170 [amdgpu]
janv. 25 20:34:37 cyril-home kernel:  kfd_topology_add_device+0x560/0x6f0 [amdgpu]
janv. 25 20:34:37 cyril-home kernel:  kgd2kfd_device_init.cold+0x3a0/0x515 [amdgpu]
janv. 25 20:34:37 cyril-home kernel:  amdgpu_amdkfd_device_init+0x168/0x210 [amdgpu]
janv. 25 20:34:37 cyril-home kernel:  amdgpu_device_ip_init+0x845/0x88e [amdgpu]
janv. 25 20:34:37 cyril-home kernel:  amdgpu_device_init.cold+0x2bf/0x7c3 [amdgpu]
janv. 25 20:34:37 cyril-home kernel:  amdgpu_driver_load_kms+0x1a/0x120 [amdgpu]
janv. 25 20:34:37 cyril-home kernel:  amdgpu_pci_probe+0x16d/0x3a0 [amdgpu]
janv. 25 20:34:37 cyril-home kernel:  amdgpu_init+0x6a/0x1000 [amdgpu]
janv. 25 20:34:37 cyril-home kernel: amdgpu: SRAT table not found
janv. 25 20:34:37 cyril-home kernel: amdgpu: Virtual CRAT table created for GPU
janv. 25 20:34:37 cyril-home kernel: amdgpu: Topology: Add dGPU node [0x744c:0x1002]
janv. 25 20:34:37 cyril-home kernel: kfd kfd: amdgpu: added device 1002:744c
janv. 25 20:34:37 cyril-home kernel: amdgpu 0000:03:00.0: amdgpu: SE 6, SH per SE 2, CU per SH 8, active_cu_number 84
janv. 25 20:34:37 cyril-home kernel: amdgpu 0000:03:00.0: amdgpu: ring gfx_0.0.0 uses VM inv eng 0 on hub 0
janv. 25 20:34:37 cyril-home kernel: amdgpu 0000:03:00.0: amdgpu: ring comp_1.0.0 uses VM inv eng 1 on hub 0
janv. 25 20:34:37 cyril-home kernel: amdgpu 0000:03:00.0: amdgpu: ring comp_1.1.0 uses VM inv eng 4 on hub 0
janv. 25 20:34:37 cyril-home kernel: amdgpu 0000:03:00.0: amdgpu: ring comp_1.2.0 uses VM inv eng 6 on hub 0
janv. 25 20:34:37 cyril-home kernel: amdgpu 0000:03:00.0: amdgpu: ring comp_1.3.0 uses VM inv eng 7 on hub 0
janv. 25 20:34:37 cyril-home kernel: amdgpu 0000:03:00.0: amdgpu: ring comp_1.0.1 uses VM inv eng 8 on hub 0
janv. 25 20:34:37 cyril-home kernel: amdgpu 0000:03:00.0: amdgpu: ring comp_1.1.1 uses VM inv eng 9 on hub 0
janv. 25 20:34:37 cyril-home kernel: amdgpu 0000:03:00.0: amdgpu: ring comp_1.2.1 uses VM inv eng 10 on hub 0
janv. 25 20:34:37 cyril-home kernel: amdgpu 0000:03:00.0: amdgpu: ring comp_1.3.1 uses VM inv eng 11 on hub 0
janv. 25 20:34:37 cyril-home kernel: amdgpu 0000:03:00.0: amdgpu: ring sdma0 uses VM inv eng 12 on hub 0
janv. 25 20:34:37 cyril-home kernel: amdgpu 0000:03:00.0: amdgpu: ring sdma1 uses VM inv eng 13 on hub 0
janv. 25 20:34:37 cyril-home kernel: amdgpu 0000:03:00.0: amdgpu: ring vcn_unified_0 uses VM inv eng 0 on hub 1
janv. 25 20:34:37 cyril-home kernel: amdgpu 0000:03:00.0: amdgpu: ring vcn_unified_1 uses VM inv eng 1 on hub 1
janv. 25 20:34:37 cyril-home kernel: amdgpu 0000:03:00.0: amdgpu: ring jpeg_dec uses VM inv eng 4 on hub 1
janv. 25 20:34:37 cyril-home kernel: amdgpu 0000:03:00.0: amdgpu: ring mes_kiq_3.1.0 uses VM inv eng 14 on hub 0
janv. 25 20:34:37 cyril-home kernel: [drm] ring gfx_32768.1.1 was added
janv. 25 20:34:37 cyril-home kernel: [drm] ring compute_32768.2.2 was added
janv. 25 20:34:37 cyril-home kernel: [drm] ring compute_32768.2.3 was added
janv. 25 20:34:37 cyril-home kernel: [drm] ring compute_32768.2.4 was added
janv. 25 20:34:37 cyril-home kernel: [drm] ring compute_32768.2.5 was added
janv. 25 20:34:37 cyril-home kernel: [drm] ring sdma_32768.3.6 was added
janv. 25 20:34:37 cyril-home kernel: [drm] ring sdma_32768.3.7 was added
janv. 25 20:34:37 cyril-home kernel: [drm] ring gfx_32768.1.1 test pass
janv. 25 20:34:37 cyril-home kernel: [drm] ring gfx_32768.1.1 ib test pass
janv. 25 20:34:37 cyril-home kernel: [drm] ring compute_32768.2.2 test pass
janv. 25 20:34:37 cyril-home kernel: [drm] ring compute_32768.2.2 ib test pass
janv. 25 20:34:37 cyril-home kernel: [drm] ring compute_32768.2.3 test pass
janv. 25 20:34:37 cyril-home kernel: [drm] ring compute_32768.2.3 ib test pass
janv. 25 20:34:37 cyril-home kernel: [drm] ring compute_32768.2.4 test pass
janv. 25 20:34:37 cyril-home kernel: [drm] ring compute_32768.2.4 ib test pass
janv. 25 20:34:37 cyril-home kernel: [drm] ring compute_32768.2.5 test pass
janv. 25 20:34:37 cyril-home kernel: [drm] ring compute_32768.2.5 ib test pass
janv. 25 20:34:37 cyril-home kernel: [drm] ring sdma_32768.3.6 test pass
janv. 25 20:34:37 cyril-home kernel: [drm] ring sdma_32768.3.6 ib test pass
janv. 25 20:34:37 cyril-home kernel: [drm] ring sdma_32768.3.7 test pass
janv. 25 20:34:37 cyril-home kernel: [drm] ring sdma_32768.3.7 ib test pass
janv. 25 20:34:37 cyril-home kernel: amdgpu 0000:03:00.0: amdgpu: Using BACO for runtime pm
janv. 25 20:34:37 cyril-home kernel: [drm] Initialized amdgpu 3.49.0 20150101 for 0000:03:00.0 on minor 0
janv. 25 20:34:37 cyril-home kernel: fbcon: amdgpudrmfb (fb0) is primary device
janv. 25 20:34:37 cyril-home kernel: [drm] DSC precompute is not needed.
janv. 25 20:34:37 cyril-home kernel: amdgpu 0000:03:00.0: [drm] fb0: amdgpudrmfb frame buffer device
janv. 25 20:34:37 cyril-home kernel: amdgpu 0000:13:00.0: enabling device (0006 -> 0007)
janv. 25 20:34:37 cyril-home kernel: [drm] initializing kernel modesetting (IP DISCOVERY 0x1002:0x164E 0x1002:0x164E 0xC2).
janv. 25 20:34:37 cyril-home kernel: [drm] register mmio base: 0xFCA00000
janv. 25 20:34:37 cyril-home kernel: [drm] register mmio size: 524288
janv. 25 20:34:37 cyril-home kernel: [drm] add ip block number 0 <nv_common>
janv. 25 20:34:37 cyril-home kernel: [drm] add ip block number 1 <gmc_v10_0>
janv. 25 20:34:37 cyril-home kernel: [drm] add ip block number 2 <navi10_ih>
janv. 25 20:34:37 cyril-home kernel: [drm] add ip block number 3 <psp>
janv. 25 20:34:37 cyril-home kernel: [drm] add ip block number 4 <smu>
janv. 25 20:34:37 cyril-home kernel: [drm] add ip block number 5 <dm>
janv. 25 20:34:37 cyril-home kernel: [drm] add ip block number 6 <gfx_v10_0>
janv. 25 20:34:37 cyril-home kernel: [drm] add ip block number 7 <sdma_v5_2>
janv. 25 20:34:37 cyril-home kernel: [drm] add ip block number 8 <vcn_v3_0>
janv. 25 20:34:37 cyril-home kernel: [drm] add ip block number 9 <jpeg_v3_0>
janv. 25 20:34:37 cyril-home kernel: amdgpu 0000:13:00.0: amdgpu: Fetched VBIOS from VFCT
janv. 25 20:34:37 cyril-home kernel: amdgpu: ATOM BIOS: 102-RAPHAEL-006
janv. 25 20:34:37 cyril-home kernel: [drm] VCN(0) decode is enabled in VM mode
janv. 25 20:34:37 cyril-home kernel: [drm] VCN(0) encode is enabled in VM mode
janv. 25 20:34:37 cyril-home kernel: amdgpu 0000:13:00.0: amdgpu: Trusted Memory Zone (TMZ) feature not supported
janv. 25 20:34:37 cyril-home kernel: amdgpu 0000:13:00.0: amdgpu: PCIE atomic ops is not supported
janv. 25 20:34:37 cyril-home kernel: [drm] vm size is 262144 GB, 4 levels, block size is 9-bit, fragment size is 9-bit
janv. 25 20:34:37 cyril-home kernel: amdgpu 0000:13:00.0: amdgpu: VRAM: 512M 0x000000F400000000 - 0x000000F41FFFFFFF (512M used)
janv. 25 20:34:37 cyril-home kernel: amdgpu 0000:13:00.0: amdgpu: GART: 1024M 0x0000000000000000 - 0x000000003FFFFFFF
janv. 25 20:34:37 cyril-home kernel: amdgpu 0000:13:00.0: amdgpu: AGP: 267419648M 0x000000F800000000 - 0x0000FFFFFFFFFFFF
janv. 25 20:34:37 cyril-home kernel: [drm] Detected VRAM RAM=512M, BAR=512M
janv. 25 20:34:37 cyril-home kernel: [drm] RAM width 128bits DDR5
janv. 25 20:34:37 cyril-home kernel: [drm] amdgpu: 512M of VRAM memory ready
janv. 25 20:34:37 cyril-home kernel: [drm] amdgpu: 15617M of GTT memory ready.
janv. 25 20:34:37 cyril-home kernel: [drm] GART: num cpu pages 262144, num gpu pages 262144
janv. 25 20:34:37 cyril-home kernel: [drm] PCIE GART of 1024M enabled (table at 0x000000F41FC00000).
janv. 25 20:34:37 cyril-home kernel: amdgpu 0000:13:00.0: amdgpu: PSP runtime database doesn't exist
janv. 25 20:34:37 cyril-home kernel: amdgpu 0000:13:00.0: amdgpu: PSP runtime database doesn't exist
janv. 25 20:34:37 cyril-home kernel: [drm] Loading DMUB firmware via PSP: version=0x05000500
janv. 25 20:34:37 cyril-home kernel: [drm] use_doorbell being set to: [true]
janv. 25 20:34:37 cyril-home kernel: [drm] Found VCN firmware Version ENC: 1.24 DEC: 2 VEP: 0 Revision: 0
janv. 25 20:34:37 cyril-home kernel: amdgpu 0000:13:00.0: amdgpu: Will use PSP to load VCN firmware
janv. 25 20:34:37 cyril-home kernel: [drm] reserve 0xa00000 from 0xf41e000000 for PSP TMR
janv. 25 20:34:37 cyril-home kernel: amdgpu 0000:13:00.0: amdgpu: RAS: optional ras ta ucode is not available
janv. 25 20:34:37 cyril-home kernel: amdgpu 0000:13:00.0: amdgpu: RAP: optional rap ta ucode is not available
janv. 25 20:34:37 cyril-home kernel: amdgpu 0000:13:00.0: amdgpu: SECUREDISPLAY: securedisplay ta ucode is not available
janv. 25 20:34:37 cyril-home kernel: amdgpu 0000:13:00.0: amdgpu: smu driver if version = 0x00000004, smu fw if version = 0x00000005, smu fw program = 0, smu fw version = 0x00544900 (84.73.0)
janv. 25 20:34:37 cyril-home kernel: amdgpu 0000:13:00.0: amdgpu: SMU driver if version not matched
janv. 25 20:34:37 cyril-home kernel: amdgpu 0000:13:00.0: amdgpu: SMU is initialized successfully!
janv. 25 20:34:37 cyril-home kernel: [drm] Display Core initialized with v3.2.207!
janv. 25 20:34:37 cyril-home kernel: [drm] DMUB hardware initialized: version=0x05000500
janv. 25 20:34:37 cyril-home kernel: [drm] kiq ring mec 2 pipe 1 q 0
janv. 25 20:34:37 cyril-home kernel: [drm] VCN decode and encode initialized successfully(under DPG Mode).
janv. 25 20:34:37 cyril-home kernel: kfd kfd: amdgpu: Allocated 3969056 bytes on gart
janv. 25 20:34:37 cyril-home kernel: amdgpu: sdma_bitmap: 3
janv. 25 20:34:37 cyril-home kernel: amdgpu: HMM registered 512MB device memory
janv. 25 20:34:37 cyril-home kernel: amdgpu: SRAT table not found
janv. 25 20:34:37 cyril-home kernel: amdgpu: Virtual CRAT table created for GPU
janv. 25 20:34:37 cyril-home kernel: amdgpu: Topology: Add dGPU node [0x164e:0x1002]
janv. 25 20:34:37 cyril-home kernel: kfd kfd: amdgpu: added device 1002:164e
janv. 25 20:34:37 cyril-home kernel: amdgpu 0000:13:00.0: amdgpu: SE 1, SH per SE 1, CU per SH 2, active_cu_number 2
janv. 25 20:34:37 cyril-home kernel: amdgpu 0000:13:00.0: amdgpu: ring gfx_0.0.0 uses VM inv eng 0 on hub 0
janv. 25 20:34:37 cyril-home kernel: amdgpu 0000:13:00.0: amdgpu: ring comp_1.0.0 uses VM inv eng 1 on hub 0
janv. 25 20:34:37 cyril-home kernel: amdgpu 0000:13:00.0: amdgpu: ring comp_1.1.0 uses VM inv eng 4 on hub 0
janv. 25 20:34:37 cyril-home kernel: amdgpu 0000:13:00.0: amdgpu: ring comp_1.2.0 uses VM inv eng 5 on hub 0
janv. 25 20:34:37 cyril-home kernel: amdgpu 0000:13:00.0: amdgpu: ring comp_1.3.0 uses VM inv eng 6 on hub 0
janv. 25 20:34:37 cyril-home kernel: amdgpu 0000:13:00.0: amdgpu: ring comp_1.0.1 uses VM inv eng 7 on hub 0
janv. 25 20:34:37 cyril-home kernel: amdgpu 0000:13:00.0: amdgpu: ring comp_1.1.1 uses VM inv eng 8 on hub 0
janv. 25 20:34:37 cyril-home kernel: amdgpu 0000:13:00.0: amdgpu: ring comp_1.2.1 uses VM inv eng 9 on hub 0
janv. 25 20:34:37 cyril-home kernel: amdgpu 0000:13:00.0: amdgpu: ring comp_1.3.1 uses VM inv eng 10 on hub 0
janv. 25 20:34:37 cyril-home kernel: amdgpu 0000:13:00.0: amdgpu: ring kiq_2.1.0 uses VM inv eng 11 on hub 0
janv. 25 20:34:37 cyril-home kernel: amdgpu 0000:13:00.0: amdgpu: ring sdma0 uses VM inv eng 12 on hub 0
janv. 25 20:34:37 cyril-home kernel: amdgpu 0000:13:00.0: amdgpu: ring vcn_dec_0 uses VM inv eng 0 on hub 1
janv. 25 20:34:37 cyril-home kernel: amdgpu 0000:13:00.0: amdgpu: ring vcn_enc_0.0 uses VM inv eng 1 on hub 1
janv. 25 20:34:37 cyril-home kernel: amdgpu 0000:13:00.0: amdgpu: ring vcn_enc_0.1 uses VM inv eng 4 on hub 1
janv. 25 20:34:37 cyril-home kernel: [drm] Initialized amdgpu 3.49.0 20150101 for 0000:13:00.0 on minor 1
janv. 25 20:34:37 cyril-home kernel: amdgpu 0000:13:00.0: [drm] Cannot find any crtc or sizes
janv. 25 20:34:37 cyril-home systemd[1]: Starting Load Kernel Module drm...
janv. 25 20:34:37 cyril-home systemd[1]: modprobe@drm.service: Deactivated successfully.
janv. 25 20:34:37 cyril-home systemd[1]: Finished Load Kernel Module drm.
janv. 25 20:34:37 cyril-home kernel: snd_hda_intel 0000:13:00.1: bound 0000:13:00.0 (ops amdgpu_dm_audio_component_bind_ops [amdgpu])
janv. 25 20:34:37 cyril-home kernel: snd_hda_intel 0000:03:00.1: bound 0000:03:00.0 (ops amdgpu_dm_audio_component_bind_ops [amdgpu])
janv. 25 20:34:39 cyril-home sensors[1226]: amdgpu-pci-0300
janv. 25 20:34:39 cyril-home sensors[1226]: amdgpu-pci-1300
janv. 25 20:34:40 cyril-home kernel: amdgpu 0000:03:00.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=none:owns=none
janv. 25 20:34:40 cyril-home kernel: amdgpu 0000:13:00.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=none:owns=none
janv. 25 20:34:44 cyril-home kernel: [drm] Unknown EDID CEA parser results
janv. 25 20:34:45 cyril-home kernel: [drm] Unknown EDID CEA parser results

I should also note that when I run a project in the Godot game engine, it does seem to run on the GPU properly (as indicated by Vulkan API 1.3.238 - Using Vulkan Device #0: AMD - AMD Radeon RX 7900 XT (RADV GFX1100)), which seems to concur with the Unigine Benchmark I ran a few days ago. At this point, I'm suspecting that Steam (flatpak) is the one causing issues and not using the GPU... (although that doesn't explain why nvtop also fails to detect the GPU)

I'm just finished trying the Kisak PPA again to check how Steam fares, and it actually doesn't work either, so I'm in more or less the same situation with both Kisak and Oibaf PPAs.

sudo nano /usr/share/X11/xorg.conf.d/10-amdgpu.conf -> add Option "SWcursor" "true"

To me (my personal opinion which could be wrong), the fact this needs to be done seems to indicate the amdgpu driver still needs some work for it to work properly with this GPU on X Server. I have no idea if this might be a factor with regards to ability to game.

I honestly don't know what to think about this one, I definitely agree that something is wrong here, but a friend of mine has a similar setup (same CPU and GPU, not from the same vendor though), and while he also had to use the software cursor, he got his GPU working on ArchLinux (with the now official packages, but he compiled Mesa before that, for both 64 and 32 bit IIRC).

That's strange because the mesa update from the oibaf PPA lists these packages will be affected, which includes the two packages highlighted above:

This update affects the following installed packages:
• libegl-mesa0
• libegl-mesa0:i386
• libgbm1
• libgbm1:i386
• libgl1-mesa-dri
• libgl1-mesa-dri:i386
• libglapi-mesa
• libglapi-mesa:i386
• libglx-mesa0
• libglx-mesa0:i386
• libxatracker2
• mesa-va-drivers
• mesa-vdpau-drivers
• mesa-vdpau-drivers:i386
• mesa-vulkan-drivers
• mesa-vulkan-drivers:i386

What is the output of this command: apt policy libglx-mesa0:i386 libgl1-mesa-dri:i386

Thanks for your feedback roblm, here's the output of the command:

Code: Select all

libglx-mesa0:i386:
  Installed: (none)
  Candidate: 22.0.5-0ubuntu0.3
  Version table:
     22.0.5-0ubuntu0.3 500
        500 http://archive.ubuntu.com/ubuntu jammy-updates/main i386 Packages
     22.0.1-1ubuntu2 500
        500 http://archive.ubuntu.com/ubuntu jammy/main i386 Packages
libgl1-mesa-dri:i386:
  Installed: (none)
  Candidate: 22.0.5-0ubuntu0.3
  Version table:
     22.0.5-0ubuntu0.3 500
        500 http://archive.ubuntu.com/ubuntu jammy-updates/main i386 Packages
        100 /var/lib/dpkg/status
     22.0.1-1ubuntu2 500
        500 http://archive.ubuntu.com/ubuntu jammy/main i386 Packages

[SMG]

In the BIOS settings, priority is given to the 7900 XT instead of the CPU's integrated graphics.

I'm not sure what that means with respect to the firmware (BIOS/UEFI) settings and capabilities, but this does seem to indicate both are available for use.

The Xorg log does indicate that. Both are probed and drm devices set for both cards.

Code: Select all

[     8.186] (II) xfree86: Adding drm device (/dev/dri/card0)
[     8.186] (II) Platform probe for /sys/devices/pci0000:00/0000:00:01.1/0000:01:00.0/0000:02:00.0/0000:03:00.0/drm/card0
[     8.213] (II) xfree86: Adding drm device (/dev/dri/card1)
[     8.213] (II) Platform probe for /sys/devices/pci0000:00/0000:00:08.1/0000:13:00.0/drm/card1
[     8.216] (--) PCI:*(3@0:0:0) 1002:744c:1da2:471e rev 204, Mem @ 0xf000000000/34359738368, 0xf800000000/268435456, 0xfcb00000/1048576, I/O @ 0x0000f000/256, BIOS @ 0x????????/131072
[     8.216] (--) PCI: (19@0:0:0) 1002:164e:1002:164e rev 194, Mem @ 0xf820000000/268435456, 0xf830000000/2097152, 0xfca00000/524288, I/O @ 0x0000d000/256

Display drivers are loaded for each GPU.

This below is the part showing both renderers are loaded. That means, according to the operating system, both are available for use. Now whether or not the BIOS makes a determination of what it sees in use based on whether or not monitors are attached to each GPU might be something different. I don't know the design considerations for this setup.

Code: Select all

[     8.392] (II) AMDGPU(0): glamor X acceleration enabled on AMD Radeon RX 7900 XT (gfx1100, LLVM 15.0.5, DRM 3.49, 6.1.0-1004-oem)
[     8.392] (II) AMDGPU(0): glamor detected, initialising EGL layer.

[     8.433] (II) AMDGPU(G0): glamor X acceleration enabled on AMD Radeon Graphics (gfx1036, LLVM 15.0.5, DRM 3.49, 6.1.0-1004-oem)
[     8.433] (II) AMDGPU(G0): glamor detected, initialising EGL layer.

As for journalctl -b | grep -i "drm\|amdgpu\|03:00.0\|13:00.0", here is the output:

I went searching through bug reports on 7900 on AMD Gitlab and found a closed report on UBSAN: array-index-out-of-bounds. The person posting the report has a 7900 XT. They closed the report indicating "upgrading to kernel 6.1.1 (xanmod) no longer shows this error", but they also don't indicate they were having any problems because of it. (Xanmod kernel adds kernel parameters and files in addition to the kernel pacakges.)

I also found I suspect amdgpu driver in memory leak. They are testing patches for the bug, which apparently was introduced sometime between the 6.1.7 kernel and the 6.2 release candidate that person was using. The current 6.1 kernel you are using is okay. However, I noticed the person mentioned in how to reproduce the error:

Play in the game "Tom Clancy’s The Division® 2" 3-4 hours with DX12 render.
For it needed steam client, bleeding edge proton experimental and the game "Tom Clancy’s The Division® 2".

so maybe you need "bleeding edge proton experimental" for steam client to work?

I'm just finished trying the Kisak PPA again to check how Steam fares, and it actually doesn't work either, so I'm in more or less the same situation with both Kisak and Oibaf PPAs.

Rua mentioned that earlier and I think I've seen one or two other people on this forum mentioning getting errors about missing i386 with kisak as well.

a friend of mine has a similar setup (same CPU and GPU, not from the same vendor though), and while he also had to use the software cursor, he got his GPU working on ArchLinux (with the now official packages, but he compiled Mesa before that, for both 64 and 32 bit IIRC).

Is he using X Server? or something else? Maybe that is making a difference.

[SMG]

Also, using nvtop to try and monitor the GPU tells me "No GPU to monitor".

I found this closed nvtop bug AMDGPU RX 6700 XT issue #144 with the same message. Check to see which version you are using. The developer indicates, "The AMDGPU support was added in v2.0.0" which at the time that bug was posted was a newer version than what was in the Ubuntu 22.04 (LM21) repositories.

[Cykyrios]

I just happen to have tried this before going to bed - turns out we have a very old version on Mint 21.1, which is version 1.2.2. I downloaded the version 3.0.1 AppImage on GitHub, and it detects my GPU just fine.
All in all, I'm now pretty convinced that simply following your guide did actually get my 7900 XT working, it's just that other tools and apps may be outdated as well and not using it properly.

Additionally, I also ran sudo update-pciids, which causes lspci and neofetch to print the names of the devices (GPU: AMD ATI 13:00.0 Raphael for onboard graphics and GPU: AMD ATI Radeon RX 7900 XT/7900 for the discrete GPU), not sure whether that has any other consequence.

Now the only issue I'm left with (I hope), is Steam either not installing once Kisak PPA or Oibaf PPA are installed (or getting removed if installed before that), or the Flatpak version causing games to not use the GPU. Should I move this to another thread and mark this one solved?

[roblm]

There are no libglx-mesa0:i386 and libgl1-mesa-dri:i386 packages installed, but there should be from the oibaf PPA. I assume you opened the Update Manager after installing that PPA and installed the mesa package from oibaf. Check if that package was installed.

If you did install the mesa package and you want to troubleshoot this further, then I suggest opening Software Sources > PPAs and remove the oibaf PPA. Then select Maintenance > Downgrade foreign packages and select all the packages listed and downgrade them. Then post the output of apt policy libglx-mesa0:i386 libgl1-mesa-dri:i386 again. Older versions of those two packages should be installed. If they are, then you can try adding the oibaf PPA again.

[SMG]

Additionally, I also ran sudo update-pciids, which causes lspci and neofetch to print the names of the devices (GPU: AMD ATI 13:00.0 Raphael for onboard graphics and GPU: AMD ATI Radeon RX 7900 XT/7900 for the discrete GPU), not sure whether that has any other consequence.

I guess you will find out and can let us know. I would think that is more of a "human readable" function and not something used by the graphics driver code.

Now the only issue I'm left with (I hope), is Steam either not installing once Kisak PPA or Oibaf PPA are installed (or getting removed if installed before that), or the Flatpak version causing games to not use the GPU. Should I move this to another thread and mark this one solved?

Considering the newer mesa (currently only available through PPAs) is key to getting this GPU to work correctly, it's fine to continue here.

[Cykyrios]

a friend of mine has a similar setup (same CPU and GPU, not from the same vendor though), and while he also had to use the software cursor, he got his GPU working on ArchLinux (with the now official packages, but he compiled Mesa before that, for both 64 and 32 bit IIRC).

Is he using X Server? or something else? Maybe that is making a difference.

Sorry, I missed your previous post while answering this morning. Yes, he is using X as well (not sure if Wayland messes up the cursor as well).

There are no libglx-mesa0:i386 and libgl1-mesa-dri:i386 packages installed, but there should be from the oibaf PPA. I assume you opened the Update Manager after installing that PPA and installed the mesa package from oibaf. Check if that package was installed.

If you did install the mesa package and you want to troubleshoot this further, then I suggest opening Software Sources > PPAs and remove the oibaf PPA. Then select Maintenance > Downgrade foreign packages and select all the packages listed and downgrade them. Then post the output of apt policy libglx-mesa0:i386 libgl1-mesa-dri:i386 again. Older versions of those two packages should be installed. If they are, then you can try adding the oibaf PPA again.

I don't have a package called "mesa", but I do have both libglx-mesa0 and libgl1-mesa-dri installed from oibaf PPA. In Synaptic, I can also see libgl1-mesa-dri:i386 (version 22.0.5-0ubuntu0.3), which is not installed, but not libglx-mesa0:i386. Here is the output from apt list --installed | grep mesa:

Code: Select all

libegl-mesa0/jammy,now 23.1~git2301260600.a08d6d~oibaf~j amd64 [installed]
libgl1-mesa-dev/jammy,now 23.1~git2301260600.a08d6d~oibaf~j amd64 [installed]
libgl1-mesa-dri/jammy,now 23.1~git2301260600.a08d6d~oibaf~j amd64 [installed]
libglapi-mesa/jammy,now 23.1~git2301260600.a08d6d~oibaf~j amd64 [installed]
libglu1-mesa-dev/jammy,now 9.0.2-1 amd64 [installed]
libglu1-mesa/jammy,now 9.0.2-1 amd64 [installed]
libglx-mesa0/jammy,now 23.1~git2301260600.a08d6d~oibaf~j amd64 [installed]
mesa-utils-bin/jammy,now 8.4.0-1ubuntu1 amd64 [installed]
mesa-utils/jammy,now 8.4.0-1ubuntu1 amd64 [installed]
mesa-va-drivers/jammy,now 23.1~git2301260600.a08d6d~oibaf~j amd64 [installed]
mesa-vdpau-drivers/jammy,now 23.1~git2301260600.a08d6d~oibaf~j amd64 [installed]
mesa-vulkan-drivers/jammy,now 23.1~git2301260600.a08d6d~oibaf~j amd64 [installed]

I would include what apt-cache dumpavail | grep mesa gives me as well, but it's over 650 lines long.

From there, I removed oibaf PPA and downgraded foreign packages:

Code: Select all

The following additional packages will be installed:
  libgl1-amber-dri
The following NEW packages will be installed:
  libgl1-amber-dri
The following packages will be DOWNGRADED:
  libdrm-amdgpu1 libdrm-common libdrm-intel1 libdrm-nouveau2
  libdrm-radeon1 libdrm2 libegl-mesa0 libgbm1 libgl1-mesa-dev
  libgl1-mesa-dri libglapi-mesa libglx-mesa0 libvdpau1 libxatracker2
  mesa-va-drivers mesa-vdpau-drivers mesa-vulkan-drivers
0 upgraded, 1 newly installed, 17 downgraded, 0 to remove and 3 not upgraded.

The 3 not upgraded packages should be irrelevant here (libinput-bin, libinput-dev, libinput10).

Then I ran apt policy libglx-mesa0:i386 libgl1-mesa-dri:i386:

Code: Select all

libglx-mesa0:i386:
  Installed: (none)
  Candidate: 22.0.5-0ubuntu0.3
  Version table:
     22.0.5-0ubuntu0.3 500
        500 http://archive.ubuntu.com/ubuntu jammy-updates/main i386 Packages
     22.0.1-1ubuntu2 500
        500 http://archive.ubuntu.com/ubuntu jammy/main i386 Packages
libgl1-mesa-dri:i386:
  Installed: (none)
  Candidate: 22.0.5-0ubuntu0.3
  Version table:
     22.0.5-0ubuntu0.3 500
        500 http://archive.ubuntu.com/ubuntu jammy-updates/main i386 Packages
        100 /var/lib/dpkg/status
     22.0.1-1ubuntu2 500
        500 http://archive.ubuntu.com/ubuntu jammy/main i386 Packages

After that, I can install Steam (package version), but of course my GPU no longer meets its requirements (Mesa 22.0.5 with LLVM 13.0.1).

[SMG]

not sure if Wayland messes up the cursor as well

The information I found indicates the issue is only with X Server. I did not find mention of problems with Wayland.

I did some searches and it seems the issue with i386 package installs sporadically pops up for some people from time to time. Maybe roblm will have some ideas, but I did not find anything helpful other than this old ValveSoftware bug report »libgl1-mesa-dri:i386« does not exist #7663 which mentions at the bottom:

consider using Valve's official steam package rather than Ubuntu's modified version

This open bug report from 3 weeks ago with a 7900XT was Steam kills X after being stuck on "Installing breakpad exception handler" 7900 XT #9066 was "interesting" in that the OP says they recommend using Mesa 22.3.0 because "Mesa is such a unstable mess at the moment for RDNA3".

Looking through the closed ValveSoftare bug reports this one Application may not be hardware accelerated on AMD RX 7900 XTX #9077 has a post which seems to reference the issue you've been having? I'm not sure how that might translate to Linux Mint because I'm not really familiar with how Arch handles their packages.

btw: Here is an explanation of Proton Experimental and Proton GE (which I think is considered one of the "bleeding edge version) Proton Experimental Bleeding Edge or Proton-GE-7-10?.

[roblm]

Try re-adding Oibaf PPA, but create a Timeshift snapshot first because this PPA does cause problems sometimes, which I have personally experienced in testing it.

[Cykyrios]

Try re-adding Oibaf PPA, but create a Timeshift snapshot first because this PPA does cause problems sometimes, which I have personally experienced in testing it.

I actually did the opposite: I created a snapshot before downgrading to test your suggestion, and reverted back to it after that. In the current state of things, I prefer having some broken dependencies rather than a non-functional GPU. If needed or when a solution to this issue is found, I might just revert to a fresh install.

btw: Here is an explanation of Proton Experimental and Proton GE (which I think is considered one of the "bleeding edge version) Proton Experimental Bleeding Edge or Proton-GE-7-10?.

Proton Experimental is part of Steam and can be selected on a per-game basis or as a general setting. I have never tried installing it separately (I didn't actually know of the GE version), it's usually enough to choose between Experimental and a specific version whenever a game breaks.


Also, something interesting happened today: I came back from work, booted my computer, noticed there were updates available. Mesa was listed as a flatpak update, version 22.3. I installed it and immediately opened Steam, and... it just works \o/ I tried Portal, the Stanley Parable, Elden Ring, and all three games work perfectly fine now.

The only caveat right now is that I'm using the flatpak version of Steam, and of course I still have broken dependencies/i386 packages due to oibaf PPA (so I cannot install the package version of steam). The only thing I did in the meanwhile was installing wine as per the instructions from the wineHQ website, which does install a bunch of i386 packages. sudo apt install steam-installer still complains about the following i386 packages:

Code: Select all

The following packages have unmet dependencies:
 libglx0:i386 : Depends: libglx-mesa0:i386 but it is not going to be installed
 steam:i386 : Depends: libgl1-mesa-dri:i386 (>= 17.3) but it is not going to be installed
              Recommends: libegl1:i386 but it is not installable
              Recommends: libgbm1:i386 but it is not going to be installed
              Recommends: libsdl2-2.0-0:i386 but it is not installable
              Recommends: mesa-vulkan-drivers:i386 but it is not going to be installed
E: Unable to correct problems, you have held broken packages.

I'm wondering again whether I should mark this thread as solved, as it is somewhat of a misnomer: the only time the GPU was not working properly was before upgrading the kernel, mesa drivers and firmware, and this part works - after that, and still true today, the problem is more about package issues with kisak or oibaf PPAs.

Thank you again SMG and robIm for your help on this, I am of course still open to suggestions about the current package issue, and will myself try to look for answers about this and update here if I do find anything (that is, unless mesa drivers are updated in Mint packages and therefore kisak/oibaf PPAs become unnecessary).

[roblm]

I just finished doing some testing on the test partition of my AMD PC with Mint 21, 5.15 kernel and Radeon RX 560.
I added the Oibaf PPA and had no problems.

Code: Select all

inxi -Gx
Graphics:
  Device-1: AMD Baffin [Radeon RX 460/560D / Pro
  450/455/460/555/555X/560/560X]
    vendor: ASUSTeK AREZ driver: amdgpu v: kernel bus-ID: 02:00.0
  Display: x11 server: X.Org v: 1.21.1.3 driver: X: loaded: amdgpu,ati
    unloaded: fbdev,modesetting,vesa gpu: amdgpu resolution: 1920x1080~60Hz
  OpenGL: renderer: AMD Radeon RX 560 Series (polaris11 LLVM 15.0.5 DRM
    3.42 5.15.0-47-generic)
    v: 4.6 Mesa 23.1.0-devel (git-87a9018 2023-01-27 jammy-oibaf-ppa)
    direct render: Yes

Code: Select all

apt policy libglx-mesa0:i386 libgl1-mesa-dri:i386
libglx-mesa0:i386:
  Installed: 23.1~git2301270600.87a901~oibaf~j
  Candidate: 23.1~git2301270600.87a901~oibaf~j
  Version table:
 *** 23.1~git2301270600.87a901~oibaf~j 500
        500 http://ppa.launchpad.net/oibaf/graphics-drivers/ubuntu jammy/main i386 Packages
        100 /var/lib/dpkg/status
     22.0.5-0ubuntu0.3 500
        500 http://archive.ubuntu.com/ubuntu jammy-updates/main i386 Packages
     22.0.1-1ubuntu2 500
        500 http://archive.ubuntu.com/ubuntu jammy/main i386 Packages
libgl1-mesa-dri:i386:
  Installed: 23.1~git2301270600.87a901~oibaf~j
  Candidate: 23.1~git2301270600.87a901~oibaf~j
  Version table:
 *** 23.1~git2301270600.87a901~oibaf~j 500
        500 http://ppa.launchpad.net/oibaf/graphics-drivers/ubuntu jammy/main i386 Packages
        100 /var/lib/dpkg/status
     22.0.5-0ubuntu0.3 500
        500 http://archive.ubuntu.com/ubuntu jammy-updates/main i386 Packages
     22.0.1-1ubuntu2 500
        500 http://archive.ubuntu.com/ubuntu jammy/main i386 Packages

Code: Select all

apt list --installed |grep mesa
libegl-mesa0/jammy,now 23.1~git2301270600.87a901~oibaf~j amd64 [installed]
libegl-mesa0/jammy,now 23.1~git2301270600.87a901~oibaf~j i386 [installed]
libgl1-mesa-dri/jammy,now 23.1~git2301270600.87a901~oibaf~j amd64 [installed]
libgl1-mesa-dri/jammy,now 23.1~git2301270600.87a901~oibaf~j i386 [installed]
libglapi-mesa/jammy,now 23.1~git2301270600.87a901~oibaf~j amd64 [installed]
libglapi-mesa/jammy,now 23.1~git2301270600.87a901~oibaf~j i386 [installed]
libglu1-mesa/jammy,now 9.0.2-1 amd64 [installed]
libglx-mesa0/jammy,now 23.1~git2301270600.87a901~oibaf~j amd64 [installed]
libglx-mesa0/jammy,now 23.1~git2301270600.87a901~oibaf~j i386 [installed]
mesa-utils-bin/jammy,now 8.4.0-1ubuntu1 amd64 [installed]
mesa-utils/jammy,now 8.4.0-1ubuntu1 amd64 [installed]
mesa-va-drivers/jammy,now 23.1~git2301270600.87a901~oibaf~j amd64 [installed]
mesa-va-drivers/jammy,now 23.1~git2301270600.87a901~oibaf~j i386 [installed]
mesa-vdpau-drivers/jammy,now 23.1~git2301270600.87a901~oibaf~j amd64 [installed]
mesa-vdpau-drivers/jammy,now 23.1~git2301270600.87a901~oibaf~j i386 [installed]
mesa-vulkan-drivers/jammy,now 23.1~git2301270600.87a901~oibaf~j amd64 [installed]
mesa-vulkan-drivers/jammy,now 23.1~git2301270600.87a901~oibaf~j i386 [installed]

I then installed Steam using the command apt install steam-installer and had no problems but I don't have any games to test. I then removed Steam and installed the flatpak version of Steam with no problems

If it was me, I probably would do a fresh installation, since you stated that you tried adding the Kisak and Oibaf PPAs multiple times and I don't know what you did between each addition - nothing or did you try to remove it with a purge command or in another way, so some important file(s) may have gotten removed or something got mis-configured.

After a fresh installation, install all updates in Update Manager, the newer required kernel and firmware, create a Timeshift snapshot and then add the Oibaf PPA.

[SMG]

I added the Oibaf PPA and had no problems.

It might be because yours is a newer version. Maybe the issue has been corrected.
Mesa 23.1.0-devel (git-87a9018 2023-01-27 jammy-oibaf-ppa)

Here is Cykyrios's earlier inxi
OpenGL: renderer: AMD Radeon RX 7900 XT (gfx1100 LLVM 15.0.5 DRM 3.49
6.1.0-1004-oem)
v: 4.6 Mesa 23.1.0-devel (git-159edf7 2023-01-24 jammy-oibaf-ppa)
direct render: Yes

One reason oibaf can be problematic is because it is updated quite often (I've heard it can be as often as every 12 hours). That's one reason snapshots are really important with that PPA. While I highlighted the date, the git number would also be important to check when doing comparisons.

unless mesa drivers are updated in Mint packages and therefore kisak/oibaf PPAs become unnecessary

I just checked Lunar Lobster's version (the upcoming Ubuntu 23.04) and it is currently slated to be 22.2.5 so while I expect LM21 Mesa versions would be updated before it goes end of life, I doubt it will be new enough for your GPU for quite some time into the future.

[Cykyrios]

Thanks a lot for the further testing. Looking at this Reddit thread, I see that one thing I should have done is check the System Information popup from within Steam, which currently says this:

Code: Select all

Video Card:
    Driver:  AMD AMD Radeon Graphics (gfx1100, LLVM 15.0.7, DRM 3.49, 6.1.0-1004-oem)
    Driver Version:  4.6 (Compatibility Profile) Mesa 22.3.3 (git-08341a7b16)

while inxi -Fxxxrz outputs the following:

Code: Select all

  OpenGL: renderer: AMD Radeon RX 7900 XT (gfx1100 LLVM 15.0.5 DRM 3.49
  6.1.0-1004-oem)
    v: 4.6 Mesa 23.1.0-devel (git-87a9018 2023-01-27 jammy-oibaf-ppa)

The Mesa update from today brought it to the minimum supported version of 22.3 (or was it 22.2?) for the AMD 7900 XT/XTX cards, which is why it wouldn't work before.

I just checked Lunar Lobster's version (the upcoming Ubuntu 23.04) and it is currently slated to be 22.2.5 so while I expect LM21 Mesa versions would be updated before it goes end of life, I doubt it will be new enough for your GPU for quite some time into the future.

To be honest, I'm considering switching to a rolling release distribution such as Manjaro, at least for this specific hardware or until Mint updates to the next Ubuntu LTS base (24.04?), as the conflicts between mandatory very recent packages for the GPU and older distribution packages is likely to remain an issue here.

[SMG]

The Mesa update from today brought it to the minimum supported version of 22.3 (or was it 22.2?) for the AMD 7900 XT/XTX cards, which is why it wouldn't work before.

The GPU needs at least 22.2. Kisak is currently at 22.3 which meets that requirement.

I think I had 22.3 in my mind when I was checking the Ubuntu mesa packages. While Luna will be 22.2.5, Kinetic (Ubuntu 22.10) has 22.2.1 so technically there is already an Ubuntu release which meets the Mesa requirement.

Not sure if/when the Kinetic version might reach Jammy updates (which is what comes through to Linux Mint). There are some bug fixes related to certain AMD GPUs in the newer Mesas so I expect newer versions will be coming through, but I don't know when.

It sounds like Steam was the issue all along with regards to the GPU information being seen by Steam. The "(Compatibility Profile)" seems to indicate Steam is not directly using the GPU.

[SMG]

I just checked Lunar Lobster's version (the upcoming Ubuntu 23.04) and it is currently slated to be 22.2.5 so while I expect LM21 Mesa versions would be updated before it goes end of life, I doubt it will be new enough for your GPU for quite some time into the future.

To be honest, I'm considering switching to a rolling release distribution such as Manjaro, at least for this specific hardware or until Mint updates to the next Ubuntu LTS base (24.04?), as the conflicts between mandatory very recent packages for the GPU and older distribution packages is likely to remain an issue here.

Just wanted to let you know the Mesa version in LM21.1 is now 22.2.5.
(That didn't take nearly as long as I thought it would. )

[Cykyrios]

Thank you for the heads up, that is very good news!
I might have a try this weekend, but I will probably keep a rolling release distro on this computer, and use Mint for my other computer with less cutting-edge hardware.