Re: [Madwifi-users] hardware error; resetting
Status: Beta
Brought to you by:
otaku
From: <ce...@co...> - 2003-11-04 19:26:30
|
It is indeed a broadcom based AP (Linksys)... Thanks for the heads-up... /mike Tom Marshall wrote: >I have the same issue with my Linksys WRT54G and I think it's an .11g >interop problem between madwifi and Broadcom. Is your AP based on a >Broadcom chip? If it's a WRT54G or WAP54G, I'm pretty sure it is. Nobody >seems to have found the cause, or even whether the problem is with the AP or >the madwifi driver. I suspect the driver because it seems to work fine when >I reboot into Win32, but that's not hard evidence. It could be that the >Broadcom driver is doing something that's out of spec and the madwifi driver >is less forgiving than the Win32 driver. > >I've worked around the issue temporarily by forcing my madwifi driver into >.11b mode. It's not an optimal solution but it works. > >On Sun, Nov 02, 2003 at 05:29:07PM -0500, ce...@co... wrote: > >>2 issues: >> >>1. As posted earlier, I am getting thousands of these after a day or so of >>running... Nothing obvious to me in the logs as I don't have chip docs to >>decipher the register dumps posted in my prior email. >> >>2. the hardware reset appears to be missing something as it eventually >>does nothing to alleviate the "hardware error" where removing the module, >>reinserting it does... >> >>So, at this point I have a cron job running once an hour to do just that... >> >>This has drastically reduced the number of errors reported which tells me >>that something is missing in the reset sequence that the module load >>toggles... >> >>Clearly it is a nasty hack and even more intrusive on my DHCP based laptop >>than the static IP desktop with NFS mounts over wirelss (yes, I know I am >>asking for trouble - but hey where is the fun in just surfing...) >> >>I have seen only one other post regarding "hardware error; resetting" in >>the bug list... Is this something unique to Linksys/Orinoco? or have I >>missed an earlier discussion regarding a work-around? >> >>So far I have tried the following configs with the same result: >>Kernel 2.4.19- `22 >>RH 7.2/7.3 >>desktop (amd) >>laptop (dell PIII) >>PCMCIA (carbus) >>PCI >>Linksys cards in all >>madwifi: >>ath_hal: 0.9.5.11 BETA (Sam Leffler <sa...@er...>) >>wlan: 0.7.1.1 BETA (Sam Leffler <sa...@er...>) >>ath_pci: 0.8.3.2 BETA (Sam Leffler <sa...@er...>) >> >>Perhaps, interesting things about my setup is potential 2.4GHz >>interference sources: >>1. Wireless phone >>2. 802.11b Access point hardcoded to different channel >>3. linksys 11G hard coded to 11G and seperate channel. >> >>The "b" access point is needed as linksys router locks up with mixed 11b >>and 11G access - I should point out that although I saw the above behavior >>prior to setting up old 11b for my "legacy" devices, I recently discovered >>my neighbor's 11b router can be seen from my house so I have always and >>will always have 11b "interference". >> >>Happy to hack and provide any additional debug needed, just need a little >>guidance as to either where I can find Spec/Docs for the chip to decipher >>reg dumps or what additional info is needed to debug this... >> >>Any opinions and/or advice on locking cards themselvs into 11G as I have >>the router? >> >>/mike >> >> >>------------------------------------------------------- >>This SF.net email is sponsored by: SF.net Giveback Program. >>Does SourceForge.net help you be more productive? Does it >>help you create better code? SHARE THE LOVE, and help us help >>YOU! Click Here: http://sourceforge.net/donate/ >>_______________________________________________ >>Madwifi-users mailing list >>Mad...@li... >>https://lists.sourceforge.net/lists/listinfo/madwifi-users > > |