FS#20185 - [kernel26] ath9k wifi not working on 2.6.34-2

Attached to Project: Arch Linux
Opened by Aleksandar Vasiljevic (Satan) - Thursday, 15 July 2010, 13:43 GMT
Last edited by Thomas Bächler (brain0) - Wednesday, 04 August 2010, 11:54 GMT
Task Type Bug Report
Category Upstream Bugs
Status Closed
Assigned To Tobias Powalowski (tpowa)
Thomas Bächler (brain0)
Architecture x86_64
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

after upgrade of kernel to 2.6.34-1.1 my TP-link ath9k wifi card doesn't work anymore.
using hostapd and shorewall for managing the card but it doesn't matter since i turned those 2 off
since there is no wlan card in ifconfig/iwconfig (only lo and 2 eth cards).
System is uptodate.
Card in question: TL-WN951N.

this is from log: grep -i "ath" /var/log/everything.log
kernel: ath9k 0000:06:01.0: PCI INT A -> GSI 19 (level, low) -> IRQ 19
kernel: ath: EEPROM regdomain: 0x809c
kernel: ath: EEPROM indicates we should expect a country code
kernel: ath: doing EEPROM country->regdmn map search
kernel: ath: country maps to regdmn code: 0x52
kernel: ath: Country alpha2 being used: CN
kernel: ath: Regpair used: 0x52
kernel: ath9k 0000:06:01.0: Failed to initialize device
kernel: ath9k 0000:06:01.0: PCI INT A disabled
kernel: ath9k: probe of 0000:06:01.0 failed with error -2
kernel: ath_pci 0000:06:01.0: PCI INT A -> GSI 19 (level, low) -> IRQ 19
kernel: MadWifi: ath_attach: Switching rfkill capability off.
kernel: Error loading module "ath_rate_sample"
kernel: ath_pci 0000:06:01.0: PCI INT A disabled


Additional info:
kernel26 2.6.34-1.1
linux-firmware 20100623-2


Steps to reproduce:
on every boot
This task depends upon

Closed by  Thomas Bächler (brain0)
Wednesday, 04 August 2010, 11:54 GMT
Reason for closing:  Not a bug
Comment by Aleksandar Vasiljevic (Satan) - Thursday, 15 July 2010, 13:45 GMT
sorry, added wrong version of kernel to title of the bug report, it should be 2.6.34-1.1 as written in details.. dunno how to change it.
Comment by Gerardo Exequiel Pozzi (djgera) - Tuesday, 03 August 2010, 22:35 GMT
  • Field changed: Summary (ath9k wifi not working on 2.6.34-2 → [kernel26] ath9k wifi not working on 2.6.34-2)
  • Field changed: Status (Unconfirmed → Assigned)
  • Field changed: Category (Packages: Extra → Upstream Bugs)
  • Task assigned to Thomas Bächler (brain0), Tobias Powalowski (tpowa)
status with 2.6.34.2-1?
Comment by Aleksandar Vasiljevic (Satan) - Tuesday, 03 August 2010, 23:33 GMT
ok just updated and rebooted, 2.6.34.2-1

kernel: cfg80211: Calling CRDA to update world regulatory domain
kernel: ath9k 0000:06:01.0: PCI INT A -> GSI 19 (level, low) -> IRQ 19
kernel: ath: EEPROM regdomain: 0x809c
kernel: ath: EEPROM indicates we should expect a country code
kernel: ath: doing EEPROM country->regdmn map search
kernel: ath: country maps to regdmn code: 0x52
kernel: ath: Country alpha2 being used: CN
kernel: ath: Regpair used: 0x52
kernel: phy0: Failed to initialize wep: -2
kernel: ath9k 0000:06:01.0: Failed to initialize device
kernel: ath9k 0000:06:01.0: PCI INT A disabled
kernel: ath9k: probe of 0000:06:01.0 failed with error -2
kernel: ath_pci 0000:06:01.0: PCI INT A -> GSI 19 (level, low) -> IRQ 19
kernel: MadWifi: ath_attach: Switching rfkill capability off.
kernel: Error loading module "ath_rate_sample"
kernel: ath_pci 0000:06:01.0: PCI INT A disabled

still same :(
Comment by Thomas Bächler (brain0) - Wednesday, 04 August 2010, 07:33 GMT
You are trying to load both madwifi and ath9k and it looks like they are fighting for your card and both failing. Uninstall madwifi.
Comment by Aleksandar Vasiljevic (Satan) - Wednesday, 04 August 2010, 09:50 GMT
*doublepost*
Comment by Thomas Bächler (brain0) - Wednesday, 04 August 2010, 09:55 GMT
If you don't read what I am saying, I cannot help you.
Comment by Aleksandar Vasiljevic (Satan) - Wednesday, 04 August 2010, 09:56 GMT
sry, no idea how this got posted twice, removing and rebooting, back in 2 min
Comment by Aleksandar Vasiljevic (Satan) - Wednesday, 04 August 2010, 10:13 GMT
i removed madwifi, (pacman -Rc madwifi madwifi-utils) and i'm still getting completely same report in log,
/*slocate madwifi gives me besides pacman and abs directories this: /lib/modules/2.6.34-ARCH/kernel/drivers/net/wireless/madwifi.*/
nvm database wasn't updated, directory doesn't exist, but somehow on boot madwifi is still probed after ath9k.
Comment by Thomas Bächler (brain0) - Wednesday, 04 August 2010, 10:54 GMT
Try find /lib/modules/2.6.34-ARCH/ -name ath\*ko
Comment by Aleksandar Vasiljevic (Satan) - Wednesday, 04 August 2010, 11:02 GMT
/lib/modules/2.6.34-ARCH/kernel/drivers/bluetooth/ath3k.ko
/lib/modules/2.6.34-ARCH/kernel/drivers/net/wireless/ath/ath.ko
/lib/modules/2.6.34-ARCH/kernel/drivers/net/wireless/ath/ath5k/ath5k.ko
/lib/modules/2.6.34-ARCH/kernel/drivers/net/wireless/ath/ath9k/ath9k.ko
/lib/modules/2.6.34-ARCH/kernel/drivers/net/wireless/ath/ath9k/ath9k_common.ko
/lib/modules/2.6.34-ARCH/kernel/drivers/net/wireless/ath/ath9k/ath9k_hw.ko
Comment by Thomas Bächler (brain0) - Wednesday, 04 August 2010, 11:07 GMT
Okay, that looks sane. I still don't get those messages above, they should not be referencing madwifi.

However, this message indicates that a required kernel module is missing:
kernel: phy0: Failed to initialize wep: -2
My suspicion is that you have included your wireless drivers (not just ath9k, but also madwifi) into initramfs, which is a big mistake and will result in problems as you describe them.
Comment by Aleksandar Vasiljevic (Satan) - Wednesday, 04 August 2010, 11:19 GMT
/etc/mkinitcpio.conf :
MODULES="pata_jmicron ata_generic ahci ppp_generic"
BINARIES=""
FILES=""
HOOKS="base udev autodetect pata scsi sata net keymap filesystems"

rc.conf:
MODULES=(ath9k snd-hda-intel fuse nvidia intel-agp pata_acpi pata_jmicron usbcore ehci-hcd uhci-hcd slhc evdev !usblp lp !ath_pci) (added !ath_pci couple of mins before to try to block madwifi but nothing)

can't remember any other location to look at, but this should be it, nothing in initrd, nothing passed to kernel line in grub.



Comment by Thomas Bächler (brain0) - Wednesday, 04 August 2010, 11:25 GMT
What is the 'net' hook doing there? It is the root of your problem.
Comment by Aleksandar Vasiljevic (Satan) - Wednesday, 04 August 2010, 11:35 GMT
removed, updated initrd image, it works now. Thanks alot (it worked just fine before on 2.6.33)
Solved.

Loading...