I recently installed Hardy on a friend's laptop only to see that the wireless isn't working. This is odd for me because the drivers and everything seem to be there and working and what not. Basically, we can not connect to anything, not even an open network with no security on it. I have tried 4 other threads in the forums and nothing seems to resolve the problem. We have a fresh, fully updated install of Hardy and are coming here fresh for help and ideas as to what this issue could be.

Here is some of the relevant information that I think will help with the issue at hand: We can not connect/use the wireless connection.

Code:
lshw:

*-network
                description: Wireless interface
                product: PRO/Wireless 3945ABG Network Connection
                vendor: Intel Corporation
                physical id: 0
                bus info: pci@0000:07:00.0
                logical name: wmaster0
                version: 02
                serial: 00:1c:bf:54:ed:f9
                width: 32 bits
                clock: 33MHz
                capabilities: pm msi pciexpress bus_master cap_list logical ethernet physical wireless
                configuration: broadcast=yes driver=iwl3945 latency=0 module=iwl3945 multicast=yes wireless=IEEE 802.11g
Code:
ifconfig

wlan0     Link encap:Ethernet  HWaddr 00:1c:bf:54:ed:f9  
          inet6 addr: fe80::21c:bfff:fe54:edf9/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:104 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 B)  TX bytes:13977 (13.6 KB)

wlan0:avahi Link encap:Ethernet  HWaddr 00:1c:bf:54:ed:f9  
          inet addr:169.254.11.40  Bcast:169.254.255.255  Mask:255.255.0.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1

wmaster0  Link encap:UNSPEC  HWaddr 00-1C-BF-54-ED-F9-00-00-00-00-00-00-00-00-00-00  
          UP BROADCAST RUNNING 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)
Code:
iwconfig

wmaster0  no wireless extensions.

wlan0     IEEE 802.11g  ESSID:"OurPlace"  Nickname:""
          Mode:Managed  Frequency:2.417 GHz  Access Point: 00:0B:B4:EE:11:4D   
          Tx-Power=27 dBm   
          Retry min limit:7   RTS thr:off   Fragment thr=2346 B   
          Encryption key:3939-3939-3936-3636-3636
          Power Management:off
          Link Quality:0  Signal level:0  Noise level:0
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0
Code:
lspci -v

07:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG Network Connection (rev 02)
	Subsystem: Hewlett-Packard Company Unknown device 135d
	Flags: bus master, fast devsel, latency 0, IRQ 217
	Memory at f4300000 (32-bit, non-prefetchable) [size=4K]
	Capabilities: [c8] Power Management version 2
	Capabilities: [d0] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable+
	Capabilities: [e0] Express Legacy Endpoint IRQ 0
Basically, everything shows up in network manager and such, (though on my machine I can detect networks, but this machine does not seem to do that, even when in roaming mode). We are using WEP for our security, though even testing on an open network didn't work. I know the network is ok because we can connect with anything else (psp, ps3, my gentoo notebook, etc).

Let me know if you would like anything else, here is a quick bit of information I grabbed from /var/log/messages | grep iwl

Code:
 /var/log/messages | grep iwl

May 31 07:57:16 ubuntu kernel: [   30.052423] iwl3945: Intel(R) PRO/Wireless 3945ABG/BG Network Connection driver for Linux, 1.2.0
May 31 07:57:16 ubuntu kernel: [   30.052426] iwl3945: Copyright(c) 2003-2007 Intel Corporation
May 31 07:57:16 ubuntu kernel: [   30.052618] iwl3945: Detected Intel PRO/Wireless 3945ABG Network Connection
May 31 07:57:16 ubuntu kernel: [   30.995270] iwl3945: Tunable channels: 13 802.11bg, 4 802.11a channels
May 31 01:04:37 ubuntu kernel: [   29.579868] iwl3945: Intel(R) PRO/Wireless 3945ABG/BG Network Connection driver for Linux, 1.2.0
May 31 01:04:37 ubuntu kernel: [   29.579872] iwl3945: Copyright(c) 2003-2007 Intel Corporation
May 31 01:04:37 ubuntu kernel: [   29.580011] iwl3945: Detected Intel PRO/Wireless 3945ABG Network Connection
May 31 01:04:37 ubuntu kernel: [   30.784480] iwl3945: Tunable channels: 13 802.11bg, 4 802.11a channels
May 31 01:29:30 ubuntu kernel: [   31.993087] iwl3945: Intel(R) PRO/Wireless 3945ABG/BG Network Connection driver for Linux, 1.2.0
May 31 01:29:30 ubuntu kernel: [   31.993091] iwl3945: Copyright(c) 2003-2007 Intel Corporation
May 31 01:29:30 ubuntu kernel: [   31.993224] iwl3945: Detected Intel PRO/Wireless 3945ABG Network Connection
May 31 01:29:30 ubuntu kernel: [   32.894372] iwl3945: Tunable channels: 13 802.11bg, 4 802.11a channels
May 31 10:02:20 ubuntu kernel: [   30.458874] iwl3945: Intel(R) PRO/Wireless 3945ABG/BG Network Connection driver for Linux, 1.2.0
May 31 10:02:20 ubuntu kernel: [   30.458876] iwl3945: Copyright(c) 2003-2007 Intel Corporation
May 31 10:02:20 ubuntu kernel: [   30.459024] iwl3945: Detected Intel PRO/Wireless 3945ABG Network Connection
May 31 10:02:20 ubuntu kernel: [   31.117202] iwl3945: Tunable channels: 13 802.11bg, 4 802.11a channels
May 31 10:54:35 ubuntu kernel: [  146.791841] iwl3945: Radio Frequency Kill Switch is On:
May 31 10:54:58 ubuntu kernel: [  151.445324] iwl3945: Radio Frequency Kill Switch is On:
May 31 10:57:48 ubuntu kernel: [  190.652499] iwl3945: Radio Frequency Kill Switch is On:
May 31 11:50:39 ubuntu kernel: [ 3066.115583] iwl3945: Radio Frequency Kill Switch is On:
May 31 12:18:05 ubuntu kernel: [   30.973712] iwl3945: Intel(R) PRO/Wireless 3945ABG/BG Network Connection driver for Linux, 1.2.0
May 31 12:18:05 ubuntu kernel: [   30.973716] iwl3945: Copyright(c) 2003-2007 Intel Corporation
May 31 12:18:05 ubuntu kernel: [   30.973852] iwl3945: Detected Intel PRO/Wireless 3945ABG Network Connection
May 31 12:18:05 ubuntu kernel: [   31.757780] iwl3945: Tunable channels: 13 802.11bg, 4 802.11a channels
May 31 12:18:53 ubuntu kernel: [   56.045089] iwl3945: Radio Frequency Kill Switch is On:
May 31 14:41:35 ubuntu kernel: [   31.757490] iwl3945: Intel(R) PRO/Wireless 3945ABG/BG Network Connection driver for Linux, 1.2.0
May 31 14:41:35 ubuntu kernel: [   31.757494] iwl3945: Copyright(c) 2003-2007 Intel Corporation
May 31 14:41:35 ubuntu kernel: [   31.757650] iwl3945: Detected Intel PRO/Wireless 3945ABG Network Connection
May 31 14:41:35 ubuntu kernel: [   32.905906] iwl3945: Radio Frequency Kill Switch is On:
May 31 14:41:35 ubuntu kernel: [   32.911055] iwl3945: WARNING: Requesting MAC access during RFKILL wakes up NIC
May 31 14:41:35 ubuntu kernel: [   32.921060] iwl3945: WARNING: Requesting MAC access during RFKILL wakes up NIC
May 31 14:41:35 ubuntu kernel: [   32.940985] iwl3945: WARNING: Requesting MAC access during RFKILL wakes up NIC
May 31 14:41:35 ubuntu kernel: [   32.968233] iwl3945: WARNING: Requesting MAC access during RFKILL wakes up NIC
May 31 14:41:35 ubuntu kernel: [   32.988171] iwl3945: Tunable channels: 13 802.11bg, 4 802.11a channels
May 31 16:24:24 ubuntu kernel: [  354.377805] iwl3945: Radio Frequency Kill Switch is On:
May 31 20:40:07 ubuntu kernel: [   39.340542] iwl3945: Intel(R) PRO/Wireless 3945ABG/BG Network Connection driver for Linux, 1.2.0
May 31 20:40:07 ubuntu kernel: [   39.340545] iwl3945: Copyright(c) 2003-2007 Intel Corporation
May 31 20:40:07 ubuntu kernel: [   39.340675] iwl3945: Detected Intel PRO/Wireless 3945ABG Network Connection
May 31 20:40:07 ubuntu kernel: [   40.023935] iwl3945: Radio Frequency Kill Switch is On:
May 31 20:40:07 ubuntu kernel: [   40.029119] iwl3945: WARNING: Requesting MAC access during RFKILL wakes up NIC
May 31 20:40:07 ubuntu kernel: [   40.039139] iwl3945: WARNING: Requesting MAC access during RFKILL wakes up NIC
May 31 20:40:07 ubuntu kernel: [   40.059080] iwl3945: WARNING: Requesting MAC access during RFKILL wakes up NIC
May 31 20:40:07 ubuntu kernel: [   40.086354] iwl3945: WARNING: Requesting MAC access during RFKILL wakes up NIC
May 31 20:40:07 ubuntu kernel: [   40.106276] iwl3945: Tunable channels: 13 802.11bg, 4 802.11a channels
May 31 21:16:12 ubuntu kernel: [  186.964934] iwl3945: Intel(R) PRO/Wireless 3945ABG/BG Network Connection driver for Linux, 1.2.25
May 31 21:16:12 ubuntu kernel: [  186.964950] iwl3945: Copyright(c) 2003-2007 Intel Corporation
May 31 21:16:12 ubuntu kernel: [  186.965110] iwl3945: Detected Intel PRO/Wireless 3945ABG Network Connection
May 31 21:16:12 ubuntu kernel: [  187.053332] iwl3945: Tunable channels: 13 802.11bg, 4 802.11a channels
May 31 21:16:12 ubuntu kernel: [  187.054325] Registered led device: iwl-phy1:RX
May 31 21:16:12 ubuntu kernel: [  187.054344] Registered led device: iwl-phy1:TX
May 31 21:16:15 ubuntu kernel: [  188.363991] Registered led device: iwl-phy1:RX
May 31 21:16:15 ubuntu kernel: [  188.364036] Registered led device: iwl-phy1:TX
May 31 21:16:17 ubuntu kernel: [  189.638366] Registered led device: iwl-phy1:RX
May 31 21:16:17 ubuntu kernel: [  189.638394] Registered led device: iwl-phy1:TX
May 31 21:16:51 ubuntu kernel: [  195.880313] Registered led device: iwl-phy1:RX
May 31 21:16:51 ubuntu kernel: [  195.880342] Registered led device: iwl-phy1:TX
May 31 21:16:54 ubuntu kernel: [  197.625701] Registered led device: iwl-phy1:RX
May 31 21:16:54 ubuntu kernel: [  197.625720] Registered led device: iwl-phy1:TX
May 31 21:16:56 ubuntu kernel: [  198.853148] Registered led device: iwl-phy1:RX
May 31 21:16:56 ubuntu kernel: [  198.853166] Registered led device: iwl-phy1:TX
May 31 21:17:20 ubuntu kernel: [  202.412216] Registered led device: iwl-phy1:RX
May 31 21:17:20 ubuntu kernel: [  202.412246] Registered led device: iwl-phy1:TX
May 31 21:17:22 ubuntu kernel: [  203.547342] Registered led device: iwl-phy1:RX
May 31 21:17:22 ubuntu kernel: [  203.547360] Registered led device: iwl-phy1:TX
I am not sure if the problem lies in the messages log, I do see those big WARNING signs though... If any more information is needed, please do ask, we would both love to see this one resolved.

Thanks in advance!