I have the same issue as them. My driver version is 550.90.07 and on ls /dev/dri I get the following.
by-path card1 renderD128
Adding environment.sessionVariables.VK_DRIVER_FILES = "/run/opengl-driver/share/vulkan/icd.d/nvidia_icd.x86_64.json"; solved this issue but introduced a new one in form of Vulkan failing to initialize.
and this is my driver version for Nvidia : 555.58.02
I have the latest driver now because I recently updated my channel, I didn’t test if obsidian work now…
Update
I just tested obsidian now from nixpkgs unstable and it’s behavior is always this weird… so for the moment I use the flatpak version of it, this one work great!
EDIT :
Steam have weird issue too, if I start it from the terminal all work fine, but I got this nvidia warning :
$ steam
steam.sh[304339]: Running Steam on nixos 24.11 64-bit
steam.sh[304339]: STEAM_RUNTIME is enabled automatically
setup.sh[304417]: Steam runtime environment up-to-date!
steam.sh[304339]: Steam client's requirements are satisfied
[2024-07-06 00:12:25] Startup - updater built Jun 20 2024 17:13:49
[2024-07-06 00:12:25] Startup - Steam Client launched with: '/home/alez/.local/share/Steam/ubuntu12_32/steam' '-srt-logger-opened'
07/06 00:12:25 minidumps folder is set to /tmp/dumps
07/06 00:12:25 Init: Installing breakpad exception handler for appid(steam)/version(1718904662)/tid(304478)
[2024-07-06 00:12:25] Loading cached metrics from disk (/home/alez/.local/share/Steam/package/steam_client_metrics.bin)
[2024-07-06 00:12:25] Using the following download hosts for Public, Realm steamglobal
[2024-07-06 00:12:25] 1. https://client-update.akamai.steamstatic.com, /, Realm 'steamglobal', weight was 1000, source = 'update_hosts_cached.vdf'
[2024-07-06 00:12:25] 2. https://cdn.cloudflare.steamstatic.com, /client/, Realm 'steamglobal', weight was 1, source = 'update_hosts_cached.vdf'
[2024-07-06 00:12:25] 3. https://cdn.steamstatic.com, /client/, Realm 'steamglobal', weight was 1, source = 'baked in'
[2024-07-06 00:12:25] Verifying installation...
[2024-07-06 00:12:25] Verification complete
UpdateUI: skip show logo
Steam logging initialized: directory: /home/alez/.local/share/Steam/logs
XRRGetOutputInfo Workaround: initialized with override: 0 real: 0xe9b267b0
XRRGetCrtcInfo Workaround: initialized with override: 0 real: 0xe9b24f90
CAppInfoCacheReadFromDiskThread took 30 milliseconds to initialize
Steam Runtime Launch Service: starting steam-runtime-launcher-service
Steam Runtime Launch Service: steam-runtime-launcher-service is running pid 304731
bus_name=com.steampowered.PressureVessel.LaunchAlongsideSteam
DRM kernel driver 'nvidia-drm' in use. NVK requires nouveau.
DRM kernel driver 'nvidia-drm' in use. NVK requires nouveau.
DRM kernel driver 'nvidia-drm' in use. NVK requires nouveau.
DRM kernel driver 'nvidia-drm' in use. NVK requires nouveau.
BRefreshApplicationsInLibrary 1: 0ms
BuildCompleteAppOverviewChange: 257 apps
RegisterForAppOverview 1: 5ms
RegisterForAppOverview 2: 6ms
but when I start it from the app launcher (Hyprland with wofi) it start normally but the window is transparent, very weird
Assuming you’re not deliberately using a multi-gpu setup, that definitely looks like an instance of the bug I ran into. If so, you will have some applications failing, depending on whether they happen to use your actual GPU or not.
What’s the rest of your config? Did you reboot after making nvidia drive the fbdev? What does dmesg | grep drm give you?
Fair enough, that’s a different scenario then. I’d be curious if this is crossed wires with whatever you use to switch between GPUs.
Your system does also load simpledrm, but it’s not the issue:
Either way, I guess this particular error can come about a number of ways, and what I found just happened to be one way that lined up roughly with the report dates. Further debugging would require playing around with your configuration until you manage to root cause it.
I don’t know if I made a mistake when configuring my GPUs, I configured it with the help of the Nixos wiki.
There is the output I get when doing sudo lshw -c display :
It seems so. I’m hitting this on a computer which definitely only has one GPU, the Nvidia one (the CPU is a Threadripper without integrated graphics support).
FWIW, I did have that spurious 31" monitor issue too. Adding nvidia-drm.fbdev=1 to kernel parameters seems to have fixed that, but the NVK warning is still there. vulkaninfo (and Chrome) still output these lines to stderr, but proceed to work nicely after that:
WARNING: [Loader Message] Code 0 : terminator_CreateInstance: Received return code -3 from call to vkCreateInstance in ICD /nix/store/g4gar0lac83yl5qnj51mhhcrnscl8lzk-mesa-24.0.7-drivers/lib/libvulkan_dzn.so. Skipping this driver.
WARNING: [Loader Message] Code 0 : terminator_CreateInstance: Received return code -3 from call to vkCreateInstance in ICD /nix/store/g4gar0lac83yl5qnj51mhhcrnscl8lzk-mesa-24.0.7-drivers/lib/libvulkan_virtio.so. Skipping this driver.
DRM kernel driver 'nvidia-drm' in use. NVK requires nouveau.
ERROR: [../src/nouveau/vulkan/nvk_physical_device.c:935] Code 0 : VK_ERROR_INCOMPATIBLE_DRIVER
Setting the environment variable VK_DRIVER_FILES=/run/opengl-driver/share/vulkan/icd.d/nvidia_icd.x86_64.json seems to make these warnings go away.
when i play battle.net in Lutris - i have this in logs:
1) DRM kernel driver 'nvidia-drm' in use. NVK requires nouveau.
2) ntlm_auth: /home/reloner/.local/share/lutris/runtime/Ubuntu-18.04-x86_64/libjansson.so.4: no version information available (required by /nix/store/4gcggjvzrbywi92r66p6l15hckxng2q0-samba-4.20.1/lib/samba/libcommon-auth-private-samba.so)
for 1st warning - i have one rtx gpu with stable 550 driver, and i am on X11. Setting VK_DRIVER_FILES environment variable fixed this warning, but the game doesnt launch anymore
for 2nd warning - Tried samba, amdvlk, jansson, vulkan-tools packages - nothing fixes this
After deleting variable VK_DRIVER_FILES - 1st warning returns, but the game actually launch now
The format of your bus configuration differs from what is said in the wiki. For you it should be nvidiaBusId = "PCI:1:0:0"; and amdgpuBusId = "PCI:7:0:0";
The wiki states
Note the two values under “bus info” above, which may differ from laptop to laptop. Our Nvidia Bus ID is 0e:00.0 and our Intel Bus ID is 00:02.0 . Watch out for the formatting; convert them from hexadecimal to decimal, remove the padding (leading zeroes), replace the dot with a colon, then add them like this:
{
hardware.nvidia.prime = {
# Make sure to use the correct Bus ID values for your system!
intelBusId = "PCI:0:2:0";
nvidiaBusId = "PCI:14:0:0";
# amdgpuBusId = "PCI:54:0:0"; For AMD GPU
};
}
Yea thanks, I saw this a few weeks ago, but this is not related to the current issue sadly…
I regularly updated my flake (which is on the unstable channel) and now have the 555.58.02 version of the drivers, now the message DRM kernel driver 'nvidia-drm' in use. NVK requires nouveau. don’t appear anymore, but my obsidian still can’t start, there is the logs :
2024-08-09 16:08:23 Loading main app package /nix/store/8v8cnvz4xcgrbnssq3flrkhhb0an79hr-obsidian-1.6.7/share/obsidian/obsidian.asar
Ignored: Error: ENOENT: no such file or directory, open '/home/alez/.config/obsidian/obsidian.json'
2024-08-09 16:08:23 Checking for update using Github
2024-08-09 16:08:24 Success.
2024-08-09 16:08:24 Latest version is 1.6.7
2024-08-09 16:08:24 App is up to date.
[2906:0809/180824.164068:ERROR:gl_display.cc(515)] EGL Driver message (Critical) : eglCreateImage failed with 0x00003003
[2906:0809/180824.164248:ERROR:scoped_egl_image.cc(23)] Failed to create EGLImage: EGL_BAD_ALLOC
[2906:0809/180824.164302:ERROR:native_pixmap_egl_binding.cc(109)] Unable to initialize binding from pixmap
[2906:0809/180824.164406:ERROR:ozone_image_backing.cc(365)] OzoneImageBacking::ProduceSkiaGanesh failed to create GL representation
[2906:0809/180824.164466:ERROR:shared_image_manager.cc(229)] SharedImageManager::ProduceSkia: Trying to produce a Skia representation from an incompatible backing: OzoneImageBacking
[2906:0809/180824.164639:ERROR:gpu_service_impl.cc(1124)] Exiting GPU process because some drivers can't recover from errors. GPU process will restart shortly.
[2687:0809/180824.180894:ERROR:gpu_process_host.cc(997)] GPU process exited unexpectedly: exit_code=8704
[2962:0809/180824.477229:ERROR:gl_display.cc(515)] EGL Driver message (Critical) : eglCreateImage failed with 0x00003003
[2962:0809/180824.477321:ERROR:scoped_egl_image.cc(23)] Failed to create EGLImage: EGL_BAD_ALLOC
[2962:0809/180824.477373:ERROR:native_pixmap_egl_binding.cc(109)] Unable to initialize binding from pixmap
[2962:0809/180824.477431:ERROR:ozone_image_backing.cc(365)] OzoneImageBacking::ProduceSkiaGanesh failed to create GL representation
[2962:0809/180824.477478:ERROR:shared_image_manager.cc(229)] SharedImageManager::ProduceSkia: Trying to produce a Skia representation from an incompatible backing: OzoneImageBacking
[2962:0809/180824.477582:ERROR:gpu_service_impl.cc(1124)] Exiting GPU process because some drivers can't recover from errors. GPU process will restart shortly.
[2687:0809/180824.486559:ERROR:gpu_process_host.cc(997)] GPU process exited unexpectedly: exit_code=8704
[2995:0809/180824.800480:ERROR:gl_display.cc(515)] EGL Driver message (Critical) : eglCreateImage failed with 0x00003003
[2995:0809/180824.800628:ERROR:scoped_egl_image.cc(23)] Failed to create EGLImage: EGL_BAD_ALLOC
[2995:0809/180824.800676:ERROR:native_pixmap_egl_binding.cc(109)] Unable to initialize binding from pixmap
[2995:0809/180824.800748:ERROR:ozone_image_backing.cc(365)] OzoneImageBacking::ProduceSkiaGanesh failed to create GL representation
[2995:0809/180824.800789:ERROR:shared_image_manager.cc(229)] SharedImageManager::ProduceSkia: Trying to produce a Skia representation from an incompatible backing: OzoneImageBacking
[2995:0809/180824.801010:ERROR:gpu_service_impl.cc(1124)] Exiting GPU process because some drivers can't recover from errors. GPU process will restart shortly.
[2687:0809/180824.810282:ERROR:gpu_process_host.cc(997)] GPU process exited unexpectedly: exit_code=8704
the drivers just crash? I don’t really know.
Is there a way to start the process with my integrated AMD gpu instead of the Nvidia one just for obsidian? this would be more simpler to fix this issue…
Because my games just run fine (the game had the weird message too, but now gone with the recent update), so I think that’s more a chromium/electron issue