LinuxQuestions.org
Visit Jeremy's Blog.
Home Forums Tutorials Articles Register
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Hardware
User Name
Password
Linux - Hardware This forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?

Notices


Reply
  Search this Thread
Old 02-23-2003, 06:42 PM   #1
riv
LQ Newbie
 
Registered: Feb 2003
Distribution: debian
Posts: 3

Rep: Reputation: 0
Unhappy prb - nVidia tar - 2.4.20 - unresolved symbols


Hello Everyone - this is my first post here therefore sorry for any errors I may do ;-)

My goal is to install the new nVidia drivers on a debian woody with 2.4.20 kernel

Systems:
a) Winfast K7NCR18D with GeForce 4 Ti 4600
b) Asus A7V-333 ER with leadtek GeForce3 Ti 200

both systems have been installed through the boot floppyes available here: people.debian.org/~blade/ then bf2.4

I have downloaded the tar source files of both kernel and glx, version 4191. I untared them, then run make install in both, as described. The problem is : every manual supposes that this goes just well, and continues with config of the XF86config-4 file. Nothing is right!

first I got an error with modversions.h. I fixed that one by adding:

deb http://www.fs.tum.de/~bunk/debian woody/bunk-1 main contrib non-free
same line with deb-src.

then apt-get update
then apt-get install kernel-headers-2.4.20
then apt-get install kernel-source-2.4.20

then i returned into the nvidia kernel directory, and run
make install SYSINCLUDE=/usr/src/linux-2.4.20/include

this helped a lot, since i now get another error message :-/

now its:
riv:~/NVIDIA_kernel-1.0-4191# make install SYSINCLUDE=/usr/src/kernel-headers-2.4.20/include/
ld -r -o nvidia.o nv-linux.o nv-kernel.o
size nvidia.o
text data bss dec hex filename
1248439 92824 32940 1374203 14f7fb nvidia.o
depmod: *** Unresolved symbols in /lib/modules/2.4.20-bf2.4/kernel/drivers/video/nvidia.o
make: *** [package-install] Error 1
riv:~/NVIDIA_kernel-1.0-4191#

this error seems widespread, but the solutions I tried didn't work.

My assumption was that the kernel sources I dled were different from the actual kernel installed, so I installed a fresh 2.4.20 kernel on system (a).

I rerunned the make command.

and...

still got the same error.

<...banging my head slowly on the table...>

At this point, I WELLCOME any help - since I am totally lost!
later, i'll have also problems with the nforce drivers that state
cc1 Invalid option '-falign-functions=4'

please turn on user_is_dumb mode for replys ;-)

thanx!
 
Old 02-24-2003, 06:29 PM   #2
disgrace
LQ Newbie
 
Registered: Oct 2002
Posts: 4

Rep: Reputation: 0
I too am having a problem. I downloaded the latest nvidia source. When I run "make" in the nvidia driver source directory, I get the following:

ld -r -o nvidia.o nv-linux.o nv-kernel.o
size nvidia.o
text data bss dec hex filename
1248126 92760 32940 1373826 14f682 nvidia.o
depmod: *** Unresolved symbols in /lib/modules/2.4.18-24.8.0/kernel/drivers/video/nvidia.o
/lib/modules/2.4.18-24.8.0/kernel/drivers/video/nvidia.o: unresolved symbol mem_map_Rfa588ddb
/lib/modules/2.4.18-24.8.0/kernel/drivers/video/nvidia.o: unresolved symbol proc_root_driver_Re083a0d7
/lib/modules/2.4.18-24.8.0/kernel/drivers/video/nvidia.o: unresolved symbol init_mm_R53803726
/lib/modules/2.4.18-24.8.0/kernel/drivers/video/nvidia.o: unresolved symbol register_chrdev_R7f978a1c
/lib/modules/2.4.18-24.8.0/kernel/drivers/video/nvidia.o: unresolved symbol remove_proc_entry_Rffeac3fc
/lib/modules/2.4.18-24.8.0/kernel/drivers/video/nvidia.o: unresolved symbol irq_stat_R04f4c6f7
/lib/modules/2.4.18-24.8.0/kernel/drivers/video/nvidia.o: unresolved symbol create_proc_entry_R3784f9a1
/lib/modules/2.4.18-24.8.0/kernel/drivers/video/nvidia.o: unresolved symbol proc_root_Ra289cfd3
/lib/modules/2.4.18-24.8.0/kernel/drivers/video/nvidia.o: unresolved symbol __pollwait_Raa34e74a
/lib/modules/2.4.18-24.8.0/kernel/drivers/video/nvidia.o:
Hint: You are trying to load a module without a GPL compatible license
and it has unresolved symbols. Contact the module supplier for
assistance, only they can help you.

I did the searching, and it seems there is a kernel source compatibility issue, but it is not at all clear how to resolve. I have RH8, 2.4.18-24.8.0 kernel and the source (all retrieved using up2date).
 
Old 02-25-2003, 02:25 AM   #3
riv
LQ Newbie
 
Registered: Feb 2003
Distribution: debian
Posts: 3

Original Poster
Rep: Reputation: 0
Cool

Well, I found the solution that worked for me:

since I installed from 2.4.20 - boot floppies -

I had to download the exact kernel headers: 2.4.20-bf2.4-2.4.20

the make instal SYSINCLUDE=/usr/src/kernel-headers(...)/include et voila!
 
Old 02-25-2003, 11:12 AM   #4
xcon
Member
 
Registered: Jan 2002
Location: Ohio
Distribution: Slackware 9.1 (and some 9.0)
Posts: 181

Rep: Reputation: 30
i had a similar error... the solution was not only to have the correct kernel and headers all matching as well as the currently running kernel, but then finally a "make clean" on the driver removed an incorrect object leftover from incorrect headers.

just make sure you recompile the driver from the ground up every time

Last edited by xcon; 02-25-2003 at 11:13 AM.
 
Old 02-25-2003, 01:13 PM   #5
disgrace
LQ Newbie
 
Registered: Oct 2002
Posts: 4

Rep: Reputation: 0
Although I am not at home, I can almost bet that is what it is. I probably have a lot of leftover object files from my hours of trying to build with the wrong source/kernel files.


As to the previous post, I did use SYSINCLUDE= to do my builds. Thanks for the help both of you, hopefully when I get in tonight I will be able to resolve the problem quickly.
 
Old 02-25-2003, 05:13 PM   #6
riv
LQ Newbie
 
Registered: Feb 2003
Distribution: debian
Posts: 3

Original Poster
Rep: Reputation: 0
Quote:
Originally posted by xcon
i had a similar error... the solution was not only to have the correct kernel and headers all matching as well as the currently running kernel, but then finally a "make clean" on the driver removed an incorrect object leftover from incorrect headers.

just make sure you recompile the driver from the ground up every time
Well yes, lets just say I took the habit to completely remove the folder and re-decompress the gzipped tarball - makefiles aren't allways perfect :-)

Ya-hoo, just got to work an matrox G400 mill with hardware acceleration... im getting better :-รพ
 
Old 02-25-2003, 09:38 PM   #7
xcon
Member
 
Registered: Jan 2002
Location: Ohio
Distribution: Slackware 9.1 (and some 9.0)
Posts: 181

Rep: Reputation: 30
of course... way to be sure
 
  


Reply



Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
***Unresolved Symbols*** red8user Linux - Networking 2 09-12-2003 06:34 AM
***Unresolved Symbols*** red8user Linux - Software 0 09-11-2003 05:37 PM
The Nvidia 4191 Unresolved Symbols-thingie. Udo von Dunke Linux - Newbie 4 02-03-2003 04:56 PM
nvidia driver....unresolved symbols glumx Linux - Hardware 11 01-21-2003 01:28 PM
Nvidia + kernel 2.4.20 = unresolved symbols? Dipp Linux - General 3 12-12-2002 09:55 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Hardware

All times are GMT -5. The time now is 11:15 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration