On Sat 2003-09-06 at 11:26:42 -0700, [EMAIL PROTECTED] wrote:
> On Sat, 2003-09-06 at 07:41, Benjamin Pflugmann wrote:
> > On Sat 2003-09-06 at 14:01:30 +0200, [EMAIL PROTECTED] wrote:
> > > 2.4.22-5mdkenterprise:
> > > The Nvidia vidio (NVIDIA_kernel-1.0-4363) driver compiles
> > > but is not possible to install it. I get a lot of unresolved
> > > symbols like:
> > > /lib/modules/2.4.22-5mdkenterprise/kernel/drivers/video/nvidia.o:
> > > unresolved symbol irq_stat
> > > 
> > > I have the same problem with 2.4.22-5mdk-i686-up-4GB.
> > > 2.4.22-4mdkenterprise works fine.
> > 
> > This is mainly a "me too".
[...]
> > I am not sure if it is related or not, but just to be sure I tried the
> > "make mrproper; ..." tip from the other nvidia/kernel related mail
> > with no apparent effect.
[...]
> Well, I went a bit further and ran make oldconfig and make dep

I did that. That was what I referred to with "make mrproper; ..."[1]
Well, I'll just tried again:

  $ cd /usr/src/linux
  $ make mrproper
  $ cp arch/i386/defconfig .config
  $ make oldconfig dep

Nope, I now even removed the source, cleaned up what was left
over and started from the beginning. Same result.

Okay. Let's reboot to kernel-2.4.22.5mdk-1-1mdk, calling the
NVidia script... and it works!

Reboot to kernel-i686-up-4GB-2.4.22.5mdk-1-1mdk. Well, as I
feared, the now installed module doesn't work.

Hmmmmm. Let's see if there is a defconfig for that kernel...
yepp: arch/i386/defconfig-i686-up-4GB. One "make mrproper", a
copy and "make oldconfig dep" later: it works!

Now I go back to my corner with a deeply red face and allow
myself some time feeling dumb.[2]

> The nvidia module now is loaded correctly. 

Thanks for sharing,

       Benjamin.


[1] Note the ellipses; since there was only one such suggestion
    in the last days, I thought it was unambiguous - well, I know
    better know ;-).

[2] Well, for my defense I can say that though I use Linux since
    the version 0.9 days I never had a need to configure (and
    compile) a kernel myself. Yep, most times it simply worked,
    and for critical systems, there was always some "kernel-guy"
    around.


Reply via email to