LinuxQuestions.org
Review your favorite Linux distribution.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Networking
User Name
Password
Linux - Networking This forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.

Notices


Reply
  Search this Thread
Old 05-14-2014, 10:00 PM   #1
xiongnu
Member
 
Registered: Sep 2004
Distribution: Devuan, Void
Posts: 264

Rep: Reputation: 23
wicd Connection Failed: Bad Password


hi,

i've got a Netgear PCI MA311 wi-fi card that i installed on my Debian7 box. i've installed the 'hostap' driver associated with this wi-fi card. network manager 'wicd' is installed. 'ifconfig' correctly identifies the card. and i can see my wi-fi network from wicd network manager. the network is configured with wep encryption and the key is corrected entered in wicd.

However, when i try to connect to my wifi network, it returns with 'authentication failed, bad password' error.

i had this computer connected to home wi-fi network before, then i took out the wifi card for another pc, after i reinstalled the wifi card back into this pc, suddenly i began to receive 'bad password' error.

any help is appreciated.

thanks,
 
Old 05-15-2014, 12:56 PM   #2
ondoho
LQ Addict
 
Registered: Dec 2013
Posts: 19,872
Blog Entries: 12

Rep: Reputation: 6053Reputation: 6053Reputation: 6053Reputation: 6053Reputation: 6053Reputation: 6053Reputation: 6053Reputation: 6053Reputation: 6053Reputation: 6053Reputation: 6053
does the card still work as expected in the other computer?

why are you using WEP encryption? i thought WPA was the way to go these days...

can you (temporarily) disable your networks encryption and connect to it?
 
Old 05-16-2014, 12:03 PM   #3
xiongnu
Member
 
Registered: Sep 2004
Distribution: Devuan, Void
Posts: 264

Original Poster
Rep: Reputation: 23
Quote:
Originally Posted by ondoho View Post
does the card still work as expected in the other computer?

why are you using WEP encryption? i thought WPA was the way to go these days...

can you (temporarily) disable your networks encryption and connect to it?
yes, the card works well with my other pc.

i've tried to disable wi-fi encryption, still couldn't connect to the newtwork.

i use WEP because this card only supports WEP in windows, i used to have dual-boot on the pc, not sure whether it supports wpa in debian linux.
 
Old 05-16-2014, 03:47 PM   #4
dolphin_oracle
MX Linux
 
Registered: Dec 2013
Posts: 402

Rep: Reputation: Disabled
Does your network support "b" and "g" wireless connections? that card is "b" only (explains why it only supports wep).

***edit***never mind, I see it works with the other pc (I assume on the same network).

***edit2***have you tried both wep options in the wicd interface?

Last edited by dolphin_oracle; 05-16-2014 at 03:53 PM.
 
Old 05-16-2014, 03:52 PM   #5
ondoho
LQ Addict
 
Registered: Dec 2013
Posts: 19,872
Blog Entries: 12

Rep: Reputation: 6053Reputation: 6053Reputation: 6053Reputation: 6053Reputation: 6053Reputation: 6053Reputation: 6053Reputation: 6053Reputation: 6053Reputation: 6053Reputation: 6053
Quote:
Originally Posted by xiongnu View Post
i've tried to disable wi-fi encryption, still couldn't connect to the newtwork.
methinks, there's some inconsistency between this and the "Bad Password" from your thread title.

how about you start posting some computer output relating to your network setup? e.g. like this:
http://crunchbang.org/forums/viewtopic.php?id=27628
since we cannot physically access your machine, our help only goes so far as you provide us with info.
 
Old 05-16-2014, 04:33 PM   #6
sycamorex
LQ Veteran
 
Registered: Nov 2005
Location: London
Distribution: Slackware64-current
Posts: 5,836
Blog Entries: 1

Rep: Reputation: 1251Reputation: 1251Reputation: 1251Reputation: 1251Reputation: 1251Reputation: 1251Reputation: 1251Reputation: 1251Reputation: 1251
I have read about people having the exact same problem with wicd but not with, eg. nm-applet. Try a different network manager and see if the problem persists.

I have been having the same problem on a laptop. For me neither network manager works: wicd complains about a bad password, nm-applet just spits up the password dialog again.

The workaround I've been using is to remove the module for the card and load it back. Then in 90% of the cases it connects to the network straight away:

For example (on my system it's the 'wl' module):
Code:
# rmmod wl
# modprobe wl
Then I provide the password again and usually it works. It's a not-so-quick and dirty workaround but it works. I think it's to do with the drivers and their support for a wifi chip (mine is very new).

HTH.

Last edited by sycamorex; 05-16-2014 at 07:26 PM.
 
Old 05-17-2014, 07:10 PM   #7
xiongnu
Member
 
Registered: Sep 2004
Distribution: Devuan, Void
Posts: 264

Original Poster
Rep: Reputation: 23
Quote:
Originally Posted by ondoho View Post
methinks, there's some inconsistency between this and the "Bad Password" from your thread title.

how about you start posting some computer output relating to your network setup? e.g. like this:
http://crunchbang.org/forums/viewtopic.php?id=27628
since we cannot physically access your machine, our help only goes so far as you provide us with info.
outputs of:


Code:
erdos@debian:/etc/network$ uname -rv
3.2.0-4-686-pae #1 SMP Debian 3.2.51-1
erdos@debian:/etc/network$ dmesg|grep -Ei 'wlan|firmw|dhc'
[    7.849034] wifi0: defaulting to host-based encryption as a workaround for firmware bug in Host AP mode WEP
[    7.849039] wifi0: defaulting to bogus WDS frame as a workaround for firmware bug in Host AP mode WDS
[    7.851942] wifi0: registered netdevice wlan0
[    8.419185] platform radeon_cp.0: firmware: agent aborted loading radeon/R300_cp.bin (not found?)
[    8.419370] [drm:r100_cp_init] *ERROR* Failed to load firmware!
[    8.435560] platform radeon_cp.0: firmware: agent aborted loading radeon/R300_cp.bin (not found?)
[    8.436080] [drm:r100_cp_init] *ERROR* Failed to load firmware!
[   59.712016] wlan0: no IPv6 routers present
erdos@debian:/etc/network$ sudo cat /var/log/syslog | grep -Ei 'net|wpa|dhc'
[sudo] password for erdos: 
erdos@debian:/etc/network$ sudo cat /var/log/syslog | grep -Ei 'net|wpa|dhc'
erdos@debian:/etc/network$ sudo rfkill list
sudo: rfkill: command not found
erdos@debian:/etc/network$ su
Password: 
root@debian:/etc/network# rfkill list
Can't open RFKILL control device: No such file or directory
 
Old 05-17-2014, 07:15 PM   #8
xiongnu
Member
 
Registered: Sep 2004
Distribution: Devuan, Void
Posts: 264

Original Poster
Rep: Reputation: 23
Quote:
Originally Posted by sycamorex View Post
I have read about people having the exact same problem with wicd but not with, eg. nm-applet. Try a different network manager and see if the problem persists.

I have been having the same problem on a laptop. For me neither network manager works: wicd complains about a bad password, nm-applet just spits up the password dialog again.

The workaround I've been using is to remove the module for the card and load it back. Then in 90% of the cases it connects to the network straight away:

For example (on my system it's the 'wl' module):
Code:
# rmmod wl
# modprobe wl
Then I provide the password again and usually it works. It's a not-so-quick and dirty workaround but it works. I think it's to do with the drivers and their support for a wifi chip (mine is very new).

HTH.
i think 'hostap' is the wi-fi module for my card, when i run 'lsmod'to display loaded module, it shows 'hostap' and 'lib80211', i'm not sure which one is the module for the card.

Code:
erdos@debian:/etc/network$ lsmod
Module                  Size  Used by
mperf                  12421  0 
speedstep_lib          12574  0 
cpufreq_stats          12762  0 
cpufreq_conservative    12987  0 
cpufreq_powersave      12422  0 
cpufreq_userspace      12520  0 
ppdev                  12651  0 
lp                     12797  0 
nfsd                  173890  2 
nfs                   265921  0 
nfs_acl                12463  2 nfs,nfsd
auth_rpcgss            32143  2 nfs,nfsd
fscache                31978  1 nfs
lockd                  57277  2 nfs,nfsd
sunrpc                143904  6 lockd,auth_rpcgss,nfs_acl,nfs,nfsd
ext3                  134152  1 
jbd                    47281  1 ext3
loop                   17810  0 
fuse                   52184  1 
radeon                636657  2 
ttm                    47786  1 radeon
drm_kms_helper         22738  1 radeon
drm                   146387  4 drm_kms_helper,ttm,radeon
iTCO_wdt               16945  0 
iTCO_vendor_support    12632  1 iTCO_wdt
power_supply           13283  1 radeon
i2c_algo_bit           12713  1 radeon
snd_intel8x0           22372  4 
pcspkr                 12515  0 
serio_raw              12803  0 
hostap_pci             43405  2 
rng_core               12580  0 
evdev                  17225  7 
hostap                 84352  1 hostap_pci
lib80211               12829  2 hostap,hostap_pci
shpchp                 26717  0 
processor              27565  0 
snd_ac97_codec         84236  1 snd_intel8x0
snd_pcm_oss            36181  0 
snd_mixer_oss          17668  2 snd_pcm_oss
snd_pcm                53461  3 snd_pcm_oss,snd_ac97_codec,snd_intel8x0
snd_page_alloc         12867  2 snd_pcm,snd_intel8x0
snd_seq_midi           12744  0 
snd_seq_midi_event     13124  1 snd_seq_midi
snd_rawmidi            22472  1 snd_seq_midi
snd_seq                39512  2 snd_seq_midi_event,snd_seq_midi
snd_seq_device         13016  3 snd_seq,snd_rawmidi,snd_seq_midi
snd_timer              22356  2 snd_seq,snd_pcm
snd                    42722  15 snd_timer,snd_seq_device,snd_seq,snd_rawmidi,snd_pcm,snd_mixer_oss,snd_pcm_oss,snd_ac97_codec,snd_intel8x0
soundcore              12921  2 snd
ac97_bus               12462  1 snd_ac97_codec
parport_pc             22036  1 
button                 12817  0 
i2c_i801               12670  0 
i2c_core               19116  5 i2c_i801,i2c_algo_bit,drm,drm_kms_helper,radeon
parport                31254  3 parport_pc,lp,ppdev
ext4                  306996  1 
crc16                  12327  1 ext4
jbd2                   52330  1 ext4
mbcache                12938  2 ext4,ext3
usbhid                 31554  0 
hid                    60152  1 usbhid
sg                     21476  0 
sd_mod                 35425  4 
crc_t10dif             12332  1 sd_mod
ata_generic            12439  0 
pata_it821x            13136  0 
floppy                 48087  0 
ata_piix               25271  3 
libata                125014  3 ata_piix,pata_it821x,ata_generic
thermal                13103  0 
fan                    12594  0 
8139too                22028  0 
uhci_hcd               22337  0 
thermal_sys            17752  3 fan,thermal,processor
mii                    12595  1 8139too
ehci_hcd               35509  0 
firewire_ohci          26784  0 
scsi_mod              135037  3 libata,sd_mod,sg
firewire_core          38753  1 firewire_ohci
crc_itu_t              12331  1 firewire_core
usbcore               104555  4 ehci_hcd,uhci_hcd,usbhid
usb_common             12338  1 usbcore
 
Old 05-18-2014, 02:53 AM   #9
sycamorex
LQ Veteran
 
Registered: Nov 2005
Location: London
Distribution: Slackware64-current
Posts: 5,836
Blog Entries: 1

Rep: Reputation: 1251Reputation: 1251Reputation: 1251Reputation: 1251Reputation: 1251Reputation: 1251Reputation: 1251Reputation: 1251Reputation: 1251
Yes, it looks like the hostap module is the right one.

What is your wifi chipset?
Code:
/sbin/lspci | grep network
 
Old 06-07-2014, 11:25 PM   #10
xiongnu
Member
 
Registered: Sep 2004
Distribution: Devuan, Void
Posts: 264

Original Poster
Rep: Reputation: 23
Quote:
Originally Posted by sycamorex View Post
Yes, it looks like the hostap module is the right one.

What is your wifi chipset?
Code:
/sbin/lspci | grep network

Code:
root@debian:/etc/network# /sbin/lspci | grep network
bash: /sbin/lspci: No such file or directory
root@debian:/etc/network# lspci | grep network
root@debian:/etc/network#

Last edited by xiongnu; 06-07-2014 at 11:28 PM.
 
Old 06-08-2014, 02:07 AM   #11
sycamorex
LQ Veteran
 
Registered: Nov 2005
Location: London
Distribution: Slackware64-current
Posts: 5,836
Blog Entries: 1

Rep: Reputation: 1251Reputation: 1251Reputation: 1251Reputation: 1251Reputation: 1251Reputation: 1251Reputation: 1251Reputation: 1251Reputation: 1251
Hmmm, what about:

Code:
lspci -nn | grep Network
See:
https://wiki.debian.org/HowToIdentifyADevice/PCI
 
Old 06-08-2014, 11:21 AM   #12
ondoho
LQ Addict
 
Registered: Dec 2013
Posts: 19,872
Blog Entries: 12

Rep: Reputation: 6053Reputation: 6053Reputation: 6053Reputation: 6053Reputation: 6053Reputation: 6053Reputation: 6053Reputation: 6053Reputation: 6053Reputation: 6053Reputation: 6053
or:
Code:
lspci -nn | grep -i net
:-)

we really have to find out about your hardware and whether linux is loading the right modules+firmware.

there's a few suspicions i have already but i'll keep them to myself until we know more.
 
Old 06-21-2014, 05:10 PM   #13
xiongnu
Member
 
Registered: Sep 2004
Distribution: Devuan, Void
Posts: 264

Original Poster
Rep: Reputation: 23
Quote:
Originally Posted by sycamorex View Post
Hmmm, what about:

Code:
lspci -nn | grep Network
See:
https://wiki.debian.org/HowToIdentifyADevice/PCI
output of 'grep' command:
Code:
root@debian:/home/erdos/Downloads# lspci -nn | grep Network
02:06.0 Network controller [0280]: Intersil Corporation ISL3874 [Prism 2.5]/ISL3872 [Prism 3] [1260:3873] (rev 01)
root@debian:/home/erdos/Downloads# lspci -nn | grep -i net
02:04.0 Ethernet controller [0200]: Accton Technology Corporation SMC2-1211TX [1113:1211] (rev 10)
02:06.0 Network controller [0280]: Intersil Corporation ISL3874 [Prism 2.5]/ISL3872 [Prism 3] [1260:3873] (rev 01)
root@debian:/home/erdos/Downloads#
 
Old 01-11-2015, 09:07 AM   #15
xiongnu
Member
 
Registered: Sep 2004
Distribution: Devuan, Void
Posts: 264

Original Poster
Rep: Reputation: 23
in the end, i configured a Linksys WRT54GL as a wi-fi repeater and connected to computer's ethernet port for net access.

this eliminated the internal wi-fi card since i can't resolve the 'bad password' error after all.
 
  


Reply


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
Wicd WiFi connection fails - bad password -wpa2 frank4360 Linux - Software 13 06-07-2024 01:33 AM
Connection Failed Bad password phillip69 Linux - Newbie 3 06-04-2012 09:16 PM
wicd bad password VisionIncision Slackware 16 01-04-2012 01:21 PM
Slackware; wicd bad password guisome Linux - Wireless Networking 3 02-20-2011 06:53 PM
Wicd - 'Bad Password' error brinesharks Linux - Wireless Networking 1 02-01-2011 06:46 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Networking

All times are GMT -5. The time now is 11:59 AM.

Main Menu
Advertisement
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
Open Source Consulting | Domain Registration