i executed update-modules force and obtained this: <<<<<<<<<<<<<< # update-modules force Warning: /etc/modules.conf has not been automatically generated * --force specified, (re)generating file anyway * Updating modules.conf ... [ ok ] * Updating modules.dep ... [ ok ] * Please file a bug about /etc/modules.d/ipw3945: it needs an /etc/modprobe.d/ipw3945 * Updating modprobe.conf by hand ... >>>>>>>>>>>>>> it seems this should depend on #215626 question is: can i reboot my machine safely?
Frankly, on a recent system, there's no need for either modules.conf, modprobe.conf or /etc/modules.d/ - modprobe should pick up all the *.conf files from /etc/modprobe.d automatically, obsoleting 'update-modules'. Anyway, IIRC, /etc/modules.d/ (and modules.conf) was a legacy of 2.4 kernel anyway. Simpy check both of those dirs for any files that you didn't create: - if there's one in /etc/modules.d/, see if reemerging puts it in /etc/modprobe.d - if there's one in /etc/modprobe.d without conf extension, it's either a bug in the package or the package is late in being stabled For any files you've created, move to /etc/modules.d/, making sure about extension. modprobe.conf and modules.conf should be safe to remove.
(In reply to comment #1) > Frankly, on a recent system, there's no need > for either modules.conf, modprobe.conf or /etc/modules.d/ > - modprobe should pick up all the *.conf files from /etc/modprobe.d > automatically, obsoleting 'update-modules'. > Anyway, IIRC, /etc/modules.d/ (and modules.conf) was a legacy of > 2.4 kernel anyway. > Simpy check both of those dirs for any files that you didn't create: > - if there's one in /etc/modules.d/, see if reemerging puts it > in /etc/modprobe.d > - if there's one in /etc/modprobe.d without conf extension, > it's either a bug in the package or the package is late in being stabled > > For any files you've created, move to /etc/modules.d/, making sure about > extension. > modprobe.conf and modules.conf should be safe to remove. > Rafal, thanks a lot. Really nice answer from your part. I did this: # l /etc/modules.d/ total 12 drwxr-xr-x 2 root root 4096 nov 4 16:41 . drwxr-xr-x 110 root root 4096 ene 12 21:09 .. -rw-r--r-- 1 root root 613 dic 26 2006 ipw3945 i realized that this file corresponds to the old driver of my intel wifi card, new driver is called iwl3945. Of course, nowadays i am working with iwl3945 so i think it is safe to remove. Anyway, just to make sure, i performed this: # equery belongs ipw3945 [ Searching for file(s) ipw3945 in *... ] with no results...so i deleted the file, reboot and everything is working
