[Toshiba L735-101] hotkeys don't work before system has been suspended in Precise.

[Swâmi Petaramesh]

Hi,

My Toshiba L735-101 has [Fn]}[some_key] hotkeys for a number of features, i.e.:
- Sound volume +/- / Mute
- Suspend to RAM, hibernate
- Backlight brightness +/-
- Wi-Fi On-Off
- Numlock
- Touchpad on/off
- Etc...

I've noticed something quite weird : Right after bootup, most of these hotkeys don't work at all - except for sound volume and NumLock that work.

But once after I have suspended to RAM then resumed the system, all hotkeys work OK.

This is perfectly reproductible, everytime.

(I have another issue : the screen brightess keys to display a brightness popup with a "level bar" that reacts, but besides this it has no effect on the actual screen brightness, but I will file a separate bug report for this one.)

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: linux-image-3.2.0-21-generic 3.2.0-21.34
ProcVersionSignature: Ubuntu 3.2.0-21.34-generic 3.2.13
Uname: Linux 3.2.0-21-generic i686
NonfreeKernelModules: nvidia
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 2.0-0ubuntu2
Architecture: i386
CheckboxSubmission: 1ea6109db29b53f721a523a77b7f3abf
CheckboxSystem: d00f84de8a555815fa1c4660280da308
Date: Mon Apr 2 19:25:04 2012
EcryptfsInUse: Yes
HibernationDevice: RESUME=UUID=0e7ded16-c4fc-4f81-8562-3cb1196809d3
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
MachineType: TOSHIBA SATELLITE L735
ProcEnviron:
 LANGUAGE=fr_FR:fr:en_US:en
 TERM=xterm
 PATH=(custom, user)
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.2.0-21-generic root=/dev/mapper/VG1-UBUNTU ro rdblacklist=nouveau nouveau.blacklist=1 acpi_backlight=vendor clocksource=hpet rdblacklist=nouveau nouveau.blacklist=1 acpi_backlight=vendor quiet splash vt.handoff=7
SourcePackage: linux
StagingDrivers: rts5139 mei
UpgradeStatus: Upgraded to precise on 2012-03-10 (23 days ago)
dmi.bios.date: 02/10/2012
dmi.bios.vendor: INSYDE
dmi.bios.version: 2.20
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: Base Board Product Name
dmi.board.vendor: Intel Corp.
dmi.board.version: Base Board Version
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: OEM Chassis Manufacturer
dmi.chassis.version: OEM Chassis Version
dmi.modalias: dmi:bvnINSYDE:bvr2.20:bd02/10/2012:svnTOSHIBA:pnSATELLITEL735:pvrPSK0CE-00900LFR:rvnIntelCorp.:rnBaseBoardProductName:rvrBaseBoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:
dmi.product.name: SATELLITE L735
dmi.product.version: PSK0CE-00900LFR
dmi.sys.vendor: TOSHIBA

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

http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.4-rc1-precise/

[Launchpad Janitor (janitor)]

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

[Stephen (sawjew)]

I have the same problem here with a Toshiba Satellite E300 running Kubuntu 12.10. I haad the same problem with Kubuntu and Ubuntu 11.04, also affects Linux Mint 13 but appears to work correctly in OpenSuse 12.2.

I upgraded to 12.10 hoping it would fix the problem but it hasn't.

[Swâmi Petaramesh (swami-petaramesh)]

Hum forget it. My previous comment is a mistake, I mixed bugs and thought it was just about the screen brightness hotkeys.

The only things true there is that I now run ArchLinux with a 3.12.4-1-ARCH kernel, have BIOS 2.50 and still have the "can't set backlight brightness" issue. For the "other hotkeys", I don't remember having noticed any issue for long (possibly the BIOS upgrade fixed it, possibly upgrading from Precise did it, possibly changing for Arch ?), so as far as I'm concerned, I'm not concerned anymore ;-)

[penalvch (penalvch)]

Swâmi Petaramesh, this bug report is being closed due to your last comment https://bugs.launchpad.net/ubuntu/+source/linux/+bug/971734/comments/7 regarding this being fixed with an update. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find.