NetBSD-Users archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: Re: Microsoft Wireless Optical Mouse 4000



At the time my Apple Mini PPC had a screen, I used a wireless
keyboard/mouse (from Logitech). It worked nice

###########
NetBSD 4.0 (GENERIC.MP) #0: Sun Dec 16 00:33:59 PST 2007
        
builds@wb30:/home/builds/ab/netbsd-4-0-RELEASE/macppc/200712160005Z-obj/home/builds/ab/netbsd-4-0-RELEASE/src/sys/arch/macppc/compile/GENERIC.MP
<snip>
uhub4 at uhub3 port 1
uhub4: NEC 2.0 hub, class 9/0, rev 2.00/1.00, addr 2
uhub4: single transaction translator
uhub4: 4 ports with 4 removable, self powered
uhidev0 at uhub0 port 1 configuration 1 interface 0
uhidev0: Apple Computer product 0x1000, rev 2.00/19.65, addr 2, iclass
3/1
ukbd0 at uhidev0
wskbd1 at ukbd0 mux 1
wskbd1: connecting to wsdisplay0
uhidev1 at uhub0 port 1 configuration 1 interface 1
uhidev1: Apple Computer product 0x1000, rev 2.00/19.65, addr 2, iclass
3/1
ums0 at uhidev1: 5 buttons
wsmouse0 at ums0 mux 0
uhidev2 at uhub4 port 4 configuration 1 interface 0
uhidev2: Logitech USB Receiver, rev 1.10/39.00, addr 3, iclass 3/1
ukbd1 at uhidev2
wskbd2 at ukbd1 mux 1
wskbd2: connecting to wsdisplay0
uhidev3 at uhub4 port 4 configuration 1 interface 1
uhidev3: Logitech USB Receiver, rev 1.10/39.00, addr 3, iclass 3/1
uhidev3: 4 report ids
ums1 at uhidev3 reportid 1: 16 buttons and Z dir.
wsmouse1 at ums1 mux 0
uhid0 at uhidev3 reportid 2: input=2, output=0, feature=0
uhid1 at uhidev3 reportid 3: input=1, output=0, feature=0
uhid2 at uhidev3 reportid 4: input=3, output=0, feature=0
###########

Regards,
        Jo

On Wed, Apr 02 2008 - 13:06, Gary Thorpe wrote:
> --- David Brownlee <abs%absd.org@localhost> wrote:
> 
> >     Anyone using one of these under NetBSD? It appears to be detected
> >     fine, but is non responsive (works fine under Windows)
> > 
> > uhidev0 at uhub1 port 2 configuration 1 interface 0
> > uhidev0: Microsoft Microsoft Wireless Optical MouseM-BM-. 1.00, rev 
> > 2.00/0.07, addr 2, iclass 3/1
> > uhidev0: 23 report ids
> > ums0 at uhidev0 reportid 17: 5 buttons and 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
> > 
> > 
> > -- 
> >                        David Brownlee -- abs%absd.org@localhost
> > 
> 
> I have a similar problem with the 1000 model (almost identical dmesg).
> A wired USB mouse works but doesn't identify as a UHID device. This
> seems to be an older problem from what I have seen in mailing list
> archives: has anyone had success with these UHID mice? Or, is the
> wireless feature the problem (is there a newer mouse protocol being
> used over USB)?
> 

Attachment: pgpsBKUSy7SBL.pgp
Description: PGP signature



Home | Main Index | Thread Index | Old Index