Return-path: Received: from dnvrco-outbound-snat.email.rr.com ([107.14.73.231]:8465 "EHLO dnvrco-cmomta01.email.rr.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1751349AbeFNEPS (ORCPT ); Thu, 14 Jun 2018 00:15:18 -0400 Message-ID: <20180614041517.1GPY0.168676.root@dnvrco-web14> (sfid-20180614_061522_809149_0CA07418) Date: Thu, 14 Jun 2018 4:15:17 +0000 From: To: sedat.dilek@gmail.com, mgreger@cinci.rr.com Subject: Re: Atheros AR9462 - 5Ghz not working Cc: linux-wireless@vger.kernel.org In-Reply-To: <20180612181932.KVWU0.184603.root@dnvrco-web01> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Sender: linux-wireless-owner@vger.kernel.org List-ID: ---- mgreger@cinci.rr.com wrote: > > ---- mgreger@cinci.rr.com wrote: > > > > ---- mgreger@cinci.rr.com wrote: > > > > > > ---- Sedat Dilek wrote: > > > > On Tue, May 22, 2018 at 7:21 PM, 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?