On Thu, 2010-02-04 at 15:26 -0800, Dan Williams wrote: > On Thu, 2010-02-04 at 18:03 -0500, Chris Siebenmann wrote: > > | > I'm not sure what the machine's exact configuration is because > > | > I inherited it (the usual long cycle of passing older and older > > | > hardware around at work), but I believe it must; I certainly don't > > | > have anything plugged into any external slots or sockets. > > | > > | And just to confirm, what are the exact symptoms that you have with > > | "broken" kernels? Just that connections can't be made, the card can't > > | find access points, etc? or? > > > > In the GUI, no wireless networks show up/are listed in the usual > > dropdown menu; this means that I can't go as far as even trying to > > connect to anything. From the command line, 'iwlist wifi0 scanning' > > lists nothing. > > Wait, wifi0? You need to be using 'eth0' or 'eth1', whichever eth > device that 'iwconfig' reports. wifi0 is a historical airo anomaly > that's only used for packet capture and sniffing of the 802.11 frames. > It should not be used for anything other than Wireshark basically. > > Do you get the same behavior if you use the normal ethX interface of the > airo device? Note that just because wifi0 may return scan results doesn't mean it should be used with iwconfig... But also, you're doing the iwlist scan as root, correct? Dan -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
