On Fri, Aug 27, 2010 at 01:49:33PM +0100, Brett Parker wrote:
On 26 Aug 20:52, Chris G wrote:
On Thu, Aug 26, 2010 at 08:42:40PM +0100, Chris G wrote:
Well, you could check that you're not being insane by going to a terminal and doing:
/sbin/iwlist <nameofwirelessinterface> scanand see if that brings anything back... if it says that the interface wasn't available or some other such, then you might need to ifconfig the interface up first.
So what's <nameofwirelessinterface>? This is often much of the problem with WiFi, these 'things' that if you know what they are are obvious but if you don't are inscrutable.
... well I've discovered that eth1 is my WiFi as nm-tool reports:-
Device: eth1 ----------------------------------------------------------------- Type: 802.11 WiFi Driver: wl State: disconnected Default: no HW Address: 70:F1:A1:2D:DA:86
Capabilities:
Wireless Properties WEP Encryption: yes WPA Encryption: yes WPA2 Encryption: yes
... but I can't scan it:-
chris@laptop:~$ /sbin/iwlist eth1 scan eth1 Interface doesn't support scanning.Hmph! :-)
It's lying to you...
(Or rather, it's saying "the interface doesn't support scanning (when it's not up)")
What's you need to do first, loike, is: sudo ifconfig eth1 up
Then scan again :)
chris@laptop:~$ sudo ifconfig eth1 up [sudo] password for chris: chris@laptop:~$ /sbin/iwlist eth1 scan eth1 Interface doesn't support scanning.
chris@laptop:~$
However I think there's something more subtle wrong, digging from another direction it seems that the driver for eth1 (which is called wl0, I think) isn't loaded and I can't load it with modprobe. I'll investigate further when I get back home, it's too painful doing it from here in Belgium. :-)