NVIDIA 364.12 release: Vulkan, GLVND, DRM KMS, and EGLStreams
Can you please confirm that "Support for Vulkan" includes Fermi (GTX 400/500 series) class GPUs? By my reading of the documentation I'm ecstatic.
Can you please confirm that "Support for Vulkan" includes Fermi (GTX 400/500 series) class GPUs? By my reading of the documentation I'm ecstatic.

#16
Posted 03/22/2016 02:19 AM   
No, Fermi is not supported by the Vulkan driver at this time.
No, Fermi is not supported by the Vulkan driver at this time.

Aaron Plattner
NVIDIA Linux Graphics

#17
Posted 03/22/2016 04:13 AM   
Even with "options nvidia-drm modeset=1" instead of nvidia_drm in my modprobe.d/*.conf it doesn't apply the parameter at boot. I even added this file to my initramfs and it should be picked up by the modconf hook in mkinitcpio on Arch. I noticed that I can use both nvidia-drm and nvidia_drm, when I manually load the module. I first thought that it might be a typo in the README, because the module is called nvidia_drm. I'm out of ideas at this point.
Even with "options nvidia-drm modeset=1" instead of nvidia_drm in my modprobe.d/*.conf it doesn't apply the parameter at boot. I even added this file to my initramfs and it should be picked up by the modconf hook in mkinitcpio on Arch. I noticed that I can use both nvidia-drm and nvidia_drm, when I manually load the module. I first thought that it might be a typo in the README, because the module is called nvidia_drm. I'm out of ideas at this point.

#18
Posted 03/22/2016 08:22 AM   
Hello! I remember that GLvnd wasn't enabled by default in 361.xx driver. I think, few applications had check "if "GLX vendor" is NVIDIA, then that code, else another code". Now NVIDIA check had success, but the special code isn't needed anymore. And application is failing. So I remember Windows NT history. In 4.0, it haven't much of components. Games released in 90th had check of WinNT. Then in WinNT 5.0 all components were added, an old games weren't start anyway. http://www.microsoft.com/library/media/1033/technet/images/prodtechnol/winxppro/maintain/lgcya01_big.gif Did you remember that? This is just changing useragent of OS! Just make something that: [code]__GL_OLD_APP=1 ./limbo.x86[/code]
Hello! I remember that GLvnd wasn't enabled by default in 361.xx driver. I think, few applications had check "if "GLX vendor" is NVIDIA, then that code, else another code". Now NVIDIA check had success, but the special code isn't needed anymore. And application is failing.

So I remember Windows NT history. In 4.0, it haven't much of components. Games released in 90th had check of WinNT. Then in WinNT 5.0 all components were added, an old games weren't start anyway.


http://www.microsoft.com/library/media/1033/technet/images/prodtechnol/winxppro/maintain/lgcya01_big.gif


Did you remember that? This is just changing useragent of OS! Just make something that:

__GL_OLD_APP=1 ./limbo.x86

#19
Posted 03/22/2016 08:42 AM   
Kudos and thanks for the continued support, guys! Being a Fedora user I'm glad to see improvements on the EGL/Wayland front, even though there is still some ground to cover. Looking forward for the next releases!
Kudos and thanks for the continued support, guys! Being a Fedora user I'm glad to see improvements on the EGL/Wayland front, even though there is still some ground to cover. Looking forward for the next releases!

#20
Posted 03/22/2016 11:08 AM   
That's great news. Thank you guys for your hard work!
That's great news. Thank you guys for your hard work!

#21
Posted 03/22/2016 11:13 AM   
Hi devs Ctl+Alt+F1 works Ctl+Alt+F7 does not . it hangs on black screen . wakeup from suspend does not work . PS : with the driver 355-11 everything works . another issue / trying to stop X with "sudo service lightdm stop" i got this message / nvidia-modeset : ERROR: GPU-0:Idling EVO timedout :0x0000907d:0:0:0x00000 NMI watchdog: BUG: Softlockup .... cannot switch to old driver 355-11 because of this Bug . Anyhelp please ? Thank you Mounir
Hi devs
Ctl+Alt+F1 works
Ctl+Alt+F7 does not . it hangs on black screen .

wakeup from suspend does not work .
PS : with the driver 355-11 everything works .


another issue /
trying to stop X with "sudo service lightdm stop" i got this message /
nvidia-modeset : ERROR: GPU-0:Idling EVO timedout :0x0000907d:0:0:0x00000
NMI watchdog: BUG: Softlockup ....



cannot switch to old driver 355-11 because of this Bug .

Anyhelp please ?

Thank you

Mounir

#22
Posted 03/22/2016 01:12 PM   
[quote=""]Hi devs Ctl+Alt+F1 works Ctl+Alt+F7 does not . it hangs on black screen . wakeup from suspend does not work . PS : with the driver 355-11 everything works . another issue / trying to stop X with "sudo service lightdm stop" i got this message / nvidia-modeset : ERROR: GPU-0:Idling EVO timedout :0x0000907d:0:0:0x00000 NMI watchdog: BUG: Softlockup .... cannot switch to old driver 355-11 because of this Bug . Anyhelp please ? Thank you Mounir[/quote] I have the same problem when stoping lightdm. You can bypass that by uninstalling drivers with "sudo nvidia-uninstall", then reboot the system, get into TTY, stop lightdm and install the drivers. I know that is not the solution, but for now it is like that. I had that problem with every 36x.xx driver.
said:Hi devs
Ctl+Alt+F1 works
Ctl+Alt+F7 does not . it hangs on black screen .

wakeup from suspend does not work .
PS : with the driver 355-11 everything works .


another issue /
trying to stop X with "sudo service lightdm stop" i got this message /
nvidia-modeset : ERROR: GPU-0:Idling EVO timedout :0x0000907d:0:0:0x00000
NMI watchdog: BUG: Softlockup ....



cannot switch to old driver 355-11 because of this Bug .

Anyhelp please ?

Thank you

Mounir



I have the same problem when stoping lightdm.
You can bypass that by uninstalling drivers with "sudo nvidia-uninstall", then reboot the system, get into TTY, stop lightdm and install the drivers. I know that is not the solution, but for now it is like that. I had that problem with every 36x.xx driver.

#23
Posted 03/22/2016 02:08 PM   
thank U Milos_SD , I installed the 355-11 via synaptic . it works like a charm .
thank U Milos_SD ,
I installed the 355-11 via synaptic . it works like a charm .

#24
Posted 03/22/2016 02:14 PM   
[quote="aritger"]For the fbdev question: yes, that is something we hope to provide eventually.[/quote] Oh, that's nice to hear. I figured nvidia has no reason to care about fbdev. But if you implement it, it'll for sure make some people happy.
aritger said:For the fbdev question: yes, that is something we hope to provide eventually.

Oh, that's nice to hear. I figured nvidia has no reason to care about fbdev. But if you implement it, it'll for sure make some people happy.

#25
Posted 03/22/2016 03:02 PM   
[quote=""]Even with "options nvidia-drm modeset=1" instead of nvidia_drm in my modprobe.d/*.conf it doesn't apply the parameter at boot. I even added this file to my initramfs and it should be picked up by the modconf hook in mkinitcpio on Arch. I noticed that I can use both nvidia-drm and nvidia_drm, when I manually load the module. I first thought that it might be a typo in the README, because the module is called nvidia_drm. I'm out of ideas at this point. [/quote] Yes this is quite weird as there's no real feedback but it works (through kernel parameter nvidia-drm.modeset=1 for me). Keep in mind this is a very barebones KMS support so there's no high resolution console or flicker-free VT switch. I found out the only way to know KMS is enabled is if these lines are present in the journal : [code][drm] Supports vblank timestamp caching Rev 2 (21.10.2013). [drm] No driver support for vblank timestamp query. [/code] As they don't appear if I boot without nvidia-drm.modeset=1. Anyways I managed to run the patched weston and a few Wayland applications so I guess I got it right. Here's a screenshot : http://i.imgur.com/skSQjd7.png I also tried to run X with the modesetting driver. It works but is quite slow and buggy (KDE plasma crashes).
said:Even with "options nvidia-drm modeset=1" instead of nvidia_drm in my modprobe.d/*.conf it doesn't apply the parameter at boot. I even added this file to my initramfs and it should be picked up by the modconf hook in mkinitcpio on Arch. I noticed that I can use both nvidia-drm and nvidia_drm, when I manually load the module. I first thought that it might be a typo in the README, because the module is called nvidia_drm. I'm out of ideas at this point.


Yes this is quite weird as there's no real feedback but it works (through kernel parameter nvidia-drm.modeset=1 for me). Keep in mind this is a very barebones KMS support so there's no high resolution console or flicker-free VT switch.
I found out the only way to know KMS is enabled is if these lines are present in the journal :

[drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[drm] No driver support for vblank timestamp query.


As they don't appear if I boot without nvidia-drm.modeset=1.

Anyways I managed to run the patched weston and a few Wayland applications so I guess I got it right.
Here's a screenshot : http://i.imgur.com/skSQjd7.png


I also tried to run X with the modesetting driver. It works but is quite slow and buggy (KDE plasma crashes).

#26
Posted 03/22/2016 06:18 PM   
this driver fixed the the screen shifting to the right problem that all drivers since 352 series had thanks nvidia ubuntu install
this driver fixed the the screen shifting to the right problem that all drivers since 352 series had thanks nvidia ubuntu install

#27
Posted 03/22/2016 07:14 PM   
Hello. I have a GTX 260. I'm not asking for Vulkan, I know it's a feature that really requires present hardware. But do you plan to release Wayland support on legacy driver for some GPU chips?
Hello.

I have a GTX 260.

I'm not asking for Vulkan, I know it's a feature that really requires present hardware.


But do you plan to release Wayland support on legacy driver for some GPU chips?

#28
Posted 03/22/2016 07:20 PM   
No, we have no plans to backport the new support to the legacy branches. The legacy branches get critical fixes and support for new kernels and X servers only.
No, we have no plans to backport the new support to the legacy branches. The legacy branches get critical fixes and support for new kernels and X servers only.

Aaron Plattner
NVIDIA Linux Graphics

#29
Posted 03/22/2016 11:49 PM   
After nvidia-drm has been loaded with modeset=1, attempting to run weston-launch outputs the following error in the journal: [code] [ 5338.262318] vgaarb: device changed decodes: PCI:0000:02:00.0,olddecodes=none,decodes=none:owns=io+mem [ 5338.262416] nvidia-nvlink: Nvlink Core is being initialized, major device number 250 [ 5338.262437] NVRM: loading NVIDIA UNIX x86_64 Kernel Module 364.12 Wed Mar 16 21:11:26 PDT 2016 [ 5338.263459] nvidia-modeset: Loading NVIDIA Kernel Mode Setting Driver for UNIX platforms 364.12 Wed Mar 16 20:44:12 PDT 2016 [ 5338.263950] [drm] [nvidia-drm] [GPU ID 0x00000200] Loading driver [ 5338.824705] nvidia-modeset: Allocated GPU:0 (GPU-595b3d36-aaea-d916-d4ce-4efa80c7c223) @ PCI:0000:02:00.0 [ 5338.886475] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). [ 5338.886476] [drm] No driver support for vblank timestamp query. [ 5350.257392] [drm:nvidia_drm_gem_import_nvkms_memory [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000200] Failed to import NVKMS memory to GEM object [/code] [b]Failed to import NVKMS memory to GEM object[/b] -- What could I have missed?
After nvidia-drm has been loaded with modeset=1, attempting to run weston-launch outputs the following error in the journal:

[ 5338.262318] vgaarb: device changed decodes: PCI:0000:02:00.0,olddecodes=none,decodes=none:owns=io+mem
[ 5338.262416] nvidia-nvlink: Nvlink Core is being initialized, major device number 250
[ 5338.262437] NVRM: loading NVIDIA UNIX x86_64 Kernel Module 364.12 Wed Mar 16 21:11:26 PDT 2016
[ 5338.263459] nvidia-modeset: Loading NVIDIA Kernel Mode Setting Driver for UNIX platforms 364.12 Wed Mar 16 20:44:12 PDT 2016
[ 5338.263950] [drm] [nvidia-drm] [GPU ID 0x00000200] Loading driver
[ 5338.824705] nvidia-modeset: Allocated GPU:0 (GPU-595b3d36-aaea-d916-d4ce-4efa80c7c223) @ PCI:0000:02:00.0
[ 5338.886475] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[ 5338.886476] [drm] No driver support for vblank timestamp query.
[ 5350.257392] [drm:nvidia_drm_gem_import_nvkms_memory [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000200] Failed to import NVKMS memory to GEM object


Failed to import NVKMS memory to GEM object -- What could I have missed?

#30
Posted 03/23/2016 07:55 PM   
Scroll To Top

Add Reply