Mailinglist Archive: opensuse-bugs (4709 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: Mon, 19 Apr 2010 21:36:26 +0000
  • Message-id: <20100419213626.6CC842454D6@xxxxxxxxxxxxxxxxxxxxxx>
http://bugzilla.novell.com/show_bug.cgi?id=567137

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


David Rankin <drankinatty@xxxxxxxxxxxxxxxxxx> changed:

What |Removed |Added
----------------------------------------------------------------------------
Status|NEEDINFO |ASSIGNED
InfoProvider|drankinatty@suddenlinkmail. |
|com |

--- Comment #10 from David Rankin <drankinatty@xxxxxxxxxxxxxxxxxx> 2010-04-19
21:36:24 UTC ---
OK Jiri,

I have booted back into 2.6.25.20-0.7-default and this bug really shows up
big-time. Here is the rundown:

(1) booting 2.6.25.20-0.7-default ignores the blacklist of ath5k in
/etc/modprobe.d/blacklist, so the ath5k module is loaded and wireless fails;

(2) attempting to configure in yast2 lan fails because no wireless connection
(under the hardware tab) recognizes the ath5k module as being present on the
system (this bug) and ath_pci isn't recognized as present due to ath5k being
present. Basically with the openSuSE kernel the module listbox on the yast2 lan
-> hardware tab is empty so you cannot configure a wireless device with either
ath5k or ath_pci.

(3) manually unloading ath5k and attempting to load ath_pci with rmmod and
modprobe does not work.

(4) blacklisting ath5k has NO affect, the ONLY way you can get the ath_pci
module to load so that the ath_pci module is available to yast2 lan is to
REMOVE the ath5k module from /lib/modules/2.6.25.20-0.7-default with:

mv -u 2.6.25.20-0.7-default/kernel/drivers/net/wireless/ath5k
/home/backup/alchemy/lib/modules/2.6.25.20-0.7-default/kernel/drivers/net/wireless

(now that's just not right)

(5) on reboot, after completely removing the ath5k module from the module tree
to prevent it from loading, the ath_pci module is loaded correctly and ath0
springs to life.

So in sum, the problem is that ath5k in the standard kernel incorrectly
recognizes the hardware and blacklisting ath5k is ignored leaving the wireless
user screwed unless you go through the steps outlined above. Most just give up
and search for some inferior ndiswrapper solution. The only reason I knew it
should work is because this hardware worked fine on 10.2 and 10.3, then due to
this bug was completely broken in 11.0 and 11.1.

In answer to your other question, the wpa_passphrase utility does nothing more
than generate the information for /etc/wpa_supplicant/wpa_supplicant.conf. That
just allows you to create a search/priority list for the wireless access points
you normally use. It just speeds up the initial connection.

Let me know if you need/want anything else. Thanks for your help.

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