Nvidia drivers
Recent nvidia updates
There have been other recent updates besides 304.128 on ftp://download.nvidia.com/XFree86/Linux-x86/
e.g.
340.93
346.96
352.41
355.11
e.g.
340.93
346.96
352.41
355.11
LxPup = Puppy + LXDE
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64
- Argolance
- Posts: 3767
- Joined: Sun 06 Jan 2008, 22:57
- Location: PORT-BRILLET (Mayenne - France)
- Contact:
Bonjour,
I am running Puppy Precise 5.7.1 with kernel 3.9.11.
I tried to use getnividia to build a 340.93 NVIDIA driver SFS file.
I loaded the devx, downloaded/loaded the "kernel_src-3.9.11-patched.sfs" from BK repository, installed getnvidia and so on. Unfortunately, getnvidia says that my kernel source package does not match with the running kernel.
What's wrong?
Thank you for your attention.
Corldialement.
I am running Puppy Precise 5.7.1 with kernel 3.9.11.
I tried to use getnividia to build a 340.93 NVIDIA driver SFS file.
I loaded the devx, downloaded/loaded the "kernel_src-3.9.11-patched.sfs" from BK repository, installed getnvidia and so on. Unfortunately, getnvidia says that my kernel source package does not match with the running kernel.
What's wrong?
Thank you for your attention.
Corldialement.
- Attachments
-
- 151022_130333_440x320_easyshot.jpg
- (27.81 KiB) Downloaded 6980 times
- Argolance
- Posts: 3767
- Joined: Sun 06 Jan 2008, 22:57
- Location: PORT-BRILLET (Mayenne - France)
- Contact:
Sorry! The "kernel_src-3.9.11-patched.sfs" was in the list of mounted sfs, but only queued and not really loaded: this is why getnvidia displayed the error message. As this may happen to "unexperimented" users like me, I do not delete my message...
Thank you to shinobar for getnvidia which is really amazing and did the work perfectly.
Cordialement.
Thank you to shinobar for getnvidia which is really amazing and did the work perfectly.
Cordialement.
Nvidia driver building for kernel 4.3+
Heads up!
With kernels 4.3 onwards, if the kernel is configured:
any new modules compiled for that kernel will need to be cryptographically signed using utility /usr/src/linux/scripts/sign-file
found in the kernel-sources.
GetNvidia will need to be updated to include signing if nvidia drivers are to continue working on kernels 4.3 onwards.
For example, nvidia-304.131 fails to build for stemsee's kernel 4.3.2 because module loading fails because the module is not signed.
(there is a futher problem with stemsee's 4.3.2 that sign-file does not work due to some problem with missing version information for libcrypto).
Cheers
peebee
With kernels 4.3 onwards, if the kernel is configured:
Code: Select all
CONFIG_MODULE_SIG=y
CONFIG_MODULE_SIG_ALL=y
CONFIG_MODULE_SIG_SHA1=y
CONFIG_MODULE_SIG_HASH="sha1"
found in the kernel-sources.
GetNvidia will need to be updated to include signing if nvidia drivers are to continue working on kernels 4.3 onwards.
For example, nvidia-304.131 fails to build for stemsee's kernel 4.3.2 because module loading fails because the module is not signed.
(there is a futher problem with stemsee's 4.3.2 that sign-file does not work due to some problem with missing version information for libcrypto).
Cheers
peebee
LxPup = Puppy + LXDE
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64
Re: Nvidia driver building for kernel 4.3+
I'm running Tahr 6.0.5 with Stemsee's 4.3.2 32bit pae kernel and downloaded/compiled NVIDIA-Linux-x86-340.96.run OK and its apparently working fine with my 8600GT nvidia graphics card (I used Shinobar's getnvidia-1.0.pet to perform the compile).peebee wrote:Heads up!
With kernels 4.3 onwards, if the kernel is configured:any new modules compiled for that kernel will need to be cryptographically signed using utility /usr/src/linux/scripts/sign-fileCode: Select all
CONFIG_MODULE_SIG=y CONFIG_MODULE_SIG_ALL=y CONFIG_MODULE_SIG_SHA1=y CONFIG_MODULE_SIG_HASH="sha1"
found in the kernel-sources.
GetNvidia will need to be updated to include signing if nvidia drivers are to continue working on kernels 4.3 onwards.
For example, nvidia-304.131 fails to build for stemsee's kernel 4.3.2 because module loading fails because the module is not signed.
(there is a futher problem with stemsee's 4.3.2 that sign-file does not work due to some problem with missing version information for libcrypto).
Cheers
peebee
Looking at the DotConfig the configuration matches what you posted above.
Don't really know what I'm doing, just follow the instructions - but from my perspective it all looks fine !!??
[size=75]( ͡° ͜ʖ ͡°) :wq[/size]
[url=http://murga-linux.com/puppy/viewtopic.php?p=1028256#1028256][size=75]Fatdog multi-session usb[/url][/size]
[size=75][url=https://hashbang.sh]echo url|sed -e 's/^/(c/' -e 's/$/ hashbang.sh)/'|sh[/url][/size]
[url=http://murga-linux.com/puppy/viewtopic.php?p=1028256#1028256][size=75]Fatdog multi-session usb[/url][/size]
[size=75][url=https://hashbang.sh]echo url|sed -e 's/^/(c/' -e 's/$/ hashbang.sh)/'|sh[/url][/size]
Re: Nvidia driver building for kernel 4.3+
Perhaps different versions - mine older 304.131 - yours 340.96 build differently??rufwoof wrote:compiled NVIDIA-Linux-x86-340.96.run OK and its apparently working fine with my 8600GT nvidia graphics card (I used Shinobar's getnvidia-1.0.pet to perform the compile).
from my perspective it all looks fine !!??
Can you do - modinfo nvidia
in a terminal and see if your driver is signed?
Thanks
peebee
LxPup = Puppy + LXDE
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64
Re: Nvidia driver building for kernel 4.3+
Hi peebee. Don't think it is. I see Licence nvidia ???peebee wrote:Can you do - modinfo nvidia
in a terminal and see if your driver is signed?
- Attachments
-
- modinfo.jpg
- (57.04 KiB) Downloaded 6739 times
[size=75]( ͡° ͜ʖ ͡°) :wq[/size]
[url=http://murga-linux.com/puppy/viewtopic.php?p=1028256#1028256][size=75]Fatdog multi-session usb[/url][/size]
[size=75][url=https://hashbang.sh]echo url|sed -e 's/^/(c/' -e 's/$/ hashbang.sh)/'|sh[/url][/size]
[url=http://murga-linux.com/puppy/viewtopic.php?p=1028256#1028256][size=75]Fatdog multi-session usb[/url][/size]
[size=75][url=https://hashbang.sh]echo url|sed -e 's/^/(c/' -e 's/$/ hashbang.sh)/'|sh[/url][/size]
Re: Nvidia driver building for kernel 4.3+
Thanks rufwoofrufwoof wrote:Hi peebee. Don't think it is. I see Licence nvidia ???peebee wrote:Can you do - modinfo nvidia
in a terminal and see if your driver is signed?
I'm trying to compile 304.131 drivers for slackocurrent (based on slackware current) however the same error occurs for both tahrpup-6.0.5 and slacko-6.3.0
Nvidia Drivers build no problem for k4.1.11 from 01micko and k4.2.5 from stemsee.
But with k4.3.2 from stemsee I get:
More investigation is needed....ERROR: Unable to load the kernel module.
ERROR: Installation has failed.
nvidia: module license 'NVIDIA' taints kernel.
nvidia: module verification failed: signature and/or required key missing - tainting kernel
This link has useful info about module signing:
https://wiki.gentoo.org/wiki/Signed_ker ... le_support
Cheers
peebee
Last edited by peebee on Sat 02 Jan 2016, 17:05, edited 1 time in total.
LxPup = Puppy + LXDE
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64
Don't know if it has any bearing, but for reference I used the devx from Tahr 6.0.5 - and the kernel source, zdrv, vmlinuz from emsee 4.3.2 (and I appended the Tahr 6.0.5 ID (from DISTRO_SPECS) to zdrv and vmlinuz)
[size=75]( ͡° ͜ʖ ͡°) :wq[/size]
[url=http://murga-linux.com/puppy/viewtopic.php?p=1028256#1028256][size=75]Fatdog multi-session usb[/url][/size]
[size=75][url=https://hashbang.sh]echo url|sed -e 's/^/(c/' -e 's/$/ hashbang.sh)/'|sh[/url][/size]
[url=http://murga-linux.com/puppy/viewtopic.php?p=1028256#1028256][size=75]Fatdog multi-session usb[/url][/size]
[size=75][url=https://hashbang.sh]echo url|sed -e 's/^/(c/' -e 's/$/ hashbang.sh)/'|sh[/url][/size]
I get the same error message with both slacko-6.3.0 and tahrpup-6.0.5 with k4.3.2 so its not the devx that's the problem after all....this is trying to build the 304.131 driver....rufwoof wrote:Don't know if it has any bearing, but for reference I used the devx from Tahr 6.0.5 - and the kernel source, zdrv, vmlinuz from emsee 4.3.2 (and I appended the Tahr 6.0.5 ID (from DISTRO_SPECS) to zdrv and vmlinuz)
LxPup = Puppy + LXDE
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64
Booted to command prompt using emsee 4.3.2 kernel and tahr 6.0.5 puppy. Ran the getnvidia for my own graphics card (340.96) and ran through to completion OK.
Ran getnvidia for the 304.131 (32 bit linux x86) and it seems to compile but then fails at the end (doesn't build pet's/sfs).
/root/getnvidia.log has 5 lines complaining about unknown symbol mtrr_add
/var/log/nvidia-installer.log has a error near the top ... line 28 onwards of (might not be a actual error, maybe just showing code ???)
and last few lines (3538 onwards) of
Looks to my naive eyes that it compiled/built, but hit problems loading the module, maybe because it conflicts with my hardware ???
Don't know if that's of any help/use.
Ran getnvidia for the 304.131 (32 bit linux x86) and it seems to compile but then fails at the end (doesn't build pet's/sfs).
/root/getnvidia.log has 5 lines complaining about unknown symbol mtrr_add
/var/log/nvidia-installer.log has a error near the top ... line 28 onwards of (might not be a actual error, maybe just showing code ???)
Code: Select all
-> Building kernel module:
executing: 'cd ./kernel; make module SYSSRC=/lib/modules/4.3.2-EmSee-32-pae/source SYSOUT=/lib/modules/4.3.2-EmSee-32-pae/build'...
NVIDIA: calling KBUILD...
make -C /lib/modules/4.3.2-EmSee-32-pae/build KBUILD_SRC=/usr/src/linux \
-f /usr/src/linux/Makefile modules
test -e include/generated/autoconf.h -a -e include/config/auto.conf || ( \
echo >&2; \
echo >&2 " ERROR: Kernel configuration is invalid."; \
echo >&2 " include/generated/autoconf.h or include/config/auto.conf are missing.";\
echo >&2 " Run 'make oldconfig && make prepare' on kernel src to fix it."; \
echo >&2 ; \
/bin/false)
mkdir -p /tmp/selfgz18575/NVIDIA-Linux-x86-304.131/kernel/.tmp_versions ; rm -f /tmp/selfgz18575/NVIDIA-Linux-x86-304.131/kernel/.tmp_versions/*
make -f /usr/src/linux/scripts/Makefile.build obj=/tmp/selfgz18575/NVIDIA-Linux-x86-304.131/kernel
cc -Wp,-MD,/tmp/selfgz18575/NVIDIA-Linux-x86-304.131/kernel/.nv.o.d -nostdinc -isystem /usr/lib/gcc/i686-linux-gnu/4.8/include -I/usr/src/linux/arch/x86/include -Iarch/x86/include/generated/uapi -Iarch/x86/include/generated -I/usr/src/linux/include -Iinclude -I/usr/src/linu
Code: Select all
NVIDIA: left KBUILD.
-> done.
-> Kernel module compilation complete.
-> Installing both new and classic TLS OpenGL libraries.
-> Uninstalling the previous installation with /bin/nvidia-uninstall.
-> Searching for conflicting X files:
-> done.
-> Searching for conflicting OpenGL files:
-> done.
-> Installing 'NVIDIA Accelerated Graphics Driver for Linux-x86' (304.131):
executing: '/sbin/ldconfig'...
executing: '/sbin/depmod -aq 4.3.2-EmSee-32-pae'...
-> done.
-> Driver file installation is complete.
ERROR: Unable to load the kernel module.
ERROR: Installation has failed. Please see the file '/var/log/nvidia-installer.log' for details. You may find suggestions on fixing installation problems in the README available on the Linux driver download page at www.nvidia.com.
Don't know if that's of any help/use.
[size=75]( ͡° ͜ʖ ͡°) :wq[/size]
[url=http://murga-linux.com/puppy/viewtopic.php?p=1028256#1028256][size=75]Fatdog multi-session usb[/url][/size]
[size=75][url=https://hashbang.sh]echo url|sed -e 's/^/(c/' -e 's/$/ hashbang.sh)/'|sh[/url][/size]
[url=http://murga-linux.com/puppy/viewtopic.php?p=1028256#1028256][size=75]Fatdog multi-session usb[/url][/size]
[size=75][url=https://hashbang.sh]echo url|sed -e 's/^/(c/' -e 's/$/ hashbang.sh)/'|sh[/url][/size]
304 series problem with k4.3
I get those errors too....rufwoof wrote:/root/getnvidia.log has 5 lines complaining about unknown symbol mtrr_add
Looks like it's a known problem introduced with k4.3 but affecting 304.* series drivers only....
https://bugs.archlinux.org/task/47092
https://devtalk.nvidia.com/default/topi ... nt=4758413
so it needs a patch to the kernel - or for nvidia to release an updated 304.*.run
LxPup = Puppy + LXDE
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64
IndeedLooks like it's a known problem introduced with k4.3 but affecting 304.* series drivers only....
http://git.kernel.org/cgit/linux/kernel ... 1486285bdc
The following snippet taken out of this https://raw.githubusercontent.com/manja ... mbol.patch manjaro patch indicates the cause of the problem with the above kernel change
mtrr_add() and mtrr_del() having been 'removed', but needed by 304 nvidia driver+ * With 2baa891e42d84159b693eadd44f6fe1486285bdc the kernel internal
+ * MTRR interfaces (unexport mtrr_add() and mtrr_del()) got removed.
+ * However Nvidia legacy driver 304xx still needs these exports
[size=75]( ͡° ͜ʖ ͡°) :wq[/size]
[url=http://murga-linux.com/puppy/viewtopic.php?p=1028256#1028256][size=75]Fatdog multi-session usb[/url][/size]
[size=75][url=https://hashbang.sh]echo url|sed -e 's/^/(c/' -e 's/$/ hashbang.sh)/'|sh[/url][/size]
[url=http://murga-linux.com/puppy/viewtopic.php?p=1028256#1028256][size=75]Fatdog multi-session usb[/url][/size]
[size=75][url=https://hashbang.sh]echo url|sed -e 's/^/(c/' -e 's/$/ hashbang.sh)/'|sh[/url][/size]
nvidia 304.* patch for >k4.3
A patch has become available to enable the legacy 304.131 driver to correctly install on >k.4.3
I've done a manual build for k4.4.1 to test - see screenie
It would be very nice if such patches could be applied as part of get-nvidia....
The patch is attached - false .gz
I've done a manual build for k4.4.1 to test - see screenie
It would be very nice if such patches could be applied as part of get-nvidia....
The patch is attached - false .gz
- Attachments
-
- nvidia_mtrr_k4_3.patch.gz
- (446 Bytes) Downloaded 795 times
-
- nvidia-k4.4.1.png
- (117.2 KiB) Downloaded 6378 times
LxPup = Puppy + LXDE
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64
Re: nvidia 304.* patch for >k4.3
Just to report that with 666philb's excellent help I have been able to apply the >k4.3 patch to the 304.131 .run file and then use getnvidia to build the sfs.peebee wrote:It would be very nice if such patches could be applied as part of get-nvidia....
The secret is knowing that nvidia have used the makeself utility to build the .run files.
You can therefore extract (unpack) the .run file, patch it and then rebuild a patched .run file using the makeself utility which is contained within the .run archive.
The links 666philb gave me to explain this process were:
https://tr.opensuse.org/NVIDIA
http://stephanepeter.com/makeself/
The runes I used were:
Code: Select all
cd directory/where/you/saved/NVIDIA-Linux-x86-304.131.run
./NVIDIA-Linux-x86-304.131.run --extract-only
apply patch
./NVIDIA-Linux-x86-304.131/makeself.sh \
--target-os Linux --target-arch x86 \
NVIDIA-Linux-x86-304.131 \
NVIDIA-Linux-x86-304.131-patched.run \
"NVIDIA driver 304.131 patched for k4.3+" \
./nvidia-installer
Cheers
peebee
LxPup = Puppy + LXDE
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64
304.131 for k4.6
Here is the patch needed to get nvidia-304.131 to compile on kernel 4.6
Remove false .gz
This is in addition to the kernel 4.3 patch above.
You can download the patched .run if anybody wants it.
Cheers
peebee
Remove false .gz
This is in addition to the kernel 4.3 patch above.
You can download the patched .run if anybody wants it.
Cheers
peebee
- Attachments
-
- nvidia-304.131-k4.6.patch.gz
- remove false .gz
- (1.76 KiB) Downloaded 581 times
LxPup = Puppy + LXDE
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64
Nvidia driver for Slacko6.0
Hi peebee,
I can't find the nvidia 304xx driver for
http://lx-pup.weebly.com/slacko60.html
Please let me know if this is available.
btw. unlike any other distros, here the leds Num, Caps and Scroll lock on my keyboard don't light, although the keys work properly. Can this be changed?
I can't find the nvidia 304xx driver for
http://lx-pup.weebly.com/slacko60.html
Please let me know if this is available.
btw. unlike any other distros, here the leds Num, Caps and Scroll lock on my keyboard don't light, although the keys work properly. Can this be changed?
Re: Nvidia driver for Slacko6.0
I've uploaded to:riedzig wrote:Hi peebee,
I can't find the nvidia 304xx driver for
http://lx-pup.weebly.com/slacko60.html
Please let me know if this is available.
btw. unlike any other distros, here the leds Num, Caps and Scroll lock on my keyboard don't light, although the keys work properly. Can this be changed?
http://smokey01.com/peebee/nvidia/nvidi ... e-s630.sfs
Can't answer the keyboard lights query I'm afraid - suggest you post somewhere else on the forum with more details of your computer hardware....
LxPup = Puppy + LXDE
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64
-
- Posts: 2
- Joined: Thu 30 Jun 2016, 15:15