| Date | Fri, 14 Sep 2007 17:12:00 +0200 | From | Robert de Rooy <> | Subject | ath5k driver not working on ThinkPad |
| |
Mel Gorman wrote: > (To list based on CC's in net-add-ath5k-wireless-driver-fix.patch . If > that is in error, apologies) > > On (31/08/07 21:58), Andrew Morton didst pronounce: > >> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.23-rc4/2.6.23-rc4-mm1/ >> >> > > I thought I would give the ath5k driver a shot on my Thinkpad T60p to see > what happened but it wasn't particularly successful. lspci -v shows > > 03:00.0 Ethernet controller: Atheros Communications, Inc. AR5212 802.11abg NIC (rev 01) > Subsystem: IBM ThinkPad 11a/b/g Wireless LAN Mini Express Adapter (AR5BXB6) > Flags: bus master, fast devsel, latency 0, IRQ 22 > Memory at edf00000 (64-bit, non-prefetchable) [size=64K] > Capabilities: [40] Power Management version 2 > Capabilities: [50] Message Signalled Interrupts: Mask- 64bit- Queue=0/0 Enable- > Capabilities: [60] Express Legacy Endpoint IRQ 0 > Capabilities: [90] MSI-X: Enable- Mask- TabSize=1 > Capabilities: [100] Advanced Error Reporting > Capabilities: [140] Virtual Channel > > During boot, the following relevant information in dmesg shows up; > > ACPI: PCI Interrupt 0000:03:00.0[A] -> GSI 17 (level, low) -> IRQ 21 > PCI: Setting latency timer of device 0000:03:00.0 to 64 > Uhhuh. NMI received for unknown reason b1 on CPU 0. > You have some hardware problem, likely on the PCI bus. > Dazed and confused, but trying to continue > ath5k_hw_nic_wakeup: failed to resume the MAC Chip > ACPI: PCI interrupt for device 0000:03:00.0 disabled > ath_pci: probe of 0000:03:00.0 failed with error -5 > > Needless to say, it fails to bring up networking later. I have no real idea > how to debug something like this. Any suggestions? > > I just tried Fedora 8test2 LiveCD which includes the 0.9.5-BSD version of the ath5k driver and get the exact same thing on my ThinkPad T60. Fedora 8test2 uses a 2.6.23 based kernel. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
|