All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philipp Raich <philipp.raich@gmail.com>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] need help debugging/pinning down obscure freezes/hangs using AR9287
Date: Fri, 14 Oct 2011 12:23:12 +0200	[thread overview]
Message-ID: <4E980D90.80401@gmail.com> (raw)
In-Reply-To: <CAJ-Vmo=VH0PzSgLCKwRbDY5b7EDw9_iDHC1ws3W6Fb5gmBP61g@mail.gmail.com>

On 10/14/2011 03:23 AM, Adrian Chadd wrote:
> Right, I must've missed that. Then you have an AR9227, not an AR9287. :-)
>
> At this point I'm tempted to say "Try PCBsd 9.0 Beta3" (freebsd +
> desktop environment) - I believe the DVD image comes with a live
> system, so you can test things out. The ath/hal driver code is
> included by default in their system. Let me know if it hangs or not.
>
>
> Adrian
Apparently you are right, ar9227 is PCI and ar9287 is PCIe, according to 
a page related to "athn" in openBSD... GRR, just why do manufacturers 
have to be so close-fisted with their info on wireless adapters, it took 
me hours to find this information and I still don't know if it is 
correct. And Atheros itself has no info about the PCI-Variants of their 
chipsets on their public homepage...

Nevertheless, might this be the problem itself? Does ath9k detect the 
wrong chipset for my device? Or is there no difference for ath9k how to 
handle the PCI/PCIe variants?

I am right now downloading the Live-DVD of PCBsd, and will try it, but 
may I ask what the goal of this would be? Is there any point in testing 
a presumably different driver (I may tell you, I already tried windows, 
works like a charm...)? I mean, what if it works? What are we going to 
do with that information? Sorry my questioning of your advices, I just 
would like to know what we are trying to show/achieve.

Thanks,
Philipp
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.ath9k.org/pipermail/ath9k-devel/attachments/20111014/ae9aa2a1/attachment.htm 

  reply	other threads:[~2011-10-14 10:23 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-11 18:38 [ath9k-devel] need help debugging/pinning down obscure freezes/hangs using AR9287 Philipp Raich
2011-10-12  6:59 ` Mohammed Shafi
2011-10-12 12:21   ` Philipp Raich
2011-10-12 15:37     ` Mohammed Shafi
2011-10-12 19:19       ` Philipp Raich
2011-10-12 19:35         ` Ben Greear
2011-10-13 16:26           ` Philipp Raich
2011-10-13 17:04             ` Ben Greear
2011-10-13 19:32               ` Philipp Raich
2011-11-14 18:10                 ` Philipp Raich
2011-11-15  3:16                   ` Adrian Chadd
2011-10-12 13:53 ` Peter Stuge
2011-10-12 14:09   ` Mohammed Shafi
2011-10-12 14:56     ` Peter Stuge
2011-10-12 15:15       ` Mohammed Shafi
2011-10-12 15:35         ` Peter Stuge
2011-10-12 16:51           ` Felix Fietkau
2011-10-12 17:23             ` Peter Stuge
2011-10-12 18:36               ` Felix Fietkau
2011-10-13  0:42             ` Adrian Chadd
2011-10-12 15:29       ` Adrian Chadd
2011-10-12 16:01         ` Peter Stuge
2011-10-12 18:19           ` Luca Olivetti
2011-10-13  0:44 ` Adrian Chadd
2011-10-13 15:50   ` Philipp Raich
2011-10-14  1:23     ` Adrian Chadd
2011-10-14 10:23       ` Philipp Raich [this message]
2011-10-14 11:36         ` Adrian Chadd
  -- strict thread matches above, loose matches on Subject: below --
2011-12-26 22:46 Malcom Haak
2011-12-27  3:43 ` Adrian Chadd
2011-12-27  3:47   ` Malcom Haak

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=4E980D90.80401@gmail.com \
    --to=philipp.raich@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.