Please note: This project is no longer active. The website is kept online for historic purposes only.
If you´re looking for a Linux driver for your Atheros WLAN device, you should continue here .

Changes between Version 3 and Version 4 of StuckBeacon

Author:
anonymous (IP: 0.0.0.0)
Timestamp:
12/09/05 17:00:46 (14 years ago)
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • StuckBeacon

    v3 v4  
    1 = The infamous Stuck Beacon Problem = 
     1= The Infamous Stuck Beacon Problem = 
    22 
     3''This page, more than most, is a work-in-progress. If you have any detailed experience with the Stuck Beacon, please suffix it here.'' 
    34 
    4 The Stuck Beacon Problem (SBP) is an intermittant but severe problem for some users.  It has been around for a while, but has yet to be resolved.  Please help collect and report data on this bug be suffixing your experience to this page.  Since no one yet knows the basis for the problem, the meaures to report here will be refined over time.  Please read on for more hints. 
     5The Stuck Beacon Problem (SBP) is an intermittant but severe problem for some users.  It has been around for a while, but has yet to be resolved.  Please help collect and report data on this bug by suffixing your experience to this page.  Since no one yet knows the basis for the problem, the meaures to report here will be refined over time.  Please read on for more hints. 
     6 
    57 
    68The SBP is generally associated with a reduction in performance.  Data transfer rates drop.  Data may stop moving all together.  You may get a 'Stuck Beacon' message. 
    79 
    8 Anecdotal evidence suggests that the SBP occurs to varying degrees, and only the most severe are reported as 'Stuck Beacon'.  One of the measures that can indicate the problem is an acceleration in the card's hardware interrupt rate.  To watch the accumulation of interrupts on '''wifi0''', key in the folowing line from a console.  Substitute your interface name for '''wifi0''':  in the 'old' code, typically that is '''ath0''', and in the 'NG' code, the name of the base device, typically '''wifi0'''. 
     10Anecdotal evidence suggests that the SBP occurs to varying degrees, and only the most severe are reported as 'Stuck Beacon'.   
     11 
     12One of the measures that can indicate the problem is an ''acceleration'' in the card's hardware interrupt rate.  To watch the accumulation of interrupts on '''wifi0''', key in the folowing line from a console.  Substitute your interface name for '''wifi0''':  in the 'old' code, typically that is '''ath0''', and in the 'NG' code, the name of the base device, typically '''wifi0'''.  If the accumulation rate accelerates significantly, you may be heading towards a stuck beacon.  NB:  the count shown below will increase, and that is normal.  Accelerated rates are the issue. 
    913 
    1014 watch -n 1 'cat /proc/interrupts | grep wifi0'