LinuxQuestions.org
Go Job Hunting at the LQ Job Marketplace
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices

Reply
 
Search this Thread
Old 09-19-2012, 09:23 PM   #1
bigfoot cascadia
LQ Newbie
 
Registered: May 2008
Posts: 10

Rep: Reputation: 0
Slack_64-13.37 wicd


I'm using Slack 64-13.37 on a Thinkpad 550SC. I just started having repeated connection drops with wicd-1.7.2.1_slack64_13.37-2. I hooked up a CAT-5 cable an continued to get repeated connection drops. I was finally able to FTP wicd-1.7.2.1-slack64_13.37-1 and replaced the version 2 with the version 1. This fixed the problem and I have had no further connection problems. I wonder if this is connected with the update to the dhcp package lst week?

Here is a section of my debug log:

Quote:
Sep 19 18:43:05 palantir kernel: [ 3576.010021] wlan0: no IPv6 routers present
Sep 19 18:44:20 palantir kernel: [ 3651.217122] ieee80211 phy0: wlan0: No probe response from AP 00:18:e7:c8:c1:30 after 500ms, disconnecting.
Sep 19 18:47:34 palantir kernel: [ 3844.730023] eth0: no IPv6 routers present
Sep 19 18:47:51 palantir kernel: [ 3861.474062] eth0: no IPv6 routers present
Sep 19 18:48:32 palantir kernel: [ 3902.674021] eth0: no IPv6 routers present
Sep 19 18:49:38 palantir kernel: [ 3968.898017] eth0: no IPv6 routers present
Sep 19 18:49:50 palantir kernel: [ 3980.674110] eth0: no IPv6 routers present
Sep 19 18:51:18 palantir kernel: [ 4068.706100] eth0: no IPv6 routers present
Sep 19 18:56:15 palantir kernel: [ 4366.044974] wlan0: authenticate with 00:18:e7:c8:c1:30 (try 1)
Sep 19 18:56:15 palantir kernel: [ 4366.047239] wlan0: authenticated
Sep 19 18:56:15 palantir kernel: [ 4366.047280] wlan0: associate with 00:18:e7:c8:c1:30 (try 1)
Sep 19 18:56:15 palantir kernel: [ 4366.049675] wlan0: RX AssocResp from 00:18:e7:c8:c1:30 (capab=0x431 status=0 aid=1)
Sep 19 18:56:15 palantir kernel: [ 4366.049679] wlan0: associated
Sep 19 18:56:26 palantir kernel: [ 4376.770095] wlan0: no IPv6 routers present
From my syslog:

Quote:
Sep 19 18:48:13 palantir dhcpcd[7631]: timed out
Sep 19 18:48:13 palantir dhcpcd[7656]: dhcpcd not running
Sep 19 18:48:13 palantir dhcpcd[7662]: dhcpcd not running
Sep 19 18:48:21 palantir dhcpcd[7677]: dhcpcd not running
Sep 19 18:48:22 palantir dhcpcd[7683]: dhcpcd not running
Sep 19 18:48:22 palantir dhcpcd[7691]: dhcpcd not running
Sep 19 18:49:26 palantir dhcpcd[7787]: dhcpcd not running
Sep 19 18:49:26 palantir dhcpcd[7793]: dhcpcd not running
Sep 19 18:49:39 palantir dhcpcd[7812]: dhcpcd not running
Sep 19 18:49:39 palantir dhcpcd[7818]: dhcpcd not running
Sep 19 18:49:40 palantir dhcpcd[7826]: dhcpcd not running
Sep 19 18:51:06 palantir dhcpcd[7938]: dhcpcd not running
Sep 19 18:51:06 palantir dhcpcd[7944]: dhcpcd not running
Sep 19 18:56:13 palantir dhcpcd[8899]: dhcpcd not running
Sep 19 18:56:13 palantir dhcpcd[8905]: dhcpcd not running
Sep 19 18:56:13 palantir dhcpcd[8913]: dhcpcd not running
From my message log:

Quote:
Sep 19 18:49:26 palantir dhcpcd[7725]: received SIGHUP, releasing
Sep 19 18:49:26 palantir dhcpcd[7725]: eth0: removing interface
Sep 19 18:49:26 palantir kernel: [ 3956.651471] r8169 0000:08:00.0: eth0: link down
Sep 19 18:49:26 palantir kernel: [ 3956.652946] ADDRCONF(NETDEV_UP): eth0: link is not ready
Sep 19 18:49:26 palantir kernel: [ 3956.749172] ADDRCONF(NETDEV_UP): wlan0: link is not ready
Sep 19 18:49:26 palantir kernel: [ 3956.797444] r8169 0000:08:00.0: eth0: link down
Sep 19 18:49:26 palantir kernel: [ 3956.799043] ADDRCONF(NETDEV_UP): eth0: link is not ready
Sep 19 18:49:28 palantir kernel: [ 3958.748152] r8169 0000:08:00.0: eth0: link up
Sep 19 18:49:28 palantir kernel: [ 3958.749625] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Sep 19 18:49:39 palantir kernel: [ 3970.294307] ADDRCONF(NETDEV_UP): wlan0: link is not ready
Sep 19 18:49:40 palantir kernel: [ 3970.337386] r8169 0000:08:00.0: eth0: link up
Sep 19 18:49:40 palantir kernel: [ 3970.379768] r8169 0000:08:00.0: eth0: link up
Sep 19 18:49:42 palantir dhcpcd[7831]: version 5.2.12 starting
Sep 19 18:49:42 palantir dhcpcd[7831]: eth0: rebinding lease of 192.168.0.198
Sep 19 18:49:42 palantir dhcpcd[7831]: eth0: acknowledged 192.168.0.198 from 192.168.0.1
Sep 19 18:49:42 palantir dhcpcd[7831]: eth0: checking for 192.168.0.198
Sep 19 18:49:46 palantir dhcpcd[7831]: eth0: leased 192.168.0.198 for 86400 seconds
Sep 19 18:49:46 palantir dhcpcd[7831]: forked to background, child pid 7860
Sep 19 18:51:05 palantir kernel: [ 4056.131108] r8169 0000:08:00.0: eth0: link down
Sep 19 18:51:05 palantir dhcpcd[7860]: eth0: carrier lost
Sep 19 18:51:05 palantir dhcpcd[7921]: sending signal 1 to pid 7860
Sep 19 18:51:05 palantir dhcpcd[7921]: waiting for pid 7860 to exit
Sep 19 18:51:05 palantir dhcpcd[7860]: received SIGHUP, releasing
Sep 19 18:51:05 palantir dhcpcd[7860]: eth0: removing interface
Sep 19 18:51:06 palantir kernel: [ 4056.332100] r8169 0000:08:00.0: eth0: link down
Sep 19 18:51:06 palantir kernel: [ 4056.333575] ADDRCONF(NETDEV_UP): eth0: link is not ready
Sep 19 18:51:06 palantir kernel: [ 4056.432721] ADDRCONF(NETDEV_UP): wlan0: link is not ready
Sep 19 18:51:06 palantir kernel: [ 4056.474980] r8169 0000:08:00.0: eth0: link down
Sep 19 18:51:06 palantir kernel: [ 4056.476468] ADDRCONF(NETDEV_UP): eth0: link is not ready
Sep 19 18:51:08 palantir kernel: [ 4058.492425] r8169 0000:08:00.0: eth0: link up
Sep 19 18:51:08 palantir kernel: [ 4058.493881] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Sep 19 18:54:11 palantir dbus-daemon: [system] Reloaded configuration
Sep 19 18:54:12 palantir last message repeated 3 times
Sep 19 18:55:46 palantir last message repeated 4 times
Sep 19 18:56:02 palantir kernel: [ 4353.297624] r8169 0000:08:00.0: eth0: link down
Sep 19 18:56:13 palantir kernel: [ 4363.810719] ADDRCONF(NETDEV_UP): wlan0: link is not ready
Sep 19 18:56:13 palantir kernel: [ 4363.855417] r8169 0000:08:00.0: eth0: link down
Sep 19 18:56:13 palantir kernel: [ 4363.856429] ADDRCONF(NETDEV_UP): eth0: link is not ready
Sep 19 18:56:13 palantir kernel: [ 4363.919640] ADDRCONF(NETDEV_UP): wlan0: link is not ready
Sep 19 18:56:15 palantir kernel: [ 4366.054487] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
Sep 19 18:56:16 palantir dhcpcd[8932]: version 5.2.12 starting
Sep 19 18:56:16 palantir dhcpcd[8932]: wlan0: rebinding lease of 192.168.0.197
Sep 19 18:56:16 palantir dhcpcd[8932]: wlan0: acknowledged 192.168.0.197 from 192.168.0.1
Sep 19 18:56:16 palantir dhcpcd[8932]: wlan0: checking for 192.168.0.197
Sep 19 18:56:21 palantir dhcpcd[8932]: wlan0: leased 192.168.0.197 for 86400 seconds
Sep 19 18:56:21 palantir dhcpcd[8932]: forked to background, child pid 8961
 
Old 09-20-2012, 04:17 AM   #2
H_TeXMeX_H
Guru
 
Registered: Oct 2005
Location: $RANDOM
Distribution: slackware64
Posts: 12,928
Blog Entries: 2

Rep: Reputation: 1269Reputation: 1269Reputation: 1269Reputation: 1269Reputation: 1269Reputation: 1269Reputation: 1269Reputation: 1269Reputation: 1269
Well, I'm running version 2 and it connects without problems, even with the dhcp update.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

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
Need help with wicd timmybobo Linux - Newbie 5 03-20-2012 08:07 PM
Wicd Fantastic Linux - Software 2 03-31-2011 11:00 AM
wicd Polanski Linux - Software 14 04-13-2010 06:51 PM
where is wicd 1.7 ? witek Slackware 6 01-25-2010 04:36 PM
WICD tray icon says not connected, WICD manager says conneted to wired network?!?! intheshadows Linux - Newbie 1 12-24-2009 12:15 PM


All times are GMT -5. The time now is 03:29 PM.

Main Menu
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
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration