Re: Problems with Netgear MA101

Joerg Albert <[email protected]>
Newsgroups gmane.linux.drivers.at76c503a.user
Message-ID <Pine.LNX.4.56.0407170009060.1427@invb>
Hi Christoph,

On Wed, 14 Jul 2004, Christoph Nickel wrote:

> First I see no difference between setting the debug level 0x180003 or 0x000003.
> Where is the information why the bss don't match (DBG 0x080000)?

The BSS does match in your case, it was chosen by find_matching_bss
(non-NULL return value), but the problem occured later (with the auth_req ?).

> Jul 14 22:27:40 harley kernel: at76c503.c: 0xc9d468c0: bssid
>  00:30:ab:22:aa:94 channel 6 ssid Funknetz (46756E6B6E65747A) capa x001$
> Jul 14 22:27:40 harley kernel: at76c503.c: wlan0: state 1 -> 6 (JOINING)
> Jul 14 22:27:40 harley kernel: at76c503.c: wlan0 find_matching_bss:
>  returned c9d468c0
> Jul 14 22:27:40 harley kernel: at76c503.c: wlan0 join addr
>  00:30:ab:22:aa:94 ssid Funknetz type 2 ch 6 timeout 2000

Please check that the auth alg. (open-system or shared key) is the
same in the client driver and the access point.
You may set the debug level to 0x180243 to see the tx/rx management
packets.

> Second, after disconnecting the device there seems no way to reactivate it.
> In the following log message the device was unplugged at 21:56:50 and
> reconnectet at 22:21:34 but not unplugged again.
> Jul 14 21:56:50 harley kernel: usb.c: USB disconnect on device 00:07.2-2 address 3
> Jul 14 21:56:50 harley kernel: at76c503-rfmd.c: wlan0 disconnected
> Jul 14 22:21:34 harley kernel: hub.c: new USB device 00:07.2-2, assigned address 4
> Jul 14 22:21:34 harley kernel: usbdfu.c: Downloading firmware for USB device 4...
> Jul 14 22:21:36 harley kernel: usb.c: USB disconnect on device 00:07.2-2 address 4

Sorry, I've no idea where the last disconnect comes from. Please retry and
set the debug output to max. (-1) just before you unplug the device. This
may reveal in which state the second disconnect happens.

/Jörg
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.