11-02-2008
#1 (permalink )
Linux User
Join Date: Aug 2005
Location: The Netherlands
Posts: 291
Module is loaded, how do I connect now? (Debian, Gnome)
Hello,
I've just installed Debian Lenny on my HP 8710w GC124EA Laptop and want to connect to my wireless WPA protected home network. I have Ubuntu on another partition, and there wireless worked out of the box.
On
HP-Compaq 8710W - Linux Laptop Wiki it says use the iwl4965 driver. This driver has been loaded in Debian automatically. However, iwconfig gives no results.
How do I connect now?
Code:
daan@schmauck:~$ sudo ifconfig
eth0 Link encap:Ethernet HWaddr 00:1b:38:f8:09:78
inet addr:192.168.1.68 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::21b:38ff:fef8:978/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:21676 errors:0 dropped:0 overruns:0 frame:0
TX packets:13863 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:28691718 (27.3 MiB) TX bytes:1285511 (1.2 MiB)
Base address:0x5040 Memory:e8020000-e8040000
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:66 errors:0 dropped:0 overruns:0 frame:0
TX packets:66 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:5104 (4.9 KiB) TX bytes:5104 (4.9 KiB)
daan@schmauck:~$ sudo iwconfig
lo no wireless extensions.
eth0 no wireless extensions.
daan@schmauck:~$ lsmod | grep iwl4965
iwl4965 98312 0
firmware_class 9312 2 pcmcia,iwl4965
mac80211 114380 1 iwl4965
daan@schmauck:~$ locate iwl4965
/lib/modules/2.6.24-1-686/kernel/drivers/net/wireless/iwlwifi/iwl4965.ko
/lib/modules/2.6.26-1-686/kernel/drivers/net/wireless/iwlwifi/iwl4965.ko
/mnt/sda5/lib/modules/2.6.24-21-generic/ubuntu/wireless/iwlwifi/iwlwifi/compatible/iwl4965.ko
daan@schmauck:~$
__________________ OS's I use: Debian Lenny , Windows XP, Windows Vista
11-02-2008
#2 (permalink )
Linux User
Join Date: Aug 2005
Location: The Netherlands
Posts: 291
OK, so after a reboot I do get results from iwconfig...
__________________ OS's I use: Debian Lenny , Windows XP, Windows Vista
11-02-2008
#3 (permalink )
Linux User
Join Date: Aug 2005
Location: The Netherlands
Posts: 291
I am in Gnome, and when I left click the little network icon in the top right, there are no wireless networks to choose from. When I choose "Connect to Other Wireless Network..." and fill in the details of my wireless home network, it tries to connect, but without success.
What can I do?
__________________ OS's I use: Debian Lenny , Windows XP, Windows Vista
11-02-2008
#4 (permalink )
Trusted Penguin
Join Date: Jul 2004
Location: Franklin, Wisconsin
Posts: 3,957
Right-click on that same icon, and make sure "Enable wireless" is checked.
__________________
Paul
Please do not PM me with requests for help. I will not reply.
11-02-2008
#5 (permalink )
Linux User
Join Date: Aug 2005
Location: The Netherlands
Posts: 291
Hi waterhead,
It was enabled all the time. Also, the wireless icon above my keyboard is switched on.
Here's some more info that might help:
Code:
schmauck:/home/daan# ifconfig
eth0 Link encap:Ethernet HWaddr 00:1b:38:f8:09:78
inet addr:192.168.1.68 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::21b:38ff:fef8:978/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1182 errors:0 dropped:0 overruns:0 frame:0
TX packets:1170 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:354893 (346.5 KiB) TX bytes:253185 (247.2 KiB)
Memory:e8020000-e8040000
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:95 errors:0 dropped:0 overruns:0 frame:0
TX packets:95 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:6365 (6.2 KiB) TX bytes:6365 (6.2 KiB)
schmauck:/home/daan# iwconfig
lo no wireless extensions.
eth0 no wireless extensions.
wmaster0 no wireless extensions.
wlan0 IEEE 802.11 ESSID:""
Mode:Managed Frequency:2.412 GHz Access Point: Not-Associated
Tx-Power=0 dBm
Retry min limit:7 RTS thr:off Fragment thr=2352 B
Encryption key: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
schmauck:/home/daan# lspci | grep 4965
10:00.0 Network controller: Intel Corporation PRO/Wireless 4965 AG or AGN [Kedron] Network Connection (rev 61)
schmauck:/home/daan# lsmod | grep 4965
iwl4965 92904 0
firmware_class 6816 2 pcmcia,iwl4965
iwlcore 23520 1 iwl4965
mac80211 139680 2 iwl4965,iwlcore
cfg80211 21576 2 iwl4965,mac80211
schmauck:/home/daan#
__________________ OS's I use: Debian Lenny , Windows XP, Windows Vista
11-02-2008
#6 (permalink )
Linux User
Join Date: Aug 2005
Location: The Netherlands
Posts: 291
And:
Code:
schmauck:/home/daan# iwlist wlan0 scanning
wlan0 Interface doesn't support scanning : Network is down
__________________ OS's I use: Debian Lenny , Windows XP, Windows Vista
11-02-2008
#7 (permalink )
Linux User
Join Date: Aug 2005
Location: The Netherlands
Posts: 291
And more:
Code:
schmauck:/home/daan# ifconfig wlan0 up
SIOCSIFFLAGS: No such file or directory
__________________ OS's I use: Debian Lenny , Windows XP, Windows Vista
11-02-2008
#8 (permalink )
Trusted Penguin
Join Date: Jul 2004
Location: Franklin, Wisconsin
Posts: 3,957
NetworkManager (that icon) can't handle a wired and wireless network simultaneously. Unplug the wired connection, and run these commands.
The wireless also needs firmware to work. It looks like it is present, but run this command to check.
Code:
dmesg | grep firmware
__________________
Paul
Please do not PM me with requests for help. I will not reply.
11-02-2008
#9 (permalink )
Linux User
Join Date: Aug 2005
Location: The Netherlands
Posts: 291
I did the following withe the network cable unplugged:
Code:
schmauck:/home/daan# dmesg | grep firmware
[ 35.690147] firmware: requesting iwlwifi-4965-1.ucode
[ 35.751430] iwl4965: iwlwifi-4965-1.ucode firmware file req failed: Reason -2
[ 38.795002] firmware: requesting iwlwifi-4965-1.ucode
[ 38.796437] iwl4965: iwlwifi-4965-1.ucode firmware file req failed: Reason -2
[ 55.921970] firmware: requesting iwlwifi-4965-1.ucode
[ 55.932613] iwl4965: iwlwifi-4965-1.ucode firmware file req failed: Reason -2
[ 69.569395] firmware: requesting iwlwifi-4965-1.ucode
[ 69.577999] iwl4965: iwlwifi-4965-1.ucode firmware file req failed: Reason -2
[ 73.202911] firmware: requesting iwlwifi-4965-1.ucode
[ 73.213125] iwl4965: iwlwifi-4965-1.ucode firmware file req failed: Reason -2
[ 91.677746] firmware: requesting iwlwifi-4965-1.ucode
[ 91.685859] iwl4965: iwlwifi-4965-1.ucode firmware file req failed: Reason -2
[ 95.331943] firmware: requesting iwlwifi-4965-1.ucode
[ 95.334925] iwl4965: iwlwifi-4965-1.ucode firmware file req failed: Reason -2
[ 113.813902] firmware: requesting iwlwifi-4965-1.ucode
[ 113.825291] iwl4965: iwlwifi-4965-1.ucode firmware file req failed: Reason -2
[ 117.429127] firmware: requesting iwlwifi-4965-1.ucode
[ 117.437130] iwl4965: iwlwifi-4965-1.ucode firmware file req failed: Reason -2
[ 135.977422] firmware: requesting iwlwifi-4965-1.ucode
[ 135.985655] iwl4965: iwlwifi-4965-1.ucode firmware file req failed: Reason -2
[ 139.561315] firmware: requesting iwlwifi-4965-1.ucode
[ 139.569497] iwl4965: iwlwifi-4965-1.ucode firmware file req failed: Reason -2
[ 158.284715] firmware: requesting iwlwifi-4965-1.ucode
[ 158.295117] iwl4965: iwlwifi-4965-1.ucode firmware file req failed: Reason -2
[ 161.869138] firmware: requesting iwlwifi-4965-1.ucode
[ 161.872776] iwl4965: iwlwifi-4965-1.ucode firmware file req failed: Reason -2
[ 180.490681] firmware: requesting iwlwifi-4965-1.ucode
[ 180.502614] iwl4965: iwlwifi-4965-1.ucode firmware file req failed: Reason -2
[ 184.044909] firmware: requesting iwlwifi-4965-1.ucode
[ 184.053489] iwl4965: iwlwifi-4965-1.ucode firmware file req failed: Reason -2
[ 202.716028] firmware: requesting iwlwifi-4965-1.ucode
[ 202.727994] iwl4965: iwlwifi-4965-1.ucode firmware file req failed: Reason -2
[ 206.280712] firmware: requesting iwlwifi-4965-1.ucode
[ 206.291058] iwl4965: iwlwifi-4965-1.ucode firmware file req failed: Reason -2
[ 324.890580] firmware: requesting iwlwifi-4965-1.ucode
[ 324.898746] iwl4965: iwlwifi-4965-1.ucode firmware file req failed: Reason -2
[ 328.480920] firmware: requesting iwlwifi-4965-1.ucode
[ 328.490740] iwl4965: iwlwifi-4965-1.ucode firmware file req failed: Reason -2
[ 447.078487] firmware: requesting iwlwifi-4965-1.ucode
[ 447.087080] iwl4965: iwlwifi-4965-1.ucode firmware file req failed: Reason -2
[ 450.672897] firmware: requesting iwlwifi-4965-1.ucode
[ 450.681007] iwl4965: iwlwifi-4965-1.ucode firmware file req failed: Reason -2
[ 569.282169] firmware: requesting iwlwifi-4965-1.ucode
[ 569.293744] iwl4965: iwlwifi-4965-1.ucode firmware file req failed: Reason -2
[ 572.865434] firmware: requesting iwlwifi-4965-1.ucode
[ 572.873482] iwl4965: iwlwifi-4965-1.ucode firmware file req failed: Reason -2
[ 692.041210] firmware: requesting iwlwifi-4965-1.ucode
[ 692.049309] iwl4965: iwlwifi-4965-1.ucode firmware file req failed: Reason -2
[ 695.615760] firmware: requesting iwlwifi-4965-1.ucode
[ 695.624205] iwl4965: iwlwifi-4965-1.ucode firmware file req failed: Reason -2
[ 814.547730] firmware: requesting iwlwifi-4965-1.ucode
[ 814.557484] iwl4965: iwlwifi-4965-1.ucode firmware file req failed: Reason -2
[ 818.166732] firmware: requesting iwlwifi-4965-1.ucode
[ 818.166774] iwl4965: iwlwifi-4965-1.ucode firmware file req failed: Reason -2
[ 937.309618] firmware: requesting iwlwifi-4965-1.ucode
[ 937.317927] iwl4965: iwlwifi-4965-1.ucode firmware file req failed: Reason -2
[ 940.873619] firmware: requesting iwlwifi-4965-1.ucode
[ 940.884415] iwl4965: iwlwifi-4965-1.ucode firmware file req failed: Reason -2
[ 1059.927128] firmware: requesting iwlwifi-4965-1.ucode
[ 1059.935466] iwl4965: iwlwifi-4965-1.ucode firmware file req failed: Reason -2
[ 1061.138553] firmware: requesting iwlwifi-4965-1.ucode
[ 1061.153377] iwl4965: iwlwifi-4965-1.ucode firmware file req failed: Reason -2
[ 1063.482033] firmware: requesting iwlwifi-4965-1.ucode
[ 1063.491256] iwl4965: iwlwifi-4965-1.ucode firmware file req failed: Reason -2
[ 1182.752538] firmware: requesting iwlwifi-4965-1.ucode
[ 1182.759981] iwl4965: iwlwifi-4965-1.ucode firmware file req failed: Reason -2
[ 1186.293478] firmware: requesting iwlwifi-4965-1.ucode
[ 1186.301687] iwl4965: iwlwifi-4965-1.ucode firmware file req failed: Reason -2
[ 1305.377421] firmware: requesting iwlwifi-4965-1.ucode
[ 1305.385528] iwl4965: iwlwifi-4965-1.ucode firmware file req failed: Reason -2
[ 1308.907875] firmware: requesting iwlwifi-4965-1.ucode
[ 1308.915910] iwl4965: iwlwifi-4965-1.ucode firmware file req failed: Reason -2
[ 1428.072163] firmware: requesting iwlwifi-4965-1.ucode
[ 1428.082038] iwl4965: iwlwifi-4965-1.ucode firmware file req failed: Reason -2
[ 1431.605872] firmware: requesting iwlwifi-4965-1.ucode
[ 1431.614576] iwl4965: iwlwifi-4965-1.ucode firmware file req failed: Reason -2
[ 1550.466179] firmware: requesting iwlwifi-4965-1.ucode
[ 1550.478083] iwl4965: iwlwifi-4965-1.ucode firmware file req failed: Reason -2
[ 1553.988563] firmware: requesting iwlwifi-4965-1.ucode
[ 1553.998633] iwl4965: iwlwifi-4965-1.ucode firmware file req failed: Reason -2
schmauck:/home/daan# ifdown eth0
RTNETLINK answers: No such process
Internet Systems Consortium DHCP Client V3.1.1
Copyright 2004-2008 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/
wmaster0: unknown hardware address type 801
wmaster0: unknown hardware address type 801
Listening on LPF/eth0/00:1b:38:f8:09:78
Sending on LPF/eth0/00:1b:38:f8:09:78
Sending on Socket/fallback
DHCPRELEASE on eth0 to 192.168.1.254 port 67
send_packet: Network is unreachable
send_packet: please consult README file regarding broadcast address.
schmauck:/home/daan# ifup wlan0
Ignoring unknown interface wlan0=wlan0.
schmauck:/home/daan# ping uva.nl
ping: unknown host uva.nl
schmauck:/home/daan# /etc/init.d/networking restart
Reconfiguring network interfaces...Internet Systems Consortium DHCP Client V3.1.1
Copyright 2004-2008 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/
wmaster0: unknown hardware address type 801
wmaster0: unknown hardware address type 801
Listening on LPF/eth0/00:1b:38:f8:09:78
Sending on LPF/eth0/00:1b:38:f8:09:78
Sending on Socket/fallback
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 4
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 9
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 17
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 15
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 8
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 8
No DHCPOFFERS received.
No working leases in persistent database - sleeping.
done.
schmauck:/home/daan#
__________________ OS's I use: Debian Lenny , Windows XP, Windows Vista
11-02-2008
#10 (permalink )
Linux User
Join Date: Aug 2005
Location: The Netherlands
Posts: 291
Code:
schmauck:/home/daan# dmesg | tail -10
[ 2522.893181] firmware: requesting iwlwifi-4965-1.ucode
[ 2522.901984] iwl4965: iwlwifi-4965-1.ucode firmware file req failed: Reason -2
[ 2522.901995] iwl4965: Could not read microcode: -2
[ 2522.902082] ACPI: PCI interrupt for device 0000:10:00.0 disabled
[ 2524.961125] ACPI: PCI Interrupt 0000:10:00.0[A] -> GSI 17 (level, low) -> IRQ 17
[ 2524.961125] PM: Writing back config space on device 0000:10:00.0 at offset 1 (was 100002, writing 100006)
[ 2524.961125] firmware: requesting iwlwifi-4965-1.ucode
[ 2524.970318] iwl4965: iwlwifi-4965-1.ucode firmware file req failed: Reason -2
[ 2524.970329] iwl4965: Could not read microcode: -2
[ 2524.970415] ACPI: PCI interrupt for device 0000:10:00.0 disabled
schmauck:/home/daan#
__________________ OS's I use: Debian Lenny , Windows XP, Windows Vista
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)
Thread Tools Display Modes Linear Mode
Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
HTML code is Off