Re: usb2 moused issue

On Monday 16 February 2009, Giorgos Keramidas wrote:
> On Mon, 16 Feb 2009 19:30:24 +0100, Hans Petter Selasky 
<hselasky_at_freebsd.org> wrote:
> >On Monday 16 February 2009, Giorgos Keramidas wrote:
> >>On Mon, 16 Feb 2009 17:52:56 +0100, Hans Petter Selasky wrote:
> >>> On Monday 16 February 2009, Giorgos Keramidas wrote:
> >>>> I just rebuild my kernel after flipping the switch to usb2 in my
> >>>> kernel config file:
> >>>>
> >>>>   [ dmesg output with hw.usb2.ums.debug=1 ]
> >>>>   Feb 16 16:19:00 kobe kernel: ugen4.2: <Microsoft> at usbus4
> >>>>   Feb 16 16:19:00 kobe kernel: ums0: <Microsoft Wireless Optical Mouse
> >>>> 3000 (Model 1056), class 0/0, rev 2.00/0.07, addr 2> on usbus4 Feb 16
> >>>> 16:19:00 kobe kernel: ums0: 5 buttons and [XYZ] coordinates Feb 16
> >>>> 16:19:00 kobe kernel: ums_attach:582: sc=0xc63c7000
> >>>
> >>> If you "cat /dev/ums0" while having the debugging on, do you see
> >>> anything?
> >>
> >> Hmm, there's a dmesg line saying that:
> >>
> >>   Feb 16 20:09:51 kobe kernel: Symlink: ums0 -> usb4.2.0.16
> >>
> >> but there is no ums0 symlink in /dev:
> >>
> >>   # ls -ld ums*
> >>   ls: ums*: No such file or directory
> >>   #
> >
> > Hi, The device is invisible. You should be able to cat it, if it's not
> > already opened.
>
> It was opened by moused, so I killed it.  There's no output when I
> attach and move the mouse, other than the following in syslog:
>

Hi,

What is "usbconfig" saying about your mouse?

How is your mouse connected to the PC? Directly or through a USB HUB?

--HPS