On Sat, Nov 29, 2008 at 4:55 PM, Jim mickeyboa@sbcglobal.net wrote:
Thorsten Leemhuis wrote:
On 29.11.2008 15:42, Valent Turkovic wrote:
On Sat, Nov 29, 2008 at 3:28 PM, Thorsten Leemhuis fedora@leemhuis.info wrote:
On 29.11.2008 14:51, Valent Turkovic wrote:
[...] After compiling madwifi-hal and blacklisting ath5k wireless started working perfectly.
FYI, in case you are not aware of it: You can get madwifi pre-compiled from RPM Fusion. Getting it from there might be the best for those that don't want to compile or blacklist manually.
For Fedora 9 madwifi drivers from rpmfusion stopped working for me (I believe I also posted a bug on your mailing list)
Not all package maintainer read the mailing lists. Hence please file a bug (http://bugzilla.rpmfusion.org) if you encounter a problem. That is the best way to get a problem fixed -- then it'll not only work for you, but also "just work" for everybody else. And that's what all of us want, isn't it?
so I started manually compiling drivers. I'm using now the new madwifi-hal and not madwifi drivers.
RPM Fusion in the F-10 branch as well.
Cu knurd
The driver for the wireless on the eeePC is built in the 2.6.27 kernel.
Yes it is but it is performing really poorly :( you can have a look at my bug report.
Cheers, Valent.