this post was submitted on 16 Feb 2025
74 points (98.7% liked)

Linux Gaming

16413 readers
618 users here now

Discussions and news about gaming on the GNU/Linux family of operating systems (including the Steam Deck). Potentially a $HOME away from home for disgruntled /r/linux_gaming denizens of the redditarian demesne.

This page can be subscribed to via RSS.

Original /r/linux_gaming pengwing by uoou.

Resources

WWW:

Discord:

IRC:

Matrix:

Telegram:

founded 2 years ago
MODERATORS
 

I purchased a system76 Thelio Mira Elite With a AMD Radeon RX 7900 XT. I kinda regret not going with Nvidia at this point but it is what it is. I primarily use it as a developer workstation, but want to play games on it as well so I can be rid of my windows box.

I didn't expect it to be able to play the latest and greatest games but I did expect it to be able to play older titles reasonably well. Games launch from steam and seem to work, but I'm getting between 0 and 10 fps on the title screen of Kerbal Space Program. Other games are similarly functional but poorly performing.

Where do I start? How can I ensure my GPU is being leveraged? Is this as good as it gets?

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 12 points 1 week ago* (last edited 1 week ago) (16 children)

Games launch from steam and seem to work, but I’m getting between 0 and 10 fps on the title screen of Kerbal Space Program.

Something is definitely off on your system. I've a 7900 XTX (the slightly-higher-end version of that card), and while I don't have the box in front of me, it definitely runs at at least reasonable (60fps+) rates at 2560x1440 on KSP. Might do well above that, dunno. It's definitely not herky-jerky to the level you're seeing, though.

Are you using Wayland or Xorg?

If you run radeontop (in Debian trixie, package radeontop) it should tell you various load characteristics. There isn't a GPU-agnostic utility to do this, unless things have changed since last I've looked -- Nvidia and AMD both have their own utilities.

I kinda regret not going with Nvidia at this point

Unless you're aiming for AI stuff, where there are some significant benefits, like a large userbase and support for transformers, I'd probably recommend AMD for Linux use.

EDIT:

If you run glxinfo on either Xorg (or Wayland, since the emulation layer will handle it), package mesa-utils on Debian trixie, it'll tell you what OpenGL is trying to use. If you're using hardware-accelerated stuff, you'll get something like this:

Vendor: AMD (0x1002)
Device: AMD Radeon Graphics (radeonsi, gfx1103_r1, LLVM 19.1.4, DRM 3.59, 6.12.11-amd64) (0x1900)
OpenGL renderer string: AMD Radeon Graphics (radeonsi, gfx1103_r1, LLVM 19.1.4, DRM 3.59, 6.12.11-amd64)

That's been the quick-thumb-in-the-wind test to know whether hardware 3d acceleration is running since just about forever. KSP probably doesn't actually use OpenGL -- I'd guess that it's probably using DirectX going through some emulation layer in Proton to Vulkan -- but if you've got something wonky like no usable 3D driver support for your GPU, that'll show it up.

EDIT2: There's also vulkaninfo in (package vulkan-tools in Debian trixie). It'll give you something like:

GPU id : 0 (AMD Radeon Graphics (RADV GFX1103_R1)):

EDIT3: If you're using Xorg and that doesn't show hardware acceleration in use, then the next thing that I'd probably look at is /var/log/Xorg.0.log to see what Xorg is saying regarding your GPU. I don't know much about diagnosing Wayland issues, as I've not been using it for all that long. The kernel log may also have interesting messages information (as root, journalctl -kb or dmesg) if the problem is at the kernel level.

[–] [email protected] 5 points 1 week ago* (last edited 1 week ago) (13 children)

glxinfo | grep Vendor Vendor: Mesa (0xffffffff)

glxinfo | grep Device Device: llvmpipe (LLVM 17.0.6, 256 bits) (0xffffffff)

glxinfo | grep "OpenGL rend" OpenGL renderer string: llvmpipe (LLVM 17.0.6, 256 bits)

Let me know if that's not right. glxinfo dumps a lot of text but those are the only hits for your comment.

When I launch radeontop it prints this before launching, and then the output suggests it isn't working:

Unknown Radeon card. <= R500 won't work, new cards might.

All stats sit at 0.00% except for Memory Clock @ 9%.

EDIT:

xorg, not wayland

[–] [email protected] 8 points 1 week ago* (last edited 1 week ago) (3 children)

llvmpipe

Yeah, so it's not using hardware acceleration then -- your (poor) CPU has been trying to do all this in software emulation. I updated my comment above -- take a look in Xorg.0.log if you're on Xorg. My first guess is that you most-likely need newer drivers.

I know that these are new enough for the 7900 XTX; that's current for Debian trixie, just to provide a known-good point in terms of driver version.

$ dpkg -l|grep radeon
ii  libdrm-radeon1:amd64                                2.4.123-1                                 amd64        Userspace interface to radeon-specific kernel DRM services -- runtime
ii  libdrm-radeon1:i386                                 2.4.123-1                                 i386         Userspace interface to radeon-specific kernel DRM services -- runtime
ii  radeontop                                           1.4-2                                     amd64        Utility to show Radeon GPU utilization
ii  xserver-xorg-video-radeon                           1:22.0.0-1                                amd64        X.Org X server -- AMD/ATI Radeon display driver

EDIT: You don't say what distro you're using. If you're using Debian stable -- I think I was when I first got my 7900 XTX, and IIRC they didn't have driver support in at that point, though that was a while back now -- you might check whether you have the backports repository present.

EDIT2: The first results for my search as to minimum supported version, though I wouldn't take this as authoritative:

https://old.reddit.com/r/debian/comments/1301rph/radeon_7900_support/

Afaik 7900 needs preferably kernel 6.2+ and Mesa 23+.

EDIT3: Sorry, you did say which OS you were using -- PopOS.

[–] [email protected] 5 points 1 week ago* (last edited 1 week ago)

dpkg -l|grep radeon

ii  libdrm-amdgpu-radeon1:amd64             1:2.4.120.60103-1787201.22.04                                amd64        Userspace interface to radeon-specific kernel DRM services -- runtime
ii  libdrm-radeon1:amd64                    2.4.120-1pop1~1706792268~22.04~bfb54ee                       amd64        Userspace interface to radeon-specific kernel DRM services -- runtime
ii  libdrm-radeon1:i386                     2.4.120-1pop1~1706792268~22.04~bfb54ee                       i386         Userspace interface to radeon-specific kernel DRM services -- runtime
ii  radeontop                               1.4-1                                                        amd64        Utility to show Radeon GPU utilization
ii  xserver-xorg-video-radeon               1:19.1.0-2ubuntu1                                            amd64        X.Org X server -- AMD/ATI Radeon display driver

I don't know exactly what i'm looking for in the xorg logs... cat /var/log/Xorg.*.log | grep "EE"

cat /var/log/Xorg.*.log | grep "WW"

[  5068.047] (WW) Falling back to old probe method for modesetting
[  5068.047] (WW) Falling back to old probe method for fbdev

cat /var/log/Xorg.*.log | grep "gpu"

[  5067.696] (II) Applying OutputClass "AMDgpu" to /dev/dri/card1
[  5067.696] 	loading driver: amdgpu
[  5067.696] (==) Matched amdgpu as autoconfigured driver 0
[  5067.696] (II) LoadModule: "amdgpu"
[  5067.696] (II) Loading /usr/lib/xorg/modules/drivers/amdgpu_drv.so
[  5067.696] (II) Module amdgpu: vendor="X.Org Foundation"
	All GPUs supported by the amdgpu kernel driver

sudo journalctl -kb | grep gpu

Feb 15 08:59:51 pop-os kernel: [drm] amdgpu kernel modesetting enabled.
Feb 15 08:59:51 pop-os kernel: amdgpu: Virtual CRAT table created for CPU
Feb 15 08:59:51 pop-os kernel: amdgpu: Topology: Add CPU node
Feb 15 08:59:51 pop-os kernel: amdgpu 0000:03:00.0: enabling device (0006 -> 0007)
Feb 15 08:59:51 pop-os kernel: amdgpu 0000:03:00.0: amdgpu: Fetched VBIOS from VFCT
Feb 15 08:59:51 pop-os kernel: amdgpu: ATOM BIOS: 113-APM7199-002
Feb 15 08:59:51 pop-os kernel: amdgpu 0000:03:00.0: amdgpu: CP RS64 enable
Feb 15 08:59:51 pop-os kernel: amdgpu 0000:03:00.0: [drm:jpeg_v4_0_early_init [amdgpu]] JPEG decode is enabled in VM mode
Feb 15 08:59:51 pop-os kernel: amdgpu 0000:03:00.0: vgaarb: deactivate vga console
Feb 15 08:59:51 pop-os kernel: amdgpu 0000:03:00.0: amdgpu: Trusted Memory Zone (TMZ) feature not supported
Feb 15 08:59:51 pop-os kernel: amdgpu 0000:03:00.0: amdgpu: MEM ECC is not presented.
Feb 15 08:59:51 pop-os kernel: amdgpu 0000:03:00.0: amdgpu: SRAM ECC is not presented.
Feb 15 08:59:51 pop-os kernel: amdgpu 0000:03:00.0: amdgpu: VRAM: 16368M 0x0000008000000000 - 0x00000083FEFFFFFF (16368M used)
Feb 15 08:59:51 pop-os kernel: amdgpu 0000:03:00.0: amdgpu: GART: 512M 0x00007FFF00000000 - 0x00007FFF1FFFFFFF
Feb 15 08:59:51 pop-os kernel: [drm] amdgpu: 16368M of VRAM memory ready
Feb 15 08:59:51 pop-os kernel: [drm] amdgpu: 64286M of GTT memory ready.
Feb 15 08:59:51 pop-os kernel: [drm] GART: num cpu pages 131072, num gpu pages 131072
Feb 15 08:59:51 pop-os kernel: amdgpu 0000:03:00.0: amdgpu: Will use PSP to load VCN firmware
Feb 15 08:59:51 pop-os kernel: amdgpu 0000:03:00.0: amdgpu: reserve 0x1300000 from 0x83fc000000 for PSP TMR
Feb 15 08:59:51 pop-os kernel: amdgpu 0000:03:00.0: amdgpu: RAP: optional rap ta ucode is not available
Feb 15 08:59:51 pop-os kernel: amdgpu 0000:03:00.0: amdgpu: SECUREDISPLAY: securedisplay ta ucode is not available
Feb 15 08:59:51 pop-os kernel: amdgpu 0000:03:00.0: amdgpu: smu driver if version = 0x0000003d, smu fw if version = 0x00000040, smu fw program = 0, smu fw version = 0x004e7e00 (78.126.0)
Feb 15 08:59:51 pop-os kernel: amdgpu 0000:03:00.0: amdgpu: SMU driver if version not matched
Feb 15 08:59:51 pop-os kernel: amdgpu 0000:03:00.0: amdgpu: SMU is initialized successfully!
Feb 15 08:59:51 pop-os kernel: amdgpu 0000:03:00.0: [drm:jpeg_v4_0_hw_init [amdgpu]] JPEG decode initialized successfully.
Feb 15 08:59:51 pop-os kernel: amdgpu: HMM registered 16368MB device memory
Feb 15 08:59:51 pop-os kernel: kfd kfd: amdgpu: Allocated 3969056 bytes on gart
Feb 15 08:59:51 pop-os kernel: kfd kfd: amdgpu: Total number of KFD nodes to be created: 1
Feb 15 08:59:51 pop-os kernel: amdgpu: Virtual CRAT table created for GPU
Feb 15 08:59:51 pop-os kernel: amdgpu: Topology: Add dGPU node [0x744c:0x1002]
Feb 15 08:59:51 pop-os kernel: kfd kfd: amdgpu: added device 1002:744c
Feb 15 08:59:51 pop-os kernel: amdgpu 0000:03:00.0: amdgpu: SE 6, SH per SE 2, CU per SH 8, active_cu_number 80
Feb 15 08:59:51 pop-os kernel: amdgpu 0000:03:00.0: amdgpu: ring gfx_0.0.0 uses VM inv eng 0 on hub 0
Feb 15 08:59:51 pop-os kernel: amdgpu 0000:03:00.0: amdgpu: ring comp_1.0.0 uses VM inv eng 1 on hub 0
Feb 15 08:59:51 pop-os kernel: amdgpu 0000:03:00.0: amdgpu: ring comp_1.1.0 uses VM inv eng 4 on hub 0
Feb 15 08:59:51 pop-os kernel: amdgpu 0000:03:00.0: amdgpu: ring comp_1.2.0 uses VM inv eng 6 on hub 0
Feb 15 08:59:51 pop-os kernel: amdgpu 0000:03:00.0: amdgpu: ring comp_1.3.0 uses VM inv eng 7 on hub 0
Feb 15 08:59:51 pop-os kernel: amdgpu 0000:03:00.0: amdgpu: ring comp_1.0.1 uses VM inv eng 8 on hub 0
Feb 15 08:59:51 pop-os kernel: amdgpu 0000:03:00.0: amdgpu: ring comp_1.1.1 uses VM inv eng 9 on hub 0
Feb 15 08:59:51 pop-os kernel: amdgpu 0000:03:00.0: amdgpu: ring comp_1.2.1 uses VM inv eng 10 on hub 0
Feb 15 08:59:51 pop-os kernel: amdgpu 0000:03:00.0: amdgpu: ring comp_1.3.1 uses VM inv eng 11 on hub 0
Feb 15 08:59:51 pop-os kernel: amdgpu 0000:03:00.0: amdgpu: ring sdma0 uses VM inv eng 12 on hub 0
Feb 15 08:59:51 pop-os kernel: amdgpu 0000:03:00.0: amdgpu: ring sdma1 uses VM inv eng 13 on hub 0
Feb 15 08:59:51 pop-os kernel: amdgpu 0000:03:00.0: amdgpu: ring vcn_unified_0 uses VM inv eng 0 on hub 8
Feb 15 08:59:51 pop-os kernel: amdgpu 0000:03:00.0: amdgpu: ring vcn_unified_1 uses VM inv eng 1 on hub 8
Feb 15 08:59:51 pop-os kernel: amdgpu 0000:03:00.0: amdgpu: ring jpeg_dec uses VM inv eng 4 on hub 8
Feb 15 08:59:51 pop-os kernel: amdgpu 0000:03:00.0: amdgpu: ring mes_kiq_3.1.0 uses VM inv eng 14 on hub 0
Feb 15 08:59:51 pop-os kernel: amdgpu 0000:03:00.0: amdgpu: Using BACO for runtime pm
Feb 15 08:59:51 pop-os kernel: [drm] Initialized amdgpu 3.57.0 20150101 for 0000:03:00.0 on minor 2
Feb 15 08:59:51 pop-os kernel: fbcon: amdgpudrmfb (fb0) is primary device
Feb 15 08:59:51 pop-os kernel: amdgpu 0000:03:00.0: [drm] fb0: amdgpudrmfb frame buffer device
Feb 15 08:59:52 pop-os kernel: RAPL PMU: hw unit of domain pp1-gpu 2^-14 Joules
Feb 15 08:59:52 pop-os kernel: snd_hda_intel 0000:03:00.1: bound 0000:03:00.0 (ops amdgpu_dm_audio_component_bind_ops [amdgpu])
...
load more comments (2 replies)
load more comments (11 replies)
load more comments (13 replies)