Guys, I need a miracle! 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 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 Basically, I'm f'ing stumped... 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. My shortcoming here is that I know not 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. I need the collective wisdom of the brain-trust to point out where I'm doing the stupid thing that I'm apparently doing repeatedly... (at least I'm consistent) What else would make sense to try or check here? -- 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