Brightness fn keys lost functionality (Lenovo laptops)

[Oybon]

Binary package hint: devicekit

Worked fine in 9.04 & previous.

Brightness keys only have failed; all other fn keys still function as intended.

Brightness gnome-panel applet works, but occasionally reports it can't recover data when it can. (not seen since Karmic-RC)

Via KeyboardShortcuts debug process there is no determinable response from the brightness keys at all. All other fn keys give expected output.

System is a: Lenovo 3000 N200 (0769EUG)

ProblemType: Bug
Architecture: i386
Date: Wed Jul 29 18:43:32 2009
DistroRelease: Ubuntu 9.10
Package: devicekit 003-1
ProcEnviron:
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-4.23-generic
SourcePackage: devicekit
Uname: Linux 2.6.31-4-generic i686

[Ofir Klinger (klinger-ofir)]

I also lost brightness key.

It is frustrating since the screen sometimes is very dark that I can barely see it.

[Oybon (oybon)]

Ahh, now the right package, my mistake

[Oybon (oybon)]

Also noticed system not mentioned properly, must have been an off day when I reported this,

Lenovo 3000 N200 (0769EUG)

[Ofir Klinger (klinger-ofir)]

This bug is not related to gnome-power-manager, since I use KDE4 and I have the same problem.

[Oybon (oybon)]

Ok

Have tried the test regime on

https://wiki.ubuntu.com/Hotkeys/Troubleshooting

An can't find a way of registering any key-press for brightness up / down. Thus by 6.b. it is probably kernel.

[Oybon (oybon)]

Checked again with Alpha 5, no change

[spaetz (spaetz)]

Same problem on a Apple MacBook 4,1. Brightness keys used to work like a charme in Jaunty. Tested Karmic alpha and brightness keys don`t work anymore. Colume changes still work, so the special keys did not totally stop working.

[Don Owen (donald.e.owen)]

Same symptoms on an HP dv6565us. Most of the other fn (function) keys work like they're supposed to, but not brightness control. (Fn + F7/F8) Running most up to date kernel - 2.6.31rc9

Linux grayhat 2.6.31-9-generic #29-Ubuntu SMP Sun Aug 30 17:39:26 UTC 2009 x86_64 GNU/Linux

[Andy Whitcroft (apw)]

@spaetz, @donald -- the original reported found they had no key presses at all generated, could you go thorugh the same debug exercise and see if that is the same for you. See the guide below for details:

    https://wiki.ubuntu.com/Hotkeys/Troubleshooting

Note that if you find the same that no keys are generated at all, then it is very likely an issue which is specific to the make and model of your machine and if it is a different machine would need a separate bug.

[Andy Whitcroft (apw)]

@Oybon -- can you try the latest mainline kernel (2.6.31-rc9) build for us and confirm that the issue is also present there. That kernel can be found at the URL below:

    https://wiki.ubuntu.com/KernelTeam/MainlineBuilds

[Oybon (oybon)]

@ Andy Whitcroft

Tried mainline kernel, exactly same behaviour with all troubleshooting tests.

[spaetz (spaetz)]

Will also try mainline kernel soon. As for keypresses they are magic to me anyway:

capturing keypresses with xev, I get keypresses (including key codes) for some special keys, but not for the brightness ones. On the other hand, I also don't see anything thorugh xev when using the volume keys, but the volume is being changed correctly (OSD volume level changes).

[Oybon (oybon)]

And still continues with -10 kernel

[Spohl (bernfresse)]

The same for me, Lenovo 3000 V200

[Oybon (oybon)]

And -11

[Stefan Bader (smb)]

Could you test this with the -12 kernel and when that still fails, please add the output of "grep -r . /proc/acpi/video" to this bug report as well as the dmesg output of the boot. Thanks.

[Oybon (oybon)]

With -12

running through the standard tests

xev with the recommended sed setting still reports nothing, though equally dosn't for other fn keys that do work. The working fn keys do show up with just xev though.

keymap = nothing

acpi_listen = nothing

[Oybon (oybon)]

and dmesg

[spaetz (spaetz)]

Macbook 4,1 here. Brightness keys still don't work, while e.g. Volume keys do work. Using xev, I get KeymapNotify events pressing Brightness keys, but don't get KeyPress/KeyRelease events (neither with the Volume keys).

Linux spaetz-macbook 2.6.31-12-generic #40-Ubuntu SMP Wed Oct 7 04:13:44 UTC 2009 x86_64 GNU/Linux
------------------------------------------------------------------
grep -r . /proc/acpi/video:

/proc/acpi/video/GFX0/TV/EDID:<not supported>
/proc/acpi/video/GFX0/TV/brightness:<not supported>
/proc/acpi/video/GFX0/TV/state:state: 0x1d
/proc/acpi/video/GFX0/TV/state:query: 0x00
/proc/acpi/video/GFX0/TV/info:device_id: 0x0200
/proc/acpi/video/GFX0/TV/info:type: TVOUT
/proc/acpi/video/GFX0/TV/info:known by bios: yes
/proc/acpi/video/GFX0/VGA/EDID:<not supported>
/proc/acpi/video/GFX0/VGA/brightness:<not supported>
/proc/acpi/video/GFX0/VGA/state:state: 0x1d
/proc/acpi/video/GFX0/VGA/state:query: 0x00
/proc/acpi/video/GFX0/VGA/info:device_id: 0x0300
/proc/acpi/video/GFX0/VGA/info:type: DVI
/proc/acpi/video/GFX0/VGA/info:known by bios: yes
/proc/acpi/video/GFX0/LCD/EDID:<not supported>
/proc/acpi/video/GFX0/LCD/brightness:<not supported>
/proc/acpi/video/GFX0/LCD/state:state: 0x1f
/proc/acpi/video/GFX0/LCD/state:query: 0x01
/proc/acpi/video/GFX0/LCD/info:device_id: 0x0400
/proc/acpi/video/GFX0/LCD/info:type: LCD
/proc/acpi/video/GFX0/LCD/info:known by bios: yes
/proc/acpi/video/GFX0/DOS:DOS setting: <7>
/proc/acpi/video/GFX0/POST:<not supported>
/proc/acpi/video/GFX0/POST_info:<not supported>
/proc/acpi/video/GFX0/ROM:<TODO>
/proc/acpi/video/GFX0/info:Switching heads: yes
/proc/acpi/video/GFX0/info:Video ROM: no
/proc/acpi/video/GFX0/info:Device to be POSTed on boot: no

[Biji (biji)]

confirmed on Lenovo G410
changing brighness from power manager worked nicely... only the Fn+BRIGHTDOWN and UP not working

[Oybon (oybon)]

Still not working with -13 and -14

[Delvien (dstubbs28)]

HP dv1000se laptop
2.6.31-14-generic

This is the same problem I have. Every other fn key works, but not the brightness up and down.

[Delvien (dstubbs28)]

More to add.. When going through the "fixing hotkeys" guide.

I ran: sudo /lib/udev/keymap -i input/event5

I then proceeded to hit all the fn keys and its respective hotkeys, F1 F2 F3 ... etc. When I got to the brightness keys (F7, and F8) neither were recognized. It seems there is an issue with the kernel not picking up the FN combos for these two keys.

[D3xter (andreas-sinz)]

Same here on a Lenovo 3000 N500.

I get the same behaviour on Gentoo with 2.6.30-r5

[Pieter Ennes (skion)]

Count me in with -14 on karmic on a MacBook 2.1

[Josh Hill (ingenium)]

Works for me on a Thinkpad T400 on karmic. Upgraded from jaunty last night. When I installed jaunty, I followed these directions, so maybe something I did there is making it work now (specifically the kernel boot option to enable the mute key): http://www.thinkwiki.org/wiki/Install_Ubuntu_9.04_(Jaunty_Jackalope)_on_a_ThinkPad_T400

[Oybon (oybon)]

Ok, still there, and I can confirm it on a 3000 N500 I upgraded over the weekend. So I have two systems with the same problem now.

Looks like it will be there in release. Oh well.

As a side note, the brightness applet in the task bar works, but is, to put it simply, awful. Where the brightness ends up bares no resemblance to what actions you intend and brightness has to be set through an iterative click and see approach with a significant click-action delay.

[Neil Woolford (neil-neilwoolford)]

Yes, still no brightness function keys here on my Lenovo 3000 N200.

I agree with Oybon about the performance of the brightness applet; I would suggest using the gnome-power-manager (battery icon on the upper task bar) as it has a better brightness control on the Preferences AC Power tab. Hope this helps others...

[Michael%S (msappir)]

Same problem on Dell Mini 12 (with lpia variant.) See discussion here: http://ubuntuforums.org/showthread.php?t=1294173

[Tadeu Bastos (tmcb)]

Also happenning in a Lenovo Ideapad Y430.

Ubuntu version is 9.10 for AMD64 and kernel is 2.6.31-14-generic.

[Akagi (akagi010)]

I can confirm this problem for Samsung NC10 also.

Also the brightness applet does not work.

[Oybon (oybon)]

NC10 is a different error. It can be fixed by upgrading the system bios.

If you go through the testing scheme suggested above you see that the NC10 is still registering the key presses.

[Oybon (oybon)]

On that, have the non-lenovo users gone through the full checking system at

https://wiki.ubuntu.com/Hotkeys/Troubleshooting

[Przemysław Kochański (kochas315)]

There is no keypress event, exercise the "Fixing broken keys":

== Fixing broken keys ==

In order to make a broken key work on your system and send it back to upstream
for inclusion you need to do the following steps:

 1. Find the keyboard device.

 Run /lib/udev/findkeyboards. This should always give you an "AT
 keyboard" and possibly a "module". Some laptops (notably Thinkpads, Sonys, and
 Acers) have multimedia/function keys on a separate input device instead of the
 primary keyboard. The keyboard device should have a name like "input/event3".
 In the following commands, the name will be written as "input/eventX".

 2. Dump current mapping:

 sudo /lib/udev/keymap input/eventX > /tmp/orig-map.txt

 3. Find broken scan codes:

 sudo /lib/udev/keymap -i input/eventX

 Press all multimedia/function keys and check if the key name that gets printed
 out is plausible. If it is unknown or wrong, write down the scan code (looks
 like "0x1E") and the intended functionality of this key. Look in
 /usr/include/linux/input.h for an available KEY_XXXXX constant which most
 closely approximates this functionality and write it down as the new key code.

 For example, you might press a key labeled "web browser" which currently
 produces "unknown". Note down this:

   0x1E www # Fn+F2 web browser

 Repeat that for all other keys. Write the resulting list into a file. Look at
 /lib/udev/keymaps/ for existing key map files and make sure that you use the
 same structure.

 4. Find out your system vendor and product:

 cat /sys/class/dmi/id/sys_vendor
 cat /sys/class/dmi/id/product_name

 5. Generate a device dump with "udevadm info --export-db > /tmp/udev-db.txt".

 6. Send the system vendor/product names, the key mapping from step 3,
 /tmp/orig-map.txt from step 2, and /tmp/udev-db.txt from step 5
 to the bug tracker, so that they can be included in the next release:

   https://bugs.launchpad.net/udev-extras/+bugs

For local testing, copy your map file to /lib/udev/keymaps/ with an appropriate
name, and add an appropriate udev rule to /lib/udev/rules.d/95-keymap.rules:

  * If you selected an "AT keyboard", add the rule to the section after
  'LABEL="keyboard_vendorcheck"'.

  * If you selected a "module", add the rule to the top section where the
  "ThinkPad Extra Buttons" are.

[Andreas Korth (andreaskorth)]

I've tried the hints of Przemysław Kochański with Lenovo 3000 N200 (Product-Name: 0769AC6).

Concerning paragraph 3: the outputs of all Fn-Keys (excepting the brightness-Keys) are plausible and OK. The Brightness-Keys doesn't generate any feedback, not even an "unknown" or something.

Should i collect the other informations for sending them to the bug tracker anyway?
There would be no "resulting keymap" because all other things are working correctly.

[Cruxic (cruxic)]

Workaround: If you have Intel graphics you should be able to use the "xbacklight" command. Should also work with the open-source nvidia drivers as well. (src: https://wiki.ubuntu.com/Halsectomy)

BTW: I too get nothing with kemap -i for the two brightness keys on my Lenovo G530. Other Fn keys output known codes.

[Tadeu Bastos (tmcb)]

I don't know if this information helps, but here in my Lenovo Y430 the keys work fine until just a bit after GDM starts. Maybe it's a module or daemon loaded by Upstart. I think it's worth to check it.

[Luther (lty)]

Same problem with HP Pavillion dv2000; ran all the listed troubleshooting and there are no key events generated for the brightness keys (as seen by either keymap or acpi_listen); brightness function itself (via applet or xbacklight) work fine.

[Ualpa (superualpa)]

Same problem on Dell Studio 15 (1537), but the brightness keys did not work properly in 9.04 either, though I noticed that if you tried to adjust brightness before logging in, then they worked.

[Andreas Korth (andreaskorth)]

On Lenovo 3000 N200, I have to revoke the experiences of Ualpa and mientefuego, that the brightness-keys would work until (or short after) loading GDM.
In my case, the brightness-keys stop working immediately when passing grub2 in the boot-process.

[Neil Woolford (neil-neilwoolford)]

I've just tried the brightness function keys on my 3000 N200, and they do still work while the grub menu is on screen, but stop working as soon as the grub menu countdown finishes and grub starts work.

As others have found, the function keys F10 and F11 produce a normal keycode by themselves, but nothing at all if used with the Fn key to try to generate the brightness keycodes. Other Fn and key combinations all appear to work fine.

[Ualpa (superualpa)]

Last night the brightness keys worked correctly on my Dell Studio 15, quite weird because I think no update was installed and no particular actions were made before logging in... I'll try to check if the bluetooth/wifi switch may somehow influence the behaviour of the brightness keys, even if the two things shouldn't be related.

[Przemysław Kochański (kochas315)]

More and more laptops are reported as affected. My friends reported the same issue on their's Dell Studio 1555. It's Ubuntu upstream!

[Nelson Álvarez Sáez (alvareznelson)]

Same problem on Acer Aspire 5738. And brightness adjustment didn't work on Jaunty, either.

Besides, the screen never seems to reach its full brightness and it flickers sometimes.

[kennymchansen (kennymchansen)]

I have the same problem on my lenovo 3000 v200. I think perhaps it has something to do with KMS?

Before upgrading to Karmic I tried installing the latest kernel and enabling KMS in Jaunty, and then i had the same problem. When i disabled KMS, i could use the fn keys again just fine.

I hope this helps in fixing the problem somehow.

[zimbardo (mail-zimbardo)]

I have the problem too with a Lenovo 3000 N200 with an Intel graphic. I have upgraded from 9.04 to 9.10.
When I boot the old .28-16 Kernel, the two keys worked perfecty.

[Vish (vish)]

Thank you for bringing this bug to our attention. However, a paper cut should be a small usability issue, in the default Ubuntu 9.10 install, that affects many people and is quick and easy to fix. So this bug can't be addressed as part of this project.

- This is a bug , and not a design flaw, Hence not a papercut.
For further information about papercuts criteria, please read https://wiki.ubuntu.com/PaperCut.

Don't worry though, this bug has been marked as "Invalid" only in the papercuts project. The is still active in the other projects.

[bkainz (bernhard-kainz-gmail)]

Hi,

I can confirm the same problem on my DELL Studio 1555 notebook, but after installing the current mainline kernel (2.6.32-020632rc7-generic - https://wiki.ubuntu.com/KernelTeam/MainlineBuilds) all FN keys now are working fine.

bye
bernhard

[Gergely Csépány (cheoppy)]

I'm also affected on a Lenovo Ideapad Y450. The brightness keys doesn't show in the xev output, but they do show up the acpi_listen's output:

brightness up:
video DD03 00000086 00000000
brighness down:
video DD03 00000087 00000000

How can I set these keys to work thru acpi?

[Gergely Csépány (cheoppy)]

I found a workaround here: http://bbs.archlinux.org/viewtopic.php?id=73889

I can change the brightness with setpci -s 00:02.0 F4.B=FF where FF is a brightest mode and 00:02.0 is from lspci | grep VGA.

Now I can set the brightness using setpci, how can I make acpi to use this command?

[Micah Cowan (micahcowan)]

Same issue on a Compaq CQ60. Only missing the brightness keys, no others; were working fine in Jaunty. No messages from xev or acpi_listen.

[Michael Lustfield (michaellustfield)]

This is the output I got from screen brightness down:
KeyPress event, serial 35, synthetic NO, window 0x1e00001,
    root 0x110, subw 0x0, time 12140504, (289,478), root:(358,796),
    state 0x0, keycode 232 (keysym 0x1008ff03, XF86MonBrightnessDown), same_screen YES,
    XLookupString gives 0 bytes:
    XmbLookupString gives 0 bytes:
    XFilterEvent returns: False

This is the output I got from screen brightness down:
KeyPress event, serial 37, synthetic NO, window 0x1e00001,
    root 0x110, subw 0x0, time 12142853, (289,478), root:(358,796),
    state 0x0, keycode 233 (keysym 0x1008ff02, XF86MonBrightnessUp), same_screen YES,
    XLookupString gives 0 bytes:
    XmbLookupString gives 0 bytes:
    XFilterEvent returns: False

Obviously that's only key down, not up.

The setpci command works for me to change brightness. However, the keys do not change the brightness. I'm also not running gnome-power-manager so I wouldn't expect this to work.

I was running 9.04 this morning and xev wasn't showing any output for the keys. However, I upgraded to 10.04 and the issue seems to have gone away.

Could somebody else try with the daily live cd?
Linux panther 2.6.32-9-generic #13-Ubuntu SMP Thu Dec 17 17:01:59 UTC 2009 x86_64 GNU/Linux

[spaetz (spaetz)]

Is this the same as bug 397617? brightness keys only don't wrk with KMS enabled. Disabling KMS using the "nomodeset" kernel parameter on boot my brightness keys work fine.

[David Tombs (dgtombs)]

Invalidating upstream kernel task, at least until the issue is ready to be reported upstream.

[David Tombs (dgtombs)]

Invalidating upstream g-p-m task as we're not sure the issue is actually with g-p-m.

[David Tombs (dgtombs)]

Invalidating g-p-m package assignment as Andy seems to think this is in the kernel. Przemysław, please be more conservative with bug status modifications.

[spaetz (spaetz)]

Sorry for the noise, but are you sure this is an upstream kernel issue? Comment #52 says the keys work fine with the mainline kernels 2.6.32. So either this is ubuntu kernel-specific or it has been solved upstream already (in which case ubuntu would need to backport a fix or upgrade the kernel (improbble)). In either case, this would not be an invalid bug report.

[spaetz (spaetz)]

Oooh, ahh. Ignore my previous comment #61. I see that you only changed the upstream linux aspect as invalid, and not the whole bug. I am fine with that change, of course. Sorry for even more noise.

[Paul Dufresne (paulduf)]

From bug #503577, on a Dell mini 10, 'apci_backlight=vendor' kernel parameter seems to make it work.
"acpi_backlight= [HW,ACPI]
acpi_backlight=vendor
acpi_backlight=video
If set to vendor, prefer vendor specific driver
(e.g. thinkpad_acpi, sony_acpi, etc.) instead
of the ACPI video.ko driver."

[David Tombs (dgtombs)]

I've updated the title and description to reflect that this report is for Lenovo laptops only. People with other brands should file separate bug reports, please. Thank you!

[spaetz (spaetz)]

mmh, not overly happy to have this bug "hijacked" to be only about Lenovo after 6 months (granted that the initial report is about a Lenovo though :-) ). I have filed bug 509508 for my MacBook4,1 which has exactly the same issue still. I do think that these 2 bugs are closely related though.

[David Tombs (dgtombs)]

Hi spaetz, sorry about the "hijacking," but I have been trying to take action on this apparently-stalled bug and just realized that it had actually originally been hijacked from being a Lenovo-specific bug. It's quite possible your bug and this one are related, but until that can be confirmed it's much more useful to developers to have different bug reports. (And the vague title was bringing in people who I'm sure don't have the same exact issue.)

Sorry for the inconvenience, but I think it's worth it!

[Oybon (oybon)]

Have just tried Lucid Alpha-2 live DVD. Still not working.

I know it needs an install for the full `troubleshoot' but I did the keypress test (xev | sed etc...) and got no response from the keys. Though I also got no response from volume Up / Down and they appear to be working perfectly.

Brightness applet as ever seems to work.

[Trent Telfer (unnaturalhigh)]

For Toshiba laptops I filed a bug under https://bugs.launchpad.net/ubuntu/+source/linux/+bug/514477

[Trent Telfer (unnaturalhigh)]

Kernel bugs that may be of interest to affected users here:

http://bugzilla.kernel.org/show_bug.cgi?id=14506
http://bugzilla.kernel.org/show_bug.cgi?id=15054
http://bugzilla.kernel.org/show_bug.cgi?id=15162

[Oybon (oybon)]

No on install of Lucid Beta 1, problem still exists.

[raido357 (raido357)]

Count me in too - Clevo W83T.

Booting with "acpi=off" makes FN brightness keys work but ofcource everything acpi like is killed.

Anyone who has problem, please try "acpi=off".

[Reece (reece)]

Still exists on MacBook Pro 5,3 with Lucid Beta 1.

[Przemysław Kochański (kochas315)]

@Paul Dufresne: acpi_backlight=vendor | acpi_backlight=video don't bring any difference.

@raido357: acpi=off works on Lucid beta 1! Thanks. If I remember correct, it didn't on Karmic!

My FN brightness keys works now under Lenovo N200 after adding "acpi=off" to "GRUB_CMDLINE_LINUX_DEFAULT=" line in "/etc/default/grub". Please try it on your laptops under Lucid Beta.

[Tomek Bury (tomek-bury)]

HP Pavilion dv2500 shows the same issue. The "acpi=off" brings FN+F7/F8 back to life but at the cost of WiFi. I can be a hint but it's not good enough even as a workaround, as far as I'm concerned.

[scottuss (scottuss)]

I have this problem on my Samsung R730, Lucid Release Candidate

[aquasync (aquasync)]

Confirmed with my Lenovo G530.

Without any changes to boot params, the brightness keys work until
gdm, (eg ok during plymouth) and also in single user mode. No acpi
events are generated though.

Using acpi=off works also (no events generated, handled by bios
I suppose), but is useless as it kills suspend, battery status
and other important things.

For me, acpi_backlight=video and =vendor both had no effect.

Trying nomodeset was successful. Plymouth looked ugly, but it
booted ok, brightness keys work and generate osd notify bubbles,
and acpi_listen shows appropriate events:

# Down
video DD03 00000087 00000000
# Up
video DD03 00000086 00000000

I'll try and build a kernel with the patch from https://bugzilla.kernel.org/show_bug.cgi?id=15054, and see if works with kms.

[Prakash (e-prakashs)]

Even the same issue with lenovo y410 with 10.04, brightness keys are not getting captured in any input/eventX
All other features work fine. including automatic brightness control.

There is a crazy issue with this laptop.

brightness value varies from 0 - 5 and 5 - 10 where 5 being the least and 0 or 10 being the heighest. to calrify more, if I use the brightness applet, the brightness is least when the slider is in the middle and increases on either side. I found max_brightness option but there is no min_brightness If at all I need to put 5 there :-)

[Prakash (e-prakashs)]

I updated the kernel to 2.6.34-020634rc6-generic and the voila, the function keys to change brightness works fine.

Issue with 5 being the least brightness is not yet resolved. Let me know if there is any workaround.
When the system is on battery, the brightness reduced automatically to half (5) which is least for me, and when I become idle the brightness is reduced to (0) which is highest for me (problem)

Thanks for 2.6.34-020634rc6-generic work

[aquasync (aquasync)]

Thanks for the tip Prakash - I can also confirm the brightness keys now work on my Lenovo G530 with kms enabled using 2.6.34-020634rc6-generic from kernel-ppa. It incorporates the previously mentioned patch from the kernel bugzilla:

Zhang Rui (1):
      drm/i915: set DIDL using the ACPI video output device _ADR method return.

[Przemysław Kochański (kochas315)]

I've tested the 2.6.34-rc6 kernel and it fixes the issue completely!!! Thanks!!!
You can easily download and install it from http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.34-rc6-lucid/

[Gergely Csépány (cheoppy)]

I wouldn't say that a fix is released, since it's only a workaround using an unsupported release candidate kernel. I think a real fix would be to have this fix backported to official lucid (and maybe karmic) kernels, but until that it's a working *temporary* solution. :)

[Przemysław Kochański (kochas315)]

Yes, you're right, it's not official and supported yet, just fixed.

[Lake Denman (lake-lakedenman)]

I tested the 2.6.34-rc6 kernel as well, and it fixes the issue on my Lenovo G550.

[David Tombs (dgtombs)]

Actually, Confirmed is more appropriate here because Fix Committed implies that the release is in -proposed. Thanks for testing the mainline build, though, that will help speed things along.

[bhuvi (bhuvanesh)]

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

[Oybon (oybon)]

Well, just installed Maverick Alpha 3 and it appears to be working again. Wooo. Will see how it goes for the beta

[Darwin Bautista (baudm)]

This bug has been fixed upstream since 2.6.34-rc6 by this commit:
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=3143751ff51a163b77f7efd389043e038f3e008e

I've rebuilt the i915 module in 2.6.32 with the patch above and the brightness keys are working again as expected. I've been using this for almost a month already, no hiccups or whatsoever. That being said, I hope that the Ubuntu kernel devs will backport the fix, which has been available for about FOUR months now, as soon as possible. This bug is really annoying but can be readily fixed. Thanks.

[David Tombs (dgtombs)]

Upstream bug is <https://bugzilla.kernel.org/show_bug.cgi?id=15054> per last comment.

[Hans-Dominik (hdm-mail)]

with linux-image-2.6.35-020635rc1-generic_2.6.35-020635rc1_i386 brightness buttons works good as reported in Bug #579967.

but with new Maveric Beta Buttons lost theire increas funktion again, just a short bright flash of the screnn after pressing Increas buton, but then brightnes falls back to lowest value

[David Tombs (dgtombs)]

Any other reports on Maverick release?

[Lapaj (lapaj)]

Working on Maverick here (Lenovo 3000 N500)

On Sun, Oct 31, 2010 at 19:11, David Tombs <email address hidden> wrote:

> Any other reports on Maverick release?
>
> --
> Brightness fn keys lost functionality (Lenovo laptops)
> https://bugs.launchpad.net/bugs/406515
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in Gnome Powermanager: Invalid
> Status in One Hundred Paper Cuts: Invalid
> Status in The Linux Kernel: Unknown
> Status in NULL Project: Invalid
> Status in “gnome-power-manager” package in Ubuntu: Invalid
> Status in “linux” package in Ubuntu: Triaged
>
> Bug description:
> Binary package hint: devicekit
>
> Worked fine in 9.04 & previous.
>
> Brightness keys only have failed; all other fn keys still function as
> intended.
>
> Brightness gnome-panel applet works, but occasionally reports it can't
> recover data when it can. (not seen since Karmic-RC)
>
> Via KeyboardShortcuts debug process there is no determinable response from
> the brightness keys at all. All other fn keys give expected output.
>
> System is a: Lenovo 3000 N200 (0769EUG)
>
> ProblemType: Bug
> Architecture: i386
> Date: Wed Jul 29 18:43:32 2009
> DistroRelease: Ubuntu 9.10
> Package: devicekit 003-1
> ProcEnviron:
> LANG=en_GB.UTF-8
> SHELL=/bin/bash
> ProcVersionSignature: Ubuntu 2.6.31-4.23-generic
> SourcePackage: devicekit
> Uname: Linux 2.6.31-4-generic i686
>
>
>
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/gnome-power/+bug/406515/+subscribe
>

[Andreas Korth (andreaskorth)]

I've only tested it with 10.10 64Bit Live-DVD on Lenovo 3000 N200. The Fn-Keys are working now but every key-press the brightness increases/decreases by two steps. You can see the first step of increase/decrease but shortly after (about 0.5 sec), it makes a second step.

[David Tombs (dgtombs)]

OK, based on your responses I'm going to mark this as fixed. Thanks!

If you continue to have problems with unexpected behavior, that is a separate issue, so please file a different bug report.