According to Charles E. Gelm: While burning my CPU.
> 
> I am running an IP-MASQuerade with Slackware 3.5.0.  I
> 
> make mrproper
> make config
> make dep clean
> make zlilo
> make modules modules_install
> 
>  Why does
> depmod -a
>  return unresolved sysbols for things I did not select in make config?
> I don't (think I) want any of these modules:

The modules are possably from an old compile, at a guess i would say you
were running 2.0.34 and now you have made a new kernel which is also 2.0.34
right,??.

So you now have a mixture of "old" modules and "new" modules in the same
directory. One way around this without losing any modules, allowing you to
use the old ones with the old kernel, make a symbolic link in /lib/modules
called 2.0.34 and rename the old directory to org-2.0.34, then make a new
directory for each compile, call them 2.0.34-1 2.0.34-2 etc.

mv 2.0.34 org-2.0.34
mkdir 2.0.34-1
ln -s 2.0.34-1 2.0.34
copy the newly made modules to 2.0.34-1 (you should see which ones are the
new ones from the timestamps on the files).
Now the next time you make a fresh 2.0.34 kernel BEFORE doing make modules
remove the symlink in /lib/modules to the new "To be compiled kernel", for
example this time it will be 2.0.34-2, so you would need to do;

cd /lib/modules
rm 2.0.34
mkdir 2.0.34-2
ln -s 2.0.34-2 2.0.34

Now when you do 'make modules modules_install' the new modules will go into
/lib/modules/2.0.34-2. Booting the new 2.0.34 kernel should not give any
more errors.

I wrote a script for booting multiple kernels of the same kernel version,
because of this very problem.

If we call our images 2.0.34-1 -2 etc, in /etc/lilo.conf then its very easy
to use a script to link to the desired modules directory, by way of looking
into the proc filesystem during boottime, cmdline contains that data, so
then a script can remove the old link and create a new one automaticly.

> 
> /lib/modules/2.0.34/fs/nls.o: unresolved symbol(s)
> /lib/modules/2.0.34/fs/ncpfs.o: unresolved symbol(s)
> /lib/modules/2.0.34/misc/ipx.o: unresolved symbol(s)
> /lib/modules/2.0.34/misc/appletalk.o: unresolved symbol(s)
> /lib/modules/2.0.34/misc/psaux.o: unresolved symbol(s)
> /lib/modules/2.0.34/misc/msbusmouse.o: unresolved symbol(s)
> /lib/modules/2.0.34/misc/busmouse.o: unresolved symbol(s)
> /lib/modules/2.0.34/misc/atixlmouse.o: unresolved symbol(s)
> /lib/modules/2.0.34/net/dlci.o: unresolved symbol(s)
> /lib/modules/2.0.34/net/ibmtr.o: unresolved symbol(s)
> /lib/modules/2.0.34/block/raid0.o: unresolved symbol(s)
> /lib/modules/2.0.34/block/linear.o: unresolved symbol(s)
> /lib/modules/2.0.34/ipv4/ip_alias.o: unresolved symbol(s)
> 
> :-|
> Chuck
> 


-- 
Regards Richard.
[EMAIL PROTECTED]

Merry Xmas to all, and may all your troubles be small (ones).

Reply via email to