From mboxrd@z Thu Jan 1 00:00:00 1970 From: Philipp Raich Date: Fri, 14 Oct 2011 12:23:12 +0200 Subject: [ath9k-devel] need help debugging/pinning down obscure freezes/hangs using AR9287 In-Reply-To: References: <8E4915FC-90CA-46C6-B15D-BFFC3037BA22@gmail.com> Message-ID: <4E980D90.80401@gmail.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: ath9k-devel@lists.ath9k.org 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