2008/4/18, Ildar Rakhmanov <[EMAIL PROTECTED]>: > Hi ath5k-developers: > > After waiting long time for an ath5k driver in 2.6.25 I finally compiled it > yesterday. > This is a result on Thinkpad T60p: > > <6>ath5k_pci 0000:03:00.0: registered as 'phy0' > <0>Uhhuh. NMI received for unknown reason b1 on CPU 0. > <0>You have some hardware problem, likely on the PCI bus. > <0>Dazed and confused, but trying to continue > <3>ath5k phy0: failed to resume the MAC Chip > <6>ACPI: PCI interrupt for device 0000:03:00.0 disabled > <6>iTCO_wdt: Intel TCO WatchDog Timer Driver v1.02 (26-Jul-2007) > <4>ath5k_pci: probe of 0000:03:00.0 failed with error -5 > > > > > > lspci -vn -d 168c: > 03:00.0 Class 0200: 168c:1014 (rev 01) > Subsystem: 1014:058a > 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 > > Looks like this chip is not supported yet? > I am back to madwifi driver, which BTW also see NMIs, and I use "iwpriv ath0 > bgscan 0" to avoid lockups. Work great nevertheless. > Is there any chance that more recent code will work? If so can you point > out? > > Will be happy to provide any additional information. > > Thanks a lot for your great work. > Ildar >
Are you using compat-wireless or an old snapshot ??? -- GPG ID: 0xD21DB2DB As you read this post global entropy rises. Have Fun ;-) Nick _______________________________________________ ath5k-devel mailing list [email protected] https://lists.ath5k.org/mailman/listinfo/ath5k-devel
