Fn-F8 broken on Dell E6410

Bug #642715 reported by Vladimir Prus
22
This bug affects 4 people
Affects Status Importance Assigned to Milestone
udev (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Binary package hint: udev

Pressing Fn-F8 appears to produce symbol 'p' on Maverick beta. keymap -i reports two scan codes when Fn-F8 is pressed:
0xDB (leftmeta) and 0x19 (p). When I press Fn and hold it, no scancode is reported -- both scancodes are reported when F8 is later pressed with Fn still held. README.keymap.txt does not say how to fix such situation, so all I can do is report all data.

$ cat /sys/class/dmi/id/sys_vendor
Dell Inc.

$ cat /sys/class/dmi/id/product_name
Latitude E6410

Keymap and udev db will be attached.

Revision history for this message
Vladimir Prus (vladimir-prus) wrote :
Revision history for this message
Vladimir Prus (vladimir-prus) wrote :
Revision history for this message
Vladimir Prus (vladimir-prus) wrote :

Also, Fn+F2 (disable battery charge), Fn+F3 (battery), Fn+F7 (DCP) produce no scan codes at all. Here "disable battery charge" is supposed to make laptop stop charging a battery, and "DCP" on windows pops up some Dell utility. I suppose the latter makes no sense on Linux, while the former can be potentially useful. Also, Fn-F10 and Fn-F11 produce the same scancode 0xB7 -- while they should produce different ones for sysrq and printscreen respectively.

summary: - Fn-F8 borken on Dell E6410
+ Fn-F8 broken on Dell E6410
Revision history for this message
Vladimir Prus (vladimir-prus) wrote :

I've tried to enable low-level debugging with:

echo 1 > /sys/module/i8042/parameters/debug

What I get is this:

Nov 22 20:28:31 thunder kernel: [ 7063.583624] /build/buildd/linux-2.6.35/drivers/input/serio/i8042.c: e0 <- i8042 (interrupt, 0, 1) [1768702]
Nov 22 20:28:31 thunder kernel: [ 7063.583697] /build/buildd/linux-2.6.35/drivers/input/serio/i8042.c: 5b <- i8042 (interrupt, 0, 1) [1768702]
Nov 22 20:28:31 thunder kernel: [ 7063.583767] /build/buildd/linux-2.6.35/drivers/input/serio/i8042.c: 19 <- i8042 (interrupt, 0, 1) [1768702]

Nov 22 20:28:33 thunder kernel: [ 7065.812387] /build/buildd/linux-2.6.35/drivers/input/serio/i8042.c: 99 <- i8042 (interrupt, 0, 1) [1769260]

Nov 22 20:28:48 thunder kernel: [ 7080.289168] /build/buildd/linux-2.6.35/drivers/input/serio/i8042.c: e0 <- i8042 (interrupt, 0, 1) [1772885]
Nov 22 20:28:48 thunder kernel: [ 7080.291579] /build/buildd/linux-2.6.35/drivers/input/serio/i8042.c: db <- i8042 (interrupt, 0, 1) [1772886]

The first three lines is then I press F8 (there's nothing in response to pressing Fn), the following line ('99') is for depressing F8 and the last two lines is for depressing Fn.

However, I am still not sure how I make setkeycodes do anything useful with this, much less how to handle a 3-byte code reported above.

Revision history for this message
papukaija (papukaija) wrote :

This bug report is being marked as confirmed because it is affecting more than one person. 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.

Changed in udev (Ubuntu):
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.