All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Sune Mølgaard" <sune@molgaard.org>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] ath9k flaky in 3.6(.x)
Date: Tue, 16 Oct 2012 22:36:42 +0200	[thread overview]
Message-ID: <507DC55A.1060507@molgaard.org> (raw)
In-Reply-To: <20121014184429.2967.qmail@stuge.se>

Peter Stuge wrote:
> Sune M?lgaard wrote:
>> I'm hoping for someone to say "this is a known problem - we are
>> working on it"
>
> Forget it. You will also not really get any help with debugging. If
> you can find, and ideally prove, a regression then developers will
> likely look into the problem.
>
> If you perceive and can demonstrate a problem, and complain loudly,
> then developers will attempt to reproduce the problem in a lab, but
> that is of course absolutely useless.

Behaviour seems erratic, but without any clear cause - have temporarily 
switched to USB dongle that I remembered I had lying around...

>> 08:01.0 Network controller: Atheros Communications Inc.
>>    AR922X Wireless Network Adapter (rev 01)
>
> This is quite old hardware by now. The driver is supposed to work
> well also with this hardware, but in practise it has never for me.
>
> I have a feeling that the AR922x PCI silicon is not so great, and
> that it causes some of the problems. Perhaps the driver could work
> around them, but I'm not sure if it does.

That could very well be true. Would you happen to know a resource for 
finding consumer-level hardware with specific (new) chips?

>
> When dealing with this kernel driver your best chances at any kind of
> success is to use the hardware that developers currently work on.
> Those code paths are actively tested, improved, and debugged. Of
> course there is a small complication here; since the developers work
> on the driver before the hardware is made available on the market.
>
> At the moment I would not use anything older than AR9380 with the
> ath9k driver.
>
>
> I would suggest that you give FreeBSD a go on your laptop. Adrian is
> the author of that driver, it is not a copypaste of the ath9k, so it
> may work better or simply differently. I believe it supports your
> card. You obviously have to be open to trying out FreeBSD for that.

I'm not opposed to FreeBSD per se, but I do like me my Linux, so if you, 
or anyone else can answer my questions above, I'll buy a newer card.

>
>
> //Peter
> _______________________________________________
> ath9k-devel mailing list
> ath9k-devel at lists.ath9k.org
> https://lists.ath9k.org/mailman/listinfo/ath9k-devel
>

Thank you for answering.

Best regards,

Sune M?lgaard

-- 
No trees were harmed in the transmission of this email but trillions of 
electrons were excited to participate.

  reply	other threads:[~2012-10-16 20:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-13 17:35 [ath9k-devel] ath9k flaky in 3.6(.x) Sune Mølgaard
2012-10-14  4:41 ` Adrian Chadd
2012-10-14 18:44 ` Peter Stuge
2012-10-16 20:36   ` Sune Mølgaard [this message]
2012-10-18  4:32 ` Sujith Manoharan

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=507DC55A.1060507@molgaard.org \
    --to=sune@molgaard.org \
    --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.