From: Alan Stern <stern@rowland.harvard.edu>
To: Walt H <walt_h@lorettotel.net>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
<linux-usb-devel@lists.sourceforge.net>,
<dmitry.torokhov@qmail.com>, <vojtech@suse.cz>
Subject: Re: PROBLEM: PS/2 keyboard does not work with 2.6.15
Date: Sat, 14 Jan 2006 12:09:02 -0500 (EST) [thread overview]
Message-ID: <Pine.LNX.4.44L0.0601141206280.8167-100000@netrider.rowland.org> (raw)
In-Reply-To: <43C908C0.9090706@lorettotel.net>
On Sat, 14 Jan 2006, Walt H wrote:
> I've an AMD based SMP setup w/ Chaintech 7KDD motherboard. It's an older
> board, and there are no more recent BIOS updates available for me than
> what I'm running. I've tried enabling/disabling legacy USB
> keyboard/mouse emulation in the BIOS with no change. I'm using a USB
> mouse connected via the OHCI controller in addition to the ps/2
> keyboard. If I comment out the handoff code in pci-quirks.c the
> keyboard works, even after loading the USB modules. I'm running a ck
> based 2.6.15 kernel BTW.
>
> During bootup with handoff code enabled, I do see a message print when
> PS/2 gets init'd, and I think it is
> "i8042.c: Can't read CTR while initializing i8042", but it scrolls by
> too fast so I'm not positive.
>
> lspci and config attached. Anything else you need? Please CC replies
> to me, as I'm not subscribed. I tried to CC relevant people involved,
> sorry if I missed anyone. Thanks,
What happens if you comment out only the OHCI part of the hand-off code,
or only the EHCI part?
Check dmesg to see exactly what that i8042 message says. Are there any
lines reporting handoff problems in ohci-hcd or ehci-hcd?
Alan Stern
next prev parent reply other threads:[~2006-01-14 17:09 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-14 14:20 PROBLEM: PS/2 keyboard does not work with 2.6.15 Walt H
2006-01-14 17:09 ` Alan Stern [this message]
2006-01-14 19:27 ` Walt H
2006-01-15 15:45 ` Alan Stern
-- strict thread matches above, loose matches on Subject: below --
2006-01-09 6:10 Leonid
2006-01-05 13:58 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
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.0601141206280.8167-100000@netrider.rowland.org \
--to=stern@rowland.harvard.edu \
--cc=dmitry.torokhov@qmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
--cc=vojtech@suse.cz \
--cc=walt_h@lorettotel.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).