Re: Has my intel box two AT keyboard interfaces

[Vojtech P. <vo...@su...>]

On Mon, Feb 11, 2002 at 12:32:09PM +0200, Aivils Stoss wrote:
> Hi
>      I plug second keyboard in PS/2 hole and get this:
> skipped dmesg
> Testing ttyS0 (0x03f8, 0x00000000)...
> ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
> Testing ttyS1 (0x02f8, 0x00000000)...
> ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
> Testing ttyS2 (0x03e8, 0x00000000)...
> serial: ttyS2: simple autoconfig failed (ff, ff)
> Testing ttyS3 (0x02e8, 0x00000000)...
> serial: ttyS3: simple autoconfig failed (ff, ff)
> serio: i8042 KBD port at 0x60,0x64 irq 1
> serio: i8042 AUX port at 0x60,0x64 irq 12
> input.c: calling /sbin/hotplug input [HOME=/
> PATH=/sbin:/bin:/usr/sbin:/usr/bin ACTION=add PRODUCT=11/1/2/ab83
> NAME=atkbd.c AT Set 2 keyboard]
> input.c: hotplug returned -2
> input: AT Set 2 keyboard on isa0060/serio1
> input.c: calling /sbin/hotplug input [HOME=/
> PATH=/sbin:/bin:/usr/sbin:/usr/bin ACTION=add PRODUCT=11/1/2/ab02
> NAME=atkbd.c AT Set 2 keyboard]
> input.c: hotplug returned -2
> input: AT Set 2 keyboard on isa0060/serio0
> skipped dmesg
> 
> 
> If single pluged in, both keyboards works very fine. If two pluged in,
> works only second keyboard with PS/2 connector.

Can you #define I8042_DEBUG_IO in drivers/input/serio/i8042.h and send
me the dmesg in that case? That'd tell us why the two keyboard
combination fails on your system.

By the way, what tree are you using? Latest CVS? What version of
i8042.o?

> First keyboard has old type connector. inputattach  -ps2ser :  No such
> device. Both keyboards detected without ps2serkbd module.

PS2serkbd isn't needed unless you connect the keyboard to the COM ports.

> Under ruby I lost my serial mouse. Any programm would use serial hungup my
> system.
> Sample$ cat /dev/ttyS0
> Do not know how to debug this. With printk() I find , uart_open() is caled.
> In uart_open()  uart_startup() ever end, uart_block_til_ready() may start,
> but never end. If debug is turned on in serial_core.c and serial_8250.c
> sometimes I get message:
> rs_interrupt_single(4)...
> status=f9...IIR=C1...end
> Sometimes this message repeated 2...3 times.

That's a bug in the new serial core most likely.

-- 
Vojtech Pavlik
SuSE Labs