Bug 607761 - RHEL6-Snapshot: Display toggle HotKeys Fn+F8 does not generate KEY_SWITCHVIDEOMODE
Summary: RHEL6-Snapshot: Display toggle HotKeys Fn+F8 does not generate KEY_SWITCHVIDE...
Status: CLOSED DUPLICATE of bug 595763
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: xorg-x11-drv-evdev
Version: 6.0
Hardware: All
OS: Linux
Target Milestone: rc
: 6.0
Assignee: Peter Hutterer
QA Contact: desktop-bugs@redhat.com
Keywords: Triaged
Depends On:
TreeView+ depends on / blocked
Reported: 2010-06-24 18:18 UTC by Issue Tracker
Modified: 2010-06-30 01:32 UTC (History)
2 users (show)

Clone Of:
Last Closed: 2010-06-30 01:32:11 UTC

Attachments (Terms of Use)

Description Issue Tracker 2010-06-24 18:18:00 UTC
Escalated to Bugzilla from IssueTracker

Comment 1 Issue Tracker 2010-06-24 18:18:03 UTC
Event posted on 06-22-2010 05:48pm EDT by Rezwanul_Kabir

Description of problem:

 Due to Win7 requirement of using Win+P key to switch display, all recent Dell platform BIOSen are generating the same scancodes for Fn+F8 as with Win+P. The problem is they are not mapped to the right keycode used in linux for display switching ( i.e. KEY_SWITCHVIDEOMODE).

  The scancodes for Fn+F8 and Win+P are as below:

     0xe0 0x5b 0x19    0x99 0xe0 0xdb
     [Key Press   ]    [ Key release]

   The Keycodes for Fn+F8 press and release are:

     125 press 25 press 25 release 125 release 
How reproducible:


Steps to Reproduce:

1. Install RHEL6 Snapshot6
2. Use "showkey -s" or "showkey -k" to verify

Actual results:

1. KEY_LEFTMETA + KEY_P are produced

Expected results:


Additional info:

This event sent from IssueTracker by dwa  [Dell-Engineering]
 issue 1051003

Comment 5 RHEL Product and Program Management 2010-06-24 18:32:59 UTC
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release.  Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release.  This request is not yet committed for

Comment 7 Peter Hutterer 2010-06-30 01:32:11 UTC
Marking as duplicate of 595763.

This bug needs to be addressed in the session, not in the X driver. We don't have any knowledge in the X driver of whether a device requires a quirk or not.

*** This bug has been marked as a duplicate of bug 595763 ***

Note You need to log in before you can comment on or make changes to this bug.