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 .
Version 7 (modified by anonymous, 14 years ago)

The Infamous Stuck Beacon Problem

This page, more than most, is a work-in-progress. If you have any detailed experience with the Stuck Beacon, please suffix it here.

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 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.

The 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.

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. 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.

watch -n 1 'cat /proc/interrupts | grep wifi0'

I encounter the SBP mostly when doing things that are network-intensive- RDesktop and VNC especially seem to trigger the problem. It does seem interrupt-related- I was watching a video recorded with MythTV today when it happened, and the video became choppy, though CPU idle was still over 90%. If I down the interface and rmmod ath_pci, that sometimes helps, but not always. Today, I encoutered the SBP, downed the interface, removed the driver, re-inserted it, brought the interface back up, and was able to work for another two hours. But after that, the SBP persisted through several down-remove-modprobe-up cycles, and I ended up going back to wired.

I should mention I'm using a D-link DWL-AG650 PCI card with drivers from CVS on 12/28/2005 in master mode as my access point, and an Atheros AR5001X Mini-PCI card in my laptop with drivers from 9/21/2005 as a client. I've only ever seen the SBP on my access point, never the laptop.

Perhaps someone could post debugging procedures, and where to send debug data to on this page?

it appears that stuck beacon can be caused mostly by wireless cards that have some sort of power saving feature, namely intel centrino (2200BG ) and equiv cards. this causes stuck beacon to appear, to fix this, turn the card out of power saving mode in the control panel, this may or may not fix the problem, but appeared to work for me. uptime is around 10+days with latest madwifi drivers.

more information specific to intel centrino laptops can be found here: