Summary: | coldplug-20040920 does not load net modules | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | John Altstadt <altstadt> |
Component: | [OLD] Core system | Assignee: | Greg Kroah-Hartman (RETIRED) <gregkh> |
Status: | VERIFIED FIXED | ||
Severity: | critical | CC: | lorien420 |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
John Altstadt
2004-11-11 16:46:53 UTC
rc-update coldplug to the boot level, the same level you had hotplug at. That should solve this issue. As for the firmware files, they should have all been moved already by the packages that own them. If not, file bugs for them. You are making an incorrect assumption. sabre root # cd /etc/runlevels sabre runlevels # ls boot default boot: alsasound checkfs clock hostname localmount net.lo serial bootmisc checkroot consolefont keymaps modules rmnologin urandom default: autofs distccd lm_sensors netmount sshd bootsplash domainname local nfs syslog-ng cupsd hotplug net.eth0 ntpd vixie-cron sabre runlevels # As you can see, hotplug is in default, not boot. Why can't coldplug go in the same place? I will try coldplug in boot though. Coldplug should go into the same place as hotplug. The assumption was that a lot of users put hotplug in their boot level, that is why I made it. If coldplug is at the same level as hotplug, there should be no difference, unless you happened to have hotplug running before net.* due to the way you installed the box :) coldplug works when added to runlevels/boot but not when it is added to runlevels/default which was where hotplug always lived. Can this be fixed? The forum discussion mentioned above has one comment that states: "You are probably right but shouldn't be issue solved by adding "before net" to those damn coldplug scripts?" As for the firmware files, this system never had any that I can tell. The command locate firmware doesn't find anything relevant. Over the long term I would prefer to move the required modules into /etc/modules.autoload.d/kernel*, which currently only contains ide-scsi. So, is there any way of finding out exactly which modules coldplug (or the old hotplug) is loading? All that shows up at boot is a generic message that says coldplug is working on usb, pci, etc. dmesg doesn't contain the console boot messages, and there are not enough messages coming from the modules themselves to identify them. (Our last comments collided.) As I mentioned in bug #70793 and the forum discussion, I have no idea how hotplug got on my systems. It had to have been in the first few hours of a fresh install. The directions given at that time must have been to put it in default, because I wouldn't have had a clue otherwise at the time. I guess a lot of people were just lucky up till now. :-) Look at what modules are loaded after booting. If they aren't listed in your autoload file, put them there. That's all you need to do. And yes, it does look like a lot of people were getting lucky. Put coldplug at the "boot" level should solve the issue for everyone. I was afraid you were going to say that. lsmod shows lots of modules, but I know that many of them were already installed before coldplug was started and that installing some of them will automatically trigger the installation of others. Is there a problem with putting them all in modules.autoload.d, i.e. will some other part of the boot try to load them a second time and break the system in some other imaginative way? How about just putting the modules that you _know_ you need in there (like for your network card) and then working from there. And no, just putting all of them in there would not harm anything. |