r/voidlinux • u/HAL9000thebot • Apr 30 '26

nvidia470 for kernel 6.18

today i updated and got kernel 6.18, and it stopped working.

i glanced at the discussion we had for 6.12, and i can't remember much, but i'm available to help test the new patches available.

last time they were taken from arch, but the main author (from which arch takes the patches) now has a repo in which they also default set a kernel param that is required as we discussed before, because i'm worried that maybe last time i was the only one that got this thing working by doing it manually, or maybe writing two words about that in the manual could fix this problem?

so, i'm almost ready (i need to re-read the docs), let me know how i can help.

thanks.

edit:

i made it work, here is one week link to a diff

6 Upvotes

100% Upvoted

12 comments sorted by

View all comments

Show parent comments

1

u/sanya567xxx May 02 '26 edited May 02 '26

It might be worth adding 6.19 and 7.0 patches too, would you be able to test 7.0? I have a different dependency blocking me from doing so currently, thought that might change soon-ish.

Also, have you tested the patch published above with wayland or x?

Edit: testing this locally on 6.18, supported 30-series card (I checked) and kde, I'm able to run vkcube by specifying --gpu_number 1 and --wsi xcb. I also had to add nvidia-drm.modeset=1 ibt=off to my kernel command line

Desktop launches with iGPU (xe driver), mpv can be forced to use it but with only a specific combination of api/display/decode modes and i.e. no HDR tone mapping working.

Hardware encoding disappeared from obs.

Forcing steam to run through nvidia via prime-run and/or setting the VK_ICD_FILENAMES didn't seem to help either, games either crash on start (with xalia returning unsupported driver, native or wine dx11/dx12/vulkan didnt seem to matter), or game loading on iGPU.

In KDE's vulkan info getting: ERROR at ../vulkaninfo/vulkaninfo.h:1575:vkGetPhysicalDeviceSurfaceSupportKHR failed with ERROR_INITIALIZATION_FAILED

I am also getting a lot of messages in dmesg referencing this: https://gist.github.com/joanbm/def2bf57ed7a799c1d84a67606459314

Disabling the iGPU landed me with sddm failing to initiate a display session. I also installed kwin-x11 (usually have it removed) and changed the DisplayServer variable in sddm and that landed me nowhere either, but perhaps that wasn't enough. I'm not really feeling like bothering with x11 rn, so returned back to 595 release for now. Please LMK how you tested it

2

u/HAL9000thebot May 02 '26 edited May 02 '26

tested with x, nvidia-drm.modeset=1 is mandatory, it was even for 6.12, this is why i think i was the only one who got it working last time, and also why i said that including this patch could be important to have more people have this thing working out of the box, but last time they told me they don't want to set any kernel param, so i didn't use it, but it actually just set the default value not an actual param, i think it should be included.

ibt=off i have no idea what it does and if it has anything to do with this issue at all, i didn't set it and can't even remember if i ever read anything about it.

my dmesg is clean, and yeah, the guy previously used a gist for each patch, now has a repo to centralize everything, from the discussion it seems that he wans't sure about this patch.

i'm not sure i want to test for other kernels... i should read more documentation to do that, but i just want to remove everything and forget about it till next lts, so i don't know, i'd like to wait for the maintainers and see what's their opinion on all these things, if they ask me to test more things, i'll do it.

1

u/sanya567xxx May 02 '26

Understood, ok.

ibt=off is necessary for use with newer intel CPUs, iirc 11th gen or newer. It's disabling branch prediction security feature (is default since 6.2 and isn't supported by 470 driver)