| 1 |
Actually, Will you are a bit wrong. Restarting the ipw3945d service yields |
| 2 |
the same results. Here's what happens when I restart the ipw3945 service: |
| 3 |
|
| 4 |
# /etc/init.d/ipw3945d restart |
| 5 |
* Stopping eth1 |
| 6 |
* Bringing down eth1 |
| 7 |
* Stopping dhcpcd on eth1 ... |
| 8 |
[ ok ] |
| 9 |
* Shutting down eth1 ... |
| 10 |
[ ok ] |
| 11 |
* Stopping wpa_cli on eth1 ... |
| 12 |
[ ok ] |
| 13 |
* Stopping wpa_supplicant on eth1 ... |
| 14 |
[ ok ] |
| 15 |
* Stopping ipw3945d ... |
| 16 |
[ ok ] |
| 17 |
* Starting ipw3945d ... |
| 18 |
[ ok ] |
| 19 |
* Starting eth1 |
| 20 |
* Starting wpa_supplicant on eth1 ... |
| 21 |
ioctl[SIOCSIWMODE]: Resource temporarily unavailable |
| 22 |
Could not configure driver to use managed mode |
| 23 |
ioctl[SIOCGIWRANGE]: Resource temporarily unavailable |
| 24 |
ioctl[SIOCSIWAUTH]: Resource temporarily unavailable |
| 25 |
WEXT auth param 7 value 0x1 - ioctl[SIOCSIWENCODEEXT]: Resource |
| 26 |
temporarily unavailable |
| 27 |
ioctl[SIOCSIWENCODEEXT]: Resource temporarily unavailable |
| 28 |
ioctl[SIOCSIWENCODEEXT]: Resource temporarily unavailable |
| 29 |
ioctl[SIOCSIWENCODEEXT]: Resource temporarily unavailable |
| 30 |
ioctl[SIOCSIWAUTH]: Resource temporarily unavailable |
| 31 |
WEXT auth param 4 value 0x0 - ioctl[SIOCSIWAUTH]: Resource temporarily |
| 32 |
unavailable |
| 33 |
[ ok ]th param 5 value 0x1 - |
| 34 |
* Starting wpa_cli on eth1 ... |
| 35 |
[ ok ] |
| 36 |
* Backgrounding ... |
| 37 |
|
| 38 |
Which is basically the same problem as what José posted about, except he |
| 39 |
is restarting net.eth1. |
| 40 |
|
| 41 |
Anyone know of a solution to fix this? (Aside from getting a different |
| 42 |
wireless NIC) |
| 43 |
|
| 44 |
* net-wireless/ipw3945 |
| 45 |
Latest version available: 1.2.0 |
| 46 |
Latest version installed: 1.2.0 |
| 47 |
|
| 48 |
* net-wireless/ipw3945-ucode |
| 49 |
Latest version available: 1.14.2 |
| 50 |
Latest version installed: 1.14.2 |
| 51 |
|
| 52 |
* net-wireless/ipw3945d |
| 53 |
Latest version available: 1.7.22-r4 |
| 54 |
Latest version installed: 1.7.22-r4 |
| 55 |
|
| 56 |
- Brian |
| 57 |
|
| 58 |
On Thu, April 26, 2007 8:35 pm, Will Briggs wrote: |
| 59 |
> � wrote: Hi all! |
| 60 |
> |
| 61 |
> |
| 62 |
> I own a Toshiba laptop P100-400 with a Intel PRO/Wireless 3945ABG |
| 63 |
> wireless adapter. I've managed to get it working with normal WEP |
| 64 |
> authentication, but no success with wpa_supplicant (and I really need it |
| 65 |
> for WPA auth). |
| 66 |
> |
| 67 |
> # /etc/init.d/net.eth1 restart |
| 68 |
> * Stopping eth1 |
| 69 |
> * Bringing down eth1 |
| 70 |
> * Stopping dhcpcd on eth1 |
| 71 |
> ... |
| 72 |
> [ ok ] |
| 73 |
> * Shutting down eth1 |
| 74 |
> ... |
| 75 |
> [ |
| 76 |
> ok ] * Stopping wpa_cli on eth1 |
| 77 |
> ... |
| 78 |
> [ ok ] |
| 79 |
> * Stopping wpa_supplicant on eth1 |
| 80 |
> ... |
| 81 |
> [ ok ] |
| 82 |
> * Starting eth1 |
| 83 |
> * Starting wpa_supplicant on eth1 ... |
| 84 |
> ioctl[SIOCSIWMODE]: Resource temporarily unavailable |
| 85 |
> Could not configure driver to use managed mode |
| 86 |
> ioctl[SIOCGIWRANGE]: Resource temporarily unavailable |
| 87 |
> ioctl[SIOCSIWAUTH]: Resource temporarily unavailable |
| 88 |
> WEXT auth param 7 value 0x1 - ioctl[SIOCSIWENCODEEXT]: Resource |
| 89 |
> temporarily unavailable ioctl[SIOCSIWENCODEEXT]: Resource temporarily |
| 90 |
> unavailable ioctl[SIOCSIWENCODEEXT]: Resource temporarily unavailable |
| 91 |
> ioctl[SIOCSIWENCODEEXT]: Resource temporarily unavailable |
| 92 |
> ioctl[SIOCSIWAUTH]: Resource temporarily unavailable |
| 93 |
> WEXT auth param 4 value 0x0 - ioctl[SIOCSIWAUTH]: Resource temporarily |
| 94 |
> unavailable |
| 95 |
> [ ok ]th param 5 value 0x1 - |
| 96 |
> * Starting wpa_cli on eth1 |
| 97 |
> ... |
| 98 |
> [ ok |
| 99 |
> ] |
| 100 |
> * Failed to configure eth1 in the background |
| 101 |
> |
| 102 |
> |
| 103 |
> |
| 104 |
> Ugly, uh? :/ |
| 105 |
> Yeah |
| 106 |
> |
| 107 |
> |
| 108 |
> A number of things, some of which you may know: |
| 109 |
> |
| 110 |
> |
| 111 |
> 1) Don't add net.eth1 to runlevel. The ipw3945 module loading |
| 112 |
> (/etc/modprobe.conf) runs ipw3945d init script which brings up net.eth1 |
| 113 |
> which is managed by wpa_supplicant. If you try and manage net.eth1 |
| 114 |
> yourself (with rc-update, or with something like ifplugd then things will |
| 115 |
> get confused). I do have netplug configed for eth* but I think it knows |
| 116 |
> how to get out of the way of wpa_supplicant. |
| 117 |
> |
| 118 |
> All you need to do is emerge ipw3945 - no rc-updating needed. |
| 119 |
> |
| 120 |
> |
| 121 |
> 2) If you ever need to restart net.eth1, restart ipw3945d instead. |
| 122 |
> |
| 123 |
> |
| 124 |
> 3) My wpa_supplicant.conf just as comparision: |
| 125 |
> |
| 126 |
> |
| 127 |
> # Intel PRO/Wireless 3945 :: wpa_supplicant.conf |
| 128 |
> |
| 129 |
> |
| 130 |
> ctrl_interface=/var/run/wpa_supplicant # DO NOT remove this line! |
| 131 |
> ctrl_interface_group=0 # Only allow root to read config. ap_scan=1 # |
| 132 |
> Allows wpa_supplicant to handle AP scanning. |
| 133 |
> |
| 134 |
> |
| 135 |
> # The following configures wpa_supplicant for a WPA |
| 136 |
> network={ ssid="foo" |
| 137 |
> scan_ssid=1 # Use if SSID broadcast is disabled. |
| 138 |
> psk="bar" # Your key here. |
| 139 |
> } |
| 140 |
> |
| 141 |
> |
| 142 |
> -- gentoo-user@g.o mailing list |
| 143 |
> |
| 144 |
|
| 145 |
|
| 146 |
-- |
| 147 |
gentoo-user@g.o mailing list |
Archives