No wifi connection possible with intel centrino wireless-n 1000 on Maverick while Bluetooth is turned off
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Expired
|
Undecided
|
Unassigned | ||
Bug Description
After upgrading to Ubuntu 10.10 my wifi card (Intel Centrino Wireless-N 1000) stopped working. NetworkManager (and
airodump-ng) show me lists of networks and NetworkManager can try to connect to one, but it never finishes to connect.
dmesg indicates that there is something wrong:
[ 120.616099] wlan0: direct probe to 00:27:0d:09:be:d1 (try 1)
[ 120.816053] wlan0: direct probe to 00:27:0d:09:be:d1 (try 2)
[ 121.016064] wlan0: direct probe to 00:27:0d:09:be:d1 (try 3)
[ 121.216176] wlan0: direct probe to 00:27:0d:09:be:d1 timed out
This block of messages is repeated until I stop trying to connect. It happens on multiple networks, I tried it on n and b/g networks, encrypted with WPA2 and without any encryption at all). The messages are always the same.
After collecting the information for this bug report, a more informative message popped out of dmesg:
[ 264.658594] iwlagn 0000:03:00.0: Microcode SW error detected. Restarting 0x2000000.
[ 264.658606] iwlagn 0000:03:00.0: Loaded firmware version: 128.50.3.1 build 13488
[ 264.658628] iwlagn 0000:03:00.0: Start IWL Error Log Dump:
[ 264.658635] iwlagn 0000:03:00.0: Status: 0x0002B2E4, count: 5
[ 264.658795] iwlagn 0000:03:00.0: Desc Time data1 data2 line
[ 264.658805] iwlagn 0000:03:00.0: NMI_INTERRUPT_WDG (#04) 0010254915 0x00000002 0x07030000 33398
[ 264.658812] iwlagn 0000:03:00.0: pc blink1 blink2 ilink1 ilink2 hcmd
[ 264.658821] iwlagn 0000:03:00.0: 0x006D0 0x00596 0x006D4 0x00892 0x18730 0x0001C
[ 264.658827] iwlagn 0000:03:00.0: CSR values:
[ 264.658833] iwlagn 0000:03:00.0: (2nd byte of CSR_INT_COALESCING is CSR_INT_
[ 264.658844] iwlagn 0000:03:00.0: CSR_HW_
[ 264.658853] iwlagn 0000:03:00.0: CSR_INT_COALESCING: 0X00000040
[ 264.658862] iwlagn 0000:03:00.0: CSR_INT: 0X00000000
[ 264.658871] iwlagn 0000:03:00.0: CSR_INT_MASK: 0X00000000
[ 264.658880] iwlagn 0000:03:00.0: CSR_FH_INT_STATUS: 0X00000000
[ 264.658889] iwlagn 0000:03:00.0: CSR_GPIO_IN: 0X00000000
[ 264.658899] iwlagn 0000:03:00.0: CSR_RESET: 0X00000000
[ 264.658908] iwlagn 0000:03:00.0: CSR_GP_CNTRL: 0X080403c5
[ 264.658917] iwlagn 0000:03:00.0: CSR_HW_REV: 0X0000006c
[ 264.658926] iwlagn 0000:03:00.0: CSR_EEPROM_REG: 0X007708e5
[ 264.658935] iwlagn 0000:03:00.0: CSR_EEPROM_GP: 0X90000001
[ 264.658944] iwlagn 0000:03:00.0: CSR_OTP_GP_REG: 0X00010001
[ 264.658953] iwlagn 0000:03:00.0: CSR_GIO_REG: 0X00080046
[ 264.658963] iwlagn 0000:03:00.0: CSR_GP_UCODE_REG: 0X0000116b
[ 264.658972] iwlagn 0000:03:00.0: CSR_GP_DRIVER_REG: 0X00000000
[ 264.658981] iwlagn 0000:03:00.0: CSR_UCODE_DRV_GP1: 0X00000000
[ 264.658990] iwlagn 0000:03:00.0: CSR_UCODE_DRV_GP2: 0X00000000
[ 264.658999] iwlagn 0000:03:00.0: CSR_LED_REG: 0X00000058
[ 264.659008] iwlagn 0000:03:00.0: CSR_DRAM_
[ 264.659017] iwlagn 0000:03:00.0: CSR_GIO_
[ 264.659026] iwlagn 0000:03:00.0: CSR_ANA_PLL_CFG: 0X00880300
[ 264.659035] iwlagn 0000:03:00.0: CSR_HW_REV_WA_REG: 0X0001001a
[ 264.659044] iwlagn 0000:03:00.0: CSR_DBG_
[ 264.659051] iwlagn 0000:03:00.0: FH register values:
[ 264.659069] iwlagn 0000:03:00.0: FH_RSCSR_
[ 264.659089] iwlagn 0000:03:00.0: FH_RSCSR_
[ 264.659108] iwlagn 0000:03:00.0: FH_RSCSR_
[ 264.659127] iwlagn 0000:03:00.0: FH_MEM_
[ 264.659146] iwlagn 0000:03:00.0: FH_MEM_
[ 264.659166] iwlagn 0000:03:00.0: FH_MEM_
[ 264.659185] iwlagn 0000:03:00.0: FH_MEM_
[ 264.659204] iwlagn 0000:03:00.0: FH_TSSR_
[ 264.659223] iwlagn 0000:03:00.0: FH_TSSR_
[ 264.659286] iwlagn 0000:03:00.0: Start IWL Event Log Dump: display last 1 entries
[ 264.659310] iwlagn 0000:03:00.0: EVT_LOGT:
As i said, this behavior only appeared after upgrading to Ubuntu 10.10. However, I could _not_ get the wifi to work by booting Ubuntu 10.04.1 from a Live-USB-drive. I also tried the mainline kernel corresponding to my current kernel version (mainline kernel 2.6.35.4) which didn't help.
Windows 7 x64 Prof. on the same machine can connect to wifi networks just fine, so the error does not seem to be hardware related.
As long as this error persists, I cannot use my wifi card at all.
ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: linux-image-
Regression: No
Reproducible: Yes
ProcVersionSign
Uname: Linux 2.6.35-
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
Architecture: i386
ArecordDevices:
**** List of CAPTURE Hardware Devices ****
card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xe4500000 irq 47'
Mixer name : 'IDT 92HD81B1X5'
Components : 'HDA:111d7605,
Controls : 14
Simple ctrls : 9
Card1.Amixer.info:
Card hw:1 'HDMI'/'HDA ATI HDMI at 0xe4410000 irq 48'
Mixer name : 'ATI R6xx HDMI'
Components : 'HDA:1002aa01,
Controls : 4
Simple ctrls : 1
Card1.Amixer.
Simple mixer control 'IEC958',0
Capabilities: pswitch pswitch-joined penum
Playback channels: Mono
Mono: Playback [on]
Date: Tue Oct 19 15:36:29 2010
EcryptfsInUse: Yes
HibernationDevice: RESUME=
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
MachineType: Hewlett-Packard HP TouchSmart tm2 Notebook PC
ProcCmdLine: BOOT_IMAGE=
ProcEnviron:
PATH=(custom, user)
LANG=en_GB.utf8
SHELL=/bin/bash
RelatedPackageV
SourcePackage: linux
dmi.bios.date: 06/09/2010
dmi.bios.vendor: Insyde
dmi.bios.version: F.09
dmi.board.
dmi.board.name: 3661
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 47.1A
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.
dmi.modalias: dmi:bvnInsyde:
dmi.product.name: HP TouchSmart tm2 Notebook PC
dmi.product.
dmi.sys.vendor: Hewlett-Packard
tags: | added: regression-release |
summary: |
No wifi connection possible at all (neither n nor b/g) with intel - centrino wireless-n 1000 + centrino wireless-n 1000 on Maverick |
Changed in linux (Ubuntu): | |
status: | New → Confirmed |
I noticed that this might be a duplicate of bug #614537. I'm not sure, though, since I did not use the modprobe options mentioned there.