Re: [Madwifi-devel] Stuck beacon problem: any progress?

[Jonas T <jon...@re...>]

There is progress.
I've written a dirty fix patch to temporarily cure the problem, it can be o=
btained from the madwifi FAQ.

One of the lead developers has also been able to reproduce the error and he=
nce has an upcomming sollution for it.

//Regards JT

-----Original Message-----
From: Daniel Swarbrick <da...@pr...>
To: mad...@li...
Date: Tue,  7 Dec 2004 17:04:13 +0100
Subject: [Madwifi-devel] Stuck beacon problem: any progress?

I've been running madwifi for about a year now with a Proxim Atheros-5212 b=
ased
PCI card in master mode. I'm currently using a CVS snapshot from around Apr=
il
04, with no problems.

Back in October I tried to update to a newer CVS to have a look at the WPA
stuff, and discovered that my system suffers from the infamous stuck beacon
problem. I had to roll back my driver to the April snapshot.

I'm running a 2.4.28 kernel, and would very much like to move to a 2.6 kern=
el -
but my current CVS snapshot is so old it doesn't compile cleanly with 2.6
kernels.... but I can't upgrade my CVS snapshot, because it will re-introdu=
ce
the SBP.

Is any progress being made on this issue? I'd be perfectly willing to help
debug, except that my server is about 16,000km away from me, and it would b=
e
rather uncool to hang that server. What I'm really curious about is why thi=
s
was never a problem with earlier CVS snapshots... Can someone shed light on=
 why
it seems to be an insurmountable problem, considering that it never used to=
 be?


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/
_______________________________________________
Madwifi-devel mailing list
Mad...@li...
https://lists.sourceforge.net/lists/listinfo/madwifi-devel