From: Jesper Juhl <jesper.juhl@gmail.com>
To: Martin Bretschneider <mailing-lists-mmv@bretschneidernet.de>
Cc: linux-kernel@vger.kernel.org,
Jan Engelhardt <jengelh@linux01.gwdg.de>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>
Subject: Re: PROBLEM: PS/2 keyboard does not work with 2.6.15
Date: Fri, 6 Jan 2006 20:00:53 +0100 [thread overview]
Message-ID: <9a8748490601061100g1a467b86k1c020ea7f7cf0f33@mail.gmail.com> (raw)
In-Reply-To: <E1EuuTC-0000mF-00@mars.bretschneidernet.de>
On 1/6/06, Martin Bretschneider <mailing-lists-mmv@bretschneidernet.de> wrote:
> Martin Bretschneider <mailing-lists-mmv@bretschneidernet.de> wrote:
>
> with some debugging help of Dmitry Torokhov and Jan Engelhardt I
> could *not* find the cause why the PS/2 keyboard does not work.
>
> But other things do work:
> - If I connect the keyboard with the USB, it does work with 2.6.15.
> - If I use another pc with an old AMD 500, the PS/2 keyboard does
> work.
>
> So, it could be a strange problem between the motherboard chipset
> (nforce4), the 2.6.15 kernel and the PS/2 connection.
>
> I am going to test some Kernels beetween 2.6.14.2 and 2.6.15 to find
> the problem in some time.
>
Once you've narrowed down what two release kernels are "last one
working" & "first one broken" you can get even closer by doing a git
bisection search between those two to (hopefully) narrow it down to
the exact git commit that broke it.
It's a bit of work, but usually very useful to track down the exact
thing that broke it if nothing else finds the problem :)
--
Jesper Juhl <jesper.juhl@gmail.com>
Don't top-post http://www.catb.org/~esr/jargon/html/T/top-post.html
Plain text mails only, please http://www.expita.com/nomime.html
next prev parent reply other threads:[~2006-01-06 19:00 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-05 13:58 PROBLEM: PS/2 keyboard does not work with 2.6.15 Martin Bretschneider
2006-01-05 14:37 ` Dmitry Torokhov
2006-01-06 7:21 ` Jan Engelhardt
2006-01-06 16:29 ` Martin Bretschneider
2006-01-06 19:00 ` Jesper Juhl [this message]
2006-01-08 21:23 ` Martin Bretschneider
2006-01-08 22:19 ` Dmitry Torokhov
2006-01-09 9:50 ` Martin Bretschneider
2006-01-09 6:26 ` Dmitry Torokhov
2006-01-09 15:32 ` Alan Stern
2006-01-09 16:50 ` Dmitry Torokhov
2006-01-09 17:23 ` Alan Stern
2006-01-09 17:54 ` Dmitry Torokhov
2006-01-09 20:08 ` Martin Bretschneider
2006-02-04 7:01 ` mahesh
2006-01-10 7:43 ` Vojtech Pavlik
2006-01-10 15:12 ` Alan Stern
2006-01-10 15:28 ` Vojtech Pavlik
2006-01-10 15:37 ` Dmitry Torokhov
2006-01-11 0:01 ` Jan Rekorajski
2006-01-11 0:19 ` Pete Zaitcev
2006-01-11 15:26 ` Alan Stern
2006-01-11 16:01 ` Jan Rekorajski
2006-01-11 19:57 ` Pete Zaitcev
[not found] ` <161717d50601101019k34a901a8x37fb28187a609490@mail.gmail.com>
[not found] ` <d120d5000601101225h32b44f7eobae654056cf0318c@mail.gmail.com>
[not found] ` <161717d50601101419q373cde76y6b374f1ae289ca22@mail.gmail.com>
[not found] ` <d120d5000601101425g576f8fd3kc9de80a4b320c3bf@mail.gmail.com>
2006-01-11 2:45 ` Dave Neuer
2006-01-09 18:36 ` Martin Bretschneider
2006-01-09 19:09 ` Alan Stern
2006-01-09 6:10 Leonid
2006-01-14 14:20 Walt H
2006-01-14 17:09 ` Alan Stern
2006-01-14 19:27 ` Walt H
2006-01-15 15:45 ` Alan Stern
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=9a8748490601061100g1a467b86k1c020ea7f7cf0f33@mail.gmail.com \
--to=jesper.juhl@gmail.com \
--cc=dmitry.torokhov@gmail.com \
--cc=jengelh@linux01.gwdg.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mailing-lists-mmv@bretschneidernet.de \
/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;
as well as URLs for NNTP newsgroup(s).