On Sat, Jul 13, 2002 at 12:37:17AM -0700, A Guy Called Tyketto wrote:
> 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
You're missing support for the actual PS/2 hardware itself; you've got
support for the PS/2 keyboard protocol and keyboard device, but nothing
to actually talk to the physical hardware. You probably want to turn on:
dep_tristate ' i8042 PC Keyboard controller' CONFIG_SERIO_I8042 $CONFIG_SERIO $CONFIG_ISA
--
Russell King (rmk@arm.linux.org.uk) The developer of ARM Linux
http://www.arm.linux.org.uk/personal/aboutme.html
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Mon Jul 15 2002 - 22:00:25 EST