protonscr

Proton games don't run after removing and readding the GPU via /sys/pci

protonopen
ValveSoftware/Proton#6599 · opened 2023-03-06 by culturedrock · updated 2023-03-06 · 1 comments · github
Cculturedrock 2023-03-06 github

System Information

  • GPU: NVIDIA GTX 1080 + Intel HD Graphics 530
  • Driver/LLVM version: nvidia 525.89.02 + Mesa 22.3.5
  • Kernel version: 6.1.12.zen1-1 (Arch Linux)
  • Proton version: experimental-7.0-20230227 (and any other tested)

Symptoms

/sys interface and "replugging" it with PCI rescan until the next reboot (they work correctly otherwise).

Use case: I want to be able to use the dedicated NVIDIA GPU in a VM using VFIO and without rebooting. To this end, my base rendering in Xorg is done with integrated GPU, and for Steam and Steam games I'm using NVIDIA card through PRIME; so I only need to turn these apps off in order to be able to use the dGPU in a VM. To return the NVIDIA card back to the OS to use it with PRIME again, I am removing it through the /sys interface and issuing a rescan command. After doing so, rendering with PRIME works again for native apps (tested with Valheim), but Proton apps don't run correctly. Logs from an example run (tested with Noita) attached - steam-881100.log .

Reproduction

  1. Set up the OS so that it uses the Intel card for base rendering and use NVIDIA card through PRIME for Steam and Steam games.
  2. Remove the NVIDIA GPU and then rescan PCI:
# echo 1 > /sys/bus/pci/devices/0000:01:00.0/remove
# echo 1 > /sys/bus/pci/devices/0000:01:00.1/remove
# echo 1 > /sys/bus/pci/rescan
  1. Try to run any game using Proton, which should then fail to start.
Kkisak-valve maintainer 2023-03-06 github

Hello @culturedrock, please copy your system information from Steam (Steam -> Help -> System Information) and put it in a gist, then include a link to the gist in this issue report.

Steam should only gather the extended diagnostics once when you ask for the system information, and after you collect that information, it would be nice to know if any extended diagnostics details change if you restart Steam, then cause your manual hotplug to happen, and then check Steam's system information again. If before and after are identical, then there's no point in sharing a duplicate gist.

I suspect this is a video driver issue since this is fairly uncommon for users to do.

Nothing extracted yet.