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 11 and Version 12 of StuckBeacon

Author:
Mister_X (IP: 0.0.0.0)
Timestamp:
02/12/06 23:42:00 (14 years ago)
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • StuckBeacon

    v11 v12  
    2020Stuck Beacons can often be the result of a mis-installation or mis-configuration. It's been reported that changing settings stopped the stuck beacon (which settings you ask:  the reporter said "I don't remember which setting stopped that").   
    2121 
    22 Another reporter using a D-link DWL-AG650 PCI card with drivers from CVS on 12/28/2005 encountered the SBP mostly when doing things that are network-intensive- RDesktop and VNC especially seem to trigger the problem. Watching a video recorded with MythTV induced the SBC and the video became choppy, though CPU idle was still over 90%. Downing the interface and rmmod ath_pci, sometimes helps, but not always, ie: got the SBP, downed the interface, removed the driver, re-inserted it, brought the interface back up, and that worked for another two hours. But after that, the SBP persisted through several down-remove-modprobe-up cycles.    
     22Another reporter using a D-link DWL-AG650 PCI card with drivers from CVS on 12/28/2005 encountered the SBP mostly when doing things that are network-intensive- RDesktop and VNC especially seem to trigger the problem. Watching a video recorded with MythTV induced the SBC and the video became choppy, though CPU idle was still over 90%. Downing the interface and rmmod ath_pci, sometimes helps, but not always, ie: got the SBP, downed the interface, removed the driver, re-inserted it, brought the interface back up, and that worked for another two hours. But after that, the SBP persisted through several down-remove-modprobe-up cycles.    
    2323 
    24 It appears that stuck beacon can be caused by wireless cards that have some sort of power saving feature, namely intel centrino (2200BG ) and equiv  cards. 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: http://support.intel.com/support/wireless/wlan/sb/cs-006205.htm 
     24It appears that stuck beacon can be caused by wireless cards that have some sort of power saving feature, namely intel centrino (2200BG ) and equivalent cards. 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: http://support.intel.com/support/wireless/wlan/sb/cs-006205.htm 
    2525 
    2626Here is a little perl script giving you the differences. Usage: store the code in a file, e.g. "madwifi.pl". Call it with  
    5151}}} 
    5252 
    53 i managed to cause stuckbeacon by changing channel while interface was up, to fix this change channel on startup before interface is up and it appears to be fine. 
     53I managed to cause stuckbeacon by changing channel while interface was up. To fix it, change channel on startup before interface is up and it appears to be fine. 
    5454 
    55 screenshot below 
     55Screenshot: 
    5656http://www.darktech.org.uk/stuckbeacon.jpg 
    5757