Go Back   nV News Forums > Linux Support Forums > NVIDIA Linux

Newegg Daily Deals

Reply
 
Thread Tools
Old 01-03-03, 11:31 AM   #1
nedavis
Registered User
 
Join Date: Jan 2003
Posts: 6
Default License issues with nVidia driver 4191, Debian linux, kernel 2.4.20

I'm trying to build the latest nVidia drivers, 4191, after having upgraded
my kernel to 2.4.20. I'm receiving several unresolved symbol errors and
a message about the GPL License compatibility.

I'd really like to use the new drivers with my nifty cool GeForce 4 card.

How do I/you resolve this license issue, or are you willing to provide .deb installation packages that would get around this? (Without downgrading the kernel, please.)

Thanks!

Nancy Davis
nedavis is offline   Reply With Quote
Old 01-03-03, 02:05 PM   #2
cdrradar
Registered User
 
Join Date: Dec 2002
Posts: 17
Default

Insofar as the license issue goes, there's no way around that - for some reason, nvidia doesn't want to release the source for the driver, they want to keep it a closed binary. IMHO, this is a major mistake on their part - among other reasons, if problems develop with the driver, it doesn't get resolved in a timely fashion.

I downloaded and used the tarballs to install the drivers. I don't know the exact files you get, but you need the kernel driver and the GLX driver. Make sure you get the same version...! Unpack them with 'tar -xzf NVIDIA_kernel.tar.gz' and 'tar -xzf NVIDIA_glx.tar.gz'. cd into the directories made, and type 'make install' for each. That's how it's done in a nutshell. The README file contains each step in much greater detail.
cdrradar is offline   Reply With Quote
Old 01-03-03, 02:13 PM   #3
nedavis
Registered User
 
Join Date: Jan 2003
Posts: 6
Default

Yes, I followed the installation instructions for both the
NVIDIA_kernel-1.0-4191.tar.gz and NVIDIA_GLX-1.0-4191.tar.gz.

I used the SYSINCLUDE=/usr/src/kernel-headers-2.4.20/include
as option on the make for NVIDIA_kernel. Then built NVIDIA_GLX.
This was done while running the 2.4.20 kernel.

Still receive many unresolved symbols and the license error.
The module does not load.

Thanks for any assistance you can offer.
nedavis is offline   Reply With Quote
Old 01-03-03, 02:28 PM   #4
Andy Mecham
l33t master
 
Join Date: Jul 2002
Location: Santa Clara, CA
Posts: 1,163
Default

From the README:

Q: I've rebuilt the NVIDIA_kernel module, but when I try to insert
it, I get a message telling me I have unresolved symbols.

A. Unresolved symbols are most often caused by a mismatch between your
kernel sources and your running kernel. They must match for the
NVIDIA_kernel module to build correctly. Please make sure your kernel
sources are installed and configured to match your running kernel.

--andy
__________________
Andy Mecham
NVIDIA Corporation
Andy Mecham is offline   Reply With Quote
Old 01-03-03, 02:37 PM   #5
nedavis
Registered User
 
Join Date: Jan 2003
Posts: 6
Default

Yes, I was running the 2.4.20 kernel. I pointed the
SYSINCLUDE to the 2.4.20 header include files. The 2.4.20
kernel source was present and accounted for. During build,
I receive errors that the symbols are unresolved and
that there was a licensing incompatibility problem.

The module does not load - it errors out with unresolved
symbols.

Thanks again for all your assistance.
nedavis is offline   Reply With Quote
Old 01-03-03, 02:41 PM   #6
Andy Mecham
l33t master
 
Join Date: Jul 2002
Location: Santa Clara, CA
Posts: 1,163
Default

You have unresolved symbols because your running kernel does not match the configuration of your kernel sources (ie: if you compiled a kernel from your current kernel sources, it wouldn't be the same as the kernel you're now running). In order to compile the driver, your kernel source tree *must* be configured to match your running kernel. Please make sure that you haven't changed the configuration of your kernel sources, and that they match your running kernel.

The license message appears because the NVIDIA kernel module is not opensource. It is not causing your problem.

--andy
__________________
Andy Mecham
NVIDIA Corporation
Andy Mecham is offline   Reply With Quote
Old 01-03-03, 02:49 PM   #7
nedavis
Registered User
 
Join Date: Jan 2003
Posts: 6
Default

I built the 2.4.20 kernel. I rebooted into that kernel.
I attempted to build the drivers. It failed. Below is the
entire error message. Your assistance is appreciated.

Nancy



aiza:/usr/src/NVIDIA_kernel-1.0-4191# uname -a
Linux aiza 2.4.20 #2 SMP Fri Jan 3 09:36:27 MST 2003 i686 AMD Athlon(tm) MP 2100+ AuthenticAMD GNU/Linux
aiza:/usr/src/NVIDIA_kernel-1.0-4191# make 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
1248411__ 92824__ 32940 1374175__14f7df nvidia.o
depmod: *** Unresolved symbols in /lib/modules/2.4.20/kernel/drivers/video/nvidia.o
/lib/modules/2.4.20/kernel/drivers/video/nvidia.o: unresolved symbol create_proc_entry_Rsmp_83f569d5
/lib/modules/2.4.20/kernel/drivers/video/nvidia.o: unresolved symbol proc_root_Rsmp_b4c94c07
/lib/modules/2.4.20/kernel/drivers/video/nvidia.o: unresolved symbol change_page_attr_Rsmp_9d42b338
/lib/modules/2.4.20/kernel/drivers/video/nvidia.o: unresolved symbol irq_stat_Rsmp_40a7690d
/lib/modules/2.4.20/kernel/drivers/video/nvidia.o: unresolved symbol __pollwait_Rsmp_ad8b7db3
/lib/modules/2.4.20/kernel/drivers/video/nvidia.o: unresolved symbol init_mm_Rsmp_543867be
/lib/modules/2.4.20/kernel/drivers/video/nvidia.o: unresolved symbol remove_proc_entry_Rsmp_0e547d5f
/lib/modules/2.4.20/kernel/drivers/video/nvidia.o: unresolved symbol proc_root_driver_Rsmp_e558a624
/lib/modules/2.4.20/kernel/drivers/video/nvidia.o: unresolved symbol mem_map_Rsmp_3578ee61
/lib/modules/2.4.20/kernel/drivers/video/nvidia.o: unresolved symbol register_chrdev_Rsmp_6e1b6381
/lib/modules/2.4.20/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.
/lib/modules/2.4.20/kernel/drivers/video/nvidia.o: insmod /lib/modules/2.4.20/kernel/drivers/video/nvidia.o failed
/lib/modules/2.4.20/kernel/drivers/video/nvidia.o: insmod nvidia failed
make: *** [package-install] Error 255
nedavis is offline   Reply With Quote
Old 01-03-03, 02:51 PM   #8
Andy Mecham
l33t master
 
Join Date: Jul 2002
Location: Santa Clara, CA
Posts: 1,163
Default

Try without the SYSINCLUDE. Your 2.4.20 kernel sources should be in /usr/src/linux, or /usr/src/linux should be a symlink to them.

--andy
__________________
Andy Mecham
NVIDIA Corporation
Andy Mecham is offline   Reply With Quote

Old 01-03-03, 03:06 PM   #9
nedavis
Registered User
 
Join Date: Jan 2003
Posts: 6
Default

Thanks! The module is now loading (albeit with tainting
errors), but at least it loads.

What I did:

cd /usr/src
ln -s kernel-headers-2.4.20 linux
cd NVIDIA_kernel-1.0-4191
make clean
make
cd ../NVIDIA_GLX-1.0-4191
make
vi /etc/modules # added line with just nvidia
reboot

All is happy in GeForce-land again. Strange - I thought
the SYSINCLUDE should have taken care of the includes....
It is possible that the "make clean" was the *real*
solution to my problem. (sheepish grin) Need more coffee.

Thanks again!

Nancy
nedavis is offline   Reply With Quote
Old 01-05-03, 12:08 AM   #10
Wonder
Registered User
 
Join Date: Dec 2002
Location: SoCal
Posts: 5
Default

Tainted is nothing. I'm told it means that the official Linux Kernel people won't even look at fixing problems _you_ may have with 2.4.20 kernel, since (now that you've joined this Nvidia binary to it) they have no idea what source code went into making your kernel. The "tainted" flag will show up in any core dump you would want to send the kernel folks, who, when they see it, will refuse to consider your kernel problem further.

ND from GCS?

pq
Wonder is offline   Reply With Quote
Old 01-05-03, 02:34 PM   #11
Wrawrat
Registered User
 
Wrawrat's Avatar
 
Join Date: Jan 2003
Location: Quebec City, Canada
Posts: 13
Send a message via ICQ to Wrawrat
Default Tainted kernel issue

I guess the drivers are closed source because of TV-out restrictions (Macrovision) and proprietary technologies that are still waiting for a patent. Maybe that's also to keep the control of modifications.
Wrawrat is offline   Reply With Quote
Old 01-06-03, 05:46 AM   #12
FunkyRes
Registered User
 
Join Date: Jan 2003
Posts: 21
Default Re: Tainted kernel issue

Quote:
Originally posted by Wrawrat
I guess the drivers are closed source because of TV-out restrictions (Macrovision) and proprietary technologies that are still waiting for a patent. Maybe that's also to keep the control of modifications.
Yes.
Well- that may not be why the source is close, but its a good excuse.

Of course these laws don't affect the criminal who is already breaking other laws - they only affect the honest people.

but *sigh* - with the legal budget of big industry, what can we do?
FunkyRes is offline   Reply With Quote
Reply


Thread Tools

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 On
HTML code is Off
Forum Jump


Similar Threads
Thread Thread Starter Forum Replies Last Post
UEFI+Nvidia - NVRM: Your system is not currently configured to drive a VGA console... interzoneuk NVIDIA Linux 0 06-26-12 04:51 AM
xorg locks-up with newest nvidia drivers w/ vdpau. theroot NVIDIA Linux 1 06-24-12 11:04 AM
Need Help Installing NVIDIA Tesla M2070Q in Linux RHEL5 Ferianto85 NVIDIA Linux 0 05-18-12 08:35 PM
Lucid rt kernel can't load latest nvidia driver module, but generic does. marcod NVIDIA Linux 0 05-02-12 06:23 AM
Getting the proprietary nvidia driver to run with Debian 3.0 r0 (woody) Katchina404 NVIDIA Linux 9 01-12-03 08:49 AM

All times are GMT -5. The time now is 06:13 PM.


Powered by vBulletin® Version 3.7.1
Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Copyright 1998 - 2014, nV News.