Hi all!
I recently bought a R510 laptop, installed jaunty onto, and encoutered the same 
problem...
I had it finally working, perhaps not the properly way, but working...
Here's how I did:
at boot time, I add to attach keycodes to the brightness keys (adding fdi 
definitions in hal does not seem to work):
. /usr/share/acpi-support/key-constants
setkeycodes e009 $KEY_BRIGHTNESSDOWN
setkeycodes e008 $KEY_BRIGHTNESSUP
(tu put in bootmisc.sh or another script in /etc/init.d you then add to the 
runlevel scripts)

Then there is another problem, the same encoutered here: 
https://bugs.launchpad.net/ubuntu/+source/hal-info/+bug/295251 : the key 
release event is not sent...
So I patched the kernel, using same code as here: 
http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-jaunty.git;a=commit;h=b6edef2ac7b84ba90192ec1b8947949ebc99e99c
 , but I put DMI_MATCH(DMI_PRODUCT_NAME, "R510/P510") instead of 
DMI_MATCH(DMI_PRODUCT_NAME, "SQ45S70S")

I recompiled the kernel (using http://blog.avirtualhome.com/2009/04/29
/how-to-compile-a-kernel-for-ubuntu-jaunty/)

After that, the key works, but brightness does no adjust, it seeems there is a 
bug/missing feature in the nvidia driver.
After some googling, I tried smartdimmer (using nvclock should also work), and 
that one works. I wrote a little script (brightness.sh, see attachment), and 
then binded the brightness down/up keys to that script, using the gnome 
key-binding utility.

I currently do not have other key working yet (wifi on/off,
backlight...), I will try to have them working and keep you informed.

cheers,

-manu



** Attachment added: "brightness.sh"
   http://launchpadlibrarian.net/27271257/brightness.sh

-- 
brightness hardware control on Samsung R510 doesn't work
https://bugs.launchpad.net/bugs/297962
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to