Re: Problem with cordless mouse/Keyboard combo set
Stephanie Bridges wrote: 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. I said in my original message that I was on 6.0-STABLE, but this appears to have been inacurate (I was judging by the URLs printed by pkg_add -r ) - uname(1) reports that I'm on 6.1-BETA4. -- Lennon Victor Cook "He who receives an idea from me receives without lessening, as he who lights his candle at mine receives light without darkening" - Thomas Jefferson ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: Problem with cordless mouse/Keyboard combo set
Lennon Cook wrote: > Stephanie Bridges <[EMAIL PROTECTED]> 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 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Problem with cordless mouse/Keyboard combo set
Stephanie Bridges <[EMAIL PROTECTED]> 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 -- Lennon Victor Cook "He who receives an idea from me receives without lessening, as he who lights his candle at mine receives light without darkening" - Thomas Jefferson ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: Problem with cordless mouse/Keyboard combo set
Lennon Cook wrote: > Stephanie Bridges <[EMAIL PROTECTED]> wrote: >> I had the same problem with the mouse (would occasionally move the >> cursor, never any clicks) until I accidentally got the receiver >> closer to the mouse. I now have the receiver about three inches >> away from the mouse. Works wonderfully well now. > Thanks Stephanie, but unfortunately that didn't help here. I > have moved my receiver so close to the mouse that its hard to > not bump them, but the mouse still doesn't work. > > What I have noticed since I sent my original message, is that > /dev/sysmouse exists even when only the non-working mouse is > connected nto the system. Does this mean that FreeBSD /is/ > detecting the mouse (and hence that I should be looking > somewhere else than this list for the problem), or does that > file simply always exist? Lennon, Do you have a /dev/ums0 (my usb mouse device)? 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. I was assuming that /dev/sysmouse would only exist if the system thought there was a mouse somewhere, but I'm not sure about that. ~~~ 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 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Problem with cordless mouse/Keyboard combo set
Stephanie Bridges <[EMAIL PROTECTED]> wrote: I had the same problem with the mouse (would occasionally move the cursor, never any clicks) until I accidentally got the receiver closer to the mouse. I now have the receiver about three inches away from the mouse. Works wonderfully well now. Thanks Stephanie, but unfortunately that didn't help here. I have moved my receiver so close to the mouse that its hard to not bump them, but the mouse still doesn't work. What I have noticed since I sent my original message, is that /dev/sysmouse exists even when only the non-working mouse is connected nto the system. Does this mean that FreeBSD /is/ detecting the mouse (and hence that I should be looking somewhere else than this list for the problem), or does that file simply always exist? -- Lennon Victor Cook "He who receives an idea from me receives without lessening, as he who lights his candle at mine receives light without darkening" - Thomas Jefferson ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
