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

Newegg Daily Deals

Thread Tools
Old 07-29-02, 03:38 AM   #1
Posts: n/a
Default Problem after compilation, during insmod


I had just reconfigured this system after having the drivers working on it a week earlier. After downloading the drivers (the tar.gz packages), and successfully compiling them, the problem I have is that NVdriver does not pass module dependencies on my system currently.

I run Slackware 8.0 kernel 2.4.5 with a STB Velocity 4400 TNT. Here is the error message I am recieving for NVdriver (GLX seems to install fine):

depmod: *** Unresolved symbols in /lib/modules/2.4.5/kernel/drivers/video/NVdriver

/lib/modules/2.4.5/kernel/drivers/video/NVdriver: unresolved symbol __global_cli

/lib/modules/2.4.5/kernel/drivers/video/NVdriver: unresolved tqueue_lock

/lib/modules/2.4.5/kernel/drivers/video/NVdriver: unresolved symbol __global_save_flags

/lib/modules/2.4.5/kernel/drivers/video/NVdriver: unresolved symbol __global_restore_flags
I tried editting the autoconf.h in /usr/include/linux/ to remove SMB support but I still recieved the "tqueue_lock" error.

Funny thing is that the drivers worked fine the first time i installed them months ago.

[edit] forgot to set my MTU settings again >.<; [/edit]

Hopefully there is something I can edit to knock out these module dependency errors.

  Reply With Quote
Old 07-29-02, 03:46 AM   #2
Join Date: Jul 2002
Location: Netherlands, Europe
Posts: 2,105

Most of the time NVdriver complains about unresolved symbols when you used wrong kernel headers. I mean when you use kernel headers which aren't the ones for your kernel version.
Thunderbird is offline   Reply With Quote
Old 07-29-02, 02:22 PM   #3
Posts: n/a

Okay thanks, I'll do some research into that.

I ran make with the SYSINCLUDE option for the directory that contained the include files for the 2.4.5 kernel (/usr/src/linux-2.4.5/include) but I still seem to get these unresolved symbol errors. I did make sure to make menuconfig dep before doing that.

Are there any other files that could be giving NV's makefile the wrong kernel header locations?

[edit 2]
Thank you for the help. Was not aware of that slack issue (just a newb).
  Reply With Quote
Old 07-29-02, 04:11 PM   #4
Andy Mecham
l33t master
Join Date: Jul 2002
Location: Santa Clara, CA
Posts: 1,163

Slackware 8.0 shipped with unconfigured kernel headers, which is why you're seeing the unresolved symbols. You'll probably have to reconfigure your sources and then recompile your kernel to get the two to match.

I hope this helps...

Andy Mecham
NVIDIA Corporation
Andy Mecham is offline   Reply With Quote

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
Post working out problem with 40.xx trying to work problem out, ONLY system specs b5fan NVIDIA Windows Graphics Drivers 11 10-19-02 09:17 AM
nv30 problem rumor bob747b Rumor Mill 37 10-10-02 03:14 PM
RH 8 Problem when insmod'ing NVdriver dmp NVIDIA Linux 3 10-05-02 08:14 PM
NVIDIA kernel not loading on boot-up, but insmod loads it Kyle NVIDIA Linux 3 09-10-02 12:01 AM
Nvidia Go on laptop, black border within XFree86 problem raxip NVIDIA Linux 3 07-31-02 10:58 AM

All times are GMT -5. The time now is 07:25 AM.

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