From: Robert Love <rml@tech9.net>
To: sean darcy <seandarcy@hotmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.5.40 - no keyboard
Date: 05 Oct 2002 18:41:42 -0400 [thread overview]
Message-ID: <1033857702.742.4389.camel@phantasy> (raw)
In-Reply-To: <F134x4FR0rmTIVvLVKi0000fe8b@hotmail.com>
On Sat, 2002-10-05 at 18:37, sean darcy wrote:
> I've built 2.5.40 on a rh8.0 athlon box. It boots up OK, but NO keyboard.
>
> It's a vanilla MS natural keyboard with a small DIN PS/2 connector - not
> USB. Works fine with 2.4.19 - even prior 2.5.x's.
>
> I noticed that xconfig Input device support grays out
> CONFIG_KEYBOARD_ATKBD. As a test, I hand edited .config. Still didn't work.
You need to enable serio first. Something like this:
CONFIG_SERIO=y
CONFIG_SERIO_I8042=y
CONFIG_KEYBOARD_ATKBD=y
should work.
Robert Love
next prev parent reply other threads:[~2002-10-05 22:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-05 22:37 2.5.40 - no keyboard sean darcy
2002-10-05 22:41 ` Robert Love [this message]
2002-10-05 23:08 ` Sebastian D.B. Krause
-- strict thread matches above, loose matches on Subject: below --
2002-10-06 4:21 sean darcy
2002-10-07 17:17 ` Vojtech Pavlik
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=1033857702.742.4389.camel@phantasy \
--to=rml@tech9.net \
--cc=linux-kernel@vger.kernel.org \
--cc=seandarcy@hotmail.com \
/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