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.
Also, NEVER in a million years will it ever find pre-compiled modules on the nvidia site.
The thing on the sh NVIDIA- xxx xxx .run is that it looks on the nvidia site and finds the links to the running kernel. then it compiles the Module to match the running kernel. If you say no, then it is not going to work correctly. I have experimented, and always say yes, and it will work without issue.
Thats not true... It reads your running kernel and then looks in the coresponding /lib/modules/$(uname -r)/build directory to define the kernel source...
The only thing it uses that question for is to look on Nvidia ftp server for a precompiled nvidia module so you don't have to build one yourself...
Originally posted by jong357 Thats not true... It reads your running kernel and then looks in the coresponding /lib/modules/$(uname -r)/build directory to define the kernel source...
The only thing it uses that question for is to look on Nvidia ftp server for a precompiled nvidia module so you don't have to build one yourself...
then why when I did it, it would not work, and when I said Yes, it did, go figure.
Originally posted by ramdog jong: if you could upload those drivers, I'd be most grateful. and no, I did not find any 'Make' files in the directory I extracted to.
go here _>> nVidia 7174 Drivers Page and then down load them. use the commands if you want to extract them, the ones I gave in this thread. Or use the sh NVIDIA*.run and just install them. Be sure to say ok, and yes where promted, or it will crash.
Distribution: Slackware64-current on Thinkpad Carbon X1
Posts: 264
Rep:
Quote:
then why when I did it, it would not work, and when I said Yes, it did, go figure.
It definitely had nothing to do with you answering 'yes'... jong is right it makes no difference unless you are running an old distro...
btw.. This thread is a bit hard to follow.. Jong: did you get the 7174 driver working? or are you still using the old ones on your site?? I still have the old ones running perfectly...
It is hard to follow. That's why I'm abandoning this thread if he keeps posting. Either he's doing it on purpose to annoy me or he's a few fries short of a happy meal.... Either way, I think I'm done here. If someone is really having a problem with these old drivers and patches, you can email me I suppose... Make sure the subject is NVIDIA related or it will more than likely get deleted. Only black screen related upon X startup too preferably dealing with laptops as well.... I'm not going answer any noobish or general questions...
I'm still using 4620 on my laptop. Still expiermenting with the newer ones tho... If I make any headway, I'll let you know about it.. I also fully patched the 4620 driver for 2.6.11 (vmalloc included) and uploaded it to my site if it helps people like ramdog.. The link is back 2 pages where this thread stopped being helpfull....
Also, I should point out just incase, NEVER work from a FAT partition. I'm still trying to understand why you got all those perm problems and no Makefile symlink... If you tried to extract the driver on a FAT32 partition, there is your problem. If you use linux, then use linux. Work from your / partition and not a shared partition for windows that you may have lying around..
Originally posted by jong357 It is hard to follow. That's why I'm abandoning this thread if he keeps posting. Either he's doing it on purpose to annoy me or he's a few fries short of a happy meal.... Either way, I think I'm done here. If someone is really having a problem with these old drivers and patches, you can email me I suppose... Make sure the subject is NVIDIA related or it will more than likely get deleted. Only black screen related upon X startup too preferably dealing with laptops as well.... I'm not going answer any noobish or general questions...
I'm still using 4620 on my laptop. Still expiermenting with the newer ones tho... If I make any headway, I'll let you know about it.. I also fully patched the 4620 driver for 2.6.11 (vmalloc included) and uploaded it to my site if it helps people like ramdog.. The link is back 2 pages where this thread stopped being helpfull....
Also, I should point out just incase, NEVER work from a FAT partition. I'm still trying to understand why you got all those perm problems and no Makefile symlink... If you tried to extract the driver on a FAT32 partition, there is your problem. If you use linux, then use linux. Work from your / partition and not a shared partition for windows that you may have lying around..
I will agree with you here. I have the latest and working fine, but not a laptop. I did make a Laptop work, but it has not got nVidia Chipsets on it, so no way to get that part of it in. I know that some just do things cause they have no better reason. If it works, break it, then someone can fix it for me, so much for attention getters. I have the 7147 working fine with the Linux 2.4.30 so it has to be something thta he is not paying attention to.
Working with FAT on Linux??? Huh!!!??? I had that for a little while, when I first started, but finally got away from it, so now I am a fully Linux Girl and completely Fat free lol.
Maybe he should just go back to that "If you Buy this computer, you HAVE to have this OS on it, or you can't buy this computer" oh the days of creative licensing.
Well, yea you goof... Thats what this entire thread has been about. Newer nvidia drivers not working on an integrated Geforce laptop mobo... It's usually a good idea to read the entire thread and understand what's going on before you post....
Originally posted by jong357 Well, yea you goof... Thats what this entire thread has been about. Newer nvidia drivers not working on an integrated Geforce laptop mobo... It's usually a good idea to read the entire thread and understand what's going on before you post....
Lol, well If my memory is not failing, Ithink Igot here and was posting from about the 5th or 6th message in the thread. Maybe.
whoops... should have mentioned I was dual-booting with WinXP. Since I had to dl all the drivers using WinXP, I was working with them off the shared partition (FAT32).
Sorry for any hairs that might have been pulled out.
Yea, I figured as much... Don't work from a FAT32 partition. It doesn't support symlinks and it's hard to get proper permissions. I think if it's mounted umask=0 from fstab, you might be able to work on it, but it still doesn't handle symlinks.. Just make a ~/work directory and use that...
so much for hoping it was as simple as that... heres the new log:
Code:
nvidia-installer log file '/var/log/nvidia-installer.log'
creation time: Wed May 25 20:53:49 2005
option status:
license pre-accepted : false
update : false
force update : false
expert : false
uninstall : false
driver info : false
no precompiled interface: true
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 : (not specified)
kernel install path : (not specified)
proc mount point : /proc
ui : (not specified)
tmpdir : /tmp
ftp site : ftp://download.nvidia.com
Using: nvidia-installer ncurses user interface
-> License accepted.
-> Not probing for precompiled kernel interfaces.
-> Kernel source path: '/usr/src/linux'
-> Cleaning kernel module build directory.
executing: 'cd ./usr/src/nv; make clean'...
cat: /lib/modules/2.6.11.9/build/Makefile: No such file or directory
cat: /lib/modules/2.6.11.9/build/Makefile: No such file or directory
cat: /lib/modules/2.6.11.9/build/Makefile: No such file or directory
-> Building kernel module:
executing: 'cd ./usr/src/nv; make SYSSRC=/usr/src/linux module'...
make[1]: Entering directory `/usr/src/linux-2.4.29'
make -C /tmp/selfgz1768/NVIDIA-Linux-x86-1.0-4620-pkg0/usr/src/nv CFLAGS="-
D__KERNEL__ -I/usr/src/linux-2.4.29/include -Wall -Wstrict-prototypes -Wno-t
rigraphs -O2 -fno-strict-aliasing -fno-common -fomit-frame-pointer -pipe -mp
referred-stack-boundary=2 -march=i486 -DMODULE" MAKING_MODULES=1 modules
make[2]: Entering directory `/tmp/selfgz1768/NVIDIA-Linux-x86-1.0-4620-pkg0/
usr/src/nv'
echo \#define NV_COMPILER \"`cc -v 2>&1 | tail -n 1`\" > nv_compiler.h
cc -D__KERNEL__ -I/usr/src/linux-2.4.29/include -Wall -Wstrict-prototypes -W
no-trigraphs -O2 -fno-strict-aliasing -fno-common -fomit-frame-pointer -pipe
-mpreferred-stack-boundary=2 -march=i486 -DMODULE -I. -Wno-cast-qual -Wno-s
trict-prototypes -D__KERNEL__ -DMODULE -D_LOOSE_KERNEL_NAMES -DNTRM -D_GNU_S
OURCE -D_LOOSE_KERNEL_NAMES -D__KERNEL__ -DMODULE -DNV_MAJOR_VERSION=1 -DNV
_MINOR_VERSION=0 -DNV_PATCHLEVEL=4620 -DNV_UNIX -DNV_LINUX -DNV_INT64_O
K -DNVCPU_X86 -DREMAP_PAGE_RANGE_4 -nostdinc -iwith
prefix include -DKBUILD_BASENAME=nv -c -o nv.o nv.c
In file included from nv-linux.h:119,
from nv.c:14:
/usr/src/linux-2.4.29/include/linux/agpgart.h:128: error: parse error before
"agp_version"
/usr/src/linux-2.4.29/include/linux/agpgart.h:128: warning: no semicolon at
end of struct or union
/usr/src/linux-2.4.29/include/linux/agpgart.h:136: error: parse error before
'}' token
/usr/src/linux-2.4.29/include/linux/agpgart.h:136: warning: type defaults to
`int' in declaration of `agp_info'
/usr/src/linux-2.4.29/include/linux/agpgart.h:136: warning: data definition
has no type or storage class
/usr/src/linux-2.4.29/include/linux/agpgart.h:196: error: parse error before
"agp_memory"
/usr/src/linux-2.4.29/include/linux/agpgart.h:196: warning: no semicolon at
end of struct or union
/usr/src/linux-2.4.29/include/linux/agpgart.h:198: error: parse error before
'}' token
/usr/src/linux-2.4.29/include/linux/agpgart.h:198: warning: type defaults to
`int' in declaration of `agp_controller'
/usr/src/linux-2.4.29/include/linux/agpgart.h:198: warning: data definition
has no type or storage class
/usr/src/linux-2.4.29/include/linux/agpgart.h:215: error: parse error before
"agp_controller"
/usr/src/linux-2.4.29/include/linux/agpgart.h:215: warning: no semicolon at
end of struct or union
/usr/src/linux-2.4.29/include/linux/agpgart.h:216: warning: type defaults to
`int' in declaration of `controllers'
/usr/src/linux-2.4.29/include/linux/agpgart.h:216: warning: data definition
has no type or storage class
/usr/src/linux-2.4.29/include/linux/agpgart.h:220: error: parse error before
'}' token
nv.c: In function `nvos_probe_devices':
nv.c:242: warning: implicit declaration of function `pci_get_class'
nv.c:242: warning: assignment makes pointer from integer without a cast
nv.c:296: warning: assignment makes pointer from integer without a cast
nv.c: In function `nvos_malloc_pages':
nv.c:385: warning: use of cast expressions as lvalues is deprecated
nv.c: In function `nvos_create_alloc':
nv.c:458: warning: use of cast expressions as lvalues is deprecated
nv.c:468: warning: use of cast expressions as lvalues is deprecated
nv.c: In function `nvos_find_agp_by_class':
nv.c:539: warning: assignment makes pointer from integer without a cast
nv.c:550: warning: assignment makes pointer from integer without a cast
nv.c: In function `nv_alloc_file_private':
nv.c:1109: warning: use of cast expressions as lvalues is deprecated
nv.c:1120: warning: use of cast expressions as lvalues is deprecated
nv.c: In function `nv_kern_open':
nv.c:1180: warning: use of cast expressions as lvalues is deprecated
nv.c: In function `nv_kern_ctl_open':
nv.c:1827: warning: use of cast expressions as lvalues is deprecated
make[2]: *** [nv.o] Error 1
make[2]: Leaving directory `/tmp/selfgz1768/NVIDIA-Linux-x86-1.0-4620-pkg0/u
sr/src/nv'
make[1]: *** [_mod_/tmp/selfgz1768/NVIDIA-Linux-x86-1.0-4620-pkg0/usr/src/nv
] Error 2
make[1]: Leaving directory `/usr/src/linux-2.4.29'
make: *** [module] Error 2
-> 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.
heres the low-down on what I've got. I'm running Slack 10.1, with kernel 2.6.11.9, compiled by myself from the sources on kernel.org. The linux partitions are all ReiserFS, except for swap, of course. The machine is a Compaq Presario R3210CA, with a NV17 chip (that GeForce4 440 Go, or something like that), with an AMD Athalon XP-M 2800+ processor, and a 15" screen.
If you need more details, let me know. I'll also send you the .config file that I saved my kernel compile options in, if it'll be of any help.
jong: thanks for everything, I wouldn't blame you if left this thread.
Nah... I'm jobless right now so I have nothing better to do it would seem.... It might be nice if other people stay out of here for the time being tho... . This sounds like nothing more than a misconfigured kernel tree. No need to confuse the issue...
First off...
1. Check that "/lib/modules/2.6.11.9/build" is a symlink that points to "/usr/src/linux-2.6.11.9"..
Once again, it's saying that it can't find a Makefile. Only this time it's complaining about /usr/src/linux-2.6.11.9/Makefile
I don't know why it would be missing, especially if you compiled your own kernel... If you compiled without one, then thats a really cool trick... You know, Pat has 2.6.11.9 in testing right now... Maybe you should have went with the pre-compiled packages... Might be easier..
Let me know whatcha' got.
Look at this, I completely overlooked it at first...
It can't find a Makefile in /usr/src/linux-2.6.11.9 so it's trying to build from your 2.4 kernel directory... How funny... Thats odd... You have some serious misconfigured stuff on your system right now in the way of kernels. I would start fresh if I were you in regards to the 2.6 kernel. Sounds like you may need to anyway... Just chalk all this up as a good learning expierence...
So, if you have a 'Makefile' in /usr/src/linux-2.6.11.9 then your /lib/modules/2.6.11.9/build symlink must not be there. That or it's pointing to some where else besides /usr/src/linux-2.6.11.9... You should also have another symlink in /lib/modules/2.6.11.9... It's called 'source' and it points to your 2.6 kernel source as well.....
Ah... look
Code:
executing: 'cd ./usr/src/nv; make SYSSRC=/usr/src/linux
It fell back on the old /usr/src/linux symlink to define your kernel directory. Thats still pointing at linux-2.4.29 when it should be pointing at linux-2.6.11.9... Another aspect of an improperly configured kernel directory... If you do have the 'Makefile' in your 2.6 tree, it would have worked there.... People argue that that symlink isn't good for much, but it is used... It should always point to your running kernel tree whenever possible...
sorry I didn't get back to you for so long. I've been swamped.
I think I'll just wipe the linux partitions, and re-install slack. Just to make sure I'm not working with any artifacts from the 2.6.11 kernel. I'll try using the 2.6.10 that comes with the dist.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.