Kind of funny that I’m not able to run PS1 games in RetroArch because of the Vulkan drama with my new card. I’ll wait it out. Are we looking at 1 year until this is in tip top shape? ;_;
1 Like
With my Gigabyte Gaming OC 9070 xt, I’ve seen transient spikes up to about 420w.
While you may be able to gimp the max power down, I’d still be weary of the transient spikes. Make sure your existing PSU has over current protection imo. Also, if your PSU is old / aged, it may not deliver the same levels of output as it did on day 1.
I had a 750w in my system, but I was too paranoid to run the card on it, so I waited for the new 850w I purchased and have since installed.
I have a 9070XT NITRO+ in an aircooling case (the torrent). Here’s what I’m running with in a stable manner:
Are you checking potondb for game specific tweaks?
At any rate the first thing I’d try is running with amdvlk drivers and default GPU settings, I’m having a better time with amdvlk than radv in Path of Exile 2 and Dragons Dogma 2 at least.
1 Like
I’m not overclocking, but i found my mem temps to reach & slightly exceed 90c which I was unhappy with. Here’s my fan setup:
This is causing the fans to come on way sooner and blast harder keeping the memory in check. Memory doesn’t exceed 80c which I’m happy with. This is on my Gigabyte Gaming OC 9070 xt.
Sure am. I’ve undervolted so far (no big performance drops really from that which is dope) but nothing seems to have helped really.
I’ve had it hang on browsers before though. It’s really hard to judge the cause so far. I really don’t think it’s a game specifically causing it, however it does happen more frequently under heavy load such as MH Wilds.
I switched to X11 qtile to see if maybe it’s weird stuff going on with wayland specifically or not. So far haven’t had any hangs since, but it’s only been a day so we’ll see.
I saw something the other day that I had no clue of, and I haven’t actually looked further into it to verify, but apparently Flatpaks pair their own Mesa drivers with them.
This explains why PCSX2 was inop for me until swapping to Nightly, and may explain your RetroArch issues.
1 Like
thx, yeah that would be too sketchy.
While I do have a “good” Leadex III, it is generationaly older and would probably not handle those transients nicely.
1 Like
If it’s been using duckstation as a backend or anything based on that it may just need and update, trying myself there and it was saying renderer not supported, but then i removed the older duckstation-git i had installed and tried a newer binary version and it worked, so may you may just need to update retroarch / the libretro backends. to get it working or just switch to opengl
It seems there are now some patches for the page flip timeout issues that are expected to land in 6.15-rc2.
drm/amd/display: Protect FPU in dml2_validate()/dml21_validate() (366e77cd)
drm/amd/display: Protect FPU in dml2_init()/dml21_init() (afcdf51d)
drm/amd/display: Protect FPU in dml21_copy() (4408b59e)
1 Like
Hello
I spent some time with some distros and finally tried Ubuntu 25.04 successfully, bundled with kernel 6.14 and mesa 25.
I still want to know why all the Linux distro’s that I have tried all do the same thing with the 9070(all KDE), I launch a game and the damn thing opens on the screen thats NOT set to primary, every time I reboot the PC I gotta do this for it keep games on the primary screen…
xrandr --listmonitors
then
xrandr --output DP-2 --primary
then all games use the primary screen until I need to restart again, seems like it might be a KDE issue, but I went on their forum and wrote a huge paragraph explaining it in detail and all I get are crickets.
Has anybody been able to run 7680x2160 @ 240hz?
I got the 57" samsung odyssey and I know the GPU can handle it because in Windows I can run the 240Hz refresh rate. When I switch to NixOS or KDE Neon and set the monitor OSD to 240Hz it gets locked down at 60Hz. When I set the monitor OSD to 120Hz it works on 120Hz normally within all linux environments.
It seems that the monitor OSD had another setting to switch the DP version. When I switched to DP 2.1 it loaded at 240Hz.
Yeah. I was using gamescope to address this, but now gamescope is broken for KDE lol. I’ll try your way and just make it a startup script.
I just wish someone would officially fix the problem, KDE forum just ignores me and so do most forums on different distros when bringing up the issue, it’s a problem thats only happening since i got the 9070. Could be a driver issue, but I think it’s a KDE issue or doesn’t seem to be a wayland issue as it happens switching to X11 also, im just not wanting to change to a different one since my UI will be drastically different.
have you tried putting the primary monitor on dp-1 instead of dp-2? just because 9070 seems to really care about the order in which monitors are plugged in.
For me at least, it doesn’t make a difference. (I have the same problem)
I have a new problem… ALL GAMES play for a short time and then the whole system freezes and I have to press the power button.
System Specs:
9600X
64gigs ram
9070(non XT)
All games and operating systems are using SATA(OS) and M.2 SSD’s(Games)
I tested these OS:
Garuda Linux – Kernel 6.14.2, MESA 25.0.4(KDE/Wayland) - entire system locks up within 10 minutes of starting a game and have to force it off with power button
OpenMandriva ROME Linux Kernel 6.14.2, MESA 25.0.4(KDE/Wayland) - entire system locks up within 10 minutes of starting a game and have to force it off with power button
Bazzite Linux Kernel 6.13.9, MESA 25.0.3(KDE/Wayland) - entire system locks up within 10 minutes of starting a game and have to force it off with power button
Windows 11 Pro(a custom stripped down bare bones version) - no issues, everything works.
I tested it in X11 and same problem, tested different monitors same problem…
I also took apart the whole PC and cleaned things out, re-seating all the cards, did a bios flash tot he newest version and reset it twice.
Changed all HDMI and DP cables to newer, faster versions
Also tried the monitors individually on HDMI and DP
None of that fixed the problem while windows is still working fine
There are no logs in Linux indicating why it’s locking up…
@hrts001 It doesn’t seem to matter on which order the monitors are plugged in it just uses the wrong one as primary still ignoring whats set in the monitors section, only thing thats been fixing that is to use only 1 monitor or force it with the xrandr --output DP-2 --primary(or whatever DP is supposed to be set as primary.
cant really speak for your exact problem as games for me on bazzite have generally run much better than on say fedora or cachyos but all 3 had some problem with multimonitor, in that if im running a game and i say have freetube open or alt-tab to change audio levels from system, it would either crash the screen the game is on, or all screens making them freeze for a moment before going black and turning off. this made me try bazzite which did that less often but still eventually did it. what fixed it for me was running the game in gamescope, so the only thing i can tell you to try if you have not already is gamescope and hopefully it helps.
as for your other problem, i have not really run into it in the same way on any of the linux installations i have. the worst that’s happened for me is that if settings are reset it would go back to defaulting on the monitor plugged into dp1. if you have not already you could try to set which monitor the game will run on via either gamescope or kde’s window rules. of course it’s a problem it’s happening at all, but can’t really figure out why you’re having that problem.