Gripe: Every ubuntu nvidia driver install is harder than the previous

Questions and Answers : Unix/Linux : Gripe: Every ubuntu nvidia driver install is harder than the previous
Message board moderation

To post messages, you must log in.

AuthorMessage
Profile Joseph Stateson Project Donor
Volunteer tester
Avatar

Send message
Joined: 27 May 99
Posts: 281
Credit: 70,759,933
RAC: 3
United States
Message 2019223 - Posted: 16 Nov 2019, 3:49:25 UTC

Setting up a H110--BTC rig to replace several small systems. Have notes from the previous Ubuntu installs but nothing seems to work the same way as before.

Installed 18.04 with 1660Ti with driver 440.31 (latest). All worked ok following notes I had made on a fresh install.

Pulled gtx-1070 from HPz-400 (it had a 1060 in addition to the 1070) but was not recognized when put in to the new system.
Could not re-install the 440.31 driver: "already installed"

In the mean time, that HPz-400 with the left over gtx1060 didn't recognized the 1060. Seems taking out the 1070 messed things up there.

Google for how to uninstall nvidia driver found instructions to run /usr/bin/nvidia-uninstall but that file did not exist
"ubuntu-drivers devices" saw the 1070 but did not get the friendly name for the 1660Ti and suggested driver 435 for the 1070.

Went back to nvidia and read the readme and the 440.31 was good for all the boards,. It should have worked.

I put in that 435 and that caused 440 to disappear and I also got that missing file "nvidia-uninstall". Both video boards were recognized by nvidia-smi but no CUDA was available so boinc had nothing to do.

"apt list --installed" give me a list of nvidia packages and I did a purge delete of all nvidia packages that had anything to do with video. Some motherboards have nvidia chipsets so cant just do a purge of *nvidia*

I then tried that 440.31 driver again but was told to remove the nouveau one. That messaged was new. It did not show up the first time I ran that 440.31 install. Also the 32bit lib support went in. Did not see that before so the 435 driver had something that was missing from the 440.31. Followed instructions on blacklisting and the subsequent install of 440.31 worked fine and boinc is crunching SETI using 1660 and 1070. I need to add my remaining 1060 boards

Windows does not have this problem but I am told that "windows sucks more"


ID: 2019223 · Report as offensive
Ian&Steve C.
Avatar

Send message
Joined: 28 Sep 99
Posts: 3259
Credit: 1,282,604,591
RAC: 6,640
United States
Message 2019252 - Posted: 16 Nov 2019, 13:44:12 UTC - in response to Message 2019223.  

It sounds like you’re using the nvidia .run file to install. You should be using the PPA.

If you’re not using a motherboard with an nvidia chipset, go for the purge. All of those boards are very old. Your H110 board has an H110 chipset.

When I change nvidia drivers, I do this:

1. sudo apt purge *nvidia*

Then:
2. Reinstall new drivers from the PPA with:
sudo apt install nvidia-driver-<version>
Seti@Home classic workunits: 29,492 CPU time: 134,419 hours

ID: 2019252 · Report as offensive
Profile Joseph Stateson Project Donor
Volunteer tester
Avatar

Send message
Joined: 27 May 99
Posts: 281
Credit: 70,759,933
RAC: 3
United States
Message 2019271 - Posted: 16 Nov 2019, 16:10:17 UTC - in response to Message 2019252.  
Last modified: 16 Nov 2019, 16:43:00 UTC

It sounds like you’re using the nvidia .run file to install. You should be using the PPA.

If you’re not using a motherboard with an nvidia chipset, go for the purge. All of those boards are very old. Your H110 board has an H110 chipset.

When I change nvidia drivers, I do this:

1. sudo apt purge *nvidia*

Then:
2. Reinstall new drivers from the PPA with:
sudo apt install nvidia-driver-<version>


Thanks for replying. It appears that RUN file does not have all the ingredients needed. I should have started with the PPA and gone on to the RUN if there was a problem. Even the folks over at BOINC have stated that windows does a better job of integrating drivers and can handle both amd, nvidia and the "intel" if the intel cpu supports video.

I discovered the hard way that purging all "AMD" gets rid of more than the ATI video drivers. Going to make a note here of exactly what happened as it might be useful for someone else

from ebay: used h110 and cheapest i7-6700 I could find.

1. Initial setup: Put in 1660Ti in X16slot, booted USB3 flash with 18.03 full desktop install with 3rd party enabled
+updates+upgrades
+build_essential
+vsftpd+xinitd
+openss-server
+boinc from ppa:costamgnagianfranco as they seem to be the release ppa for all boinc Linux
At this point I rebooted and configured boinc using BoincTasks. With the boinc client working I did
sudo bash NVIDIA-Linux-x86_64-440.31.run
there was no complaint about the nouvdeau driver but I did get a complaint about missing 32bit libraries
Boinc started crunching SETI but on cuda60 as I had not put in the "special"
===looked like all was going just fine===

2. Problems: Put in gtx1070 on riser. Boinc saw only the 1660Ti
Pulled 1660ti and put gtx1070 in x16 slot but worse: Boinc saw nothing
could not re-install 440.31 nor find /usr/bin/nvidia_uninstall

3. Tried the PPA
ubuntu-drivers devices listed
driver   : nvidia-driver-430 - distro non-free
driver   : nvidia-driver-435 - distro non-free recommended
driver   : nvidia-driver-390 - distro non-free

did the sudo apt install nvidia-435 which got rid of the 440.31 and put in that uninstall program
upon reboot nvidia-smi shows both video boards BUT BUT BUT

4. Boinc did not see any usable GPU
Decided to try that RUN again.
Purged nvidia packages after looking at apt list --installed
sudo apt-get --purge remove nvidia-driver-435
sudo apt-get --purge remove nvidia-cuda-toolkit
sudo apt-get --purge remove nvidia-cuda-dev
sudo apt-get --purge remove nvidia-cuda-doc
sudo apt-get --purge remove nvidia-opencl-dev
sudo apt-get --purge remove nvidia-utils-435
sudo apt-get --purge remove nvidia-dkms-435
sudo apt-get --purge remove nvidia-compute-utils
sudo apt-get --purge remove nvidia-compute-utils-435
sudo apt-get --purge remove nvidia-*435*
sudo apt-get --purge remove nvidia-*390*


solved 32 bit problem with
     sudo dpkg --add-architecture i386
     sudo apt install libc6:i386

not sure why I need 32bit but the RUN asked about it.
did not use "bash" as the readme showed "sh"
sudo sh NVIDIA-Linux-x86_64-440.31.run
This install told me to blacklist that nouveau driver and once that was done the "RUN" worked
I added gtx1060 on riser and all 3 boards working on "special" app.

Been reading about vlar problems
Does Linux has problems with those vlars? Do I need to downgrade?
ID: 2019271 · Report as offensive
Ian&Steve C.
Avatar

Send message
Joined: 28 Sep 99
Posts: 3259
Credit: 1,282,604,591
RAC: 6,640
United States
Message 2019278 - Posted: 16 Nov 2019, 17:20:24 UTC - in response to Message 2019271.  

Linux does not have the problem. You can use whatever drivers you want.

I think you are over complicating matters. KISS applies.

Keep nvidia and AMD cards on segregated systems. Install the OS normally, add the nvidia drivers PPA, install the drivers from command line, reboot, drop the all-in-one package in your Home folder, make any small configuration changes (like app_config or command lines) and you’re off to the races. It’s very fast and straightforward.
Seti@Home classic workunits: 29,492 CPU time: 134,419 hours

ID: 2019278 · Report as offensive
Profile Joseph Stateson Project Donor
Volunteer tester
Avatar

Send message
Joined: 27 May 99
Posts: 281
Credit: 70,759,933
RAC: 3
United States
Message 2019286 - Posted: 16 Nov 2019, 18:32:01 UTC - in response to Message 2019278.  

Linux does not have the problem. You can use whatever drivers you want.

I think you are over complicating matters. KISS applies.

Keep nvidia and AMD cards on segregated systems. Install the OS normally, add the nvidia drivers PPA, install the drivers from command line, reboot, drop the all-in-one package in your Home folder, make any small configuration changes (like app_config or command lines) and you’re off to the races. It’s very fast and straightforward.


You are correct.

Found out I had BIOS 1.10 and latest is 1.6 so after upgrading BIOS and seeing a lot of complaints I decided to go the ppa route
should have checked for latest bios before doing anything in the first place

I am no expert on Linux so google helped me find these
sudo add-apt-repository ppa:graphics-drivers/ppa
sudo apt-get update
ubuntu-drivers devices
---
driver   : nvidia-driver-440 - third-party free recommended
driver   : nvidia-driver-430 - distro non-free
driver   : nvidia-driver-415 - third-party free
driver   : nvidia-driver-410 - third-party free
driver   : nvidia-driver-390 - third-party free
---


I put in that 440 one and got cuda with it. Possibly the original problem of the other board not being seen was the older bios
ID: 2019286 · Report as offensive
Grant (SSSF)
Volunteer tester

Send message
Joined: 19 Aug 99
Posts: 13063
Credit: 208,696,464
RAC: 304
Australia
Message 2019322 - Posted: 17 Nov 2019, 0:08:59 UTC

I had issues trying to get my Mint Cinnamon 4.2 going with the Nvidia driver.

I followed the instructions to get the driver as part of the install, but couldn't get it to work once the system was up and running. It would just use the Nouveau driver and Using Admin, Driver Manager didn't give me the option for the most recent Nvidia drivers (even after doing Admin, Software Sources updating), even though they were there on the USB Live session.
So I just nuked the whole thing, redid the installation without including drivers/multimedia etc options, then used Admin, Driver Manager- which gave the option of the latest NVidia driver- installed it, then did all the other configuration & update work.

Even now the System Report doesn't recognise my RTX 2060 Super, it's just "Device-3: Nvidia" whereas my GTX 1070 is listed as "Device-2: Nvidia GP104 [GeForce GTX 1070]". Nvidia X server settings recognises it, and it's crunching, so i'm happy to leave things as they stand.


I like the look and feel of Mint Cinnamon (even with it's quirks), but if Linux is really serious about taking on Windows, they need to make it possible to add, remove & find out what is installed using the GUI. Until such time that occurs they will never come close to challenging Windows.
By all means, keep the command line for the power user, but make it usable for everyone else as well.
Grant
Darwin NT
ID: 2019322 · Report as offensive
Profile Mr. Kevvy Crowdfunding Project Donor*Special Project $250 donor
Volunteer moderator
Volunteer tester
Avatar

Send message
Joined: 15 May 99
Posts: 3219
Credit: 1,114,826,392
RAC: 3,319
Canada
Message 2019334 - Posted: 17 Nov 2019, 1:09:50 UTC - in response to Message 2019322.  

I like the look and feel of Mint Cinnamon (even with it's quirks), but if Linux is really serious about taking on Windows, they need to make it possible to add, remove & find out what is installed using the GUI. Until such time that occurs they will never come close to challenging Windows.


It is... open the menu bottom-left, type "dr" and launch Driver Manager. This is the only method I use for adding/changing video drivers. I'll use command-line for purging.
ID: 2019334 · Report as offensive
Grant (SSSF)
Volunteer tester

Send message
Joined: 19 Aug 99
Posts: 13063
Credit: 208,696,464
RAC: 304
Australia
Message 2019339 - Posted: 17 Nov 2019, 1:30:37 UTC - in response to Message 2019334.  

It is... open the menu bottom-left, type "dr" and launch Driver Manager. This is the only method I use for adding/changing video drivers. I'll use command-line for purging.
But it is of no use to find out what driver is presently installed for my iGPU, no use for finding out what other drivers are presently installed.

In Windows you just use Device Manager to see all the hardware on the system, what driver is or isn't installed, to remove, add (locally or from the net) or rollback a driver. No command line work necessary. When you can do that in Linux, with no need to use the command line, then they'll be able to take on Windows.
Grant
Darwin NT
ID: 2019339 · Report as offensive
Profile Joseph Stateson Project Donor
Volunteer tester
Avatar

Send message
Joined: 27 May 99
Posts: 281
Credit: 70,759,933
RAC: 3
United States
Message 2021483 - Posted: 3 Dec 2019, 0:45:32 UTC

Should have know better!

Moved a system to the garage as it was too noisy and powered it up. Got a messaged about important updates. Should have thought twice about updating but I didn't.

Lost nvidia drivers for the 3 cards.

did the following
ubuntu-drivers devices

picked the one they suggested
driver : nvidia-driver-440 - third-party free recommended

It told me I needed 18.04.02 and I only had 18.04.01

Tried "update" followed by "upgrade" but was told there were none for me.

I picked
nvidia-driver-435 - distro non-free

It worked. I have no idea why it is "non-free". My credit card is not anywhere on file on this system and I never see advertisements as it is headless miner.
ID: 2021483 · Report as offensive
Profile Keith Myers Special Project $250 donor
Volunteer tester
Avatar

Send message
Joined: 29 Apr 01
Posts: 11914
Credit: 1,160,866,277
RAC: 1,873
United States
Message 2021488 - Posted: 3 Dec 2019, 1:19:16 UTC - in response to Message 2021483.  

It worked. I have no idea why it is "non-free". My credit card is not anywhere on file on this system and I never see advertisements as it is headless miner.

The term "non-free" is a misnomer. That is referring to closed source proprietary drivers, i.e. the Nvidia drivers from Nvidia. The "free" drivers are from the graphics-drivers ppa maintained by that team and is open-source.

If you have the Software&Updates application and open the Additional Drivers tab, you can see the various versions of the Nvidia drivers listed and their source descriptors. The 435 version drivers are listed as proprietary while the 440 version drivers are listed as open-source.

Depends on whether the download source is from the official distros or the ppa. And none of them require payment for use.
Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)
ID: 2021488 · Report as offensive
Ian&Steve C.
Avatar

Send message
Joined: 28 Sep 99
Posts: 3259
Credit: 1,282,604,591
RAC: 6,640
United States
Message 2021510 - Posted: 3 Dec 2019, 4:37:34 UTC
Last modified: 3 Dec 2019, 4:41:19 UTC

Assuming the PPA is already setup. All you need to do is:

sudo apt purge *nvidia*

sudo apt install nvidia-driver-440
(Or 410, or 418, or 435, whatever you want/need)

Reboot.
Seti@Home classic workunits: 29,492 CPU time: 134,419 hours

ID: 2021510 · Report as offensive
Profile Joseph Stateson Project Donor
Volunteer tester
Avatar

Send message
Joined: 27 May 99
Posts: 281
Credit: 70,759,933
RAC: 3
United States
Message 2021544 - Posted: 3 Dec 2019, 14:04:03 UTC - in response to Message 2021510.  

Assuming the PPA is already setup. All you need to do is:

sudo apt purge *nvidia*
sudo apt install nvidia-driver-440

Reboot.


I will do that the next time there is a problem (it ain't broke yet)

Must be misinterpreting something:
from "uname -a" I get the following that shows "18.04.1"

Linux tb85-nvidia 5.0.0-37-generic #40~18.04.1-Ubuntu SMP Thu Nov 14 12:06:39 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
jstateson@tb85-nvidia:~$


Yet SETI reports I have 18.04.3
and an attempted install of driver 440 shows I am missing 18.04.2
sudo apt-get install nvidia-driver-440

The following packages have unmet dependencies:
 nvidia-driver-440 : Depends: xserver-xorg-video-nvidia-440 (= 440.26-0ubuntu0~gpu18.04.2) but it is not going to be installed
                     Depends: libnvidia-cfg1-440 (= 440.26-0ubuntu0~gpu18.04.2) but it is not going to be installed
E: Unable to correct problems, you have held broken packages


going to leave in driver 435.21 as newest board is gtx1060 and 440 probably not going to help those board much plus "it ain't broke yet"
ID: 2021544 · Report as offensive
Ian&Steve C.
Avatar

Send message
Joined: 28 Sep 99
Posts: 3259
Credit: 1,282,604,591
RAC: 6,640
United States
Message 2021555 - Posted: 3 Dec 2019, 16:08:31 UTC - in response to Message 2021544.  

question, I know you say this system is headless, but are you running the desktop version of Ubuntu? do you have the whole desktop environment when you VNC into it?

your error message explains whats going on. you have broken packages.

i would wipe out everything from the nvidia drivers with the purge command from before.

sudo apt update
sudo apt upgrade

then try these:
sudo apt install -f
sudo dpkg --configure -a

then reinstall the nvidia drivers:
sudo apt install nvidia-driver-440

then reboot.
Seti@Home classic workunits: 29,492 CPU time: 134,419 hours

ID: 2021555 · Report as offensive
Profile Keith Myers Special Project $250 donor
Volunteer tester
Avatar

Send message
Joined: 29 Apr 01
Posts: 11914
Credit: 1,160,866,277
RAC: 1,873
United States
Message 2021558 - Posted: 3 Dec 2019, 16:12:34 UTC

The command to check your distribution level is:
lsb_release -a

keith@Serenity:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 18.04.3 LTS
Release: 18.04
Codename: bionic
keith@Serenity:~$

Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)
ID: 2021558 · Report as offensive
Profile Joseph Stateson Project Donor
Volunteer tester
Avatar

Send message
Joined: 27 May 99
Posts: 281
Credit: 70,759,933
RAC: 3
United States
Message 2021567 - Posted: 3 Dec 2019, 21:13:48 UTC

jstateson@h110btc:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu 18.04.3 LTS
Release:        18.04
Codename:       bionic


I installed full desktop as I do not know of any way to set fan speed except iterate through
/usr/bin/nvidia-settings -a "[gpu:$n]/GPUFanControlState=1"
/usr/bin/nvidia-settings -a "[fan:$n]/GPUTargetFanSpeed=100"


AFAICT there is no way to do that using putty (ssh) which is how I access my "headless" systems.
By "headless" I mean I substitute an dummy HDMI plug for the monitor AFTER the fans are set and use the monitor elsewhere.
I had problems installing "RealVNC" though I did get Teamviewer to work once. Not using any remote desktop on any Linux systems currently. If I can fix those broken packages I will give RealVNC another try. I use in on a few windows systems that are not part of my 5 free license splashtops.

If I can get the right adapter cables I would like to have all fans hard set to 12v to avoid having to run that nvidia-settings. Have been looking for nvidia female graphic socket to male 3 or 4 pin for possible use with several PWM speed controller modules I picked up. I think I need something like the opposite of this.
Temps are great right now but I will need to get better control of the temps when the summer months show up and want to have those fan controllers working or just set fans to the full 12v.

Is there any way to set the fans using ssh? Maybe faking an "x display" to allow nvidia-settings to work?
ID: 2021567 · Report as offensive
Ian&Steve C.
Avatar

Send message
Joined: 28 Sep 99
Posts: 3259
Credit: 1,282,604,591
RAC: 6,640
United States
Message 2021629 - Posted: 4 Dec 2019, 2:16:41 UTC - in response to Message 2021567.  

using that dummy plug, you should be able to get a desktop via VNC to do remote configuration. It's how I remote manage everything. I have VNC Viewer installed on my Windows 10 laptop. I'm using an older version of VNC Viewer that does not require any of the user accounts nonsense that the new versions need. I have version 6.17.1113 (r31799) x64. Ubuntu 18.04 has built in VNC functionality. Attach a monitor to the system and do the following:

Go to Settings -> Sharing
Click the slider at the upper right of the window to turn Sharing "ON"
Click the Screen Sharing button
In the upper left of the window that opens, click it to "ON"
Make sure "Allow connections to control the screen" is checked
Set a password to be used for the connection (8 characters)



next you need to make one tweak (this might only be specific to VNC Viewer). I was not able to connect to any of my systems with VNC Viewer due to Ubuntu requiring encryption. but you can turn it off.

install dconf-editor
sudo apt install deconf-editor

run it (via terminal or GUI)
navigate to /org/gnome/desktop/remote-access
on "require encryption", click the slider to "OFF"



get the IP address of the system, you'll need it, or add it's host name to your host file.

now you're all configured. unplug the monitor, put the dummy plug back on. and from another system using VNC viewer or whatever VNC client software you prefer

connect to it at <ip-address>::5900 and using the password you created.

when I want to connect to a remote system not on my local LAN, I just VPN to that location (I run VPN servers at both locations) and then VNC over the tunnel.
Seti@Home classic workunits: 29,492 CPU time: 134,419 hours

ID: 2021629 · Report as offensive
Profile Joseph Stateson Project Donor
Volunteer tester
Avatar

Send message
Joined: 27 May 99
Posts: 281
Credit: 70,759,933
RAC: 3
United States
Message 2021632 - Posted: 4 Dec 2019, 3:13:12 UTC - in response to Message 2021629.  
Last modified: 4 Dec 2019, 3:34:38 UTC

WORKING WORKING WORKING!!

Thank you so much!

Got it working on the TB85 which does not have the broken packages. Will try next on the H110BTC. Will try to fix the packages first

[edit]
yesterday I ran

sudo apt update
sudo apt upgrade


and was told there was nothing to upgrade. Now I run it. Runs for 5 minutes and put in 440 without having to ask!!!

[edit2]
Got it working on the HTC110!!

thank you again!
ID: 2021632 · Report as offensive
Ian&Steve C.
Avatar

Send message
Joined: 28 Sep 99
Posts: 3259
Credit: 1,282,604,591
RAC: 6,640
United States
Message 2021635 - Posted: 4 Dec 2019, 4:02:04 UTC - in response to Message 2021632.  

good to hear :)
Seti@Home classic workunits: 29,492 CPU time: 134,419 hours

ID: 2021635 · Report as offensive

Questions and Answers : Unix/Linux : Gripe: Every ubuntu nvidia driver install is harder than the previous


 
©2020 University of California
 
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.