Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 16 Feb 2009 21:48:18 +0200
From:      Giorgos Keramidas <keramida@freebsd.org>
To:        Hans Petter Selasky <hselasky@freebsd.org>
Cc:        freebsd-current@freebsd.org, Andrew Thompson <thompsa@freebsd.org>
Subject:   Re: usb2 moused issue
Message-ID:  <87tz6u6u4d.fsf@kobe.laptop>
In-Reply-To: <200902161930.25235.hselasky@freebsd.org> (Hans Petter Selasky's message of "Mon, 16 Feb 2009 19:30:24 %2B0100")
References:  <87mycme9wc.fsf@kobe.laptop> <200902161752.56998.hselasky@freebsd.org> <87wsbqmeq4.fsf@kobe.laptop> <200902161930.25235.hselasky@freebsd.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 16 Feb 2009 19:30:24 +0100, Hans Petter Selasky <hselasky@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:

Feb 16 21:37:45 kobe kernel: ugen4.2: <Microsoft> at usbus4
Feb 16 21:37:45 kobe kernel: ums0: <Microsoft Wireless Optical Mouse 3000 (Model 1056), class 0/0, rev 2.00/0.07, addr 2> on usbus4
Feb 16 21:37:45 kobe kernel: ums0: 5 buttons and [XYZ] coordinates
Feb 16 21:37:45 kobe kernel: ums_attach:582: sc=0xc63cd800
Feb 16 21:37:45 kobe kernel: ums_attach:583: X  48/8
Feb 16 21:37:45 kobe kernel: ums_attach:584: Y  56/8
Feb 16 21:37:45 kobe kernel: ums_attach:585: Z  64/8
Feb 16 21:37:45 kobe kernel: ums_attach:586: T  0/0
Feb 16 21:37:45 kobe kernel: ums_attach:587: W  0/0
Feb 16 21:37:45 kobe kernel: ums_attach:591: B1 40/1
Feb 16 21:37:45 kobe kernel: ums_attach:591: B2 41/1
Feb 16 21:37:45 kobe kernel: ums_attach:591: B3 42/1
Feb 16 21:37:45 kobe kernel: ums_attach:591: B4 43/1
Feb 16 21:37:45 kobe kernel: ums_attach:591: B5 44/1
Feb 16 21:37:45 kobe kernel: ums_attach:593: size=2, id=19
Feb 16 21:37:45 kobe kernel: Symlink: ums0 -> usb4.2.0.16

When I kill the moused instance that is launched on attach by devd,
start a `cat /dev/ums0' command and move the mouse, click a few buttons,
etc. there is no output at all.




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?87tz6u6u4d.fsf>