The Latest NVIDIA Linux Driver Release.

mats_b_tegner · 07-07-2017, 03:25 PM

Quote:

Originally Posted by gus3

I have an old (10 yrs) GeForce chipset that isn't supported after 304. This also means I'm using kernel 4.8.x, because I can't get the driver to compile for 4.9 or later. If anyone has any tips, I'd be grateful.

For nVidia legacy drivers R304 and R340 you will need the following patch with kernel 4.9.x:
https://devtalk.nvidia.com/default/t...-4-9-onwards-/

Code:

--- kernel/nv-drm.c   2016-12-09 19:47:20.000000000 +0000
+++ kernel/nv-drm.c   2017-01-02 16:03:57.691298148 +0000
@@ -71,7 +71,11 @@
 };
 
 static struct drm_driver nv_drm_driver = {
-    .driver_features = 0,
+#if LINUX_VERSION_CODE >= KERNEL_VERSION(4, 9, 0)
+    .driver_features = DRIVER_GEM | DRIVER_PRIME | DRIVER_LEGACY,
+#else
+     .driver_features = DRIVER_GEM | DRIVER_PRIME,
+#endif
     .load = nv_drm_load,
     .unload = nv_drm_unload,
     .fops = &nv_drm_fops,

gus3 · 07-15-2017, 11:11 AM

Thank you, mats_b_tegner. The next page after the one you linked has patches for 4.11 and 4.12, plus a link to a patch for 4.10.

After doing the proper incantations, plus adding

EXPORT_SYMBOL(init_mm);

to the end of mm/init-mm.c in the kernel source and re-building, I am now watching movies on my old nVidia Geforce using kernel 4.12.1.

mats_b_tegner · 07-15-2017, 05:00 PM

Quote:

Originally Posted by gus3

Thank you, mats_b_tegner. The next page after the one you linked has patches for 4.11 and 4.12, plus a link to a patch for 4.10.

After doing the proper incantations, plus adding

EXPORT_SYMBOL(init_mm);

to the end of mm/init-mm.c in the kernel source and re-building, I am now watching movies on my old nVidia Geforce using kernel 4.12.1.

Great that you got it working. I know that additional patches are needed for kernels 4.11.x and 4.12.x but I'm still on 4.9.x myself.

Mats

cwizardone · 07-24-2017, 06:40 PM

NVIDIA has released verion 384.59 of their Long Lived Branch driver,

https://www.nvidia.com/Download/driv...x/120917/en-us

Quote:

Added support for the following GPUs:
GeForce GT 1030
GeForce MX150
Fixed a bug that prevented changes to stereo eye assignment from getting applied from the nvidia-settings control panel.
Fixed a bug that caused S4 suspend (also known as "hibernate") to hang during suspend when SLI was enabled.
Fixed a bug where devices would not be properly enumerated by the Vulkan driver. See the "Known Issues" section of the README for more details.
Fixed a bug that could cause OpenGL applications to crash after calling glDeleteBuffers on VBOs that have been remapped with ARB_vertex_attrib_binding.
Fixed a bug that could sometimes cause OpenGL applications to lock up until the X server receives input.
Fixed a bug that caused nvidia-settings to drop device BusID values when making changes to an existing X configuration file.
Fixed a regression that prevented nvidia-xconfig from querying some GPUs, e.g. when running `nvidia-xconfig -a`.
Fixed a bug that caused VDPAU playback to be corrupted when extended to coordinates beyond 16384 pixels.
Updated nvidia-persistenced to initialize nvidia-modeset.ko in addition to nvidia.ko when setting persistence mode.
Restored several sanity checks that were inadvertently removed from the kernel module build process in the 355.06 driver.
Added support for a "Nearest" transform filter in the X driver. This causes the X driver to use nearest neighbor filtering when performing screen transformations. The filter can be requested through the 'filter' argument to RandR's RRSetCrtcTransform, or through the 'ResamplingMethod' MetaMode token.
Fixed a bug where nvidia-installer would install a wrong version of the Vulkan ICD configuration file when GLVND is disabled for the GLX client.
Fix a bug with GLX_EXT_buffer_age where incorrect buffer age values would be reported for SLI AFR configurations. In such configurations buffer age may now be greater than 3, the previous maximum buffer age.
Fixed a bug that could cause hanging and Xids when performing RandR transforms with Overlay and SLI enabled.
Extended the information reported by the NVIDIA Xinerama X extension to report PRIME displays in addition to directly-connected displays.
Fixed a bug that caused HDMI audio devices to appear or disappear inconsistently when HDMI devices were hotplugged or unplugged.
Fixed a bug that could cause driver errors when setting modes on X screens running at Depth 8 or Depth 15.
Fixed a bug that could cause intermittent kernel panics when running with PRIME Sync.
Fixed a bug that caused a kernel panic when hotplugging HDMI displays on some Zotac mini PCs.
Updated nvidia-installer to label kernel modules with SELinux file type 'modules_object_t'. Some system SELinux policies only permit loading of kernel modules with this SELinux file type.
Removed support for checking for and downloading updated driver packages and precompiled kernel interfaces from nvidia-installer. This functionality was limited to unencrypted ftp and http, and was implemented using code that is no longer actively maintained.

Their list of UNIX drivers,

https://www.nvidia.com/object/unix.html

kjhambrick · 07-24-2017, 06:48 PM

Woo Hoo !

Thanks cwizardone !

-- kjh

elcore · 07-26-2017, 07:15 AM

Tested the 384.59 on kernel 4.4.78 and learned a few things.

* nvidia-384.59 Xorg driver works on my machine, can read display EDID from file, and supports a number of native resolutions.
* nvidia-persistenced-384.59 works too, I just renamed the template to rc.nvidia-persistenced & set user and group manually accoring to documentation.
* nvidia-modeset is now used for switch to VT and it doesn't work on my machine, nvidia-modeset cannot read display EDID from file and the monitor doesn't provide one.
* nvidia-modeset can only switch to VT properly if vga=normal is passed to the kernel, in case vesafb driver is used on VT then nvidia-modeset turns off the monitor.
* nvidia-drm is still experimental, and doesn't work on my machine. Video mode and drm_kms_helper.edid_firmware is ignored by nvidia-drm, this only works properly with nouveaufb.

There's regression there somewhere, because on legacy 340 series it's possible to pass video=vesafb:1024x768 and use that resolution for VT.
While on 384 series the only available mode is vga=normal which is unsuitable for my hardware, it renders beyond display borders making it useless.

kjhambrick · 07-26-2017, 08:05 AM

Thanks for the report elcore.

Sounds like a Saturday task for my work Laptop

-- kjh(

not something I would want to try on a 'workday'

)

cwizardone · 07-26-2017, 10:10 AM

Quote:

Originally Posted by elcore

Tested the 384.59 on kernel 4.4.78 and learned a few things....

Many thanks for the feedback. What NVIDIA GPU are you using?

elcore · 07-26-2017, 10:55 AM

0x0de0 Gigabyte GeForce GT 440 1024M DDR3 VBIOS 70.08.4d.00.00

I'm surprised it even works on this setup to be honest, because the board is about 2 years behind the card and the monitor is even older.
Figured there's zero chance anyone from NVIDIA has a LCD monitor which doesn't expose EDID, they even mark with [CRT] anything connected to VGA port.
So I don't even bother reporting it to them, and use the legacy branch with vesafb.

ajohn · 07-26-2017, 11:07 AM

Quote:

Originally Posted by gus3

I have an old (10 yrs) GeForce chipset that isn't supported after 304. This also means I'm using kernel 4.8.x, because I can't get the driver to compile for 4.9 or later. If anyone has any tips, I'd be grateful.

I can't help you with a link but I stumbled over a page on nvidia's site where the card number is entered and it selects the driver for it. This was a few months ago so should still be about. I'm not sure what kernel versions they check against but would suspect only latest stable.

John
-

cwizardone · 07-31-2017, 10:22 AM

NVIDIA has released a new BETA driver with OpenGL 4.6 support.

https://developer.nvidia.com/opengl-driver

Quote:

...Please note these drivers are for developers who want to experiment with “OpenGL 4.6”. Other developers and consumers should download drivers from http://www.nvidia.com/Download/index.aspx. The best way to stay up to date with drivers and other news from NVIDIA is to install GeForce Experience...

RadicalDreamer · 07-31-2017, 11:42 AM

I was wondering if they were going to continue development of OpenGL after introducing Vulkan.

Regnad Kcin · 07-31-2017, 06:30 PM

I have used the 384.47 driver in Slackware-64-current -multilib on two different machines with geforce 960 cards and it works great.

The Nouveau drivers yield screen tearing and other glitches in the same systems.

Pixxt · 07-31-2017, 07:03 PM

Quote:

Originally Posted by RadicalDreamer

I was wondering if they were going to continue development of OpenGL after introducing Vulkan.

It would not be wise for them not to as Vulkan is much harder to program for and you need to write much more code in Vulkan than for OpenGL.

enorbet · 07-31-2017, 09:06 PM

Quote:

Originally Posted by Pixxt

It would not be wise for them not to as Vulkan is much harder to program for and you need to write much more code in Vulkan than for OpenGL.

For now....