Thanks Adrian,
Just wondering if there's anything I can do to help. I have the driver
repo.
Anthony
On 2020-09-13 14:53, Adrian Chadd wrote:
hi!
we're still working on this. It's going to take some time.
thanks,
-adrian
On Sun, 13 Sep 2020 at 11:12, Anthony Jenkins via freebsd
I have a Killer 1535 802.11ac wireless card (chipset = Qualcomm Atheros
QCA6174). I am using the ath10k/athp driver from git repo
https://github.com/erikarn/athp.git . Driver loads, but trying to start
the interface fails. What should I be looking at to fix this?
service netif start wlan2:
I'm running a fairly recent -CURRENT on my laptop with a run(4)-based
USB wireless adapter.?? I can connect to several wireless access points,
except for the ones at work.?? One's a Netgear Nighthawk X4.?? I see
errors related to WPA negotiation:
wpa_cli:
> interface wlan1
Connected to
I've been trying to run the ath10k driver port from
https://github.com/erikarn/athp/ 's master branch since I got a laptop
with a Qualcomm Atheros QCA6174 802.11ac wireless adapter. It would
load, but then crash the kernel within a few seconds. Today I figured
out what was wrong; no idea why
What is the current status of the Atheros ath10k driver effort? I have
a QCA6174 80211ac card in my new laptop.
none9@pci0:59:0:0: class=0x028000 card=0x15351a56 chip=0x003e168c
rev=0x32 hdr=0x00
vendor = 'Qualcomm Atheros'
device = 'QCA6174 802.11ac Wireless Network
Oh sorry... I'm adding it to ral(4).
Sent from Yahoo Mail on Android
On Fri, Feb 19, 2016 at 20:51, Adrian Chadd<adrian.ch...@gmail.com> wrote:
WHich driver family is it?
-a
On 19 February 2016 at 15:55, Anthony Jenkins via freebsd-wireless
<freebsd-wireless@freebsd.o
The Ralink RT3290 PCIe card is supported in Linux but not in FreeBSD.
I'm trying to port the Linux bits to FreeBSD, unless someone else has
already beat me to it...has anyone? I added the PCI device ID and most
of the firmware bits, but there's lots of stuff left to do...right now
what I
Ahhh... make in the module dir, not good? I've since done a kernel build and
I noticed it's not showing up (as much). Why would building the kernel module
that way cause that behavior?
Anthony
From: Adrian Chadd adr...@freebsd.org
To: Anthony Jenkins anthony.b.jenk...@att.net
Cc:
Will do. I'm actually thinking about reverting my changes just to see if stock
ath(4) works (it's been a looong while since I played with bringing it up). I
still occasionally see the same behavior I saw before my changes.
I'm using a recent Linux kernel (which works out of the box) to get it
I'll have to re-add the printf()s, but I'm pretty sure I saw 0x0B (of course it
could have been 0x08 I saw, but neither of those would make it through the
function - both 0x0B and 0x08 are blocked).
Anthony
On 12/22/2014 14:51, Adrian Chadd wrote:
See, that's where it's odd:
|
On 12/22/2014 15:22, Adrian Chadd wrote:
On 22 December 2014 at 11:59, Anthony Jenkins scoobi_...@yahoo.com wrote:
I'll have to re-add the printf()s, but I'm pretty sure I saw 0x0B (of course
it could have been 0x08 I saw, but neither of those would make it through
the function - both 0x0B
The attached patch seems to get my rfkill GPIO working. It seems
ar9300_enable_rf_kill() is never called. I added a call to it after
ath_hal_enable_rfkill(), but this is probably not the right place (I see it
called several times while the interface is up).
I also found several spots in the
12 matches
Mail list logo
