[HP Pavilion g7-1260us Notebook PC] "hp-wmi" module does not toggle wireless

[Ben Wolsieffer]

I am running Ubuntu 13.10 on an HP g7-1260 laptop, which has a wireless toggle button on the keyboard. This button has a light that is supposed to turn orange when the wifi is disabled and blue when it is enabled. The button should be activated when the fn+f12 combination is pressed, but this does not happen. I am guessing that this is caused by the hp-wmi kernel module not translating the key press into a toggle event. The wireless can be turned on and off manually using the Ubuntu menu and with rfkill. The light on the key responds when the wireless is enabled and disabled.

ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: linux-image-3.11.0-12-generic 3.11.0-12.19
ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
Uname: Linux 3.11.0-12-generic x86_64
ApportVersion: 2.12.5-0ubuntu2.1
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: ben 1889 F.... pulseaudio
 /dev/snd/pcmC0D0p: ben 1889 F...m pulseaudio
Date: Tue Oct 29 20:37:38 2013
HibernationDevice: RESUME=UUID=1025f6e7-4431-401d-919f-9f50f52b7a03
InstallationDate: Installed on 2013-08-26 (64 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
MachineType: Hewlett-Packard HP Pavilion g7 Notebook PC
MarkForUpload: True
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic root=UUID=bb8ada94-d922-4248-b874-caaf31211026 ro acpi_osi=Linux acpi_backlight=vendor quiet splash acpi=force vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.11.0-12-generic N/A
 linux-backports-modules-3.11.0-12-generic N/A
 linux-firmware 1.116
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
SourcePackage: linux
UpgradeStatus: Upgraded to saucy on 2013-10-19 (10 days ago)
dmi.bios.date: 10/23/2012
dmi.bios.vendor: Insyde
dmi.bios.version: F.65
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 1671
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 09.4C
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnInsyde:bvrF.65:bd10/23/2012:svnHewlett-Packard:pnHPPaviliong7NotebookPC:pvr0691120000204610000620100:rvnHewlett-Packard:rn1671:rvr09.4C:cvnHewlett-Packard:ct10:cvrChassisVersion:
dmi.product.name: HP Pavilion g7 Notebook PC
dmi.product.version: 0691120000204610000620100
dmi.sys.vendor: Hewlett-Packard

[Brad Figg (brad-figg)]

This change was made by a bot.

[Joseph Salisbury (jsalisbury)]

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.12 kernel[0].

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.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.12-rc7-saucy/

[Ben Wolsieffer (benwolsieffer)]

I upgraded my BIOS to F.66 successfully and it did not change anything. I upgraded it by booting into Windows 7 (I have a dual boot setup) and running the upgrade program.

Here is the output of "sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date":
F.66
01/24/2013

[penalvch (penalvch)]

Ben W., did this issue not occur in a release prior to Saucy?

[Ben Wolsieffer (benwolsieffer)]

I don't know if it did, because even though I had Raring installed before I upgraded to Saucy, I didn't really use it much so I did not notice this bug until recently when I started using Ubuntu more.

[penalvch (penalvch)]

Ben W., for regression testing purposes, could you please test Precise via http://releases.ubuntu.com/precise/ and advise to the results?

[Jason Rogers (tertiary-adjunct)]

I have a HP Pavilion DV7 and I have the same issue with 13.10, however this is not a problem under 12.10.
I don't know if 13.04 is affected.

[penalvch (penalvch)]

Jason Rogers, if you have a bug in Ubuntu, the Ubuntu Kernel team, Ubuntu Bug Control team, and Ubuntu Bug Squad would like you to please file a new report by executing the following in a terminal while booted into a Ubuntu repository kernel (not a mainline one) via:
ubuntu-bug linux

For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Please note, not filing a new report would delay your problem being addressed as quickly as possible.

No need exists to comment here at this time. After reading the above documentation in it's entirety, if you have further questions, you are welcome to redirect them to the appropriate mailing list or forum via http://www.ubuntu.com/support/community/mailinglists , or you may contact me directly.

Thank you for your understanding.

[Launchpad Janitor (janitor)]

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

[Mauro (mauromol)]

I have this exact same issue on Linux Mint 16 KDE (based on Ubuntu 13.10) and an HP ProBook G1 450. However in my case, I don't have to use FN+F12, but I have a dedicated button with led (orange = wifi disabled, white = wifi enabled). This button doesn't do anything, though, although it turns orange when I do "rfkill block 0" and white when I do "rfkill unblock 0".

When I press the button to switch wireless on and off, nothing happens, as I said, but I see this in dmesg:
[ 135.505274] atkbd serio0: Unknown key pressed (translated set 2, code 0xf8 on isa0060/serio0).
[ 135.505285] atkbd serio0: Use 'setkeycodes e078 <keycode>' to make it known.
[ 135.690922] atkbd serio0: Unknown key released (translated set 2, code 0xf8 on isa0060/serio0).
[ 135.690932] atkbd serio0: Use 'setkeycodes e078 <keycode>' to make it known.

[penalvch (penalvch)]

Mauro, thank you for your comment. So your hardware and problem may be tracked, could you please file a new report with Ubuntu by executing the following in a terminal while booted into Ubuntu (not Mint) via:
ubuntu-bug linux

For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs