From mboxrd@z Thu Jan 1 00:00:00 1970 From: Brian Walker Date: Sat, 09 Jan 2010 14:33:39 -0500 Subject: [ath9k-devel] trouble with DWA-552 and ath9k In-Reply-To: <1263051508.2796.5.camel@ct> References: <4B2A5FA8.8060905@charter.net> <19242.62265.487757.695747@gargle.gargle.HOWL> <4B2AFC5D.1060001@charter.net> <19243.2224.974537.876295@gargle.gargle.HOWL> <4B39058A.6080108@charter.net> <1262033354.3002.11.camel@mj> <4B391DCB.6010500@charter.net> <1262035725.3002.23.camel@mj> <4B393739.9000601@charter.net> <20091229100250.xle1s7oai8ow08k8-cebfxv@webmail.spamcop.net> <4B3A8F7B.2050106@charter.net> <20091230011624.zygif55zaco8000s-cebfxv@webmail.spamcop.net> <4B436D94.4050304@charter.net> <19270.46529.788691.185819@gargle.gargle.HOWL> <4B489D63.9030305@charter.net> <1263051508.2796.5.camel@ct> Message-ID: <4B48DA13.1070309@charter.net> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: ath9k-devel@lists.ath9k.org On 01/09/2010 10:38 AM, Pavel Roskin wrote: > On Sat, 2010-01-09 at 10:14 -0500, Brian Walker wrote: > >> This is what I have in /etc/modprobe.d/local.conf (I run Fedora 11): >> >> options ath9k debug=0xffffffff >> >> In config.mk I have: >> >> CONFIG_ATH9K_DEBUG=y >> CONFIG_ATH9K_DEBUGFS=y >> >> Is there something else I need to do to get the debugging information >> you're interested in? >> >> Brian >> >> On 01/07/2010 11:34 PM, Sujith wrote: >> >>> Brian Walker wrote: >>> >>> >>>> Any update on getting this card working with the ath9k? >>>> >>>> >>> The logs that you posted earlier didn't contain debug information. >>> Can you make sure that you load the driver with debug=0x601 and >>> post the dmesg output on doing 'ifconfig wlan0 up' ? >>> > I think the quoted message is pretty clear. Maybe it would be better > that you write under the quoted text so that you can see what you have > quoted? > > debug=0xffffffff would likely produce too much information in the kernel > log, so please change it to 0x601 as you were asked. > Apologies for quoting after my messages. I will now quote before and then enter my response below the quotes. Forgive me, but I am still confused. The only reason I set the debug=0xffffffff is that debug=0x601 did not seem to produce any debugging information in dmesg (or /var/log/messages). Even so, there does not appear to be any debugging information in either place with the debugging set so high. Do I need to blacklist the ath9k module so it does not load during boot and then manually modprobe it? As I mentioned previously, if I rmmod ath9k, this shows in the kernel logs: ath9k 0000:00:0a.0: PCI INT A disabled ath9k: Driver unloaded Then when I try modprobe ath9k debug=0x601, this shows in the kernel logs: ath9k 0000:00:0a.0: failed to initialize device ath9k 0000:00:0a.0: PCI INT A disabled ath9k: probe of 0000:00:0a.0 failed with error -5 As one might imagine, it is quite frustrating to have to reboot just to load the ath9k module again. Brian