From: Brandt Deakin <bdeakin@cardaccess-inc.com>
To: linux-wireless@vger.kernel.org
Subject: CARL9170/hostapd startup failures
Date: Fri, 08 Jul 2011 12:50:34 -0600 [thread overview]
Message-ID: <1310151034.2152.8.camel@bdeakin-x200> (raw)
I'm attempting to use carl9170 in AP mode and I'm seeing some
interesting errors. When calling hostapd to initialize the AP, 10-50%
of the attempts will be unsuccessful and report the following:
Could not set interface wlan0 flags: Connection ieee80211 phy1: lost 7
command responses/traps! w:9 g:0
usb 1-1: restart device (8)
timed out
nl80211: Could not set interface 'wlan0' UP
nl80211 driver initialization failed.
rmdir[ctrl_interface]: No such file or directory
usb 1-1: firmware upload failed (-110).
usb 1-1: Failed to restart device (-110).
usb 1-1: reset high speed USB device number 2 using ehci-omap
usb 1-1: reset high speed USB device number 2 using ehci-omap
usb 1-1: driver API: 1.9.2 2011-01-22 [1-1]
usb 1-1: firmware API: 1.9.2 2010-12-25
usb 1-1: Atheros AR9170 is registered as 'phy2'
I'm seeing this error on the Beagleboard xM (Ubuntu 11.04 2.6.38) as
well as on a Lenovo x200 PC (Ubuntu 11.04 2.6.38). I've reproduced it
with 2.6.39 on the Beagleboard (not xM) as well. When initializing the
normal client mode, I've never seen a failure to "upload" the firmware
like this. It seems to be particular to the AP mode. Suggestions for
resolution are appreciated. I'm going to open up the carl9170 firmware
source and start trying to determine a possible cause there.
Thanks,
Brandt
--
Brandt Deakin
Card Access, Inc.
11778 S. Election Rd. Ste 260
Salt Lake City, UT 84020
801-748-4900 x23
801-748-4901 fax
bdeakin@cardaccess-inc.com
www.cardaccess-inc.com
next reply other threads:[~2011-07-08 18:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-08 18:50 Brandt Deakin [this message]
2011-07-11 15:04 ` CARL9170/hostapd startup failures Brandt Deakin
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=1310151034.2152.8.camel@bdeakin-x200 \
--to=bdeakin@cardaccess-inc.com \
--cc=linux-wireless@vger.kernel.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