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