Alternatively, I tried to apply the above patch to my existing (broken) system, but I can't seem to compile it without the Linux headers, which I don't have (and can't download...ironic?), because my installation is stock-fresh.
]]>SkullOne wrote:This is fixed in Kernel 3.3.2-1. I just installed it and happily found my wireless to be working.
Does this mean that I can now safely upgrade to linux-3.3.3-1 as pacman suggests?
I'm running linux-ck 3.3.3-1, and my ath9k-based wireless card is working just fine. It's a safe bet to say that 3.3.3-1 -ARCH is working as well.
]]>This is fixed in Kernel 3.3.2-1. I just installed it and happily found my wireless to be working.
Does this mean that I can now safely upgrade to linux-3.3.3-1 as pacman suggests?
]]>Help a newbie here: if I follow the Beginner's Guide installation instructions (dd the .iso to installation media) on a fresh download, I'm getting the latest kernel? That is, this 3.3.2-1 that supposedly works perfectly?
You'd actually be getting one a bit older than 3.3.2, which wouldn't have the bad commit (it only affected 3.3.1). If you really need the latest kernel, you can use one of the testing isos: http://releng.archlinux.org/isos/ Otherwise, the older kernel should work perfectly fine until you have a chance to -Syu.
]]>Your problem must therefore lie elsewhere.
]]>How could I check to see if I'm being affected by this bug?
lspci
04:00.0 Network controller: Atheros Communications Inc. AR9300 Wireless LAN adaptor (rev 01)
uname -r
3.3.2-1-ARCH
So, if you are lazy you can just downgrade to the older kernel and upgrade when 3.3.2 is available from Core.
]]>