The Latest NVIDIA Linux Driver Release.
 

I started this topic,
https://www.linuxquestions.org/quest...-a-4175572087/

a long time ago and thought a new thread for Slackware users would be more appropriate than adding to an old thread.

NVIDIA has released a new "Long Lived Branch version," 384.47.

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

It is marked as "beta," but is working fine.... so far, with Slackware64-current.
:)

A list of their Unix/Linux Drivers,

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

I am using 381.09 with Nvidia gtx 1050
dont see a reason to go bleeding edge on drivers anymore. maybe if I had a 1080 and was doing hardcore HD gaming. But I cannot afford to.

I'm still using the latest stable, 375.66. I don't like to use their beta drivers, as i have played multiplayer games in the past where i would get crashes on occasion, resulting in me getting killed or losing items etc, where reverting to the stable driver doesn't trigger those crashes.

I always check this for the latest drivers:
But seems i'm still using the latest release for now.

What is the difference between short and long lived branches?

I reverted from NVIDIA-Linux-x86_64-381.09.run back to NVIDIA-Linux-x86_64-375.66.run a few Kernel Updates ago.

NVIDIA-Linux-x86_64-381.09.run seemed to work fine except that it concerned me that I didn't see the reassuring NVidia Splash Screen after typing: startx from my runlevel 3 bash prompt.

Staying with NVIDIA-Linux-x86_64-375.66.run for the time being ...


coralfang --

Thanks for the curl command !

Very nice, very clean, very easy !

-- kjh

FWIW I'm a rather avid gamer especially since my stroke a few years ago as it is good exercise for the brain/body connection. I learned a long time ago that while it's nice to have max graphics since it is so much easier for game developers to crank up the candy than it is to actually create a game worth playing, gameplay comes first so I don't worry about AAA titles with maxed out graphics or 3D Mark scores. I'm currently and for a few years now using an nVidia GTX-760 since it has been my policy of buying a mid $200 USD card once every 5-7 years.

Most gamers would consider my monitor crap as it is a 32 inch Vizio Smart TV that fakes 120Hz but does deliver a decent 1080p. These are sufficient for me with the most recent AAA game I've played being Deus Ex: The Human Revolution which after a bit of tweaking played very well. Soon I will try the newest 2017 release. Deus Ex: Mankind Divided, largely because I not only enjoy the series but a Native Linux version has been released, even before a Mac version. It's currently being offered through Steam at a large discount and I want to provide support for Gabe Newell's efforts which seem to have borne fruit in encouraging Native Linux versions.

I have been happily using 378.09 for some time now but within the next couple weeks will try this latest Deus Ex first with my current driver and then with this long lived Beta. I've experienced very good results with nVidia Beta drivers in the past even on aging hardware and expect similar results now. I'll report back my experiences soon.

A problem I was having with Wine after updating the multilib files turned out to be caused by the new "Long Lived Branch version," 384.47.
After reverting to the 375.66 'Long Lived" driver the problem disappeared.

I'm still with 352.63 from 14.1 Slackbuilds.. Wonder if the release mentioned here fixes it my issues.. (my G-SYNC monitor always lid is always red indicating G-SYNC is ON even thought it's not _on 375 drivers_ - older drivers - it's white) (And yeah it's white in Windows... with latest drivers)

edit: mention broken driver version

One could say it is similar to the difference between "stable" vs.
"current," i.e., the NVIDIA "short lived" driver is the "cutting edge" development series and the "long lived" is the stable, production ready release.

Reporting Back - Well while my results may be somewhat helkpful to some they are not definitive due to the above mentioned combination of new nVidia driver and Steam. I installed the LT Beta mentioned here via nVidia's own installer and everything went well, except for Steam. The base SteamApp worked but was considerably slower than what it was apparently built around and Deus Ex" Mankind Divided wouldn't launch. It had launched but loaded rather agonizingly slowly with 378.09 but balked at 384.47. I dropped back to the Steam recommended 367.57 and it ran better. Oddly the load, though better, is still very slow but the game itself, once loaded, runs great and looks amazing. I have no idea why a newer version presents any problems at all to Steam, but hopefully they will update before too long. In any case, other than this late 2016 Native Linux game ON STEAM (I used Steam because it was so much cheaper than local install) the 384.47 LT Beta worked perfectly for my GTX 760.

Thanks! I've been using the short lived driver without any problems.

Correction:

Latest Long Lived Branch version: 375.66
Latest Short Lived Branch version: 381.22

LLB are now posted to SBO.

I second enorbet's statements. I, too, game extensively, more than I should probably since I don't have a good excuse, on linux native Steam, GOG.com and Humblebundle.com, as well as WINE (and DOSBOX, but retro is a whole nuther addiction...). Also, being on a budget I also, stick with GPUs in the 200-250 range. While eye candy is nice, game play design and stability is paramount. For linux especially, sticking with the Long Lived Branch is highly recommended. The beta's can be trouble in Steam and WINE.

Having followed gaming GPUs since 3DFX Voodoo, the whole eye candy speed spec thing reminds me of the muscle car days in high school: guys bragged extensively about their hp and 1/4 mile etc etc but the car rarely left the garage. You see, the national speed limit was 55mph so you still didn't get anywhere any faster, and gas prices put you in the poor house just driving around the block (70s oil "crisis"), and all those fancy upgrades weren't cheap so you had too work overtime at the burger joint etc. I got far more beach time in then those guys!

Moral: the hardware/drivers you can actually use are better than trouble shooting the bleeding edge (no matter how "photo-realistic"). My 2 cents.

At the time I posted the first message in this topic, the information in that post was correct. I double and triple checked it as I thought it odd a "beta" driver was listed as the "Long Lived Branch" driver. It stayed like that for a day so before the page reverted back to the 375.66 release.

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-/

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

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

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


Their list of UNIX drivers,

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

Woo Hoo !

Thanks cwizardone !

-- kjh

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.

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' :) )

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

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.

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
-

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

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

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

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.

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....

The article is here, https://www.phoronix.com/scan.php?pa....13-NVIDIA-384

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

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

NVidia has released a new beta driver to support the latest Vulkan changes,

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

@cwiz-
The "new beta" is
NVIDIA-Linux-x86_64-381.26.17
but the "older" long-lived branch driver is
-384.69

What do their version numbers mean?


*

"What does it all mean, Mr. Natural?"

You might search the forum on the Nvidia web site. IIRC, this question has been asked before.

NVida has updated two of its Legacy drivers to support newer Linux kernels.

Drivers 304.137 and 340.104 can be found at,

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

This driver not working any movie (h264 or hvec) in my 970gtx, i need to use .59 to work again.

Working just fine for me. GTX 970, MPV with vdpau for both output and decoding.

Installed 340.104 on 32bit kernel 4.4.88 works fine.

NVidia has released Long Lived Branch version 384.90.

http://www.nvidia.com/download/drive...x/123918/en-us


Release highlights:
Their list of drivers, http://www.nvidia.com/object/unix.html

Installed and working just fine on my hardware.

NVidia has released a new beta version of their Vulkan Driver,

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

For those who like to be on the leading (bleeding) edge, :)
NVidia has released their latest BETA driver, version 387.12.

The change log highlights since the release of the most recent "Long Lived Branch" can be found at,

https://devtalk.nvidia.com/default/t...-387-12-beta-/


Their current list of non-beta drivers,

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

Okay, I guess quoting yourself is not standard here, but i will do it anyway. I was stuck with 352.63 for a very long time (due to the bug mentioned above).

Turning off G-SYNC works with NVIDIA-Linux-x86_64-387.12.run. (kernel 4.9.52, slackware 14.2)

Thank you NVIDIA! :D

ULMB works like a charm!

For those of you running the new LLB NVIDIA-Linux-x86_64-384.90.run on multilib - i.e, with COMPAT32, and not the SBO script - can you post or email me the location the .run installer script puts the two libnvidia-tls.so.384.90? Slackware needs the tls/ versions. For some reason, when I run nvidia-installer in a qemu VM, lib64 has both versions, which is ok as the tls/ version gets picked and 64-bit GL apps run. However, only one 32-bit lib tls gets installed, the wrong one, and 32-bit GL apps segfault. To test, I moved /usr/lib/tls/libnvidia-tls.so.384.90 (32 bit version):
(same for LD_PRELOAD=/usr/lib/libnvidia-tls.so.384.90), and
This has been driving me nuts for the past 24 hrs. A few versions ago I just popped in a symlink /usr/lib/libnvidia-tls.so.384.90 -> /usr/lib/tls/libnvidia-tls.so.384.90, but when I switched to using nvidia-installler on 375.66 I didn't seem to need the symlink.

Can anyone provide some pointers as to what might be the issue, either with my multilib install or with the nvidia-installer command line? You can snag a copy of nvidia-installer at www.linuxgalaxy.org.

In the meantime, I'll go back to the old workarounds just to get something working and posted to SBo.

kingbeowulf --

This is Slackware64 14.2 + Multilib

see below.

HTH

-- kjh

p.s. maybe a test ? does _MY_ 32-bit glxgears work ???

kingbeowolf --

I just noticed that nvidia-tls is in two places under each /usr/lib* directory.

Interestingly, the files under each directory are different and none are symlinks !

Note that I reinstalled the NVIDIA-Linux-x86_64-384.90.run this morning after installing linux-4.4.92

Anyhow ... see below

-- kjh

kjhambrick,
what happens when you run '/usr/bin/32/glxgears' without the preload?

kingbeowolf --

Works fine.

-- kjh

new computer with 1050
 

I just bought a new computer today with GT 1030 inside. I've picked the driver from Nvidia site by going through the menus, specifying what card and OS I have. Downloaded what has been offered, without checking version. Installation was clean, simple and flawless, worked like a charm. Without it, I was limited to 1024x768.