From: Ray Lehtiniemi <rayl@ma...> - 2004-03-20 19:11:40
i'm seeing some weird problem with my wireless 802.11a setup. every
so often, i see this in my syslog:
Mar 20 11:36:03 ray kernel: ath0: hardware error; resetting
at this point, my wireless link is toast and i must power cycle the
access point to get things running again. on the client side, iwconfig
reports that the card is scanning all channels, finding the AP, then
after a few seconds the AP MAC reverts to all ff's, it scans all channels,
finds the AP again, and repeats this in a loop until i power cycle the
i am using suse linux 8.2 with athlon kernel on the client. modules are
Mar 14 20:23:22 ray kernel: ath_hal: 0.9.6.11
Mar 14 20:23:22 ray kernel: wlan: 0.7.3.1 BETA
Mar 14 20:23:22 ray kernel: ath_pci: 0.8.5.1 BETA
the client is using SMC 2735W cardbus adapter. lspci -v reports the
02:00.0 Ethernet controller: Unknown device 168c:0007 (rev 01)
Subsystem: Unknown device 168c:0007
Flags: bus master, medium devsel, latency 168, IRQ 9
Memory at 20000000 (32-bit, non-prefetchable) [size=64K]
Capabilities:  Power Management version 2
i'm using an el-cheapo ($30 CDN) netgear HE102 access point from tiger
direct, which i'm pretty sure is a refurb or something similar, so
hardware issues are definitely not out of the question... i peeled
open another identical netgear AP, and it seems to be using a 5210 chip
as well, not sure of the revision.
any ideas what i might be doing wrong here?
Ray L <rayl@...>
> i'm using an el-cheapo ($30 CDN) netgear HE102 access
> point from tiger
> direct, which i'm pretty sure is a refurb or something
> similar, so
> hardware issues are definitely not out of the question...
> i peeled
> open another identical netgear AP, and it seems to be
> using a 5210 chip
> as well, not sure of the revision.
I had an HE102 for awhile and I saw the same issues. The
AP just quits working right until its rebooted. I think
this is a design flaw, and is probably the reason why they
are so cheap these days. I have tested a Nortel a/b AP
and a Proxim A AP and they both worked great with MADWIFI.
One thing I noted was that I had issues with the HE102
even under windows, and using several different 802.11A
cards, all based on the Atheros chipset the problems where
Hope this helps,
Get latest updates about Open Source Projects, Conferences and News.