CrunchBang Linux Forums » Help & Support (Stable) » Replacing NetworkManager with WICD in Statler [Solved]
I've heard that when installing WICD in #! 9.04, that it replaces NetworkManager. I wondered if this was the case with statler, or if something different had to be done.
Last edited by Him (2010-06-20 21:35:08)
No it should be the same. Ubuntu is based on Debian after all.
Awesome!
So, I don't have to go and edit the rc.conf or anything like that?
I don't think so.
Okay, I've gotten wicd installed and added myself as a user, all without a hitch.
But now that I've gotten it installed, it won't connect. It keeps saying that I'm using a bad password, when I'm sure that I'm using the right one. I've also added wlan0 to the wireless interfaces, and I'm sure that I'm using the right type of encryption. What is it that I'm doing wrong?
EDIT: It appears that both wicd and networkmanager daemons are running at start, or at least, I think that's what's happening. Before GDM appears, it shows "Starting up NetworkManager", then "Starting up WICD".
Last edited by Him (2010-06-20 16:26:29)
Strange, wicd used to conflict with NM. I'd download the NM packages just in case, then try to uninstall it.
a.
Okay, I've gotten wicd installed and added myself as a user, all without a hitch.
But now that I've gotten it installed, it won't connect. It keeps saying that I'm using a bad password, when I'm sure that I'm using the right one. I've also added wlan0 to the wireless interfaces, and I'm sure that I'm using the right type of encryption. What is it that I'm doing wrong?
EDIT: It appears that both wicd and networkmanager daemons are running at start, or at least, I think that's what's happening. Before GDM appears, it shows "Starting up NetworkManager", then "Starting up WICD".
I'm not saying this is the answer but the last time I used wicd it insisted on using WEP and not WPA. Just something I remember. 
Him wrote:Okay, I've gotten wicd installed and added myself as a user, all without a hitch.
But now that I've gotten it installed, it won't connect. It keeps saying that I'm using a bad password, when I'm sure that I'm using the right one. I've also added wlan0 to the wireless interfaces, and I'm sure that I'm using the right type of encryption. What is it that I'm doing wrong?
EDIT: It appears that both wicd and networkmanager daemons are running at start, or at least, I think that's what's happening. Before GDM appears, it shows "Starting up NetworkManager", then "Starting up WICD".
I'm not saying this is the answer but the last time I used wicd it insisted on using WEP and not WPA. Just something I remember.
I'm thinking it might have something to do with the fact that NetworkManager is still there. When using NM to post these, it constantly disconnected until I got rid of wicd and all of its packages.
Perhaps I should do the same to NM. I'm just paranoid, as if I do so, I'll be without a way to get NM back.
You'll need, of course, to have one or the other. It's been awhile but wicd used to replace nm. Not sure why that isn't the case.
You'll need, of course, to have one or the other. It's been awhile but wicd used to replace nm. Not sure why that isn't the case.
That was in the Ubuntu base. As this is alpha, I guess there really isn't any reason other than it's straight Debian.
winotree wrote:You'll need, of course, to have one or the other. It's been awhile but wicd used to replace nm. Not sure why that isn't the case.
That was in the Ubuntu base. As this is alpha, I guess there really isn't any reason other than it's straight Debian.
Um. Not so sure as I believe I tried to add wicd to a Debian Sid [from netinst] I played with about a month ago and IIRC they swapped each other out but wicd was buggy about using WEP. Maybe you could search if that still the case.
I wish I were more help but this little bugger I'm using invariably works flawlessly unless I begin hammering it. 
Best to you, nonetheless. 
Him wrote:winotree wrote:You'll need, of course, to have one or the other. It's been awhile but wicd used to replace nm. Not sure why that isn't the case.
That was in the Ubuntu base. As this is alpha, I guess there really isn't any reason other than it's straight Debian.
Um. Not so sure as I believe I tried to add wicd to a Debian Sid [from netinst] I played with about a month ago and IIRC they swapped each other out but wicd was buggy about using WEP. Maybe you could search if that still the case.
I wish I were more help but this little bugger I'm using invariably works flawlessly unless I begin hammering it.
Heh, thanks.
I've used WICD not only on this computer before, but on this very network. I'll see if I can find a networkmanager.deb and try again.
EDIT: Once I removed Networkmanager and installed Wicd, everything went smoothly. Thanks for the help everyone!
Last edited by Him (2010-06-20 21:35:40)
I am running #! on three computers, Asus eee pc 1005HA with Cruncheee, MSI A5000 with Statler, and a quad-core desktop with Statler. In spite of Corenominal's dire warnings about stability, I have found this distro to be nearly flawless.
The only real problems I have encountered are with wireless. I had continuous problems with dropped connections on the netbook until I replaced Network Mananger with wicd. This was a completely painless install. I did an apt-get and wicd installed and removed NM without issue. I was up and running again in minutes and the dropped connections disappeared completely.
However, on the other laptop running Statler, the situation was different. I was also suffering from very annoying dropped connections. When I attempted to install wicd, it failed to remove NM and there was an immediate conflict and no ability to connect.
Since I was running a dual boot, I verified that the connection issues were a problem with NM, because Win XP performed fine with the same hardware.
I used synaptic to manually remove NM, rebooted, reinstalled wicd, started the client and still could not connect. It kept reporting that it could not obtain an IP address. I reinstalled again with the same result.
I ended up removing wicd and reverting to NM, but was hoping that someone might know why wicd fails to install cleanly and remove NM as it did in previous #! releases.
Any advice on getting wicd to work would be appreciated.
I also had an un-smooth change over from nm to wicd.
Some things you might want to consider are; purging nm instead of removing. I use a program called sysv-rc-conf
which shows which daemons start at boot. After removing nm and rebooting I ran sudo sysv-rc-conf and noticed entries for nm were still there.
I then ran sudo /etc/init.d/network-manager stop and sudo /etc/init.d/wicd restart which got things going.
If that doesn't work use htop to check if dhclient or wpa-supplicant are running and kill them before restarting wicd.
Finally check back with sudo sysv-rc-conf -P which should purge the nm entries so that wicd will behave after a reboot.
Good luck....
Thanks for the tips. I suspected that something was being left behind after removing NM. Hopefully, your suggestions will cure that problem.
Do I need to edit autostart.sh to remove the entry for the nm-applet?
Thanks again.
Do I need to edit autostart.sh to remove the entry for the nm-applet?
Yes and add the wicd applet if you want. I use only wicd-curses and not the gtk part so I'm not sure of the exact line to add.
Have fun ...
Posts [ 16 ]
CrunchBang Linux Forums » Help & Support (Stable) » Replacing NetworkManager with WICD in Statler [Solved]
Forums powered by PunBB. Hosted by Linode.
Copyright © CrunchBang Linux.
Proudly powered by Debian GNU/Linux.
Debian is a registered trademark of Software in the Public Interest, Inc.