Minor issue after trying multiple games, they all work mostly fine, some seem to just slow down to 20FPS or less and then lock the system up though.
Then another issue where games aren’t opening on the screen set to “primary” …they keep opening on the left 4k screen when primary is set to a 1440p ultrawide. Some game shave an in game setting to choose a monitor, thats not working either they just open on the left screen again…lol
LACT doesn’t work atm, but there is a new version here Release v0.7.2 · ilya-zlobintsev/LACT · GitHub that hopefully makes it in the repo soon since it supports the 9070 cards.
RDNA4 support! LACT now works on RX 9070 series GPUs with functional clocks settings, power limit and fan control.
For posterity, update to kernel-firmware was done, anyone should be able to get the 9070 working on openmandriva cooker with
sudo dnf distro-sync && sudo dracut --regenerate-all --force && sudo reboot
For new installs you might need to wait a few days so that the images are rebuilt with the latest firmware, make sure that the build date is 16/03/2025 or later to be 100% sure it has the latest fixes.
I’m making a PR for LACT right now: Update to 0.7.2 by Pingasmaster · Pull Request #4 · OpenMandrivaAssociation/lact · GitHub
If you can provide me the output of
dmesg | grep amdgpu
after the freezes happen, I could debug this a bit more, my bet is on an unoptimized / erroneous code in amdgpu. The driver is still maturing. Also, this may be due to something wine/proton related. Are the games you run windows games? Maybe wine needs a fix for them. Have you tried running them through steam with proton experimental? Also, do you run X11 or wayland? I bet its X11, multi output/display support on X11 is very much a hack, hence why it may fail especially on high refresh rates or weird (ultrawide) configurations.
Im on Wayland, I moved away from X11 a while ago, only use wayland
I resolved the weird monitor issue by re-arranging the screens, where they were plugged into the GPU, unplugged both and plugged the one I wanted primary in first in a different port and then the second one and then set them up again and now the issue seems resolved.
I play mostly Windows Games, one I was playing through Lutris, Star Wars Outlaws, it crashed and locked up as well as random slow downs dropping the FPS to below 20FPS. For UBISOFT games to work have to get Ubisoft Connect installed via Lutris, in Lutris I have it set up like this, using Proton GE 9-26 …because it allows me to configure wine to use Windows 11 Pro, Avatar Frontiers of Pandora runs perfectly, minor slow downs here and there but nothing like Outlaws. The games through steam are also windows games. Kingdom Come Deliverance 2 crashed once, but it’s been fine after that. Rise of the Ronin actually just runs like crap, but it runs like crap on Windows also so im going to chalk that up as just a bad port. Ghost of Tsushima crashes when Turning FSR on or frame gen.
Also nothing happens when entering dmesg | grep amdgpu or sudo modprobe amdgpu …butt he GPU is showing up.
Great stuff! I managed to update the system and now can use OpenMandriva again! Thanks for all the help!
Welp seems like these are issues that are wine and proton-related. You need to wait a bit for these issues to be ironed out on their side. If nothing shows when using dmesg | grep amdgpu then there is no error from the driver/firmware perspective, so it’s only going to be wine fixes that are then going to be ported to proton and solve these issues. Lact 7.2 has been merged so enjoy tweaking the GPU! You can help by reporting the Ghost of Tsushima FSR crash and Outlaws big slowdowns upstream: WineHQ Bugzilla – Search by bug number
This issue looks like its an X11 issue… because it is! Wine uses Xwayland and for now uses the X11 driver by default, but the wayland driver has been merged in 10.0 and will become the default next year in 11.0. Proton is always a few months behind, so you need to wait until 10.0 is backported (ideally, but you can still use this method on 9.0 although the driver is highly experimental) and then you can use this method to force wayland drivers to be used: How to use the new wayland driver on wine ? - WineHQ Forums. Your problem is due to X11/Xwayland having no monitor awareness in this case, hence why windows launch on the wrong screen.
