[ath9k-devel] trouble with DWA-552 and ath9k

[Brian Walker <walkerbm@charter.net>]

Thanks for that information! I'm recompiling ath9k with 
CONFIG_ATH9K_DEBUG=y and CONFIG_ATH9K_DEBUGFS=y. After that I will 
reboot and load ath9k with debug=0x600. Looking at 
http://linuxwireless.org/en/users/Drivers/ath9k/debug for information on 
debugging the ath9k driver, is there anything of particular interest in 
/sys/kernel/debug/ath9k that I should post?

Brian

On 12/17/2009 11:44 PM, Sujith wrote:
> Brian Walker wrote:
>    
>> Hi. In config.mk I find no option named CONFIG_ATH9K_DEBUG, but there is
>> one named CONFIG_ATH9K_DEBUGFS. Also, as I tried to include in a
>> followup to my original post, the output from lspci -vnn is:
>>      
> Indeed, the option is missing.
> Adding the line "CONFIG_ATH_DEBUG=y" and "CONFIG_ATH9K_DEBUGFS=y" to config.mk
> and recompiling should do it.
>
>    
>> 00:0a.0 Network controller [0280]: Atheros Communications Inc. AR922X
>> Wireless Network Adapter [168c:0029] (rev 01)
>>       Subsystem: D-Link System Inc Device [1186:3a7a]
>>       Flags: 66MHz, medium devsel, IRQ 5
>>       [virtual] Memory at f8040000 (32-bit, non-prefetchable) [size=64K]
>>       Capabilities: [44] Power Management version 2
>>       Kernel driver in use: ath9k
>>       Kernel modules: ath9k
>>
>> The 168c:0029 seems pretty standard for an Atheros wireless N adapter,
>> but I wonder if the 1186:3a7a is a new revision of this card and is
>> perhaps not 100% supported yet?
>>      
> That can be determined by looking at the kernel log on loading the driver
> with 'debug=0x600'.
>
> Sujith
>