Atheros Wifi 9.2.0.496 Allos.zip
Savage Doherty
sudo apt-get install build-essential linux-headers-$(uname -r) gitecho "options ath10k_core skip_otp=y" sudo tee /etc/modprobe.d/ath10k_core.confwget -4.4.2-1.tar.gztar -zxvf backports-4.4.2-1.tar.gzcd backport-4.4.2-1make defconfig-wifimakesudo make installgit clone -firmware.gitsudo cp -r ath10k-firmware/QCA9377 /lib/firmware/ath10k/sudo cp /lib/firmware/ath10k/QCA9377/hw1.0/firmware-5.bin_WLAN.TF.1.0-00267-1 /lib/firmware/ath10k/QCA9377/hw1.0/firmware-5.bin
I'm having a very similar issue. My wifi will suddently disconnect. The troubleshooter resolves the issue, but it's very annoying to have to do this every 30 minutes or so. It loves to drop Skype calls as well. I just installed the recommended driver, and hope that resolves the issue. Do you know why it's not listed on the recommended drivers list? I have a Pavilion dv5-2035dx.
I am running OpenWRT 21.02.03 on a Linksys MR8300. I added one wifi on radio0 Qualcomm Atheros QCA9886 802.11nac and another one on for radio1 Qualcomm Atheros IPQ4019 802.11bgn. The third radio (radio2) Qualcomm Atheros IPQ4019 802.11nac is not in use.
Having a modern fully open source wifi chipset would be really nice, ath9k was a nice blip in history but so far has not been repeated. Currently mediatek looks like they are warming up to the idea a bit but I have no idea if we will ever get anything as open as those 9000 series atheros ones again.
Yeah I guess I am a bit pessimistic about this though I got a major white pill today with amd going for coreboot support by default by 2026. So maybe one of the radio chipset manufacturers will have a bright moment at some point, might be mediatek, might be atheros coming back from the grave or someone entirely different. Even then I doubt we are ever going to get as much freedom as with the ath9k because of regulations.
I'm looking for a good SOHO WiFi router that can be flashed with Openwrt firmware to expand the wifi range in some remote areas of the building. Our wifi "backbone" is running on Cisco HW, but in this situation we're talking about two small black areas that we want to cover with WiFi signal and Wired network
It works well, but I'm hoping that using a dedicated wifi usb dongle, rather than the integrated chip will boost the signal range, which is currently quite limited. Thus, I plugged in an 802.11 USB 2.0 wifi dongle by TP-Link: TL-WN721N.
You could also test disabling your routers wifi security feature very briefly to see if you can connect properly with it disabled. Be sure to reboot the router after making this change. Never leave your wifi network unprotected for any length of time, this is simply a very short term trouble shooting measure.
I have the following Atheros card: 168c:002b Qualcomm Atheros AR9285 Wireless Network Adapter (PCI-Express) (rev 01) (Subsystem: 105b:e025) which I rebranded in Windows 7 as Broadcom 14e4:4365 for my Lenovo B590 using the aet_rw512 atheros_eeprom_tool. The only reason I used Windows 7 for rebranding was because I couldn't make any of the various versions of iwleeprom tool to write data in EEPROM. I've tried the official googlecode one-revisions 21-44, Andy's iwleeprom, MacNB_iwleeprom and some of my own hacks at the iwleeprom code. I'm pretty sure the card is not an OTP card as I don't see any OTP text when working with the iwleeprom tool and I was able to rebrand it with aet_rw512 tool. Unfortunately, I was rushing things too much and didn't change the Subsystem IDs. Therefore the card doesn't pass the whitelist test in my B590.
root@eee:/atheros/AtherosROMKit-master/MacNB_iwleeprom# echo Y./iwleeprom -d 0000:02:00.0 -i
../../rebrand/htpc/original.bin -D 1
debug level: 1
Using device 0000:02:00.0 [RW] Broadcom Corporation BCM43142 802.11b/g/n
IO driver: ath9k
Supported ops: read write parse patch11n patch_rd
address: f9ff0000
HW: AR9285 (PCI-E) rev 0002
RF: integrated
Checking NVM size...
ath9k short eeprom base: 128 size: 376
About to write device EEPROM, press 'Y' if you are sure... Writing data to EEPROM...
'.' = match, 'x' = write
Dump file byte order: LITTLE ENDIAN
0000 [....
**** Write verify error: Addr 0008, wrote 168c, read 14e4 ****
**** Write verify error: Addr 000a, wrote 2b, read 4365 ****...................................
.......................]
0080 [................................................................]
0100 [................................................................]
0180 [................................................................]
0200 [................................................................]
0280 [................................................................]
0300 [................................................................]
0380 [................................................................]
0400 [................................................................]
0480 [................................................................]
0500 [................................................................]
0580 [................................................................]
0600 [................................................................]
0680 [................................................................]
0700 [................................................................]
0780 [................................................................]
0800 [....
**** Write verify error: Addr 0808, wrote 168c, read 14e4 ****
**** Write verify error: Addr 080a, wrote 2b, read 4365 ****...................................
.......................]
0880 [................................................................]
0900 [................................................................]
0980 [................................................................]
0a00 [................................................................]
0a80 [................................................................]
0b00 [................................................................]
0b80 [................................................................]
0c00 [................................................................]
0c80 [................................................................]
0d00 [................................................................]
0d80 [................................................................]
0e00 [................................................................]
0e80 [................................................................]
0f00 [................................................................]
0f80 [................................................................]
EEPROM has been written from '../../rebrand/htpc/original.bin'
This is tough one. When I was getting those "write verify errors", it was because the atheros driver did not like the state of the atheros card (bad checksum). I think you need to look further into the linux driver as to what/where the "writes" are being ignored/discarded.
aa06259810