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 9 and Version 10 of DevDocs/AthDebug

Author:
mrenzmann (IP: 0.0.0.0)
Timestamp:
08/23/06 06:28:42 (15 years ago)
Comment:

Added toc; minor spelling and layout corrections; added reference to Paolo's {ath,80211}debug dialog wrapper

Legend:

Unmodified
Added
Removed
Modified
  • DevDocs/AthDebug

    v9 v10  
    1 = HOWTO use the debugging tools athdebug and 80211debug = 
     1[[PageOutline(2-4)]] 
    22 
    3 madwifi contains quite extensive debugging facilities, which are hidden to most people. The `tools/` directory contains two programs which are also installed by default, called `athdebug` and `80211debug`. These two programs can be used to control the amount of debugging output which appears in the kernel log (`dmesg` and `/var/log/messages` or `/var/log/kern.log` depending on the distribution).  
     3= How to use the debugging tools athdebug and 80211debug = 
    44 
    5 The reason why there are two separate programs is that one controls the debugging output from the device (`ath`) specific part and the other one for the generic (`80211`) part. Remember: The 802.11 stack used by madwifi (net80211) is derived from FreeBSD where it supports more wireless devices than just Atheros based. 
     5MadWifi contains quite extensive debugging facilities, which are hidden to most people. The `tools/` directory contains two programs which are also installed by default, called `athdebug` and `80211debug`. These two programs can be used to control the amount of debugging output which appears in the kernel log (`dmesg` and `/var/log/messages` or `/var/log/kern.log` depending on the distribution).  
     6 
     7The reason why there are two separate programs is that one controls the debugging output from the device (`ath`) specific part and the other one for the generic (`80211`) part. Remember: The 802.11 stack used by MadWifi (net80211) is derived from FreeBSD where it supports more wireless devices than just Atheros based. 
    68 
    79Both programs have the same user interface and basically work by setting a bitmap in the driver enabling or disabling debugging output from various subsystems. Both also take an optional parameter `-i device` (e.g. -i wifi1) which can be ommitted if you use wifi0. 
    4042rate          - the rate control modules 
    4143reset         - reset processing and inititalization 
     44 
    4245mode          - mode changes 
    4346beacon        - beacon handling 
    8689roam          - station mode roaming 
    8790}}} 
     91 
     92== Dialog wrapper == 
     93 
     94[wiki:UserDocs/Tools/ath+802_debug-wrapper] provides a shell script that implements a dialog interface to the debug tools, making it a lot easier for users to work with the debug tools. 
    8895 
    8996== Examples and Tips == 
    138145}}} 
    139146 
    140 === Performance Impact === 
     147== Performance Impact == 
    141148'''Attention:''' Enabling all debugging output on smaller systems can make them very slow and sometimes unresponsive. So it's usually better to only enable the output from the part you are interrested in.  
    142149 
    143 But sometimes you don't know in advance. So it might sometimes be useful to use script or write all commands in one line to enable debugging output, issue a short command and disable it again. E.g: 
     150But sometimes you don't know in advance. So it might sometimes be useful to use a script or write all commands in one line to enable debugging output, issue a short command and disable it again. E.g: 
    144151{{{ 
    145152athdebug 0xffffffff; iwpriv ath0 mode 1; athdebug 0x0;