Bug#369256: installation-reports: modprobe does not find kernel modules
On 5/29/06, Eddy Petrişor <email@example.com> wrote:
On 5/29/06, Joey Hess <firstname.lastname@example.org> wrote:
> Eddy Petrisor wrote:
> > The modprobe command bundled in d-i environment does not work out of the
> > box. If one starts the installer in expert mode and skips directly to
> > the "Load installer components from CD" menu item, chooses a kernel
> > module (let's say crypto modules) after the package's installation
> > attempting to run "modprobe aes" on vt2 will result in an error message
> > that the module is not found.
> > It seems that after running netcfg the modprobe command behaves
> > corectly.
> You have to run depmod. Before that, obviously modprobe has no way to
> know that your module is available. depmod is run by hw-detect.
> I'm not sure that I'd characterise this as a bug at all.
So depending on ethernet-card-detection should allow modprobe to work
I am quite sure that ppp-udeb had this failure when its postinst was
ran because at some time during my tests modprobing pppoe failed even
if ethernet-card-detection was a dependency since I started to modify
it (initially it depended on configured-network).
modify it = modify ppp-udeb
"Imagination is more important than knowledge" A.Einstein