On Tue, 22 May 2012, wes wrote: > the point of doing it other ways (ifconfig, iwlist) is to demonstrate that > it's an issue specific to NM, not the driver or kernel or anything else.
wes, OK, here're the results: 'ifconfig wlan0' shows it's neither UP nor RUNNING. 'ifconfig wlan0 up' brings it UP: the radio light on the front edge turns on. Still not RUNNING. 'iwconfig wlan0' shows how the interface is configured. 'iwlist scan' produces a list of neighborhood WAPs. 'ifconfig wlan0' shows it's still not RUNNING, but it's UP. This was the same situation with wicd running instead of NM. WICD has nothing to do with eth0, only wireless interfaces. It works on my Dell running Slackware-13.37/x86_64, on the Toshiba running Xubuntu-11.10 (which won't work on eth0, strangely enough), and on previous portables I've had. So, since wlan0 can be brought UP manually, can we assume it's a NM issue and not a hardware issue? Thanks, Rich _______________________________________________ PLUG mailing list [email protected] http://lists.pdxlinux.org/mailman/listinfo/plug
