Historical ath9k-devel archives
 help / color / mirror / Atom feed
From: Bertrand Marc <beberking@gmail.com>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] Complete freeze when scanning
Date: Sun, 02 Jun 2013 22:50:49 +0200	[thread overview]
Message-ID: <51ABB029.2050802@gmail.com> (raw)

Dear ath9k maintainers,

I recently bought a TP-link WN751ND and I can't get it to work on my
linux box (Debian Wheezy, with a 3.2 kernel). I tried with the last
stable version of compat-drivers without success.

Here is what I do: I load the ath9k module and bring up the device but
as soon as I try to scan for networks (iw dev wlan0 scan), the system
completely freezes and I need to hard reboot.

Could you help me to get this device working ? I can provide any
information you need and try any version of compat-drivers. The computer
is very old, so I won't be able to compile a whole kernel unfortunately.

You'll find attached the output of lspci -vvvxxxx and a syslog dump just
before the freeze (with debug=0xffffffff option passed to ath9k). I
tried with netconsole, but nothing about ath9k came up. I also tried to
stop network-manager, it doesn't help as NM doesn't managed the card
anyway so you can safely ignore NM messages in syslog.

I don't know if it's relevant, but lspci thinks the chipset is a AR9227
but in syslog it says AR9287... The device is a cheap, single antenna
PCI card (not PCIexpress).

It might be interesting to note that with a live version of xubuntu
13.04 (I forgot the kernel version), NM was able to show me a list of
the networks right before it froze.

For the record, the device is working on Windows, so it is not broken.

Thanks,
Bertrand
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: lspci
Url: http://lists.ath9k.org/pipermail/ath9k-devel/attachments/20130602/53f9b749/attachment-0002.txt 
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: syslog
Url: http://lists.ath9k.org/pipermail/ath9k-devel/attachments/20130602/53f9b749/attachment-0003.txt 

                 reply	other threads:[~2013-06-02 20:50 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=51ABB029.2050802@gmail.com \
    --to=beberking@gmail.com \
    --cc=ath9k-devel@lists.ath9k.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox