In this case you can simply uninstall madwifi-0.9.4 and ndiswrapper (if you only needed it for the WLAN, of course).
Get the latest HAL, currently
madwifi-hal-0.10.5.6-current.tar.gz
at snapshots.madwifi.org.
Make sure that everything you need to build kernel modules is installed.
Compile and install the new HAL package.
Reboot and the wlan inferface is there (usually called “ath0”).
On some machines with this chip, the kernel tries to use the ath5k module for the hardware and fails. In this case, the “ath5k” should be blacklisted in order to prevent automatic loading.
i uninstalled ndiswrapper and madwifi software then i downloaded madwifi-halXXX then compiled it with make ; make install
rebooted but still i dont see ath0 device
My understanding is that, if the detectors do NOT see
your device, then the only chance for it to work is with ndiswrapper.
And, based on your output from ndiswrapper, you do NOT
have the correct windows driver loaded. For ndiswrapper
details, see: Ndiswrapper - openSUSE
Your problem may be either the 32 vs 64-bit problem, or
that you need to choose one from another section of
the Windows distribution media, if that’s what you’re using:
e.g. win-2000 vs win-me vs win-xp vs win-vista, etc.
Try them all, one at a time.
The key, as mentioned there, is that you MUST see
‘device present’ info after the ‘driver installed’ line.
Evidently, my understanding is incorrect. Correct statement seems to be
if the detectors do NOT see it, then NOTHING will work.
So, I’m at a loss to understand why it isn’t showing up in hwinfo.
[Do you dual-boot Windows? If so, and it works there, that would
help. You can determine the ids from Windows, tho I don’t remember
how off the top of my head.]
Just a quick question, you are not using both ndiswrapper & madwifi are you ? if so, they will conflict & cause problems. If one doesn’t work, uninstall & try the other. Just to make sure you are using the correct driver, post the output of lspci -v from a console
when i reboot laptop after that i cant see dmesg | grep ath and lsmod | grep ath output
but again i do modprobe ath_pci and i can see outputs like this
From the 103c:002a that you found, your device is an Atheros AR9280,
which uses ath9k as its driver.
I know very little about Atheros devices, but I do know that this
driver is not fully available until kernel 2.6.28, which is why
openSUSE 11.0 with 2.6.25 does not recognize it. You might get it to
work with the MadWifi driver (http://madwifi.org/), but it is more
likely to work with the kernel from wireless testing (see http://wireless.kernel.org/en/users/Drivers/ath9k). Yes, that will
entail adding all the packages needed for kernel development, and
compiling your own kernel, but neither is rocket science.
Incidentally, wireless-testing has a 2.6.27-rc6 kernel, but the
wireless parts contain most of the stuff that will be in 2.6.28. I
have been running 2.6.27 kernels since the code merge of this version
started. There have been some show stopping bugs in the process, but
it has been good since 2.6.27-rc3.
For the wireless problem on this machine, remove madwifi and ndiswrapper. Go to PackMan :: Package details for broadcom-wl and one click install the appropriate driver.
The wireless button works but doesn’t turn into red in my case but I think that is not crucial…
