On 2001.08.31 09:19 Iain Conochie wrote:
> Hiya people,
>
> Q2 Usually when I get unresolved symbols in a module for a kernel
> compilation, it is because I am loading a module that was not compiled for
> that kernel - eg make modules_install without rm -rvf
> /lib/modules/*kernel-version* so some old modules may still be hanging
> around. I dont usually see it from the outset. What does unresolved
> symbols actually mean?? The Function call does not exist?? Is there no
> place for the module to hook into the kernel (kinda like amino acids - key
> and a lock thing) ??
Hi Monkey,
This can happen when your System.map file conflicts with your kernel.
Did you remember to move /usr/src/linux/System.map to /boot when you recompiled?
>
> Thanks for any pointers / answers / general advice,
HTH
>
> Monkey
>
cheers
Lawrence
--------------------------------------------------------------------
http://www.lug.org.uk http://www.linuxportal.co.uk
http://www.linuxjob.co.uk http://www.linuxshop.co.uk
--------------------------------------------------------------------
