RE: Problems with chipset AT76C505a

Hi Steve,

You might find that it isn't actually a driver problem.
When I wrote the international roaming and pseudo-monitor mode extensions to
this driver I was (un)plugging the adapter into/from my USB port more times
than I could possibly guess! Then I started seeing all sorts of USB
failures/timeouts...

Turns out that through good 'ol ware-n-tear caused the multi-layered PCB
actually to start to fail (I'm assuming some of the tracks broke). I could
still make it work by bending it in certain directions. In the end I just
got a new one and connected to the supplied extension cord and haven't
disconnected it from the cord since (so (un)plugging happens with the more
robust cord connector).

Try using the extension cord and pile books on the adapter-side plug to keep
the whole thing as still as possible. Then try to go about your business,
without even bumping the table!

Good luck,
Balint

> -----Original Message-----
> From: [email protected] [mailto:at76c503a-user-
> [email protected]] On Behalf Of Steve MOREAU
> Sent: Friday, 1 April 2005 6:47 PM
> To: [email protected]
> Subject: [at76c503a-user] Problems with chipset AT76C505a
> 
> Hello,
>  Using the Berlios driver with Fedroa Core 3, I experiment some problems I
> didn't have before. Actually, the driver worked for some days, even at
> boot (automatically detected thanks to ifcfg-wlan0 script), and a green
> LED switched on to say the card was scanning and working.
>  But now, this LED doesn't want to come back and it's impossible to join
> the network. I have a ping response on my card (it's a internal USB card)
> but tcpdump on wlan0 say nothing pass.
>  Here is the error I've got when I plugged the card :
> 
> ip_tables: (C) 2000-2002 Netfilter core team
> /drivers/wifi/at76c503a/at76c503.c: wlan0: tx timeout.
> usb 3-2: events/0 timed out on ep0in
> /drivers/wifi/at76c503a/at76c503.c: wlan0: get_cmd_status failed: -110
> /drivers/wifi/at76c503a/at76c503.c: wlan0: tx timeout.
> /drivers/wifi/at76c503a/at76c503.c: wlan0: tx timeout.
> /drivers/wifi/at76c503a/at76c503.c: wlan0: tx timeout.
> usb 3-2: events/0 timed out on ep0out
> /drivers/wifi/at76c503a/at76c503.c: wlan0: set_card_command(CMD_RADIO)
> failed: -110
> /drivers/wifi/at76c503a/at76c503.c: wlan0: tx timeout.
> /drivers/wifi/at76c503a/at76c503.c: wlan0: tx timeout.
> usb 3-2: events/0 timed out on ep0out
> /drivers/wifi/at76c503a/at76c503.c: wlan0: set_mib (preamble) failed:
> -110
> usb 3-2: events/0 timed out on ep0out
> /drivers/wifi/at76c503a/at76c503.c: wlan0: kevent: start_scan failed
> with -110
> 
> [root@localhost ~]# lsmod | grep at
> at76c505a_rfmd2958     40964  0
> at76c503               84704  1 at76c505a_rfmd2958
> at76_usbdfu             5508  1 at76c503
> battery                 9285  0
> 
> [root@localhost ~]# iptables -L
> ip_tables: (C) 2000-2002 Netfilter core team
> Chain INPUT (policy ACCEPT)
> target     prot opt source               destination
> 
> Chain FORWARD (policy ACCEPT)
> target     prot opt source               destination
> 
> Chain OUTPUT (policy ACCEPT)
> target     prot opt source               destination
> 
> I don't remember having done something on my network configuration so I
> don't understand this regression :-(
> Did somone meet the same problem ? Did someone have a clue ?
> Thanks
> Steve
> 
> _______________________________________________
> at76c503a-user mailing list
> [email protected]
> http://lists.berlios.de/mailman/listinfo/at76c503a-user