How to install the development version of atk9k
ath9k is the new open source driver for newer atheros cards including those with 11n hardware support.
At the time of writing(Kevmitch 23:31, 10 September 2008 (CEST)), ath9k will not compile against the current kernel release 2.6.26. It is however included in the most recent release candidate 2.6.27-rc6. Thus, in order to get it running, you will either need to backport ath9k to your older kernel or download and compile 2.6.27-rc6. It is expected that the latter process will be significantly easier especially now that you can download the necessary kernel source directly off the web without using git. If you have managed to backport the driver to an older kernel, please share your knowledge and add to this page.
Compiling your kernel is at a minimum going to require gcc, make and the qt3 development libraries to run the x-configuration utility. The names of these packages and how to install them will vary from distro to distro. You'll also want to add yourself to the src group so that you can do most of the kernel compilation as a regular user. You will have to log out and log back in for this change to take effect.
# aptitude install git-core build-essential kernel-package libqt3-mt-dev fakeroot
# adduser <you> src
$ sudo aptitude install git-core build-essential kernel-package libqt3-mt-dev fakeroot
$ sudo adduser <you> src
Get the kernel sources
Download and unzip the kernel sources
$ cd /usr/src
$ wget http://www.kernel.org/pub/linux/kernel/v2.6/testing/linux-2.6.27-rc6.tar.bz2
$ tar xvjf linux-2.6.27-rc6.tar.bz2
$ cd linux-2.6.27-rc6
This is the part most people are afraid of. However, you can use your current kernel's configuration as a baseline to help ease the pain. Most self-respecting distributions keep a copy of your kernel configuration in the /boot directory alongside the kernel itself. If this is not the case, you might find a copy of the kernel config at /proc/config.gz (which will of course needs to be gunziped). Whatever the case, you will want to copy the the current config file to the directory of the the kernel tree you are about to compile /usr/src/linux-2.6.27-rc6/.config
$ cp /boot/config-`uname -r` ./.config
Configure the kernel
$ make xconfig
You'll likely see some messages in the terminal about unset or unrecognized configuration variables which automatically either get added or removed respectively. You might want to make sure the following are enabled
Networking → Networking Options → [Y]QoS and/or fair queueing (CONFIG_NET_SCHED)
Networking → Networking Options → QoS and/or fair queueing → [M]Multiband Priority Queueing (PRIO) (CONFIG_NET_SCH_PRIO)
Networking → Wireless Networking → [M]Improved wireless configuration API (CONFIG_CFG80211)
Networking → Wireless Networking → Improved wireless configuration API → [Y]nl80211 new netlink interface support (CONFIG_NL80211)
Networking → Wireless Networking → [Y]Wireless Extensions (CONFIG_MAC80211)
Networking → Wireless Networking → [M]Generic IEEE 802.11 Networking Stack (mac80211) (CONFIG_WIRELESS_EXT)
Networking → Wireless Networking → Generic IEEE 802.11 Networking Stack (mac80211) → Rate control algorithm selection → [Y]PID controller based rate control algorithm (CONFIG_MAC80211_RC_PID)
and most importantly
Device Drivers → [Y]Network Device Support (CONFIG_WLAN80211)
Device Drivers → Network Device Support → Wireless LAN → [Y]Wireless LAN (IEEE 802.11) (CONFIG_WLAN80211)
Device Drivers → Network Device Support → Wireless LAN → Wireless LAN (IEEE 802.11) → [m]Atheros 802.11n wireless cards support (CONFIG_ATH9K)
Also, unless you want to worry about creating an initrd (initial RAM disk), you're also probably best to build anything necessary to read your root filesystem into the kernel rather than as modules. This includes both filesystem (e.g. ext3) and low level hardware drivers (e.g. libata). The particular drivers required will depend on your particular setup. You can try and get an idea of what you might need to include by examining the output of
lsmod. If you see any modules in there that might be required to boot the system, you should make sure you compile these in.
Make sure you save any changes you make before you exit.
Now it's time to compile your kernel. If you have NCPU cpus, the generic way to do this is
$ make -j <NCPU+1>
# make modules_install
# cp arch/<your architecture>/boot/bzImage /boot/linux-2.6.27-rc6
Where <your architecture> will be x86 if you're running a 32-bit system or x86_64 if you're running 64-bit.
Then you'll have to set your bootloader to load the new kernel. If you're using grub, you'll add this to /boot/grub/menu.list or /etc/grub.conf or whatever
title Linux kernel 2.6.27-rc6 root (hd#,#) kernel /boot/linux-2.6.27-rc6 root=/dev/<your root device> ro
You're going to have to set (hd#,#) and root=/dev/<your root device> to reflect your boot device configuration. The best bet is probably to just copy and modify an existing entry.
Now reboot into your new kernel.
Debian has a system to help you build kernels as Debian packages. If NCPU is the number of CPUs you have,
$ CONCURRENCY_LEVEL=<NCPU+1> fakeroot make-kpkg --append-to-version=.mykernel linux_image
(for Ubuntu, skip "su" and prepend the below commands with "sudo")
Note: if running Debian with initrd, you can run:
$ CONCURRENCY_LEVEL=<NCPU+1> fakeroot make-kpkg --initrd --append-to-version=.mykernel linux_image
# dpkg -i /usr/src/linux-image-2.6.27-rc6.mykernel_2.6.27-rc6.mykernel-10.00.Custom_amd64.deb
or if you're running 32-bit i386
# dpkg -i /usr/src/linux-image-2.6.27-rc6.mykernel_2.6.27-rc6.mykernel-10.00.Custom_i386.deb
Again it is recommended that you build what you need into your kernel. However, if aren't sure what is needed to read your root file system and so can't just build it into your kernel, you can create an initrd using update-initramfs
# update-initramfs -c -k 2.6.27-rc6.mykernel
Ok, now see if it worked
Once you have your kernel compiled and install, reboot and choose it from your grub or lilo menu. Hopefully it boots Ok, and you can open a command line and
# modprobe ath9k
The first command should hopefully generate no errors and the second is purely diagnostic and should show you a working wireless device. You can then proceed to use wpa_supplicant or network manager or iwconfig to setup your wireless networking.
168c:0024 (MacBook Wireless)
Currently with this hardware (output of
lspci -vvv), the driver installs, but does not allow association with an access point.
02:00.0 Network controller: Atheros Communications, Inc. Unknown device 0024 (rev 01) Subsystem: Apple Computer Inc. Unknown device 0087 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- Latency: 0, Cache Line Size: 256 bytes Interrupt: pin A routed to IRQ 17 Region 0: Memory at 50100000 (64-bit, non-prefetchable) [size=64K] Capabilities:  Power Management version 2 Flags: PMEClk- DSI- D1+ D2- AuxCurrent=375mA PME(D0+,D1+,D2-,D3hot+,D3cold-) Status: D0 PME-Enable- DSel=0 DScale=0 PME- Capabilities:  Message Signalled Interrupts: Mask- 64bit- Queue=0/0 Enable- Address: 00000000 Data: 0000 Capabilities:  Express Legacy Endpoint IRQ 0 Device: Supported: MaxPayload 128 bytes, PhantFunc 0, ExtTag- Device: Latency L0s <512ns, L1 <64us Device: AtnBtn- AtnInd- PwrInd- Device: Errors: Correctable- Non-Fatal- Fatal- Unsupported- Device: RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop- Device: MaxPayload 128 bytes, MaxReadReq 512 bytes Link: Supported Speed 2.5Gb/s, Width x1, ASPM L0s L1, Port 0 Link: Latency L0s <512ns, L1 <64us Link: ASPM L1 Enabled RCB 128 bytes CommClk+ ExtSynch- Link: Speed 2.5Gb/s, Width x1 Capabilities:  MSI-X: Enable- Mask- TabSize=1 Vector table: BAR=0 offset=00000000 PBA: BAR=0 offset=00000000 Capabilities:  Advanced Error Reporting Capabilities:  Virtual Channel