On Wed, Oct 29, 2008 at 2:40 PM, Federico Castagnini < [EMAIL PROTECTED]> wrote:
> On Wed, Oct 29, 2008 at 7:18 AM, Ben Armstrong > <[EMAIL PROTECTED]> wrote: > > On Wed, 29 Oct 2008 06:57:37 +0100 > > "Sergio Blanco" <[EMAIL PROTECTED]> wrote: > >> I'm using wicd so using the interfaces file is useless for me. Even if I > >> tried, the first problem to solve would be it's inability to scan for > APs. > >> If I have the interface up and running it doesn't matter if it knows > where > >> to connect, I should be able to search for networks, no? > > I have made almost the same tests and still have the same problem, can > not scan or connect. > > With a usb dongle (mod rt73) i was able to scan and use that interface > as expected, so the trouble is with the atheros wifi device... > > This problem came up with an upgrade i made last week, that upgrade > the kernel (plus other things) from 2.6.26-4? to 2.6.26-8. > > I think this is something relevant. Sure it is. I have the same box, and upgraded from 2.6.25 to 2.6.26-8, when that was advertised on this list. I used wifi with wpasupplicant and now I am giving network manager a try. Both are working fine. I give a couple of suggestions: 1. get the newest installation image on an usb device and boot with it to check if you can get a working wifi connection, to rule out hardware problems. I believe the latest image is expected to work fine with wifi; 2. if all goes fine, leave wicd out for a while and try to debug your setup on the command line. iwconfig and iwlist can make the job and maybe give you error messages to point the way to go. I hope this helps, Pedro
_______________________________________________ Debian-eeepc-devel mailing list [email protected] http://lists.alioth.debian.org/mailman/listinfo/debian-eeepc-devel
