How to install nvidia non-free driver 304.*** in Slitaz 5?

SliTaz Forum » English Support » Live and installation

How to install nvidia non-free driver 304.*** in Slitaz 5?

(18 posts) (5 voices)

Started 7 years ago by TraceE
Latest reply from gdesilva
This topic is resolved

Tags:

No tags yet.

12 Next »

TraceE

offline
Member

I am trying to use Openscad (3d CAD application) in the latest 5 rolling core.

The Slitaz package loads and starts but the section of the gui where the design is drawn is missing and I can see right through to the desktop. I have a strong suspicion that it may be a driver problem.

I think I might need to use the nvidia 173 non-free driver for my nvidia 7000m/610 GPU ... can anyone tell me how to load it properly?

I download it ... then run nvidia-xconfig as root and restart the xserver but it can't find the nvidia driver.

I can't find any posts detailing how to install the non-free driver in 5 ... can someone give me a step by step please?

Posted 7 years ago #
gdesilva

offline
Member

According to nVidia site the driver you would need is 304.134 - check out here

http://www.nvidia.com/download/driverResults.aspx/112986/en-us under the supported products tab.

Posted 7 years ago #
TraceE

offline
Member

Thanks for that gdesilva ... can you tell me the easiest way to install it in 5 rolling core please?

Posted 7 years ago #
totoetsasoeur

offline
Moderator

It reminds me of something ;-)

It was a long time ago, but it may still work (I haven't tested today):
http://forum.slitaz.org/topic/slitaz-40-rc2-install-nvidia-non-free-drivers

Keep us informed.

Posted 7 years ago #
gdesilva

offline
Member

Yes, just follow the steps described in totoetsasoeur's post. However, when I ran the script I had to provide the location of the header files - it could have been just me. If you get an error stating could not find header files or something to that effect you would need to provide the linux source directory as an option when running the script. See how you go - if you run into problems I can reinstall my driver and let you know the the details - hopefully you will not have to.

Posted 7 years ago #
TraceE

offline
Member

Is this what you mean? asking for the file to patch:

root@slitaz:/home/tux# get-linux-source
Connecting to http://www.kernel.org (199.204.44.194:80)
Connecting to http://www.kernel.org (198.145.20.140:443)
Connecting to http://www.kernel.org (198.145.20.140:80)
Connecting to http://www.kernel.org (199.204.44.194:443)
Connecting to http://www.kernel.org (198.145.20.140:80)
Connecting to http://www.kernel.org (198.145.20.140:443)
linux-3.2.71.tar.xz 100% |*******************************| 64110k 0:00:00 ETA
patching file scripts/package/Makefile
Hunk #2 FAILED at 152.
1 out of 2 hunks FAILED -- saving rejects to file scripts/package/Makefile.rej
Apply linux-diff.u
patching file arch/x86/vdso/Makefile
patching file scripts/Makefile.lib
Apply linux-header.u
patching file arch/x86/boot/header.S
Apply linux-freeinitrd.u
patching file arch/x86/mm/init.c
patching file init/initramfs.c
Apply linux-subroot.u
patching file Documentation/kernel-parameters.txt
patching file init/do_mounts.c
Apply linux-romfs.u
patching file fs/romfs/super.c
Apply linux-CVE-2016-5696.u
patching file net/ipv4/tcp_input.c
Apply aufs3-base.patch
patching file fs/namei.c
Hunk #1 succeeded at 1763 (offset 10 lines).
patching file fs/splice.c
Hunk #1 succeeded at 1116 (offset 31 lines).
Hunk #2 succeeded at 1144 (offset 31 lines).
patching file include/linux/namei.h
patching file include/linux/splice.h
Apply aufs3-standalone.patch
patching file fs/file_table.c
patching file fs/inode.c
patching file fs/namei.c
Hunk #1 succeeded at 1767 (offset 10 lines).
patching file fs/namespace.c
Hunk #1 succeeded at 1507 (offset 1 line).
patching file fs/notify/group.c
patching file fs/notify/mark.c
Hunk #2 succeeded at 192 (offset 2 lines).
Hunk #3 succeeded at 280 (offset 2 lines).
Hunk #4 succeeded at 336 (offset 2 lines).
patching file fs/open.c
patching file fs/splice.c
Hunk #1 succeeded at 1140 (offset 31 lines).
Hunk #2 succeeded at 1167 (offset 31 lines).
patching file security/commoncap.c
Hunk #1 succeeded at 981 (offset 6 lines).
patching file security/device_cgroup.c
patching file security/security.c
Apply aufs3-loopback.patch
patching file drivers/block/loop.c
Hunk #13 succeeded at 948 (offset 5 lines).
Hunk #14 succeeded at 958 (offset 5 lines).
Hunk #15 succeeded at 1006 (offset 5 lines).
Hunk #16 succeeded at 1027 (offset 5 lines).
Hunk #17 succeeded at 1070 (offset 7 lines).
can't find file to patch at input line 189
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/fs/aufs/f_op.c b/fs/aufs/f_op.c
|index d6318f08b..56555de 100644
|--- a/fs/aufs/f_op.c
|+++ b/fs/aufs/f_op.c
--------------------------
File to patch:

What do I put for the file to patch?

Posted 7 years ago #
gdesilva

offline
Member

No, the possible error I was referring to would have come up in step 5 in totoetsasoeur's post. Did you run all the commands under step 3 before trying to run get-linux-source?

I would run all of the following commands in the order given.

#tazpkg get-install slitaz-toolchain
#tazpkg get-install ncurses-dev
#tazpkg get-install perl
#tazpkg get-install linux-source
#tazpkg get-install xorg-server

Then run get-linux-source and you should not get any errors at this point. If you do then there are more issues with your installation.

Download the driver script as per Step 0 obviously changing the version number to suit what you need and run the nVidia script.

Hope this helps.

Posted 7 years ago #
TraceE

offline
Member

Still the same ... all the packages were installed but I used --forced to re-install them all again:

tux@slitaz:~$ su
Password:
root@slitaz:/home/tux# tazpkg get-install slitaz-toolchain

"slitaz-toolchain" package is already installed.
You can use the --forced option to force installation.

root@slitaz:/home/tux# tazpkg get-install slitaz-toolchain --forced
Package "slitaz-toolchain-5.0" already in the cache

Installation of package "slitaz-toolchain"
================================================================================
SliTaz meta package to rebuild or install current toolchain.
--------------------------------------------------------------------------------
Copying package... [ Done ]
Extracting package... [ Done ]
Remember modified packages... [ Done ]
Installing package... [ Done ]
Removing all tmp files... [ Done ]
================================================================================
Package "slitaz-toolchain" (5.0) is installed.

root@slitaz:/home/tux# tazpkg get-install ncurses-dev

"ncurses-dev" package is already installed.
You can use the --forced option to force installation.

root@slitaz:/home/tux# tazpkg get-install ncurses-dev --forced
Package "ncurses-dev-5.9" already in the cache

Installation of package "ncurses-dev"
================================================================================
Devel files for the ncurses library.
--------------------------------------------------------------------------------
Copying package... [ Done ]
Extracting package... [ Done ]
Remember modified packages... [ Done ]
Installing package... [ Done ]
Removing all tmp files... [ Done ]
================================================================================
Package "ncurses-dev" (5.9) is installed.

root@slitaz:/home/tux# tazpkg get-install perl

"perl" package is already installed.
You can use the --forced option to force installation.

root@slitaz:/home/tux# tazpkg get-install perl --forced
Package "perl-5.12.3" already in the cache

Installation of package "perl"
================================================================================
Full Perl interpreter and modules.
--------------------------------------------------------------------------------
Copying package... [ Done ]
Extracting package... [ Done ]
Remember modified packages... [ Done ]
Execute pre-install commands... [ Done ]
Installing package... [ Done ]
Removing all tmp files... [ Done ]
================================================================================
Package "perl" (5.12.3) is installed.

root@slitaz:/home/tux# tazpkg get-install linux-source

"linux-source" package is already installed.
You can use the --forced option to force installation.

root@slitaz:/home/tux# tazpkg get-install linux-source --forced
Package "linux-source-3.2.71" already in the cache

Installation of package "linux-source"
================================================================================
The Linux kernel source files.
--------------------------------------------------------------------------------
Copying package... [ Done ]
Extracting package... [ Done ]
Remember modified packages... [ Done ]
Installing package... [ Done ]
Removing all tmp files... [ Done ]
Update system databases... [ Done ]
================================================================================
Package "linux-source" (3.2.71) is installed.

root@slitaz:/home/tux# tazpkg get-install xorg-server

"xorg-server" package is already installed.
You can use the --forced option to force installation.

root@slitaz:/home/tux# tazpkg get-install xorg-server --forced
xorg-server-1.12.4.t 100% |*******************************| 967k 0:00:00 ETA
Installation of package "xorg-server"
================================================================================
Xorg core server.
--------------------------------------------------------------------------------
Copying package... [ Done ]
Extracting package... [ Done ]
Remember modified packages... [ Done ]
Installing package... [ Done ]
Removing all tmp files... [ Done ]
Execute post-install commands... [ Done ]
================================================================================
Package "xorg-server" (1.12.4) is installed.

root@slitaz:/home/tux# get-linux-source
Connecting to http://www.kernel.org (149.20.4.69:80)
Connecting to http://www.kernel.org (199.204.44.194:443)
Connecting to http://www.kernel.org (198.145.20.140:80)
Connecting to http://www.kernel.org (149.20.4.69:443)
patching file scripts/package/Makefile
Hunk #2 FAILED at 152.
1 out of 2 hunks FAILED -- saving rejects to file scripts/package/Makefile.rej
Apply linux-diff.u
patching file arch/x86/vdso/Makefile
patching file scripts/Makefile.lib
Apply linux-header.u
patching file arch/x86/boot/header.S
Apply linux-freeinitrd.u
patching file arch/x86/mm/init.c
patching file init/initramfs.c
Apply linux-subroot.u
patching file Documentation/kernel-parameters.txt
patching file init/do_mounts.c
Apply linux-romfs.u
patching file fs/romfs/super.c
Apply linux-CVE-2016-5696.u
patching file net/ipv4/tcp_input.c
Apply aufs3-base.patch
patching file fs/namei.c
Hunk #1 succeeded at 1763 (offset 10 lines).
patching file fs/splice.c
Hunk #1 succeeded at 1116 (offset 31 lines).
Hunk #2 succeeded at 1144 (offset 31 lines).
patching file include/linux/namei.h
patching file include/linux/splice.h
Apply aufs3-standalone.patch
patching file fs/file_table.c
patching file fs/inode.c
patching file fs/namei.c
Hunk #1 succeeded at 1767 (offset 10 lines).
patching file fs/namespace.c
Hunk #1 succeeded at 1507 (offset 1 line).
patching file fs/notify/group.c
patching file fs/notify/mark.c
Hunk #2 succeeded at 192 (offset 2 lines).
Hunk #3 succeeded at 280 (offset 2 lines).
Hunk #4 succeeded at 336 (offset 2 lines).
patching file fs/open.c
patching file fs/splice.c
Hunk #1 succeeded at 1140 (offset 31 lines).
Hunk #2 succeeded at 1167 (offset 31 lines).
patching file security/commoncap.c
Hunk #1 succeeded at 981 (offset 6 lines).
patching file security/device_cgroup.c
patching file security/security.c
Apply aufs3-loopback.patch
patching file drivers/block/loop.c
Hunk #13 succeeded at 948 (offset 5 lines).
Hunk #14 succeeded at 958 (offset 5 lines).
Hunk #15 succeeded at 1006 (offset 5 lines).
Hunk #16 succeeded at 1027 (offset 5 lines).
Hunk #17 succeeded at 1070 (offset 7 lines).
can't find file to patch at input line 189
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/fs/aufs/f_op.c b/fs/aufs/f_op.c
|index d6318f08b..56555de 100644
|--- a/fs/aufs/f_op.c
|+++ b/fs/aufs/f_op.c
--------------------------
File to patch:

Posted 7 years ago #
TraceE

offline
Member

Here's the extract up to line 152 where Hunk 2 fails in the original Makefile:

# ---------------------------------------------------------------------------
help: FORCE
@echo ' rpm-pkg - Build both source and binary RPM kernel packages'
@echo ' binrpm-pkg - Build only the binary kernel package'
@echo ' deb-pkg - Build the kernel as an deb package'
@echo ' tar-pkg - Build the kernel as an uncompressed tarball'
@echo ' targz-pkg - Build the kernel as a gzip compressed tarball'
@echo ' tarbz2-pkg - Build the kernel as a bzip2 compressed tarball'
@echo ' tarxz-pkg - Build the kernel as a xz compressed tarball'
@echo ' perf-tar-src-pkg - Build $(perf-tar).tar source tarball'
@echo ' perf-targz-src-pkg - Build $(perf-tar).tar.gz source tarball'
@echo ' perf-tarbz2-src-pkg - Build $(perf-tar).tar.bz2 source tarball'
@echo ' perf-tarxz-src-pkg - Build $(perf-tar).tar.xz source tarball'

And the whole of scripts/package/Makefile.rej:

--- scripts/package/Makefile Mon Nov 22 20:03:49 2010
+++ scripts/package/Makefile Sat Nov 27 09:56:12 2010
@@ -152,4 +159,4 @@
@echo ' perf-tar-src-pkg - Build $(perf-tar).tar source tarball'
@echo ' perf-targz-src-pkg - Build $(perf-tar).tar.gz source tarball'
@echo ' perf-tarbz2-src-pkg - Build $(perf-tar).tar.bz2 source tarball'
-
+ @echo ' tazpkg - Build the kernel as a SliTaz package'

Any ideas?

Posted 7 years ago #
mojo

offline
Key Master

Nvidia-304.134 builds with linux-module-headers.
Linux-source is broken but linux-module-headers will get the job done.

Posted 7 years ago #
TraceE

offline
Member

Nvidia-304.134 builds with linux-module-headers.
Linux-source is broken but linux-module-headers will get the job done.

Ok that seemed to work following the procedure linked to above ...

Except Stage 4 where I tried to replace "get-linux-source" with "get-linux-module-headers" and it couldn't find the file.

So I just ignored it and carried on and the rest went smoothly.

After restarting x .... I used tazusb writefs (gzip) to save a new rootfs.gz

On rebooting I could not start slim because of the nouveau module overiding the nvidia one.

I sorted this by using the "nomodeset" boot option and saving it permanently in extlinux.conf

Does that sound like an acceptable install and solution or is there a better way I could have done it?

Posted 7 years ago #
gdesilva

offline
Member

Perhaps another option may be to simply blacklist nouveau driver.

Posted 7 years ago #
TraceE

offline
Member

Ok I will blacklist nouveau driver.

Does it matter that Step 4 "# get-linux-module-headers" couldn't find the file and so I just skipped it ... or is that command not applicable with "linux-module-headers" ?

Posted 7 years ago #
mojo

offline
Key Master

The command is not applicable,linux-module-headers has no get script.
All files are in the package and installed on your system when the package is installed.
An alternative to nomodeset or blacklisting nouveau when your running nvidia proprietary driver is to remove nouveau.ko.xz from your system by removing linux-drm tazpkg which owns it.

Posted 7 years ago #
sixofeight

offline
Member

blacklist nouveau...
Usually the nvidia installer should have already done this for you.
However
I have a "nvidia-installer-disable-nouveau.conf" in /etc/modprobe.d
with following content:

# generated by nvidia-installer
blacklist nouveau
options nouveau modeset=0

Posted 7 years ago #

RSS feed for this topic

12 Next »

Reply »

You must log in to post.