SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I'm trying to install Slack 10.1 on my laptop (Compaq R3210CA). I've upgraded the kernel from the default 2.4.29 to 2.6.11.9 .
I'm trying to do the same extract-patch-install procedure outlined in mziab's post. However, I can't seem to exract the files from the .run file. I've tried using differen .run files, all with the same problem. The extractor quits after saying something about UID 1000, GID 1000.
Sorry I can't have a more detailed description, but the only way I can access the net now is by going into Windows.
Any help will be much appreciated.
Rameses
Question, did you actually get it installed first, then do the Kernel update? Did you go through the instructions here for your kernel compile too?? It should work. I put Slackware on an E-Machiine M2105 and it was a bear at most, and had to use the May, 2 2005 RC I downloaded to even get it to work. I recently updated to Linux 2.4.30 off the Slackware site so I am pretty much up to date with this. now, the display driver
sh NVIDIA*.run and yes it works fine, that is how I do it. Then let it go and you will be set. As for extracting it, did you get the read me off the nvidia site, it has some nice tips on how to make it work.
from the READ ME I have
The .run file accepts many commandline options. Here are a few of the
more common options:
--info
Print embedded info about the .run file and exit.
--check
Check integrity of the archive and exit.
--extract-only
Extract the contents of ./NVIDIA-Linux-x86-1.0-7174.run,
but do not run 'nvidia-installer'.
--help
Print usage information for the common commandline options
and exit.
--advanced-options
Print usage information for the common commandline options as
well as the advanced options, and then exit.
Installation will also install the utility `nvidia-installer`, which may
be later used to uninstall drivers, auto-download updated drivers, etc.
Last edited by BenneJezzerette; 05-23-2005 at 03:52 PM.
Usually when you get those errors, it still extracts fine. It just couldn't change the permissions for the files. Sounds pretty basic, but, did you check to see if you have an NVIDIA-BlahBlahBlah folder in the same directory?
Also, which drivers are these? Where did you get them from. What version are you trying to extract? Somebody assigned -g 1000 -o 1000 to the drivers your trying to use, which is pretty bogus. Thats probably why your getting that error because you don't have a Group "1000" or Owner "1000"... They should be root:root....
If they did extract and the perms weren't changed like I suspect, just do a:
chown -R root.root NVIDIA-NameOfFolder
Then patch and make a new .run file if you wish...
Originally posted by jong357 Usually when you get those errors, it still extracts fine. It just couldn't change the permissions for the files. Sounds pretty basic, but, did you check to see if you have an NVIDIA-BlahBlahBlah folder in the same directory?
Also, which drivers are these? Where did you get them from. What version are you trying to extract? Somebody assigned -g 1000 -o 1000 to the drivers your trying to use, which is pretty bogus. Thats probably why your getting that error because you don't have a Group "1000" or Owner "1000"... They should be root:root....
If they did extract and the perms weren't changed like I suspect, just do a:
chown -R root.root NVIDIA-NameOfFolder
Then patch and make a new .run file if you wish...
you can also not even make a new run file, just type make install, from the read me
Benne: I downloaded the 2.6.11.9 kernel source from kernel.org, and compiled my own kernel after going thru the xconfig. Then I put it into my /boot partition, edited lilo.conf so I can select which kernel I want to boot with at startup.
I managed to install the 7174 drivers using the sh NVIDIA-blah.run command. But 7174 doesn't work. So I was trying to use the 2.6 modifed 4620 and patch it for 2.6.11, as per the instructions somewhere on page 3 of this thread.
jong: I'm using the .run file from your site! Anyways, I checked carefully this time and I found that the files did indeed extract into the folder. Sorry for any confusion.
I'll give the patch and install a try right now. I'll let you know how it goes.
Originally posted by ramdog Benne: I downloaded the 2.6.11.9 kernel source from kernel.org, and compiled my own kernel after going thru the xconfig. Then I put it into my /boot partition, edited lilo.conf so I can select which kernel I want to boot with at startup.
I managed to install the 7174 drivers using the sh NVIDIA-blah.run command. But 7174 doesn't work. So I was trying to use the 2.6 modifed 4620 and patch it for 2.6.11, as per the instructions somewhere on page 3 of this thread.
jong: I'm using the .run file from your site! Anyways, I checked carefully this time and I found that the files did indeed extract into the folder. Sorry for any confusion.
I'll give the patch and install a try right now. I'll let you know how it goes.
Again, sorry for any confusion,
R
god Luck, I am going to attemt the Linux 2.6.11.10 and see what mess I can make of my system.
Well, I've tried to install the drivers. However, I've run up against the same wall that I did when I tried to install 7174; the installer fails to make the modules that it must. To fix that for the 7174 install I used:
Code:
sh NVIDIA-blah-blah.run -k 2.6.11.9
which worked then. But when I tried that here, it failed on me. Here's what nvidia-installer.log had to say about the whole thing:
Code:
nvidia-installer log file '/var/log/nvidia-installer.log'
creation time: Mon May 23 18:34:05 2005
option status:
license pre-accepted : false
update : false
force update : false
expert : false
uninstall : false
driver info : false
no precompiled interface: false
no ncurses color : false
query latest driver ver : false
OpenGL header files : false
no questions : false
silent : false
XFree86 install prefix : /usr/X11R6
OpenGL install prefix : /usr
Installer install prefix: /usr
kernel source path : /usr/src/linux-2.6.11.9
kernel install path : false
proc mount point : /proc
ui : (not specified)
tmpdir : /tmp
ftp site : ftp://download.nvidia.com
Using: nvidia-installer ncurses user interface
-> License accepted.
-> No precompiled kernel interface was found to match your kernel; would you li
ke the installer to attempt to download a kernel interface for your kernel f
rom the NVIDIA ftp site (ftp://download.nvidia.com)? (Answer: No)
-> No precompiled kernel interface was found to match your kernel; this means
that the installer will need to compile a new kernel interface.
-> Using the kernel source path '/usr/src/linux-2.6.11.9' as specified by the
'--kernel-source-path' commandline option.
-> Kernel source path: '/usr/src/linux-2.6.11.9'
-> Performing cc_version_check with CC="cc".
-> Cleaning kernel module build directory.
executing: 'cd ./usr/src/nv; make clean'...
make: *** No rule to make target `clean'. Stop.
-> Building kernel module:
executing: 'cd ./usr/src/nv; make SYSSRC=/usr/src/linux-2.6.11.9 module'...
make: *** No rule to make target `module'. Stop.
-> Error.
ERROR: Unable to build the NVIDIA 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.
BTW, I compiled my own kernel from the source at kernel.org, and copied vmlinuz from the compile to vmlinuz.new in /boot. I've modifed lilo.conf so that it can boot both kernels, but leaving the original 2.4.29 kernel as untouched as possible. could that be causing the problem?
Thanks again for all the help guys, hopefully this thing will get fixed.
is 2.6.xx really worth all this trouble? the only thing thats caught my eye (and that too from reading this thread) is the ide-cdwriter support... matter of fact, I don't remember scsi-cdwriting support being all that hard to get working. I'll give this thing another try tomorrow, and if that doesn't work I'll go back to 2.4.xx...
Mind you, even then I'll have to get back here, since I've noticed another problem with the drivers on that. Well lets wait and see if one of the older ones (6111, perhaps?) works.
Originally posted by ramdog Well, I've tried to install the drivers. However, I've run up against the same wall that I did when I tried to install 7174; the installer fails to make the modules that it must. To fix that for the 7174 install I used:
<Cut No Paste>
Ok so you did one big thing wrong.
Quote:
rom the NVIDIA ftp site (ftp://download.nvidia.com)? (Answer: No)
-> No precompiled kernel interface was found to match your kernel; this means
that the installer will need to compile a new kernel interface.
<Cut No Paste>
Here where you said, no, should have been yes, so that it could do what it's supposed to and then you would have the nVidia Drivers installed.
Quote:
BTW, I compiled my own kernel from the source at kernel.org, and copied vmlinuz from the compile to vmlinuz.new in /boot. I've modifed lilo.conf so that it can boot both kernels, but leaving the original 2.4.29 kernel as untouched as possible. could that be causing the problem?
Thanks again for all the help guys, hopefully this thing will get fixed.
R
Not a problem, it's good, just in case you made a mistake.
Originally posted by ramdog is 2.6.xx really worth all this trouble? the only thing thats caught my eye (and that too from reading this thread) is the ide-cdwriter support... matter of fact, I don't remember scsi-cdwriting support being all that hard to get working. I'll give this thing another try tomorrow, and if that doesn't work I'll go back to 2.4.xx...
Mind you, even then I'll have to get back here, since I've noticed another problem with the drivers on that. Well lets wait and see if one of the older ones (6111, perhaps?) works.
Thanks,
R
I am using Linux 2.4.30 from the Slackware Updates, I personally had a lot of problems, and appar4ently others are still having problems.
Benne... I'm having a hard time understanding you and I think this thread is degenerating rapidly because of it.. No offense....
There's nothing wrong with:
Code:
sh NVIDIA-Linux-x86-1.0-4620-pkg0 -k $(uname -r)
I've had to do it myself on newer nvidia drivers, otherwise it states the the kernel source is misconfigured or some such nonsense... That's what he is talking about.. Your just specifying the running kernel, which it tries to do anyway on it's own... Nothing wrong with helping it out...
Also, NEVER in a million years will it ever find pre-compiled modules on the nvidia site. It doesn't matter whether you say yes or no to that question. You still need to compile your own... I also purposefully remove the precompiled directory in the driver package to save space because those will NEVER match your running kernel anyway.. Not unless your running Redhat 7.3....
Let's try to keep the posts down to a minimum, otherwise no one is going to want to read it, much less try to help by posting...
ramdog.... I honestly think you have a two fold problem going on... Make sure you visually inspect usr/sr/nv for a Makefile symlink. I could guess and say that because of your initial extraction problems with the permissions, that maybe it also wasn't able to create the "Makefile" symlink which points to "Makefile.kbuild"... Your error indicated this. Atleast, that's the first thing I would have checked... It said "no rule to make target".. You get that when it can't find a 'Makefile'....
You also might have a problem with your running kernel directory in /usr/src.... Who knows... I patched and made a 2.6.11 driver (.run file) if your interested in trying it out. Don't think I'll upload it unless your interested in trying it...
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.