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- 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