Comment 115 for bug 1383184

Revision history for this message
laaag (lagged) wrote : Re: Atheros Qualcomm Killer N1525 Wireless-AC [168c:003e] not supported

I got it working as described in this thread: http://lists.infradead.org/pipermail/ath10k/2015-April/004958.html
Using xubuntu (14.10 upgraded to 15.04) Anyway distro shouldn't be much different. Basically to make it working you need to do (what i did):

1. Get the windows drivers from your notebook manufacturer, in my case MSI GS60. http://download.msi.com/nb_drivers/lan/KillerSuite_1.1.49.1068_Win7_Win81-MSI.zip
2. Get the needed phyton scripts to extract windows firmware:
dissect.py https://gist.github.com/kazikcz/8e5845ad84ca251aa295
assemble.py https://gist.github.com/kazikcz/c970cbf3a863ebbc4495
3. Get kvalo's kernel tree from https://github.com/kvalo/ath

4. Unpack Killer suite and run the following commands: (run commands as root , sudo / sudo su)
python dissect.py < drivers/Production/Windows8.1-x64/k1525w81/qca61x420.bin
mkdir /lib/firmware/ath10k/QCA6174/hw2.1
python assemble.py killer-n1525-fw 0 fw-2.bin fw-1.bin 4 > /lib/firmware/ath10k/QCA6174/hw2.1/firmware-4.bin
cp drivers/Production/Windows8.1-x64/k1525w81/eeprom_qca9377_1p0_NFA435_olpc.bin /lib/firmware/ath10k/QCA6174/hw2.1/board.bin

5. Unpack kvalo's kernel and compile it with:

sudo apt-get install libncurses5-dev gcc make git exuberant-ctags

To simplify things copy your current kernel config to ath-master root folder:
cp /boot/config-`uname -r`* .config
you can configure if you want with: (not needed)
make menuconfig
then compile with: (where X is the number of cores of you processor, i used 6)
make -jX
# then take a coffee or even better a cold beer, anyway it just took about 20 minutes for me.

6. Install the new kernel:
sudo make modules_install install

7. Create config file with:
nano /etc/modprobe.d/ath10k.conf
Write to it:
options ath10k_core skip_otp=y

8. Reboot using your new kernel 4.x.x-wl-ath

9. Run ifconfig

10. Voila wlan0 should be there waiting for you, now try to connect to you AP.

If its not working try to check if you missed something, check log file (/var/log/dmesg) for more details of what failed.

Give thanks to the guys who made this possible for me: http://lists.infradead.org/mailman/listinfo/ath10k