From: "Brian Johnson" <brian@dogtoe.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] ipw3945 and wpa_supplicant issues
Date: Wed, 16 May 2007 12:29:15 -0700 (PDT) [thread overview]
Message-ID: <11443.12.146.139.19.1179343755.squirrel@mail.dogtoe.com> (raw)
In-Reply-To: <46316F9F.1090207@burnieanglican.org.au>
Actually, Will you are a bit wrong. Restarting the ipw3945d service yields
the same results. Here's what happens when I restart the ipw3945 service:
# /etc/init.d/ipw3945d restart
* Stopping eth1
* Bringing down eth1
* Stopping dhcpcd on eth1 ...
[ ok ]
* Shutting down eth1 ...
[ ok ]
* Stopping wpa_cli on eth1 ...
[ ok ]
* Stopping wpa_supplicant on eth1 ...
[ ok ]
* Stopping ipw3945d ...
[ ok ]
* Starting ipw3945d ...
[ ok ]
* Starting eth1
* Starting wpa_supplicant on eth1 ...
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
[ ok ]th param 5 value 0x1 -
* Starting wpa_cli on eth1 ...
[ ok ]
* Backgrounding ...
Which is basically the same problem as what José posted about, except he
is restarting net.eth1.
Anyone know of a solution to fix this? (Aside from getting a different
wireless NIC)
* net-wireless/ipw3945
Latest version available: 1.2.0
Latest version installed: 1.2.0
* net-wireless/ipw3945-ucode
Latest version available: 1.14.2
Latest version installed: 1.14.2
* net-wireless/ipw3945d
Latest version available: 1.7.22-r4
Latest version installed: 1.7.22-r4
- Brian
On Thu, April 26, 2007 8:35 pm, Will Briggs wrote:
> � wrote: Hi all!
>
>
> I own a Toshiba laptop P100-400 with a Intel PRO/Wireless 3945ABG
> wireless adapter. I've managed to get it working with normal WEP
> authentication, but no success with wpa_supplicant (and I really need it
> for WPA auth).
>
> # /etc/init.d/net.eth1 restart
> * Stopping eth1
> * Bringing down eth1
> * Stopping dhcpcd on eth1
> ...
> [ ok ]
> * Shutting down eth1
> ...
> [
> ok ] * Stopping wpa_cli on eth1
> ...
> [ ok ]
> * Stopping wpa_supplicant on eth1
> ...
> [ ok ]
> * Starting eth1
> * Starting wpa_supplicant on eth1 ...
> 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
> [ ok ]th param 5 value 0x1 -
> * Starting wpa_cli on eth1
> ...
> [ ok
> ]
> * Failed to configure eth1 in the background
>
>
>
> Ugly, uh? :/
> Yeah
>
>
> A number of things, some of which you may know:
>
>
> 1) Don't add net.eth1 to runlevel. The ipw3945 module loading
> (/etc/modprobe.conf) runs ipw3945d init script which brings up net.eth1
> which is managed by wpa_supplicant. If you try and manage net.eth1
> yourself (with rc-update, or with something like ifplugd then things will
> get confused). I do have netplug configed for eth* but I think it knows
> how to get out of the way of wpa_supplicant.
>
> All you need to do is emerge ipw3945 - no rc-updating needed.
>
>
> 2) If you ever need to restart net.eth1, restart ipw3945d instead.
>
>
> 3) My wpa_supplicant.conf just as comparision:
>
>
> # Intel PRO/Wireless 3945 :: wpa_supplicant.conf
>
>
> ctrl_interface=/var/run/wpa_supplicant # DO NOT remove this line!
> ctrl_interface_group=0 # Only allow root to read config. ap_scan=1 #
> Allows wpa_supplicant to handle AP scanning.
>
>
> # The following configures wpa_supplicant for a WPA
> network={ ssid="foo"
> scan_ssid=1 # Use if SSID broadcast is disabled.
> psk="bar" # Your key here.
> }
>
>
> -- gentoo-user@gentoo.org mailing list
>
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2007-05-16 19:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-10 15:09 [gentoo-user] ipw3945 and wpa_supplicant issues José Pedro Saraiva
2007-04-26 0:11 ` José Pedro Saraiva
2007-04-26 10:03 ` Christian
2007-04-26 10:15 ` [gentoo-user] " Alexander Skwar
2007-04-27 3:35 ` [gentoo-user] " Will Briggs
2007-05-16 19:29 ` Brian Johnson [this message]
2007-05-16 21:06 ` Dan Farrell
2007-05-17 3:42 ` Mike Mazur
2007-05-17 6:07 ` Will Briggs
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=11443.12.146.139.19.1179343755.squirrel@mail.dogtoe.com \
--to=brian@dogtoe.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox