Success after all!!! - was: Re: Totally non-functioning wifi card- starting again completely was: Re: Laptop wireless problem
On Monday 04 July 2016 17:37:00 Brian wrote:
> On Mon 04 Jul 2016 at 15:37:42 +0100, Lisi Reisz wrote:
> > On Monday 04 July 2016 15:16:23 Brian wrote:
> >
> > It isn't. It is just a short quotation to show the ipw 2200 and the
> > DRIVERS=="?*", because it bothered me that the drivers bit just had a
> > question mark, but apparently my worry about that was misplaced. Whole
> > file beneath my signature.
>
> Full quotes are always preferable. If I were in your position I'd
> regenerate the file. You've possibly got at least one device there
> which is not on the machine. Let the system take care of things.
>
> Be that as it may, you appear to have all necessary firmware and
> drivers. So, how do you fancy a bit of low level stuff?
Trying again.
> Reboot and first check firmware loading from 'journalctl'.
root@debian-wheezy:/home/sarah# journalctl -b | grep 2200
Jul 04 23:10:49 debian-wheezy kernel: ipw2200: Intel(R) PRO/Wireless 2200/2915
Network Driver, 1.2.2kmprq
Jul 04 23:10:49 debian-wheezy kernel: ipw2200: Copyright(c) 2003-2006 Intel
Corporation
Jul 04 23:10:49 debian-wheezy kernel: ipw2200: Detected Intel PRO/Wireless
2200BG Network Connection
Jul 04 23:10:49 debian-wheezy kernel: ipw2200 0000:03:03.0: firmware:
direct-loading firmware ipw2200-bss.fw
Jul 04 23:10:49 debian-wheezy kernel: ipw2200: Detected geography ZZD (13
802.11bg channels, 0 802.11a channels)
Jul 04 23:11:06 debian-wheezy NetworkManager[1239]: <info> rfkill0: found WiFi
radio killswitch
(at /sys/devices/pci0000:00/0000:00:1e.0/0000:03:03.0/ieee80211/phy0/rfkill0)
(driver ipw2200)
Jul 04 23:11:07 debian-wheezy NetworkManager[1239]: <info> (wlan0): new 802.11
WiFi device (driver: 'ipw2200' ifindex: 3)
root@debian-wheezy:/home/sarah#
> Then
> issue the command 'wpa_cli'.
>
> 1. wpa-cli
> You get a prompt ">". This is interactive mode. A selected
> interface should be shown. TAB completion of commands works.
> Command history is with the UP and DOWN keys. The following
> commands are typed at the prompt.
>
> 2. add_network
> You'll probably get 0 for the network number.
>
> 3. set_network 0 ssid "Your_SSID"
> The response should be "OK".
>
> 4. set_network psk "Your_passphrase"
> The response should be "OK".
>
> 5. enable_network 0
> The response should be "OK". Authentication and association
> should take place.
>
> 6. status 0
> Has it?
I don't *believe* it!
root@debian-wheezy:/home/sarah# wpa_cli
wpa_cli v2.3
Copyright (c) 2004-2014, Jouni Malinen <j@w1.fi> and contributors
This software may be distributed under the terms of the BSD license.
See README for more details.
Selected interface 'wlan0'
Interactive mode
<3>CTRL-EVENT-SCAN-RESULTS
> add_network
0
> set_network 0 ssid "NETGEAR08"
OK
<3>CTRL-EVENT-SCAN-RESULTS
> set_network psk "yyyyyyyyyyyyy"
Invalid SET_NETWORK command: needs three arguments
(network id, variable name, and value)
<3>CTRL-EVENT-SCAN-RESULTS
<3>CTRL-EVENT-SCAN-RESULTS
<3>CTRL-EVENT-SCAN-RESULTS
<3>CTRL-EVENT-SCAN-RESULTS
> set_network 0 psk "yyyyyyyyyyyyy"
OK
<3>CTRL-EVENT-SCAN-RESULTS
> enable network 0
OK
<3>CTRL-EVENT-SCAN-RESULTS
<3>Trying to associate with xx:xx:xx:xx:xx (SSID='NETGEAR08' freq=2437 MHz)
<3>Association request to the driver failed
<3>Associated with xx:xx:xx:xx:xx
<3>WPA: Key negotiation completed with xx:xx:xx:xx:xx [PTK=CCMP GTK=CCMP]
<3>CTRL-EVENT-CONNECTED - Connection to xx:xx:xx:xx:xx completed [id=0
id_str=]
<3>CTRL-EVENT-SCAN-RESULTS
>
[1]+ Stopped wpa_cli
root@debian-wheezy:/home/sarah# ping 192.168.0.1
PING 192.168.0.1 (192.168.0.1) 56(84) bytes of data.
64 bytes from 192.168.0.1: icmp_seq=1 ttl=64 time=0.475 ms
64 bytes from 192.168.0.1: icmp_seq=2 ttl=64 time=0.491 ms
64 bytes from 192.168.0.1: icmp_seq=3 ttl=64 time=0.483 ms
64 bytes from 192.168.0.1: icmp_seq=4 ttl=64 time=0.429 ms
^C
--- 192.168.0.1 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 2999ms
rtt min/avg/max/mdev = 0.429/0.469/0.491/0.032 ms
root@debian-wheezy:/home/sarah# ping www.google.co.uk
PING www.google.co.uk (216.58.213.163) 56(84) bytes of data.
64 bytes from lhr26s02-in-f3.1e100.net (216.58.213.163): icmp_seq=1 ttl=57
time=12.5 ms
64 bytes from lhr26s02-in-f3.1e100.net (216.58.213.163): icmp_seq=2 ttl=57
time=12.4 ms
64 bytes from lhr26s02-in-f3.1e100.net (216.58.213.163): icmp_seq=3 ttl=57
time=13.2 ms
64 bytes from lhr26s02-in-f3.1e100.net (216.58.213.163): icmp_seq=4 ttl=57
time=11.6 ms
64 bytes from lhr26s02-in-f3.1e100.net (216.58.213.163): icmp_seq=5 ttl=57
time=12.1 ms
^C
--- www.google.co.uk ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4007ms
rtt min/avg/max/mdev = 11.610/12.405/13.225/0.526 ms
root@debian-wheezy:/home/sarah#
Brilliant! \o/ \o/ But what next??
I stand rebuked for my lack of faith. :-(
I hope that it is not permanent as i am about to change the passphrase - but
I suppose that I could always call it network 1 in future.
I really can't start dancing jigs around the house at this time of night at
my age!!!!
Lisi
Reply to: