Linux wireless drivers development
 help / color / mirror / Atom feed
From: <mgreger@cinci.rr.com>
To: Janusz Dziedzic <janusz.dziedzic@gmail.com>
Cc: linux-wireless <linux-wireless@vger.kernel.org>, sedat.dilek@gmail.com
Subject: Re: Atheros AR9462 - 5Ghz not working
Date: Fri, 15 Jun 2018 13:31:02 +0000	[thread overview]
Message-ID: <20180615133102.N4IRI.135706.root@dnvrco-web10> (raw)
In-Reply-To: <CAFED-jn2jtR+9cdEzgKzzJgzNip=Sdh1DwdV4uW2tjFHWGCQiw@mail.gmail.com>


---- Janusz Dziedzic <janusz.dziedzic@gmail.com> wrote: 
> 2018-06-14 6:15 GMT+02:00  <mgreger@cinci.rr.com>:
> >
> > ---- mgreger@cinci.rr.com wrote:
> >>
> >> ---- mgreger@cinci.rr.com wrote:
> >> >
> >> > ---- mgreger@cinci.rr.com wrote:
> >> > >
> >> > > ---- Sedat Dilek <sedat.dilek@gmail.com> wrote:
> >> > > > On Tue, May 22, 2018 at 7:21 PM,  <mgreger@cinci.rr.com> wrote:
> >> > > > > I've run out of ideas and am hoping someone here can help.
> >> > > > >
> >> > > > > All I want to do is connect a client to my 5Ghz network.
> >> > > > >
> >> > > > > My client:
> >> > > > >   OS is Debian stable "Stretch" with sysvinit instead of systemd
> >> > > > >   Atheros AR9462 (World roaming 0x64 regdomain in EEPROM)
> >> > > > >   "iw reg set US"
> >> > > > >   "iw list" shows both 2.4Ghz and 5Ghz bands available.
> >> > > > >   "iw wlp3s0 survey dump" shows received traffic on 5Ghz bands.
> >> > > > >
> >> > > > > There are oodles of 5Ghz AP's within range, but scans (including passive scans) reveal only 2.4Ghz networks. My only guess was that it won't transmit due to regulatory requirements, but I cannot make it work.
> >> > > > >
> >> > > > > What I've tried:
> >> > > > >   Running with and without CRDA
> >> > > > >   Running latest mainline kernel
> >> > > > >   Hacking around on the ath9k driver and nl80211 to remove all regulatory enforcement.
> >> > > > >
> >> > > > > Nothing works and I'm pulling my hair out. Any help would be greatly appreciated.
> >> > > >
> >> > > > Hi,
> >> > > >
> >> > > > I try to give some initial help.
> >> > > >
> >> > > > The linux-wireless driver is supported by ath9k driver see [1] and [2].
> >> > > >
> >> > > > Unfortunately, you have not sent any log-files at least your dmesg-log.
> >> > > > No output of the above userspace commands or userspace-tools versions.
> >> > > > No information to VendorID/ProductID (PCI, USB, whatever).
> >> > > > It's not clear to me if this is a kernelspace (ath9k-driver) or
> >> > > > userspace (CRDA/regulatory) problem.
> >> > > > How should someone help you effectively?
> >> > > >
> >> > > > The linux-wireless wiki has somne informations on how to debug
> >> > > > Atheros/Qualcomm ath9k-driver, see [3].
> >> > > >
> >> > > > As a debianist I say try Linux v4.16 Debian packages from
> >> > > > stretch-backports (and maybe a higher version of wireless-regdb).
> >> > > >
> >> > > > Try to ask questions the smart way [4] :-).
> >> > > >
> >> > > > Hope this helps.
> >> > > >
> >> > > > Regards,
> >> > > > - Sedat -
> >> > > >
> >> > > > [1] https://wireless.wiki.kernel.org/en/users/drivers/ath9k
> >> > > > [2] https://wireless.wiki.kernel.org/en/users/drivers/ath9k/devices
> >> > > > [3] https://wireless.wiki.kernel.org/en/users/drivers/ath9k/debug
> >> > > > [4] http://www.catb.org/esr/faqs/smart-questions.html
> >> > >
> >> > >
> >> > > I have also built the latest wireless-regdb and crda, but it made no difference.
> >> >
> >> >
> >> >
> >> > Did any of the information I posted point towards a cause?
> >>
> >>
> >> Also, I'll gladly send one of these adapters to someone with ath9k experience if they suspect they can make it work.
> >> Just message me.   :)
> >
> >
> > I'm surprised at the apparent lack of interest in this by anybody whatsoever.
> >
> > Are there any other M.2 cards (both A and E keyed) on the market that support dual band with a fully open driver and requiring no proprietary firmware?
> >
> > Maybe it was too good to be true and there is no such thing?
> >
> >
> 
> Seems, pcie version works fine:
> root@test4:~# lspci |grep Atheros
> 01:00.0 Network controller: Qualcomm Atheros AR9462 Wireless Network
> Adapter (rev 01)
> root@test4:~# iw wlp1s0 scan|grep "freq: 5"
>     freq: 5180
>     freq: 5180
>     freq: 5180
>     freq: 5220
>     freq: 5220
>     freq: 5220
>     freq: 5220
>     freq: 5220
>     freq: 5620
>     freq: 5745
>     freq: 5785
>     freq: 5785
>     freq: 5745
>     freq: 5785
>     freq: 5785
>     freq: 5785
>     freq: 5200
>     freq: 5200
>     freq: 5220
>     freq: 5220
>     freq: 5785
>     freq: 5180
>     freq: 5220
>     freq: 5220
>     freq: 5220
>     freq: 5220
>     freq: 5220
>     freq: 5220
>     freq: 5220
>     freq: 5220
>     freq: 5540
>     freq: 5540
>     freq: 5540
>     freq: 5540
>     freq: 5540
>     freq: 5785
>     freq: 5785
>     freq: 5785
>     freq: 5785
>     freq: 5785
>     freq: 5200
>     freq: 5200
>     freq: 5220
>     freq: 5220
>     freq: 5220
>     freq: 5220
>     freq: 5220
>     freq: 5220
>     freq: 5240
>     freq: 5540
>     freq: 5540
>     freq: 5540
>     freq: 5660
>     freq: 5745
>     freq: 5745
>     freq: 5785
>     freq: 5785
>     freq: 5785
>     freq: 5785
>     freq: 5785
>     freq: 5785
>     freq: 5785
>     freq: 5785
>     freq: 5785
>     freq: 5785
>     freq: 5785
>     freq: 5785
>     freq: 5785
>     freq: 5785
>     freq: 5785
>     freq: 5785
>     freq: 5785
>     freq: 5200
>     freq: 5220
>     freq: 5785
>     freq: 5785
> root@test4:~# uname -a
> Linux test4 4.17.0-rc7+ #5 SMP Mon May 28 12:35:22 CEST 2018 x86_64 GNU/Linux
> 
> Added:
> ATH_USER_REGD - openwrt patch (4 returns in ath/regd.c)
> 
> I have this card (pcie version) in 10 laptops (in some 2,3 of them) -
> working perfectly :)
> 
> BR
> Janusz


I have working PCI-E cards with this chipset as well, but M.2 cards with the same chipset (AR9462) do NOT work.

Many laptops only have M.2 slots, making the PCI-E solution impossible. Specifically I have laptops from ThinkPenguin which only have an A-keyed M.2 slot. It seems most M.2 cards available are E-keyed, making it difficult to find a compatible card that supports 5Ghz at all. I was excited to find these cards, only to be disappointed when they didn't work.

  reply	other threads:[~2018-06-15 13:31 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 [this message]
2018-06-15 16:08               ` Michał Kazior
2018-06-15 16:58                 ` mgreger
2018-06-15 17:23                   ` mgreger
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=20180615133102.N4IRI.135706.root@dnvrco-web10 \
    --to=mgreger@cinci.rr.com \
    --cc=janusz.dziedzic@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