It worked before I rebooted…
After the reboot, can not get it to work any longer.

there is a build service repo available ( its for the eeepc which has the ar5007eg wireless )

http://download.opensuse.org/repositories/home:etrash:eeePC/openSUSE_11.0

if you don’t feel like a eeepc wifi driver then heres a generic version:

http://download.opensuse.org/repositories/home:schmolle1980/openSUSE_11.0

Just ensure you pick the madwifi-r3725+AR5007EG ( works ) package it provides not madwifi-trunk+r3717 ( won’t work )

i am using the eeepc version and it works fine, just make sure to override the automatically suggested alsa-driver package to not install, who knows what it will do to your sound ( if you use the eeepc repo ).

a more happier opensuse user

I was able to get my AR5007EG running on suse 11.0 64-bit using the exact same steps, but instead using (what appears to be) the latest patched madwifi drivers.

Just replace step:

wget -c http://snapshots.madwifi.org/special/madwifi-ng-r2756+ar5007.tar.gz

With this:

wget http://snapshots.madwifi.org/madwifi-hal-0.10.5.6/madwifi-hal-0.10.5.6-r3772-20080716.tar.gz

untar, make, make install, etc. It even worked after reboot. Just make sure you have ‘ath_pci’ listed as the module name in Network settings. I’m using an Acer Aspire 5520 laptop if that helps any.

Sounds like everything is being done properly. I have seen that ‘phy0′ come up before, even on other distributions. I think that may be coming from a kernel update, but I’m not sure at all.

Here is a link that helped me out a lot. It focuses more on Fedora and Ubuntu, but it can be applied to Suse as well.

http://home.nyc.rr.com/computertaijutsu/rhwireless.html#5007

I’m having the exact same problem.

I also put ath5k in my modprobe.d/blacklist, and I also entered “modprobe ath_pci”

After startup when I type dmesg |grep ath5k, I still get
ath5k_pci 0000:07:00.0: registered as ‘phy0′
ath5k phy0: failed to resume the MAC Chip
ath5k_pci: probe of 0000:07:00.0 failed with error -5

dmesg |grep HAL
MadWifi: unable to attach hardware: ‘Hardware didn’t respond as expected’ (HAL status 3)

I don’t get why it is loaded when I boot, because I really thought that blacklisting ath5k would
prevent it from loading, it looks like my computer just ignores the blacklist.

I’m not running suse, but I’m running Gentoo.
I’ve opened a thread under “networking & security”, but no one is responding.

Any other way to completely remove the ath5k driver??

The site of madwifi says HAL status 3 means that ath5k and madwifi are both running.

To remove ath5k I used the command ‘rmmod ath5k’
The I entered ‘modprobe ath_pci’ to prevent it from being loaded at boot time.
I ran these commands as root and rebooted.

Whoah, correction. modprobe ath_pci installs the driver, it doesn’t blacklist it. My bad.
(must not post on lack of sleep:)

It sounds like ath5k won’t go away no matter what you do.

One sure-fire way to kill it is to reinstall opensuse and enter ‘brokenmodules=ath5k’ (without the quotes) on the boot line parameter; that way ath5k will never install to begin with.

Otherwise, I would use the rmmod command before attempting anything else. Maybe try rmmod ath5k, rmmod ath5k_pci, rmmod phy0, then blacklist all of them, reboot, make sure no ath5k loads up, then install madwifi. Then…

modprobe ath_pci
ifconfig ath0 up
iwlist ath0 scan

wlan0 is usually ndiswrapper and that should not be there. remove any trace of ndiswrapper and use ath0 for madwifi.

I use WPA2 and madwifi with no problems.:)