# Vulkan not working on MX130

**URL:** <https://forums.developer.nvidia.com/t/vulkan-not-working-on-mx130/381028>\
**Category:** Linux\
**Tags:** vulkan\
**Created:** [August 23, 2026, 7:59pm UTC](https://forums.developer.nvidia.com/t/vulkan-not-working-on-mx130/381028 "2026-08-23T19:59:15Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![fibo0112358](https://developer.download.nvidia.com/images/forums/profile-default-devtalk-84.png) [@fibo0112358](https://forums.developer.nvidia.com/u/fibo0112358)\
**Post date:** [August 23, 2026, 7:59pm UTC](https://forums.developer.nvidia.com/t/vulkan-not-working-on-mx130/381028/1 "2026-08-23T19:59:15Z")

</div>

I have an some older laptop (Dell Latitude 5590) with dual GPU: Intel iGPU + MX130, and I run Gentoo on it with currently installed nvidia-drivers `580.178.04`.

I can easily run vkcube or vkgears on iGPU - works flawless. But when trying to run on nvidia gpu with `nvx start vkcube|vkgears` it crashes:

```plaintext
$ nvx start vkcube 
Selected WSI platform: wayland 
Selected GPU 0: NVIDIA GeForce MX130, type: DiscreteGpu, apiVersion: 4211000 (1.4.312), driverVersion: -1859354368 (68.712.256) 
(exit code: 245)

```

I was able to trace it to the `vkCreateSwapchainKHR` call which returns `-13` and `swapchain` value in `NULL`.

I have currently installed vulkan tools in version `1.4.357.0`.

(I have no problem with running glxgears on MX130).

Anyone can help with solving this issue?

---

<div class="post-metadata">

**Author:** ![morgwai666](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/morgwai666/32/393870_2.png) [@morgwai666](https://forums.developer.nvidia.com/u/morgwai666)\
**Post date:** [September 6, 2026, 9:16pm UTC](https://forums.developer.nvidia.com/t/vulkan-not-working-on-mx130/381028/2 "2026-09-06T21:16:43Z")

</div>

is `nvx` some Gentoo specific utility? If so, you may have more luck asking on Gentoo forums.

Normally, the way to start `vkcube` on a specific device is by using `--gpu_number` option. If this also fails, then please provide some more debug info before posting again: ideally an Nvidia bug report file, relevant log excerpts (`nvidia|nvrm|nvl|gsp|nouveau`), output of `vulkaninfo --summary` etc…

---

<div class="post-metadata">

**Author:** ![fibo0112358](https://developer.download.nvidia.com/images/forums/profile-default-devtalk-84.png) [@fibo0112358](https://forums.developer.nvidia.com/u/fibo0112358)\
**Post date:** [September 6, 2026, 9:48pm UTC](https://forums.developer.nvidia.com/t/vulkan-not-working-on-mx130/381028/3 "2026-09-06T21:48:37Z")

</div>

No, this is just external too to easy switching GPUs in Optimus systems: [GitHub - pedro00dk/nvidia-exec: GPU switching without log out for Nvidia Optimus laptops under Linux · GitHub](https://github.com/pedro00dk/nvidia-exec)

`nvx start app` just loads nvidia module, sets env variables and runs the app at nvidia GPU. I run normally on integrated iGPU and want nVidia only for games or so.

I can also use it to load GPU with `nvx on`, and then:

This works fine:

```auto
$ vkcube --gpu_number 1 
Selected WSI platform: wayland 
Selected GPU 1: Intel(R) UHD Graphics 620 (KBL GT2), type: IntegratedGpu, apiVersion: 4211042 (1.4.354), driverVersion: 109060097 (26.2.1

```

This crashes:

```auto
$ vkcube --gpu_number 0 
Selected WSI platform: wayland 
Selected GPU 0: NVIDIA GeForce MX130, type: DiscreteGpu, apiVersion: 4211000 (1.4.312), driverVersion: -1859354368 (68.712.256)  
Segmentation violationvkcube --gpu_number 0

```

This is what happens in my system logs:

```auto
Sep 6 23:44:24 coop kernel: pci 0000:03:00.0: [10de:174d] type 00 class 0x030200 PCIe Endpoint
Sep 6 23:44:24 coop kernel: pci 0000:03:00.0: BAR 0 [mem 0xee000000-0xeeffffff]
Sep 6 23:44:24 coop kernel: pci 0000:03:00.0: BAR 1 [mem 0xd0000000-0xdfffffff 64bit pref]
Sep 6 23:44:24 coop kernel: pci 0000:03:00.0: BAR 3 [mem 0xe0000000-0xe1ffffff 64bit pref]
Sep 6 23:44:24 coop kernel: pci 0000:03:00.0: BAR 5 [io 0xe000-0xe07f]
Sep 6 23:44:24 coop kernel: pci 0000:03:00.0: ROM [mem 0x00000000-0x0007ffff pref]
Sep 6 23:44:24 coop kernel: pci 0000:03:00.0: 8.000 Gb/s available PCIe bandwidth, limited by 2.5 GT/s PCIe x4 link at 0000:00:1c.4 (capable of 31.504 Gb/s with 8.0 GT/s PCIe x4 link)
Sep 6 23:44:24 coop kernel: pci 0000:03:00.0: BAR 1 [mem 0xd0000000-0xdfffffff 64bit pref]: assigned
Sep 6 23:44:24 coop kernel: pci 0000:03:00.0: BAR 3 [mem 0xe0000000-0xe1ffffff 64bit pref]: assigned
Sep 6 23:44:24 coop kernel: pci 0000:03:00.0: BAR 0 [mem 0xee000000-0xeeffffff]: assigned
Sep 6 23:44:24 coop kernel: pci 0000:03:00.0: ROM [mem 0xef000000-0xef07ffff pref]: assigned
Sep 6 23:44:24 coop kernel: pci 0000:03:00.0: BAR 5 [io 0xe000-0xe07f]: assigned
Sep 6 23:44:24 coop kernel: nvidia-nvlink: Nvlink Core is being initialized, major device number 511
Sep 6 23:44:24 coop kernel: NVRM: loading NVIDIA UNIX x86_64 Kernel Module 580.178.04 Tue Jul 7 12:38:21 UTC 2026
Sep 6 23:44:24 coop kernel: nvidia-modeset: Loading NVIDIA Kernel Mode Setting Driver for UNIX platforms 580.178.04 Tue Jul 7 12:03:04 UTC 2026
Sep 6 23:44:24 coop kernel: [drm] [nvidia-drm] [GPU ID 0x00000300] Loading driver
Sep 6 23:44:25 coop kernel: [drm] Initialized nvidia-drm 0.0.0 for 0000:03:00.0 on minor 1
Sep 6 23:44:25 coop kernel: nvidia 0000:03:00.0: [drm] No compatible format found
Sep 6 23:44:25 coop kernel: nvidia 0000:03:00.0: [drm] Cannot find any crtc or sizes
Sep 6 23:44:25 coop kernel: nvidia_uvm: module uses symbols nvUvmInterfaceDisableAccessCntr from proprietary module nvidia, inheriting taint.
Sep 6 23:44:25 coop kernel: vkcube[3084359]: segfault at 180 ip 00007ff0d3b695f3 sp 00007fffce23bf78 error 4 in libnvidia-glcore.so.580.178.04[d695f3,7ff0d3200000+c00000] likely on CPU 1 (core 1, socket 0)
Sep 6 23:44:25 coop kernel: Code: 00 00 c7 45 70 00 00 00 00 e9 f1 fa ff ff 66 0f 1f 84 00 00 00 00 00 4c 8d 5e b0 48 85 f6 b8 00 00 00 00 49 89 d2 4c 0f 44 d8 <45> 8b 8b 80 01 00 00 48 85 c9 74 51 44 39 0a 44 0f 46 0a 45 85 c9
Sep 6 23:44:25 coop kernel: [drm] [nvidia-drm] [GPU ID 0x00000300] Unloading driver
Sep 6 23:44:25 coop kernel: nvidia-modeset: Unloading
Sep 6 23:44:28 coop kernel: nvidia-nvlink: Unregistered Nvlink Core, major device number 511

```

For iGPU:

```auto
vulkaninfo --summary 
========== 
VULKANINFO 
========== 
 
Vulkan Instance Version: 1.4.357 
 
 
Instance Extensions: count = 27 
------------------------------- 
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_layer_settings : extension revision 2 
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_maintenance1 : extension revision 1 
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 
VK_NV_display_stereo : extension revision 1 
 
Instance Layers: count = 12 
--------------------------- 
VK_LAYER_FROG_gamescope_wsi_x86_64 Gamescope WSI (XWayland Bypass) Layer (x86_64) 1.3.221 version 1 
VK_LAYER_KHRONOS_validation Khronos Validation Layer 1.4.357 version 1 
VK_LAYER_MANGOHUD_overlay_x86_64 Vulkan Hud Overlay 1.3.0 version 1 
VK_LAYER_MESA_anti_lag Open-source implementation of the VK_AMD_anti_lag extension. 1.4.303 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_NV_optimus NVIDIA Optimus layer 1.4.312 version 1 
VK_LAYER_NV_present NVIDIA GR2608 layer 1.4.312 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.4.354 
        driverVersion = 26.2.1 
        vendorID = 0x8086 
        deviceID = 0x5917 
        deviceType = PHYSICAL_DEVICE_TYPE_INTEGRATED_GPU 
        deviceName = Intel(R) UHD Graphics 620 (KBL GT2) 
        driverID = DRIVER_ID_INTEL_OPEN_SOURCE_MESA 
        driverName = Intel open-source Mesa driver 
        driverInfo = Mesa 26.2.1 
        conformanceVersion = 1.4.0.0 
        deviceUUID = 86801759-0700-0000-0002-000000000000 
        driverUUID = beb33ed6-1b6b-4804-f218-acbcea808065

```

but for nvidia modules loaded:

```auto
ERROR while creating surface for extension VK_KHR_display : /var/tmp/portage/dev-util/vulkan-tools-1.4.357.0/work/Vulkan-Tools-vulkan-sdk-1.4.357.0/vulkaninfo/./vulkaninfo.h:249:vkGetPhysicalDeviceDisplayPropertiesKHR failed with ERROR_UNKNOWN

```

[nvidia-bug-report.log.gz](https://forums.developer.nvidia.com/uploads/short-url/1py7DVBqrxgyjw4rCeAY51SsT0d.gz) (370.7 KB)
