|
From: Kjetil K. <kj...@kj...> - 2003-11-03 14:27:49
|
Hi! Svetoslav has been helping me a lot off-list, but touched by your attention, I guess I can bring it back on... :-) On Monday 03 November 2003 10:53, Aivils Stoss wrote: > >usb_control/bulk_msg: timeout > > google show similar results for "Tangtop Generic USBPS2" under Linux. > hid-core.c, hid-input.c, which is important, is quite old > FEB/AUG-2002. USB input derived from Johan Deneux , which go away > from USB backport since SEP-2002 :-( > > >Scary, huh? > > Very. I've upgraded to 2.4.22, Marcelo's tree, and patched with the latest bruby patch now, and I haven't seen this message since. (The patch didn't apply cleanly to the debian kernel-source, but nevermind). I guess this fixed that problem. 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 (and haven't for a few different configurations...), and the secondary keyboard and mouse are also quite dead... 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/ > > keyboard.c Tangtop Generic USBPS2 VT1 first VC 8 > > Correct. dmesg is helpful. Yup, the funny thing now is that my non-bruby 2.4.22 kernel detects both the mouse and keyboad on this device: input: USB HID v1.00 Keyboard [Tangtop Generic USBPS2] on usb1:2.0 input: USB HID v1.00 Mouse [Tangtop Generic USBPS2] on usb1:2.1 whereas the bruby kernel only detects the keyboard. That is, in dmesg I see keyboard.c Tangtop Generic USBPS2 vc:17-17 input: USB HID v1.00 Keyboard [Tangtop Generic USBPS2] on usb-00:04.2-2 (so, I'm now starting the second X-server with vt17, OK?) One of the recent things I've done, following Svetoslav's advice, is to add above hid usbcore to modules.conf (or rather /etc/modutils/local, that's how I understand the Debian Way... :-) ). I was for a while seriously confused, as KEYBDEV was not available in the kernel, but HID wanted it... :-) Allthough the above looks like the keyboard it least should be loaded, there is little to be seen in http://dev.kjernsmo.net/tmp/multi-user-logs3/proc.bus.usb.devices Mmmm, I much prefer the way it looks in /proc/bus/usb/devices of my currently running non-bruby kernel: P: Vendor=0d3d ProdID=0001 Rev= 0.01 S: Manufacturer=Tangtop S: Product=Generic USBPS2 C:* #Ifs= 2 Cfg#= 1 Atr=a0 MxPwr=100mA I: If#= 0 Alt= 0 #EPs= 1 Cls=03(HID ) Sub=01 Prot=01 Driver=hid E: Ad=81(I) Atr=03(Int.) MxPS= 8 Ivl=10ms I: If#= 1 Alt= 0 #EPs= 1 Cls=03(HID ) Sub=01 Prot=02 Driver=hid E: Ad=82(I) Atr=03(Int.) MxPS= 5 Ivl=10ms Currently, /dev/input/mouse0 is my USB mouse with the non-bruby-kernel. 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 I can't see that in my non-bruby kernel dmesg (ok, since I'm talking so much about it, I've dumped that too on my website)... I think I'm getting close now... :-) Help for the final bit would be greatly appreciated! Best, 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 |