SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Hi all,
I have a Broadcom BCM4312, and have installed wicd from the /extra directory on the DVD. Whenever I try to connect to a WPA network, I get a Bad Password message.
I _think_ it is wicd that requires that keys (hex) be entered with A-F in uppercase. I know it is _one_ of the common wireless configuration methods, but I'm not able to test which one at the moment.
I _think_ it is wicd that requires that keys (hex) be entered with A-F in uppercase. I know it is _one_ of the common wireless configuration methods, but I'm not able to test which one at the moment.
Hi, I am not using a hex key. It is an english language string, I have tried entering the sting in uppercase just in case, but no luck.
Thanks for the response by the way. This is driving me mad!
Wicd (pronouced as wicked) aims to provide a simple interface to connect to networks with a wide variety of settings. Some of Wicd's features include:
Ability to connect to wired and wireless networks
Profiles for each wireless network and wired network
Many encryption schemes, some of which include WEP/WPA/WPA2
Remains compatible with wireless-tools
Tray icon showing network activity and signal strength
Read more about it here: http://wicd.net/
Wicd installs a daemon which talks to your computer's dbus messagebus to detect network connects/disconnects. Configuration of your wireless as well as wired interfaces is done via a wicd client. You can either run the graphical wicd-client in your X Window session (KDE, XFCE, blackbox, …), or use the console program wicd-curses if you are not using X.
If you want to use wicd, you will have to remove any network interface configuration information from /etc/rc.drc.inet1.conf in order to prevent a struggle for power between wicd and Slackware's rc.inet1 script.
What state is '/etc/rc.d/rc.inet1.conf'? Original or modified? Note the underlined text above.
I've had this issue before. I think it's complaining about the driver used by wpa_supplicant.
After you open up Wicd Network Manager, there should be a "Preferences" button in between "Refresh" and "About." A new window will pop up, and you should see several tabs. The one we want is "Advanced Settings." Under that tab, there should be a "WPA Supplicant" section with a Driver pre-selected. Try changing the drivers and re-connecting.
Distribution: Debian Sid AMD64, Raspbian Wheezy, various VMs
Posts: 7,680
Rep:
I've had a problem where removing network-manager and network-manager-gnome meant wicd would then work with a passphrase. I'm running Debian though so not sure how much help that is.
The advice from onebuck / Alien Bob regarding the /etc/rc.d/rc.inet1.conf is important - I could not get wicd working until I got this file back to its virgin state.
Even after that though, I found that wireless access via wicd seemed to be a bit random - worked sometimes, but often did not. I have now gotten into a habit which seems to make it work nearly every time: Before pressing the "Connect" button in the main wicd dialog, I press the "Settings" (I think that's right, I working from memory) button next to it. In the dialog I then over-write the final few characters of the passphrase that comes up with the same characters. Press OK and then press "Connect". Why this should make a difference (forces a re-read of a wicd configuration file?) or even whether it really does make a difference I have no idea, but as I say, wicd connects for me practically every time now.
Ya know, the 1st time I used wicd I had everything so screwed up that the only way I got it to work was to remove wicd, (removepkg)
delete the .wicd folder in /home,
deleate the /etc/wicd folder (removepkg dosent remove it).
Return /etc/rc.d/rc.inet1.conf to it's natural state.
Reinstall wicd. Then it worked perfect.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.