Re: unresolved symbols

[Marcelo Chiapparini <chiappa@centroin.com.br>]

On Sat, May 19, 2001 at 10:43:48PM -0400, Michael P. Soulier wrote:
>     So I installed the kernel image package for 2.4.4 686, and now when depmod
> -a runs, I get this:
> 
> tigger:/etc# depmod -a
> depmod: *** Unresolved symbols in
> /lib/modules/2.4.4-686/kernel/drivers/scsi/pci2220i.o
> 
>     Is this package broken?
> 

I had a problem like this some days ago whith 2.2.19. In your example the 
pci2220i.o is a module. It depends on other modules which either have been 
compiled into directly into the kernel or they were not included (directly or 
as modules) into the kernel at all. My suggestion is to look the modules 
pci2220i.o depends on and compile them into the kernel as modules too.

My problem was with the modules epat.o, friq.o and frpw.o. All of them depends 
on paride.o. I compiled paride directly into the kernel, but epat, friq and 
frpw as modules. At boot time depmod -a complained about the unresolved 
symbols epat.o, friq.o and frpw.o. Apparently depmod didn't realised that the 
paride support was already compiled into the kernel. The solution was to 
compile paride like a module too.

Hope this helps,
Marcelo