LinuxQuestions.org
Review your favorite Linux distribution.
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 02-27-2008, 07:16 PM   #16
mrclisdue
Senior Member
 
Registered: Dec 2005
Distribution: Slackware -current, 14.1
Posts: 1,048

Rep: Reputation: 170Reputation: 170

Ok.

So yesterday was the first that I'd heard of wicd, so I promptly dl'd the tarball, and installed from source, etc. Replaced the networking.py with the *proper* one for Slack. I stopped /etc/rc.d/rc.inet1; started the daemon, ran gui-py - entered the interface info, tried each wpa option (it's ralink, rt),...nothing. It simply doesn't find the interface. The wicd.log shows persistent attempts to find/start the interface, but no luck.

On a second box, I installed the package from slackbuilds.org, same results: nothing. Only difference is that this nic is Atheros.

Any advice/suggestions/direction?

Thanks,
 
Old 02-27-2008, 09:45 PM   #17
sparker
Member
 
Registered: Aug 2007
Location: Canada
Distribution: OpenBSD 4.6, Debian Lenny
Posts: 64

Original Poster
Rep: Reputation: 16
Quote:
Originally Posted by em21701 View Post
Yes I did start the service, I should have mentioned that. Does slack 12 ship with an older version of GTK? Why wouldn't wicd throw a build error if the GTK version was too old?
Did you install the dbus-python and pyGTK packages too? When I first built wicd I forgot the dbus-python and I didn't get any errors when building.
 
Old 02-28-2008, 03:16 PM   #18
em21701
Member
 
Registered: Feb 2008
Location: Rhode Island, USA
Distribution: Slackware12.2 & Slackware64-13
Posts: 247

Rep: Reputation: 40
Quote:
Originally Posted by sparker View Post
Did you install the dbus-python and pyGTK packages too? When I first built wicd I forgot the dbus-python and I didn't get any errors when building.
Yes, I downloaded both of them from slackbuilds.org ran the scripts and then the installers. Then I ran the build and install scripts for wicd (also from slackbuilds.org)
 
Old 02-28-2008, 11:29 PM   #19
theoffset
Member
 
Registered: Aug 2005
Location: Guadalajara, Jal, Mexico
Distribution: Slackware Linux
Posts: 211

Rep: Reputation: 30
Quote:
started the daemon, ran gui-py - entered the interface info, tried each wpa option (it's ralink, rt),...nothing. It simply doesn't find the interface. The wicd.log shows persistent attempts to find/start the interface, but no luck.
Did you try the "Preferences" menu in the GUI? IIRC ralink's interfaces are named "ra?"

I've been happily running WICD (with an Intel card. I'm also running -current, tho') for a couple of months now.

As for modifying networking.py, using dhclient seems to work for me at several places *EXCEPT* when using my home AP (for some reason dhclient doesn't update /etc/resolv.conf as it should... but only with this AP so far).
 
Old 02-29-2008, 05:22 AM   #20
mrclisdue
Senior Member
 
Registered: Dec 2005
Distribution: Slackware -current, 14.1
Posts: 1,048

Rep: Reputation: 170Reputation: 170
Quote:
Originally Posted by theoffset View Post
Did you try the "Preferences" menu in the GUI? IIRC ralink's interfaces are named "ra?"
Yes. The interface is wlan0, though when I used the nic in Fedora, it was rausb0. I'm going to do some serious playing around today to see if I can solve the issue.

I'm not overly concerned because both boxes work fine without wicd - my interest was piqued when this thread originated, and it's just a wee bit frustrating when what should be a fairly simple application doesn't behave as expected. I'll keep y'all posted...

cheers,
 
Old 02-29-2008, 06:42 AM   #21
em21701
Member
 
Registered: Feb 2008
Location: Rhode Island, USA
Distribution: Slackware12.2 & Slackware64-13
Posts: 247

Rep: Reputation: 40
mrclisdue, what were you using before to connect to your wireless? Since this is a laptop I want to be able to see the networks availiable to me, I used wicd when Kubuntu was installed on this machine and it worked well.
 
Old 02-29-2008, 07:42 AM   #22
mrclisdue
Senior Member
 
Registered: Dec 2005
Distribution: Slackware -current, 14.1
Posts: 1,048

Rep: Reputation: 170Reputation: 170
Quote:
Originally Posted by em21701 View Post
mrclisdue, what were you using before to connect to your wireless? Since this is a laptop I want to be able to see the networks availiable to me, I used wicd when Kubuntu was installed on this machine and it worked well.
On the box with the Atheros card, I installed madwifi. I *believe* that I then made the appropriate modifications to /etc/rc.d/rc.inet1.conf, restarted /etc/rc.d/rc.inet1, et voila!

On the second box, I retrieved and installed the appropriate driver from serialmonkey, made the modifications to /etc/rc.d/rc.inet1.conf, etc..

I like the idea of wicd, tho', especially the gui, because I believe it simplifies the scanning for available networks, connecting, etc. processes (this is the point where someone will jump in with the cli commands in an attempt to prove to me how much simpler it is to do it from the command line - I *already* know how to connect from the cli - it's *everyone* else I'm concerned with. If I wish to spread the Linux gospel, I must do so on the "educated by MS" terms, not on my terms....)

cheers,
 
Old 02-29-2008, 10:00 PM   #23
hemp4fuel
Member
 
Registered: Jun 2003
Location: Topeka, KS
Distribution: Slackware
Posts: 192

Rep: Reputation: 45
I have been having trouble when I am at home then suspend to ram, take my laptop to school and try to connect using wicd. Before I leave I use the "Disconnect" button(but I get the same result whether I do or not). When I try connecting to my schools network it won't get an ip until I reboot. I have tried doing it manually as well with dhcpcd and dhclient but I get the same result, no ip until I reboot then everything works fine. I am using a modified networking.py that uses dhcpcd. I have the same result if I then suspend to ram and return home, no ip until I reboot. I started using wicd hoping a tool such as this would be able to connect to different networks without the reboot but I can't seem to get it to work. It would seem that one should be able to connect to different networks without a reboot. My home network uses wpa2 and the school network is unencrypted.

Last edited by hemp4fuel; 02-29-2008 at 10:02 PM.
 
Old 03-01-2008, 08:52 AM   #24
em21701
Member
 
Registered: Feb 2008
Location: Rhode Island, USA
Distribution: Slackware12.2 & Slackware64-13
Posts: 247

Rep: Reputation: 40
I finally have it working. Since Slackware was a recent install I decided to go back to square 1 and reinstall Slack12.

Step1:

I setup my wireless adapter (broadcom). There are a lot of substeps to this, and it varies by wireless manufacturer. There are lots of posts and tutorials availiable.

Step2:

Install dbus-python
Install pygobject
Install pycairo
Install pygtk

Step3:

Install wicd

Step4:

start daemon (/etc/rc.d/rc/wicd start)
start wicd (sucess!)

Step5:

make it automatic, add:

Code:
if [ -x /etc/rc.d/rc.wicd ]; then
     /etc/rc.d/rc.wicd start
fi
into /etc/rc.d/rc.local

Last edited by em21701; 03-01-2008 at 08:54 AM.
 
Old 03-01-2008, 11:21 AM   #25
evilDagmar
Member
 
Registered: Mar 2005
Location: Right behind you.
Distribution: NBG, then randomed.
Posts: 480

Rep: Reputation: 31
Quote:
Originally Posted by nawcom View Post
let me know if you still need help. sounds like you didnt start up the wicd daemon "/opt/wicd/daemon.py" at boot time. if you use slackware you will also have to replace the networking.py with a modified one, for wicd is setup to use dhclient, while slackware uses dhcpcd to update the resol.conf realtime. oh wells, email me if you still need the help.
No, actually so long as he didn't elect not to install the dhcp package, dhclient will work just fine.

The behaviours of dhclient and dhcpcd are also different enough that just replacing "dhclient" with "dhcpcd" in the script is not very likely to be a good (or working) solution.
 
Old 03-01-2008, 03:06 PM   #26
mRgOBLIN
Slackware Contributor
 
Registered: Jun 2002
Location: New Zealand
Distribution: Slackware
Posts: 999

Rep: Reputation: 227Reputation: 227Reputation: 227
Actually in this case as long as you only replace the *word* "\<dhclient\>" with dhcpcd in daemon.py and networking.py it does appear to work fine. I've been using it this way for a few weeks with no issues.

Code:
cd /opt/wicd && sed -i 's/\<dhclient\>/dhcpcd/g' {networking,daemon}.py
Did the trick for me
 
Old 03-02-2008, 01:20 AM   #27
evilDagmar
Member
 
Registered: Mar 2005
Location: Right behind you.
Distribution: NBG, then randomed.
Posts: 480

Rep: Reputation: 31
Either way it's not necessary. dhclient works fine.
 
Old 03-12-2008, 05:11 PM   #28
nawcom
LQ Newbie
 
Registered: May 2004
Posts: 17

Rep: Reputation: 0
dhclient doesn't update resolv.conf without modifying the dhclient-script. slackware is set up to have dhcpcd deal with resolv.conf updates initially. thats why replacing dhclient with dhcpcd and the dhclient route commands with dhcpcd equivalent works. you can use dhclient just fine - you just wont be able to update your resolv.conf automatically with it without some changes in inet1.

I talked to the wicd developer; he plans on making the next major update to include support for what it has so far, plus dhcpcd and pump, along with others.

if you got dhclient to update the resolv.conf in slackware evilDagmar, that's great. It's just that if there is an easier route to solving the problem without making any changes, that's the best way to go. dhcpcd has resolv.conf control in slackware. which is why its better to use dhcpcd with wicd. make 2 line changes in networking.py - wallah. problem solved.

here is an updated package that will take care of the dirty work for you:
http://nawcom.com/files/slack/wicd-1.4.2-i486-3bpn.tgz

direct link to the wicd forum relating to this topic:
http://wicd.sourceforge.net/phpbb/vi...e1bbf7415070db

wicd bug report about this topic: https://bugs.launchpad.net/wicd/+bug/191091

Last edited by nawcom; 03-12-2008 at 06:29 PM. Reason: added pkg link
 
Old 03-12-2008, 05:13 PM   #29
nawcom
LQ Newbie
 
Registered: May 2004
Posts: 17

Rep: Reputation: 0
if there are problems with it email me at nawcom@nawcom.com; I seem to focus on the linuxquestions.org forums less and less these days.

Last edited by nawcom; 03-12-2008 at 06:21 PM.
 
  


Reply

Tags
slackware, wicd


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
trouble with wicd unisol Debian 1 08-20-2007 04:22 PM
LXer: Managing wireless connections seamlessly with wicd LXer Syndicated Linux News 1 07-31-2007 05:10 PM
About Slackware 9.1 boot disk?? ftp://ftp.kpn.be/pub/linux/slackware/slackware-9.1-is AL3OMDAH Slackware 4 04-18-2007 09:54 AM


All times are GMT -5. The time now is 03:53 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