Thanks a ton generix, this patchmade it.
https://pastebin.com/yPZ1tEwb
For later driver versions refer to this thread:
https://devtalk.nvidia.com/default/topic/1044851/linux/fyi-nvidia-410-78-driver-fails-with-segmentation-fault-on-fedora-fc29-workstation-with-nvs-510-card/post/5301228/#5301228
Which driver version?
I’ve had no problems with 4.19 (+ driver 410.78, aka what’s currently in Fedora) that weren’t there before (stuff like HDMI sound gone since 4.17 or that it stays in P0/P2 for 45 seconds after clicking a link in Chrome). I could say “nothing works” but it didn’t work prior to 4.19, so I don’t see how this is any different :)
something in the Kernel changed, i dont know :/
tried 396.54.09, 410.78 and 415.13 on kernel 4.19*, both installed correct but not working after reboot.
ya i know … read the effing logs and such, but what if im just a clueless casual ?
i want use the 396.54.09 for Vulkan 1.1.85 but ive read its not supported anymore.
atm im using that under kernel 4.18, works great.
Due to this thread https://www.if-not-true-then-false.com/2015/fedora-nvidia-guide/ ive learned that Kernel 4.19 changed things and we got to patch our drivers to make it work.
Their patched 390.87 driver ( https://www.if-not-true-then-false.com/2015/fedora-nvidia-guide/4/#download-nvidia-patched-installer ) is 100 years old but works actually under kernel 4.19 - the only driver ever worked on that kernel here yet, no other driver is working, not from Fedora rawhide repo nor from Nvidia.
I also tried to patch 396.54.09 with the given patches, had to manually add
#if LINUX_VERSION_CODE >= KERNEL_VERSION(4,3,0)
#undef CONFIG_MTRR
#endif
but its the same like the other drivers before, no gfx, driver is not working.
What is MTRR ?
Installing 396.54.09 on Kernel 4.18 works fine.
Installing that patched 390.87 on Lernel 4.19 works fine.
Everything else failed.
/welp
Rawfox, the 396.54.09 driver has never been an official release but a ‘developer preview’, so there’s nothing to complain if it stops working.
The current 410 and 415 are working fine with kernel 4.19. The difference is that those drivers have a changed layout, so if you previously broke your GL(X) setup, this will now surface and nothing works. This is what I’m suspecting is happening to you right now, see this:
https://devtalk.nvidia.com/default/topic/1044485/linux/two-systems-with-4k-monitors-connected-via-display-port-are-incorrectly-detecting-the-monitors-as-non-dri-capable-on-both-410-78-and-415-18-they-were-correctly-detected-on-396-54/
Generix has provided a patch to me and i could patch the 396.54.09 to make my hair shine great again on Kernel 4.19, but …
The option of a broken GL/x is an interresting hint, ill follow up on that, thanks for some direction \m/
IIRC, this kind of failure so far has only been reported by users of Fedora 29. So while it works for most F29 users, there seems to be something specific to F29 glvnd/glxvnd which is prone to breakage. Didn’t dig deeper into this, though.
The most recent fresh install here was Fedora25.
From then its only updated, there can be ofcause some kind of mess, leftovers from the stoneage … cool bandname tho
I think ill find it once i get the 410/415 drivers working.
Ya, Fedora is known for “innovations” …
The glvnd stuff normally breaks when a user is dumb enough to use the .run file.
Can you validate your claim that fedora libglvnd is broken?, currently there are no open reports against libglvnd!
I did not claim that Fedora is broken in general but since this so far only happened to Fedora users, there seems to be something specific to it. Might also be leftovers from the glvnd mess with F25 which now surface in some cases, maybe depending on upgrade path, IDK.
Explain to me, how else we can get up2date drivers ?
Its the Kernel changes that have not been respected by Nvidia, i doubt its a distro thing.
Ive seen the reports first from Fedora users, but there is a good chunk of Ubuntu’s and Arch’s reporting similar issues.
libglvnd is version 1.1.0 here.
You guys like my new sig ?^^
rpmfusion has 410.78 in all stable releases and if that isn’t new enough there is 415.18 in rawhide repo which can be used on stable releases.
It’s easy to blame nvidia, perhaps you should look in the mirror for the real reason!
I wouldn’t expect anything else from a PICNIC :-)
Playing the blame-game does not really help anyone. Why not start investigating what exactly broke starting with something as simple as
ls -l /usr/lib/libGL*
and compare that with the expected layout of a Fedora system?
[rawfox@operator ~]$ ls -l /usr/lib/libGL*
lrwxrwxrwx. 1 root root 22 16. Aug 21:04 /usr/lib/libGLdispatch.so -> libGLdispatch.so.0.0.0
lrwxrwxrwx. 1 root root 22 16. Aug 21:04 /usr/lib/libGLdispatch.so.0 -> libGLdispatch.so.0.0.0
-rwxr-xr-x. 1 root root 334264 16. Aug 21:04 /usr/lib/libGLdispatch.so.0.0.0
lrwxrwxrwx. 1 root root 32 25. Nov 20:56 /usr/lib/libGLESv1_CM_nvidia.so.1 -> libGLESv1_CM_nvidia.so.396.54.09
-rwxr-xr-x. 1 root root 47316 25. Nov 20:56 /usr/lib/libGLESv1_CM_nvidia.so.396.54.09
lrwxrwxrwx. 1 root root 21 16. Aug 21:04 /usr/lib/libGLESv1_CM.so -> libGLESv1_CM.so.1.2.0
lrwxrwxrwx. 1 root root 21 16. Aug 21:04 /usr/lib/libGLESv1_CM.so.1 -> libGLESv1_CM.so.1.2.0
-rwxr-xr-x. 1 root root 41396 16. Aug 21:04 /usr/lib/libGLESv1_CM.so.1.2.0
lrwxrwxrwx. 1 root root 29 25. Nov 20:56 /usr/lib/libGLESv2_nvidia.so.2 -> libGLESv2_nvidia.so.396.54.09
-rwxr-xr-x. 1 root root 84180 25. Nov 20:56 /usr/lib/libGLESv2_nvidia.so.396.54.09
lrwxrwxrwx. 1 root root 18 16. Aug 21:04 /usr/lib/libGLESv2.so -> libGLESv2.so.2.1.0
lrwxrwxrwx. 1 root root 18 16. Aug 21:04 /usr/lib/libGLESv2.so.2 -> libGLESv2.so.2.1.0
-rwxr-xr-x. 1 root root 65968 16. Aug 21:04 /usr/lib/libGLESv2.so.2.1.0
-rw-r–r--. 1 root root 660 25. Nov 20:56 /usr/lib/libGL.la
lrwxrwxrwx. 1 root root 14 16. Aug 21:04 /usr/lib/libGL.so -> libGL.so.1.7.0
lrwxrwxrwx. 1 root root 14 16. Aug 21:04 /usr/lib/libGL.so.1 -> libGL.so.1.7.0
-rwxr-xr-x. 1 root root 414448 16. Aug 21:04 /usr/lib/libGL.so.1.7.0
lrwxrwxrwx. 1 root root 15 19. Jul 21:07 /usr/lib/libGLU.so -> libGLU.so.1.3.1
lrwxrwxrwx. 1 root root 15 19. Jul 21:07 /usr/lib/libGLU.so.1 -> libGLU.so.1.3.1
-rwxr-xr-x. 1 root root 544204 19. Jul 21:07 /usr/lib/libGLU.so.1.3.1
lrwxrwxrwx. 1 root root 26 25. Nov 20:56 /usr/lib/libGLX_indirect.so.0 -> libGLX_nvidia.so.396.54.09
lrwxrwxrwx. 1 root root 20 6. Nov 00:36 /usr/lib/libGLX_mesa.so.0 -> libGLX_mesa.so.0.0.0
-rwxr-xr-x. 1 root root 555920 6. Nov 00:38 /usr/lib/libGLX_mesa.so.0.0.0
lrwxrwxrwx. 1 root root 26 25. Nov 20:56 /usr/lib/libGLX_nvidia.so.0 -> libGLX_nvidia.so.396.54.09
-rwxr-xr-x. 1 root root 1138396 25. Nov 20:56 /usr/lib/libGLX_nvidia.so.396.54.09
lrwxrwxrwx. 1 root root 15 16. Aug 21:04 /usr/lib/libGLX.so -> libGLX.so.0.0.0
lrwxrwxrwx. 1 root root 15 16. Aug 21:04 /usr/lib/libGLX.so.0 -> libGLX.so.0.0.0
-rwxr-xr-x. 1 root root 79188 16. Aug 21:04 /usr/lib/libGLX.so.0.0.0
lrwxrwxrwx. 1 root root 25 6. Nov 00:36 /usr/lib/libGLX_system.so.0 -> /usr/lib/libGLX_mesa.so.0
Oh right, now i see that guy that has not changed the Kernel and has not corrected mishaps to the Nvidia drivers. Man man, you are a special pleb. At least that guy in the mirror would not put green fonts on a white background ^^
When you look in the mirror, you can clearly see that guy, that aint read about those drivers not working here.
Is my GL libs okay ? … i mean, im totally not responsible for Fedora builds, updates, Kernelchanges or Nvidia drivertweaks … nwm, the last aint happened anyways xD
Help me getting the 410/415 going here and we may help others to solve the same issue.
… and please dont take everything so serious ^^
Perhaps you should read the forum sticky https://devtalk.nvidia.com/default/topic/522835/linux/if-you-have-a-problem-please-read-this-first/
As for helping you, I will take a pass on that.
This ‘special pleb’ has better things to do with his time.
Ya, we dont come together, im just that dumb user using the .run file while you have all those “i am important” badges … lol.
You also take everything total serious :(
There is not a smallest flatulence of empathy and your contribution to solve not only my angry behavior, but the problem with the drivers as well, was kinda zero.
Its not always compatible between people.
I had error “BUG: unable to handle kernel NULL pointer dereference at 0000000000000080” when tried to start some applications.
All works fine on my computer, after i installed Fedora kernel 4.19.5 from test repos (they applied patch https://lore.kernel.org/patchwork/patch/1015988/ )
P.S. i’m not sure you have same issue as mine, but maybe it will help
Thanks for giving another hint.
We had a glibc update, i thought it would solve it but it failed as well.
Ill wait for 4.19.5 being in updates and try again then.
Im still using the patched 396.54.09 on 4.19* kernels but there is a new Vulkan driver 415.18.02 i would want to use.
I hope that new kernel will finally fix things.
Thanks tho ^^