LinuxQuestions.org
Review your favorite Linux distribution.
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 02-02-2019, 07:48 AM   #1
someone named bert
LQ Newbie
 
Registered: Nov 2013
Distribution: Slackware64 14.2
Posts: 24

Rep: Reputation: Disabled
Unhappy 4.4.172 kernel and nividia-legacy*340* (SBo)


Hello,
so I've read the threads on here about the current nVidia binary/proprietary driver not working with the newest stock kernel, 4.4.172, but I'm running the nividia-legacy340 binary driver from SBo, which breaks for the same reasons supposedly.
I gather there won't be a solution from nVidia to keep running that old proprietary driver, and no one else can do one. Am I right?

Love & Light
 
Old 02-02-2019, 08:20 AM   #2
RadicalDreamer
Member
 
Registered: Jul 2016
Location: USA
Distribution: Slackware64-Current
Posts: 948

Rep: Reputation: 440Reputation: 440Reputation: 440Reputation: 440Reputation: 440
Users are asking about it here: https://devtalk.nvidia.com/default/t...t_user_pages-/

You are right. It is the price of using NVIDIA.
 
1 members found this post helpful.
Old 02-02-2019, 10:34 AM   #3
Petri Kaukasoina
Member
 
Registered: Mar 2007
Posts: 389

Rep: Reputation: 246Reputation: 246Reputation: 246
Would you like to move to kernel 4.19, like in current? Legacy driver 340.106 builds for linux-4.19.19 after this patch https://www.linuxquestions.org/quest...ml#post5808278
 
1 members found this post helpful.
Old 02-02-2019, 11:38 AM   #4
Richard Cranium
Senior Member
 
Registered: Apr 2009
Location: Carrollton, Texas
Distribution: Slackware64 14.2
Posts: 3,184

Rep: Reputation: 1549Reputation: 1549Reputation: 1549Reputation: 1549Reputation: 1549Reputation: 1549Reputation: 1549Reputation: 1549Reputation: 1549Reputation: 1549Reputation: 1549
If it's that old of a card, maybe the nouveau driver will perform well enough for you.
 
1 members found this post helpful.
Old 02-02-2019, 11:45 AM   #5
someone named bert
LQ Newbie
 
Registered: Nov 2013
Distribution: Slackware64 14.2
Posts: 24

Original Poster
Rep: Reputation: Disabled
Thanks RadicalDreamer and Petri Kaukasoina, much appreciated.
Richard Cranium, when I `init 4`'ed after `nvidia-switch --remove`, KDE didn't even offer the native resolution of my display. Do I need to do anythong else to use noveau properly?
Love & Light
 
Old 02-02-2019, 12:42 PM   #6
bassmadrigal
LQ Guru
 
Registered: Nov 2003
Location: West Jordan, UT, USA
Distribution: Slackware
Posts: 5,705

Rep: Reputation: 3479Reputation: 3479Reputation: 3479Reputation: 3479Reputation: 3479Reputation: 3479Reputation: 3479Reputation: 3479Reputation: 3479Reputation: 3479Reputation: 3479
Quote:
Originally Posted by someone named bert View Post
Richard Cranium, when I `init 4`'ed after `nvidia-switch --remove`, KDE didn't even offer the native resolution of my display. Do I need to do anythong else to use noveau properly?
You would need to make sure nouveau isn't blacklisted. That needs to be done when installing the binary driver and I'm not sure if nvidia-switch --remove will take it away. Have a look in /etc/modprobe.d/ and make sure there are no files there that blacklist the nouveau module.
 
3 members found this post helpful.
Old 02-02-2019, 05:53 PM   #7
someone named bert
LQ Newbie
 
Registered: Nov 2013
Distribution: Slackware64 14.2
Posts: 24

Original Poster
Rep: Reputation: Disabled
Angry

Thanks bassmadrigal.

I got the proprietary driver mainly for playing UFO:AI, it made the difference between that being playable or not. I didn't play for a long time, so let me try noveau.

The fonts render differently now, a bit bigger in most applications.
More importantly, KDE keeps telling me that I need to reduce my resolution to 0*0 to be able to run OpenGL desktop effects.
glxgears started from a terminal in KDE fails with:
Code:
X Error of failed request:  BadValue (integer parameter out of range for operation)
  Major opcode of failed request:  154 (GLX)
  Minor opcode of failed request:  3 (X_GLXCreateContext)
  Value in failed request:  0x0
  Serial number of failed request:  23
  Current serial number in output stream:  24
Xorg.0.log doesn't show anything that looks like a problem, besides "unloading nv" maybe (I don't know the relation between "nv" and noveau).
 
Old 02-02-2019, 11:03 PM   #8
bassmadrigal
LQ Guru
 
Registered: Nov 2003
Location: West Jordan, UT, USA
Distribution: Slackware
Posts: 5,705

Rep: Reputation: 3479Reputation: 3479Reputation: 3479Reputation: 3479Reputation: 3479Reputation: 3479Reputation: 3479Reputation: 3479Reputation: 3479Reputation: 3479Reputation: 3479
Quote:
Originally Posted by someone named bert View Post
Thanks bassmadrigal.

I got the proprietary driver mainly for playing UFO:AI, it made the difference between that being playable or not. I didn't play for a long time, so let me try noveau.

The fonts render differently now, a bit bigger in most applications.
More importantly, KDE keeps telling me that I need to reduce my resolution to 0*0 to be able to run OpenGL desktop effects.
glxgears started from a terminal in KDE fails with:
Code:
X Error of failed request:  BadValue (integer parameter out of range for operation)
  Major opcode of failed request:  154 (GLX)
  Minor opcode of failed request:  3 (X_GLXCreateContext)
  Value in failed request:  0x0
  Serial number of failed request:  23
  Current serial number in output stream:  24
Xorg.0.log doesn't show anything that looks like a problem, besides "unloading nv" maybe (I don't know the relation between "nv" and noveau).
Maybe posting the output of /var/log/Xorg.0.log and glxinfo could help some diagnose your issues. I have basically no experience with Nvidia cards as I don't run them. But we do have a lot of knowledgeable people on this forum that do use them (both with the proprietary driver and others with the opensouce nouveau).
 
Old 02-03-2019, 12:04 AM   #9
Richard Cranium
Senior Member
 
Registered: Apr 2009
Location: Carrollton, Texas
Distribution: Slackware64 14.2
Posts: 3,184

Rep: Reputation: 1549Reputation: 1549Reputation: 1549Reputation: 1549Reputation: 1549Reputation: 1549Reputation: 1549Reputation: 1549Reputation: 1549Reputation: 1549Reputation: 1549
I've had issues with nvidia-switch not quite doing the right thing. (Mainly due to my not dropping into runlevel 3, run nvidia-switch --remove, and then upgrade the nvidia packages.)

As it so happens, I've broken my own system on the upgrade to 4.4.172! Lucky you!

run:
Code:
ls -l /usr/lib64/xorg/modules/extensions/
(or the 32 bit equivalent)

On my machine...

Code:
$ ls -l /usr/lib64/xorg/modules/extensions/
total 14932
-rwxr-xr-x 1 root root     1503 Oct 18  2017 libglx.la*
lrwxrwxrwx 1 root root       29 Feb  2 20:12 libglxserver_nvidia.so -> libglxserver_nvidia.so.410.78*
-rwxr-xr-x 1 root root 14997128 Feb  2 12:21 libglxserver_nvidia.so.410.78*
lrwxrwxrwx 1 root root       29 Feb  2 20:12 libglx.so -> libglxserver_nvidia.so.410.78*
-rwxr-xr-x 1 root root   285992 Apr 15  2016 libglx.so-xorg*
I ran
Code:
nvidia-switch --remove
as root again (which did not result in happiness). I then ran the sequence
Code:
cd /usr/lib64/xorg/modules/extensions/
mv libglx.so-xorg libglx.so
as root and then restarted X windows.

glxgears was able to run afterwards.

EDIT: My card is a GeForce GT 640, which probably isn't your card; maybe we can still help if things aren't working for you.

Last edited by Richard Cranium; 02-03-2019 at 12:08 AM. Reason: I restarted X-windows and stuff worked.
 
Old 02-03-2019, 12:28 PM   #10
kingbeowulf
Member
 
Registered: Oct 2003
Location: WA
Distribution: Slackware64 14.2 Slackware 14.2, Slackware{32,64}-current
Posts: 878
Blog Entries: 9

Rep: Reputation: 352Reputation: 352Reputation: 352Reputation: 352
I'll take a look at nvidia-switch. Nvidia tends to move stuff around and the older legacy scripts still use an old version.

see also: https://www.linuxquestions.org/quest...ml#post5957248
 
Old 02-10-2019, 12:46 PM   #11
someone named bert
LQ Newbie
 
Registered: Nov 2013
Distribution: Slackware64 14.2
Posts: 24

Original Poster
Rep: Reputation: Disabled
Sorry, the problem was just that I didn't uninstall the two nvidia-legacy340 packages. I only did nvidia-switch --remove and renamed the blacklist file in /etc/modprobe.d/. Removepkg'ing the two packages fixed it fine.

I'm going to mark this thread as solved when nVidia releases a fixed 340 driver OR when it's clear they won't.

Last edited by someone named bert; 02-10-2019 at 12:46 PM. Reason: add one slash
 
  


Reply

Tags
graphics, kernel 4.4.172, nvidia, sbo


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
Kernel 4.4.172 on Slack64 and Nvidia camorri Slackware 45 Yesterday 07:44 PM
nvidia-driver SBo The symbolic link '/usr/lib/libGL.so.1' does not point to 'tmp/SBo/package-nvidia-driver/usr/lib64/libGL.so.1' Gerardo Zamudio Slackware 5 07-30-2017 11:44 PM
Questions for Robby, ponce, or anyone from SBo about SBo submission requirements. ReaperX7 Slackware 4 06-07-2015 12:30 PM
Nvidia-driver.SlackBuild from SBo (or: I am a bad and sloppy SBo maintainer) kingbeowulf Slackware 8 08-31-2012 03:41 AM

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

All times are GMT -5. The time now is 03:00 PM.

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