Problem with AMD drivers

cryptearth · 2024-08-10 13:32:04

lucernius wrote:

when i install steam, i press to install amdvlk and his lib )

amdvlk shows up first as its sorted alphabetical - but the better option is actually the mesa radv driver: (lib32-)vulkan-radeon
to switch first install (lib32-)vulkan-radeon and then remove (lib32-)amdvlk

https://wiki.archlinux.org/title/Vulkan
https://wiki.archlinux.org/title/AMDGPU

Last edited by cryptearth (2024-08-10 13:32:45)

seth · 2024-08-10 17:01:43

@luvernius, your OP says

when I launched a game, I was only getting 30 FPS for no apparent reason. It used to be 170 FPS

If "game" is your metric for the problem, how did you assess the situation before and after installing steam?

lucernius · 2024-08-10 17:08:07

If "game" is your metric for the problem, how did you assess the situation before and after installing steam?

I type in console and see this

❯ journalctl -p err -b
Aug 10 23:04:42 archhost kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.GP17.MP2], AE_NOT_FOUND (20240322/psargs-330)
Aug 10 23:04:42 archhost kernel: ACPI Error: Aborting method \_SB.GPIO._EVT due to previous error (AE_NOT_FOUND) (20240322/psparse-529)
Aug 10 23:04:43 archhost kernel: Bluetooth: hci0: No dsm support to set reset delay
Aug 10 23:04:43 archhost kernel: iwlwifi 0000:04:00.0: WRT: Invalid buffer destination
Aug 10 23:04:44 archhost kernel: iwlwifi 0000:04:00.0: WRT: Invalid buffer destination
Aug 10 23:04:44 archhost kernel: iwlwifi 0000:04:00.0: WRT: Invalid buffer destination
Aug 10 23:04:44 archhost kernel: Bluetooth: hci0: Malformed MSFT vendor event: 0x02
Aug 10 23:04:49 archhost kernel: iwlwifi 0000:04:00.0: Not associated and the session protection is over already...

So i think that the problem solved, but now I understand that this means nothing

I'll repeat, I am a new Arch Linux user and previously only had a week of experience with Ubuntu. But I really like this distribution and would like to continue exploring and working with it. I apologize for my inexperience.

Last edited by lucernius (2024-08-10 17:10:46)

seth · 2024-08-10 17:09:50

Post an updated journal, xorg log and output of

glxinfo -B
DRI_PRIME=pci-0000_03_00_0 glxinfo -B

lucernius · 2024-08-10 17:12:58

❯ glxinfo -B
DRI_PRIME=pci-0000_03_00_0 glxinfo -B
bash: glxinfo: command not found
bash: glxinfo: command not found

To avoid making mistakes, which specific drivers do I need to install?

seth · 2024-08-10 17:15:00

"pacman -F glxinfo" can tell you that it's part of mesa-utils

lucernius · 2024-08-10 17:25:37

❯ glxinfo -B

❯ glxinfo -B
DRI_PRIME=pci-0000_03_00_0 glxinfo -B
name of display: :0
display: :0  screen: 0
direct rendering: Yes
Extended renderer info (GLX_MESA_query_renderer):
    Vendor: AMD (0x1002)
    Device: AMD Radeon Graphics (radeonsi, renoir, LLVM 18.1.8, DRM 3.57, 6.10.3-zen1-2-zen) (0x1638)
    Version: 24.3.0
    Accelerated: yes
    Video memory: 512MB
    Unified memory: no
    Preferred profile: core (0x1)
    Max core profile version: 4.6
    Max compat profile version: 4.6
    Max GLES1 profile version: 1.1
    Max GLES[23] profile version: 3.2
Memory info (GL_ATI_meminfo):
    VBO free memory - total: 69 MB, largest block: 69 MB
    VBO free aux. memory - total: 7480 MB, largest block: 7480 MB
    Texture free memory - total: 69 MB, largest block: 69 MB
    Texture free aux. memory - total: 7480 MB, largest block: 7480 MB
    Renderbuffer free memory - total: 69 MB, largest block: 69 MB
    Renderbuffer free aux. memory - total: 7480 MB, largest block: 7480 MB
Memory info (GL_NVX_gpu_memory_info):
    Dedicated video memory: 512 MB
    Total available memory: 8196 MB
    Currently available dedicated video memory: 69 MB
OpenGL vendor string: AMD
OpenGL renderer string: AMD Radeon Graphics (radeonsi, renoir, LLVM 18.1.8, DRM 3.57, 6.10.3-zen1-2-zen)
OpenGL core profile version string: 4.6 (Core Profile) Mesa 24.3.0-devel (git-d330870f9c)
OpenGL core profile shading language version string: 4.60
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile

OpenGL version string: 4.6 (Compatibility Profile) Mesa 24.3.0-devel (git-d330870f9c)
OpenGL shading language version string: 4.60
OpenGL context flags: (none)
OpenGL profile mask: compatibility profile

OpenGL ES profile version string: OpenGL ES 3.2 Mesa 24.3.0-devel (git-d330870f9c)
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20

❯ DRI_PRIME=pci-0000_03_00_0 glxinfo -B

❯ DRI_PRIME=pci-0000_03_00_0 glxinfo -B
name of display: :0
Segmentation fault (core dumped)

xogr.log - https://0x0.st/XWAK.log
journal.log - https://0x0.st/XWAP.log

Lone_Wolf · 2024-08-10 17:53:01

[  1133.445] (++) Using config file: "/root/xorg.conf.new"

Please try starting X as normal user , instead of root .

Also remove all packages which name starts with xf86-video .

seth · 2024-08-10 18:00:12

There's like 100 boots in the journal, I just looked a the last one:

Aug 10 23:06:00 archhost kernel: amdgpu 0000:03:00.0: amdgpu: PSP create ring failed!
Aug 10 23:06:00 archhost kernel: amdgpu 0000:03:00.0: amdgpu: PSP resume failed
Aug 10 23:06:00 archhost kernel: [drm:amdgpu_device_fw_loading [amdgpu]] *ERROR* resume of IP block <psp> failed -62
Aug 10 23:06:00 archhost kernel: amdgpu 0000:03:00.0: amdgpu: amdgpu_device_ip_resume failed (-62).

But they all have

Aug 10 00:16:49 archhost kernel: amdgpu 0000:03:00.0: probe with driver amdgpu failed with error -22
Aug 10 01:00:30 archhost kernel: amdgpu 0000:03:00.0: probe with driver amdgpu failed with error -22
Aug 10 09:31:51 archhost kernel: amdgpu 0000:03:00.0: probe with driver amdgpu failed with error -22
Aug 10 09:33:05 archhost kernel: amdgpu 0000:03:00.0: probe with driver amdgpu failed with error -22
Aug 10 09:33:47 archhost kernel: amdgpu 0000:03:00.0: probe with driver amdgpu failed with error -22
Aug 10 11:16:24 archhost kernel: amdgpu 0000:03:00.0: probe with driver amdgpu failed with error -22
Aug 10 12:36:56 archhost kernel: amdgpu 0000:03:00.0: probe with driver amdgpu failed with error -22
Aug 10 12:37:32 archhost kernel: amdgpu 0000:03:00.0: probe with driver amdgpu failed with error -22
Aug 10 12:38:21 archhost kernel: amdgpu 0000:03:00.0: probe with driver amdgpu failed with error -22
Aug 10 12:39:19 archhost kernel: amdgpu 0000:03:00.0: probe with driver amdgpu failed with error -22
Aug 10 12:40:27 archhost kernel: amdgpu 0000:03:00.0: probe with driver amdgpu failed with error -22
Aug 10 12:42:36 archhost kernel: amdgpu 0000:03:00.0: probe with driver amdgpu failed with error -22
Aug 10 13:02:39 archhost kernel: amdgpu 0000:03:00.0: probe with driver amdgpu failed with error -22
Aug 10 13:10:32 archhost kernel: amdgpu 0000:03:00.0: probe with driver amdgpu failed with error -22
Aug 10 13:25:31 archhost kernel: amdgpu 0000:03:00.0: probe with driver amdgpu failed with error -22
Aug 10 13:48:45 archhost kernel: amdgpu 0000:03:00.0: probe with driver amdgpu failed with error -22
Aug 10 14:06:11 archhost kernel: amdgpu 0000:03:00.0: probe with driver amdgpu failed with error -22
Aug 10 14:14:59 archhost kernel: amdgpu 0000:03:00.0: probe with driver amdgpu failed with error -22
Aug 10 16:31:19 archhost kernel: amdgpu 0000:03:00.0: probe with driver amdgpu failed with error -22
Aug 10 17:18:31 archhost kernel: amdgpu 0000:03:00.0: probe with driver amdgpu failed with error -22
Aug 10 20:25:35 archhost kernel: amdgpu 0000:03:00.0: probe with driver amdgpu failed with error -22
Aug 10 20:31:54 archhost kernel: amdgpu 0000:03:00.0: probe with driver amdgpu failed with error -22
Aug 10 20:49:51 archhost kernel: amdgpu 0000:03:00.0: probe with driver amdgpu failed with error -22

The xorg log looks older

[  1133.364] (==) Log file: "/var/log/Xorg.0.log", Time: Sat Aug 10 13:44:21 2024
…
[  1133.445] (++) Using config file: "/root/xorg.conf.new"
[  1133.445] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[  1133.445] (==) ServerLayout "X.org Configured"
[  1133.445] (**) |-->Screen "Screen0" (0)
[  1133.445] (**) |   |-->Monitor "Monitor0"
[  1133.445] (**) |   |-->Device "Card0"
[  1133.445] (**) |-->Screen "Screen1" (1)
[  1133.445] (**) |   |-->Monitor "Monitor1"
[  1133.446] (**) |   |-->Device "Card1"
[  1133.446] (**) |-->Screen "Screen2" (2)
[  1133.446] (**) |   |-->Monitor "Monitor2"
[  1133.446] (**) |   |-->Device "Card2"
[  1133.446] (**) |-->Screen "Screen3" (3)
[  1133.446] (**) |   |-->Monitor "Monitor3"
[  1133.446] (**) |   |-->Device "Card3"
[  1133.446] (**) |-->Screen "Screen4" (4)
[  1133.446] (**) |   |-->Monitor "Monitor4"
[  1133.446] (**) |   |-->Device "Card4"
[  1133.446] (**) |-->Screen "Screen5" (5)
[  1133.446] (**) |   |-->Monitor "Monitor5"
[  1133.446] (**) |   |-->Device "Card5"
[  1133.446] (**) |-->Input Device "Mouse0"
[  1133.446] (**) |-->Input Device "Keyboard0"

Remove that config file, you're getting a bunch of errors and X11 fails to start.
Also NEVER! run ANY GUI session as root!

Then please boot some live distro (eg. grml) and check whether the 2nd GPU responds there.

lucernius · 2024-08-10 18:05:34

i dont know what u mean, that i run x11 with 'root'. Im create a new user with 'useradd' and give him a 'wheel'. Did i do something wrong?

seth · 2024-08-10 18:12:05

[  1133.445] (++) Using config file: "/root/xorg.conf.new"

The fact that the config is read out of that path implies that X11 was started as UID0, this has nothing to do w/ the wheel group.
You either logged in as root and started X11 or maybe ran "sudo startx"

lucernius · 2024-08-10 18:24:21

❯ startx

/usr/lib/Xorg.wrap: Only console users are allowed to run the X server
xinit: giving up
xinit: unable to connect to X server: Connection refused
xinit: server error
Couldn't get a file descriptor referring to the console.

seth · 2024-08-10 18:28:54

You're already running a GUI session…
In case you're running this through google translate, try https://deepl.com/

lucernius · 2024-08-10 18:34:34

You either logged in as root and started X11 or maybe ran "sudo startx"

But I'm not logged in as a root user or running anything. After login: archhost login, password. I only wrote Hyprland. I don't think I can break anything or run as root anymore.

seth · 2024-08-10 18:40:08

seth wrote:

You're already running a GUI session…

Wtf do you think Hyprland is?

Start an X11 session and post an updated Xorg log and the glxinfo outputs.

lucernius · 2024-08-10 18:59:52

I cant run 'startx' after logging

Heres log

[  1350.897] _XSERVTransSocketUNIXCreateListener: ...SocketCreateListener() failed
[  1350.897] 
X.Org X Server 1.21.1.13
X Protocol Version 11, Revision 0
[  1350.897] Current Operating System: Linux archhost 6.10.3-zen1-2-zen #1 ZEN SMP PREEMPT_DYNAMIC Tue, 06 Aug 2024 07:47:21 +0000 x86_64
[  1350.897] Kernel command line: BOOT_IMAGE=/vmlinuz-linux-zen root=UUID=4408879c-c27e-47bd-b89f-b5a29d7a3acc rw loglevel=3 quiet
[  1350.897]  
[  1350.897] Current version of pixman: 0.43.4
[  1350.897] 	Before reporting problems, check http://wiki.x.org
	to make sure that you have the latest version.
[  1350.897] Markers: (--) probed, (**) from config file, (==) default setting,
	(++) from command line, (!!) notice, (II) informational,
	(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[  1350.897] (==) Log file: "/var/log/Xorg.0.log", Time: Sun Aug 11 00:22:21 2024
[  1350.897] (II) Module ABI versions:
[  1350.897] 	X.Org ANSI C Emulation: 0.4
[  1350.897] 	X.Org Video Driver: 25.2
[  1350.897] 	X.Org XInput driver : 24.4
[  1350.897] 	X.Org Server Extension : 10.0
[  1350.898] (--) using VT number 2

[  1350.898] (II) systemd-logind: logind integration requires -keeptty and -keeptty was not provided, disabling logind integration
[  1350.898] (II) xfree86: Adding drm device (/dev/dri/card1)
[  1350.898] (II) Platform probe for /sys/devices/pci0000:00/0000:00:08.1/0000:06:00.0/drm/card1
[  1350.901] (--) PCI: (3@0:0:0) 1002:73df:1462:1316 rev 207, Mem @ 0xf800000000/17179869184, 0xfc00000000/268435456, 0xfcb00000/1048576, BIOS @ 0x????????/131072
[  1350.901] (--) PCI:*(6@0:0:0) 1002:1638:1462:1316 rev 196, Mem @ 0xfc20000000/268435456, 0xfc30000000/2097152, 0xfca00000/524288, I/O @ 0x0000f000/256
[  1350.901] List of video drivers:
[  1350.901] 	modesetting
[  1350.901] (II) LoadModule: "modesetting"
[  1350.901] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so
[  1350.913] (II) Module modesetting: vendor="X.Org Foundation"
[  1350.913] 	compiled for 1.21.1.13, module version = 1.21.1
[  1350.913] 	Module class: X.Org Video Driver
[  1350.913] 	ABI class: X.Org Video Driver, version 25.2
[  1350.913] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
[  1350.975] (++) Using config file: "/root/xorg.conf.new"
[  1350.975] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[  1350.975] (==) ServerLayout "X.org Configured"
[  1350.975] (**) |-->Screen "Screen0" (0)
[  1350.975] (**) |   |-->Monitor "Monitor0"
[  1350.976] (**) |   |-->Device "Card0"
[  1350.976] (**) |-->Screen "Screen1" (1)
[  1350.976] (**) |   |-->Monitor "Monitor1"
[  1350.976] (**) |   |-->Device "Card1"
[  1350.976] (**) |-->Input Device "Mouse0"
[  1350.976] (**) |-->Input Device "Keyboard0"
[  1350.976] (**) Allowing byte-swapped clients
[  1350.976] (==) Automatically adding devices
[  1350.976] (==) Automatically enabling devices
[  1350.976] (==) Automatically adding GPU devices
[  1350.976] (==) Automatically binding GPU devices
[  1350.976] (==) Max clients allowed: 256, resource mask: 0x1fffff
[  1350.976] (WW) The directory "/usr/share/fonts/misc" does not exist.
[  1350.976] 	Entry deleted from font path.
[  1350.976] (WW) The directory "/usr/share/fonts/OTF" does not exist.
[  1350.976] 	Entry deleted from font path.
[  1350.976] (WW) The directory "/usr/share/fonts/Type1" does not exist.
[  1350.976] 	Entry deleted from font path.
[  1350.976] (WW) The directory "/usr/share/fonts/misc" does not exist.
[  1350.976] 	Entry deleted from font path.
[  1350.976] (WW) The directory "/usr/share/fonts/OTF" does not exist.
[  1350.976] 	Entry deleted from font path.
[  1350.976] (WW) The directory "/usr/share/fonts/Type1" does not exist.
[  1350.976] 	Entry deleted from font path.
[  1350.976] (**) FontPath set to:
	/usr/share/fonts/TTF,
	/usr/share/fonts/100dpi,
	/usr/share/fonts/75dpi,
	/usr/share/fonts/TTF,
	/usr/share/fonts/100dpi,
	/usr/share/fonts/75dpi
[  1350.976] (**) ModulePath set to "/usr/lib/xorg/modules"
[  1350.976] (WW) Hotplugging is on, devices using drivers 'kbd', 'mouse' or 'vmmouse' will be disabled.
[  1350.976] (WW) Disabling Mouse0
[  1350.976] (WW) Disabling Keyboard0
[  1350.976] (EE) open /dev/dri/card0: No such file or directory
[  1350.976] (EE) open /dev/dri/card0: No such file or directory
[  1350.976] (WW) Falling back to old probe method for modesetting
[  1350.976] (EE) open /dev/dri/card0: No such file or directory
[  1350.976] (EE) open /dev/dri/card0: No such file or directory
[  1350.976] 
[  1350.976] 
Xorg detected your mouse at device /dev/input/mice.
Please check your config if the mouse is still not
operational, as by default Xorg tries to autodetect
the protocol.
[  1350.976] 
Xorg has configured a multihead system, please check your config.
[  1350.976] 
Your xorg.conf file is /root/xorg.conf.new

[  1350.976] To test the server, run 'X -config /root/xorg.conf.new'

[  1350.976] (EE) Server terminated with error (2). Closing log file.

seth · 2024-08-10 19:04:48

1. you're still running as root
2. /root/xorg.conf.new is still in place.

This is absolutely not going anywhere - consider a more beginner-friendly distro like ubuntu until you know your way around.

lucernius · 2024-08-10 19:15:00

Sorry dude, I just think you should always learn something new, and Windows and Ubuntu are no longer what I want to work on.

seth · 2024-08-10 20:09:13

You previously wrote:

I don`t expect to configure my GPU. I just want to use my computer normally (play games, watch videos, sharing discord screen and others) and that's it. I`m notice that my RTX 6700 didn`t work and my Ryzen GPU still working. I just wont that my 6700 start working normal
In short, I'd like to get a brief guide on what's good, what's bad, and what can be removed or kept in this system to avoid any issues.

But then start paying attention and using your brain - this is not going to work on autopilot.

lucernius · 2024-08-10 20:43:44

I hope i did all right https://0x0.st/XWaX.txt

startx
glxinfo -B; DRI_PRIME=pci-0000_03_00_0 glxinfo -B | curl -F 'file=@-' 0x0.st

Last edited by lucernius (2024-08-10 20:45:01)

seth · 2024-08-10 20:46:17

Idk - that's glxinfo, no DRI_PRIME (at least doesn't look like) and we lack a corresponding xorg log (which you're gonna look at first: make sure it doesn't load the static server config out of /root and also check "whoami" and make sure that doesn't say "root" either)

Edit:

(glxinfo -B; DRI_PRIME=pci-0000_03_00_0 glxinfo -B) | curl -F 'file=@-' 0x0.st

the braces are important, but if that's supposed to be w/ prime, your dedicated GPU doesn't seem to be available again. The X11 log will tell.

Last edited by seth (2024-08-10 20:47:50)

lucernius · 2024-08-10 20:47:24

http://0x0.st/XWam.0.log

seth · 2024-08-10 20:51:38

You're back to square one (because re-installing won't change anything about this) - the dedicated GPU is completely ignored and I bet your right arm it's because of the previous probing issues.

sudo journalctl -b | curl -F 'file=@-' 0x0.st

What exact model of a notebook is this?
(Vendor, product)?

lucernius · 2024-08-10 20:55:37

What exact model of a notebook is this?
(Vendor, product)?

MSI Delta-15-A5EFK

Does this make any sense? ( Xogr.0.log )

[    15.981] (II) LoadModule: "fbdev"
[    15.982] (WW) Warning, couldn't open module fbdev
[    15.982] (EE) Failed to load module "fbdev" (module does not exist, 0)
[    15.982] (II) LoadModule: "vesa"
[    15.982] (WW) Warning, couldn't open module vesa
[    15.982] (EE) Failed to load module "vesa" (module does not exist, 0)
[    15.982] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
[    15.982] (II) modeset(0): using drv /dev/dri/card1
[    15.982] (WW) VGA arbiter: cannot open kernel arbiter, no multi-card support
[    15.982] (II) modeset(0): Creating default Display subsection in Screen section

sudo journalctl -b | curl -F 'file=@-' 0x0.st

http://0x0.st/XWaa.bin

Last edited by lucernius (2024-08-10 20:56:06)

lucernius · 2024-08-10 21:06:12

and maybe this to

Aug 11 02:37:02 archhost kernel: [drm] amdgpu kernel modesetting enabled.
Aug 11 02:37:02 archhost kernel: amdgpu: vga_switcheroo: detected switching method \_SB_.PCI0.GP17.VGA_.ATPX handle
Aug 11 02:37:02 archhost kernel: amdgpu: ATPX version 1, functions 0x00000001
Aug 11 02:37:02 archhost kernel: amdgpu: ATPX Hybrid Graphics
Aug 11 02:37:02 archhost kernel: amdgpu: Virtual CRAT table created for CPU
Aug 11 02:37:02 archhost kernel: amdgpu: Topology: Add CPU node
Aug 11 02:37:02 archhost kernel: amdgpu 0000:03:00.0: enabling device (0000 -> 0002)
Aug 11 02:37:02 archhost kernel: [drm] initializing kernel modesetting (NAVY_FLOUNDER 0x1002:0x73DF 0x1462:0x1316 0xCF).
Aug 11 02:37:02 archhost kernel: [drm] register mmio base: 0xFCB00000
Aug 11 02:37:02 archhost kernel: [drm] register mmio size: 1048576
Aug 11 02:37:02 archhost kernel: [drm:amdgpu_discovery_set_ip_blocks [amdgpu]] *ERROR* amdgpu_discovery_init failed
Aug 11 02:37:02 archhost kernel: amdgpu 0000:03:00.0: amdgpu: Fatal error during GPU init
Aug 11 02:37:02 archhost kernel: amdgpu 0000:03:00.0: amdgpu: amdgpu: finishing device.
Aug 11 02:37:02 archhost kernel: amdgpu 0000:03:00.0: probe with driver amdgpu failed with error -22
Aug 11 02:37:02 archhost kernel: amdgpu 0000:06:00.0: enabling device (0006 -> 0007)
Aug 11 02:37:02 archhost kernel: [drm] initializing kernel modesetting (RENOIR 0x1002:0x1638 0x1462:0x1316 0xC4).

its looks like modset didnt suport multi-card and i should to delete him and install fdev or vesa, right?

Last edited by lucernius (2024-08-10 21:09:34)

Arch Linux

#26 2024-08-10 13:32:04

Re: Problem with AMD drivers

#27 2024-08-10 17:01:43

Re: Problem with AMD drivers

#28 2024-08-10 17:08:07

Re: Problem with AMD drivers

#29 2024-08-10 17:09:50

Re: Problem with AMD drivers

#30 2024-08-10 17:12:58

Re: Problem with AMD drivers

#31 2024-08-10 17:15:00

Re: Problem with AMD drivers

#32 2024-08-10 17:25:37

Re: Problem with AMD drivers

#33 2024-08-10 17:53:01

Re: Problem with AMD drivers

#34 2024-08-10 18:00:12

Re: Problem with AMD drivers

#35 2024-08-10 18:05:34

Re: Problem with AMD drivers

#36 2024-08-10 18:12:05

Re: Problem with AMD drivers

#37 2024-08-10 18:24:21

Re: Problem with AMD drivers

#38 2024-08-10 18:28:54

Re: Problem with AMD drivers

#39 2024-08-10 18:34:34

Re: Problem with AMD drivers

#40 2024-08-10 18:40:08

Re: Problem with AMD drivers

#41 2024-08-10 18:59:52

Re: Problem with AMD drivers

#42 2024-08-10 19:04:48

Re: Problem with AMD drivers

#43 2024-08-10 19:15:00

Re: Problem with AMD drivers

#44 2024-08-10 20:09:13

Re: Problem with AMD drivers

#45 2024-08-10 20:43:44

Re: Problem with AMD drivers

#46 2024-08-10 20:46:17

Re: Problem with AMD drivers

#47 2024-08-10 20:47:24

Re: Problem with AMD drivers

#48 2024-08-10 20:51:38

Re: Problem with AMD drivers

#49 2024-08-10 20:55:37

Re: Problem with AMD drivers

#50 2024-08-10 21:06:12

Re: Problem with AMD drivers

Board footer