On Wednesday 01 March 2006 7:36 pm, Dimitrios Apostolou wrote: > > Customize your mkinitrd.conf by changing AUTODETECT=0 to AUTODETECT=1, > > then rebuild your initrd with the mkinitrd auto command, reboot, and they > > are gone. > > OK, but by doing this you don't solve the problem, only bypass it. You > have a specific initrd for your own system, like having built a specific > kernel, and if the hardware changes you 'll face a new problem. I'm > curious how it can be solved while retaining the generic initrd. How do > other distros do it?
I recall from the time I used Mandrake, that the mkinitrd scripts somehow detected your hardware and only included the modules you needed when the initrd was created. I don't recall how exactly it did that, and I don't have an old install to look at. I imagine that hwdetect could somehow be used to provide the list of needed modules and only include those in initrd. -- Greg _______________________________________________ arch mailing list [email protected] http://www.archlinux.org/mailman/listinfo/arch
