From: Vojtech Pavlik <vojtech@suse.cz>
To: A Guy Called Tyketto <tyketto@wizard.com>
Cc: Ed Sweetman <safemode@speakeasy.net>, linux-kernel@vger.kernel.org
Subject: Re: kbd not functioning in 2.5.25-dj2
Date: Sat, 13 Jul 2002 11:32:36 +0200 [thread overview]
Message-ID: <20020713113236.A29227@ucw.cz> (raw)
In-Reply-To: <20020713090702.GA1094@wizard.com>; from tyketto@wizard.com on Sat, Jul 13, 2002 at 02:07:02AM -0700
On Sat, Jul 13, 2002 at 02:07:02AM -0700, A Guy Called Tyketto wrote:
> On Sat, Jul 13, 2002 at 04:45:56AM -0400, Ed Sweetman wrote:
> > Nope, failure. I'm not getting any reaction from the kernel at all
> > about the keyboard. I'm including my config
>
> You have network support compiled in. Are you able to get into the box
> remotely (ssh, telnet, etc)? If so, get onto the box, and mail me the output
> of `cat /proc/interrupts. I'd like to confirm something that's on my end as
> well. my guess is that IRQ 1 is not listed. Another thing I should mention:
> I'm encountering this problem with 2.5.25, though I reported this in the
> 2.5.20-dj tree. Vanilla 2.5.25 still has the legacy API there, so I'm able to
> fall back on that.
Vanilla 2.5.25 still uses the original driver even if the new one was
enabled. It isn't removed there. If both are enabled, they won't work.
-dj trees have the old driver removed, so the new one can work. In
2.5.26 (or http://linux-input.bkbits.net:8080/linux-input) the new
driver config option will disable the old one.
> I haven't run a -dj kernel since 2.5.20-dj3.
>
> > CONFIG_INPUT=y
> > #
> > # Userland interfaces
> > #
> > CONFIG_INPUT_KEYBDEV=y
> > CONFIG_INPUT_MOUSEDEV=y
> > CONFIG_INPUT_MOUSEDEV_SCREEN_X=1024
> > CONFIG_INPUT_MOUSEDEV_SCREEN_Y=768
> > CONFIG_INPUT_EVDEV=y
> > # CONFIG_INPUT_EVBUG is not set
> >
> > CONFIG_SERIO=y
> > # CONFIG_SERIO_I8042 is not set
>
> IIRC, CONFIG_SERIO_I8042 must be set for you to have a keyboard
> present. This is the chipset that the keyboard and mouse use. This has to be
> set to y.
>
> > CONFIG_I8042_REG_BASE=60
> > CONFIG_I8042_KBD_IRQ=1
> > CONFIG_I8042_AUX_IRQ=12
>
> Rest looks fine. give that a go, and see what you get.
--
Vojtech Pavlik
SuSE Labs
next prev parent reply other threads:[~2002-07-13 9:29 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-13 7:24 Ed Sweetman
2002-07-13 7:37 ` A Guy Called Tyketto
2002-07-13 8:01 ` Ed Sweetman
2002-07-13 8:45 ` Ed Sweetman
2002-07-13 9:06 ` Vojtech Pavlik
2002-07-13 21:48 ` A Guy Called Tyketto
2002-07-14 8:05 ` Vojtech Pavlik
2002-07-14 10:18 ` A Guy Called Tyketto
2002-07-14 10:32 ` Russell King
2002-07-14 12:01 ` Vojtech Pavlik
2002-07-14 12:17 ` Andries Brouwer
2002-07-14 12:37 ` Vojtech Pavlik
2002-07-14 13:36 ` Rogier Wolff
2002-07-14 17:32 ` Vojtech Pavlik
2002-07-14 17:49 ` Russell King
2002-07-14 17:59 ` Vojtech Pavlik
2002-07-14 18:07 ` Russell King
2002-07-14 18:11 ` Vojtech Pavlik
2002-07-14 17:37 ` Andries Brouwer
2002-07-14 18:01 ` Vojtech Pavlik
2002-07-14 18:13 ` Russell King
2002-07-14 18:17 ` Vojtech Pavlik
2002-07-15 3:53 ` Maciej W. Rozycki
2002-07-14 21:30 ` A Guy Called Tyketto
2002-07-15 3:00 ` Vojtech Pavlik
2002-07-15 8:30 ` A Guy Called Tyketto
2002-07-15 7:28 ` Alexander Hoogerhuis
2002-07-15 10:56 ` Arnd Bergmann
2002-07-15 10:06 ` Alexander Hoogerhuis
2002-07-13 9:07 ` A Guy Called Tyketto
2002-07-13 9:32 ` Vojtech Pavlik [this message]
2002-07-13 9:04 ` Russell King
2002-07-15 15:45 Rudmer van Dijk
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=20020713113236.A29227@ucw.cz \
--to=vojtech@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=safemode@speakeasy.net \
--cc=tyketto@wizard.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
all inboxes | Powered by JetHome®