On Sun, 2009-01-04 at 19:37 -0500, Bob Copeland wrote: > On Sun, Jan 04, 2009 at 12:43:44AM +0000, Martin wrote: > > Hi, > > I'm trying to sort out a problem with the ath5k module not loading on > > a ThinkPad T42. I'm using the current Debian testing kernel (2.6.26) on > > i686. Detail of the PCI bus configuration of this machine can be found > > here: > > (device is: 168c:1014) > > > The Debian developer in charge of handling this suggested contacting you > > for more information. Can anyone make any suggestions? Thanks in > > advance for your time and for the great driver (once loaded it works > > fantastically). > > The driver uses the PCI device ID as well as the silicon revision > (SREV) and radio revision read from the card. We've had this PCI id in > since the beginning as far as I can tell. It would be good to see the > output of the following lines from 'dmesg' when the driver attempts to > load: > > ath5k: registered as 'phy0' > [any failure messages might show up here] > ath5k: Atheros ARxxxx chip found (MAC: 0x??, PHY: 0x??)
The only lines are from when I manually inserted the module Dec 9 10:12:58 kernel: [ 389.200838] ACPI: PCI Interrupt 0000:02:02.0[A] -> Link [LNKC] -> GSI 11 (level, low) -> IRQ 11 Dec 9 10:12:58 kernel: [ 389.200907] ath5k_pci 0000:02:02.0: registered as 'phy0' Dec 9 10:12:59 kernel: [ 389.497733] ath5k phy0: Atheros AR5213 chip found (MAC: 0x56, PHY: 0x41) Dec 9 10:12:59 kernel: [ 389.497751] ath5k phy0: RF5111 5GHz radio found (0x17) Dec 9 10:12:59 kernel: [ 389.497759] ath5k phy0: RF2111 2GHz radio found (0x23) Dec 9 10:12:59 kernel: [ 389.530256] udev: renamed network interface wlan0 to ath0 Dec 9 10:12:59 kernel: [ 389.704721] ADDRCONF(NETDEV_UP): ath0: link is not ready > If you don't see any of the above, then chances are the driver didn't > attempt loading at all. ... I have a nasty suspicion that I wasted everyone's time and this is a stupid user error. You saying this got me thinking about mechanisms for preventing drivers from loading and thus digging through /etc/modules.d/ only to find that for a previous kernel I had the madwifi drivers installed which had helpfully blacklisted ath5k . Sorry, PEBCAK. Thanks for your patients. > > Moritz said: > >> Could you forward your mail to the ath5k devs at > >> ath5k-de...@lists.ath5k.org? If they can provide an isolated 2.6.26 > >> backport we can apply it to the 2.6.26-13 kernel upload or add it to > >> a point update later. > > compat-wireless might fill this role, but I don't know offhand if it > goes back to 2.6.26. Cheers, - Martin _______________________________________________ ath5k-devel mailing list ath5k-devel@lists.ath5k.org https://lists.ath5k.org/mailman/listinfo/ath5k-devel
