Date: Tue, 17 Feb 2009 00:38:14 +0200 From: Giorgos Keramidas <keramida@ceid.upatras.gr> To: Hans Petter Selasky <hselasky@freebsd.org> Cc: freebsd-current@freebsd.org, Andrew Thompson <thompsa@freebsd.org> Subject: Re: usb2 moused issue (Microsoft Wireless Optical) Message-ID: <873aee0zzd.fsf@kobe.laptop> In-Reply-To: <874oyut5ze.fsf@kobe.laptop> (Giorgos Keramidas's message of "Mon, 16 Feb 2009 23:41:09 %2B0200") References: <87mycme9wc.fsf@kobe.laptop> <200902161930.25235.hselasky@freebsd.org> <87tz6u6u4d.fsf@kobe.laptop> <200902162212.37027.hselasky@freebsd.org> <87r61ynkrj.fsf@kobe.laptop> <874oyut5ze.fsf@kobe.laptop>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 16 Feb 2009 23:41:09 +0200, Giorgos Keramidas <keramida@ceid.upatras.gr> wrote: >>> Can you try the following patch: >>> http://perforce.freebsd.org/chv.cgi?CH=157814 >> >> This looks ok. I'll give it a run in a few minutes, thanks :-) > > A quick 'buildkernel' with -DNO_CLEAN and a reboot just finished. > > The patch doesn't seem to have changed anything, but I started a full > buildkernel without -DNO_CLEAN too. I'll report back in ~= 1 hour. No luck either. I finished a full buildkernel & reboot, but moused still has a bit of a problem reading movement events. Trying hd(1) on /dev/ums0 shows no data either as I move the mouse. The good news is that *other* USB mice I have work fine :-))) This one, for instance, works without any issues: kernel: ugen4.2: <Genius> at usbus4 kernel: ums0: <Genius NetScroll + Mini Traveler, class 0/0, rev 1.10/1.10, addr 2> on usbus4 kernel: ums0: 3 buttons and [XYZ] coordinates kernel: ums_attach:582: sc=0xc6336000 kernel: ums_attach:583: X 8/8 kernel: ums_attach:584: Y 16/8 kernel: ums_attach:585: Z 24/8 kernel: ums_attach:586: T 0/0 kernel: ums_attach:587: W 0/0 kernel: ums_attach:591: B1 0/1 kernel: ums_attach:591: B2 1/1 kernel: ums_attach:591: B3 2/1 kernel: ums_attach:593: size=4, id=0 kernel: Symlink: ums0 -> usb4.2.0.16 A third, tiny wired USB mouse (labelled 'Samsung' but reporting as 'Creative Labs' in dmesg) works fine too: kernel: ugen4.2: <Creative Labs> at usbus4 kernel: ums0: <Creative Labs product 0x0003, class 0/0, rev 1.10/0.00, addr 2> on usbus4 kernel: ums0: 5 buttons and [XYZ] coordinates kernel: ums_attach:582: sc=0xc65ba000 kernel: ums_attach:583: X 8/8 kernel: ums_attach:584: Y 16/8 kernel: ums_attach:585: Z 24/8 kernel: ums_attach:586: T 0/0 kernel: ums_attach:587: W 0/0 kernel: ums_attach:591: B1 0/1 kernel: ums_attach:591: B2 1/1 kernel: ums_attach:591: B3 2/1 kernel: ums_attach:591: B4 3/1 kernel: ums_attach:591: B5 4/1 kernel: ums_attach:593: size=4, id=0 kernel: Symlink: ums0 -> usb4.2.0.16 It's only my wireless USB mouse [Microsoft Wireless Optical Mouse 3000 (Model 1056)] that seems to have issues with the new USB stack. I just changed its battery, but that doesn't seem to have helped much either.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?873aee0zzd.fsf>