keyboard loss in DF

Michael Powell nightrecon at hotmail.com
Mon Dec 13 02:40:51 PST 2004


Jeroen Ruigrok/asmodai wrote:

> -On [20041213 05:12], Matthew Dillon (dillon at xxxxxxxxxxxxxxxxxxxx) wrote:
>>    If possible could you try some older kernels?  There are older kernel
>>    images (just the kernel, not the whole ISO) available for download.
>>    Try going back a month or two and see if the problem is still there,
>>    then try going back even further.
> 
> I've been having it for at least over 2 months.
> 
> Problem is that I cannot do too much reboot/testing since it is my box at
> work and I am supposed to do some work here. ;)
> 
> My guess is that the interrupt code is going tits up somewhere all of a
> sudden since it deadlocks the entire keyboard.  If I remember correctly I
> couldn't even use the LED/status switch of caps-lock/num-lock and the
likes.
> 
> If others could verify this.
> 

Yes, this is what I see too. I am wondering why such a small group sees this
problem, while it seems most do not. I look for commonality and am curious
as to what chipset your mobo is using. An i8042 is supposed to be an i8042,
but I'm wondering if the cause couldn't be something else such as related
to whatever generation IRQ controller a particular chipset has.

I also tried the moused_enable as per other post, as well as things like
turning off typematic, usb, etc in BIOS. I've booted the LiveCD and run
both the HD install and the LiveCD in single user, safe mode, etc and
nothing external I attempt has any effect.

-Mike 





More information about the Bugs mailing list