iwconfig & iwlwifi fail to connect to a WEP network

Bug #1002015 reported by Egor on 2012-05-20
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Wireless Tools
David Paleino
wicd (Ubuntu)

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/'] failed with exit code 255:
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
 **** 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
 **** List of CAPTURE Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: ALC269VB Analog [ALC269VB Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
 /dev/snd/controlC0: gluk47 5033 F.... pulseaudio
 /dev/snd/pcmC0D0p: gluk47 5033 F...m pulseaudio
 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
 PATH=(custom, user)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-24-generic root=UUID=27cbd1f6-ff3d-4b30-be3a-39441a6dea66 ro quiet splash
 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) 07/04/2011
dmi.bios.vendor: Phoenix Technologies Ltd.
dmi.bios.version: 01VG.M013.20110704.RHU
dmi.board.asset.tag: SAMSUNG 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: NC210/NC110
dmi.product.version: Not Applicable

Egor (gluk47) wrote :
Brad Figg (brad-figg) on 2012-05-20
Changed in linux (Ubuntu):
status: New → Confirmed
Joseph Salisbury (jsalisbury) wrote :

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 . 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.

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

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.

Niket Parekh (n-u-parekh) wrote :

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 ?

tags: added: precise
removed: quantal
Egor (gluk47) wrote :

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
Joseph Salisbury (jsalisbury) wrote :

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 [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.


Changed in linux (Ubuntu):
status: Confirmed → Triaged
Changed in linux:
importance: Unknown → Medium
status: Unknown → Confirmed
Changed in linux:
status: Confirmed → Incomplete
Egor (gluk47) wrote :

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
affects: linux (Ubuntu) → wicd (Ubuntu)
Changed in wicd (Ubuntu):
importance: Medium → Undecided
status: Triaged → New
no longer affects: linux
Egor (gluk47) wrote :

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
David Paleino (dpaleino) on 2012-11-21
Changed in wicd:
status: New → Triaged
importance: Undecided → Medium
assignee: nobody → David Paleino (dpaleino)
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.