Wireless connection dropping out constantly or failing authentication

**lindsey** · 03-12-2011

Been having the worst time getting wireless up for my Desktop (Debian 6.0).

Using Wicd and it keeps dropping out or telling me "bad password" when the password is in fact correct. I even know it works because the first couple of times it worked, but the connection wasn't sustained for more than a few seconds each time.

My reasoning is my wireless is functional in Ubuntu, there's no reason it shouldn't be in Debian.

Wireless network card is ASUS PCE-N13.

Ralink driver is installed.

WPA-supplicant is installed.

Gnome Network Manager is also present, though I've heard that it doesn't support my particular situation.

Please, help.

**rokytnji** · 03-12-2011

Have you tried checking the box in Wicd>Preferences>Advanced Settings>use dbm to measure signal strength.

To expalin. I am running AntiX 11 rc1 which is based on Debian 7 Wheezy

Code:

harry@biker:~$ lsb_release -a
No LSB modules are available.
Distributor ID:	Debian
Description:	Debian GNU/Linux testing (wheezy)
Release:	testing
Codename:	wheezy

I had the same problem as you seem to have after I did my install. This problem was not present in my AntiX 8.5 install using wicd. In this new install. I would get dropped connections and weak signal strength even though I had the right driver installed and firmware.

Code:

harry@biker:~$ su -c "hwinfo --wlan"
Password: 
14: PCI 203.0: 0282 WLAN controller                             
  [Created at pci.318]
  UDI: /org/freedesktop/Hal/devices/pci_8086_4223
  Unique ID: JNkJ.UUkIjzf8b73
  Parent ID: 6NW+.Wc+DHj8LOy0
  SysFS ID: /devices/pci0000:00/0000:00:1e.0/0000:02:03.0
  SysFS BusID: 0000:02:03.0
  Hardware Class: network
  Model: "Intel PRO/Wireless 2915ABG [Calexico2] Network Connection"
  Vendor: pci 0x8086 "Intel Corporation"
  Device: pci 0x4223 "PRO/Wireless 2915ABG [Calexico2] Network Connection"
  SubVendor: pci 0x8086 "Intel Corporation"
  SubDevice: pci 0x1000 
  Revision: 0x05
  Driver: "ipw2200"
  Driver Modules: "ipw2200"
  Device File: eth1
  Features: WLAN
  Memory Range: 0xe8602000-0xe8602fff (rw,non-prefetchable)
  IRQ: 9 (no events)
  HW Address: 00:15:00:10:0a:ce
  Link detected: yes
  WLAN channels: 1 2 3 4 5 6 7 8 9 10 11 36 40 44 48 52 56 60 64 149 153 157 161 165
  WLAN frequencies: 2.412 2.417 2.422 2.427 2.432 2.437 2.442 2.447 2.452 2.457 2.462 5.18 5.2 5.22 5.24 5.26 5.28 5.3 5.32 5.745 5.765 5.785 5.805 5.825
  WLAN bitrates: 1 2 5.5 11 6 9 12 18 24 36 48 54
  WLAN encryption modes: WEP40 WEP104 TKIP CCMP
  WLAN authentication modes: open sharedkey wpa-psk wpa-eap
  Requires: ipw-firmware
  Module Alias: "pci:v00008086d00004223sv00008086sd00001000bc02sc80i00"
  Driver Info #0:
    Driver Status: ipw2200 is active
    Driver Activation Cmd: "modprobe ipw2200"
  Config Status: cfg=new, avail=yes, need=no, active=unknown
  Attached to: #4 (PCI bridge)
harry@biker:~$ su -c "hwinfo --netcard"
Password: 
22: PCI 202.0: 0200 Ethernet controller                         
  [Created at pci.318]
  UDI: /org/freedesktop/Hal/devices/pci_10ec_8139
  Unique ID: rBUF.EmzoWp5WhT7
  Parent ID: 6NW+.Wc+DHj8LOy0
  SysFS ID: /devices/pci0000:00/0000:00:1e.0/0000:02:02.0
  SysFS BusID: 0000:02:02.0
  Hardware Class: network
  Model: "Matsushita Electric Industrial Panasonic CF-Y5 laptop"
  Vendor: pci 0x10ec "Realtek Semiconductor Co., Ltd."
  Device: pci 0x8139 "RTL-8139/8139C/8139C+"
  SubVendor: pci 0x10f7 "Matsushita Electric Industrial Co., Ltd."
  SubDevice: pci 0x8338 "Panasonic CF-Y5 laptop"
  Revision: 0x10
  Driver: "8139too"
  Driver Modules: "8139too"
  Device File: eth0
  I/O Ports: 0x4400-0x44ff (rw)
  Memory Range: 0xe8603400-0xe86034ff (rw,non-prefetchable)
  IRQ: 9 (12914 events)
  HW Address: 00:80:45:29:3f:1d
  Link detected: no
  Module Alias: "pci:v000010ECd00008139sv000010F7sd00008338bc02sc00i00"
  Driver Info #0:
    Driver Status: 8139too is active
    Driver Activation Cmd: "modprobe 8139too"
  Driver Info #1:
    Driver Status: 8139cp is active
    Driver Activation Cmd: "modprobe 8139cp"
  Config Status: cfg=new, avail=yes, need=no, active=unknown
  Attached to: #13 (PCI bridge)

23: PCI 203.0: 0282 WLAN controller
  [Created at pci.318]
  UDI: /org/freedesktop/Hal/devices/pci_8086_4223
  Unique ID: JNkJ.UUkIjzf8b73
  Parent ID: 6NW+.Wc+DHj8LOy0
  SysFS ID: /devices/pci0000:00/0000:00:1e.0/0000:02:03.0
  SysFS BusID: 0000:02:03.0
  Hardware Class: network
  Model: "Intel PRO/Wireless 2915ABG [Calexico2] Network Connection"
  Vendor: pci 0x8086 "Intel Corporation"
  Device: pci 0x4223 "PRO/Wireless 2915ABG [Calexico2] Network Connection"
  SubVendor: pci 0x8086 "Intel Corporation"
  SubDevice: pci 0x1000 
  Revision: 0x05
  Driver: "ipw2200"
  Driver Modules: "ipw2200"
  Device File: eth1
  Features: WLAN
  Memory Range: 0xe8602000-0xe8602fff (rw,non-prefetchable)
  IRQ: 9 (12914 events)
  HW Address: 00:15:00:10:0a:ce
  Link detected: yes
  WLAN channels: 1 2 3 4 5 6 7 8 9 10 11 36 40 44 48 52 56 60 64 149 153 157 161 165
  WLAN frequencies: 2.412 2.417 2.422 2.427 2.432 2.437 2.442 2.447 2.452 2.457 2.462 5.18 5.2 5.22 5.24 5.26 5.28 5.3 5.32 5.745 5.765 5.785 5.805 5.825
  WLAN bitrates: 1 2 5.5 11 6 9 12 18 24 36 48 54
  WLAN encryption modes: WEP40 WEP104 TKIP CCMP
  WLAN authentication modes: open sharedkey wpa-psk wpa-eap
  Requires: ipw-firmware
  Module Alias: "pci:v00008086d00004223sv00008086sd00001000bc02sc80i00"
  Driver Info #0:
    Driver Status: ipw2200 is active
    Driver Activation Cmd: "modprobe ipw2200"
  Config Status: cfg=new, avail=yes, need=no, active=unknown
  Attached to: #13 (PCI bridge)

I fought this problem in ceni, and rutilt. Which are different network tools than wicd. But when I enabled use dbm to measure signal strength. Things settled down in Wicd. I don't know why this fixed it. Just know that was what sorted wicd for me. My wicd version is

Code:

harry@biker:~$ apt-cache policy wicd
wicd:
  Installed: 1.7.0+ds1-6
  Candidate: 1.7.0+ds1-6
  Version table:
 *** 1.7.0+ds1-6 0
        500 http://ftp.us.debian.org/debian/ testing/main i386 Packages
        100 /var/lib/dpkg/status

I have written this response in the hope you learn how to ask wireless questions with the intent to provide what you have tried, Pertinent info, instead of the generic

My reasoning is my wireless is functional in Ubuntu, there's no reason it shouldn't be in Debian.

Which are worlds apart in operating system philosophy. So hope my post helps you in more than just wireless. Otherwise, you may just as well run Ubuntu if that works for you better than Debian. I would if it was me. Not a Linux Fanboy. Just a spaced out tattoed linux using biker.

Happy Trails, Rok

**lindsey** · 03-13-2011

Originally Posted by rokytnji

Have you tried checking the box in Wicd>Preferences>Advanced Settings>use dbm to measure signal strength.

To expalin. I am running AntiX 11 rc1 which is based on Debian 7 Wheezy

Code:

harry@biker:~$ lsb_release -a
No LSB modules are available.
Distributor ID:	Debian
Description:	Debian GNU/Linux testing (wheezy)
Release:	testing
Codename:	wheezy

I had the same problem as you seem to have after I did my install. This problem was not present in my AntiX 8.5 install using wicd. In this new install. I would get dropped connections and weak signal strength even though I had the right driver installed and firmware.

Code:

harry@biker:~$ su -c "hwinfo --wlan"
Password: 
14: PCI 203.0: 0282 WLAN controller                             
  [Created at pci.318]
  UDI: /org/freedesktop/Hal/devices/pci_8086_4223
  Unique ID: JNkJ.UUkIjzf8b73
  Parent ID: 6NW+.Wc+DHj8LOy0
  SysFS ID: /devices/pci0000:00/0000:00:1e.0/0000:02:03.0
  SysFS BusID: 0000:02:03.0
  Hardware Class: network
  Model: "Intel PRO/Wireless 2915ABG [Calexico2] Network Connection"
  Vendor: pci 0x8086 "Intel Corporation"
  Device: pci 0x4223 "PRO/Wireless 2915ABG [Calexico2] Network Connection"
  SubVendor: pci 0x8086 "Intel Corporation"
  SubDevice: pci 0x1000 
  Revision: 0x05
  Driver: "ipw2200"
  Driver Modules: "ipw2200"
  Device File: eth1
  Features: WLAN
  Memory Range: 0xe8602000-0xe8602fff (rw,non-prefetchable)
  IRQ: 9 (no events)
  HW Address: 00:15:00:10:0a:ce
  Link detected: yes
  WLAN channels: 1 2 3 4 5 6 7 8 9 10 11 36 40 44 48 52 56 60 64 149 153 157 161 165
  WLAN frequencies: 2.412 2.417 2.422 2.427 2.432 2.437 2.442 2.447 2.452 2.457 2.462 5.18 5.2 5.22 5.24 5.26 5.28 5.3 5.32 5.745 5.765 5.785 5.805 5.825
  WLAN bitrates: 1 2 5.5 11 6 9 12 18 24 36 48 54
  WLAN encryption modes: WEP40 WEP104 TKIP CCMP
  WLAN authentication modes: open sharedkey wpa-psk wpa-eap
  Requires: ipw-firmware
  Module Alias: "pci:v00008086d00004223sv00008086sd00001000bc02sc80i00"
  Driver Info #0:
    Driver Status: ipw2200 is active
    Driver Activation Cmd: "modprobe ipw2200"
  Config Status: cfg=new, avail=yes, need=no, active=unknown
  Attached to: #4 (PCI bridge)
harry@biker:~$ su -c "hwinfo --netcard"
Password: 
22: PCI 202.0: 0200 Ethernet controller                         
  [Created at pci.318]
  UDI: /org/freedesktop/Hal/devices/pci_10ec_8139
  Unique ID: rBUF.EmzoWp5WhT7
  Parent ID: 6NW+.Wc+DHj8LOy0
  SysFS ID: /devices/pci0000:00/0000:00:1e.0/0000:02:02.0
  SysFS BusID: 0000:02:02.0
  Hardware Class: network
  Model: "Matsushita Electric Industrial Panasonic CF-Y5 laptop"
  Vendor: pci 0x10ec "Realtek Semiconductor Co., Ltd."
  Device: pci 0x8139 "RTL-8139/8139C/8139C+"
  SubVendor: pci 0x10f7 "Matsushita Electric Industrial Co., Ltd."
  SubDevice: pci 0x8338 "Panasonic CF-Y5 laptop"
  Revision: 0x10
  Driver: "8139too"
  Driver Modules: "8139too"
  Device File: eth0
  I/O Ports: 0x4400-0x44ff (rw)
  Memory Range: 0xe8603400-0xe86034ff (rw,non-prefetchable)
  IRQ: 9 (12914 events)
  HW Address: 00:80:45:29:3f:1d
  Link detected: no
  Module Alias: "pci:v000010ECd00008139sv000010F7sd00008338bc02sc00i00"
  Driver Info #0:
    Driver Status: 8139too is active
    Driver Activation Cmd: "modprobe 8139too"
  Driver Info #1:
    Driver Status: 8139cp is active
    Driver Activation Cmd: "modprobe 8139cp"
  Config Status: cfg=new, avail=yes, need=no, active=unknown
  Attached to: #13 (PCI bridge)

23: PCI 203.0: 0282 WLAN controller
  [Created at pci.318]
  UDI: /org/freedesktop/Hal/devices/pci_8086_4223
  Unique ID: JNkJ.UUkIjzf8b73
  Parent ID: 6NW+.Wc+DHj8LOy0
  SysFS ID: /devices/pci0000:00/0000:00:1e.0/0000:02:03.0
  SysFS BusID: 0000:02:03.0
  Hardware Class: network
  Model: "Intel PRO/Wireless 2915ABG [Calexico2] Network Connection"
  Vendor: pci 0x8086 "Intel Corporation"
  Device: pci 0x4223 "PRO/Wireless 2915ABG [Calexico2] Network Connection"
  SubVendor: pci 0x8086 "Intel Corporation"
  SubDevice: pci 0x1000 
  Revision: 0x05
  Driver: "ipw2200"
  Driver Modules: "ipw2200"
  Device File: eth1
  Features: WLAN
  Memory Range: 0xe8602000-0xe8602fff (rw,non-prefetchable)
  IRQ: 9 (12914 events)
  HW Address: 00:15:00:10:0a:ce
  Link detected: yes
  WLAN channels: 1 2 3 4 5 6 7 8 9 10 11 36 40 44 48 52 56 60 64 149 153 157 161 165
  WLAN frequencies: 2.412 2.417 2.422 2.427 2.432 2.437 2.442 2.447 2.452 2.457 2.462 5.18 5.2 5.22 5.24 5.26 5.28 5.3 5.32 5.745 5.765 5.785 5.805 5.825
  WLAN bitrates: 1 2 5.5 11 6 9 12 18 24 36 48 54
  WLAN encryption modes: WEP40 WEP104 TKIP CCMP
  WLAN authentication modes: open sharedkey wpa-psk wpa-eap
  Requires: ipw-firmware
  Module Alias: "pci:v00008086d00004223sv00008086sd00001000bc02sc80i00"
  Driver Info #0:
    Driver Status: ipw2200 is active
    Driver Activation Cmd: "modprobe ipw2200"
  Config Status: cfg=new, avail=yes, need=no, active=unknown
  Attached to: #13 (PCI bridge)

I fought this problem in ceni, and rutilt. Which are different network tools than wicd. But when I enabled use dbm to measure signal strength. Things settled down in Wicd. I don't know why this fixed it. Just know that was what sorted wicd for me. My wicd version is

Code:

harry@biker:~$ apt-cache policy wicd
wicd:
  Installed: 1.7.0+ds1-6
  Candidate: 1.7.0+ds1-6
  Version table:
 *** 1.7.0+ds1-6 0
        500 http://ftp.us.debian.org/debian/ testing/main i386 Packages
        100 /var/lib/dpkg/status

I have written this response in the hope you learn how to ask wireless questions with the intent to provide what you have tried, Pertinent info, instead of the generic

Which are worlds apart in operating system philosophy. So hope my post helps you in more than just wireless. Otherwise, you may just as well run Ubuntu if that works for you better than Debian. I would if it was me. Not a Linux Fanboy. Just a spaced out tattoed linux using biker.

Happy Trails, Rok

Thank you for your suggestion Rok.

Yes I've heard about dbm method. It doesn't seem to help in my case. If I do manage to get connected, it's only momentarily before it drops out again.

I really want to use Debian so Ubuntu isn't a solution for me presently...

**rokytnji** · 03-13-2011

Look in /var/log/wicd and see what it says about dropping connections. Maybe it will shed some light on why it is dropping out.

**lindsey** · 03-14-2011

Originally Posted by rokytnji

Look in /var/log/wicd and see what it says about dropping connections. Maybe it will shed some light on why it is dropping out.

Sorry for the delay in getting back.

/var/log/wicd seemed empty?

In any case, the situation appears to have improved. Note sure exactly what did it, but it was probably some helpful combination of rebooting my router, rebooting Debian and disabling Network Manager. Still not as good compared to its performance in Windows but drops out only occasionally now. Very happy.

Thanks Rok.

**rokytnji** · 03-14-2011

Some things you can try in Wicd since I use it exclusively to connect with wireless.

Go to Wicd>Preferences>External Programs and change from Automatic to dhclient. See if connection drops quit. you can always change it back.

On my Debian Wheezy based AntiX. I had to also go to Wicd>Prefernces>Advanced Settings and tick on te box Use dbm to measure signal strength to settle wicd down. I was dropping connection every few seconds on it till I did that. But that was in AntiX 11 rc1 whic is still a testing release distro so some bugs are expected.

Glad you have it sorted somewhat.
.

Thread Tools

Display

Wireless connection dropping out constantly or failing authentication

Posting Permissions