LinuxQuestions.org
Download your favorite Linux distribution at LQ ISO.
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 08-15-2009, 02:00 AM   #1
tux_dude
Member
 
Registered: Dec 2008
Distribution: Slackware64 Current
Posts: 226

Rep: Reputation: 33
major wicd issues


Running (was) wicd-1.6.2 on slack current and I having nothing but problem since going to 1.6.x. I use wicd strictly for monitoring purposes due to its ui. Wpa_supplicant is used for all network configuration.

1. First problem I had was kde would boot to a black screen occasionally or upon unlocking my desktop, the screen would remain black. Thought this was the NVIDIA driver acting up again. I narrowed it down to wicd because it only occurs when wifi is not available.

2. wicd sometimes prevent my nic from scanning for wifi networks. Killing wicd and wpa_supplicant do not help. I have to unload the wifi module and reload it.

3. And the most frequent problem is the inability to receive data over wifi. Network connection would be active with packets being sent but none being received. Restarting the wlan would restore the connection, however connection would last only for a few minutes at best.

This took a lot a hair pulling to figure out. I narrowed it down to wicd completely by accident when I hooked up my ethernet after loosing wifi. My system has been running smoothly after remove wicd.

Anyone else had any of these symptoms? Slack is running on Lenovo T61 (centrino) with Intel iwlwifi-4965-ucode-228.61.2.24.
 
Old 08-15-2009, 02:29 AM   #2
rworkman
Slackware Contributor
 
Registered: Oct 2004
Location: Tuscaloosa, Alabama (USA)
Distribution: Slackware
Posts: 1,945

Rep: Reputation: Disabled
Nope, all is well here, and I've seen nothing similar in the wicd IRC channel.
 
Old 08-15-2009, 12:36 PM   #3
BCarey
Senior Member
 
Registered: Oct 2005
Location: New Mexico
Distribution: Slackware
Posts: 1,490

Rep: Reputation: Disabled
It sounds like a driver problem. Does wifi work fine if you don't use wicd?

Brian
 
Old 08-18-2009, 08:00 AM   #4
unclejed613
Member
 
Registered: Mar 2009
Posts: 326

Rep: Reputation: 26
i had the same problem when i first installed my wireless card..... as it turns out wicd and inetd were butting heads. when i set inetd to default (set the inetd.conf to out-of-box defaults) wicd took over and works very nicely. basically you can't have both inetd and wicd trying to configure your network devices at the same time. choose one or the other. i think wicd has better functionality.
 
Old 08-18-2009, 10:39 AM   #5
onebuck
Moderator
 
Registered: Jan 2005
Location: Midwest USA, Central Illinois
Distribution: SlackwareŽ
Posts: 11,450
Blog Entries: 4

Rep: Reputation: 1505Reputation: 1505Reputation: 1505Reputation: 1505Reputation: 1505Reputation: 1505Reputation: 1505Reputation: 1505Reputation: 1505Reputation: 1505Reputation: 1505
Hi,

Why not just configure the '/etc/inetd.conf' if you think there is a conflict.

Quote:
excerpt from 'man inetd';

inetd -- internet ``super-server''

SYNOPSIS
inetd [-d] [-R rate] [configuration file]

DESCRIPTION
inetd should be run at boot time by /etc/rc (see rc(8)). It then listens
for connections on certain internet sockets. When a connection is found
on one of its sockets, it decides what service the socket corresponds to,
and invokes a program to service the request. After the program is fin-
ished, it continues to listen on the socket (except in some cases which
will be described below). Essentially, inetd allows running one daemon
to invoke several others, reducing load on the system.
...
Your 'inetd' provides the 'super-server' for a reason to inet communication with other daemons. I'm not saying your wrong with stopping the service, it's your machine. But what about 'time' or 'authentication' ? 'inetd' provides other configurable means for useful service to other daemons.
 
Old 08-18-2009, 04:35 PM   #6
rworkman
Slackware Contributor
 
Registered: Oct 2004
Location: Tuscaloosa, Alabama (USA)
Distribution: Slackware
Posts: 1,945

Rep: Reputation: Disabled
inetd and wicd are unrelated - I think "rc.inet1.conf" is what the poster meant.
That's also mentioned in the README.SLACKWARE file for wicd.
 
Old 08-18-2009, 07:40 PM   #7
onebuck
Moderator
 
Registered: Jan 2005
Location: Midwest USA, Central Illinois
Distribution: SlackwareŽ
Posts: 11,450
Blog Entries: 4

Rep: Reputation: 1505Reputation: 1505Reputation: 1505Reputation: 1505Reputation: 1505Reputation: 1505Reputation: 1505Reputation: 1505Reputation: 1505Reputation: 1505Reputation: 1505
Hi,

Quote:
Originally Posted by rworkman View Post
inetd and wicd are unrelated - I think "rc.inet1.conf" is what the poster meant.
That's also mentioned in the README.SLACKWARE file for wicd.
I should have 'quoted' unclejed613 as my post was directed to him. Sorry about the mix up. I really couldn't see the relationship but if there are conflicts then try to configure than remove something as important as 'inetd'.

Edit: I re-read 'unclejed613' post and if you do apply the thought of 'inet1.conf' then probably where the confusion came for me. I just could not see disabling 'inetd'.

Last edited by onebuck; 08-18-2009 at 07:44 PM. Reason: add comment
 
Old 08-18-2009, 09:31 PM   #8
unclejed613
Member
 
Registered: Mar 2009
Posts: 326

Rep: Reputation: 26
sorry for the mix-up. when i described the problem i was having with wicd a few months back, the developers of wicd told me in an email it was conflicting with the settings in inet1.conf, and to set inet1.conf back to the default configuration. after that wicd has worked fine...
inetd is still running, but it's not handling the wireless or wired cards directly, as that's what wicd is doing.
 
Old 08-18-2009, 11:31 PM   #9
onebuck
Moderator
 
Registered: Jan 2005
Location: Midwest USA, Central Illinois
Distribution: SlackwareŽ
Posts: 11,450
Blog Entries: 4

Rep: Reputation: 1505Reputation: 1505Reputation: 1505Reputation: 1505Reputation: 1505Reputation: 1505Reputation: 1505Reputation: 1505Reputation: 1505Reputation: 1505Reputation: 1505
Hi,

That's OK!

It just didn't make sense to stop 'inetd' to me. I just couldn't see how that would be a problem with 'wicd'. If so then possible config changes but to what I wasn't sure.

robby, pointed out that he thought the 'inet1.conf' was the intent. I read your post thinking about using 'inet1.conf' and the light brightened.
 
Old 08-19-2009, 12:36 AM   #10
mRgOBLIN
Slackware Contributor
 
Registered: Jun 2002
Location: New Zealand
Distribution: Slackware
Posts: 999

Rep: Reputation: 227Reputation: 227Reputation: 227
I think the confusion stems from the missing rc. from rc.inet1.conf =)
 
Old 08-20-2009, 10:06 AM   #11
tux_dude
Member
 
Registered: Dec 2008
Distribution: Slackware64 Current
Posts: 226

Original Poster
Rep: Reputation: 33
I tried going back to stock rc.inet1.conf and used wicd fully but I found it took forever to boot. Plus, it kept messing up my resolv.conf file whenever decides to connect to my neighbor's wifi. Seeing the wifi strength on the taskbar is nice. If only I had an app (that worked) just for that.

I no longer have the above problems now that wicd has been removed, but I am getting more frequent wifi disconnects than usual. Could be the wifi driver. I might have some time to troubleshoot over the weekend. Will let you know my findings.
 
Old 08-25-2009, 12:35 PM   #12
tux_dude
Member
 
Registered: Dec 2008
Distribution: Slackware64 Current
Posts: 226

Original Poster
Rep: Reputation: 33
Looks like BCarey was right on this one. iwlwifi-4965-ucode-228.61.2.24 would stop transmitting after 10-15 sec when transferring large files over wifi. Wicd would lock up when this happens. Guess it was trying to poll the wifi or something. Disconnecting/reconnecting with wpa_sup_gui or a rc.inet1 restart would restore wicd. If this happened before logging into kde, kde desktop would not load. In this case I can log into kde by killing wicd or restarting the wifi. I went back to iwlwifi-4965-ucode-228.57.2.23 which resolved the issue. Didn't find anything on the kernel bug tracker related to this driver so I'll be submitting one.

One thing that came up while I had this issue, where are the old packages from previous revision of current kept? Had to build my own package using the slackbuild script.
 
Old 08-25-2009, 01:33 PM   #13
rworkman
Slackware Contributor
 
Registered: Oct 2004
Location: Tuscaloosa, Alabama (USA)
Distribution: Slackware
Posts: 1,945

Rep: Reputation: Disabled
Quote:
Originally Posted by tux_dude View Post
Looks like BCarey was right on this one. iwlwifi-4965-ucode-228.61.2.24 would stop transmitting after 10-15 sec when transferring large files over wifi. Wicd would lock up when this happens. Guess it was trying to poll the wifi or something. Disconnecting/reconnecting with wpa_sup_gui or a rc.inet1 restart would restore wicd. If this happened before logging into kde, kde desktop would not load. In this case I can log into kde by killing wicd or restarting the wifi. I went back to iwlwifi-4965-ucode-228.57.2.23 which resolved the issue. Didn't find anything on the kernel bug tracker related to this driver so I'll be submitting one.
Ewww, that's just wonderful. The reason for the upgrade was because my hardware craps out on large transfers with the previous firmware -- I mailed the wireless guys a stack trace and dmesg, and they referred me to the new firmware with a fix for it.

Quote:
One thing that came up while I had this issue, where are the old packages from previous revision of current kept? Had to build my own package using the slackbuild script.
They're not The build script is the solution
 
Old 08-25-2009, 02:46 PM   #14
tux_dude
Member
 
Registered: Dec 2008
Distribution: Slackware64 Current
Posts: 226

Original Poster
Rep: Reputation: 33
That's interesting, similar issue with different driver versions. I don't recall anything unusual in dmesg and I didn't do a stack trace. I will upgrade and check again.

Quote:
Originally Posted by rworkman View Post
They're not The build script is the solution
Just as I thought. Was checking to see if there was a public repository somewhere.

Last edited by tux_dude; 08-25-2009 at 10:13 PM.
 
Old 08-25-2009, 04:14 PM   #15
rworkman
Slackware Contributor
 
Registered: Oct 2004
Location: Tuscaloosa, Alabama (USA)
Distribution: Slackware
Posts: 1,945

Rep: Reputation: Disabled
The "stack trace" was actually just the information printed in the kernel OOPS, fwiw.
 
  


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
Major Ati issues Andrew Sorensen Suse/Novell 1 05-22-2007 10:58 PM
major issues with glibc Atmchicago Slackware 9 03-07-2006 07:33 PM
Major APF issues =( Label2021 Linux - Software 1 11-13-2005 10:43 PM
Major Flash Issues Annex Linux - Software 3 05-01-2002 11:05 PM
HELP!!!! Major issues jsut came up! Stephanie Linux - General 6 09-02-2001 04:15 PM


All times are GMT -5. The time now is 08:16 PM.

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