LinuxQuestions.org
Welcome to the most active Linux Forum on the web.
Home Forums Tutorials Articles Register
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
Reload this Page Odd wireless problem with Slackware-current on Latitude 110L
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 12-06-2009, 11:16 AM   #1
easuter
Member
 
Registered: Dec 2005
Location: Portugal
Distribution: Slackware64 13.0, Slackware64 13.1
Posts: 538

Rep: Reputation: 62
Odd wireless problem with Slackware-current on Latitude 110L

Hi,

I installed Slackware-current on a Dell Latitude 110L laptop, and so far everything is working fine except for an odd wireless problem: when connecting to a wireless network with WPA-PSK, the connection lasts only a few seconds before dying.
The laptop has a built-in Intel 2200 wireless chip driven by the ipw2200 module.

I generally use Wicd to manage my wireless network connections, so I thought that perhaps it might be a problem with this program, however even if I manually configure and launch wpa_supplicant + dhcpcd, the connection still falls after a few seconds.

Here is a snippet of my /var/log/messages during the time I insert the kernel module, bring up the interface, authenticate with wpa_supplicant and then use dhcpcd to get an IP address:

Code:
Dec  5 18:24:51 sirius kernel: ipw2200 0000:02:03.0: PCI INT A disabled
Dec  5 18:25:40 sirius kernel: ieee80211: 802.11 data/management/control stack, git-1.1.13
Dec  5 18:25:40 sirius kernel: ieee80211: Copyright (C) 2004-2005 Intel Corporation <jketreno@linux.intel.com>
Dec  5 18:25:40 sirius kernel: ipw2200: Intel(R) PRO/Wireless 2200/2915 Network Driver, 1.2.2kmprq
Dec  5 18:25:40 sirius kernel: ipw2200: Copyright(c) 2003-2006 Intel Corporation
Dec  5 18:25:40 sirius kernel: ipw2200 0000:02:03.0: PCI INT A -> GSI 19 (level, low) -> IRQ 19
Dec  5 18:25:40 sirius kernel: ipw2200: Detected Intel PRO/Wireless 2200BG Network Connection
Dec  5 18:25:40 sirius kernel: ipw2200 0000:02:03.0: firmware: requesting ipw2200-bss.fw
Dec  5 18:25:40 sirius kernel: ipw2200: Detected geography ZZD (13 802.11bg channels, 0 802.11a channels)
Dec  5 18:27:00 sirius dhcpcd[4138]: eth1: dhcpcd 3.2.3 starting
Dec  5 18:27:00 sirius dhcpcd[4138]: eth1: hardware address = 00:16:6f:15:b7:1f
Dec  5 18:27:00 sirius dhcpcd[4138]: eth1: DUID = 00:01:00:01:12:ac:20:94:00:14:22:bf:fb:19
Dec  5 18:27:00 sirius dhcpcd[4138]: eth1: broadcasting for a lease
Dec  5 18:27:00 sirius dhcpcd[4138]: eth1: offered 192.168.2.102 from 192.168.2.1
Dec  5 18:27:00 sirius dhcpcd[4138]: eth1: checking 192.168.2.102 is available on attached networks
Dec  5 18:27:01 sirius dhcpcd[4138]: eth1: leased 192.168.2.102 for infinity
Dec  5 18:27:01 sirius dhcpcd[4138]: eth1: adding IP address 192.168.2.102/24
Dec  5 18:27:01 sirius dhcpcd[4138]: eth1: adding default route via 192.168.2.1 metric 0
Dec  5 18:27:01 sirius dhcpcd[4138]: eth1: adding route to 169.254.0.0/16 metric 0
Dec  5 18:27:01 sirius dhcpcd[4138]: eth1: exiting
Dec  5 18:27:15 sirius dhcpcd[4149]: eth1: sending signal 1 to pid 4139
Dec  5 18:27:15 sirius dhcpcd[4139]: eth1: received SIGHUP, releasing lease
Dec  5 18:27:15 sirius dhcpcd[4139]: eth1: removing default route via 192.168.2.1 metric 0
Dec  5 18:27:15 sirius dhcpcd[4139]: eth1: removing route to 169.254.0.0/16 metric 0
Dec  5 18:27:15 sirius dhcpcd[4139]: eth1: removing IP address 192.168.2.102/24
Dec  5 18:27:15 sirius dhcpcd[4139]: eth1: exiting
Dec  5 18:27:15 sirius dhcpcd[4149]: eth1: exiting
Dec  5 18:27:25 sirius kernel: ADDRCONF(NETDEV_UP): eth1: link is not ready
In the lines I highlighted, the dhcpcd daemon looks like it's committing suicide or something
Note that if I don't call dhcpcd, then the interface stays up and wpa_supplicant maintains the authentication with the router just fine.
Its only after I call dhcpcd that I lose my connection.

Next I tried a wireless USB dongle, and I managed to connect and maintain the connection without problems, but the log still shows dhcpcd dying once and then reconnecting:

Code:
Dec  5 18:42:18 sirius kernel: usb 1-3: USB disconnect, address 2                                              
Dec  5 18:42:21 sirius kernel: usb 1-1: new high speed USB device using ehci_hcd and address 3                 
Dec  5 18:42:22 sirius kernel: usb 1-1: New USB device found, idVendor=083a, idProduct=b522                    
Dec  5 18:42:22 sirius kernel: usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3               
Dec  5 18:42:22 sirius kernel: usb 1-1: Product: EZ Connect N Draft 11n Wireless USB2.0 Adapter                
Dec  5 18:42:22 sirius kernel: usb 1-1: Manufacturer: SMC                                                      
Dec  5 18:42:22 sirius kernel: usb 1-1: configuration #1 chosen from 1 choice                                  
Dec  5 18:42:22 sirius kernel: usbcore: registered new interface driver rt2870                                 
Dec  5 18:43:48 sirius dhcpcd[4815]: ra0: dhcpcd 3.2.3 starting                                                
Dec  5 18:43:48 sirius dhcpcd[4815]: ra0: hardware address = 00:13:f7:98:9c:08                                 
Dec  5 18:43:48 sirius dhcpcd[4815]: ra0: DUID = 00:01:00:01:12:ac:20:94:00:14:22:bf:fb:19                     
Dec  5 18:43:48 sirius dhcpcd[4815]: ra0: broadcasting for a lease                                             
Dec  5 18:43:49 sirius dhcpcd[4815]: ra0: offered 192.168.2.103 from 192.168.2.1                               
Dec  5 18:43:49 sirius dhcpcd[4815]: ra0: checking 192.168.2.103 is available on attached networks
Dec  5 18:43:50 sirius dhcpcd[4815]: ra0: leased 192.168.2.103 for infinity
Dec  5 18:43:50 sirius dhcpcd[4815]: ra0: adding IP address 192.168.2.103/24
Dec  5 18:43:50 sirius dhcpcd[4815]: ra0: adding default route via 192.168.2.1 metric 0
Dec  5 18:43:50 sirius dhcpcd[4815]: ra0: adding route to 169.254.0.0/16 metric 0
Dec  5 18:43:50 sirius dhcpcd[4815]: ra0: exiting
Dec  5 18:44:12 sirius dbus-daemon: Reloaded configuration
Dec  5 18:44:14 sirius dbus-daemon: Reloaded configuration
Dec  5 18:44:34 sirius kernel: ADDRCONF(NETDEV_UP): eth1: link is not ready
Dec  5 18:45:39 sirius dhcpcd[5231]: ra0: sending signal 1 to pid 4818
Dec  5 18:45:39 sirius dhcpcd[4818]: ra0: received SIGHUP, releasing lease
Dec  5 18:45:39 sirius dhcpcd[4818]: ra0: removing default route via 192.168.2.1 metric 0
Dec  5 18:45:39 sirius dhcpcd[4818]: ra0: removing route to 169.254.0.0/16 metric 0
Dec  5 18:45:39 sirius dhcpcd[4818]: ra0: removing IP address 192.168.2.103/24
Dec  5 18:45:39 sirius dhcpcd[4818]: ra0: exiting
Dec  5 18:45:39 sirius dhcpcd[5231]: ra0: exiting
Dec  5 18:45:40 sirius dhcpcd[5240]: eth0: exiting
Dec  5 18:45:40 sirius kernel: ADDRCONF(NETDEV_UP): eth0: link is not ready
Dec  5 18:45:41 sirius dhcpcd[5246]: ra0: exiting
Dec  5 18:45:42 sirius dhcpcd[5258]: eth0: exiting
Dec  5 18:45:42 sirius kernel: ADDRCONF(NETDEV_UP): eth0: link is not ready
Dec  5 18:45:48 sirius dhcpcd[5271]: eth0: exiting
Dec  5 18:45:48 sirius kernel: ADDRCONF(NETDEV_UP): eth0: link is not ready
Dec  5 18:45:48 sirius dhcpcd[5279]: ra0: exiting
Dec  5 18:45:55 sirius dhcpcd[5301]: ra0: dhcpcd 3.2.3 starting
Dec  5 18:45:55 sirius dhcpcd[5301]: ra0: hardware address = 00:13:f7:98:9c:08
Dec  5 18:45:55 sirius dhcpcd[5301]: ra0: DUID = 00:01:00:01:12:ac:20:94:00:14:22:bf:fb:19
Dec  5 18:45:55 sirius dhcpcd[5301]: ra0: broadcasting for a lease
Dec  5 18:45:55 sirius dhcpcd[5301]: ra0: offered 192.168.2.103 from 192.168.2.1
Dec  5 18:45:55 sirius dhcpcd[5301]: ra0: checking 192.168.2.103 is available on attached networks
Dec  5 18:45:56 sirius dhcpcd[5301]: ra0: leased 192.168.2.103 for infinity
Dec  5 18:45:56 sirius dhcpcd[5301]: ra0: adding IP address 192.168.2.103/24
Dec  5 18:45:56 sirius dhcpcd[5301]: ra0: adding default route via 192.168.2.1 metric 0
Dec  5 18:45:56 sirius dhcpcd[5301]: ra0: adding route to 169.254.0.0/16 metric 0
Dec  5 18:45:56 sirius dhcpcd[5301]: ra0: exiting
So with the dongle, the daemon restarts and reconnects, but this doesn't happen with the on-board wireless card for some reason.
Also, I went to my college campus which has an Eduroam setup (WPA-EAP + TTLS + MSCHAPv2), and there I managed to maintain a stable connection.

Has anyone ever had a similar problem? I really can't fathom this one out.
Last edited by easuter; 12-06-2009 at 02:44 PM.
 
Old 12-07-2009, 04:44 AM   #2
business_kid
LQ Guru
 
Registered: Jan 2006
Location: Ireland
Distribution: Slackware, Slarm64 & Android
Posts: 16,259

Rep: Reputation: 2321Reputation: 2321Reputation: 2321Reputation: 2321Reputation: 2321Reputation: 2321Reputation: 2321Reputation: 2321Reputation: 2321Reputation: 2321Reputation: 2321
Check 2 things
Dec 5 18:25:40 sirius kernel: ipw2200 0000:02:03.0: firmware: requesting ipw2200-bss.fw
Have you the latest firmware? All modern drivers seem to need it.
Also, it is possible to put your key into wpa_supplicant.conf and think that's all you need. Not so Run this command if you haven't already
wpa_passphrase my_essid my_key and that will return

bash-3.1$ wpa_passphrase my_essid my_key_short
network={
ssid="my_essid"
#psk="my_key_short"
psk=3de1dca3d740a5c9cdb6640a44040f9353944a9a695190e3f3d25bfe0cb21fef
}

Put the bit between brackets in wpa_supplicant.conf. It's the long number the thing needs
 
  


Reply



Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Can't get wireless to work on Slackware 12.2/current, Aspire One yhzmet Slackware 2 04-03-2009 10:24 PM
odd problem with wireless under fedora 8 bp787@hotmail.com Linux - Wireless Networking 1 03-12-2008 07:45 AM
Odd problem with xorg radeon drivers on Slackware current Eternal_Newbie Slackware 1 11-23-2007 11:17 AM
dell latitude 110L touchpad problem trecool Mandriva 0 02-15-2007 02:09 AM
latitude 110l wireless problem nathan.payton Linux - Wireless Networking 2 10-22-2006 11:05 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 01:18 PM.

Contact Us - Advertising Info - Rules - Privacy - LQ Merchandise - Donations - Contributing Member - LQ Sitemap -
Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration