Menu
▾
▴
Re: Mouse and keyboard troubles with USB -> PS/2 adapter
|
From: Kjetil K. <kj...@kj...> - 2003-11-03 22:38:59
|
Hi! I'm following up on myself, I've done a few small things. Mainly, I compiled the USB stuff, UHCI, HID etc into the kernel, rather as modules. On Monday 03 November 2003 15:27, Kjetil Kjernsmo wrote: > The current status is (on the surface) that X starts OK on both > screens, but only the main PS/2 keyboard works. There's no output > from the devices in /dev/input/ except event1, which is the PS/2 > keyboard. The primary mouse (on the PS/2 port) is dead, not even > giving output to /dev/psaux Now, the primary mouse works and it sends output to both /dev/input/mouse0 and /dev/psaux. So it actually looks like it helped to not use modules for this... > and the secondary keyboard and mouse are also quite dead... They still are. > A new set of logs and config files (aka "More about my system than > would be good for anybody's sanity) is to be found at > http://dev.kjernsmo.net/tmp/multi-user-logs3/ Now supplemented with something new, see below. > There are a couple of lines in the bruby-kernel dmesg that looks > somewhat suspecious...: > usb-uhci.c: interrupt, status 2, frame# 658 > hid-core.c: ctrl urb status -75 received Googling and reading source (!), I find the following info: The error is apparently this: -EOVERFLOW The amount of data returned by the endpoint was greater than either the max packet size of the endpoint or the remaining buffer size. "Babble". The question is then who does it, the mouse or the keyboard? The keyboard seems to be initialized allready, so perhaps it is the mouse? Is HID then giving up breath and giving up on both the keyboard and the mouse? I figured, since I'm seeing this in the backstreet ruby kernel, and not in the vanilla (that is, debian-patched) kernel, am I actually getting bitten by a bug....? Well, I went back and enabled CONFIG_USB_DEBUG=y (and I have CONFIG_INPUT_EVBUG=m, but I haven't enabled the general kernel debugging). I've including this evening's kern.log in http://dev.kjernsmo.net/tmp/multi-user-logs3/kern.log and the new config is there too, but note that the rest is from the previous boot.... These are the messages that looks relevant to USB/HID problems.....: Nov 3 20:27:09 owl kernel: usb.c: hub driver claimed interface dfe9fe40 Nov 3 20:27:09 owl kernel: host/usb-uhci.c: v1.275:USB Universal Host Controller Interface driver Nov 3 20:27:09 owl kernel: usb.c: registered new driver hiddev Nov 3 20:27:09 owl kernel: usb.c: registered new driver hid Nov 3 20:27:09 owl kernel: hid-core.c: v1.31:USB HID core driver Nov 3 20:27:09 owl kernel: mice: PS/2 mouse device common for all mice Nov 3 20:27:09 owl kernel: input: ImExPS/2 Logitech Explorer Mouse on isa0060/serio1 Nov 3 20:27:09 owl kernel: serio: i8042 AUX port at 0x60,0x64 irq 12 Nov 3 20:27:09 owl kernel: keyboard.c AT Set 2 keyboard vc:1-16 Nov 3 20:27:09 owl kernel: input: AT Set 2 keyboard on isa0060/serio0 Nov 3 20:27:09 owl kernel: serio: i8042 KBD port at 0x60,0x64 irq 1 Nov 3 20:27:09 owl kernel: hub.c: port 2, portstatus 301, change 2, 1.5 Mb/s Nov 3 20:27:09 owl kernel: hub.c: port 2, portstatus 301, change 2, 1.5 Mb/s Nov 3 20:27:09 owl last message repeated 2 times Nov 3 20:27:09 owl kernel: hub.c: port 2, portstatus 303, change 0, 1.5 Mb/s Nov 3 20:27:09 owl kernel: hub.c: new USB device 00:04.2-2, assigned address 2 Nov 3 20:27:09 owl kernel: usb.c: kmalloc IF dfe5a3c0, numif 2 Nov 3 20:27:09 owl kernel: usb.c: skipped 1 class/vendor specific interface descriptors Nov 3 20:27:09 owl kernel: usb.c: skipped 1 class/vendor specific interface descriptors Nov 3 20:27:09 owl kernel: usb.c: new device strings: Mfr=1, Product=2, SerialNumber=0 Nov 3 20:27:09 owl kernel: usb.c: USB device number 2 default language ID 0x409 Nov 3 20:27:09 owl kernel: Manufacturer: Tangtop Nov 3 20:27:09 owl kernel: Product: Generic USBPS2 Nov 3 20:27:09 owl kernel: keyboard.c Tangtop Generic USBPS2 vc:17-17 Nov 3 20:27:09 owl kernel: input: USB HID v1.00 Keyboard [Tangtop Generic USBPS2] on usb-00:04.2-2 Nov 3 20:27:09 owl kernel: usb.c: hid driver claimed interface dfe5a3c0 Nov 3 20:27:09 owl kernel: host/usb-uhci.c: interrupt, status 2, frame# 827 Nov 3 20:27:09 owl kernel: hid-core.c: ctrl urb status -75 received If I am to go waaaaay beyond what I should put my nose into, the warning is something about size, and that's kmalloc too, so perhaps kmalloc IF dfe5a3c0, numif 2 has something to do with it, since that's the problematic interface... Or perhaps I'm just doing what the docs I pasted above says, babbling... :-) Just poking... :-) Cheers, Kjetil -- Kjetil Kjernsmo Astrophysicist/IT Consultant/Skeptic/Ski-orienteer/Orienteer/Mountaineer kj...@kj... web...@sk... ed...@le... Homepage: http://www.kjetil.kjernsmo.net/ OpenPGP KeyID: 6A6A0BBC |
