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

Linux Gaming

16393 readers
753 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?

top 50 comments
sorted by: hot top controversial new old
[–] Lomkey@lemmy.world 1 points 4 days ago

I see the system you got came with a 4070 if was the elite or was custom?, Not sure if you try to reinstall pop is? Unless someone said it all ready. Its very weird that your video card giving you problem should just work.

[–] zamithal@programming.dev 1 points 4 days ago

When I select proton-experimental as the version under force proton runtime, I actually see usage in rocm-smi, however I get a black screen or that weird "see behind my window effect I screenshotted" in another comment. When I let it choose, I can see the game but sit at 0% utilization.

[–] Uncut_Lemon@lemmy.world 2 points 5 days ago* (last edited 5 days ago)

NVTOP - terminal top-like app, works well for AMD GPU stats.

Mission Control - flatpak, windows task manager style process monitoring, shows GPU stats, much like windows.

MangoHUD, in game overlay, showing live fps, CPU and GPU usage

This are the 3 I tend to use to monitor my system performance

(If you running a Wayland powered desktop, that may be a source of issues. I've had issues that I dont experience in good old X. But that was some time ago. My 6800XT performs as well as I expect it to under windows. Running NVIDIA on Linux is generally a real chore, AMD has been plug and play for me)

[–] sith@lemmy.zip 1 points 5 days ago

Almost certainly the game isn't running on the GPU. Use rocm-smi to see which processes are using the discrete GPU. Should be similar to nvidia-smi.

Also, check the Proton status of your games at ProtonDB.

[–] FauxLiving@lemmy.world 1 points 5 days ago* (last edited 5 days ago) (1 children)

OP, I didn't see if you'd confirmed that you'd enable Steam Play, see this article: https://support.system76.com/articles/linux-gaming

Kerbal Space Program has a Linux native client and a windows client. By default, Steam will try to install the Linux native client, which is using OpenGL and, apparently, doing software rendering.

You could try to troubleshoot why OpenGL is broken, you probably are missing an environmental variable or something to tell it to use a specific device and so it defaults to software. However, this is kind of a moot point. Development stopped on OpenGL in 2017 and so bugs and weirdness will continue to crop up and fixing it won't resolve your core issue (Which may be that you're just not using Proton).

If you're going to game on this system then you should do what most people do and enable Steam Play and let Steam download the Windows version of KSP and run it through Proton (aka Steam's version of WINE). Often the Windows versions of games are more supported than the Linux native versions and WINE/Proton do an excellent job of translating the underlying windows system calls into Linux-ese. Proton is the primary reason why gaming on Linux works, because it lets you just play the Windows version of games.

Your logs indicate that your graphics card is the default device for Vulkan and so it should just work as soon as you enable Steam Play. If you have any problems with other games (once you verify that you're using your graphics card) you can look them up on Protondb (https://www.protondb.com/) and see if you need to make any setting changes. KSP looks to have a Gold rating and appears to work with Proton without any changes.

[–] zamithal@programming.dev 1 points 5 days ago* (last edited 5 days ago) (1 children)

So steam play was already enabled, it looks like it defaults to "steam Linux runtime 1.0 (scout). When I select different versions of proton runtime I get different behavior dependig on which one I select.

Proton 9 says that it cannot switch to my monitors resolution,

Proton experimental and hot fix launch the game (I can hear it!), but things are ... Weird. It only renders the windows behind it and the custom game cursor. When I alt enter to bring it into Windows mode, it's still just the windows/desktop that would be behind the game but now it's scaled differently.

EDIT:

It's hard to tell but the above screenshot is the game window

[–] FauxLiving@lemmy.world 1 points 5 days ago* (last edited 5 days ago) (1 children)

Stay with experimental for now.

Do other games show a similar behavior or is it limited to KSP?

BG3 should work fine (was just playing it on Linux about 30m ago, but Arch, btw, etc).

You can get some extra logging from steam, if you exit completely and the, in a terminal, run:

steam -d

It'll start Steam but output a lot of info to the terminal. The bit we're interested in isn't the stuff that it generates while Steam is starting. We want the bit that happens when you press play on a game. It'll output the information about the important bits (like the Vulkan device, driver versions, monitors, etc )

Make sure there's no obvious account info in the logs (there shouldn't be, but always check) and post that.

I'm off to bed but I'll check in with you tomorrow

[–] zamithal@programming.dev 1 points 4 days ago (1 children)

Well I've installed BG3 just for the sake of testing and the DX11 launch results in a black screen. The Vulkan launch options crashing immediately...

Here is my steam logs when launching KSP I think the only thing of interest is this:

pressure-vessel-wrap[42106]: W: "opt/amdgpu/share/libdrm" is unlikely to appear in "/run/host"
pressure-vessel-wrap[42106]: W: "opt/amdgpu/share/drirc.d" is unlikely to appear in "/run/host"
Adding process 42106 for gameID 220200
Adding process 42107 for gameID 220200
pressure-vessel-wrap[42106]: I: pv_runtime_provide_container_access: Setting up runtime without using bwrap
pressure-vessel-wrap[42106]: I: EGL ICD #0 at /usr/share/glvnd/egl_vendor.d/50_mesa.json: libEGL_mesa.so.0
pressure-vessel-wrap[42106]: I: Vulkan ICD #0 at /usr/share/vulkan/icd.d/intel_hasvk_icd.i686.json: /usr/lib/i386-linux-gnu/libvulkan_intel_hasvk.so
pressure-vessel-wrap[42106]: I: Vulkan ICD #1 at /usr/share/vulkan/icd.d/radeon_icd.x86_64.json: /usr/lib/x86_64-linux-gnu/libvulkan_radeon.so
pressure-vessel-wrap[42106]: I: Vulkan ICD #2 at /usr/share/vulkan/icd.d/intel_icd.x86_64.json: /usr/lib/x86_64-linux-gnu/libvulkan_intel.so
pressure-vessel-wrap[42106]: I: Vulkan ICD #3 at /usr/share/vulkan/icd.d/virtio_icd.i686.json: /usr/lib/i386-linux-gnu/libvulkan_virtio.so
pressure-vessel-wrap[42106]: I: Vulkan ICD #4 at /usr/share/vulkan/icd.d/intel_icd.i686.json: /usr/lib/i386-linux-gnu/libvulkan_intel.so
pressure-vessel-wrap[42106]: I: Vulkan ICD #5 at /usr/share/vulkan/icd.d/radeon_icd.i686.json: /usr/lib/i386-linux-gnu/libvulkan_radeon.so
pressure-vessel-wrap[42106]: I: Vulkan ICD #6 at /usr/share/vulkan/icd.d/intel_hasvk_icd.x86_64.json: /usr/lib/x86_64-linux-gnu/libvulkan_intel_hasvk.so
pressure-vessel-wrap[42106]: I: Vulkan ICD #7 at /usr/share/vulkan/icd.d/lvp_icd.i686.json: /usr/lib/i386-linux-gnu/libvulkan_lvp.so
pressure-vessel-wrap[42106]: I: Vulkan ICD #8 at /usr/share/vulkan/icd.d/virtio_icd.x86_64.json: /usr/lib/x86_64-linux-gnu/libvulkan_virtio.so
pressure-vessel-wrap[42106]: I: Vulkan ICD #9 at /usr/share/vulkan/icd.d/lvp_icd.x86_64.json: /usr/lib/x86_64-linux-gnu/libvulkan_lvp.so
pressure-vessel-wrap[42106]: I: Vulkan explicit layer #0 at /usr/share/vulkan/explicit_layer.d/VkLayer_INTEL_nullhw.json: libVkLayer_INTEL_nullhw.so
pressure-vessel-wrap[42106]: I: Vulkan explicit layer #1 at /usr/share/vulkan/explicit_layer.d/VkLayer_MESA_overlay.json: libVkLayer_MESA_overlay.so
pressure-vessel-wrap[42106]: I: Vulkan implicit layer #0 at /home/zamithal/.local/share/vulkan/implicit_layer.d/steamfossilize_i386.json: /home/zamithal/.steam/debian-installation/ubuntu12_32/libVkLayer_steam_fossilize.so
pressure-vessel-wrap[42106]: I: Vulkan implicit layer #1 at /home/zamithal/.local/share/vulkan/implicit_layer.d/steamfossilize_x86_64.json: /home/zamithal/.steam/debian-installation/ubuntu12_64/libVkLayer_steam_fossilize.so
pressure-vessel-wrap[42106]: I: Vulkan implicit layer #2 at /home/zamithal/.local/share/vulkan/implicit_layer.d/steamoverlay_i386.json: /home/zamithal/.steam/debian-installation/ubuntu12_32/steamoverlayvulkanlayer.so
pressure-vessel-wrap[42106]: I: Vulkan implicit layer #3 at /home/zamithal/.local/share/vulkan/implicit_layer.d/steamoverlay_x86_64.json: /home/zamithal/.steam/debian-installation/ubuntu12_64/steamoverlayvulkanlayer.so
pressure-vessel-wrap[42106]: I: Vulkan implicit layer #4 at /usr/share/vulkan/implicit_layer.d/VkLayer_MESA_device_select.json: libVkLayer_MESA_device_select.so
pressure-vessel-wrap[42106]: I: Capturing glvnd loadable module #0: /usr/share/glvnd/egl_vendor.d/50_mesa.json
pressure-vessel-wrap[42106]: I: Checking for implementation on x86_64-linux-gnu: libEGL_mesa.so.0
pressure-vessel-wrap[42106]: I: Captured glvnd loadable module #0: /usr/share/glvnd/egl_vendor.d/50_mesa.json
pressure-vessel-wrap[42106]: I: Implementation on x86_64-linux-gnu: SONAME
pressure-vessel-wrap[42106]: I: Capturing vulkan loadable module #0: /usr/share/vulkan/icd.d/intel_hasvk_icd.i686.json
pressure-vessel-wrap[42106]: I: Checking for implementation on x86_64-linux-gnu: /usr/lib/i386-linux-gnu/libvulkan_intel_hasvk.so
pressure-vessel-wrap[42106]: I: Capturing vulkan loadable module #1: /usr/share/vulkan/icd.d/radeon_icd.x86_64.json
pressure-vessel-wrap[42106]: I: Checking for implementation on x86_64-linux-gnu: /usr/lib/x86_64-linux-gnu/libvulkan_radeon.so
pressure-vessel-wrap[42106]: I: Capturing vulkan loadable module #2: /usr/share/vulkan/icd.d/intel_icd.x86_64.json
pressure-vessel-wrap[42106]: I: Checking for implementation on x86_64-linux-gnu: /usr/lib/x86_64-linux-gnu/libvulkan_intel.so
pressure-vessel-wrap[42106]: I: Capturing vulkan loadable module #3: /usr/share/vulkan/icd.d/virtio_icd.i686.json
pressure-vessel-wrap[42106]: I: Checking for implementation on x86_64-linux-gnu: /usr/lib/i386-linux-gnu/libvulkan_virtio.so
pressure-vessel-wrap[42106]: I: Capturing vulkan loadable module #4: /usr/share/vulkan/icd.d/intel_icd.i686.json
pressure-vessel-wrap[42106]: I: Checking for implementation on x86_64-linux-gnu: /usr/lib/i386-linux-gnu/libvulkan_intel.so
pressure-vessel-wrap[42106]: I: Capturing vulkan loadable module #5: /usr/share/vulkan/icd.d/radeon_icd.i686.json
pressure-vessel-wrap[42106]: I: Checking for implementation on x86_64-linux-gnu: /usr/lib/i386-linux-gnu/libvulkan_radeon.so
pressure-vessel-wrap[42106]: I: Capturing vulkan loadable module #6: /usr/share/vulkan/icd.d/intel_hasvk_icd.x86_64.json
pressure-vessel-wrap[42106]: I: Checking for implementation on x86_64-linux-gnu: /usr/lib/x86_64-linux-gnu/libvulkan_intel_hasvk.so
[–] FauxLiving@lemmy.world 1 points 4 days ago (1 children)

No errors, that's good and also not useful :/

As an aside, this is likely not the problem, but a good tip in general, is to use protonup to install GE-Proton (https://github.com/GloriousEggroll/proton-ge-custom). It is a community fork which essentially Proton Experimental + community fixes. The System76 article I linked above has the instructions (TL;DR, install protonup (terminal) or protonup-qt (GUI) and they'll grab it for you and put it in the right directory, restart Steam and select the new version from the Compatibility menu either globally or per-game).

You essentially always want to be using the latest version of Proton unless something that was working breaks in a newer version.

So, next step, more logs:

You can enable proton logging by setting PROTON_LOG=1 as an environmental variable. You can do this per-game by right clicking a game -> Properties -> General and editing the launch options to say

PROTON_LOG=1 %command%

Launch the game and let it crash or whatever. There will be a steam-$APPID.log in your home directory.

[–] zamithal@programming.dev 1 points 3 days ago* (last edited 3 days ago) (1 children)

Well, back at it again. Tried ProtonGE with the same results. But the vulkan logs are interesting!

cat ~/steam-220200.log | grep err

err:   Presenter: Failed to create Vulkan swapchain: VK_ERROR_INITIALIZATION_FAILED
err:   Presenter: Failed to create Vulkan swapchain: VK_ERROR_INITIALIZATION_FAILED
err:   Presenter: Failed to create Vulkan swapchain: VK_ERROR_INITIALIZATION_FAILED
err:   Presenter: Failed to create Vulkan swapchain: VK_ERROR_INITIALIZATION_FAILED
err:   Presenter: Failed to create Vulkan swapchain: VK_ERROR_INITIALIZATION_FAILED
err:   Presenter: Failed to create Vulkan swapchain: VK_ERROR_INITIALIZATION_FAILED

EDIT: more context

info:  Presenter: Actual swapchain properties:
info:    Format:       VK_FORMAT_B8G8R8A8_SRGB
info:    Color space:  VK_COLOR_SPACE_SRGB_NONLINEAR_KHR
info:    Present mode: VK_PRESENT_MODE_IMMEDIATE_KHR (dynamic: no)
info:    Buffer size:  1920x1080
info:    Image count:  4
err:   Presenter: Failed to create Vulkan swapchain: VK_ERROR_INITIALIZATION_FAILED

It's filled with this error. The entire log is massive I cant even upload it to pastebin. If you want me to search for something specific lmk or how I can supply the entire log.

EDIT2: also found:

99664.262:00d4:00d8:err:xrandr:xrandr14_get_adapters Failed to get adapters

99670.682:0180:0184:err:ole:com_get_class_object class {82c5ab54-c92c-4d52-aac5-27e25e22604c} not registered
99670.683:00e8:033c:warn:threadname:NtSetInformationThread Thread renamed to L"wine_rpcrt4_io"
99670.683:0180:0184:err:ole:create_server class {82c5ab54-c92c-4d52-aac5-27e25e22604c} not registered
99670.684:0180:0184:fixme:ole:com_get_class_object CLSCTX_REMOTE_SERVER not supported
99670.684:0180:0184:err:ole:com_get_class_object no class object {82c5ab54-c92c-4d52-aac5-27e25e22604c} could be created for context 0x15

[–] FauxLiving@lemmy.world 1 points 2 days ago (1 children)

99664.262:00d4:00d8:err:xrandr:xrandr14_get_adapters Failed to get adapters

Hmmm, this gets some hits. It seems like it isn't able to figure out which driver to use.

You can specify the driver that Vulkan should use by adding an environmental variable VK_ICD_FILENAME set the the json file for your card.

Try editing a game and changing the launch options to:

VK_ICD_FILENAMES=/usr/share/vulkan/icd.d/radeon_icd.x86_64.json %command%
[–] zamithal@programming.dev 1 points 2 days ago (1 children)

This removes that "Failed to get adapters" error from the proton log but the behavior remains the same and the VK_ERROR_INITIALIZATION_FAILED still persists

[–] FauxLiving@lemmy.world 1 points 2 days ago* (last edited 2 days ago) (1 children)

I just noticed my reply from my phone didn't go through x.x

This seems a lot like you're missing some 32bit libraries. There isn't a /usr/share/vulkan/icd.d/radeon_icd.i386.json listed in the vulkan logs.

I have no idea how they'd be named in PopOS, but I'd look into vulkan first. You may have the vulkan-radeon 64bit drivers , but not the 32bit. Wine needs the 32bit libraries for the time being.

Check

dpkg -l | grep vulkan

(or post all of dkpg -l if it isn't too long)

to see if you have the i386 version of the vulkan radeon drivers (for reference, in arch this is lib32-vulkan-radeon, possibly the same in PopOS)

If not install them (apt search vulkan and look for something with vulkan, radeon and i386 in the file name)

[–] zamithal@programming.dev 1 points 2 days ago (1 children)

looks like it is.

ii  libvulkan1:amd64                        1.3.280.0-1pop1~1722439676~22.04~a41a7d6                     amd64        Vulkan loader library
ii  libvulkan1:i386                         1.3.280.0-1pop1~1722439676~22.04~a41a7d6                     i386         Vulkan loader library
ii  mesa-vulkan-drivers:amd64               24.0.3-1pop1~1711635559~22.04~7a9f319                        amd64        Mesa Vulkan graphics drivers
ii  mesa-vulkan-drivers:i386                24.0.3-1pop1~1711635559~22.04~7a9f319                        i386         Mesa Vulkan graphics drivers
ii  vulkan-tools                            1.3.204.0+dfsg1-1                                            amd64        Miscellaneous Vulkan utilities
➜  ~ 

The whole log is too large for lemmy, but here is a pastebin link: https://pastebin.com/sxU2QYTc

System76 is advising I go full nuclear and reinstall from recovery partition, which I don't really think would fix anything and I'm hesitant to do.

[–] FauxLiving@lemmy.world 1 points 2 days ago (1 children)

Yeah, you have Vulkan and Mesa and the GPU drivers are in the kernel. That's the whole stack (along with Proton).

Before reinstalling completely, run a full system upgrade, I took this from system76s support page:

sudo apt update
# configure any packages partially setup 
sudo dpkg --configure -a 
# fix any missing package dependency 
sudo apt install -f 
# upgrade all packages and dependencies to newest in release 
sudo apt full-upgrade 
# make sure the `pop-desktop` meta package is installed 
sudo apt install pop-desktop

You're also likely using some flatpak applications, so:

flatpak update

Then reboot.

They want you to reinstall because walking you through a fresh install is just more time efficient for their support staff than trying to troubleshoot system configuration problems (imagine the possible things a random user could change x.x).

[–] zamithal@programming.dev 2 points 2 days ago (1 children)

Well, that didn't work so I proceeded with the fresh install.

It works right out of the box. No strange behavior and it's lightning fast. I'm both relieved to have it working and a little sad that the answer was "kill it with fire" as I've learned nothing.

Anyway, thank you for your help. :) Time to go get everything up again

[–] FauxLiving@lemmy.world 1 points 2 days ago (1 children)

Dude, the number of times I've resorted to a reinstall are innumerable. You know a bit more than you did yesterday and that isn't nothing.

If you want to try a new project that'll need tinkering with (but won't break your existing install) look at gamescope.

Currently it's the only way to get HDR and variable refresh rate to work. It's what Valve made to get those features into the Steamdeck.

You just run it with

gamescope -- %command%

In your steam launch options. You'll need to look up the options (otherwise it defaults to 720p@60hz). Ex:

gamescope -w 2160 -- %command%

For 4k. There's a switch for HDR too but I don't remember it without looking it up. You can use gamescope to enable FSR in any game, it can apply reshade shaders (so, things like anti aliasing in games that don't have it natively).

Other than that, any issues you have with a particular game can usually be solved by looking at protondb.com

Keep using the GE-Proton builds of proton for best results.

Have fun 🤓

[–] zamithal@programming.dev 2 points 2 days ago

Variable refresh rate is cool but 99% of my games are low res or 2d pixel art, so I haven't been too interested in HDR. Very cool though will tinker with it :)

[–] bitwolf@sh.itjust.works 2 points 6 days ago (2 children)

Curious. Do you have a "run on discrete GPU" option when you right click an app icon?

Iirc that feature is exposed on GNOME. Maybe you couldn't steam on discrete GPU option as a troubleshooting step?

That said I use both AMD cpu and GPU and it correctly defaults to the discrete GPU so this may not be the case

Even the IGPU should get better performance than that. I played Kerbal Space Program on a 2011 MacBook Air and got at least 30 fps.

[–] zamithal@programming.dev 1 points 6 days ago

I don't appear to have this.

[–] kybean@pawb.social 1 points 6 days ago

There's a program called amdgou_top you can use to see the breakdown of components on the GPU(s) and their utilization, as well as what apps are running on the GPU

[–] mox@lemmy.sdf.org 31 points 1 week ago* (last edited 1 week ago) (7 children)

AMD GPUs are usually the best pick for Linux, and the RX 7900 XT is capable of a lot better performance than 0-10 FPS. (It will vary by game, settings, and resolution, of course. You didn't mention the latter two.)

It's possible your games are using the CPU's integrated GPU instead of your graphics card. (Your iGPU is made for desktop use; it's not suitable for most gaming.) Do any of your underperforming games have a screen that shows which GPU they are using? Is your monitor plugged into the motherboard's video port, or one of the graphics card's ports? Does an overlay appear in the top left of the screen if you put DXVK_HUD=1 %command% in an underperforming game's Steam Launch Options?

It could also be that you don't have a recent enough kernel, firmware, or mesa/vulkan drivers installed for that fairly new GPU model.

Since you bought from System76, I would guess that they have support staff who can help make sure these things are set up properly. They even have their own Linux distro, which I think is pretty well regarded. Have you called them?

Is this as good as it gets?

No. Not even close.

EDIT: Added note about DXVK_HUD in Steam Launch Options

load more comments (7 replies)
[–] BaroqueInMind@lemmy.one 31 points 1 week ago (1 children)

What's the point of purchasing from System76 and pay that premium along with their warranty and not utilise it?

[–] zamithal@programming.dev 16 points 1 week ago

Fair point, I should do that.

[–] Evotech@lemmy.world 28 points 1 week ago (3 children)

Make sure you have your monitor plugged into the GPU, not the motherboard.

This kinda sounds like that

[–] zamithal@programming.dev 6 points 6 days ago

It's definitely plugged into the GPU. I've had plenty of opportunity to get acquainted with the back of my machine at this point. :,)

[–] Dark_Arc@social.packetloss.gg 2 points 6 days ago (1 children)

Yup really does sound like that. I had a friend make this mistake when we upgraded some components in his computer last summer I asked him to plug everything back in...

In his case there wasn't a GPU on the CPU so the computer wasn't booting to any image.

We spent way too much time in the case second guessing my work only for me to go around to the back of the computer and facepalm.

[–] zamithal@programming.dev 4 points 6 days ago (1 children)

Now i'm starting to doubt since this these responses have been so ubiquitous, but it's definitely not plugged into the motherboard's gpu slot. The motherboard has a single hdmi and displayport port. It, like all the other motherboard ports have a matte-black finish that matches the case. The displays are plugged into the glossy silver PCIE aligned hdmi and display ports, which doesn't match the rest of the case. The card is doublewide, occupying 2 pcie slots and is labeled "ASROCK".

[–] mox@lemmy.sdf.org 1 points 5 days ago* (last edited 5 days ago) (1 children)

I believe you've checked this correctly, but I want to clarify something: Even if the display is plugged into the graphics card, it's still possible that your CPU's integrated GPU (or even a CPU core) is being used for rendering, before sending the output to the display.

In other words, we've been asking where it's plugged in not because that would definitively pinpoint the problem, but because it could influence what's going on behind the scenes.

I hope System76 was able to help.

[–] zamithal@programming.dev 1 points 5 days ago

Gotcha, today is the first business day since filing my ticket. They've requested logs but no solutions yet.

load more comments (1 replies)
[–] Artyom@lemm.ee 26 points 1 week ago* (last edited 1 week ago) (1 children)

A 7900xt is like top 5 consumer graphics cards ever made at the moment, so 10 fps on a 15 year old game is not normal. I have the same card and just beat Control and Space Marines 2 with max settings with ray tracing and it constantly stayed above 100fps, with a vast majority of its time maxed at 144.

The first thing to do is to download CS2 and see where you're at with max graphics, you should get steady 144fps. If CS2 works, it's your games you're playing, check proton db and see if there is some common advice on settings/boot configs. Proton GE and Feral gamemode are two common tricks. There's also an option to trick games into thinking you're on a steamdeck that's becoming more common. If you see something unexpected with those configs, you may need to dig into your bios and make sure your card is behaving there, and there are some profiling tools for GPUs. You may have to update your drivers depending on your distro. Not all 7900 cards are the same, depending on the company designing the card's case, you may get different behavior on things like fans.

Their are some GUI tools that profile AMD GPUs, but I've found they don't show must more than sensors and lsusb show.

[–] zamithal@programming.dev 5 points 6 days ago (1 children)

Yeah it appears my card isn't being used at all, which explains the poor performance. Honestly the fact the system runs as well as it does without it is impressive. I'm reaching out to system76 for their diagnostics on why this might be

[–] Artyom@lemm.ee 9 points 6 days ago

A simple thing to check is did you plug your HDMI into the card or the motherboard? If it's in the motherboard, the card won't be used.

[–] Ulrich@feddit.org 25 points 1 week ago* (last edited 1 week ago) (2 children)

I didn't expect it to be able to play the latest and greatest games

I have a 6800xt and can play literally all of them. There's no reason you shouldn't be able to.

I kinda regret not going with Nvidia at this point

Nooooo that would be a mistake with Linux.

I'm getting between 0 and 10 fps on the title screen of Kerbal Space Program

KSP will run on a RPi. There's no reason you shouldn't be able to run the title screen. Something is very wrong.

My advice would be to contact System76.

Being that it's a pre built and preconfigured there's very little room for user error.

Did you enable Steam Play in Steam settings, under compatibility?

[–] zamithal@programming.dev 1 points 4 days ago (1 children)

Yeah I've tried several Steam Play options. I get different behavior from crashing to some wonky rendering of the windows behind it, but none work

[–] Ulrich@feddit.org 1 points 4 days ago (1 children)

There's only one Steam Play option.

[–] zamithal@programming.dev 1 points 4 days ago (1 children)

What do you mean? There are the following:

Proton experimental Steam Linux runtime 1.0 Legacy runtime 1.0 Proton hotfix Proton 9.0-4 ....

If you mean just the global checkbox, yes that's on

[–] Ulrich@feddit.org 1 points 4 days ago

If you mean just the global checkbox

Yes, the option that says "Steam Play".

load more comments (1 replies)
[–] tal@lemmy.today 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.

load more comments (16 replies)
load more comments
view more: next ›