USB mouse, ums and wsmouse

[useche]

Hi Guys,

My problem is that my usb wireless mouse does not work on X or with smoused. From a message standpoint, everything seem normal. I got from dmesg:

uhidev0 at uhub4 port 2 configuration 1 interface 0 "Microsoft Microsoft
Wireless Optical Mouse\M-. 1.00" rev 2.00/0.07 addr 2
uhidev0: iclass 3/1, 23 report ids
ums0 at uhidev0 reportid 17: 3 buttons, Z dir
wsmouse1 at ums0 mux 0
uhid0 at uhidev0 reportid 18: input=0, output=0, feature=1
uhid1 at uhidev0 reportid 19: input=1, output=0, feature=0
uhid2 at uhidev0 reportid 20: input=1, output=0, feature=0
uhid3 at uhidev0 reportid 21: input=3, output=0, feature=0
uhid4 at uhidev0 reportid 23: input=0, output=0, feature=1

Which means that the mouse is detected and attached to the wsmouse driver as "wsmouse1". However, it does not work at all. I have been looking for a solution for a week now with no success. At this point I am clueless.

Any help is very appreciated.

Luis.

[BSDfan666]

I'm not sure if mice are multiplexed properly, I've honestly never installed multiple mice on a computer before.

Perhaps you should disable the integrated PS/2 mouse temporarily in UKC? or just change your xorg.conf file to use wsmouse1?

I just plugged in a USB mouse on a system that uses PS/2 devices, (..the majority of my systems do).. and X became aware of it instantly.

[jggimi]

I saw your thread on misc@, Luis.

While I can't help, directly, I can at least point to alternative behavior. My wms0 driver attaches without any mention of uhidev(4) "report ids", and works fine. And there are no report ids in the dmesg.

uhidev0 at uhub0
port 1 configuration 1 interface 0 "Logitech USB RECEIVER" rev 1.10/25.10 addr 2
uhidev0: iclass 3/1
ums0 at uhidev0: 16 buttons, Z dir
wsmouse1 at ums0 mux 0

[useche]

bsdfan666: I am doing this in a laptop and I cannot disable my touchpad (what is UKC?). Even if I use wsmouse1, it does not work.

jggimi: Looking at one correct dmesg output is certainly helpful. Before I didn't realize the "reportid"s could be somekind of error.

[BSDfan666]

jggimi was on track when he noticed the extra messages printed out.

Originally Posted by Miod Vallet

Sigh. Yet another Microsoft mouse with a botched report descriptor
layout.

I'm afraid that this device will not work under OpenBSD until enough
information is found to make it work.

As for your other post, the UKC is a configuration environment that allows you to enable/disable and change some devices.

At a boot> prompt, use the -c argument.. or you can use config(8) to make the changes permanent.

[BSDfan666]

The obvious solution is to obtain a different USB mouse, or to disable the laptops mouse in the BIOS and enable the Legacy support so that the USB mouse appears as a PS/2 device, you'll need to disable the uhci/ohci or ehci driver in OpenBSD first though.