-
Notifications
You must be signed in to change notification settings - Fork 27
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
32 bit ICD loading seems broken as of 570.86.16 #173
Comments
Thanks for reporting.
Doh, this is interesting, because it's what the other drivers are doing:
And they are following the same approach for both 32 and 64 bit by listing the library with the full path:
|
One single ICD ( https://github.com/negativo17/nvidia-driver/blob/master/nvidia-driver.spec#L203-L205 |
In fact I don't have this issue on Fedora:
Even with a quite old
|
Ah no, wait, you're on Bazzite/Fedora 41 and you are attempting to use a
Please try again with the one from Fedora 41, I'm sure it will work. You can also install it directly on an
|
Nope, same issue with that one:
It's very possible there's something wrong with my build here (I'm using a bazzite/silverblue variant, and the |
This is strange:
Can you do a |
This is strange if that's the output of 32 bit vulkaninfo, it should not hit that file:
I can't reproduce it on my system. |
which is what I'd expect - the 32 bit libraries are there, but the loader is only trying to load the one from |
Ah, interestingly if I force the
So it does appear to be an ICD path thing, if I don't force it, the loader won't find |
Oh good grief.
I don't remember adding that at all, but that is (obviously) the problem and that (obviously) fixed it. PEBKAC. Apologies for the noise. TYVM for the work you do. |
😄 No worries, it's good to check if we're not sure. Thanks. |
VK_LOADER_DEBUG=all
shows thatvulkaninfo32
never tries to load thei686
icd, it just tries to load the x86_64 one (which throws an ELF mismatch error as it's the wrong type)I notice that the nvidia flatpak extensions recently stopped installing 2x
icd
s here: flathub/org.freedesktop.Platform.GL.nvidia@d55b7cb (the above stuff was all done outside of a flatpak, but that's where I first noticed the failure and ultimately ended up reproducing the issue outside of a flatpak env).I also notice that at one point, a PR was done to the
.spec
file to use a single ICD: #95but this was reverted.
Did something change recently? Should one ICD be used here?
The text was updated successfully, but these errors were encountered: