At Fri, 20 Jul 2007 13:19:55 +0930 Novensiles divi Flamen <[EMAIL PROTECTED]> wrote:
> 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. Well I am running stable x86 so my baselayout is only 1.12.9-r2 and perhaps your newer version loads ipw3945. However, I am a little leery of running unstable baselayout. So I think I'll wait for the new version to become stable. I have filed a note to myself to see if that eliminates the (fairly painless) error message that I now get. Thanks again for your help and effort. allan -- [EMAIL PROTECTED] mailing list
