Re: Dependant modules question

[Vladislav Bolkhovitin <vst@vlnb.net>]

Richard B. Johnson wrote:
> Did you execute `depmod -a` after putting your modules into the
> default  directories and their information into /etc/modules.conf ?
 >
> Example:
> /etc/modules.conf
> alias char-major-177  module-a		# First to load
> alias char-major-177  module-b		# Second to load
> alias char-major-177  off		# All done
> 
> 
> # cp module-a.o /lib/modules/`uname -r`/kernel/drivers/char
> # cp module-b.o /lib/modules/`uname -r`/kernel/drivers/char
> # depmod -a
> 
> The first time anybody tries to access a device with the major
> number of 177, its modules will be loaded in the correct order
> by modprobe.
> 
> Cheers,
> Dick Johnson
> Penguin : Linux version 2.4.26 on an i686 machine (5570.56 BogoMips).
>             Note 96.31% of all statistics are fiction.

Sure, I did. That works fine if A is built in the kernel tree (i.e. the 
sources of A stays there), not when both A and B are external modules.

Actually, the problem is a bit different: compiled B know nothing about 
A and doesn't reffer to it, so depmod and friends can't help. Ever if A 
already loaded, B refused to load (can't find the symbols). I suspect, I 
need to add something in the Makefile of A/B/both. But what?

Thanks,
Vlad