From: <mgreger@cinci.rr.com>
To: "Michał Kazior" <kazikcz@gmail.com>, mgreger@cinci.rr.com
Cc: Janusz Dziedzic <janusz.dziedzic@gmail.com>,
linux-wireless <linux-wireless@vger.kernel.org>,
sedat.dilek@gmail.com
Subject: Re: Atheros AR9462 - 5Ghz not working
Date: Fri, 15 Jun 2018 17:23:35 +0000 [thread overview]
Message-ID: <20180615172335.VSLI7.207164.root@dnvrco-web09> (raw)
In-Reply-To: <20180615165838.QFYTH.206966.root@dnvrco-web09>
---- mgreger@cinci.rr.com wrote:
>
> ---- "Michał Kazior" <kazikcz@gmail.com> wrote:
> > Your noise floor readout in survey dump is terribly bad for 5GHz. It
> > ain't stellar for 2.4GHz either but within reason nonetheless.
> >
> > Did you try using the card in a different device? I wonder if the
> > device you're trying to use it in has some sort of internal noise on
> > those frequencies and/or ath9k's ANI isn't able to deal with it.
> >
> >
> > Michał
> >
> > On 15 June 2018 at 15:31, <mgreger@cinci.rr.com> wrote:
>
>
> I did.
> I took it out of the Penguin-Z notebook and put it in a Dell XPS15 9560 running Windows 10. Only 2.4Ghz networks were visible from there as well. Not exactly apples-to-apples, but consistent results.
Could it be antenna related (in multiple devices)?
On wikidevi.com I see some M.2 cards listed with an antenna connector of U.FL and others with MHF4. I can't find anything describing the difference, if any. The connectors seemed to fit OK. Also, what's the deal with 'main' and 'aux' antenna connectors? I've seen people suggest swapping them has helped in some cases with poor signal, while others insist that it makes no difference. I have not tried swapping the connectors.
next prev parent reply other threads:[~2018-06-15 17:23 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-22 17:21 Atheros AR9462 - 5Ghz not working mgreger
2018-05-25 17:06 ` Sedat Dilek
2018-05-25 20:39 ` mgreger
2018-05-25 20:50 ` mgreger
2018-05-26 14:33 ` mgreger
2018-05-30 14:05 ` mgreger
2018-06-10 23:29 ` mgreger
2018-06-12 18:19 ` mgreger
2018-06-14 4:15 ` mgreger
2018-06-14 20:57 ` Janusz Dziedzic
2018-06-15 13:31 ` mgreger
2018-06-15 16:08 ` Michał Kazior
2018-06-15 16:58 ` mgreger
2018-06-15 17:23 ` mgreger [this message]
2018-06-17 10:08 ` Michał Kazior
2018-06-17 14:52 ` mgreger
2018-06-17 21:31 ` Tom Psyborg
2018-06-18 13:53 ` mgreger
2018-06-18 19:22 ` Arend van Spriel
2018-06-18 20:01 ` Martin Blumenstingl
2018-06-21 14:01 ` mgreger
2018-06-21 15:13 ` Tom Psyborg
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=20180615172335.VSLI7.207164.root@dnvrco-web09 \
--to=mgreger@cinci.rr.com \
--cc=janusz.dziedzic@gmail.com \
--cc=kazikcz@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=sedat.dilek@gmail.com \
/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