Mailinglist Archive: opensuse-bugs (4664 mails)

< Previous Next >
[Bug 567137] 2.6.25.20-0.5 implementation of ath5k driver refuses to identify hardware correctly
  • From: bugzilla_noreply@xxxxxxxxxx
  • Date: Wed, 3 Feb 2010 18:20:14 +0000
  • Message-id: <20100203182014.38CFBCC7CD@xxxxxxxxxxxxxxxxxxxxxx>
http://bugzilla.novell.com/show_bug.cgi?id=567137

http://bugzilla.novell.com/show_bug.cgi?id=567137#c2


David Rankin <drankinatty@xxxxxxxxxxxxxxxxxx> changed:

What |Removed |Added
----------------------------------------------------------------------------
Status|NEEDINFO |NEW
Info Provider|drankinatty@suddenlinkmail. |
|com |

--- Comment #2 from David Rankin <drankinatty@xxxxxxxxxxxxxxxxxx> 2010-02-03
18:20:12 UTC ---
Sorry for the late reply, been busy...

Yes, I'm blacklisting ath5k (have to -- no choice)

# Syntax: blacklist <driver name>
# See 'man modprobe'.
#
blacklist ath5k

The problem here is in the opensuse kernel module table that coordinates card
hardware ID with the proper module. That is wrong in openSuSE and it has been
for a couple of years ( I have fought this battle since 2007 with this laptop )

It was just a fluke that I loaded Arch Linux on the spare drive for the laptop,
and presto! the same ath5k driver worked perfectly because the lookup table
properly identified the card assigned ath5k correctly.

The important point is:

openSUSE:

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


Arch Linux:

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)


The suse lookup table is out of whack for this line of Atheros Cards

--
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.

< Previous Next >
This Thread
  • No further messages