Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.

Bug 454131

Summary: DELL Inspiron 1501 unknown key pressed errors in kernel log
Product: [Fedora] Fedora Reporter: Eugene Savelov <savelov>
Component: kernelAssignee: Kernel Maintainer List <kernel-maint>
Status: CLOSED NOTABUG QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 9   
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2008-12-18 18:45:06 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Eugene Savelov 2008-07-05 05:52:19 UTC
Description of problem:

errors in kernel log on DELL Inspiron 1501

Jul  5 09:41:29 localhost kernel: atkbd.c: Unknown key pressed (translated set
2, code 0x8d on isa0060/serio0).
Jul  5 09:41:29 localhost kernel: atkbd.c: Use 'setkeycodes e00d <keycode>' to
make it known.


Version-Release number of selected component (if applicable):

kernel-2.6.25.6-55.fc9.x86_64

How reproducible:

always

Steps to Reproduce:
1. start linux on dell inspiron 1501
2.  check dmesg
3.
  
Actual results:
kernel log is full of messages

Expected results:
no errors

Additional info:
workaround is to set the scancode to some value, but if set then key auto-repeat
does not work correctly 

/usr/bin/setkeycodes e00d 141

Comment 1 Eugene Savelov 2008-12-18 18:45:06 UTC
hardware issue on dell inspiron 1501.
fixed by removing and inserting it back
probably was related to BIOS upgrade

Comment 2 Eugene Savelov 2008-12-18 18:49:20 UTC
fixed by removing battery and inserting it back