Joey Hess <joeyh@debian.org> (2006-05-28): > 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. I'm not sure whether the following idea would make sense: when an udeb is installed, shipping something below /lib/modules, we could queue a depmod run (more or less mimicking a dpkg trigger). (I haven't done any cost analysis, but we probably don't want do that after every udeb when installing a bunch of them at once.) Mraw, KiBi.
Attachment:
signature.asc
Description: Digital signature