On Mar 3, 12:34 am, Del <[EMAIL PROTECTED]> wrote: > Hi, > > I have a Toshiba laptop with an ipw2200 wireless device. It currently > runs Fedora Core 6 but I've tried a few other distros on it (mostly booting > from a small set of /boot partitions I keep at the back of the disk, and > mounting most of the rest of their stuff from an attached USB disk, but > I wouldn't think that'd cause the problem). > > Quite frequently, I'd say about 25% of the time, when it boots it comes up > with a message during network initialisation saying "ipw2200 device eth1 > not found, skipping initialisation" or whatever the distro's words to that > effect are. When I run "ipconfig -a" or look in /dev I found that the ipw2200 > device that is normally /dev/eth1 has in fact set itself up as /dev/__tmp22993 > or something equally stupid. Rebooting usually makes the problem go away,
In lieu of more appropriate and expert advice from someone else on list, I could offer some suggestions though they may not address your hardware/dev issue. What do you get when you run iwconfig ? Also, what's in /proc/net/wireless? What's in your /etc/modprobe.d/ipwXXXX file? You could kill ipwXXXX and ipwXXXXd the regulatory daemon - just as an experiment, then try to start them up again and look for errors. Maybe they start up more reliably after the boot - I have no idea. On my working system: [EMAIL PROTECTED]:init.d$ ps -ef | grep -i ipw root 3118 11 0 15:33 ? 00:00:00 [ipw3945/0] root 3119 11 0 15:33 ? 00:00:00 [ipw3945/1] root 3120 11 0 15:33 ? 00:00:00 [ipw3945/0] root 3121 11 0 15:33 ? 00:00:00 [ipw3945/1] root 3295 1 0 15:33 ? 00:00:19 /sbin/ ipw3945d-2.6.17-11-generic --quiet As an experiment, I removed the ipw3945 module using rmmod (maybe modprob -r is more appropriate) and killed off the daemon using the -- kill option to the above /sbin program. I don't get eth1 showing up at all in ifconfig or iwconfig until I 'modprobe ipw3945' which brings back the above [ipw3945/x] processes. It also starts the ipw3945d daemon. I then invoke wpa_supplicant and configure it for eth1: wpa_supplicant -ieth1 -c/etc/wpa_supplicant/wpa_supplicant.conf -Dwext -w -B (You may have to ifconfig your eth1 interface and set up your routing tables again to get connected) HTH - in some tangential way, perhaps :) Daniel -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
