From: A Guy Called Tyketto <tyketto@wizard.com>
To: Ed Sweetman <safemode@speakeasy.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: kbd not functioning in 2.5.25-dj2
Date: Sat, 13 Jul 2002 00:37:17 -0700 [thread overview]
Message-ID: <20020713073717.GA9203@wizard.com> (raw)
In-Reply-To: <1026545050.1203.116.camel@psuedomode>
On Sat, Jul 13, 2002 at 03:24:09AM -0400, Ed Sweetman wrote:
> Same config as in my last post about the issue linking with this
> kernel. I'm having my keyboard just not respond from boot. I've got
> Input Device support built in and i had it as module and the keyboard is
> ps/2. No idea what's going on here
>
Just a "me too" here.. I've had this problem since around 2.5.15-dj
and later, and have had input and keyboard support compiled into the kernel.
Luckily I was able to get into the box via ssh, and check things. both
keyboard and mouse are PS/2. If possible, see if you can do this, and check if
IRQ 1 is not listed in /proc/interrupts. That is what is happening with me,
while my mouse is working. For me to get my keyboard to work, I have to have
the following set:
CONFIG_INPUT=y
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=y
CONFIG_SERIO=y
CONFIG_SERIO_SERPORT=m
CONFIG_INPUT_KEYBOARD=y
CONFIG_KEYBOARD_ATKBD=y
CONFIG_KEYBOARD_XTKBD=y
CONFIG_INPUT_MOUSE=y
CONFIG_MOUSE_PS2=y
This leaves me without using the new Input API, but with a working
keyboard. with using the new API, mouse will work, keyboard will not. you can
try these, and use the old setup (I assume will be made legacy by the time 2.6
comes out), and let me know if they work. The new API seems to be working for
some people, but not all.
BL.
--
Brad Littlejohn | Email: tyketto@wizard.com
Unix Systems Administrator, | tyketto@ozemail.com.au
Web + NewsMaster, BOFH.. Smeghead! :) | http://www.wizard.com/~tyketto
PGP: 1024D/E319F0BF 6980 AAD6 7329 E9E6 D569 F620 C819 199A E319 F0BF
next prev parent reply other threads:[~2002-07-13 7:34 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-13 7:24 kbd not functioning in 2.5.25-dj2 Ed Sweetman
2002-07-13 7:37 ` A Guy Called Tyketto [this message]
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
2002-07-13 9:04 ` Russell King
-- strict thread matches above, loose matches on Subject: below --
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=20020713073717.GA9203@wizard.com \
--to=tyketto@wizard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=safemode@speakeasy.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.