Steam DXVK games can't be run on AMD Vulkan Driver from Proton 5.13-2

[Kai-AMD]

Compatibility Report

• Name of the game with compatibility issues: Wolfenstein II, Witcher3, Strange Brigade and ...
• Steam AppID of the game: 612880, 292030, 312670 and ...

System Information

• GPU: All AMD GPUs Supported
• Driver: AMDGPU-PRO 20.45 or open source AMDVLK v-2020.Q4.5 (Not Mesa/Radv)
• Kernel version: All Linux Kernel Supported
• Full system information: Ubuntu 20.04 + Kernel 5.4.0-53-generic
• Proton version: 5.13-2

I confirm:

• [*] that I haven't found an existing compatibility report for this game.
• [*] that I have checked whether there are updates for my system available.

Symptoms

DXVK games crash with 5.13-2, but pass with 5.0-10.

Crash info:
(1) Something regarding libGL error
(2) Something regarding VK_ERROR_EXTENSION_NOT_PRESENT error

The reason maybe OpenGL/Vulkan libraries (Loader and ICD) in /opt can NOT be accessed in game:

/opt/amdgpu-pro/lib/x86_64-linux-gnu/libGL.so.1.2
/opt/amdgpu-pro/lib/x86_64-linux-gnu/libGL.so -> libGL.so.1.2
/opt/amdgpu-pro/lib/x86_64-linux-gnu/libGL.so.1 -> libGL.so.1.2
/usr/lib/x86_64-linux-gnu/dri/amdgpu_dri.so
/opt/amdgpu/lib/x86_64-linux-gnu/dri/amdgpu_dri.so -> /usr/lib/x86_64-linux-gnu/dri/amdgpu_dri.so

/usr/lib/x86_64-linux-gnu/libvulkan.so.1.2.148
/usr/lib/x86_64-linux-gnu/libvulkan.so -> libvulkan.so.1
/usr/lib/x86_64-linux-gnu/libvulkan.so.1 -> libvulkan.so.1.2.148
/opt/amdgpu-pro/lib/x86_64-linux-gnu/amdvlk64.so

Issue can be workarounded by following steps:
(1) Add “PROTON_DUMP_DEBUG_COMMANDS=1 %command%” in the launch options
(2) Run game to generate a file called "run" at /tmp/proton_root
(3) Run with command “/tmp/proton_root/run”

Issue can also be workarounded by:
(1) Change the "library_path" in json file of AMD Vulkan ICD from "/opt/amdgpu-pro/lib/x86_64-linux-gnu/amdvlk64.so" to "/usr/lib/x86_64-linux-gnu/amdvlk64.so".
(2) Copy amdvlk64.so from /opt/amdgpu-pro/lib/x86_64-linux-gnu/ to /usr/lib/x86_64-linux-gnu/, then launch steam games.

Reproduction

(1) Install Ubuntu 20.04 64 bit OS
(2) Install AMDGPU-PRO 20.45 or set up open source AMDVLK v-2020.Q4.5
(3) Run DXVK steam games and see the crash

[kisak-valve]

Hello @Kai-AMD, this issue is already being tracked at #309 and https://gitlab.steamos.cloud/steamrt/steam-runtime-tools/-/issues/29. It should be fixed by the Steam Linux Runtime - Soldier 0.20201124.0 update.

If switching to the client_beta beta branch of Steam Linux Runtime - Soldier in Steam doesn't improve the situation, then please let me know and we can look at this issue further.

[Kai-AMD]

Hi @kisak-valve, by updating Steam Linux Runtime - Soldier to 0.20201124.0, the issue can still be reproduced.

[smcv]

Please show us a log of what pressure-vessel is thinking, and exactly what happens. You can do this without involving Proton like this:

cd /path/to/SteamLinuxRuntime_soldier
PRESSURE_VESSEL_VERBOSE=1 ./run -- steam-runtime-system-info --verbose 2>&1 | tee container.log

and then send container.log as a gist. You can edit/censor the log if there's anything in it that you consider private, as long as it's obvious where it has been edited, for instance replacing your username with REDACTED.

The SteamLinuxRuntime_soldier directory will be in one of your Steam libraries. The most likely place is ~/.local/share/Steam/steamapps/common/SteamLinuxRuntime_soldier if you haven't reconfigured the installation path.

[smcv]

Also please show us the system information (Help -> System Information in Steam). Again, you can edit/censor the log if you need to, and please send it as a gist.

[WenqingLiAMD]

Hi @smcv, please get the container.log and system info here:
https://gist.github.com/WenqingLiAMD/3736fad777675675cb85b0217557f271

[smcv]

Hi @smcv, please get the container.log and system info here:
https://gist.github.com/WenqingLiAMD/3736fad777675675cb85b0217557f271

OK. Outside the container, the amdvlk ICD is configured like this:

  "vulkan" : {
    "icds" : [
      {
        "json_path" : "/usr/share/vulkan/icd.d/amd_icd32.json",
        "library_path" : "/opt/amdgpu-pro/lib/i386-linux-gnu/amdvlk32.so",
        "api_version" : "1.2.139"
      },
      {
        "json_path" : "/usr/share/vulkan/icd.d/amd_icd64.json",
        "library_path" : "/opt/amdgpu-pro/lib/x86_64-linux-gnu/amdvlk64.so",
        "api_version" : "1.2.157"
      }
    ],

So we would expect each word-size to successfully load its own driver, and fail to load the other word-size's driver (64-bit games will fail to load amdvlk32.so but successfully load amdvlk64.so). This is similar to how Mesa works.

Inside the container, we rewrite the JSON to have different paths:

  "vulkan" : {
    "icds" : [
      {
        "json_path" : "/overrides/share/vulkan/icd.d/0-i386-linux-gnu.json",
        "library_path" : "/overrides/lib/i386-linux-gnu/vulkan/0/amdvlk32.so",
        "api_version" : "1.2.139"
      },
      {
        "json_path" : "/overrides/share/vulkan/icd.d/1-x86_64-linux-gnu.json",
        "library_path" : "/overrides/lib/x86_64-linux-gnu/vulkan/1/amdvlk64.so",
        "api_version" : "1.2.157"
      }
    ],

where /overrides/lib/i386-linux-gnu/vulkan/0/amdvlk32.so is a symbolic link to /opt/amdgpu-pro/lib/i386-linux-gnu/amdvlk32.so, and /overrides/lib/x86_64-linux-gnu/vulkan/1/amdvlk64.so is a symbolic link to /opt/amdgpu-pro/lib/x86_64-linux-gnu/amdvlk64.so.

The missing piece (I think) is that we should be mounting the actual drivers into /opt in the container, and we are not.

We might also need to mount /opt/amdgpu/share/libdrm/amdgpu.ids.

[smcv]

If you run Steam with the environment variable PRESSURE_VESSEL_FILESYSTEMS_RO=/opt/amdgpu:/opt/amdgpu-pro set, does that successfully work around this issue?

Note that it is not enough to put this variable in the Launch Options, because the container is created before the launch options take effect. You have to run something like PRESSURE_VESSEL_FILESYSTEMS_RO=/opt/amdgpu:/opt/amdgpu-pro steam.

Whether this works or not, but especially if it doesn't, a log captured like this

cd /path/to/SteamLinuxRuntime_soldier
PRESSURE_VESSEL_FILESYSTEMS_RO=/opt/amdgpu:/opt/amdgpu-pro \
PRESSURE_VESSEL_VERBOSE=1 \
./run -- steam-runtime-system-info --verbose 2>&1 | tee with-opt.log

would be useful.

[smcv]

If that workaround is successful, then I think https://gitlab.steamos.cloud/steamrt/steam-runtime-tools/-/merge_requests/192 should fix this.

[WenqingLiAMD]

Yes, the workaround works, log updated here: https://gist.github.com/WenqingLiAMD/3736fad777675675cb85b0217557f271#file-with-opt-log

[smcv]

Thanks! Use the workaround for now, but the next pressure-vessel release (next SteamLinuxRuntime_soldier beta) should make it unnecessary.

[Kai-AMD]

Hi @smcv, Thanks for fixing it. Could you please let me know which exact version of SteamLinuxRuntime_soldier will fix this issue? We will verify the fix :)