Run through Bottles (flatpak) on Fedora Silverblue, AMD GPU, lutris-GE-Proton8-26
edit edit:
- 6.8.8-200.fc39.x86_64 #1 SMP PREEMPT_DYNAMIC
- Radeon RX 6700 XT
- amd-gpu-firmware-20240410-1.fc39.noarch
- amd-ucode-firmware-20240410-1.fc39.noarch
- xorg-x11-drv-amdgpu-23.0.0-2.fc39.x86_64
Neither bg3.exe nor bg3_dx11.exe launch the game for me, so I use the LariLauncher.exe.
- with DirectX11 the game starts but there are bad textures, including on the very first rendered screen.
- with Vulkan I get this error and the game crashes still at this loading screen.
The launcher complains about data mismatch but Heroic Launcher which I use to download my gog files apparently thinks it is fine. Although, the “Verify and Repair” button takes only couple of seconds.
Any ideas please?
I suggest avoiding the Vulkan build. It has been crashy in most BG3 releases, including the current one, I think.
For the dx11 build, you might get more help if you post your kernel and amdgpu firmware versions, GPU model, and screen shots showing the bad textures.
It’s also worth browsing the Proton comments to see if anyone else has encountered the same problems.
I will rather skip the Vulkan version then, thank you. I will update the post with version information but how do I learn the amdgpu firmware versions please?
Since you’re using Fedora Atomic, I’ll give you instructions for
rpm-ostree
:Run
rpm-ostree status
and find the deployment with the dot to the left of it. Example output:State: idle Deployments: ● fedora:fedora/40/x86_64/kinoite Version: 40.20240509.0 (2024-05-09T00:47:51Z) BaseCommit: 2f8263a33190c4e1320233aebbdc8f337b0a6abcba371d4870ae43fba33aea62 GPGSignature: Valid signature by 115DF9AEF857853EE8445D0A0727707EA15B79CC LayeredPackages: akmod-nvidia akmods asusctl asusctl-rog-gui libratbag-ratbagd mullvad-vpn rpmdevtools supergfxctl virt-manager xorg-x11-drv-nvidia LocalPackages: rpmfusion-free-release-40-1.noarch rpmfusion-nonfree-release-40-1.noarch fedora:fedora/40/x86_64/kinoite Version: 40.20240507.0 (2024-05-07T00:44:22Z) BaseCommit: c7fb680111ecf1736e473cf6f9169f69e5f2ec6b50814f7017bd6f9f3c1bdaf2 GPGSignature: Valid signature by 115DF9AEF857853EE8445D0A0727707EA15B79CC LayeredPackages: akmod-nvidia akmods asusctl asusctl-rog-gui libratbag-ratbagd mullvad-vpn rpmdevtools supergfxctl virt-manager xorg-x11-drv-nvidia LocalPackages: rpmfusion-free-release-40-1.noarch rpmfusion-nonfree-release-40-1.noarch
First one has a dot next to it, which means it’s the active version. Copy the value after “BaseCommit:” (in my case it is
2f8263a33190c4e1320233aebbdc8f337b0a6abcba371d4870ae43fba33aea62
)Run
rpm-ostree db list <paste commit hash here> | grep amd
. Example output (my command wasrpm-ostree db list 2f8263a33190c4e1320233aebbdc8f337b0a6abcba371d4870ae43fba33aea62 | grep amd
):In my case, running the most recent update on Fedora Atomic KDE, it looks like I’m running version 20240410-1 of
amd-gpu-firmware
. Yours may vary depending on what update you’re on.nice write up, thank you!
I don’t know Fedora, but I expect there’s a
dnf
command that would tell you what package owns the files in /lib/firmware/amdgpu . The version of that package would probably correspond to the upstream firmware version.Since they’re running Fedora Atomic, the commands are through
rpm-ostree
, asdnf
is disabled. I’ve provided the relevant instructions.