Date: Thu, 21 Dec 2006 02:26:46 +0100 (CET) From: "Julian Stacey" <jhs@berklix.org> To: freebsd-usb@freebsd.org Subject: JVC Handy Mouse HC-MM55U works via unpowered hub but not direct. Message-ID: <200612210126.kBL1QkwK065675@fire.jhs.private>
next in thread | raw e-mail | index | archive | help
My stick mouse: JVC Handy Mouse HC-MM55U, wont work direct, but
will via a hub, even unpowered (so not a 0.5A limit problem )!
(actually it'll work via 2 different hubs that look same profile
except for the paint job.
It's not an unsurmountable problem, but weird & unexpected.
Stick mouse will also work OK via a powered hub, (but that doesnt
prove much - one could assume it's just a very greedy mouse drawing
more than 0.5 Amp. Though usbdevs -v reports : low speed, power
100 mA, config 1, rev 0.01.
I can make 2 guesses:
- Those hubs from vndr=0x04f1 might have a `big' electrolytic capacitor
smoothing the supply ?
- Maybe the voltage levels of the signal from the mouse are rather lackse,
& the computer direct is expecting more conformity to digital
thresholds, whereas the hubs are more forgiving ?
I can't think of any other reason ?
Here's usbd -d -v on 6.1-RELEASE for th 2 magicly good hubs:
usbd: device-attach event at 1166660806.602716000, USB2.0 Hub Controller, NEC Corporation:
vndr=0x0409 prdct=0x0058 rlse=0x0100 clss=0x0009 subclss=0x0000 prtcl=0x0000
device names: uhub3
usbd: Found action 'JHS - Hub Zedi' for USB2.0 Hub Controller, NEC Corporation at uhub3
usbd: device-attach event at 1166660807.293715000, product 0x0001, vendor 0x04f1:
vndr=0x04f1 prdct=0x0001 rlse=0x0001 clss=0x0000 subclss=0x0000 prtcl=0x0000
device names: ums1
usbd: Found action 'JHS - Mouse Stick' for product 0x0001, vendor 0x04f1 at ums1
usbd: Executing 'moused -p /dev/${DEVNAME} -I /var/run/moused.${DEVNAME}.pid; vidcontrol -m on'
vidcontrol: getting active vty: Inappropriate ioctl for device
usbd: 'moused -p /dev/${DEVNAME} -I /var/run/moused.${DEVNAME}.pid; vidcontrol -m on' returned 1
usbd: device-attach event at 1166660873.890891000, product 0x6560, vendor 0x04b4:
vndr=0x04b4 prdct=0x6560 rlse=0x0008 clss=0x0009 subclss=0x0000 prtcl=0x0000
device names: uhub3
usbd: Found action 'JHS - Hub MBO' for product 0x6560, vendor 0x04b4 at uhub3
usbd: device-attach event at 1166660874.579183000, product 0x0001, vendor 0x04f1:
vndr=0x04f1 prdct=0x0001 rlse=0x0001 clss=0x0000 subclss=0x0000 prtcl=0x0000
device names: ums1
usbd: Found action 'JHS - Mouse Stick' for product 0x0001, vendor 0x04f1 at ums1
usbd: Executing 'moused -p /dev/${DEVNAME} -I /var/run/moused.${DEVNAME}.pid; vidcontrol -m on'
vidcontrol: getting active vty: Inappropriate ioctl for device
usbd: 'moused -p /dev/${DEVNAME} -I /var/run/moused.${DEVNAME}.pid; vidcontrol -m on' returned 1
Julian
--
Julian Stacey. BSD Unix C Net Consultancy, Munich/Muenchen http://berklix.com
Mail Ascii, not HTML. Ihr Rauch = mein allergischer Kopfschmerz.
http://berklix.org/free-software
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200612210126.kBL1QkwK065675>