public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Stefan Winter <mail@stefan-winter.de>
To: "Brown, Len" <len.brown@intel.com>, <linux-kernel@vger.kernel.org>
Subject: Re: PROBLEM: no keyboard and mouse on 2.6.0-test4 (notebook)
Date: Tue, 2 Sep 2003 20:25:32 +0200	[thread overview]
Message-ID: <200309022025.32867.mail@stefan-winter.de> (raw)
In-Reply-To: <BF1FE1855350A0479097B3A0D2A80EE009FCE1@hdsmsx402.hd.intel.com>

> 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 <vojtech@twilight.ucw.cz> 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.


  parent reply	other threads:[~2003-09-02 18:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-01  2:45 PROBLEM: no keyboard and mouse on 2.6.0-test4 (notebook) Brown, Len
2003-09-02  6:34 ` Stefan Winter
2003-09-02 18:25 ` Stefan Winter [this message]
2003-09-23 17:13 ` Stefan Winter
2003-09-29  7:00 ` [SOLVED] no keyboard and mouse on 2.6.0-test5 (notebook) Stefan Winter
  -- strict thread matches above, loose matches on Subject: below --
2003-08-31 10:50 PROBLEM: no keyboard and mouse on 2.6.0-test4 (notebook) Stefan Winter

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200309022025.32867.mail@stefan-winter.de \
    --to=mail@stefan-winter.de \
    --cc=len.brown@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox