wicd is not wicked
Moderators: snarkout, Patrick, dann
wicd is not wicked
My ethernet broke. I think it is an onboard ethernet port hardware failure as everything else works fine.
1. I plugged in an rt2500 PCI wireless card.
2. Used Gnome Network Manager to connect with no problems.
3. Gnome Network Manager in Xubuntu annoyingly prompts for a password at every login.
4. I just listened to the latest TLLTS, so thought I'd install wicd to see if I could avoid the password.
5. I inserted the wicd repositories into sources.list.
6. sudo aptitude install wicd, which uninstalled gnome-network-manager
7. wicd does not support rt2500 cards
I am totally screwed.
* No ethernet
* No wireless
* No way to install network manager
I know this screw up is all my fault, but wicd isn't ready to replace network-manager until it supports rt2500.
1. I plugged in an rt2500 PCI wireless card.
2. Used Gnome Network Manager to connect with no problems.
3. Gnome Network Manager in Xubuntu annoyingly prompts for a password at every login.
4. I just listened to the latest TLLTS, so thought I'd install wicd to see if I could avoid the password.
5. I inserted the wicd repositories into sources.list.
6. sudo aptitude install wicd, which uninstalled gnome-network-manager
7. wicd does not support rt2500 cards
I am totally screwed.
* No ethernet
* No wireless
* No way to install network manager
I know this screw up is all my fault, but wicd isn't ready to replace network-manager until it supports rt2500.
Re: wicd is not wicked
Download the network-manager package on another machine and save it to a thumb drive. Move the thumb drive to your laptop and do 'sudo dpkg -i packagename.deb'. You should be good to go.
Ego contemno licentia
Re: wicd is not wicked
Thanks Pat
I didn't know it was possible to download the package separately. I tried downloading the source, but didn't have build-essential installed on that machine.
It was easier to just reinstall Xubuntu.
I didn't know it was possible to download the package separately. I tried downloading the source, but didn't have build-essential installed on that machine.
It was easier to just reinstall Xubuntu.
Re: wicd is not wicked
How do either of these management daemons "support" chipsets of one type or another? I mean, unless I'm (once again) missing something, what you are talking about is a kernel module that is or is not being loaded at boot time, no?
Shared pain is lessened, shared joy is increased; thus do we refute entropy.
--Spider Robinson
--Spider Robinson
Re: wicd is not wicked
All I know is that wicd could not connect to my router. In the preferences dialog, you can choose your chipset (atheros etc). Nothing like rt2500 was on the list.
Regular network manager connects fine.
Regular network manager connects fine.
Re: wicd is not wicked
Interesting; but the card should work, according to the wicd forums: http://wicd.sourceforge.net/phpbb/searc ... mit=Search
There have been issues reported though, in certain situations. Perhaps the solution to the problem lies there?
There have been issues reported though, in certain situations. Perhaps the solution to the problem lies there?
Re: wicd is not wicked
Thanks Dann. I'll have a hunt around.
- Wally Balljacker
- Posts: 1227
- Joined: Fri Jul 29, 2005 3:32 am
- Location: University of Massachusetts - Lowell
- Contact:
Re: wicd is not wicked
Why don't you just use wpa_supplicant and dhcpcd and reinstall NetworkManager?Iain wrote:All I know is that wicd could not connect to my router. In the preferences dialog, you can choose your chipset (atheros etc). Nothing like rt2500 was on the list.
Regular network manager connects fine.
Re: wicd is not wicked
The rt2500 does not use wpa_supplicant. The Ralink drivers have their own native WPA implementation. I have several of these cards and WPA does work, but you have to configure it very differently.Wally Balljacker wrote:Why don't you just use wpa_supplicant and dhcpcd and reinstall NetworkManager?
Chess Griffin