wireless switch not working (HP Pavilion dv1550se w/ 2200BG)

Bug #616076 reported by S. Christian Collins
20
This bug affects 4 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Low
Unassigned

Bug Description

** Bug Description **
Using kernel 2.6.33 or later, the wireless switch on my HP Pavilion dv1550se no longer activates the wireless card. Pressing the wireless button does absolutely nothing (nothing lights up, no network activity). Using kernel 2.6.32.* or earlier, the wireless button will cause the button to light up, the wireless LED to flash and wireless networks to be detected (note: it has to be pressed twice initially, but it does work).

I have tested the following system combinations:
 . Ubuntu Hardy through Lucid, kernels up to 2.6.32-24.39: wireless works
 . Ubuntu Lucid, kernels 2.6.33 through 2.6.35-rc6 (courtesy of mainline kernel ppa): wireless broken
 . Ubuntu Maverick alpha3, kernel 2.6.35-14 via live CD: wireless broken

All kernels seem to detect the wireless hardware, while indicating that the wireless "kill switch" is turned on.

WORKAROUND: Install rfkill and add the following command to run on startup:
rfkill unblock wifi

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: linux-image-generic 2.6.35.14.15
Regression: Yes
Reproducible: Yes
ProcVersionSignature: Ubuntu 2.6.35-14.19-generic 2.6.35
Uname: Linux 2.6.35-14-generic i686
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
Architecture: i386
AudioDevicesInUse:
 Cannot stat file /proc/2634/fd/30: Stale NFS file handle
                      USER PID ACCESS COMMAND
 /dev/snd/controlC0: ubuntu 2644 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'ICH6'/'Intel ICH6 with Cx20468-31 at irq 17'
   Mixer name : 'Conexant Cx20468-31'
   Components : 'AC97a:43585430'
   Controls : 23
   Simple ctrls : 16
Date: Tue Aug 10 21:06:07 2010
LiveMediaBuild: Ubuntu 10.10 "Maverick Meerkat" - Alpha i386 (20100803.1)
Lsusb:
 Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Hewlett-Packard HP Pavilion dv1000 (EP347UA#ABA)
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcCmdLine: file=/cdrom/preseed/hostname.seed boot=casper initrd=/casper/initrd.lz quiet splash --
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
RelatedPackageVersions: linux-firmware 1.37
SourcePackage: linux
dmi.bios.date: 03/23/2006
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: F.22
dmi.board.name: 308F
dmi.board.vendor: Quanta
dmi.board.version: 46.13
dmi.chassis.type: 10
dmi.chassis.vendor: Quanta
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnHewlett-Packard:bvrF.22:bd03/23/2006:svnHewlett-Packard:pnHPPaviliondv1000(EP347UA#ABA):pvrRev1:rvnQuanta:rn308F:rvr46.13:cvnQuanta:ct10:cvrN/A:
dmi.product.name: HP Pavilion dv1000 (EP347UA#ABA)
dmi.product.version: Rev 1
dmi.sys.vendor: Hewlett-Packard

Revision history for this message
S. Christian Collins (s-chriscollins) wrote :
Revision history for this message
S. Christian Collins (s-chriscollins) wrote :

Bug still present in Maverick RC1.

Revision history for this message
S. Christian Collins (s-chriscollins) wrote :

My current workaround:
1) Install rfkill
2) Add the following command to run on startup: rfkill unblock wifi

Revision history for this message
Koby (kobayashison) wrote :

I had the same problem but now it works again without having to "rfkill unblock all" after the kernel upgrade from 2.6.35-23-generic-pae to 2.6.35-24-generic-pae. I can't be sure that was thanks to the upgrade.

Revision history for this message
Koby (kobayashison) wrote :

With 2.6.35-27-generic-pae kernel works only if at the boot the switch was on. Booting with the switch off, is not possible to turn the wifi on even using "rfkill unblock"

Brad Figg (brad-figg)
Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
penalvch (penalvch) wrote :

S. Christian Collins, thank you for reporting this and helping make Ubuntu better. Maverick reached EOL on April 10, 2012.
Please see this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We were wondering if this is still an issue in a supported release? If so, can you try with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ .

If it remains an issue, could you run the following command in a supported release from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux <replace-with-bug-number>

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. 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'.

Please let us know your results. Thanks in advance.

penalvch (penalvch)
description: updated
Changed in linux (Ubuntu):
importance: Undecided → Low
status: Confirmed → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Changed in linux (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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