Re: Netgear MA101 Rev. A dies after minutes.
Joerg Albert <[email protected]>
| Newsgroups | gmane.linux.drivers.at76c503a.user |
|---|---|
| Message-ID | <Pine.LNX.4.56.0402262337070.675@invb> |
Hi, On Thu, 26 Feb 2004, Chaffinch wrote: > I having trouble with an MA101 Rev. A under 2.4.20 Gentoo Linux. I can get a > connection in ad-hoc mode and all seems fine but after a couple of minutes or > less the connection seems to die. I have looked through the mailing archives > and see there was a similiar problem from last April, only with a rev B. At > the time there didn't seem a resolution. > > I took the latest CVS snapshot to make sure I was up to date, firmware is > 0.90.0 (can this be updated?). I have looked through the archives and tried > all the tricks (more debug etc) but get nothing useful. there is no newer fw version for Intersil radio chipsets than 0.90.0-44, as Atmel ceased to support them. What's the peer device? How do you recognize that the link is dead? How can you recover: - restart the driver "ifconfig wlan0 down; ifconfig wlan0 up" - re-plug the device If the link is dead, does the peer still see beacons from the MA101A? Does "iwpriv wlan0 set_debug -1" show anything on the MA101's side in the syslog, apart from the wlan0: PRIV_IOCTL_SET_DEBUG input 3: -1 -> xffffffff wlan0: PRIV_IOCTL_SET_DEBUG old 0x.... new 0xfffffff wlan0: netif running .. queue_stopped .. carrier_ok .. (what are the values in the last line) ? If you can't even see these lines, please check your /etc/syslog.conf for the destination of kern.debug messages. /Jörg