I still have to check the log and put it here (I don't have the eee at hand right now), but there is something weird with all this. As I stated earlier, the latest installation images cant scan or connect too!! Only the oldest installation image connects (but also fails scanning), so the misconfiguration is a posibility, but there is something with the installer that makes the same problem happen.
Later I'll do some test and upload the logs. Thanks for your attention On Wed, Oct 29, 2008 at 6:23 PM, Pedro Bulach Gapski <[EMAIL PROTECTED]>wrote: > > > 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 > >
_______________________________________________ Debian-eeepc-devel mailing list [email protected] http://lists.alioth.debian.org/mailman/listinfo/debian-eeepc-devel
