From: Alan Stern <stern@rowland.harvard.edu>
To: Martin Bretschneider <mailing-lists-mmv@bretschneidernet.de>
Cc: Dmitry Torokhov <dtor_core@ameritech.net>,
<linux-kernel@vger.kernel.org>,
Jan Engelhardt <jengelh@linux01.gwdg.de>,
<linux-usb-devel@lists.sourceforge.net>, Greg KH <gregkh@suse.de>,
Leonid <nouser@lpetrov.net>
Subject: Re: PROBLEM: PS/2 keyboard does not work with 2.6.15
Date: Mon, 9 Jan 2006 14:09:01 -0500 (EST) [thread overview]
Message-ID: <Pine.LNX.4.44L0.0601091401470.7576-100000@iolanthe.rowland.org> (raw)
In-Reply-To: <E1Ew1sd-0000k3-00@mars.bretschneidernet.de>
On Mon, 9 Jan 2006, Martin Bretschneider wrote:
> Yes, I also use the OHCI controller (I guessed that this is
> necessary for low speed USB devices...), I commented the calls of
> quirk_usb_disable_?hci and renamed the compiled modules so that they
> cannot be loaded. Thus, the PS/2 keyboard *does* work with "USB
> keyboard support" enabled in the BIOS with kernel 2.6.15. But - of
> cource - no USB device does work.
Good work! This proves that the i8042 driver _is_ compatible with BIOS
legacy support.
The next step is to find out which part of the USB handoff code isn't
working right. Martin, first try uncommenting just the
quirk_usb_disable_ohci call but leave the modules renamed. That will
indicate whether the problem is in the handoff code or in the driver.
Next, try renaming the ohci-hcd.ko file back to its correct name so it
does get loaded. If the keyboard continues to work then the problem must
lie in either UHCI or EHCI. Try doing the same two-part test (enable the
quirk code and then un-rename the file) with each of them to see exactly
at what point the keyboard stops working.
Alan Stern
next prev parent reply other threads:[~2006-01-09 19:09 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
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 [this message]
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=Pine.LNX.4.44L0.0601091401470.7576-100000@iolanthe.rowland.org \
--to=stern@rowland.harvard.edu \
--cc=dtor_core@ameritech.net \
--cc=gregkh@suse.de \
--cc=jengelh@linux01.gwdg.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
--cc=mailing-lists-mmv@bretschneidernet.de \
--cc=nouser@lpetrov.net \
/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).