Closed JaydeepGo closed 3 years ago
Hello @JaydeepGo, I took a look at your system information and pressure vessel log and I don't see a fatal issue with the runtime container. This should be investigated on Proton's side.
Please add a comment to https://github.com/ValveSoftware/Proton/issues/3441 with the issue you're seeing. Make sure to note the last known working Proton version, and the current version. Also, please add PROTON_LOG=1 %command%
to the game's launch options and attach the generated $HOME/steam-$APPID.log to that issue report as a file. (Proton logs compress well if needed.)
And just after I wrote that I just noticed:
messages" : "*** stack smashing detected ***: terminated
timeout: the monitored command dumped core",
With 64 bit vulkan in the container. Not sure what to make of this, but it's worth holding this issue open to focus on that.
I think we'd need a backtrace from the crashing vulkaninfo
command to get anywhere with this.
It looks like Vulkan is working fine in the scout container runtime, but 64-bit vulkaninfo is crashing in the soldier container runtime, which is interesting. I wonder whether we're misdetecting some library as newer in the soldier runtime when it's actually older?
Hi @smcv @kisak-valve, Is there anything where I can help?
Is this a multi-GPU system, or is your only GPU the Intel integrated GPU?
If you're able to get a stack trace from the crashing vulkaninfo
command, perhaps by using systemd-coredump
, that might help to figure out what is going on. For example see https://wiki.archlinux.org/index.php/Core_dump#Examining_a_core_dump
Hi @smcv, This is a multi-GPU system (AMD+Intel hybrid).
The vulkaninfo
works fine outside of the container. For crashing vulkaninfo
logs are available in repo.
Please find all logs in debug-dump repo.
This is a multi-GPU system (AMD+Intel hybrid)
There's a known bug causing the Mesa device selection layer not to be loaded correctly inside the container. Presumably you were intending to be using the AMD GPU for games? The next beta of the Steam Linux Runtime will fix loading of the Mesa device selection layer, which should make it more likely that things like DKVK will get run on your AMD GPU as intended.
Workaround: try running Steam with VK_ICD_FILENAMES=/usr/share/vulkan/icd.d/radeon_icd.x86_64.json:/usr/share/vulkan/icd.d/radeon_icd.i686.json
in the environment, so the Intel Vulkan driver doesn't get loaded. At the moment, you need to have this set during Steam startup: setting it in Launch Options is too late.
Thanks @smcv, This prefix works. So after this prefix, all native steam game will also use AMD GPU?
VK_ICD_FILENAMES
will affect native Linux Steam games that use Vulkan, and Proton games that use DXVK. It won't affect games that use OpenGL.
The next beta of the Steam Linux Runtime will fix loading of the Mesa device selection layer, which should make it more likely that things like DKVK will get run on your AMD GPU as intended
This has now been released as a beta. Switching to the beta branch is the same as switching to the beta branch of a game, so please follow the same procedure as https://support.steampowered.com/kb_article.php?ref=9847-WHXC-7326, but in the properties of Steam Linux Runtime - soldier rather than CS:GO. You can see which specific versions you're using in SteamLinuxRuntime_soldier/VERSIONS.txt
.
For the issue I'm thinking of, the fix is in the pressure-vessel
component, and you want version 0.20210114.0 or later.
If you do that, and stop using the VK_ICD_FILENAMES
workaround, does it convince DXVK to use your AMD GPU?
If this doesn't help, please capture a new pressure-vessel log and new steam-runtime-system-info details. We've added an easier way to get a pressure-vessel log since you opened this bug: see https://github.com/ValveSoftware/steam-runtime/blob/master/doc/reporting-steamlinuxruntime-bugs.md#essential-information.
Hi @smcv, I have updated the SteamLinuxRuntime_soldier to beta but issue is still not resolved and now workaround also does not work.
I also try to new log method but there is no log in var/
.
Debug Logs
Hi @smcv, The Workaround: try running Steam with VK_ICD_FILENAMES=/usr/share/vulkan/icd.d/radeon_icd.x86_64.json:/usr/share/vulkan/icd.d/radeon_icd.i686.json
in the environment, so the Intel Vulkan driver doesn't get loaded, is not working anymore.
If you require more info please do tell.
Please get new debug info according to https://github.com/ValveSoftware/steam-runtime/blob/master/doc/reporting-steamlinuxruntime-bugs.md#essential-information, and attach it or upload it as a gist. Quite a lot has changed since you originally reported this, so we'll need new information to work out what is still not working.
Hi @smcv
Apologies for the late response. Please find the logs:
System Info
steam terminal
Coredump x86_64-linux-gnu-inspect-library & x86_64-linux-gnu-check-vulkan
I tried to run steam with STEAM_LINUX_RUNTIME_LOG=1 steam
but I can't find proton log in /var
.
Looking at your updated system information, it looks like 64 bit Vulkan is outright broken now. Is there a particular reason why amdvlk
was added, vulkan-intel
was removed, and nvidia-390xx
is on what appears to be an Intel-only system? I'm not asking for them to be changed, but tinkering with the installed drivers might give some insight.
Hi @kisak-valve, Thanks to pointing out about amdvlk
& nvidia-390xx
I have removed these packages and installed vulkan-intel
.
`64 bit Vulkan is outright broken now
I never notice these because I normal play Dota2 and CSGO. Here is the Updated System Info . Now the game is running without any tweaks, So good to close this bug. I have small doubt have can I check which GPU game is using when running via proton. I like to run the game via AMD driver.
Thanks for fixing the bug.
Hi @kisak-valve, Closing the issue as the bug is fixed.
System information
I have tested all proton version with game Temtem. It was working properly with proton 5.13 but it stops working yesterday. I even tried with the latest version of Steam Linux Runtime Soldier (client_beta).