<p>Well, it just started to work. I did the same as I did today like ten times this week to no avail. As I had been playing compiling ath5k and ath_pci, uninstalled the madwifi pakages. I just reinstalled the eee acpi scripts to get the standard version and reinstalled madwifi from repositories and voila! it works!</p>
<p>Weird. But it works for now. Thanks!!!<br></p>
<br><br><div class="gmail_quote">On Sat, Nov 8, 2008 at 11:12 AM, Glenn Saberton <span dir="ltr"><<a href="mailto:gsaberton@foomagic.org">gsaberton@foomagic.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
-----BEGIN PGP SIGNED MESSAGE-----<br>
Hash: SHA1<br>
<div class="Ih2E3d"><br>
Sergio Blanco wrote:<br>
> Nobody knows what to do?<br>
><br>
> I still insist, none of the USB Installers could scan, and only the<br>
> oldest I found could connect. Once I can scan for APs, probably<br>
> everything will go right<br>
><br>
</div>I'm leaning towards hardware issues, but for interests sake, what does<br>
the following command output?<br>
<br>
find /lib/modules/`uname -r` -name ath_pci.ko<br>
<br>
cheers<br>
<br>
Glenn<br>
<div class="Ih2E3d">-----BEGIN PGP SIGNATURE-----<br>
Version: GnuPG v1.4.9 (GNU/Linux)<br>
<br>
</div>iEYEARECAAYFAkkVdBoACgkQV8GyuTwyskM8wACeNqi89nVB1/BUnnJh3h/aQDf6<br>
gtsAnRgJQMDOT89zGMF/qvnuXEvshQVV<br>
=oc0i<br>
-----END PGP SIGNATURE-----<br>
</blockquote></div><br>