From: Dan Farrell <dan@spore.ath.cx>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] ipw3945 and wpa_supplicant issues
Date: Wed, 16 May 2007 16:06:33 -0500 [thread overview]
Message-ID: <20070516160633.03f8a01b@pascal.spore.ath.cx> (raw)
In-Reply-To: <11443.12.146.139.19.1179343755.squirrel@mail.dogtoe.com>
On Wed, 16 May 2007 12:29:15 -0700 (PDT)
"Brian Johnson" <brian@dogtoe.com> wrote:
> 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:
> ...
> > 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? :/
Quite. It sounds like maybe you need to insert a few more modules, or
maybe need wireless extensions enabled in the kernel?
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2007-05-16 21:15 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
2007-05-16 21:06 ` Dan Farrell [this message]
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=20070516160633.03f8a01b@pascal.spore.ath.cx \
--to=dan@spore.ath.cx \
--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