Samsung r55/r65: Laptop keys don't funtion

I just upgraded to Edgy. Getting the same problem.

Same problem also on Sony Vaio VGN-FE21M. Work around is using smartdimmer by starting from console.

https://wiki.ubuntu.com/LaptopTestingTeam/HotkeyResearch has instructions on what details are needed.

I used all three methods from the document at:

https://wiki.ubuntu.com/LaptopTestingTeam/HotkeyResearch

I found that the following keys do not work but I was able to record their values using the methods above.

fn + F12 (Scroll Lock) = 0x46 0xc6
fn + j (num pad 1) = 0x4f 0xcf
fn + k (num pad 2) = 0x50 0xd0
fn + l (num pad 3) = 0x51 0xd1
fn + u (num pad 4) = 0x4b 0xcb
fn + i (num pad 5) = 0x4c 0xcc
fn + o (num pad 6) = 0x4d 0xcd
fn + 7 (num pad 7) = 0x47 0xc7
fn + 8 (num pad 8) = 0x48 0xc8
fn + 9 (num pad 9) = 0x49 0xc9
fn + m (num pad 0) = 0x52 0xd2

I found that when I tried to record the following keys below nothing would happen. I would press the key but nothing would be recorded (In all methods). Here is a list of the keys I could not record.

Keys I could not record using all the methods provided were:
fn+F2 (Show battery)
fn+F10 (Etiquette mode)
fn+up (Brightness up)
fn+down (Brightness down)

I then recorded the following keys:

Hex Number Recorded=Key Name=Decimal from Hex
0xe0 0x4b=Left Arrow push=75
0xe0 0xcb=Left Arrow release=203
0xe0 0x4d=Right Arrow push=77
0xe0 0xcd=Right Arrow release=205
0xe0 0x2e=fn+Left Arrow push=46
0xe0 0xae=fn+Left Arrow release=174
0xe0 0x30=fn+Right Arrow push=48
0xe0 0xb0=fn+Right Arrow release= 176
0xe0 0x50=Down Arrow push= 80
0xe0 0xd0=Down Arrow release= 208
0xe0 0x48=Up Arrow push= 72
0xe0 0xc8=Up Arrow release= 200

WARNING THIS IS A GUESS:
If all the fn+ keys are -29 should not the following be the correct hex values?

0xe0 0x33 = fn+down push
0xe0 0xe8 = fn+down release
0xe0 0x2b = fn+up push
0xe0 0xab = fn+up release

I got these values by converting the for example the Down Arrow Hex to Dec and then -29 then converting it back to Hex.

So the down push key
0x50 = 80
80-29 = 51
51 to hex = 0x33

Even if these were to be correct they are not even being detected!

Is there another way to detect keys?

Marking as confirmed based on availability of requested information.

I'm experiencing the same bug on a Samsung R65 (Specs: http://www.samsung.com/uk/products/mobilecomputing/dualcore/np_r65t000suk.asp)

Try putting the line "alias video off" in /etc/modprobe.d/local

If the file doesn't exist, create it. It solved the problem for me. No idea what it does though.

Putting in the line "alias video off" into "/etc/modprobe.d/local" does not work.

Its been confirmed by multiple people and there is nothing else I can give you to help fix this.

Changing this to confirmed until someone asks me anything else.

The bug seems to be fixed in Feisty, I'm using Herd 5+.

Do you have nvidia drivers enabled?

> Do you have nvidia drivers enabled?

Ah, no, sorry.
Actually, the brightness keys work with the nv driver, but not with nvidia.

The bug is fixed for me, Feisty final, using the nvidia driver.

Still broken in feisty final for me.

On Samsung R65 with Intel graphics:

Blacklisting the "video" mudule seems to make the brightness-keys work again. For example, create a file "/etc/modprobe.d/blacklist-custom" with the line "blacklist video".

I created the file "/etc/modprobe.d/blacklist-custom" and added the line but it doesn't do anything.

In addition I removed some other modules i don't need oon this machine (why di I need "asus_acpi" on a Samsung machine?, ...). The loaded modules can be seen with the "lsmod" command. I've attached my blacklist.

Maybe, this is helpful for someone.

I have tested and this doesn't fix my problem with the brightness keys while using the nvidia driver.

I have noticed that if I press ctrl+F1 I can control the brightness to a point but once I go back into gnome (ctrl+f7) I am not able to control the brightness settings.

The latest BIO update (DFCC) from Samsung seems to fix this bug so I am closing it.