Athp driver
-
Yeah I couldn't see anything either. Seems to be working OK though so no significant regression, at least not yet!
Still seeing values in scans that cannot be correct in terms of channel or even the reported MAC. Some random data in there.
Can't wait to try
media VHT mode 11ac mediaopt hostap. Just need some way to actually apply it I guess. Fun!Steve
-
Anyone running this in a current, 12.1-stable, snapshot?
I tested the modules would load before upgrading and was surprised to find they did. But doesn't actually load the with the hardware in place.
I guess it's new modules time.
Steve
-
not anymore, I have virtualized everything on ESXi and added a Ubiquiti ap-ac-pro, for me it was too unstable.
but I have modules compiled for FreeBSD 12.1 if you want to try
https://drive.google.com/drive/folders/1fM-Jlmf8BY21kIEGueSxFWmrISZqcDj3
there is a folder athp-12.1 -
nice
Sponsored by: Rubicon Communications, LLC (d/b/a "Netgate")
Co-authored-by: Bjoern A. Zeeb bz@FreeBSD.ORG.
we had to wait for netgate to chime in before something get done
thumb up for netgate and bzfbd
but idk when we can take advantage of the patches, that drivers are intended to be built against FreeBSD 13
maybe with pfsense 2.6 ?
-
Ooo, nice I'll give them a go.
It's weird I'm seeing that firmware table full error that others reported before. It's been so long since I set this up initially I've forgotten exactly how I got past it. The notes I made that seemed sufficient at the time suddenly look woefully inadequate!
Steve
-
Looks like current snaps are loading more firmware by default. Standby....
-
And we're back...
Firmware limit removed in current snaps.Steve
-
ah it was #define FIRMWARE_MAX right?
-
Yup. https://github.com/freebsd/freebsd/commit/7dfd7b3b1a033dac9d594cdec23d2f82b84fa39d
-
@kiokoman
Can you add, please, firmware (with board-2.bin) for QCA9984/hw1.0 on FreeBSD 12.1? -
I'm not sure that is supported at all yet. What's the PCI-ID?
https://github.com/erikarn/athp/blob/master/otus/freebsd/src/sys/dev/athp/if_athp_pci.c#L126
Steve
-
@stephenw10
0x168c 0x0046 0x168c 0xcafe 0 0 "Qualcomm Atheros" "QCA9984" -
Yeah not in the code so the driver would not attach to that yet.
-
Hey, I also have a Compex WLE600VX card installed in my pFsense with 2.5.0 Dev installed, the card I understand is a Qualcomm Atheros QCA9882 based card. I'm running the latest snapshot from yesterday.
Can anyone summarise what I need to do to make use of this card please, it's currently not showing in the device list in the GUI.
-
@romprod said in Athp driver:
it's currently not showing in the device list in the GUI.
GUI ?
The dialogue from @kiokoman and @stephenw10 above is "command line world only". Wifi na and ac settings in the GUI, that silence fiction right now.
Be ready to compile your own device drivers etc .
IMHO, it implies also far more knowledge then just typing 'make' in the top of a source tree.
It's also "2.5.0" .... -
I'm born ready!
-
you need to build the driver, there are instructions here
https://github.com/Geramy/athp
2.5.0 is now freebsd 12.2 so you need to download freebsd 12.2 and compile the driver.
you can't compile inside pfsense so you need a virtual machine or something to do the work.
after that upload stuff to /boot/kernel/
cross your fingers and hope it works,if it work and the driver attach you can configure it using the guilast time i checked
you need to
git clone https://github.com/Geramy/athp/tree/NEW_ATHP_ARVIF_LOCKand not the one from erikarn, it does not build on freebsd12 but only on freebsd13
-
Yeah, I had significant difficulty getting that compiled. I think I was probably using the wrong branch for most of that time!
Steve
-
AC support on FreeBSD is terrible, almost not support at all. Make virtualization (like Xen, Proxmox and etc), than setup pfSense + OpenWrt and you will get fully support of WiFi with pfSense.
-
Yes, currently that's true. This thread is referencing the efforts to fix that though.
