Stefano Carboni wrote:
> OK, now my usb-activated .config section is the following (where may I find
> Vojtech's test tools? How does it work?):
You can get it from the same site that you got the backport patch:
ftp://ftp.suse.cz/pub/development/input/ - you need evtest.c
Basically you compile it (gcc -Wall -o evtest evtest.c, or something
like that)
You make the event interface nodes:
mknod /dev/input/event0 c 13 64
mknod /dev/input/event1 c 13 65
mknod /dev/input/event2 c 13 66
and so on...
You then check the kernel logs to see which node you need (say event1),
then
evtest /dev/input/event1
It should be obvious at that point.
> Yes, I guess: I used usb-2.3.99-pre6-7-for-2.2.14.diff.gz file. By the way,
> maybe a(nother) silly question: I applied it to the normal 2.2.14 kernel,
> may I apply it also to Mandrake 2.2.14-15mdk.i586 kernel sources?
Don't know. Don't use Mandrake, and don't know what the differences are.
If I
had to guess, I would assume it will work fine.
> After compiling the kernel with the new options, I tried three usb
> configurations:
>
> #Again, mouse and keyboard connected to monitor hub connected to usb port
> usb.c: registered new driver usbdevfs
> usb.c: registered new driver hub
> usb.c: registered new driver hid
> mice: PS/2 mouse device common for all mice
> PCI: Enabling bus mastering for device 00:a0
> usb-ohci.c: USB OHCI at membase 0xc4000000, IRQ 5
> usb.c: new USB bus registered, assigned bus number 1
> usb.c: USB new device connect, assigned device number 1
> hub.c: USB hub found
> hub.c: 2 ports detected
> (...)
> usb.c: USB new device connect, assigned device number 2
> hub.c: USB hub found
>
> that looks the same, with mouse and keyboard not working
OK, either hub is stuffed or backport doesn't work properly.
> #keyboard connected to usb port, monitor hub and mouse disconnected
> usb.c: registered new driver usbdevfs
> usb.c: registered new driver hub
> usb.c: registered new driver hid
> mice: PS/2 mouse device common for all mice
> PCI: Enabling bus mastering for device 00:a0
> usb-ohci.c: USB OHCI at membase 0xc4000000, IRQ 5
> usb.c: new USB bus registered, assigned bus number 1
> usb.c: USB new device connect, assigned device number 1
> hub.c: USB hub found
> hub.c: 2 ports detected
> (...)
> usb.c: USB new device connect, assigned device number 2
> keybdev.c: Adding keyboard: input0
> event0: Event device for input0
> input0: USB HID v1.00 Keyboard
> mouse0: PS/2 mouse device for input1
> keybdev.c: Adding keyboard: input1
> event1: Event device for input1
> input1: USB HID v1.00 device
>
> ...and, wonderful, the keyboard works very fine!
Has this keyboard got a mouse socket on it? Or is this the touchpad? Or
is some kind of multimedia / web keyboard? That should (somewhat) work
too - try the evtest on input1 with the keyboard plugged in
> #mouse connected to usb port, monitor hub and keyboard disconnected
> usb.c: registered new driver usbdevfs
> usb.c: registered new driver hub
> usb.c: registered new driver hid
> mice: PS/2 mouse device common for all mice
> PCI: Enabling bus mastering for device 00:a0
> usb-ohci.c: USB OHCI at membase 0xc4000000, IRQ 5
> usb.c: new USB bus registered, assigned bus number 1
> usb.c: USB new device connect, assigned device number 1
> hub.c: USB hub found
> hub.c: 2 ports detected
> (...)
> usb.c: USB new device connect, assigned device number 2
> mouse0: PS/2 mouse device for input0
> event0: Event device for input0
> input0: USB HID v1.00 Mouse
>
> and then, I followed step by step your guide indications:
> - In /proc/interrupts this time the count in the line:
> 5: 9 XT-PIC usb-ohci, ESS Solo1
> increased by two per click.
This is a good sign. Basically this confirms that the USB transport is
working fine (although we already knew that from the keyboard).
> - But when I continued to the next step, I obtained the result:
> [root@localhost /root]# mkdir /dev/usb
> [root@localhost /root]# mknod /dev/usb/usbmouse0 c 13 32
> [root@localhost /root]# cat /dev/usb/usbmouse0
> cat: /dev/usb/usbmouse0: No such device
OK, probably the mousedev part isn't properly associated with the hid
and input parts. This is almost certainly a bug in the backport
(not-exported symbols?). I am sure Vojtech will fix it eventually,
although most developers seem to be looking to 2.4...
I noted Harold Oga's suggestion to use modules, which is probably what
Vojtech tested. Does this fix it?
> I tried also on console (without, for now, touch the X configuration) with:
> gpm -m /dev/usb/usbmouse0 -t imps2
> with no result. Indeed, on my presario there is a touchpad that is seen as
> PS/2, I guess, and I don't know exactly what to do to have both pointers
> working (or switch from one to the other)...
Use gpm in multiplexer mode - there are instructions in the USB Guide.
Use XInput extensions if you only want X support.
> The directory /proc/bus/usb exists, but it is empty in any of the three
> above configurations I tried.
Err, did you mount usbdevfs? Try
mount -t usbdevfs usbdevfs /proc/bus/usb
In any case, this isn't especially important any more, since we know the
devices are being enumerated correctly. It would be nice to see the tree
grow though!
Brad
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
