Am 22.04.2015 um 21:39 schrieb Canek Peláez Valdés: > On Wed, Apr 22, 2015 at 2:17 PM, walt <w41...@gmail.com > <mailto:w41...@gmail.com>> wrote: > > > > I just did a huge update on an older ~amd64 machine, and now only > > three out of a dozen or so kernel modules load during bootup, which > > leaves a lot of hardware in an unusable state. > > > > What mystifies me is how those three kernel modules managed to get > > loaded while all the others didn't. (It's the same three modules every > > time, BTW.) > > > > I grepped through /etc for the names of those modules, thinking maybe > > I listed them in modprobe.conf.d sometime in the past, but no, those > > modules are not listed anywhere in /etc, nor are any of the others > > listed either. > > > > I can modprobe all of the unloaded modules manually after bootup, > > which shows that all of the modules exist and load without error, > > so the problem lies elsewhere, but where? > > > > Any clues would be most welcome. > > If you are using systemd, there are a few modules that it always loads > (ipv6, autofs4, stuff like that). Everything else is loaded > automatically, by udevm, as-needed. > > My guess (but I could be wrong); you are using an initramfs, and > didn't included the modules in it. In that case, the modules are not > loaded because they are not available. > > I have no idea if OpenRC tries to load modules.
yes it does. You poor bunny. All those years using openrc all but forgotten? > > Regards. > -- > Canek Peláez Valdés > Profesor de asignatura, Facultad de Ciencias > Universidad Nacional Autónoma de México
