Red Hat Bugzilla – Bug 609377
2.6.35-0.13.rc3.git2.fc14 = laptop keyboard doesn't function.
Last modified: 2010-07-01 11:11:39 EDT
Description of problem:
After kernel update from 2.6.35-0.2.rc3.git0.fc14 to 2.6.35-0.13.rc3.git2.fc14, my laptop keyboard became dead. It doesn't react on "capslock" key = LED doesn't turn on, "enter" doesn't work also.
It is impossible to change tty.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
0) Similar issue here (kernel-2.6.35-0.2.rc3.git0.fc14.i686 on IBM ThinkPad T41, both runlevel 3 and 5).
1) Note that input from the mouse is also ignored (for lack of a better term). So maybe all input is lost somehow.
For what it's worth, logging in and typing over a serial line and over ssh both work (serial line feels rather sluggish, but that's probably to be expected at 9600 baud).
Can you get console and check any error messages?
Created attachment 427926 [details]
dmesg of 2.6.35-0.13.rc3.git2.fc14.i686 booting
0) Would dmesg do?
1) Some errors there, but nothing that is obviously related to this issue.
(In reply to comment #0)
> Description of problem:
> After kernel update from 2.6.35-0.2.rc3.git0.fc14 to 2.6.35-0.13.rc3.git2.fc14,
> my laptop keyboard became dead. [...]
Bug #609359 is about another ThinkPad with a similar problem. Is your laptop perhaps a ThinkPad too?
My laptop as well Lenovo, but it is 3000 C100.
The question is - how to install or update new kernel through "yum upadate" and do not remove previous one?
Otherwise I won't be able to boot.
(In reply to comment #6)
> My laptop as well Lenovo, but it is 3000 C100.
> The question is - how to install or update new kernel through "yum upadate" and
> do not remove previous one?
Normally previous kernel is not removed, you can choose kernel during boot.
See if you have "timeout=5" line in /boot/grub/grub.conf - this is 5 second deley to before automatic boot of default kernel.
Could you check if blacklisting thinkpad_acpi module helps?
Yum deletes third kernel, which actually I use to boot from, and yum will remove it, because it installs new one and good one will be come "third".
My laptop is not ThinkPad, it is Lenovo 3000 C100.
I will think about to disable ACPI.
(In reply to comment #7)
> > Could you check if blacklisting thinkpad_acpi module helps?
On my IBM ThinkPad T41 that doesn't help.
(In reply to comment #8)
> Yum deletes third kernel, which actually I use to boot from, and yum will
> remove it, because it installs new one and good one will be come "third".
Can't you just manually install an rpm of a working kernel?
Please attach dmesg from working kernel for compare.
Ok, kernel-2.6.35-0.15.rc3.git3.fc14 did not make any difference. Keyboard doesn't show any sign of life.
Booted on 2.6.35-0.2.rc3.git0.fc14.
Dmesg of the kernel-2.6.35-0.15.rc3.git3.fc14 is attached.
Created attachment 428046 [details]
Dmesg of the kernel-2.6.35-0.2.rc3.git0.fc14
Created attachment 428054 [details]
dmesg of 2.6.35-0.2.rc3.git0.fc14.i686 booting
(In reply to comment #11)
> Please attach dmesg from working kernel for compare.
_working_ kernel dmesg attached.
Same issue here, but not on a laptop. I have a standard desktop AMD Athlon(tm) 64 X2 Dual Core Processor 4200+ with an nvidia card GS8400.
kernel-2.6.35-0.15.rc3.git3.fc14 and kernel2.6.35-0.13.rc3.git2.fc14 are not working, Keyboard and mouse (both are PS/2) are dead.
I include a diff between dmesg and dmesg.old here:
New kernel may solve our problem, will see soon:
* Wed Jun 30 2010 Kyle McMartin <email@example.com> 2.6.35-0.19.rc3.git4
* Tue Jun 29 2010 Chuck Ebbert <firstname.lastname@example.org>
- Disable Intel Moorestown support -- it breaks PC keyboard controllers.
Yes, please check out:
(In reply to comment #17)
That build (2.6.35-0.19.rc3.git4.fc14.i686) seems to fix it over here.
Yes, I confirm that 2.6.35-0.19.rc3.git4.fc14.i686 solved keyboard problem on my Lenovo 3000.
I think, time to close this bug.
Administrative nit picking: I'm not sure this can already be closed (is a kernel with the fix we tested scheduled to be shipped already?). Moreover, NOTABUG is clearly wrong: "The problem described is not a bug. An [explanation] of why this resolution has been chosen should be supplied." (see: https://bugzilla.redhat.com/page.cgi?id=fields.html#status ).
Sorry about this, I change it.
Update of this kernel in the mail list:
*** Bug 609359 has been marked as a duplicate of this bug. ***
*** Bug 609787 has been marked as a duplicate of this bug. ***