I have finally resolved this issue after a number of suggestions from kind people on the net. Eventually I amended some of the ideas to reach the correct solution. I found that in fact the modules (ipw3945 and ieee80211) were in fact loaded at boot but it was the regulatory daemon that was not running (ipw3945d) The solution was to append a single line to the /etc/rc.local file: /sbin/ipw3945d --quiet Now with this line in, then after boot the wireless interface is running perfectly and the regulatory daemon is running. Then with the regulatory daemon continuing to run, a user can switch the eth1 interface off or on with /sbin/ifup eth1 or /sbin/ifdown eth1 any time they like. This is nice - but it took a lot of searching to find the solution ! Mike On 4/13/06, Mike Cohler <mike.cohler@xxxxxxxxx> wrote: > On 4/12/06, Mike Cohler <mike.cohler@xxxxxxxxx> wrote: > > > >It didn't want to start up right the first time after boot. I'm > > >pretty sure I read on the ipw3945 list or website that some other > > >folks had this problem too. I haven't tried it, but I'm wondering if > > >switching /sbin/ipw3945d --quiet and /sbin/modprobe in the > > >modprobe.conf entry would make this work better. The module needs the > > That did not work unfortunately. > > Mike > -- > > mike cohler > -- mike cohler
