Driver debugging

[Tony Espy]

Dan Williams wrote:
> On Mon, 2007-07-23 at 09:00 -0700, Bill Moseley wrote:
>> I have new a Thinkpad T60p with an Atheros card running Ubuntu Feisty
>> and wpa_supplicant 0.5.7-0ubuntu2.
>>
>> A number of people have be posting on the NetworkManager list about
>> frequent disconnects (and reconnects).  We don't believe it's a real
>> signal drop out (I'm only a few feet from my AP and Linux (Sarge)
>> running two different wireless cards) and an iBook have no trouble.
>>
>> So, it was suggested on the NetworkManager list that we get some
>> wpa_supplicant debugging logs to see exactly what the connection is
>> being dropped.
> 
> No, not wpa_supplicant logs, but _driver_ logs.  From the madwifi kernel
> modules.  That's what's sending the disconnect events, and knowing why
> it's sending the disconnects is what we need to debug this further...

the following link describes the 80211debug and athdebug tools which 
allow you to control the debug messages generated by madwifi:

http://madwifi.org/wiki/DevDocs/AthDebug

in the past i've found that turning on 'auth' and 'assoc' with 
80211debug can help with tracking down disconnects.  you also might want 
to check out the following madwifi bug and associated patch:

http://madwifi.org/ticket/848

you also might want to move this thread to the madwifi-users email list...

good luck!
/tony
pepper computer