My WiFi eth1 interface (ipw3945) works when it's started by hotplug/coldplug/udev on boot, but when I try to restart the script, or disable startup on boot in the /etc/conf.d/rc file and start eth1 manually, I get following errors: * Starting eth1 * Loading networking modules for eth1 * modules: apipa arping ccwgroup macchanger macnet rename wpa_supplicant essidnet iptunnel ifconfig system dhcpcd ip6to4 * wpa_supplicant provides wireless * ifconfig provides interface * dhcpcd provides dhcp * Configuring eth1 for MAC address 00:13:CE:**:**:** ... [ ok ] y Wireless radio has been killed for interface eth1 y wpa_supplicant will launch, but not associate until y wireles radio is re-enabled for interface eth1 * Starting wpa_supplicant on eth1 ... ioctl[SIOCSIWMODE]: Resource temporarily unavailable ioctl[SIOCGIWRANGE]: Resource temporarily unavailable ioctl[SIOCSIWAUTH]: Resource temporarily unavailable WEXT auth param 7 value 0x1 - ioctl[SIOCSIWENCODEEXT]: Resource temporarily unavailable ioctl[SIOCSIWENCODEEXT]: Resource temporarily unavailable ioctl[SIOCSIWENCODEEXT]: Resource temporarily unavailable ioctl[SIOCSIWENCODEEXT]: Resource temporarily unavailable ioctl[SIOCSIWAUTH]: Resource temporarily unavailable WEXT auth param 4 value 0x0 - ioctl[SIOCSIWAUTH]: Resource temporarily unavailable [ ok ]th param 5 value 0x1 - * Starting wpa_cli on eth1 ... [ ok ] * Waiting for association [ ok ] * Backgrounding ... I could work around this by killing wpa_supplicant, restarting ipw3945d script and reloading module, and start wpa_supplicant manually. If I do all this stuff, it works as normal. I used ipw2200 on my previous thinkpad, and that worked perfectly... Info about system: # lspci |grep Wireless 03:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG Network Connection (rev 02) # emerge -s ipw3945 wpa_supplicant * net-wireless/ipw3945 Latest version available: 1.1.0-r1 Latest version installed: 1.1.0-r1 * net-wireless/ipw3945-ucode Latest version available: 1.13 Latest version installed: 1.13 * net-wireless/ipw3945d Latest version available: 1.7.22-r3 Latest version installed: 1.7.22-r3 * net-wireless/wpa_supplicant Latest version available: 0.5.4 Latest version installed: 0.5.4 There also is a thread about this on the forum. Not a lot of people with the same error, but at least I'm not alone :-) http://forums.gentoo.org/viewtopic-p-3721209.html#3721209
Exactly the same behaviour and errors here. Only minor differences: - I don't need to restart the ipw3945d - I _can't_ even reload the module (when doing rmmod, I'm told, that something still uses it) But killing wpa_supplicant and manually starting it makes the interface work again.
The behaviour seems to change with the currently marked unstable drivers - net-wireless/ipw3945 1.1.0-r1 - net-wireless/ipw3945d 1.7.22-r3 It doesn't start up on boot and when doing the killall wpa_supplicant, start wpa_supplicant manually trick, it gives: # wpa_supplicant -Dwext -i eth1 -c /etc/wpa_supplicant/wpa_supplicant.conf ioctl[SIOCSIWMODE]: Resource temporarily unavailable Could not configure driver to use managed mode ioctl[SIOCGIWRANGE]: Resource temporarily unavailable ioctl[SIOCSIWAUTH]: Resource temporarily unavailable WEXT auth param 7 value 0x1 - ioctl[SIOCSIWENCODEEXT]: Resource temporarily unavailable ioctl[SIOCSIWENCODEEXT]: Resource temporarily unavailable ioctl[SIOCSIWENCODEEXT]: Resource temporarily unavailable ioctl[SIOCSIWENCODEEXT]: Resource temporarily unavailable ioctl[SIOCSIWAUTH]: Resource temporarily unavailable WEXT auth param 4 value 0x0 - ioctl[SIOCSIWAUTH]: Resource temporarily unavailable WEXT auth param 5 value 0x1 - ioctl[SIOCGIWSCAN]: Resource temporarily unavailable ioctl[SIOCSIWSCAN]: Resource temporarily unavailable Failed to initiate AP scan. ioctl[SIOCGIWSCAN]: Resource temporarily unavailable ioctl[SIOCSIWSCAN]: Resource temporarily unavailable Failed to initiate AP scan. CTRL-EVENT-TERMINATING - signal 2 received ioctl[SIOCSIWAUTH]: Resource temporarily unavailable WEXT auth param 7 value 0x0 - Failed to disable WPA in the driver. ioctl[SIOCSIWAUTH]: Resource temporarily unavailable WEXT auth param 5 value 0x0 - ioctl[SIOCSIWAUTH]: Resource temporarily unavailable WEXT auth param 4 value 0x0 - ioctl[SIOCSIWAP]: Resource temporarily unavailable
(In reply to comment #2) > The behaviour seems to change with the currently marked unstable drivers > - net-wireless/ipw3945 1.1.0-r1 > - net-wireless/ipw3945d 1.7.22-r3 No, it doesn't really change. It's pretty messy over all with those intel drivers... :-/ > It doesn't start up on boot and when doing the killall wpa_supplicant, start > wpa_supplicant manually trick, it gives: > > # wpa_supplicant -Dwext -i eth1 -c /etc/wpa_supplicant/wpa_supplicant.conf > ioctl[SIOCSIWMODE]: Resource temporarily unavailable > Could not configure driver to use managed mode > ioctl[SIOCGIWRANGE]: Resource temporarily unavailable > ioctl[SIOCSIWAUTH]: Resource temporarily unavailable > WEXT auth param 7 value 0x1 - ioctl[SIOCSIWENCODEEXT]: Resource temporarily > unavailable > ioctl[SIOCSIWENCODEEXT]: Resource temporarily unavailable > ioctl[SIOCSIWENCODEEXT]: Resource temporarily unavailable > ioctl[SIOCSIWENCODEEXT]: Resource temporarily unavailable > ioctl[SIOCSIWAUTH]: Resource temporarily unavailable > WEXT auth param 4 value 0x0 - ioctl[SIOCSIWAUTH]: Resource temporarily > unavailable > WEXT auth param 5 value 0x1 - ioctl[SIOCGIWSCAN]: Resource temporarily > unavailable > ioctl[SIOCSIWSCAN]: Resource temporarily unavailable > Failed to initiate AP scan. > ioctl[SIOCGIWSCAN]: Resource temporarily unavailable > ioctl[SIOCSIWSCAN]: Resource temporarily unavailable > Failed to initiate AP scan. > CTRL-EVENT-TERMINATING - signal 2 received > ioctl[SIOCSIWAUTH]: Resource temporarily unavailable > WEXT auth param 7 value 0x0 - Failed to disable WPA in the driver. > ioctl[SIOCSIWAUTH]: Resource temporarily unavailable > WEXT auth param 5 value 0x0 - ioctl[SIOCSIWAUTH]: Resource temporarily > unavailable > WEXT auth param 4 value 0x0 - ioctl[SIOCSIWAP]: Resource temporarily > unavailable This can be "fixed" by adding "-w" to wpa_supplicant_eth1 in /etc/conf.d/net # wpa_supplicant_eth1="-Dwext -w" This will make wpa_supplicant wait for the interface to come up. When you modprobe the ipw3945 module, then the interface goes up and net.eth1 gets started automagically - this is still some kind of mystery to me. When you issue # /etc/init.d/net.eth1 stop the interface gets stopped, but you can't restart it. When then trying # modprobe -r ipw3945 modprobe will hang on you and I found no way back. Well, the basic thing is: Add -w to your wpa_supplicant parameters. And for the rest, I think this bug is the right one: http://bugs.gentoo.org/show_bug.cgi?id=147910 I dunno exactly what to do, but suggest closing this one.
I found a workaround for this, so that the ipw3945 is usable with the rcscripts. In /lib/rcscripts/net/wpa_supplicant add sleep 5 just before the call to start-stop-daemon wpa_supplicant in line 306 (baselayout-1-12.6). Looks like this gives the interface enough time to initialize itself before wpa_supplicant fails over and over again on it.
Nice - Works for me, too! (AMD64) Status should be changed...
(In reply to comment #4) > I found a workaround for this, so that the ipw3945 is usable with the > rcscripts. > > In > /lib/rcscripts/net/wpa_supplicant > add > sleep 5 > just before the call to start-stop-daemon wpa_supplicant in line 306 > (baselayout-1-12.6). > Looks like this gives the interface enough time to initialize itself before > wpa_supplicant fails over and over again on it. You guys tried the newer baselayout (>=1.13.0_alpha10) yet ? Otherwise I'd like to talk to Roy (UberLord) for inclusion in baselayout.
Thanks the fix in comment #4 worked for me on x86. I have baselayout 1-12.9-r2 It would be nice if you can reopen this bug, and fix it in the baselayout.
