Date: Tue, 9 May 2006 10:24:23 -0500 From: "Stephanie Bridges" <sbridges@iastate.edu> To: "'Lennon Cook'" <maguswizardo@gmail.com> Cc: freebsd-questions@freebsd.org Subject: RE: Problem with cordless mouse/Keyboard combo set Message-ID: <005801c6737c$a67bfbc0$0c20ba81@econ.iastate.edu> In-Reply-To: <76ebe6440605081630g779cb751ubef4ea8137896e81@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Lennon Cook wrote: > Stephanie Bridges <sbridges@iastate.edu> wrote: >> Do you have a /dev/ums0 (my usb mouse device)? > This exists only when my other mouse (the working one) is plugged in, > and I have no other /dev/ums* . > >> Also, even when my mouse >> didn't really work, disconnecting/reconnecting the receiver from the >> usb port (moving to another or leaving in the same port) would >> generate log messages that the mouse was being recognized correctly. > Ok, when I reconnect it, it recognises as a keyboard and mouse set, > and creates two files: /dev/ukbd0 and /dev/uhid0 . It tells me the > following May 9 09:06:01 dragon kernel: ukbd0: G-Tech CHINA USB > Wireless Mouse & KeyBoard V1.01, rev 2.00/0.20, addr 2, iclass 3/1 > May 9 09:06:01 dragon kernel: kbd1 at ukbd0 > May 9 09:06:01 dragon kernel: uhid0: G-Tech CHINA USB Wireless Mouse > & KeyBoard V1.01, rev 2.00/0.20, addr 2, iclass 3/1 Hmm, this is what I get upon disconnecting/reconnecting my receiver: ----------------- May 9 10:00:10 econ22 kernel: ukbd0: at uhub3 port 1 (addr 2) disconnected May 9 10:00:10 econ22 kernel: ukbd0: detached May 9 10:00:10 econ22 kernel: ums0: at uhub3 port 1 (addr 2) disconnected May 9 10:00:10 econ22 kernel: ums0: detached May 9 10:00:15 econ22 kernel: ukbd0: Logitech USB Receiver, rev 1.10/30.07, addr 2, iclass 3/1 May 9 10:00:15 econ22 kernel: kbd0 at ukbd0 May 9 10:00:15 econ22 kernel: ums0: Logitech USB Receiver, rev 1.10/30.07, addr 2, iclass 3/1 May 9 10:00:15 econ22 kernel: ums0: 16 buttons and Z dir. ---------------- I found some references (I believe on freebsd-current from January, look for "usb mouse support update plans") to a mouse showing up as a uhid device instead of ums -- apparently, it may not be reporting itself as a kind of mouse the USB mouse driver understands so it falls through to the uhid device. I'm not sure if you ever said, but are you on 6.0-RELEASE or something newer? I upgraded to 6.1, which fixed a lot of other unrelated things for me. ~~~~~~~~~~~~~~~~~~~~~~~ Stephanie Bridges Economics Department -- Iowa State University 80B Heady Hall, Ames, IA 50011 ph: 515.294.8732 ~~ fax: 515.294.0221 http://www.econ.iastate.edu
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?005801c6737c$a67bfbc0$0c20ba81>