Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S264026AbTIBS0V (ORCPT ); Tue, 2 Sep 2003 14:26:21 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S264231AbTIBS0V (ORCPT ); Tue, 2 Sep 2003 14:26:21 -0400 Received: from moutng.kundenserver.de ([212.227.126.183]:39628 "EHLO moutng.kundenserver.de") by vger.kernel.org with ESMTP id S264026AbTIBS0R convert rfc822-to-8bit (ORCPT ); Tue, 2 Sep 2003 14:26:17 -0400 From: Stefan Winter To: "Brown, Len" , Subject: Re: PROBLEM: no keyboard and mouse on 2.6.0-test4 (notebook) Date: Tue, 2 Sep 2003 20:25:32 +0200 User-Agent: KMail/1.5.3 References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8BIT Content-Disposition: inline Message-Id: <200309022025.32867.mail@stefan-winter.de> Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2288 Lines: 60 > Did earlier versions of 2.6 (or 2.5) work? I have now localized the version that broke keyboard support for me. It worked in 2.5.24 and broke in 2.5.25. After a quick look at the ChangeLog for 2.5.25 it seems that has commited quite some stuff that relates to keyboard. Greetings, Stefan Winter > > Curious that vanilla 2.4.x has an issue with kbd interrupts on this box, > but SuSE 8.2 does not. Apparently SuSE 8.2 has a fix or workaround for > this box that isn't in the baseline -- anybody know what it is? > > Thanks, > -Len > > > [7.7.] Other information that might be relevant to the problem > > (please look in /proc and include all information that you > > think to be relevant): > > sunshine:/proc # cat interrupts > > CPU0 > > 0: 4574746 XT-PIC timer > > 1: 14 XT-PIC i8042 > > 2: 0 XT-PIC cascade > > 5: 2 XT-PIC ohci1394, VIA8233 > > 9: 5 XT-PIC acpi > > 10: 4029 XT-PIC eth0 > > 11: 0 XT-PIC ehci_hcd > > 12: 89 XT-PIC i8042 > > 14: 5523 XT-PIC ide0 > > 15: 45 XT-PIC ide1 > > NMI: 0 > > LOC: 4570927 > > ERR: 62338 > > MIS: 0 > > > > [X.] Other notes, patches, fixes, workarounds: > > the interrupt count on INT1,CPU0 (see /proc/interrupts above) does not > > increase after key pressures. It looks like the interrupt > > from the keyboard > > isn?t caught. There is an issue on 2.4.x kernels that may > > relate to that > > problem: after running the kernel and restarting it with > > "init 6", the BIOS > > warns about "No interrupts from keyboard 0" and the BIOS > > password entry > > field doesn?t catch keypresses any more [this is only an > > issue with the > > vanilla kernel - SuSE 8.2?s patched kernel is fine]. An "init 0" and > > re-poweron solves that issue in 2.4.x kernels. Maybe the 2.6. kernel > > encounters that phenomenon earlier. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/