LinuxQuestions.org
Share your knowledge at the LQ Wiki.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 06-30-2019, 08:40 PM   #1
slackw1zard
Member
 
Registered: Jun 2019
Posts: 36

Rep: Reputation: Disabled
Exclamation Odd Nvidia driver error messages


Well I got quite a bit of cc warning and some odd "will not install" what I presume would be error messages after installing nvidia-kernel and then the nvidia-driver slackbuilds from the
"site":
Code:
Slackware package /tmp/nvidia-driver-430.14-x86_64-1_SBo.tgz created.

bash-5.0# installpkg /tmp/nvidia-driver-430.14-x86_64-1_SBo.tgz
Verifying package nvidia-driver-430.14-x86_64-1_SBo.tgz.
Installing package nvidia-driver-430.14-x86_64-1_SBo.tgz:
PACKAGE DESCRIPTION:
# nvidia-driver (Proprietary Binary Nvidia Video Driver)
#
# This is the proprietary binary video driver from nvidia for
# the x.org X server. This package does not include the kernel
# module - it is included in the nvidia-kernel package.
#
# See /usr/doc/nvidia-driver-430.14/README.Slackware
# for more information.
#
Executing install script for nvidia-driver-430.14-x86_64-1_SBo.tgz.
Installing to nvidia-driver files!

Make sure the nvidia driver is ENABLED in /etc/X11/xorg.conf
and in /etc/X11/xorg.conf.d.
Otherwise, this may lead to improperly working drivers.
mv: cannot stat 'libGL.so.1.2.0': No such file or directory
mv: cannot stat 'libGL.la': No such file or directory
mv: cannot stat 'libEGL.so.1.0.0': No such file or directory
mv: cannot stat 'libGLESv1_CM.so.1.1.0': No such file or directory
mv: cannot stat 'libGLESv2.so.2.0.0': No such file or directory
Using existing Xorg libwfb...
Package nvidia-driver-430.14-x86_64-1_SBo.tgz installed.
bash-5.0#
None the less it installed correctly...
I am assuming this has something to do with compat32 not being enabled initially.

Code:
mv: cannot stat 'libGL.so.1.2.0': No such file or directory
mv: cannot stat 'libGL.la': No such file or directory
mv: cannot stat 'libEGL.so.1.0.0': No such file or directory
mv: cannot stat 'libGLESv1_CM.so.1.1.0': No such file or directory
mv: cannot stat 'libGLESv2.so.2.0.0': No such file or directory
My question now is what does that entail and what does that infer in the future concerning my slackware machine? Will this effect multilib (which I have not yet installed due to confusion on my behalf concerning current multilib vs 14.2 installation).

Quick discussion will clear things up for me and perhaps others.

Last edited by slackw1zard; 06-30-2019 at 08:43 PM.
 
Old 06-30-2019, 09:14 PM   #2
garpu
Member
 
Registered: Oct 2009
Distribution: Slackware
Posts: 337

Rep: Reputation: 122Reputation: 122
https://docs.slackware.com/howtos:ha...aphics_drivers Have you read this?
 
Old 06-30-2019, 10:08 PM   #3
kingbeowulf
Member
 
Registered: Oct 2003
Location: WA
Distribution: Slackware64 14.2 Slackware 14.2, Slackware{32,64}-current
Posts: 900
Blog Entries: 9

Rep: Reputation: 374Reputation: 374Reputation: 374Reputation: 374
Looks like you are installing without "COMPAT32=yes" which is fine on a pure 64-bit system (no multilib). You MUST convert to multilib FIRST and THEN run "COMPAT32=yes ./nvidia-driver.SlackBuild" otherwise nvidia-switch will not be able to find the mesa and X.org files to backup.

Where most people go wrong, and get the error you observed, is when they do not read the instructions or the 100+ times on LQ where I explained this:
  1. not running nvidia-switch --remove on upgrade. The original Mesa files need to be backed up and then restored.
  2. Slackware-current is not supported yet (libglvnd).
  3. sbopkg may not work.
Since Nvidia replaces a number of mesa and xorg-server files and symlinks these are backed up to "/var/log/nvidia/" and then restored before removepkg. If not, then the buildscript and/or nvidia-switch will kick "mv" errors. ONLY nvidia-kernel can be upgradepkg like any other Slackware package.

To review, on a clean Slackware[64] that never had ANY nvidia drivers (optional activity in []):
Code:
[convert to multilib]
[COMPAT32=yes] ./nvidia-driver.SlackBuild
./nvidia-kernel.SlackBuild
installpkg /tmp/nvidia-driver...tgz /tmp/nvidia-kernel...tgz
installpkg extra/xf86-video-nouveau-blacklist-noarch-1.txz #blacklist nouveau if not done already
reboot
Upgrading from previous install (older or the same):
Code:
nvidia-switch --remove
removepkg nvidia-driver
[COMPAT32=yes] ./nvidia-driver.SlackBuild
./nvidia-kernel.SlackBuild
installpkg /tmp/nvidia-driver...tgz 
upgradepkg /tmp/nvidia-kernel...tgz
reboot
These scripts aren't perfect, but I have been tweaking and running them for years. There are no "cannot stat" messages if everything is done correctly.
This will all change when current is released due to libglvnd that allows multiple drivers to coexist. Thus, nvidia-switch may vanish.

If you bugger it, just
Code:
nvidia-switch --remove
removepkg nivdia-*
rm -f /var/log/nvidia
upgradepkg --reinstall mesa xorg-server
reboot
and try again.

Have fun!!
 
1 members found this post helpful.
Old 06-30-2019, 10:11 PM   #4
kingbeowulf
Member
 
Registered: Oct 2003
Location: WA
Distribution: Slackware64 14.2 Slackware 14.2, Slackware{32,64}-current
Posts: 900
Blog Entries: 9

Rep: Reputation: 374Reputation: 374Reputation: 374Reputation: 374
I should maybe edit that docs how-to to add some of this. also, libvdpau is now part of Slackware so that reference can be removed.
 
Old 07-01-2019, 03:56 PM   #5
slackw1zard
Member
 
Registered: Jun 2019
Posts: 36

Original Poster
Rep: Reputation: Disabled
Exclamation

Quote:
Originally Posted by kingbeowulf View Post
Looks like you are installing without "COMPAT32=yes" which is fine on a pure 64-bit system (no multilib). You MUST convert to multilib FIRST and THEN run "COMPAT32=yes ./nvidia-driver.SlackBuild" otherwise nvidia-switch will not be able to find the mesa and X.org files to backup.

Where most people go wrong, and get the error you observed, is when they do not read the instructions or the 100+ times on LQ where I explained this:
  1. not running nvidia-switch --remove on upgrade. The original Mesa files need to be backed up and then restored.
  2. Slackware-current is not supported yet (libglvnd).
  3. sbopkg may not work.
Since Nvidia replaces a number of mesa and xorg-server files and symlinks these are backed up to "/var/log/nvidia/" and then restored before removepkg. If not, then the buildscript and/or nvidia-switch will kick "mv" errors. ONLY nvidia-kernel can be upgradepkg like any other Slackware package.

To review, on a clean Slackware[64] that never had ANY nvidia drivers (optional activity in []):
Code:
[convert to multilib]
[COMPAT32=yes] ./nvidia-driver.SlackBuild
./nvidia-kernel.SlackBuild
installpkg /tmp/nvidia-driver...tgz /tmp/nvidia-kernel...tgz
installpkg extra/xf86-video-nouveau-blacklist-noarch-1.txz #blacklist nouveau if not done already
reboot
Upgrading from previous install (older or the same):
Code:
nvidia-switch --remove
removepkg nvidia-driver
[COMPAT32=yes] ./nvidia-driver.SlackBuild
./nvidia-kernel.SlackBuild
installpkg /tmp/nvidia-driver...tgz 
upgradepkg /tmp/nvidia-kernel...tgz
reboot
These scripts aren't perfect, but I have been tweaking and running them for years. There are no "cannot stat" messages if everything is done correctly.
This will all change when current is released due to libglvnd that allows multiple drivers to coexist. Thus, nvidia-switch may vanish.

If you bugger it, just
Code:
nvidia-switch --remove
removepkg nivdia-*
rm -f /var/log/nvidia
upgradepkg --reinstall mesa xorg-server
reboot
and try again.

Have fun!!
Okay understood lol. I know I must:
Code:
* In the location where you found this README, download the subdirectory with
  the name that corresponds to the Slackware version you are running.  For
  Slackware64 14.2 for instance, you would run the following command:
    # lftp -c 'open http://slackware.com/~alien/multilib/ ; mirror -c -e 14.2'
  and then change into the new "14.2" directory which has been created on
  your computer:
    # cd 14.2
* First, you will upgrade your 64bit Slackware gcc and glibc packages to their
  multilib versions by running the command:
    # upgradepkg --reinstall --install-new *.t?z
  in the directory you just changed to (the "14.2" directory in our case).
  This will upgrade gcc and glibc packages, and also install a new package
  called "compat32-tools".
* You are now going to install 32-bit compatibility packages to support all
  the 32-bit programs you may want to run (roughly 60 MB of packages, not all
  that much really!).  These packages are located in the subdirectory called
  "slackware64-compat32" which you also downloaded with the "lftp" command
  shown above.  Run this command:
    # upgradepkg --install-new slackware64-compat32/*-compat32/*.t?z
* This procedure will also work if you already had a multilib setup and have
  upgraded your Slackware to a newer release (new compat32 packages will be
  installed and existing ones will be upgraded).
* Done!  You need to reboot because of the glibc upgrade.
But I know those are the rules for 14.2 correct? What do I do differently concerning the current distribution? Please answer this question for it is essential.
 
Old 07-01-2019, 06:50 PM   #6
bassmadrigal
LQ Guru
 
Registered: Nov 2003
Location: West Jordan, UT, USA
Distribution: Slackware
Posts: 6,082

Rep: Reputation: 3750Reputation: 3750Reputation: 3750Reputation: 3750Reputation: 3750Reputation: 3750Reputation: 3750Reputation: 3750Reputation: 3750Reputation: 3750Reputation: 3750
Quote:
Originally Posted by slackw1zard View Post
But I know those are the rules for 14.2 correct? What do I do differently concerning the current distribution? Please answer this question for it is essential.
He stated in the above post that -current isn't supported right now due to a libglvnd issue.

Quote:
Slackware-current is not supported yet (libglvnd).
 
Old 07-01-2019, 07:13 PM   #7
slackw1zard
Member
 
Registered: Jun 2019
Posts: 36

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by bassmadrigal View Post
He stated in the above post that -current isn't supported right now due to a libglvnd issue.

Wow - I read that but I just couldn't fully comprehend it. What am I to do then? If I download the 14.2 version will that bugger up my system?

Last edited by slackw1zard; 07-01-2019 at 07:15 PM.
 
Old 07-01-2019, 07:14 PM   #8
slackw1zard
Member
 
Registered: Jun 2019
Posts: 36

Original Poster
Rep: Reputation: Disabled
Wow - I read that but I just couldn't fully comprehend it. What am I to do then? If I download the 14.2 version will that bugger up my system?
 
Old 07-02-2019, 06:15 PM   #9
Gerardo Zamudio
Member
 
Registered: Jan 2011
Distribution: Slackware
Posts: 109

Rep: Reputation: 72
Follow the instructions by kingbeowulf exactly, especially the bit about setting up multilib first. By the way, multilib is set up the same as in 14.2, except you mirror the -current directory:

Code:
lftp -c 'open https://slackware.nl/people/alien/multilib/ ; mirror -c -e current'
cd current
upgradepkg --reinstall --install-new *.t?z
upgradepkg --install-new slackware64-compat32/*-compat32/*.t?z
Quote:
Originally Posted by slackw1zard View Post
My question now is what does that entail and what does that infer in the future concerning my slackware machine?
You're on -current. Those messages mean the stock files were not backed up. This means you will not be able to go back to stock X and the nvidia-switch script will fail.

Your graphics will still work and so will your games. You will just have a tough time updating the driver without nvidia-switch. You can try looking at the source and figure out what it does so you can do it by hand but I would suggest just sticking with this driver for now. Newer versions typically add support for newer games and monitors so unless you're buying games left and right every day, you'll be fine.
 
Old 07-02-2019, 08:53 PM   #10
slackw1zard
Member
 
Registered: Jun 2019
Posts: 36

Original Poster
Rep: Reputation: Disabled
Exclamation

Quote:
Originally Posted by Gerardo Zamudio View Post
Follow the instructions by kingbeowulf exactly, especially the bit about setting up multilib first. By the way, multilib is set up the same as in 14.2, except you mirror the -current directory:

Code:
lftp -c 'open https://slackware.nl/people/alien/multilib/ ; mirror -c -e current'
cd current
upgradepkg --reinstall --install-new *.t?z
upgradepkg --install-new slackware64-compat32/*-compat32/*.t?z


You're on -current. Those messages mean the stock files were not backed up. This means you will not be able to go back to stock X and the nvidia-switch script will fail.

Your graphics will still work and so will your games. You will just have a tough time updating the driver without nvidia-switch. You can try looking at the source and figure out what it does so you can do it by hand but I would suggest just sticking with this driver for now. Newer versions typically add support for newer games and monitors so unless you're buying games left and right every day, you'll be fine.
I love slackware errors, every day I learn a new error name. I made sure to update the system with the usual:
Code:
slackpkg update
slackpkg install-new
slackpkg upgrade-all
slackpkg clean-system
I decided to preform a clean install and now I am getting a certification error:

Code:
bash-5.0# lftp -c 'open https://slackware.nl/people/alien/multilib/ ; mirror -c -e current'
cd: Fatal error: Certificate verification: self signed certificate in certificate chain (13:5C:EC:36:F4:9C:B8:E9:3B:1A:B2:70:CD:80:88:46:76:CE:8F:33)
mirror: Fatal error: Certificate verification: self signed certificate in certificate chain (13:5C:EC:36:F4:9C:B8:E9:3B:1A:B2:70:CD:80:88:46:76:CE:8F:33)
...
lftp -c 'open http://slackware.com/~alien/multilib/ ; mirror -c -e current'
solved

Last edited by slackw1zard; 07-02-2019 at 09:36 PM. Reason: lftp -c 'open http://slackware.com/~alien/multilib/ ; mirror -c -e current'
 
Old 07-02-2019, 10:54 PM   #11
bassmadrigal
LQ Guru
 
Registered: Nov 2003
Location: West Jordan, UT, USA
Distribution: Slackware
Posts: 6,082

Rep: Reputation: 3750Reputation: 3750Reputation: 3750Reputation: 3750Reputation: 3750Reputation: 3750Reputation: 3750Reputation: 3750Reputation: 3750Reputation: 3750Reputation: 3750
Quote:
Originally Posted by slackw1zard View Post
I decided to preform a clean install and now I am getting a certification error:

Code:
bash-5.0# lftp -c 'open https://slackware.nl/people/alien/multilib/ ; mirror -c -e current'
cd: Fatal error: Certificate verification: self signed certificate in certificate chain (13:5C:EC:36:F4:9C:B8:E9:3B:1A:B2:70:CD:80:88:46:76:CE:8F:33)
mirror: Fatal error: Certificate verification: self signed certificate in certificate chain (13:5C:EC:36:F4:9C:B8:E9:3B:1A:B2:70:CD:80:88:46:76:CE:8F:33)
...
lftp -c 'open http://slackware.com/~alien/multilib/ ; mirror -c -e current'
solved
Following these instructions would fix it as well.
 
Old 07-04-2019, 02:53 PM   #12
kingbeowulf
Member
 
Registered: Oct 2003
Location: WA
Distribution: Slackware64 14.2 Slackware 14.2, Slackware{32,64}-current
Posts: 900
Blog Entries: 9

Rep: Reputation: 374Reputation: 374Reputation: 374Reputation: 374
Right now, Current is too fast a moving target for me to play around with the Nvidia blob SBo buildscripts. I'm not quite to retirement yet where I'll have more free time for my hobbies! I only have current running on a Lenovo T510 laptop for testing right now. Once we hit RC1 ("real soon now", i'm itching to drop it on ont the NVME 250GB drive!) I'll refactor the script. It's almost all there already; I just have to tell the nvidia-installer to use the system libglvnd and the precompiled one.

That said, the 14.2 scripts "might" work on current. I just haven't tested for any libglvnd and nvidia-switch anomalies.
 
Old 07-05-2019, 11:06 PM   #13
enorbet
Senior Member
 
Registered: Jun 2003
Location: Virginia
Distribution: Slackware = Main OpSys for decades while testing others to keep up
Posts: 2,263

Rep: Reputation: 2283Reputation: 2283Reputation: 2283Reputation: 2283Reputation: 2283Reputation: 2283Reputation: 2283Reputation: 2283Reputation: 2283Reputation: 2283Reputation: 2283
Take this "with a grain of salt" since I'm an Old Skool kinda guy, but when I see someone jumping right into current along with essentially all the automation Slackware allows I wonder what brought that person to Slackware in the first place. For my twapence, I think it is better to start out as conservative as is possible. Install the Full (guaranteed stable) Release and with "Full Recommended Install" and don't automate anything you don't have to. Learn how to have everything in front of you and in your control. In short learn to administer. I'm not the best guy on here as an Admin but zero happens that I did not initiate so I almost always know where to look for the error, which is almost always mine but just one step away so it's pretty easy to fix.

The cool thing is you can always setup a different drive or partition to also run Current, but there, too, I suggest at least starting out with the least automation so you know and control everything not only that happens, but what can happen.

Like I said, "grain of salt" but it does work and with the least amount of maintenance. From my POV it's how Slackware is designed to function best.
 
1 members found this post helpful.
  


Reply

Tags
multilib, nvidia driver, slackware -current


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Odd situation with raid10 array, odd number of drives, and it took, can't regrow now Red Squirrel Linux - Software 9 08-08-2014 02:15 PM
odd Gentoo Xorg 7.0 Gnome 2.14 NVidia driver conflict unknown_mosquito Linux - Desktop 1 08-29-2006 04:13 PM
Very odd NVidia Driver Problem... justintime32 Mandriva 3 03-07-2005 09:26 AM
new nvidia driver & mouse problems - odd errors produced, no mouse detected. UrbanSlayer Debian 4 07-03-2004 08:13 PM
ACPI is working but have some odd error messages acmilanlover Linux - General 1 08-16-2003 11:13 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 12:00 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration