|
network module/daemon load at boot time
so I'm running debian testing on a dell laptop, and I've been working on getting the internal intel wifi card working. it works, but it seems that it isn't getting loaded properly at boot time.
what I'm guessing should happen is:
modprobe ipw3945 ; load the module for the wifi card, which also starts the regulatory daemon
ifup eth2 ; it'll bring up the network and get an ip address, etc.
so, I put:
auto eth2 -> /etc/network/interfaces
ipw3945 -> /etc/modules
which will load the ipw3945 module (which should start the daemon) and raise the network.
but, booting up and doing 'ps -e', I can't find the daemon, which should show up there (thus, no internet). the module is loaded, though. then, I usually have to do a 'ifdown eth2' then a 'ipw3945d' to start the daemon, and then 'ifup eth2'. it's not terrible, but it's tedious. my thinking is either:
/etc/modules merely loads the module, and doesn't follow /etc/modprobe.d (in which I also start the daemon)
or
the eth2 interface gets raised before /etc/modules is done (unlikely, and doesn't explain why ipw3945d is absent)
I've taken a look at [URL="http://www.debian.org/doc/manuals/reference/ch-system.en.html"]
but the loading system seems to enjoy using sh, and even though it wouldn't take *too* long to learn, is there any easier way to just tell the boot process what I want?
ps. I know ndiswrapper would load up correctly - I'm assuming this has something to do the with the daemon.
pss. looking through how the laptop boots, there's nothing amiss. to think of it, I don't think I see when the module loads, either. maybe that has something to do with it?
|
Tux's suggestion for hotplug should work. If it doesn't just script it with basic bash. Since I am not really sure in what order the modules are loaded, and if you are extremely paranoid, you shouldn't start your wireless before all the security 'thingies' (notice the highly technical term) have been loaded. 
