You are not logged in.
Pages: 1
I tried to run the GT740M with wine + dxvk-1.10.3
tested vkcube and it should be fine:
https://tc.z.wiki/autoupload/f/4Jl0JdO3 … X768/1.png
Then I tested wine + dxvk-1.10.3 :
https://tc.z.wiki/autoupload/f/4Jl0JdO3 … X768/2.png
But no matter what, he couldn't start any program of wine![]()
vulkaninfo --summary
==========
VULKANINFO
==========
Vulkan Instance Version: 1.4.321
Instance Extensions: count = 24
-------------------------------
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_headless_surface : extension revision 1
VK_EXT_surface_maintenance1 : extension revision 1
VK_EXT_swapchain_colorspace : extension revision 5
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 = 12
---------------------------
VK_LAYER_INTEL_nullhw INTEL NULL HW 1.1.73 version 1
VK_LAYER_MANGOHUD_overlay_x86 Vulkan Hud Overlay 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.4.303 version 1
VK_LAYER_MESA_overlay Mesa Overlay layer 1.4.303 version 1
VK_LAYER_MESA_screenshot Mesa Screenshot layer 1.4.303 version 1
VK_LAYER_MESA_vram_report_limit Limit reported VRAM 1.4.303 version 1
VK_LAYER_NV_optimus NVIDIA Optimus layer 1.2.175 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
Devices:
========
GPU0:
apiVersion = 1.2.311
driverVersion = 25.1.6
vendorID = 0x8086
deviceID = 0x0416
deviceType = PHYSICAL_DEVICE_TYPE_INTEGRATED_GPU
deviceName = Intel(R) HD Graphics 4600 (HSW GT2)
driverID = DRIVER_ID_INTEL_OPEN_SOURCE_MESA
driverName = Intel open-source Mesa driver
driverInfo = Mesa 25.1.6-arch1.1
conformanceVersion = 0.0.0.0
deviceUUID = 86801604-0600-0000-0002-000000000000
driverUUID = cad93c1a-539a-d04c-7528-68eff04f4b43
GPU1:
apiVersion = 1.2.175
driverVersion = 471.0.2.0
vendorID = 0x10de
deviceID = 0x1292
deviceType = PHYSICAL_DEVICE_TYPE_DISCRETE_GPU
deviceName = NVIDIA GeForce GT 740M
driverID = DRIVER_ID_NVIDIA_PROPRIETARY
driverName = NVIDIA
driverInfo = 470.256.02
conformanceVersion = 1.2.6.0
deviceUUID = 86be3542-6a8f-a0af-b3a6-7871365a942e
driverUUID = b67e126b-ca9f-5837-843e-603a6ad11b15 GPU 0: 10de:1292 "NVIDIA GeForce GT 740M" discrete GPU 0000:01:00.0
GPU 1: 8086:416 "Intel(R) HD Graphics 4600 (HSW GT2)" integrated GPU 0000:00:02.0Last edited by Ypixcm (2025-07-24 13:31:50)
My new name: RethLibc
Offline
Don't post pictures of text, post the text.
export VK_DRIVER_FILES=/usr/share/vulkan/icd.d/nvidia_icd.jsonMESA_VK_DEVICE_SELECT won't help since you're not even using mesa.
wine w/o dxvk still works?
Offline
] cm@thinkpad ~> export VK_DRIVER_FILES=/usr/share/vulkan/icd.d/nvidia_icd.json
[I] cm@thinkpad ~> export WINEPREFIX=/home/cm/.local/share/wineprefixes/dv/
[I] cm@thinkpad ~> winecfg
0108:fixme:winediag:loader_init wine-staging 10.12 is a testing version containing experimental patches.
0108:fixme:winediag:loader_init Please mention your exact version when filing bug reports on winehq.org.Still can't work
This problem won't exist if vulkan and dxvk is not used
My new name: RethLibc
Offline
Devices:
========
GPU0:
apiVersion = 1.2.175
driverVersion = 471.0.2.0
vendorID = 0x10de
deviceID = 0x1292
deviceType = PHYSICAL_DEVICE_TYPE_DISCRETE_GPU
deviceName = NVIDIA GeForce GT 740M
driverID = DRIVER_ID_NVIDIA_PROPRIETARY
driverName = NVIDIA
driverInfo = 470.256.02
conformanceVersion = 1.2.6.0
deviceUUID = 86be3542-6a8f-a0af-b3a6-7871365a942e
driverUUID = 59e6bdea-91a6-28ea-86ed-cf0f90d30054
GPU1:
apiVersion = 1.2.311
driverVersion = 25.1.6
vendorID = 0x8086
deviceID = 0x0416
deviceType = PHYSICAL_DEVICE_TYPE_INTEGRATED_GPU
deviceName = Intel(R) HD Graphics 4600 (HSW GT2)
driverID = DRIVER_ID_INTEL_OPEN_SOURCE_MESA
driverName = Intel open-source Mesa driver
driverInfo = Mesa 25.1.6-arch1.1
conformanceVersion = 0.0.0.0
deviceUUID = 86801604-0600-0000-0002-000000000000
driverUUID = cad93c1a-539a-d04c-7528-68eff04f4b43You're running a dual gpu system : intel integrated + nvidia .
On such setups you need a special vulkan layer to allow both devices can be used .
Verify you do have vulkan-intel & lib32-vulkan-intel present. If not, install them.
Install https://archlinux.org/packages/?name=vulkan-mesa-layers.
re-run vulkaninfo --summary and post the output
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] cm@thinkpad ~ [1]> sudo pacman -S vulkan-intel
warning: vulkan-intel-1:25.1.6-1 is up to date -- reinstalling
resolving dependencies...
^C
Interrupt signal received
[I] cm@thinkpad ~ [SIGINT]> sudo pacman -S lib32-vulkan-inte
error: target not found: lib32-vulkan-inte
[I] cm@thinkpad ~ [1]> sudo pacman -S lib32-vulkan-intel
warning: lib32-vulkan-intel-1:25.1.6-1 is up to date -- reinstalling
resolving dependencies...
^C
Interrupt signal received
[I] cm@thinkpad ~ [SIGINT]> sudo pacman -S vulkan-mesa-layers
warning: vulkan-mesa-layers-1:25.1.6-1 is up to date -- reinstalling
resolving dependencies...
^C
Interrupt signal received
==========
VULKANINFO
==========
Vulkan Instance Version: 1.4.321
Instance Extensions: count = 24
-------------------------------
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_headless_surface : extension revision 1
VK_EXT_surface_maintenance1 : extension revision 1
VK_EXT_swapchain_colorspace : extension revision 5
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 = 12
---------------------------
VK_LAYER_INTEL_nullhw INTEL NULL HW 1.1.73 version 1
VK_LAYER_MANGOHUD_overlay_x86 Vulkan Hud Overlay 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.4.303 version 1
VK_LAYER_MESA_overlay Mesa Overlay layer 1.4.303 version 1
VK_LAYER_MESA_screenshot Mesa Screenshot layer 1.4.303 version 1
VK_LAYER_MESA_vram_report_limit Limit reported VRAM 1.4.303 version 1
VK_LAYER_NV_optimus NVIDIA Optimus layer 1.2.175 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
Devices:
========
GPU0:
apiVersion = 1.2.311
driverVersion = 25.1.6
vendorID = 0x8086
deviceID = 0x0416
deviceType = PHYSICAL_DEVICE_TYPE_INTEGRATED_GPU
deviceName = Intel(R) HD Graphics 4600 (HSW GT2)
driverID = DRIVER_ID_INTEL_OPEN_SOURCE_MESA
driverName = Intel open-source Mesa driver
driverInfo = Mesa 25.1.6-arch1.1
conformanceVersion = 0.0.0.0
deviceUUID = 86801604-0600-0000-0002-000000000000
driverUUID = cad93c1a-539a-d04c-7528-68eff04f4b43
GPU1:
apiVersion = 1.2.175
driverVersion = 471.0.2.0
vendorID = 0x10de
deviceID = 0x1292
deviceType = PHYSICAL_DEVICE_TYPE_DISCRETE_GPU
deviceName = NVIDIA GeForce GT 740M
driverID = DRIVER_ID_NVIDIA_PROPRIETARY
driverName = NVIDIA
driverInfo = 470.256.02
conformanceVersion = 1.2.6.0
deviceUUID = 86be3542-6a8f-a0af-b3a6-7871365a942e
driverUUID = b67e126b-ca9f-5837-843e-603a6ad11b15Last edited by Ypixcm (2025-07-24 12:31:52)
My new name: RethLibc
Offline
You had a small typo for lib32-vulkan-intel .
You had a very similar issue in https://bbs.archlinux.org/viewtopic.php?id=307120 and solved it by installing vulkan-mesa-layers.
Why is the VK_LAYER_MESA_device_select layer missing in the vulkaninfo --summary output in #1 ?
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
You had a small typo for lib32-vulkan-intel .
Yes, but I'm sure lib32-vulkan-intel has been installed
You had a very similar issue in https://bbs.archlinux.org/viewtopic.php?id=307120 and solved it by installing vulkan-mesa-layers.
I set export MESA_VK_DEVICE_SELECT=8086:416! It has been placed in the .xprofile file
It has indeed solved the problem that wine cannot start in dual gpu a environment
Someone told me that export VK_LOADER_DRIVERS_DISABLE="nvidia_icd.json" can also solve this problem
But I chose to use MESA_VK_DEVICE_SELECT=8086:416!
It seems that this ultimately stems from the compatibility issue of 740M with vulkan
Why is the VK_LAYER_MESA_device_select layer missing in the vulkaninfo --summary output in #1 ?
Because I set MESA_VK_DEVICE_SELECT=8086:416! It affected the output of the vulkaninfo --summary command, but I forgot about it
The 740M can only use wined3d, but I want to use dxvk
As long as you ensure that the 740M uses wined3d, there won't be any problems with wine
Last edited by Ypixcm (2025-07-24 13:38:31)
My new name: RethLibc
Offline
Note: Nvidia's Kepler architecture (most GTX 600 / 700 series) is no longer supported. Please use DXVK 1.10.3 in combination with these cards.
Someone told me that export VK_LOADER_DRIVERS_DISABLE="nvidia_icd.json" can also solve this problem
That may be your best chance, try it.
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 meaning of VK_LOADER_DRIVERS_DISABLE is to disable driver loading. The purpose is still to enable NVIDIA graphics cards to use wined3d. Primer-run wine + dxvk will directly use the core graphics card. primer-run wine will use a dedicated graphics card(nvidia) but only wined3d. The Kepler graphics card is indeed too old, and perhaps there is no solution to this problem yet
Last edited by Ypixcm (2025-07-24 23:07:31)
My new name: RethLibc
Offline
Offline
Pages: 1