The Latest NVIDIA Linux Driver Release.

chrisretusn · 11-16-2018, 08:11 AM

Quote:

Originally Posted by ponce

maybe you missed it, but there's is a patch for it in the unofficial repository for current

http://cgit.ponce.cc/slackbuilds/com...gacy390-kernel

Yes I did miss it. Searched high and low with duckduckgo, didn't find much to go on. Even searched on the NVIDIA Developer Forums (not a very good search engine there if you ask me), even passed a post titled "Nvidia Geforce 4xx series drivers segfault with kernel-4.19.x", guess what was listed in the post?

Another reason is I install the blob. Hehe, should have searched closer to home.

If anyone else is interested, I adapted the patch ponce linked to, to work on the blob.

As root, in the same directory as the NVIDIA driver and the patch file run the following:

Code:

# bash NVIDIA-Linux-x86_64-390.87.run --apply-patch 4.19_blob.patch.txt
-OR- if executable
# ./NVIDIA-Linux-x86_64-390.87.run --apply-patch 4.19_blob.patch.txt

When finished it will create a file named NVIDIA-Linux-x86_64-390.87-custom.run, this file will be executable regardless of of what the original permission setting were. You can use the "custon" blob to install the drivers.

Thanks ponce!

1337_powerslacker · 11-20-2018, 03:13 PM

I had the 415.13 beta driver installed, and saw the new driver release today. It is the successor to the beta driver, and incorporates all previous fixes plus a few more. It is working without issue on my box. Awesome!

mlangdn · 11-20-2018, 05:26 PM

I went to the nvidia driver site and 410.78 is still the latest stable.

cwizardone · 11-20-2018, 05:27 PM

Quote:

Originally Posted by mlangdn

I went to the nvidia driver site and 410.78 is still the latest stable.

You can find 415.18 here,

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

It is now listed as the latest "Short Lived Branch" driver,

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

mlangdn · 11-20-2018, 05:29 PM

Yea - I just downloaded it. I reckon I could learn to look just a bit more......

cwizardone · 11-20-2018, 05:39 PM

Quote:

Originally Posted by mlangdn

Yea - I just downloaded it. I reckon I could learn to look just a bit more......

For whatever reasons there is a delay of several hours between the time the news hits the media and they update their web site.

cwizardone · 11-21-2018, 09:49 AM

If you have ever had an interest in overclocking your Nvidia GPU, this link will lead you to information on subject,

https://www.linuxquestions.org/quest...ui-4175642774/

273 · 11-23-2018, 06:51 AM

I would like to overclock but the guide linked to suggest the use of a Python tool. Not bad in itself but I have overclocked using the nvidia-settings tool in the past and would like to do so now but cannot due to no xorg.conf. I did find an thread on a forum with an xorg.conf (it allows coolbits to be set) but when I used it I had no graphics so I'm also a bit skeptical of the python tool also for that reason.

enorbet · 11-24-2018, 08:27 PM

It is not a problem to create your own xorg.conf. It will still be run and these days it should be obvious it can be really small and specifically for one device.

Here's most of mine. Note that the commented out nvidia lines were moved to a user-specific $HOME/.local.

Code:

 
## etc/X11/xorg.conf
Section "Monitor"
    Identifier     "Monitor0"
    VendorName     "Vizio"
    ModelName      "VIZ M322i-B1"
    HorizSync       31.0 - 80.0
    VertRefresh     56.0 - 76.0
    Option         "DPMS"
EndSection

Section "Device"
    Identifier     "Device0"
    Driver         "nvidia"
    VendorName     "NVIDIA Corporation"
    BoardName      "GeForce GTX 1070 Ti"
    Option         "Coolbits" "13"
### Added to satisfy Xsession-errors for KDE
    Option          "TripleBuffer" "On"
   # Option     "RegistryDwords" "PerfLevelSrc=0x3322; PowerMizerDefaultAC=0x1"
    #Option  "RegistryDwords" "PowerMizerEnable=0x1; PerfLevelSrc=0x2222; PowerMizerDefaultAC=0x1"
EndSection

Section "Screen"

# Removed Option "metamodes" "nvidia-auto-select +0+0"
    Identifier     "Screen0"
    Device         "Device0"
    Monitor        "Monitor0"
    DefaultDepth    24
    #Option         "nvidiaXineramaInfoOrder" "DFP-0"
    Option         "Stereo" "0"
    Option         "metamodes" "1920x1080_60 +0+0 { ForceCompositionPipeline = On }" 
    Option         "SLI" "Off"
    Option         "MultiGPU" "Off"
    Option         "BaseMosaic" "off"
    SubSection     "Display"
        Depth       24
    EndSubSection
EndSection

All I needed at system level was the Coolbits line and ForceCompositionPipeline. At user level I enable Performance Mode as Default and increase base fan speed to 80%. Works perfectly.

273 · 11-25-2018, 04:39 AM

I actually created a smaller oxrg.conf, following a guide on some forum or other, with just the device section but couldn't boot to X11 after doing so.
I wouldn't be sure what, exactly, to put in my xorg.conf to be the minimum required to allow things like overclocking and fan speed but still be able to use my machine.

cwizardone · 11-25-2018, 07:07 AM

Mr. Volkerding supplies a sample xorg.conf with the standard install. It is labeled xorg.conf.vesa and can be found in /etc/X11. I don't recall it is also in /etc/X11/xorg.conf.d (think so).
I take that and modify it for my monitor and rename it, xorg.conf. Works just fine. I've found my particular monitor works best when its refresh rates are listed in an xorg.conf file.

enorbet · 11-25-2018, 09:07 AM

My PCs all boot to runlevel 3 (multi-user command line) where I launch KDM for the handling of graphics and to choose a WM/DE. I use Runlevel 3 to do deep level work like build and install custom kernels and nVidia drivers. I keep Patrick's xorg.conf.vesa in /etc/X11/ as well as a very basic one based on the information Patrick provides in that template with just a few omissions obvious from messages in /var/log/Xorg.0.log such as for mouse and keyboard, no longer needed.

If I ever make a change where KDM fails to handle X, it is trivial to either edit the current xorg.conf according to the error messages in that log or to temporarily substitute a known good xorg.conf sans tweaks.

cwizardone · 11-29-2018, 01:06 PM

415.18.02

Nvidia has released a new BETA Vulkan driver.

Release notes,

Quote:

November 28th, 2018 - Windows 417.17, Linux 415.18.02

Turing support
Fixes:
VK_EXT_transform_feedback bug fixes

More information and a download link can be found at,
https://developer.nvidia.com/vulkan-driver

RadicalDreamer · 12-01-2018, 05:58 AM

The last couple of NVIDIA driver updates seem to mess up Plasma 5 occasionally when starting using startx with multiple monitors. I boot up to a blank screen and have to use computer shortcuts to navigate Plasma 5 (alt+space for krunner, etc). I usually F1+Ctrl+Alt and startx again to get it to work correctly. I had the 3 screens off for a couple hours and it did it. I notice it pauses at a blank screen longer than it used to between switching accounts with SDDM. Any ideas?

cwizardone · 12-03-2018, 08:43 PM

Nvidia-415.18.04

Nvidia has released a new BETA Vulkan driver.

Quote:

Release Updates

December 2nd, 2018 - Windows 417.23, Linux 415.18.04

New Extensions:
VK_KHR_shader_float16_int8
VK_KHR_shader_float_controls
Fixes:
Fixes regression with Unity games on Linux

More information and a download link can be found at,
https://developer.nvidia.com/vulkan-driver