wicd

iwconfig & iwlwifi fail to connect to a WEP network

Bug #1002015 reported by Egor on 2012-05-20

This bug affects 1 person

	Status	Importance	Assigned to
Wireless Tools	New	Undecided	Unassigned
wicd	Triaged	Medium	David Paleino
wicd (Ubuntu)	New	Undecided	Unassigned

Bug Description

iwlwifi driver fails to connect to a WEP-encrypted 802.11bg network.
My wireless card is
>> Intel Corporation Centrino Wireless-N 130 (rev 34)

When I connect either via wicd or iwconfig, I get a message in dmesg
>> wlan0: link not ready;

iwconfig wlan0 key ****
tells me «operation unsupported for device».

This problem is constant, I cannot connect to the network at all. As soon as I reboot my computer to M$ Windows7, everything works fine.

ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: linux-image-3.2.0-24-generic 3.2.0-24.38
ProcVersionSignature: Ubuntu 3.2.0-24.38-generic 3.2.16
Uname: Linux 3.2.0-24-generic x86_64
AcpiTables: Error: command ['gksu', '-D', 'Apport', '--', 'env', '-u', 'LANGUAGE', 'LC_MESSAGES=C', '/usr/share/apport/dump_acpi_tables.py'] failed with exit code 255:
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
AplayDevices:
**** List of PLAYBACK Hardware Devices ****
card 0: Intel [HDA Intel], device 0: ALC269VB Analog [ALC269VB Analog]
   Subdevices: 0/1
   Subdevice #0: subdevice #0
ApportVersion: 2.0.1-0ubuntu7
Architecture: amd64
ArecordDevices:
**** List of CAPTURE Hardware Devices ****
card 0: Intel [HDA Intel], device 0: ALC269VB Analog [ALC269VB Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC0: gluk47 5033 F.... pulseaudio
/dev/snd/pcmC0D0p: gluk47 5033 F...m pulseaudio
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xf0300000 irq 48'
   Mixer name : 'Realtek ALC269VB'
   Components : 'HDA:10ec0269,144dc0a8,00100100'
   Controls : 19
   Simple ctrls : 11
Date: Sun May 20 21:42:28 2012
HibernationDevice: RESUME=UUID=25859206-d32a-4f83-a67f-ce596776c8c4
MachineType: SAMSUNG ELECTRONICS CO., LTD. NC210/NC110
ProcEnviron:
LANGUAGE=
TERM=xterm
PATH=(custom, user)
LANG=ru_RU.UTF-8
SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-24-generic root=UUID=27cbd1f6-ff3d-4b30-be3a-39441a6dea66 ro quiet splash
RelatedPackageVersions:
linux-restricted-modules-3.2.0-24-generic N/A
linux-backports-modules-3.2.0-24-generic N/A
linux-firmware 1.79
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/04/2011
dmi.bios.vendor: Phoenix Technologies Ltd.
dmi.bios.version: 01VG.M013.20110704.RHU
dmi.board.asset.tag: SAMSUNG
dmi.board.name: NC210/NC110
dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.board.version: Not Applicable
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvr01VG.M013.20110704.RHU:bd07/04/2011:svnSAMSUNGELECTRONICSCO.,LTD.:pnNC210/NC110:pvrNotApplicable:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNC210/NC110:rvrNotApplicable:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:
dmi.product.name: NC210/NC110
dmi.product.version: Not Applicable
dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

Tags:

Revision history for this message

Egor (gluk47) wrote on 2012-05-20:

AlsaDevices.txt Edit (382 bytes, text/plain; charset="utf-8")
BootDmesg.txt Edit (52.0 KiB, text/plain; charset="utf-8")
CRDA.txt Edit (257 bytes, text/plain; charset="utf-8")
Card0.Amixer.values.txt Edit (2.4 KiB, text/plain; charset="utf-8")
Card0.Codecs.codec.0.txt Edit (9.0 KiB, text/plain; charset="utf-8")
CurrentDmesg.txt Edit (249.7 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (2.0 KiB, text/plain; charset="utf-8")
IwConfig.txt Edit (507 bytes, text/plain; charset="utf-8")
Lspci.txt Edit (11.9 KiB, text/plain; charset="utf-8")
Lsusb.txt Edit (394 bytes, text/plain; charset="utf-8")
PciMultimedia.txt Edit (621 bytes, text/plain; charset="utf-8")
ProcCpuinfo.txt Edit (3.0 KiB, text/plain; charset="utf-8")
ProcInterrupts.txt Edit (2.0 KiB, text/plain; charset="utf-8")
ProcModules.txt Edit (2.9 KiB, text/plain; charset="utf-8")
PulseList.txt Edit (26.3 KiB, text/plain; charset="utf-8")
RfKill.txt Edit (179 bytes, text/plain; charset="utf-8")
UdevDb.txt Edit (116.7 KiB, text/plain; charset="utf-8")
UdevLog.txt Edit (259.5 KiB, text/plain; charset="utf-8")
WifiSyslog.txt Edit (1.3 MiB, text/plain; charset="utf-8")

Brad Figg (brad-figg) on 2012-05-20

Changed in linux (Ubuntu):
status:	New → Confirmed

Revision history for this message

Joseph Salisbury (jsalisbury) wrote on 2012-05-21:

Do you know if this issue happened in a previous version of Ubuntu, or is this a new issue?

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.4kernel[1] (Not a kernel in the daily directory). Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag(Only that one tag, please leave the other tags). This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text.

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.4-precise/

Changed in linux (Ubuntu):
importance:	Undecided → Medium
status:	Confirmed → Incomplete
tags:	added: needs-upstream-testing

Revision history for this message

Egor (gluk47) wrote on 2012-05-21:

ubuntu 11.10 was also affected, the driver there was iwlagn. Actually, I discovered apport-cli just recently, that's why I haven't filed the bug earlier :)

I'll test mainline kernel, thanks for the instructions.

Revision history for this message

Niket Parekh (n-u-parekh) wrote on 2012-05-22:

I face the same problem on 12.04; the moment I changed the router to WEP Security from WPA2, Ubuntu fails to connect to internet.

Is there a bug fix ? Are some other Drivers compatible with Intel Wifi cards ?

Joseph Salisbury (jsalisbury) on 2012-05-23

tags:

added: precise
removed: quantal

Revision history for this message

Egor (gluk47) wrote on 2012-05-24:

dmesg output Edit (52.4 KiB, text/plain)

The problem is still here.
I've tested 3.4.0-030400-generic, the log is attached, it's pretty much the same (excluding version numbers :))

tags:

added: kernel-bug-exists-upstream
removed: needs-upstream-testing

Egor (gluk47) on 2012-05-25

Changed in linux (Ubuntu):
status:	Incomplete → Confirmed

Revision history for this message

Joseph Salisbury (jsalisbury) wrote on 2012-05-25:

This issue appears to be an upstream bug, since you tested the latest upstream kernel. Would it be possible for you to open an upstream bug report at bugzilla.kernel.org [1]? That will allow the upstream Developers to examine the issue, and may provide a quicker resolution to the bug.

If you are comfortable with opening a bug upstream, It would be great if you can report back the upstream bug number in this bug report. That will allow us to link this bug to the upstream report.

[1] https://wiki.ubuntu.com/Bugs/Upstream/kernel

Changed in linux (Ubuntu):
status:	Confirmed → Triaged

Bug Watch Updater (bug-watch-updater) on 2012-05-29

Changed in linux:
importance:	Unknown → Medium
status:	Unknown → Confirmed

Bug Watch Updater (bug-watch-updater) on 2012-05-30

Changed in linux:
status:	Confirmed → Incomplete

Revision history for this message

Egor (gluk47) wrote on 2012-05-30:

The bug does not affect the kernel. It's something with wicd and, possibly, iwconfig (If I use the latter correctly). I'll look through the manuals to find out where to redirect the bug.

For now I use the following solution:
# iw wlan0 connect <essid> key 0:<key> && dhclient wlan0

Egor (gluk47) on 2012-05-30

tags:

removed: kernel-bug-exists-upstream

Joseph Salisbury (jsalisbury) on 2012-05-30

affects:	linux (Ubuntu) → wicd (Ubuntu)
Changed in wicd (Ubuntu):
importance:	Medium → Undecided
status:	Triaged → New
no longer affects:	linux

Revision history for this message

Egor (gluk47) wrote on 2012-10-04:

The bug persists. I cannot auto-connect to the WEP-encrypted network.
iwconfig fails to connect,

# iw wlan0 connect <essid> key 0:<key> && dhclient wlan0
works just fine.

It'd be nice if at least wicd had an option to use iw instead of iwconfig.

affects:

wicd → wireless-tools

Egor (gluk47) on 2012-10-04

summary:	- iwlwifi fails to connect to a WEP network + iwconfig & iwlwifi fails to connect to a WEP network
summary:	- iwconfig & iwlwifi fails to connect to a WEP network + iwconfig & iwlwifi fail to connect to a WEP network