My alfa awus036h wont work with wicd.

phillip69 · 06-02-2012, 01:48 PM

I have a alfa awus036h and everytime that I try to connect to the internet its connection failed bad password. I am using debian 6.05.
I am wondering if anyone knows how to fix it.
Thanks

Babertje · 06-02-2012, 03:29 PM

Do you have rfkill installed, check if your adapter is not blocked by your wifi-switch this can give you this "failed bad password" warning!

Code:

rfkill list

soft and hard must be "blocked no"
to enable wifi

Code:

rfkill unblock wifi

you may need to do this as sudo
TIP: add this command to /etc/rc.local everytime you startup wifi will be ready to go

phillip69 · 06-02-2012, 04:13 PM

I have a new problem

2012/06/02 00:25:25 :: Traceback (most recent call last):
2012/06/02 00:25:25 :: File "/usr/share/wicd/daemon/wicd-$
2012/06/02 00:25:25 :: main(sys.argv)
2012/06/02 00:25:25 :: File "/usr/share/wicd/daemon/wicd-$

phillip69 · 06-02-2012, 04:14 PM

I get an error message that says:
Could not connect to wicd's D-bus interface. Check the wicd log for error messages

rokytnji · 06-02-2012, 04:28 PM

Quote:

Originally Posted by phillip69

I get an error message that says:
Could not connect to wicd's D-bus interface. Check the wicd log for error messages

Quote:

If not already performed, add your regular user account to the netdev group and reload DBus:

from

http://wiki.debian.org/WiFi/HowToUse

Scroll down to

Wicd

wicd (Wireless Interface Connection Daemon) is a lightweight alternative to NetworkManager. It is environment-independent, making it suitable for all desktop environments, including GNOME, Xfce, LXDE, and Fluxbox. Like NetworkManager, wicd is configured via a graphical interface. Your wireless interface should not be referenced within Debian's /etc/network/interfaces file.

Edit: This thread might help you understand wicd debian page a little better also.

http://ubuntuforums.org/showthread.php?t=1301414

phillip69 · 06-02-2012, 08:47 PM

I tried that but it said that I was already The user `phillip' is already a member of `netdev'.

Babertje · 06-03-2012, 04:20 AM

In Archlinux mankind can make the mistake to swap the daemon order around, I Know debian uses init.d S01.. S02.. and so on but does Dbus start in before Wicd in init.d, if this is not the case you end up with "Could not connect to wicd's D-bus interface" errors.