brightness hotkeys not functional on Lenovo Ideapad u450p

Also to note the function+key layout on this laptop is a bit different from other Lenovos I've used in the past.

The brightness keys are function+up and function+down. Just to note volume up and volume down are function+left, and function+right, and both of those are working properly.

--chris

Can you please find the scan codes for the brightness hotkeys, as described in /usr/share/doc/udev/README.keymap.txt.gz ? Thanks!

On 04/29/2010 12:39 AM, Martin Pitt wrote:
> Can you please find the scan codes for the brightness hotkeys, as
> described in /usr/share/doc/udev/README.keymap.txt.gz ? Thanks!

Hi Martin -- I went through the steps outlined:

vanhoof@reptar:~$ /lib/udev/findkeyboards
AT keyboard: input/event5

vanhoof@reptar:~$ sudo /lib/udev/keymap input/event5 > orig-map.txt

... however when attempting to generate output with:

vanhoof@reptar:~$ sudo /lib/udev/keymap -i input/event5

... no events are registered at all when using Function+up, or
Function+down. Both Function+left/right (volume), and all the
directional keys work just fine:

vanhoof@reptar:~$ sudo /lib/udev/keymap -i input/event5
[sudo] password for vanhoof:
Press ESC to finish
scan code: 0xC8 key code: up
scan code: 0xD0 key code: down
scan code: 0xCB key code: left
scan code: 0xCD key code: right
scan code: 0xAE key code: volumedown
scan code: 0xB0 key code: volumeup
[...]
scan code: 0x01 key code: esc

I checked on Lenovo's site, and there are presently no BIOS updates
available for this laptop yet.

Just in-case it is needed, I'm attaching steps 4, and 5 here as well:

vanhoof@reptar:~$ head /sys/class/dmi/id/sys_vendor
LENOVO
vanhoof@reptar:~$ head /sys/class/dmi/id/product_name
3389

Could this just be a BIOS issue, or any other ideas?

--chris

It's also possible that those particular keys are attached to a different input device than the normal keyboard. Easiest is probably just to try input0, input1, and so on (until you get a "No such file or directory"), and check whether they appear on any of those.

Hi Martin -- In /dev/input/ I have event 0..9. I went through each using /lib/udev/keymap -i, and nothing was returned when using function+brightness.

Regards,
Chris

Thanks for checking. So this needs to be fixed in the kernel to make the events available at all. Reassigning.

same problem for me on lenovo G550 laptop. https://bugs.launchpad.net/ubuntu/+source/udev/+bug/530238

same with lenovo y410.. with lucid on it.

same with lenovo ideapad z350 on lucid

Same problem on a lenovo ideapad u460

Have opened a fresh bug for lenovo ideapad u460 ... https://bugs.launchpad.net/bugs/623065. That bug has been reassigned to the kernel instead of udev

I installed the 2.6.35-rc1-lucid kernel from http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.35-rc1-lucid/ and that seems to solve the problem. I checked for the keymap and scan code and the FN+Up/Down keys do not register any scan code but the event is registered as an acpi_event.

Is there anything I can do to narrow down the problem to a specific program / module etc?

Also can somebody check if what I have done resolves the problem on other Ideapad laptops?

Hi Dattatraya/Chris,

I just told that brightness key of ideapad works in Maverick. I test with the ideapad B550 and it looks like the brightness is changed by BIOS code, and ACPI backlight device get the notify and change the brightness.

What I dont understand is why it does not work in lucid.

Have another test on B550

# watch --interval=1 cat /sys/class/backlight/acpi_video0/brightness

The brightness level is from 0 to 10 and each time I press the brightness hotkey, it will in/decrease by 2.

I have the same issues on my ideapad s10-3.

any news on the topic?

thanks!

and in my case it does not work with maverick....

Chris Van Hoof, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the kernel in the daily folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested and remove the tag:
needs-upstream-testing

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 text:
needs-upstream-testing

If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested.

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

If you are unable to test the mainline kernel, please comment as to why specifically you were unable to test it and add the following tags:
kernel-unable-to-test-upstream
kernel-unable-to-test-upstream-VERSION-NUMBER

Please let us know your results. Thank you for your understanding.

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