On 12/22/2009 07:23 PM, David C. Rankin wrote:
Second, under openSuSE, I have always had to use the 'ath_pci' module. No matter what, the ath5k driver has never worked -- period. That always seemed strange. Well I confirmed it was strange, because when I checked the module used by Arch Linux on this box, low-and-behold, it was using ath5k??? How does that happen?
The errors are pretty much of the same flavor. After the driver is loaded, it complains that the chip doesn't respond:
Dec 22 15:00:11 alchemy kernel: PCI: Enabling device 0000:17:00.0 (0000 -> 0002) Dec 22 15:00:11 alchemy kernel: ACPI: PCI Interrupt 0000:17:00.0[A] -> GSI 19 (level, low) -> IRQ 19 Dec 22 15:00:11 alchemy kernel: PCI: Setting latency timer of device 0000:17:00.0 to 64 Dec 22 15:00:11 alchemy kernel: MadWifi: unable to attach hardware: 'Hardware didn't respond as expected' (HAL status 3) Dec 22 15:00:11 alchemy kernel: ACPI: PCI interrupt for device 0000:17:00.0 disabled Dec 22 15:02:18 alchemy kernel: ACPI: PCI Interrupt 0000:17:00.0[A] -> GSI 19 (level, low) -> IRQ 19 Dec 22 15:02:18 alchemy kernel: PCI: Setting latency timer of device 0000:17:00.0 to 64 Dec 22 15:02:18 alchemy kernel: ath5k_pci 0000:17:00.0: registered as 'phy1' Dec 22 15:02:19 alchemy kernel: ath5k phy1: failed to wakeup the MAC Chip Dec 22 15:02:19 alchemy kernel: ACPI: PCI interrupt for device 0000:17:00.0 disabled Dec 22 15:02:19 alchemy kernel: ath5k_pci: probe of 0000:17:00.0 failed with error -5
dmesg:
ath5k_pci 0000:17:00.0: registered as 'phy0' ath5k phy0: failed to resume the MAC Chip ath5k_pci: probe of 0000:17:00.0 failed with error -5 ath_hal: 0.9.18.0 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413) wlan: 0.9.4 ath_pci: 0.9.4 eth0: RTL8101e at 0xffffc2000065a000, 00:1b:38:af:36:b8, XID 34200000 IRQ 4348
Here is an update and comparison that might help in figuring out what is going on. Currently I have my arch drive installed in this same laptop. Here is the config for madwifi that is working find on Arch: syslog: Dec 23 04:30:35 alchemy kernel: ath5k 0000:17:00.0: PCI INT A -> GSI 19 (level, low) -> IRQ 19 Dec 23 04:30:35 alchemy kernel: ath5k 0000:17:00.0: registered as 'phy0' Dec 23 04:30:35 alchemy kernel: ath5k phy0: Atheros AR2425 chip found (MAC: 0xe2, PHY: 0x70) Dec 23 04:30:51 alchemy avahi-daemon[4161]: Joining mDNS multicast group on interface wlan0.IPv4 with address 192.168.6.102. Dec 23 04:30:51 alchemy avahi-daemon[4161]: New relevant interface wlan0.IPv4 for mDNS. Dec 23 04:30:51 alchemy avahi-daemon[4161]: Registering new address record for 192.168.6.102 on wlan0.IPv4. Dec 23 04:30:52 alchemy ntpd[4170]: Listen normally on 3 wlan0 192.168.6.102 UDP 123 Dec 23 04:30:53 alchemy avahi-daemon[4161]: Registering new address record for fe80::21b:9eff:fe7c:f6e7 on wlan0.*. Dec 23 04:30:54 alchemy ntpd[4170]: Listen normally on 7 wlan0 fe80::21b:9eff:fe7c:f6e7 UDP 123 dmesg: 18:25 alchemy:~> sudo dmesg | grep ath ath5k 0000:17:00.0: PCI INT A -> GSI 19 (level, low) -> IRQ 19 ath5k 0000:17:00.0: setting latency timer to 64 ath5k 0000:17:00.0: registered as 'phy0' ath: EEPROM regdomain: 0x64 ath: EEPROM indicates we should expect a direct regpair map ath: Country alpha2 being used: 00 ath: Regpair used: 0x64 ath5k phy0: Atheros AR2425 chip found (MAC: 0xe2, PHY: 0x70) ath5k phy0: unsupported jumbo ath5k phy0: unsupported jumbo ath5k phy0: unsupported jumbo madwifi-0.9.4 package: 18:24 alchemy:~> pacman -Q madwifi madwifi 0.9.4.4100-1 18:24 alchemy:~> pacman -Ql madwifi madwifi /lib/ madwifi /lib/modules/ madwifi /lib/modules/2.6.32-ARCH/ madwifi /lib/modules/2.6.32-ARCH/kernel/ madwifi /lib/modules/2.6.32-ARCH/kernel/drivers/ madwifi /lib/modules/2.6.32-ARCH/kernel/drivers/net/ madwifi /lib/modules/2.6.32-ARCH/kernel/drivers/net/wireless/ madwifi /lib/modules/2.6.32-ARCH/kernel/drivers/net/wireless/madwifi/ madwifi /lib/modules/2.6.32-ARCH/kernel/drivers/net/wireless/madwifi/ath_hal.ko madwifi /lib/modules/2.6.32-ARCH/kernel/drivers/net/wireless/madwifi/ath_pci.ko madwifi /lib/modules/2.6.32-ARCH/kernel/drivers/net/wireless/madwifi/ath_rate_amrr.ko madwifi /lib/modules/2.6.32-ARCH/kernel/drivers/net/wireless/madwifi/ath_rate_minstrel.ko madwifi /lib/modules/2.6.32-ARCH/kernel/drivers/net/wireless/madwifi/ath_rate_onoe.ko madwifi /lib/modules/2.6.32-ARCH/kernel/drivers/net/wireless/madwifi/ath_rate_sample.ko madwifi /lib/modules/2.6.32-ARCH/kernel/drivers/net/wireless/madwifi/wlan.ko madwifi /lib/modules/2.6.32-ARCH/kernel/drivers/net/wireless/madwifi/wlan_acl.ko madwifi /lib/modules/2.6.32-ARCH/kernel/drivers/net/wireless/madwifi/wlan_ccmp.ko madwifi /lib/modules/2.6.32-ARCH/kernel/drivers/net/wireless/madwifi/wlan_scan_ap.ko madwifi /lib/modules/2.6.32-ARCH/kernel/drivers/net/wireless/madwifi/wlan_scan_sta.ko madwifi /lib/modules/2.6.32-ARCH/kernel/drivers/net/wireless/madwifi/wlan_tkip.ko madwifi /lib/modules/2.6.32-ARCH/kernel/drivers/net/wireless/madwifi/wlan_wep.ko madwifi /lib/modules/2.6.32-ARCH/kernel/drivers/net/wireless/madwifi/wlan_xauth.ko Why doesn't openSuSE activate the driver successfully in the manner that Arch does? I have looked at modinfo to see if there are any special module loading options being used in Arch, but there aren't any. Anybody got any suggestions? -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org