Bug#209301: modconf / isa-pnp
On Sat, Sep 13, 2003 at 10:17:30AM +0200, Eduard Bloch wrote:
> #include <hallo.h>
> * Ryan Underwood [Fri, Sep 12 2003, 10:21:21PM]:
> > > Short answer: use precompiled kernels if you cannot do it properly in
> > > your own. If you build the isa-pnp module with the kernel, the created
> > > modules (ISA drivers) will depend on it and autoload when needed.
> > I'm not sure what you are talking about. I am referring specifically
> > about when modconf is called during Debian installation. The new user
> Me too. Modconf used modprobe, modprobe looks on on modules.dep, the
> particular module (_if_ it works together with isa-pnp) needs isa-pnp so
> modprobe loads isa-pnp. Your scenario can only appear if you have a mix
> of modules from different kernel builds.
If the module itself is aware of isa-pnp, then yes, this is the case.
However, consider this scenario: The card is a PnP card, the driver is
not PnP aware and would like to know the I/O and IRQ resources when
loaded. The card must first be configured by loading isa-pnp, and then
the other driver can be loaded based on the resources that the card is
> As said before, isa-pnp is loaded when the kernel has been built with
> the isa-pnp module. If the particular driver does _not_ communicate with
> the isa-pnp module, loading it would not help anyways.
Please refer to the above case; I think this is an exception to your
statement, but I could be wrong. :)
Ryan Underwood, <nemesis at icequake.net>, icq=10317253