Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 16 Dec 2017 12:48:20 +0000
From:      bugzilla-noreply@freebsd.org
To:        freebsd-usb@FreeBSD.org
Subject:   [Bug 224378] moused goes crazy when there are USB mouses and no PS2 mouses
Message-ID:  <bug-224378-17@https.bugs.freebsd.org/bugzilla/>

next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D224378

            Bug ID: 224378
           Summary: moused goes crazy when there are USB mouses and no PS2
                    mouses
           Product: Base System
           Version: 11.1-RELEASE
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Many People
          Priority: ---
         Component: usb
          Assignee: freebsd-usb@FreeBSD.org
          Reporter: vermaden@interia.pl

I have several 'mouse' type devices attached to FreeBSD box, a 'normal' mou=
se,
an air mouse, but I do not have any PS2 mouse. All of them work properly on
FreeBSD. There is only problem with /etc/rc.d/moused script that always rel=
ies
on PS2 mouse for PID and status.

Here are USB mouses:

# grep '^ums' /var/run/dmesg.boot=20
ums0 on uhub4
ums0: <AliTV Remote V1 Airmouse, class 0/0, rev 1.10/10.01, addr 4> on usbu=
s0
ums0: 5 buttons and [XYZ] coordinates ID=3D0
ums1 on uhub4
ums1: <AliTV Remote V1 Airmouse, class 0/0, rev 1.10/10.01, addr 4> on usbu=
s0
ums2 on uhub4
ums2: <AliTV Remote V1 Airmouse, class 0/0, rev 1.10/10.01, addr 4> on usbu=
s0
ums3 on uhub5
ums3: <Logitech Logitech BT Mini-Receiver, class 0/0, rev 2.00/49.00, addr =
8>
on usbus0
ums3: 14 buttons and [XYZT] coordinates ID=3D2
ums3: 8 buttons and [XYZT] coordinates ID=3D5



Here are PS2 mouses (none):

#  grep '^pms' /var/run/dmesg.boot



There are moused processes that were started at boot:

# ps ax | grep moused
  362  -  Is      0:00.37 /usr/sbin/moused -p /dev/ums0 -t auto -I
/var/run/moused.ums0.pid
  379  -  Is      0:00.00 /usr/sbin/moused -p /dev/ums1 -t auto -I
/var/run/moused.ums1.pid
  396  -  Is      0:00.00 /usr/sbin/moused -p /dev/ums2 -t auto -I
/var/run/moused.ums2.pid
  413  -  Is      0:00.00 /usr/sbin/moused -p /dev/ums3 -t auto -I
/var/run/moused.ums3.pid



But the moused script 'thinks' its not running:

# /etc/rc.d/moused status
moused is not running.


I can even 'start' it but it does not changes anything:

# /etc/rc.d/moused start
Starting default mousedmoused: unable to open /dev/psm0: No such file or
directory



But I can not stop it:

# /etc/rc.d/moused stop=20=20
moused not running? (check /var/run/moused.pid).

# ps ax|grep moused=20=20=20=20=20=20
  362  -  Is      0:00.37 /usr/sbin/moused -p /dev/ums0 -t auto -I
/var/run/moused.ums0.pid
  379  -  Is      0:00.00 /usr/sbin/moused -p /dev/ums1 -t auto -I
/var/run/moused.ums1.pid
  396  -  Is      0:00.00 /usr/sbin/moused -p /dev/ums2 -t auto -I
/var/run/moused.ums2.pid
  413  -  Is      0:00.00 /usr/sbin/moused -p /dev/ums3 -t auto -I
/var/run/moused.ums3.pid



Regards,
vermaden

--=20
You are receiving this mail because:
You are the assignee for the bug.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-224378-17>