4.4.172 kernel and nividia-legacy*340* (SBo)

j12i · 02-02-2019, 06:48 AM

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

RadicalDreamer · 02-02-2019, 07:20 AM

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.

Petri Kaukasoina · 02-02-2019, 09:34 AM

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

Richard Cranium · 02-02-2019, 10:38 AM

If it's that old of a card, maybe the nouveau driver will perform well enough for you.

j12i · 02-02-2019, 10:45 AM

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

bassmadrigal · 02-02-2019, 11:42 AM

Quote:

Originally Posted by someone named bert

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.

j12i · 02-02-2019, 04:53 PM

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

bassmadrigal · 02-02-2019, 10:03 PM

Quote:

Originally Posted by someone named bert

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

Richard Cranium · 02-02-2019, 11:04 PM

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.

kingbeowulf · 02-03-2019, 11:28 AM

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

j12i · 02-10-2019, 11:46 AM

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.

kevmccor · 04-03-2019, 06:57 PM

I forgot why I wasn't upgrading my kernel, so I did the upgrade to 4.4.172. Then the nvidia-legacy340.104 reinstallation process failed. It appears the nvidia-legacy-kernel340-104 build failed -- nvidia.ko failed to build -- Makefile:189: [nvidia.ko] Error 1

I have a ThinkPad t61p, with a Quadro FX 570M chip.

It was working fine with the previous kernel, but I did not pay attention to the version number. I believe the best solution is to revert back to the previous kernel. I wonder if there any of those older packages left lying around somewhere. I suspect this is how they make people buy new computers.

elcore · 04-04-2019, 01:28 AM

On kernels 4.9.x and 4.14.x the 340 legacy driver still works. Relevant thread:

https://www.linuxquestions.org/quest...ld-4175649416/

twy · 04-04-2019, 09:36 AM

You can patch nvidia 340.107 for kernel 4.4.168+ using the patch provided by the archlinux project:

https://aur.archlinux.org/packages/nvidia-340xx-lts44/
https://aur.archlinux.org/cgit/aur.g...ia-340xx-lts44

The commands to patch and install are like this:

# ls kernel-4.4.168.patch
# chmod +x NVIDIA-Linux-x86_64-340.107.run
# ./NVIDIA-Linux-x86_64-340.107.run -x
# cd NVIDIA-Linux-x86_64-340.107
# patch -p1 < ../kernel-4.4.168.patch
# ./nvidia-installer

Works for me on 4.4.177. Maybe I can upgrade to 4.4.178 later.