linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: Adrian Chadd <adrian@freebsd.org>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: Looking for 3x3 Atheros NICs using ath9k driver.
Date: Tue, 10 May 2011 13:51:35 -0700	[thread overview]
Message-ID: <4DC9A557.9050405@candelatech.com> (raw)
In-Reply-To: <BANLkTimtRz8SMTRnn57CUgkudJ6=_vK+kw@mail.gmail.com>

On 05/09/2011 07:21 PM, Adrian Chadd wrote:
> On 10 May 2011 03:05, Ben Greear<greearb@candelatech.com>  wrote:
>
>> The NIC is still showing up funky on the other system (Atom), even with the
>> same 39-rc6+ kernel.
>>
>> This NIC is reliably showing up wrong on in this system, and the other
>> is reliably showing up well, so I think the problem must be with
>> the NIC or perhaps the ath9k driver.
>>
> When you say "other NIC", you mean "BC1A" revision, rather than "AC1E" ?
>
>> If anyone has any suggestions for how to debug this further, I'm
>> interested...
>
> Can you try (much) earlier kernels? Ignore ath9k; ath9k shouldn't be
> needed for the card device id to be setup on PCI bus reset or whenever
> specifically it happens.

I tried a stock F14 .35 kernel, same problem.

I tried booting a .29 kernel, but F14 won't boot
on so old of a kernel.

Current plan is to just stick it in one of the VIA systems
that it functions in and use it for testing..and never buy any
more of those SR71-A NICs.

The sparklan 127N 3x3 pci-e seems to be working very well, so
I plan to start using them instead.

Thanks,
Ben


-- 
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc  http://www.candelatech.com


  reply	other threads:[~2011-05-10 20:51 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-02 20:51 Looking for 3x3 Atheros NICs using ath9k driver Ben Greear
2011-05-02 21:35 ` Brian Prodoehl
2011-05-02 22:00 ` Pat Erley
2011-05-02 22:19   ` Ben Greear
2011-05-03  6:13 ` Adrian Chadd
2011-05-03  9:39   ` Roberto Riggio
2011-05-03 10:39     ` Adrian Chadd
2011-05-03 16:36   ` Ben Greear
2011-05-03 18:00   ` Ben Greear
2011-05-04 16:16     ` Adrian Chadd
2011-05-04 16:24       ` Ben Greear
2011-05-06 22:53         ` Ben Greear
2011-05-07  2:31           ` Adrian Chadd
2011-05-07  3:42             ` Ben Greear
2011-05-07  4:56               ` Adrian Chadd
2011-05-09 19:05           ` Ben Greear
2011-05-10  2:21             ` Adrian Chadd
2011-05-10 20:51               ` Ben Greear [this message]
2011-05-11  2:11                 ` Adrian Chadd
2011-05-12 18:18                 ` Ben Greear

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=4DC9A557.9050405@candelatech.com \
    --to=greearb@candelatech.com \
    --cc=adrian@freebsd.org \
    --cc=linux-wireless@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).