Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 28 Feb 2005 15:39:07 -0500
From:      Louis LeBlanc <FreeBSD@keyslapper.net>
To:        freebsd-questions@freebsd.org
Subject:   Re: USB Mouse issues
Message-ID:  <20050228203907.GJ59697@keyslapper.net>
In-Reply-To: <42237DFB.1040608@karnaugh.za.net>
References:  <42237DFB.1040608@karnaugh.za.net>

next in thread | previous in thread | raw e-mail | index | archive | help

--8P1HSweYDcXXzwPJ
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On 02/28/05 10:24 PM, Colin Alston sat at the `puter and typed:
> Hi
>=20
> I recently had some fun today on FreeBSD 5.3
>=20
> Feb 28 19:57:24 jupiter kernel: device_attach: ums0 attach returned 6
> Feb 28 19:57:24 jupiter kernel: ums0: at uhub0 port 1 (addr 2) disconnect=
ed
> Feb 28 19:57:25 jupiter kernel: uhid0: Microsoft product 0x0040, rev=20
> 1.10/3.00,
> addr 2, iclass 3/1
> Feb 28 19:57:25 jupiter kernel: uhid0: no report descriptor
> Feb 28 19:57:25 jupiter kernel: device_attach: uhid0 attach returned 6
> Feb 28 19:57:25 jupiter kernel: uhid0: at uhub0 port 1 (addr 2) disconnec=
ted
> Feb 28 19:57:26 jupiter kernel: uhid0: Microsoft product 0x0040, rev=20
> 1.10/3.00,
>=20
> What its supposed to look like is - achived after some rebooting,=20
> swearing and praying to the USB gods.
> Feb 28 19:58:44 jupiter kernel: ums0: Microsoft Microsoft 3-Button Mouse=
=20
> with IntelliEye(TM), rev 1.10/3.00, addr 2, iclass 3/1
>=20
> Not really sure whats going on, very likely my dodgey VIA USB chipset as=
=20
> this happend on Debian as well.

I've had some interesting stuff happen with usb pointer devices
recently too.  I found that when I plug them in at runtime, they seem
to get swept up by moused via the usb daemon, and wisked away to
/dev/sysmouse.

What really confused me was that I did not have moused enabled.  It
took quite a while to even realize that it was running.

Naturally, when you want to hook up a mouse and a trackball (the
trackball doesn't hurt my hand - I only use the mouse for fine pointer
work, like playing NWN), this gets tricky to have them both pulled out
=66rom under you to a place you can't really get them without rebooting
X.  When I rebooted, I got pretty much the same thing you did -
everything worked.

What I finally did was find the device "Mouse" section in
/etc/usbd.conf and comment it all out.  This way, the pointers stay
accessible at the ums* device, even when plugged in at runtime - the
usb daemon leaves them alone for apps (like X) to access there.

HTH

Lou
--=20
Louis LeBlanc                          FreeBSD-at-keyslapper-DOT-net
Fully Funded Hobbyist,                   KeySlapper Extrordinaire :)
Please send off-list email to:         leblanc at keyslapper d.t net
Key fingerprint =3D C5E7 4762 F071 CE3B ED51  4FB8 AF85 A2FE 80C8 D9A2

Kinkler's Second Law:
  All the easy problems have been solved.

--8P1HSweYDcXXzwPJ
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (FreeBSD)

iD8DBQFCI4Frr4Wi/oDI2aIRAi6HAKCCe/EIucHeVi2cvLRoJsKn0hVyTgCfc77R
RT+F64fNQawA8ETL9bQ81Sc=
=EtzX
-----END PGP SIGNATURE-----

--8P1HSweYDcXXzwPJ--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050228203907.GJ59697>