Wireless device suddenly not working

[shiv_379]

Yet more proof than Linux hates me
I have an fujitsu-siemens laptop with Kubuntu Dapper installed dual booting with windows XP. I've had it set up for a while now and had no problems. Recently I configured the wireless networking to have a fixed IP address and I'm fairly sure I remember it working like that (it was quite late at night, memory a little fuzzy). I booted into windows today because my torrents seem to run faster there, and I was using the wired network (also setup to fixed IP, for port forwarding). I rebooted to Linux and forgot to turn the wireless switch on the front of my laptop back on. Of course Linux didn't detect the wireless device, but when i remembered and switched it on it still didn't recognise! I've tried rebooting, tried undoing the fixed IP, all the basics but still it can't quite recognise a wireless device.

I can't ping or connect to my router (192.168.1.1), KNetwork Manager doesn't show any wireless devices / networks, but the network setup in system settings does show both the wired and wireless network devices (eth0 eth1). IFConfig also shows both devices (plus the loopback), but trying to ping anything returns unknown host.

Anyone have any suggestions? please?
I've been hoping to move to Linux on a more permenant basis, but setbacks like this are...offputting to say the least.

~Shiv

[shiv_379]

Re: Wireless device suddenly not working

Collected some more information in case it's helpful.
The network seems to function correctly with a direct cable connection, it's just the wireless that is refusing to work.

ifconfig:

eth0   Link encap:Ethernet HWaddr 00:03:0D:34:DD:D8
     UP BROADCAST MULTICAST MTU:1500 Metric:1
     RX packets:0 errors:0 dropped:0 overruns:0 frame:0
     TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
     collisions:0 txqueuelen:1000
     RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
     Interrupt:217 Base address:0x6c00

eth1   Link encap:Ethernet HWaddr 00:12:F0:D3:12:24
     UP BROADCAST MULTICAST MTU:1500 Metric:1
     RX packets:11 errors:982 dropped:982 overruns:0 frame:0
     TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
     collisions:0 txqueuelen:1000
     RX bytes:0 (0.0 b) TX bytes:2304 (2.2 KiB)
     Interrupt:217 Base address:0x8000 Memory:fa9fe000-fa9fefff

lo    Link encap:Local Loopback
     inet addr:127.0.0.1 Mask:255.0.0.0
     UP LOOPBACK RUNNING MTU:16436 Metric:1
     RX packets:12 errors:0 dropped:0 overruns:0 frame:0
     TX packets:12 errors:0 dropped:0 overruns:0 carrier:0
     collisions:0 txqueuelen:0
     RX bytes:1032 (1.0 KiB) TX bytes:1032 (1.0 KiB)

/var/log/messages

Aug 12 17:36:21 localhost kernel: [17179591.656000] ieee80211_1_1_13: 802.11 data/management/control stack, 1.1.13
Aug 12 17:36:21 localhost kernel: [17179591.656000] ieee80211_1_1_13: Copyright (C) 2004-2005 Intel Corporation <jketreno@linux.intel.com>
Aug 12 17:36:21 localhost kernel: [17179591.668000] ieee80211: 802.11 data/management/control stack, git-1.1.7
Aug 12 17:36:21 localhost kernel: [17179591.668000] ieee80211: Copyright (C) 2004-2005 Intel Corporation <jketreno@linux.intel.com>
Aug 12 17:36:21 localhost kernel: [17179591.768000] ipw2200: Intel(R) PRO/Wireless 2200/2915 Network Driver, 1.1.1
Aug 12 17:36:21 localhost kernel: [17179591.768000] ipw2200: Copyright(c) 2003-2006 Intel Corporation
Aug 12 17:36:21 localhost kernel: [17179591.768000] Warning: PCI driver ipw2200 has a struct device_driver shutdown method, please update!
...
Aug 12 17:36:21 localhost kernel: [17179591.768000] ipw2200: Detected Intel PRO/Wireless 2200BG Network Connection

...
Aug 12 17:36:21 localhost kernel: [17179592.208000] ipw2200: Detected geography ZZR (14 802.11bg channels, 0 802.11a channels)
...
Aug 12 17:36:21 localhost kernel: [17179593.060000] r8169 Gigabit Ethernet driver 2.2LK loaded
Aug 12 17:36:21 localhost kernel: [17179593.060000] ACPI: PCI Interrupt 0000:01:05.0[A] -> GSI 19 (level, low) -> IRQ 217
Aug 12 17:36:21 localhost kernel: [17179593.060000] eth0: RTL8169 at 0xf8956c00, 00:03:0d:34:dd:d8, IRQ 217
Aug 12 17:36:21 localhost kernel: [17179593.640000] lp: driver loaded but no devices found
Aug 12 17:36:21 localhost kernel: [17179593.648000] r8169: eth0: link down

system log:

12/08/06 17:52:53	localhost	dhclient	

12/08/06 17:52:53	localhost	dhclient	All rights reserved.

12/08/06 17:52:53	localhost	dhclient	Copyright 2004-2005 Internet Systems Consortium.

12/08/06 17:52:53	localhost	dhclient	DHCPRELEASE on eth1 to 192.168.1.1 port 67

12/08/06 17:52:53	localhost	dhclient	For info, please visit [url]http://www.isc.org/products/DHCP[/url]

12/08/06 17:52:53	localhost	dhclient	Internet Systems Consortium DHCP Client V3.0.3

12/08/06 17:52:53	localhost	dhclient	Listening on LPF/eth1/00:12:f0:d3:12:24

12/08/06 17:52:53	localhost	dhclient	Sending on  LPF/eth1/00:12:f0:d3:12:24

12/08/06 17:52:53	localhost	dhclient	Sending on  Socket/fallback

12/08/06 17:52:53	localhost	dhclient	send_packet: Network is unreachable

12/08/06 17:52:53	localhost	dhclient	send_packet: please consult README file regarding broadcast address.

12/08/06 17:52:54	localhost	dhclient	

12/08/06 17:52:54	localhost	dhclient	All rights reserved.

12/08/06 17:52:54	localhost	dhclient	Copyright 2004-2005 Internet Systems Consortium.

12/08/06 17:52:54	localhost	dhclient	For info, please visit [url]http://www.isc.org/products/DHCP[/url]

12/08/06 17:52:54	localhost	dhclient	Internet Systems Consortium DHCP Client V3.0.3

12/08/06 17:52:55	localhost	dhclient	Listening on LPF/eth1/00:12:f0:d3:12:24

12/08/06 17:52:55	localhost	dhclient	Sending on  LPF/eth1/00:12:f0:d3:12:24

12/08/06 17:52:55	localhost	dhclient	Sending on  Socket/fallback

12/08/06 17:52:58	localhost	dhclient	DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 3

12/08/06 17:53:01	localhost	dhclient	DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 5

12/08/06 17:53:06	localhost	dhclient	DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 14

12/08/06 17:53:20	localhost	dhclient	DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 11

12/08/06 17:53:31	localhost	dhclient	DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 10


12/08/06 17:53:41	localhost	dhclient	DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 18

12/08/06 17:53:59	localhost	dhclient	No DHCPOFFERS received.

12/08/06 17:53:59	localhost	dhclient	No working leases in persistent database - sleeping.

Eth0 is the wired device, and Eth1 is the wireless.
Hope that is of any help?
~Shiv

[shiv_379]

Re: Wireless device suddenly not working

I've not made any progress on this, however I have found out some more things that might help someone else make sense of this situation?

First of all, using the Wifi Manager instead of KNetwork manager it can see the wireless networks but can't seem to connect to any of them.

In console mode I noticed that if I turn the wireless switch off at the front of the laptop nothing overt happens, however if I switch it on again I get the kernel error:

[17182607.236000] ipw2200: Failed to send SCAN_ABORT: Command timed out.
[17182608.252000] ipw2200: Failed to send CARD_DISABLE: Command timed out.

Another thing that might be of use, an "iwlist eth1 scanning" gives:

eth1   Scan completed :
     Cell 01 - Address: 00:11:F5:9E:E1:73
          ESSID:"BTVOYAGER2091-73"
          Protocol:IEEE 802.11bg
          Mode:Master
          Channel:6
          Encryption key:on
          Bit Rates:54 Mb/s
          Extra: Rates (Mb/s): 1 2 5.5 6 9 11 12 18 24 36 48 54 
          Quality=68/100 Signal level=-59 dBm 
          Extra: Last beacon: 364ms ago
     Cell 02 - Address: 00:11:F5:98:7D:80
          ESSID:"BTVOYAGER2091-80"
          Protocol:IEEE 802.11bg
          Mode:Master
          Channel:8
          Encryption key:on
          Bit Rates:54 Mb/s
          Extra: Rates (Mb/s): 1 2 5.5 6 9 11 12 18 24 36 48 54 
          Quality=33/100 Signal level=-80 dBm 
          Extra: Last beacon: 360ms ago
     Cell 03 - Address: 00:14:BF:61:ED:D0
          ESSID:"Duncan"
          Protocol:IEEE 802.11bg
          Mode:Master
          Channel:10
          Encryption key:on
          Bit Rates:54 Mb/s
          Extra: Rates (Mb/s): 1 2 5.5 6 9 11 12 18 24 36 48 54 
          Quality=41/100 Signal level=-76 dBm 
          Extra: Last beacon: 940ms ago
     Cell 04 - Address: 00:0F:B5:B4:25:6E
          ESSID:"NETGEAR"
          Protocol:IEEE 802.11bg
          Mode:Master
          Channel:11
          Encryption key:off
          Bit Rates:54 Mb/s
          Extra: Rates (Mb/s): 1 2 5.5 9 11 6 12 18 24 36 48 54 
          Quality=85/100 Signal level=-84 dBm 
          Extra: Last beacon: 3372ms ago
     Cell 05 - Address: 00:14:7C:B7:4F:F2
          ESSID:"Hobgoblin"
          Protocol:IEEE 802.11bg
          Mode:Master
          Channel:13
          Encryption key:on
          Bit Rates:54 Mb/s
          Extra: Rates (Mb/s): 1 2 5.5 6 9 11 12 18 22 24 36 48 54 
          Quality=85/100 Signal level=-45 dBm 
          Extra: Last beacon: 248ms ago
     Cell 06 - Address: 00:0F:B5:BB:D0:D8
          ESSID:"<hidden>"
          Protocol:IEEE 802.11bg
          Mode:Master
          Channel:12
          Encryption key:on
          Bit Rates:54 Mb/s
          Extra: Rates (Mb/s): 1 2 5.5 9 11 6 12 18 24 36 48 54 
          Quality=46/100 Signal level=-73 dBm 
          IE: WPA Version 1
            Group Cipher : TKIP 
            Pairwise Ciphers (1) : TKIP 
            Authentication Suites (1) : PSK 
          Extra: Last beacon: 3308ms ago

How do you connect to a wireless network in console mode? I hade a poke around iwconfig,ifconfig, and iwlist but I couldn't figure out how to do...well, anything!

~Shiv