From: Felipe Balbi <me@felipebalbi.com>
To: Tilman Schmidt <tilman@imap.cc>
Cc: me@felipebalbi.com, Eugeniy Meshcheryakov <eugen@debian.org>,
linux-usb@vger.kernel.org, linux-wireless@vger.kernel.org
Subject: Re: Q: support for AVM Fritz! WLAN USB in kernel 2.6.25+
Date: Sun, 3 Aug 2008 02:12:06 +0300 [thread overview]
Message-ID: <20080802231201.GB23361@frodo> (raw)
In-Reply-To: <4894D86A.6030108@imap.cc>
On Sat, Aug 02, 2008 at 11:58:02PM +0200, Tilman Schmidt wrote:
> Aug 2 19:06:16 compaq kernel: read firmware upload result
> Aug 2 19:06:16 compaq kernel: TNETW1450 firmware upload successful!
> Aug 2 19:06:16 compaq kernel: initializing max packet templates
> Aug 2 19:06:16 compaq kernel: acx: issue_cmd(): USB read error -75
hmm... an overflow here.
It's probably timing issue as well.
> Aug 2 19:06:16 compaq kernel: acx: issue_cmd(cmd:ACX1xx_CMD_INTERROGATE) FAILED
> Aug 2 19:06:16 compaq kernel: wlan%d: interrogate(type:ACX1xx_IE_MEMORY_CONFIG_OPTIONS) FAILED
> Aug 2 19:06:16 compaq kernel: dump queue head (from card):
> Aug 2 19:06:16 compaq kernel: len: 20
> Aug 2 19:06:16 compaq kernel: tx_memory_block_address: 80000B80
> Aug 2 19:06:16 compaq kernel: rx_memory_block_address: DF313D34
> Aug 2 19:06:16 compaq kernel: tx1_queue address: 10
> Aug 2 19:06:16 compaq kernel: rx1_queue address: E080FBBD
> Aug 2 19:06:16 compaq kernel: get_mask 0x00004182, set_mask 0x00000000
> Aug 2 19:06:16 compaq kernel: don't know how to get sensitivity for radio type 0x1B
> Aug 2 19:06:16 compaq kernel: got sensitivity value 0
> Aug 2 19:06:16 compaq kernel: got antenna value 0x4A
> Aug 2 19:06:16 compaq kernel: got regulatory domain 0x30
> Aug 2 19:06:16 compaq kernel: get_mask 0x00000000, set_mask 0x00000000 - after update
> Aug 2 19:06:16 compaq kernel: new ratevector: 82 84 0B 0C 12 16 18 24 2C 30 48 60 6C
> Aug 2 19:06:16 compaq kernel: setting RXconfig to 2010:0FDD
> Aug 2 19:06:16 compaq kernel: acx: === chipset TNETW1450, radio type 0x1B (An unknown radio used by TNETW1450 USB adapters), form factor 0x00 (unspecified), EEPROM version 0x05: uploaded firmware 'Rev 2.4.0.72' ===
> Aug 2 19:06:16 compaq kernel: registering network device
> Aug 2 19:06:16 compaq kernel: creating /proc entry driver/acx_wlan0
> Aug 2 19:06:16 compaq kernel: creating /proc entry driver/acx_wlan0_diag
> Aug 2 19:06:16 compaq kernel: creating /proc entry driver/acx_wlan0_eeprom
> Aug 2 19:06:16 compaq kernel: creating /proc entry driver/acx_wlan0_phy
> Aug 2 19:06:16 compaq kernel: acx: USB module v0.3.37 loaded successfully
> Aug 2 19:06:16 compaq kernel: usb 2-2: New USB device found, idVendor=057c, idProduct=6201
> Aug 2 19:06:16 compaq kernel: usb 2-2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
> Aug 2 19:06:16 compaq kernel: usb 2-2: Product: WLAN USB Device
> Aug 2 19:06:16 compaq kernel: usb 2-2: Manufacturer: AVM GmbH
> Aug 2 19:06:16 compaq kernel: usb 2-2: SerialNumber: 001C4AF1E469
> Aug 2 19:06:16 compaq ifup: wlan0
> Aug 2 19:06:16 compaq ifup: No configuration found for wlan0
hmm... what does lsusb -v -d 057c:6201 reports to you ?
> The device was reported in iwconfig as:
>
> wlan0 IEEE 802.11b+/g+ ESSID:"STAF1E469" Nickname:"acx v0.3.37"
> Mode:Managed Frequency:2.412 GHz Access Point: Not-Associated
> Bit Rate:54 Mb/s Tx-Power=15 dBm
> Retry min limit:7 RTS thr:off
> Encryption key:off
> Power Management:off
> Link Quality:0 Signal level:0 Noise level:0
> Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
> Tx excessive retries:0 Invalid misc:0 Missed beacon:0
>
> but didn't work. In particular "iwlist wlan0 scan" failed with the message:
>
> wlan0 Interface doesn't support scanning : Resource temporarily unavailable
Did you try setting the parameters by hand ?
# iwconfig wlan0 essid <ESSID> key <KEY>
and then
# dhclient wlan0
> Aug 2 20:14:05 compaq kernel: usb 2-2: reset high speed USB device using ehci_hcd and address 12
> Aug 2 20:14:20 compaq kernel: usb 2-2: device descriptor read/64, error -110
It's probably affected by timing as well. That driver sure needs some
rework. Btw, are you using the mac80211 version or the other one ?
--
balbi
next prev parent reply other threads:[~2008-08-02 23:12 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-31 14:52 Q: support for AVM Fritz! WLAN USB in kernel 2.6.25+ Tilman Schmidt
2008-07-31 15:25 ` Johannes Berg
2008-07-31 16:34 ` Tilman Schmidt
2008-07-31 16:50 ` John W. Linville
2008-07-31 22:13 ` Tilman Schmidt
2008-07-31 22:43 ` Eugeniy Meshcheryakov
2008-08-01 23:30 ` Tilman Schmidt
2008-08-02 8:28 ` Felipe Balbi
2008-08-02 21:58 ` Tilman Schmidt
2008-08-02 23:12 ` Felipe Balbi [this message]
2008-08-03 0:45 ` Tilman Schmidt
2008-08-03 0:57 ` Felipe Balbi
2008-08-03 3:43 ` Greg KH
2008-08-03 9:11 ` Felipe Balbi
2008-08-03 21:10 ` Kamil Dzida
2008-08-01 19:04 ` Daniel Gimpelevich
2008-07-31 16:38 ` Greg KH
2008-07-31 21:34 ` Tilman Schmidt
2008-07-31 21:50 ` Greg KH
2008-07-31 22:55 ` Tilman Schmidt
2008-07-31 23:26 ` Felipe Balbi
2008-08-01 8:45 ` Tilman Schmidt
2008-08-01 8:50 ` Felipe Balbi
2008-08-01 8:58 ` Tilman Schmidt
2008-08-01 9:05 ` Felipe Balbi
2008-08-01 9:25 ` Tilman Schmidt
2008-08-01 8:45 ` Felipe Balbi
-- strict thread matches above, loose matches on Subject: below --
2008-07-29 9:01 Tilman Schmidt
2008-07-30 9:40 ` Andrew Morton
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=20080802231201.GB23361@frodo \
--to=me@felipebalbi.com \
--cc=eugen@debian.org \
--cc=linux-usb@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=tilman@imap.cc \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.