http://bugzilla.novell.com/show_bug.cgi?id=567137
http://bugzilla.novell.com/show_bug.cgi?id=567137#c4
David Rankin changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEEDINFO |NEW
InfoProvider|drankinatty@suddenlinkmail. |
|com |
--- Comment #4 from David Rankin 2010-04-04 01:36:56 UTC ---
No choice,
I can't update to 11.2, I tried, but opensuse does not have a fglrx driver
for 11.2 for my card (x1200) and without the fglrx driver desktop effects
crashes and spontaneously shuts down. The radeonhd driver is a no-go as well
due to July 09 changes that left it blackscreening for my card. So 11.0 with
the 8-9 ATI driver (fglrx 8.532) is the only workable solution.
I know this same problem affects 11.1, because I had to compile the madwifi
on buildservice after 11.1 was released. I don't think I had the same issue
with 11.2 (I just don't recall).
The Arch kernel is 2.6.33-1, and the madwifi driver has worked with all
Arch Kernels since I started using them about a year ago. So I know all Arch
kernels 2.6.32-2 through 2.6.33-1 work fine.
I am no expect of kernel module loading, but I believe the problem with the
madwifi driver is the openSuSE /lib/modules/<kernel>/modules.alias file which
causes the proper module to fail to load. Specifically, I think suse has a
problem with module.alias because it has duplicate entries for the same madwifi
device that points to different modules (that can't be right). My Atheros card
has the following ID:
ath_pci: r3725+AR5007EG
ACPI: PCI Interrupt 0000:17:00.0[A] -> GSI 19 (level, low) -> IRQ 19
^^^^^^^^^^^^^
PCI: Setting latency timer of device 0000:17:00.0 to 64
SuSE module.alias has:
alias pci:v00001FC1d00000010sv*sd*bc*sc*i* ib_ipath
alias pci:v00001FC1d0000000Dsv*sd*bc*sc*i* ib_ipath
alias pci:v0000168Cd00000024sv*sd*bc*sc*i* ath5k
alias pci:v0000168Cd00000023sv*sd*bc*sc*i* ath5k
alias pci:v0000168Cd0000001Csv*sd*bc*sc*i* ath5k
alias pci:v0000168Cd0000001Bsv*sd*bc*sc*i* ath5k
alias pci:v0000168Cd0000001Asv*sd*bc*sc*i* ath5k
alias pci:v0000168Cd00000019sv*sd*bc*sc*i* ath5k
alias pci:v0000168Cd00000018sv*sd*bc*sc*i* ath5k
alias pci:v0000168Cd00000017sv*sd*bc*sc*i* ath5k
^^^^^^ ^^^^^
alias pci:v0000168Cd00000016sv*sd*bc*sc*i* ath5k
alias pci:v0000168Cd00000015sv*sd*bc*sc*i* ath5k
alias pci:v0000168Cd00000014sv*sd*bc*sc*i* ath5k
alias pci:v0000168Cd00001014sv*sd*bc*sc*i* ath5k
alias pci:v000010B7d00000013sv*sd*bc*sc*i* ath5k
alias pci:v0000A727d00000013sv*sd*bc*sc*i* ath5k
alias pci:v0000168Cd00000013sv*sd*bc*sc*i* ath5k
alias pci:v0000168Cd00000012sv*sd*bc*sc*i* ath5k
alias pci:v0000168Cd00000011sv*sd*bc*sc*i* ath5k
alias pci:v0000168Cd00000007sv*sd*bc*sc*i* ath5k
alias pci:v0000168Cd00000207sv*sd*bc*sc*i* ath5k
alias pci:v0000168Cd00009013sv*sd*bc*sc*i* ath_pci
alias pci:v0000168Cd00000024sv*sd*bc*sc*i* ath_pci
alias pci:v0000168Cd00000023sv*sd*bc*sc*i* ath_pci
alias pci:v0000168Cd0000001Dsv*sd*bc*sc*i* ath_pci
alias pci:v0000168Cd0000001Csv*sd*bc*sc*i* ath_pci
alias pci:v0000168Cd0000001Bsv*sd*bc*sc*i* ath_pci
alias pci:v0000168Cd0000001Asv*sd*bc*sc*i* ath_pci
alias pci:v0000168Cd00000019sv*sd*bc*sc*i* ath_pci
alias pci:v0000168Cd00000018sv*sd*bc*sc*i* ath_pci
alias pci:v0000168Cd00000017sv*sd*bc*sc*i* ath_pci
^^^^^^ ^^^^^
alias pci:v0000168Cd00000016sv*sd*bc*sc*i* ath_pci
alias pci:v0000168Cd00000015sv*sd*bc*sc*i* ath_pci
alias pci:v0000168Cd0000101Asv*sd*bc*sc*i* ath_pci
alias pci:v0000168Cd00001014sv*sd*bc*sc*i* ath_pci
alias pci:v000010B7d00000013sv*sd*bc*sc*i* ath_pci
alias pci:v0000A727d00000013sv*sd*bc*sc*i* ath_pci
alias pci:v0000168Cd00000013sv*sd*bc*sc*i* ath_pci
alias pci:v0000168Cd00000012sv*sd*bc*sc*i* ath_pci
alias pci:v0000168Cd00000007sv*sd*bc*sc*i* ath_pci
That is duplicate entries for 0000:17:00.0[A] with one pointing to ath5k and
one pointing at ath_pci. Consequently it doesn't know what module to load.
No with Arch, the Arch module.alias only has one entry for 0000:17:00.0[A]:
alias pci:v0000168Cd0000001Dsv*sd*bc*sc*i* ath5k
alias pci:v0000168Cd0000001Csv*sd*bc*sc*i* ath5k
alias pci:v0000168Cd0000001Bsv*sd*bc*sc*i* ath5k
alias pci:v0000168Cd0000001Asv*sd*bc*sc*i* ath5k
alias pci:v0000168Cd00000019sv*sd*bc*sc*i* ath5k
alias pci:v0000168Cd00000018sv*sd*bc*sc*i* ath5k
alias pci:v0000168Cd00000017sv*sd*bc*sc*i* ath5k
^^^^^^ ^^^^^
alias pci:v0000168Cd00000016sv*sd*bc*sc*i* ath5k
alias pci:v0000168Cd00000015sv*sd*bc*sc*i* ath5k
alias pci:v0000168Cd00000014sv*sd*bc*sc*i* ath5k
alias pci:v0000168Cd00001014sv*sd*bc*sc*i* ath5k
alias pci:v000010B7d00000013sv*sd*bc*sc*i* ath5k
alias pci:v0000A727d00000013sv*sd*bc*sc*i* ath5k
alias pci:v0000168Cd00000013sv*sd*bc*sc*i* ath5k
alias pci:v0000168Cd00000012sv*sd*bc*sc*i* ath5k
alias pci:v0000168Cd00000011sv*sd*bc*sc*i* ath5k
alias pci:v0000168Cd00000007sv*sd*bc*sc*i* ath5k
alias pci:v0000168Cd00000207sv*sd*bc*sc*i* ath5k
alias pci:v0000168Cd0000002Esv*sd*bc*sc*i* ath9k
alias pci:v0000168Cd0000002Dsv*sd*bc*sc*i* ath9k
alias pci:v0000168Cd0000002Bsv*sd*bc*sc*i* ath9k
alias pci:v0000168Cd0000002Asv*sd*bc*sc*i* ath9k
alias pci:v0000168Cd00000029sv*sd*bc*sc*i* ath9k
alias pci:v0000168Cd00000027sv*sd*bc*sc*i* ath9k
alias pci:v0000168Cd00000024sv*sd*bc*sc*i* ath9k
alias pci:v0000168Cd00000023sv*sd*bc*sc*i* ath9k
with the single entry, my card is detected and loads every time.
If you look at the dmesg and syslog messages posted above, I think this
explains why my Atheros card is nearly impossible to get working on SuSE
without compiling custom madwifi packages, standing on one foot, and wiggling
your nose during the driver install and boot :p
Let me know if you need more info and I'm happy to chase it down.
--
Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.