linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tilman Schmidt <tilman@imap.cc>
To: me@felipebalbi.com
Cc: 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, 03 Aug 2008 02:45:11 +0200	[thread overview]
Message-ID: <4894FF97.7040600@imap.cc> (raw)
In-Reply-To: <20080802231201.GB23361@frodo>

[-- Attachment #1: Type: text/plain, Size: 5605 bytes --]

On Sun, 3 Aug 2008 02:12:06 +0300, Felipe Balbi wrote:
> hmm... what does lsusb -v -d 057c:6201 reports to you ?

compaq:/home/ts # lsusb -vvd 057c:

Bus 002 Device 002: ID 057c:6201 AVM GmbH WLAN USB v1.1
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               2.00
  bDeviceClass          255 Vendor Specific Class
  bDeviceSubClass       255 Vendor Specific Subclass
  bDeviceProtocol       255 Vendor Specific Protocol
  bMaxPacketSize0        64
  idVendor           0x057c AVM GmbH
  idProduct          0x6201 WLAN USB v1.1
  bcdDevice            1.00
  iManufacturer           3 
  iProduct                2 
  iSerial                 1 TI964E1FA4C100TNETW
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength           32
    bNumInterfaces          1
    bConfigurationValue     1
    iConfiguration          0 
    bmAttributes         0x80
      (Bus Powered)
    MaxPower              500mA
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           2
      bInterfaceClass       255 Vendor Specific Class
      bInterfaceSubClass    255 Vendor Specific Subclass
      bInterfaceProtocol    255 Vendor Specific Protocol
      iInterface              0 
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x01  EP 1 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x82  EP 2 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0
Device Qualifier (for other device speed):
  bLength                10
  bDescriptorType         6
  bcdUSB               2.00
  bDeviceClass          224 Wireless
  bDeviceSubClass         1 Radio Frequency
  bDeviceProtocol         1 Bluetooth
  bMaxPacketSize0        64
  bNumConfigurations      0
Device Status:     0x0000
  (Bus Powered)
compaq:/home/ts # 

>> 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

compaq:/home/ts # iwconfig wlan0 essid MYESSID
compaq:/home/ts # iwconfig wlan0
wlan0     IEEE 802.11b+/g+  ESSID:"MYESSID"  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/100  Signal level=100/100  Noise level=100/100
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0

compaq:/home/ts # iwlist wlan0 scan
wlan0     No scan results

compaq:/home/ts # 

Next step would be running wpa_supplicant, because my WLAN uses WPA, but:

# wpa_supplicant -Dwext -iwlan0 -c/etc/wpa_supplicant/wpa_supplicant.conf

rapidly floods my console with messages

ioctl[SIOCSIWENCODEEXT]: Operation not supported
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys

and the syslog with

Aug  3 01:55:47 compaq kernel: get_mask 0x00000000, set_mask 0x00040000
Aug  3 01:55:47 compaq kernel: important setting has been changed. Need to update packet templates, too
Aug  3 01:55:47 compaq kernel: updating packet templates
Aug  3 01:55:47 compaq kernel: updating WEP key settings
Aug  3 01:55:47 compaq kernel: setting WEP key 0 as default
Aug  3 01:55:47 compaq kernel: acx_set_status(1):SCANNING
Aug  3 01:55:47 compaq kernel: start_scan: seems like previous scan is still running. Not starting anew. Please report
Aug  3 01:55:47 compaq kernel: get_mask 0x00000000, set_mask 0x00000000 - after update

until I hit ctrl/C.

# dhclient wlan0

just repeats

DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 5

a couple of times with increasing interval values and finally tells me

No DHCPOFFERS received.
No working leases in persistent database - sleeping.

> It's probably affected by timing as well. That driver sure needs some
> rework.

Yeah, looks like it. I posted a report to the project's Sourceforge
"ACX100 USB" forum, too.

Thanks,
Tilman


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 254 bytes --]

  reply	other threads:[~2008-08-03  0:45 UTC|newest]

Thread overview: 27+ 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
2008-08-03  0:45                   ` Tilman Schmidt [this message]
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

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=4894FF97.7040600@imap.cc \
    --to=tilman@imap.cc \
    --cc=eugen@debian.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=me@felipebalbi.com \
    /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;
as well as URLs for NNTP newsgroup(s).