From mboxrd@z Thu Jan 1 00:00:00 1970 From: Sujith Date: Fri, 18 Dec 2009 10:14:32 +0530 Subject: [ath9k-devel] trouble with DWA-552 and ath9k In-Reply-To: <4B2AFC5D.1060001@charter.net> References: <4B2A5FA8.8060905@charter.net> <19242.62265.487757.695747@gargle.gargle.HOWL> <4B2AFC5D.1060001@charter.net> Message-ID: <19243.2224.974537.876295@gargle.gargle.HOWL> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: ath9k-devel@lists.ath9k.org 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