Bug 434538
| Summary: | sr #1768018 : numlock led does not reflect the status of numlock | ||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 5 | Reporter: | Alan Matsuoka <alanm> | ||||||||||||||||
| Component: | kernel | Assignee: | Mauro Carvalho Chehab <mchehab> | ||||||||||||||||
| Status: | CLOSED ERRATA | QA Contact: | Martin Jenner <mjenner> | ||||||||||||||||
| Severity: | high | Docs Contact: | |||||||||||||||||
| Priority: | medium | ||||||||||||||||||
| Version: | 5.1 | CC: | arozansk, ctatman, cward, dmair, dzickus, gerrit.slomma, jfeeney, lwang, mgahagan, syeghiay, tao, wwlinuxengineering, xgl-maint | ||||||||||||||||
| Target Milestone: | rc | Keywords: | OtherQA | ||||||||||||||||
| Target Release: | --- | ||||||||||||||||||
| Hardware: | All | ||||||||||||||||||
| OS: | Linux | ||||||||||||||||||
| Whiteboard: | |||||||||||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||||||||||
| Doc Text: | Story Points: | --- | |||||||||||||||||
| Clone Of: | Environment: | ||||||||||||||||||
| Last Closed: | 2009-01-20 20:16:24 UTC | Type: | --- | ||||||||||||||||
| Regression: | --- | Mount Type: | --- | ||||||||||||||||
| Documentation: | --- | CRM: | |||||||||||||||||
| Verified Versions: | Category: | --- | |||||||||||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||||||||||
| Embargoed: | |||||||||||||||||||
| Bug Depends On: | |||||||||||||||||||
| Bug Blocks: | 391501, 471469 | ||||||||||||||||||
| Attachments: |
|
||||||||||||||||||
|
Description
Alan Matsuoka
2008-02-22 16:34:33 UTC
Created attachment 295652 [details]
sosreport
Created attachment 295996 [details]
xorg.conf from sosreport
Created attachment 295997 [details]
Xorg.0.log from sosreport
Created attachment 295998 [details]
dmidecode from sosreport
The numlock led status issue occurs when system is booted to X GUI(init 5) or and console mode(init 3, tty1~tty6). This event sent from IssueTracker by rkhadgar issue 143833 Created attachment 314084 [details]
Patch for fixing the Keyboard LED
Some keyboards need a quirk to reset leds.
Could you please try the enclosed patch?
It adds a quirk for the DELL keyboard described on your sosreport, and backports another quirk for a Logitech keyboard (not sure if the quirk is for the same model you tested, since you didn't provide the usb id).
While on this, I also added the quirk for one USB "generic" keyboard I have here with the same bug.
If it doesn't work for your Logitech keyboard, please send us its USB ID. Also, provide us the USB ID for the SUN keyboard you've also detected this issue.
In an effort to make progress on this bugzilla, I applied the patch as found in comment #12 and built rpms so the patch could be tested. Those rpms can be found on my people page (http://people.redhat.com/jfeeney/.bz434538). Ok, I got one DELL keyboard with the same USB ID. Tested it and the patch worked fine.
I'm now submitting the upstream patch:
http://lkml.org/lkml/2008/10/9/342
After upstream addition, I'll submit it to RHEL 5 kernel.
Created attachment 320479 [details]
Patch for fixing Keyboard NUM LOCK LED version 2
The patches adding support for Bright (Belkin?) and Dell keyboards are already upstream:
commit a48c65b35a6f993aec13d18a37f6ea71fbcb0c06
commit 0dc491682f6e673a14c643d9a3e7305ce4616b96
While here, I've backported support also for Logitech keyboard:
commit 3c5f4b25f3552c9bcb52eb956753a3c8140480b7
Due to a small namespace conflict, this patch renamed two names at the #define's
The latest kernel with those patches applied is available at: http://new-people.redhat.com/~mchehab/.bz434538/ Please test. in kernel-2.6.18-123.el5 You can download this test kernel from http://people.redhat.com/dzickus/el5 Created attachment 323397 [details] Patch for fixing Keyboard NUM LOCK LED version 3 Ok, I've added the new DELL USB ID (0x2003) at the attached patch. I've already made x86_64 kernel available at: http://new-people.redhat.com/~mchehab/.bz434538/ I'll add i686 later today after finishing the build. Please test. Please retest at next snapshot to verify the patch is correctly included and functions as expected. Thanks! Feel free to add the PartnerVerified keyword and move the bug status to VERIFIED after this is complete. ~~ Snapshot 3 is now available ~~ Snapshot 3 is now available for Partner Testing, which should contain a fix that resolves this bug. ISO's available as usual at ftp://partners.redhat.com. Your testing feedback is vital! Please let us know if you encounter any NEW issues (file a new bug) or if you have VERIFIED the fix is present and functioning as expected (add PartnerVerified Keyword). Ping your Partner Manager with any additional questions. Thanks! ~~ Attention ~~ Snapshot 4 is now available for testing @ partners.redhat.com ~~ Partners, it is vital that we get your testing feedback on this important bug fix / feature request. If you are unable to test, please clearly indicate this in a comment to this bug or directly with your partner manager. If we do not receive your test feedback, this bug is at risk from being dropped from the release. If you have VERIFIED the fix, please add PartnerVerified to the Bugzilla Keywords field, along with a description of the test results. If you encounter a new bug, CLONE this bug and request from your Partner manager to review. We are no longer excepting new bugs into the release, bar critical regressions. ~~ Snapshot 5 is now available @ partners.redhat.com ~~ Partners, RHEL 5.3 Snapshot 5 is now available for testing. Please send us your testing feedback on this important bug fix / feature request AS SOON AS POSSIBLE. If you are unable to test, indicate this in a comment or escalate to your Partner Manager. If we do not receive your test feedback, this bug will be AT RISK of being dropped from the release. If you have VERIFIED the fix, please add PartnerVerified to the Bugzilla Keywords field, along with a description of the test results. If you encounter a new bug, CLONE this bug and request from your Partner manager to review. We are no longer excepting new bugs into the release, bar critical regressions. From the comments posted in Issue Tracker# 172433 this issue is fixed in RHEL5.3-Snapshot5. An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHSA-2009-0225.html I have the same problem with a Microsoft Natural Keyboard (the original one with the extensible foot on the front) with PS/2-connector and with a Microsoft Comfort Curve Keyboard (USB) as well as with a IBM Prefered Black Keyboard (USB). Kernels are for: 1. 2.6.18-128.1.1 (Scientific Linux) 2. 2.6.18-128.7.1 (Scientific Linux) 3. 2.6.18-155 (RHEL 5.4b) My mother is freeked out by this as she uses the numpad to enter her password to login... ;) |