Centrino Wireless-N + WiMAX 6150 (rev 67) Cannot Associate/Connect with Wireless AP

[TonyLudwick]

Sees Wireless Networks but cannot connect to them.

ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: linux-image-3.0.0-15-generic 3.0.0-15.26
ProcVersionSignature: Ubuntu 3.0.0-15.26-generic 3.0.13
Uname: Linux 3.0.0-15-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 1.23-0ubuntu4
Architecture: amd64
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: PCH [HDA Intel PCH], device 0: ALC269VB Analog [ALC269VB Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: guestuser 2008 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'PCH'/'HDA Intel PCH at 0xdfc00000 irq 52'
   Mixer name : 'Intel CougarPoint HDMI'
   Components : 'HDA:10ec0269,10431bd3,00100100 HDA:80862805,80860101,00100000'
   Controls : 18
   Simple ctrls : 10
Date: Fri Jan 27 08:48:32 2012
HibernationDevice: RESUME=UUID=3a8f509f-4399-41f6-87d5-72a11c89816e
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
MachineType: ASUSTeK Computer Inc. U56E
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-15-generic root=UUID=4378dac9-b7d4-4446-bac0-8a68c1878716 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.0.0-15-generic N/A
 linux-backports-modules-3.0.0-15-generic N/A
 linux-firmware 1.60
SourcePackage: linux
StagingDrivers: mei
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/26/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: U56E.208
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: U56E
dmi.board.vendor: ASUSTeK Computer Inc.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK Computer Inc.
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrU56E.208:bd07/26/2011:svnASUSTeKComputerInc.:pnU56E:pvr1.0:rvnASUSTeKComputerInc.:rnU56E:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
dmi.product.name: U56E
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK Computer Inc.

[Chris J Arges (arges)]

This bug is directly related to: http://bugzilla.intellinuxwireless.org/show_bug.cgi?id=2325

[Chris J Arges (arges)]

Depending on your configuration the following should fix the issue:

sudo rmmod iwlagn
sudo modprobe iwlagn bt_coex_active=0

or

sudo rmmod iwlwifi
sudo modprobe iwlwifi bt_coex_active=0

[Chris J Arges (arges)]

This bug is NOT a duplicate of http://launchpad.net/bugs/876147. Specifically the issue in 876147 can be fixed by disabling N-mode wireless. This particular issue in the bug cannot be solved by disabling N-mode wireless, but rather by setting bt_coex_active in the wireless module.

[Shannon Fast (sfast253025)]

I am new to Linux and seem to have this issue as well. The following commands work temporarily, but if I reboot or shutdown my computer, the wireless again does not connect.

sudo rmmod iwlwifi
sudo modprobe iwlwifi bt_coex_active=0

I am using the 12.04 release of Ubuntu. Any ideas? I suspect user error on my part may be in part to blame, since I'm still finding my way around linux. Thanks!

[Shannon Fast (sfast253025)]

Nevermind, I figured it out. I had to go into etc/modprobe.d and add a text file with options iwlwifi bt_coex_active=0.

[Bob Blanchard (blabj)]

This issue still exists with latest LTS, Linux 3.2.0-35-generic #55-Ubuntu SMP Wed Dec 5 17:42:16 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux

This workaround with bt_coex_active=0 works, but a more permanent fix should be found.

The related bug has been closed, but it has not been fixed. One of the final comments in that thread : "the problem is that BT devices on some platforms behave well with Intel's WiFi and on some platforms they don't"... not really a solution.

[Benjamin Hergert (bhergert)]

I have a theory that this is because the U56e doesn't have bluetooth and so trying to force bt_coex fails. That may explain why it only fails on some versions of the same wireless.