Dmitry Torokhov wrote:
> On 9/15/05, Piter Punk <piterpk@terra.com.br> wrote:
> 
>>PCI: Found IRQ 12 for device 00:07.2
>>PCI: Sharing IRQ 12 with 00:07.3
>>uhci.c: USB UHCI at I/O 0xd400, IRQ 12
>>usb.c: new USB bus registered, assigned bus number 1
>>hub.c: USB hub found
>>hub.c: 2 ports detected
>>PCI: Found IRQ 12 for device 00:07.3
>>PCI: Sharing IRQ 12 with 00:07.2
>>uhci.c: USB UHCI at I/O 0xd800, IRQ 12
>>usb.c: new USB bus registered, assigned bus number 2
>>hub.c: USB hub found
>>hub.c: 2 ports detected
> 
> Hmm, your USB controllers hop onto IRQ12, I don't think mouse will
> like it. 

Ok, but with other mouses it works OK. And the mouse itself isn't
with problems, because it runs in other machines.

> Does the same happen with 2.6.13? Could you post boot log for
> it as well? Also, when booting 2.6.13 you might want to add
> "usb-handoff" to the kernel boot line.

The 2.6.13 dmesg is attached.
In 2.6.13 the mouse simply doesn't works. No lights, no detect,
nothing. You can see the /proc/bus/input/devices attacched, too.

The lspci -vv is attached.

usb-handoff don't help anything. The mouse light stills off and
nothing is showed in /proc/bus/input/devices.

Again, if i swap the VCOM mouse with a mouse from Mtek, the Mtek
mouse is detected and all goes ok. If, with machines on, i swap
the detect Mtek with VCOM, the VCOM works.

				Hope those info can help,

						Piter PUNK