http://bugzilla.novell.com/show_bug.cgi?id=567137
http://bugzilla.novell.com/show_bug.cgi?id=567137#c0
Summary: 2.6.25.20-0.5 implementation of ath5k driver refuses
to identify hardware correctly
Classification: openSUSE
Product: openSUSE 11.0
Version: Final
Platform: IA64
OS/Version: openSUSE 11.0
Status: NEW
Severity: Major
Priority: P5 - None
Component: Network
AssignedTo: bnc-team-screening@forge.provo.novell.com
ReportedBy: drankinatty@suddenlinkmail.com
QAContact: qa@suse.de
Found By: ---
Blocker: ---
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.6)
Gecko/20091216 Shiretoko/3.5.6
I have probably installed the madwifi driver at least 10 time on my laptop
on SuSE 10.2 through 11.2, but after a new 11.0 install, I am unable to find a
madwifi driver that will install and "stay" installed. The funny thing is that
the madwifi driver has no problems on the same box when installed on Arch
Linux.
Even more perplexing, I still have the 11.0 rpms that 'I WAS USING ON THIS
BOX' that no longer work, so I know the difficulty is something openSuSE
specific with the latest kernel or two. I say that, because the existing
drivers I have -- have always worked when I installed them with the original
kernel and then updated through each successive kernel. Now, jumping from
2.6.25.5-1.1 to 2.6.25.20-0.5 in one step has left 11.0 in a condition where it
will not load the driver properly.
I have built and installed from the driver for the following sources all of
which worked on this box in the past:
madwifi-0.9.4-1.src.rpm # The standard 0.9.4-1 driver
madwifi-0.9.4-1-current.src.rpm # The standard 0.9.4-1 driver with the
madwifi-project suggested snapshot for 2.6.25+ kernels.
madwifi-svn-122109 # this module worked briefly (limited to 1M/s), but then
died and despite a number of reinstalls will not configure properly.
madwifi-ng_r3366+ar5007-1.4.src.rpm # always worked in the past
madwifi-ng_r3366+ar5007-1.9.src.rpm # always worked...
madwifi-r3725+AR5007EG-2.2.src.rpm # what I was running on before the 11.2
install
madwifi-trunk+r3717-1.2.src.rpm # worked in the past...
and I have one or two more around... I even got to the point I was making
sure the kernel was 'properly prepared' and that 'all' remnants of the prior
installs were removed from the module tree and unloaded by reboot. I would:
make mrproper
make cloneconfig
make modules_prepare
make clean
in between the package installs.
Two notes of interest. (1) the packages are never consistent between where
they put the modules in the module tree under
/lib/modules/2.6.25.20-0.5-default/.. Sometimes the modules go under ../net,
sometimes under ../updates, sometimes under ../weak-updates, but until now it
always worked.
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
I don't see any logical reason why what has always worked on this box now
refuses to work. I have probably uninstalled, confirmed the uninstall was
complete, built, rebuilt, reinstalled until I'm blue in the face.
I don't know what suse is doing with the module tree and how it is
assigning modules/devices. From what I can tell the modules.alias handling of
ath5k versus ath_pci may be an issue. In the past, I have always just
blacklisted ath5k in /etc/modprobe.d/blacklist to prevent it from loading, but
that doesn't work any more. I have attempted to insure that ath_pci is loaded
before ath5k with MODULES_LOADED_ON_BOOT`as shown in
http://en.opensuse.org/Kernel_module_configuration. Still doesn't help.
For comparison that will hopefully 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 (ath5k driver) that is working fine:
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. Hopefully it is just
a bug in hardware recognition that can be easily fixed. Let me know if you need
anything else. Thanks. (See the Additional information below)
Reproducible: Always
Steps to Reproduce:
1. install 11.0, update kernel to 2.6.25.20-0.5-default
2. then try to install the madwifi driver
3.
Actual Results:
ath5k doesn't recognize hardware correctly and prevents ath_pci from loading.
Blacklisting ath5k has no effect, ath5k still loads.
Expected Results:
working madwifi install.
It looks like the problem may be opensuse incorrectly recognizing the card. I
will have to swap drives to load opensuse again. It looks like opensuse fails
to recognize the hardware correctly. The dmesg error from opensuse is:
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
There is no recognigition of the AR2425 chip. Comparing, Arch Linux dmesg
information shows the chip as:
ath5k phy0: Atheros AR2425 chip found (MAC: 0xe2, PHY: 0x70)
The complete lspci from the Arch Linux install is:
17:00.0 Ethernet controller: Atheros Communications Inc. AR5001 Wireless
Network Adapter (rev 01)
Subsystem: Askey Computer Corp. Device 7128
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-