On Fri, 20 Jul 2007 12:38:12 Allan Gottlieb wrote: > Sounds good. I assume you do *not* have ipw3945 in > /etc/modules.autoload.d/kernel-2.6. If my guess is wrong, do you get > the boot-time error message I mentioned (Failed to load ipw3945). > Your guess is correct, it is not in there.
> > My /etc/modules.d/ipw3945d contains: > > > > install ipw3945 /sbin/modprobe --ignore-install ipw3945; sleep > > 0.5; /etc/init.d/ipw3945d start > > remove ipw3945 /etc/init.d/ipw3945d stop; /sbin/modprobe -r > > --ignore-remove ipw3945 > > That must be setup by default since I have the exact same and am > confident that I didn't modify it. > Once upon a time it had to be manually added, probably been the default for a while though. > > Udev-postmount holds off launching it until it reaches runlevel three. > > How do you get udev-postmount to launch it? Did you add something to > 10-local.rules? If so could you post it. > You know, I can't actually recall manually tweaking anything to get it like that (although that may be due to poor memory rather than a lack of manual intervention). I have no 10-local.rules in my /etc/udev/rules.d . I just rechecked and udev-postmount is actually a red herring (sorry). I used to have the modules load , which initiated the ipw3945d with an error that it can't start until runlevel three, then it worked perfectly once that runlevel was reached. Now it loads the module but delays starting ipw3945d until inside runlevel three with the message "device initiated services: ipw3945d udev-postmount". I think an upgrade made the difference. So maybe they have nothing to do with each other except being launched at the same time. I've been poking through my system and can't find anything that explicitly controls when it starts. I'm using baselayout-1.12.10-r4, ipw3945-1.2.0, ipw3945d-1.7.22-r4 . See if using those versions makes it magically 'just work' for you. I fnot I can poke around more. - Noven -- >-- Novensiles divi Flamen --< >---- Miles Militis Fons ----< -- [EMAIL PROTECTED] mailing list
