You are not logged in.
After not running Steam for a while (around 2 weeks), I'm finding that I can't run Windows games through Proton any more (all my native ones run fine). My system is up to date (yay -Syu). I'm normally using https://aur.archlinux.org/packages/proton-ge-custom-bin but the same issue remains after switching to a different Proton version (I've tried Experimental, 7.0, and 5.13).
Details (from inxi -F):
CPU:
Info: 8-core model: AMD Ryzen 7 4800H with Radeon Graphics bits: 64
Graphics:
Device-1: NVIDIA TU117M [GeForce GTX 1650 Ti Mobile] driver: nvidia
v: 535.54.03
Device-2: AMD Renoir driver: amdgpu v: kernel
Using prime-run glxinfo, I'm getting the correct renderer string:
OpenGL renderer string: NVIDIA GeForce GTX 1650 Ti/PCIe/SSE2
Everything outside Proton seems to be running fine. Reinstalling proton-ge-custom-bin doesn't help, neither does cleaning Steam's shader cache. The command I'm running my games in Steam is just prime-run %command% and has worked correctly before.
This is a typical log file (obtained by appending PROTON_LOG=1 to launch options) from Neon Abyss, I'm getting very similar output from all my Proton-launched games: https://pastebin.com/ETp7VPnp, where in all cases the logs contain lines similar to these:
11812.754:00cc:00d0:err:winediag:nodrv_CreateWindow Application tried to create a window, but no driver could be loaded.
11812.754:00cc:00d0:err:winediag:nodrv_CreateWindow L"Make sure that your X server is running and that $DISPLAY is set correctly."
Steam runtime diagnostics: https://hastebin.com/share/muhewowido.php
Please advise.
Last edited by mindbound (2023-07-19 20:31:35)
Offline
Yesterday I tried launching a proton-based game from steam and it opened a black screen. I could still hear the audio of the menu after it loaded but I couldn’t see or interact with it. I tried setting the game up through Lutris instead and at the point Lutris tried to create a wine prefix, there was a popup from wine that was blacked out the same way, which made me think I started having wine issues.
I update daily and the game was working fine two days ago. I rolled back all my updates to two days ago, but it didn’t appear to make a difference.
The PROTON_LOG is very full after launching a game, so I am not sure what to look for inside of it.
Offline
There was something similar when having unnecessary not working vulkan layers installed a while ago in standard wine. Is the amdgpu active for an actual purpose? Can you post your xorg log and
vulkaninfo --summary #vulkantools
Offline
The amdgpu is active for "regular" usage, I run my games and other GPU-intensive programs using prime-run.
Xorg.0.log: https://pastebin.com/bQm6Akxb
vulkaninfo --summary output:
==========
VULKANINFO
==========
Vulkan Instance Version: 1.3.255
Instance Extensions: count = 21
-------------------------------
VK_EXT_acquire_drm_display : extension revision 1
VK_EXT_acquire_xlib_display : extension revision 1
VK_EXT_debug_report : extension revision 10
VK_EXT_debug_utils : extension revision 2
VK_EXT_direct_mode_display : extension revision 1
VK_EXT_display_surface_counter : extension revision 1
VK_KHR_device_group_creation : extension revision 1
VK_KHR_display : extension revision 23
VK_KHR_external_fence_capabilities : extension revision 1
VK_KHR_external_memory_capabilities : extension revision 1
VK_KHR_external_semaphore_capabilities : extension revision 1
VK_KHR_get_display_properties2 : extension revision 1
VK_KHR_get_physical_device_properties2 : extension revision 2
VK_KHR_get_surface_capabilities2 : extension revision 1
VK_KHR_portability_enumeration : extension revision 1
VK_KHR_surface : extension revision 25
VK_KHR_surface_protected_capabilities : extension revision 1
VK_KHR_wayland_surface : extension revision 6
VK_KHR_xcb_surface : extension revision 6
VK_KHR_xlib_surface : extension revision 6
VK_LUNARG_direct_driver_loading : extension revision 1
Instance Layers: count = 18
---------------------------
VK_LAYER_INTEL_nullhw INTEL NULL HW 1.1.73 version 1
VK_LAYER_KHRONOS_validation Khronos Validation Layer 1.3.250 version 1
VK_LAYER_LUNARG_api_dump LunarG API dump layer 1.3.250 version 2
VK_LAYER_LUNARG_monitor Execution Monitoring Layer 1.3.250 version 1
VK_LAYER_LUNARG_screenshot LunarG image capture layer 1.3.250 version 1
VK_LAYER_MANGOAPP_overlay Mangoapp Layer 1.3.0 version 1
VK_LAYER_MANGOHUD_overlay_x86_64 Vulkan Hud Overlay 1.3.0 version 1
VK_LAYER_MESA_device_select Linux device selection layer 1.3.211 version 1
VK_LAYER_MESA_overlay Mesa Overlay layer 1.3.211 version 1
VK_LAYER_NV_optimus NVIDIA Optimus layer 1.3.242 version 1
VK_LAYER_RENDERDOC_Capture Debugging capture layer for RenderDoc 1.3.131 version 27
VK_LAYER_TORKEL104_libstrangle Libstrangle framerate limiter 1.1.125 version 1
VK_LAYER_VALVE_steam_fossilize_32 Steam Pipeline Caching Layer 1.3.207 version 1
VK_LAYER_VALVE_steam_fossilize_64 Steam Pipeline Caching Layer 1.3.207 version 1
VK_LAYER_VALVE_steam_overlay_32 Steam Overlay Layer 1.3.207 version 1
VK_LAYER_VALVE_steam_overlay_64 Steam Overlay Layer 1.3.207 version 1
VK_LAYER_VKBASALT_post_processing a post processing layer 1.3.223 version 1
VK_LAYER_VKBASALT_post_processing a post processing layer 1.3.223 version 1
Devices:
========
GPU0:
apiVersion = 1.3.242
driverVersion = 535.54.3.0
vendorID = 0x10de
deviceID = 0x1f95
deviceType = PHYSICAL_DEVICE_TYPE_DISCRETE_GPU
deviceName = NVIDIA GeForce GTX 1650 Ti
driverID = DRIVER_ID_NVIDIA_PROPRIETARY
driverName = NVIDIA
driverInfo = 535.54.03
conformanceVersion = 1.3.5.0
deviceUUID = 122adb08-4280-7f1b-51de-776b5df42297
driverUUID = 8b72f8cf-fcf7-59af-b250-edf6b04fc087
GPU1:
apiVersion = 1.3.246
driverVersion = 0.0.1
vendorID = 0x10005
deviceID = 0x0000
deviceType = PHYSICAL_DEVICE_TYPE_CPU
deviceName = llvmpipe (LLVM 15.0.7, 256 bits)
driverID = DRIVER_ID_MESA_LLVMPIPE
driverName = llvmpipe
driverInfo = Mesa 23.1.3 (LLVM 15.0.7)
conformanceVersion = 1.3.1.1
deviceUUID = 6d657361-3233-2e31-2e33-000000000000
driverUUID = 6c6c766d-7069-7065-5555-494400000000
It could potentially be related to this issue, where I'm unable to start any programs using regular Wine.
Last edited by mindbound (2023-07-07 14:43:51)
Offline
Get rid of vulkan-swrast and try removing xf86-video-amdgpu and rebooting/restarting xorg.
Last edited by V1del (2023-07-07 18:47:21)
Offline
Removed vulkan-swrast, nothing has changed in terms of not being able to run Proton. Removing xf86-video-amdgpu makes Xorg fail to start, which I expected since the integrated AMD GPU is configured as the default one. That has never caused any trouble for me, though.
Offline
It shouldn't fail to start xorg unless you manually configured something . The default modesetting driver should kick in in that case and drive the amdgpu output. xf86-video-amdgpu has recently come up with causing some weird issues.
Last edited by V1del (2023-07-07 22:07:17)
Offline
I have manually configured amdgpu modules and settings but the last time I made any changes was almost a year ago, while this issue started only a few weeks ago. Do you think it makes sense to remove the AMDGPU drivers? The issue seems to be specific to Proton and Wine, everything else runs normally, including native games.
Offline
Which is why I mentioned the issues started recently, this is about trying to rule out what causes the problem, it should be trivial to move the corresponding files out of the way temporarily and move them back after if it doesn't fix the problem. To complete the potential vulkan interference (there was a thread with this coming up but with the intel side, though I'm not finding that one of the top of my head) maybe install vulkan-radeon/lib32-vulkan-radeon so the amdgpu can technically provide a vulkan renderer as well.
FWIW there's this thread and post https://bbs.archlinux.org/viewtopic.php … 5#p2084725 where an incompletely/incorrectly defined xorg.conf lead to issues with wine. So maybe post those config files
Last edited by V1del (2023-07-08 01:07:03)
Offline
Right, makes sense.
So, I have in /etc/X11/xorg.conf.d/20-amdgpu.conf:
Section "Device"
Identifier "AMD"
Driver "amdgpu"
Option "DRI" "3"
EndSection
Section "OutputClass"
Identifier "AMD"
MatchDriver "amdgpu"
Driver "amdgpu"
EndSection
At the moment, I think this is everything I have configured manually.
Offline
Removing xf86-video-amdgpu and switching to modesetting driver doesn't seem to change anything.
Offline
You appear to have 2 videocards, an amdgpu an a nivdia one. The vulkaninfo output doesn't show a driver for the amd card which can cause all kinds of problems.
Please post the full output of
$ lspci -k
$ pacman -Qs vulkan
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
I currently don't have a Vulkan driver for the AMD (integrated) card. Should I install it?
Output from `lspci -k`:
00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir/Cezanne Root Complex
Subsystem: Lenovo Renoir/Cezanne Root Complex
Kernel driver in use: ryzen_smu
lspci: Unable to load libkmod resources: error -2
00:00.2 IOMMU: Advanced Micro Devices, Inc. [AMD] Renoir/Cezanne IOMMU
Subsystem: Lenovo Renoir/Cezanne IOMMU
00:01.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir PCIe Dummy Host Bridge
00:01.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Renoir PCIe GPP Bridge
Subsystem: Lenovo Renoir PCIe GPP Bridge
Kernel driver in use: pcieport
00:01.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] Renoir/Cezanne PCIe GPP Bridge
Subsystem: Lenovo Renoir/Cezanne PCIe GPP Bridge
Kernel driver in use: pcieport
00:02.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir PCIe Dummy Host Bridge
00:02.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Renoir/Cezanne PCIe GPP Bridge
Subsystem: Lenovo Renoir/Cezanne PCIe GPP Bridge
Kernel driver in use: pcieport
00:02.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] Renoir/Cezanne PCIe GPP Bridge
Subsystem: Lenovo Renoir/Cezanne PCIe GPP Bridge
Kernel driver in use: pcieport
00:08.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir PCIe Dummy Host Bridge
00:08.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Renoir Internal PCIe GPP Bridge to Bus
Subsystem: Advanced Micro Devices, Inc. [AMD] Renoir Internal PCIe GPP Bridge to Bus
Kernel driver in use: pcieport
00:08.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] Renoir Internal PCIe GPP Bridge to Bus
Subsystem: Advanced Micro Devices, Inc. [AMD] Renoir Internal PCIe GPP Bridge to Bus
Kernel driver in use: pcieport
00:14.0 SMBus: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller (rev 51)
Subsystem: Lenovo FCH SMBus Controller
Kernel driver in use: piix4_smbus
00:14.3 ISA bridge: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge (rev 51)
Subsystem: Lenovo FCH LPC Bridge
00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir Device 24: Function 0
00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir Device 24: Function 1
00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir Device 24: Function 2
00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir Device 24: Function 3
Kernel driver in use: k10temp
00:18.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir Device 24: Function 4
00:18.5 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir Device 24: Function 5
00:18.6 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir Device 24: Function 6
00:18.7 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir Device 24: Function 7
01:00.0 VGA compatible controller: NVIDIA Corporation TU117M [GeForce GTX 1650 Ti Mobile] (rev a1)
Subsystem: Lenovo TU117M [GeForce GTX 1650 Ti Mobile]
Kernel driver in use: nvidia
01:00.1 Audio device: NVIDIA Corporation Device 10fa (rev a1)
Subsystem: NVIDIA Corporation Device 10fa
Kernel driver in use: snd_hda_intel
02:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller 980
Subsystem: Samsung Electronics Co Ltd NVMe SSD Controller 980
Kernel driver in use: nvme
03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 15)
DeviceName: Realtek RTL8111E Ethernet LOM
Subsystem: Lenovo RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
Kernel driver in use: r8169
04:00.0 Network controller: Intel Corporation Wi-Fi 6 AX200 (rev 1a)
Subsystem: Intel Corporation Wi-Fi 6 AX200NGW
Kernel driver in use: iwlwifi
05:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Renoir (rev c6)
Subsystem: Lenovo Renoir
Kernel driver in use: amdgpu
05:00.2 Encryption controller: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 10h-1fh) Platform Security Processor
Subsystem: Lenovo Family 17h (Models 10h-1fh) Platform Security Processor
Kernel driver in use: ccp
05:00.3 USB controller: Advanced Micro Devices, Inc. [AMD] Renoir/Cezanne USB 3.1
Subsystem: Lenovo Renoir/Cezanne USB 3.1
Kernel driver in use: xhci_hcd
05:00.4 USB controller: Advanced Micro Devices, Inc. [AMD] Renoir/Cezanne USB 3.1
Subsystem: Lenovo Renoir/Cezanne USB 3.1
Kernel driver in use: xhci_hcd
05:00.5 Multimedia controller: Advanced Micro Devices, Inc. [AMD] ACP/ACP3X/ACP6x Audio Coprocessor (rev 01)
Subsystem: Lenovo ACP/ACP3X/ACP6x Audio Coprocessor
05:00.6 Audio device: Advanced Micro Devices, Inc. [AMD] Family 17h/19h HD Audio Controller
Subsystem: Lenovo Family 17h/19h HD Audio Controller
Kernel driver in use: snd_hda_intel
06:00.0 SATA controller: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] (rev 81)
Subsystem: Lenovo FCH SATA Controller [AHCI mode]
Kernel driver in use: ahci
06:00.1 SATA controller: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] (rev 81)
Subsystem: Lenovo FCH SATA Controller [AHCI mode]
Kernel driver in use: ahci
Output from `pacman -Qs vulkan`:
local/goverlay-bin 0.9.1-3
A GUI to help manage Vulkan/OpenGL overlays
local/lib32-nvidia-utils 535.54.03-2
NVIDIA drivers utilities (32-bit)
local/lib32-vkbasalt 0.3.2.10-1
A Vulkan post-processing layer. Some of the effects are CAS, FXAA, SMAA, deband.
local/lib32-vkd3d 1.7.1-1
Direct3D 12 to Vulkan translation library By WineHQ
local/lib32-vulkan-icd-loader 1.3.255-1
Vulkan Installable Client Driver (ICD) Loader (32-bit)
local/lib32-vulkan-mesa-layers 23.1.3-1
Mesa's Vulkan layers (32-bit)
local/lib32-vulkan-validation-layers 1.3.250.0-3
Vulkan Validation Layers (32-bit)
local/mangohud 0.6.9.1-8
A Vulkan overlay layer for monitoring FPS, temperatures, CPU/GPU load and more.
local/nvidia-utils 535.54.03-1
NVIDIA drivers utilities
local/python-glfw 2.5.9-2
Module for OpenGL, OpenGL ES, Vulkan, window and input support
local/qt6-shadertools 6.5.1-1 (qt6)
Provides functionality for the shader pipeline that allows Qt Quick to operate on Vulkan, Metal, and Direct3D, in addition to OpenGL
local/renderdoc-bin 1.27-1
OpenGL and Vulkan debugging tool - binary version
local/spirv-tools 2022.4-1 (vulkan-devel)
API and commands for processing SPIR-V modules
local/vkbasalt 0.3.2.10-1
A Vulkan post-processing layer. Some of the effects are CAS, FXAA, SMAA, deband.
local/vkd3d 1.7.1-1
Direct3D 12 to Vulkan translation library By WineHQ
local/vkmark 20220318-1
Vulkan benchmark
local/vulkada 2023.2.13-2
A complete Vulkan 1.1 binding for the Ada 2012 programming language.
local/vulkan-extra-layers 1.3.250.0-1 (vulkan-devel)
Extra layers for Vulkan development
local/vulkan-extra-tools 1.3.250.0-1 (vulkan-devel)
Vulkan lunarg tools
local/vulkan-headers 1:1.3.256-1 (vulkan-devel)
Vulkan header files
local/vulkan-html-docs 1:1.3.256-1 (vulkan-devel)
Vulkan html documentation
local/vulkan-icd-loader 1.3.255-1
Vulkan Installable Client Driver (ICD) Loader
local/vulkan-mesa-layers 23.1.3-2
Mesa's Vulkan layers
local/vulkan-tools 1.3.255-1 (vulkan-devel)
Vulkan Utilities and Tools
local/vulkan-validation-layers 1.3.250.0-2 (vulkan-devel)
Vulkan Validation Layers
Offline
Yup, install vulkan-radeon & lib32-vulkan-radeon .
Post fresh vulkaninfo --summary .
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
Output of `vulkaninfo --summary` after installing both of those packages:
==========
VULKANINFO
==========
Vulkan Instance Version: 1.3.255
Instance Extensions: count = 23
-------------------------------
VK_EXT_acquire_drm_display : extension revision 1
VK_EXT_acquire_xlib_display : extension revision 1
VK_EXT_debug_report : extension revision 10
VK_EXT_debug_utils : extension revision 2
VK_EXT_direct_mode_display : extension revision 1
VK_EXT_display_surface_counter : extension revision 1
VK_EXT_surface_maintenance1 : extension revision 1
VK_EXT_swapchain_colorspace : extension revision 4
VK_KHR_device_group_creation : extension revision 1
VK_KHR_display : extension revision 23
VK_KHR_external_fence_capabilities : extension revision 1
VK_KHR_external_memory_capabilities : extension revision 1
VK_KHR_external_semaphore_capabilities : extension revision 1
VK_KHR_get_display_properties2 : extension revision 1
VK_KHR_get_physical_device_properties2 : extension revision 2
VK_KHR_get_surface_capabilities2 : extension revision 1
VK_KHR_portability_enumeration : extension revision 1
VK_KHR_surface : extension revision 25
VK_KHR_surface_protected_capabilities : extension revision 1
VK_KHR_wayland_surface : extension revision 6
VK_KHR_xcb_surface : extension revision 6
VK_KHR_xlib_surface : extension revision 6
VK_LUNARG_direct_driver_loading : extension revision 1
Instance Layers: count = 18
---------------------------
VK_LAYER_INTEL_nullhw INTEL NULL HW 1.1.73 version 1
VK_LAYER_KHRONOS_validation Khronos Validation Layer 1.3.250 version 1
VK_LAYER_LUNARG_api_dump LunarG API dump layer 1.3.250 version 2
VK_LAYER_LUNARG_monitor Execution Monitoring Layer 1.3.250 version 1
VK_LAYER_LUNARG_screenshot LunarG image capture layer 1.3.250 version 1
VK_LAYER_MANGOAPP_overlay Mangoapp Layer 1.3.0 version 1
VK_LAYER_MANGOHUD_overlay_x86_64 Vulkan Hud Overlay 1.3.0 version 1
VK_LAYER_MESA_device_select Linux device selection layer 1.3.211 version 1
VK_LAYER_MESA_overlay Mesa Overlay layer 1.3.211 version 1
VK_LAYER_NV_optimus NVIDIA Optimus layer 1.3.242 version 1
VK_LAYER_RENDERDOC_Capture Debugging capture layer for RenderDoc 1.3.131 version 27
VK_LAYER_TORKEL104_libstrangle Libstrangle framerate limiter 1.1.125 version 1
VK_LAYER_VALVE_steam_fossilize_32 Steam Pipeline Caching Layer 1.3.207 version 1
VK_LAYER_VALVE_steam_fossilize_64 Steam Pipeline Caching Layer 1.3.207 version 1
VK_LAYER_VALVE_steam_overlay_32 Steam Overlay Layer 1.3.207 version 1
VK_LAYER_VALVE_steam_overlay_64 Steam Overlay Layer 1.3.207 version 1
VK_LAYER_VKBASALT_post_processing a post processing layer 1.3.223 version 1
VK_LAYER_VKBASALT_post_processing a post processing layer 1.3.223 version 1
Devices:
========
GPU0:
apiVersion = 1.3.246
driverVersion = 23.1.3
vendorID = 0x1002
deviceID = 0x1636
deviceType = PHYSICAL_DEVICE_TYPE_INTEGRATED_GPU
deviceName = AMD Radeon Graphics (RADV RENOIR)
driverID = DRIVER_ID_MESA_RADV
driverName = radv
driverInfo = Mesa 23.1.3
conformanceVersion = 1.2.7.1
deviceUUID = 00000000-0500-0000-0000-000000000000
driverUUID = 414d442d-4d45-5341-2d44-525600000000
GPU1:
apiVersion = 1.3.242
driverVersion = 535.54.3.0
vendorID = 0x10de
deviceID = 0x1f95
deviceType = PHYSICAL_DEVICE_TYPE_DISCRETE_GPU
deviceName = NVIDIA GeForce GTX 1650 Ti
driverID = DRIVER_ID_NVIDIA_PROPRIETARY
driverName = NVIDIA
driverInfo = 535.54.03
conformanceVersion = 1.3.5.0
deviceUUID = 122adb08-4280-7f1b-51de-776b5df42297
driverUUID = 8b72f8cf-fcf7-59af-b250-edf6b04fc087
Offline
Both your cards are now visible to vulkan using applications and should be able to be selected by standards following apps.
See vulkan-mesa-device-select-layer environment variables how to influence which card they use for vulkan.
I suggest you run some tests and tell us what remaining issues there are.
Last edited by Lone_Wolf (2023-07-15 14:08:52)
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
The remaining issue is that Proton still fails to run anything (native games run fine, also as before).
I have a suspicion that there might be something going on that impacts any version of Wine, since this issue also persists and has similar errors: https://bbs.archlinux.org/viewtopic.php?id=287016
Offline
There have been several cases recently where steam failed to run due to changes in multilib applications.
If my memory is correct, 2 workarounds have been mentioned :
- removing lib32-gudev
- installing lib32-nm
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
Steam itself runs fine (and starts native games without issues), in my case it is specifically Proton (as well as regular Wine) that are unable to launch any Windows programs.
Offline
That xorg config file doesn't make much sense as is, make sure it is not present and you've restarted xorg without it.
What's your output of
nvida-smi
and run a proton game with
PROTON_LOG=1 %command%
in the launch options and post the resultant log file from your home dir
Offline
Output of nvidia-smi (while idle):
Tue Jul 18 08:01:29 2023
+---------------------------------------------------------------------------------------+
| NVIDIA-SMI 535.54.03 Driver Version: 535.54.03 CUDA Version: 12.2 |
|-----------------------------------------+----------------------+----------------------+
| GPU Name Persistence-M | Bus-Id Disp.A | Volatile Uncorr. ECC |
| Fan Temp Perf Pwr:Usage/Cap | Memory-Usage | GPU-Util Compute M. |
| | | MIG M. |
|=========================================+======================+======================|
| 0 NVIDIA GeForce GTX 1650 Ti Off | 00000000:01:00.0 Off | N/A |
| N/A 34C P8 1W / 50W | 1MiB / 4096MiB | 0% Default |
| | | N/A |
+-----------------------------------------+----------------------+----------------------+
+---------------------------------------------------------------------------------------+
| Processes: |
| GPU GI CI PID Type Process name GPU Memory |
| ID ID Usage |
|=======================================================================================|
| No running processes found |
+---------------------------------------------------------------------------------------+
I already pasted one Proton log in the OP: https://pastebin.com/ETp7VPnp
Should I make another one?
Offline
Maybe, but generally your setup is logically slightly broken. You should see a Xorg process here on a normal PRIME enabled run. Remove your custom xorg config files, restart xorg, repost a xorg log and nvidia-smi and an updated proton log.
Offline
My Xorg is running on the integrated (amdgpu) device. I use the NVIDIA GPU for running games and other graphics-intensive apps or CUDA codes only. Should I be seeing its process in nvidia-smi in this case?
Output of `lspci | grep -i --color 'vga\|3d\|2d'`:
01:00.0 VGA compatible controller: NVIDIA Corporation TU117M [GeForce GTX 1650 Ti Mobile] (rev a1)
05:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Renoir (rev c6)
When running a process with prime-run (in this case, Relic Space started via Steam, all native games run fine), I am seeing its process.
Tue Jul 18 10:41:09 2023
+---------------------------------------------------------------------------------------+
| NVIDIA-SMI 535.54.03 Driver Version: 535.54.03 CUDA Version: 12.2 |
|-----------------------------------------+----------------------+----------------------+
| GPU Name Persistence-M | Bus-Id Disp.A | Volatile Uncorr. ECC |
| Fan Temp Perf Pwr:Usage/Cap | Memory-Usage | GPU-Util Compute M. |
| | | MIG M. |
|=========================================+======================+======================|
| 0 NVIDIA GeForce GTX 1650 Ti Off | 00000000:01:00.0 Off | N/A |
| N/A 39C P0 21W / 50W | 143MiB / 4096MiB | 99% Default |
| | | N/A |
+-----------------------------------------+----------------------+----------------------+
+---------------------------------------------------------------------------------------+
| Processes: |
| GPU GI CI PID Type Process name GPU Memory |
| ID ID Usage |
|=======================================================================================|
| 0 N/A N/A 2922516 G ...mmon/Relic Space/Relic Space.x86_64 142MiB |
+---------------------------------------------------------------------------------------+
Last edited by mindbound (2023-07-18 07:51:30)
Offline
Yes you should and yes it should... Your current xorg conf omits the nvidia driver from being loaded by xorg, chances are this trips up wine, because it wants to hook into some Xorg function (which it asks of the renderer card, which can't provide, since it doesn't know about the X screen it's supposed to look at), please test the relevant conditions. (... And there have been actual problems here with an updated xf86-video-amdgpu, I strongly suggest you test without that, seeing your config doesn't actually configure anything of note that would not be provided by the modesetting driver anyway)
If your concerned about "power saving". The default setup of prime and the xorg process it will load will not generally lead to an increase in power draw since the load is too low.
Last edited by V1del (2023-07-18 23:33:08)
Offline
All right. Aside from /etc/X11/xorg.conf.d/20-amdgpu.conf, I can't recall having made changes to anywhere else regarding GPUs, is there anything else I should remove or reset, apart from that and the amdgpu driver?
Last edited by mindbound (2023-07-19 04:11:00)
Offline