Re: USB mouse stops working after upgrading to FreeBSD 15.0

"Jin Guojun[VFF]" <[email protected]>
Newsgroups gmane.os.freebsd.questions,gmane.os.freebsd.devel.x11
Message-ID <[email protected]>
It is not very clear if the issue is in the X11 or hms driver because 
Compx 2.4G Receiver works well in 13-R, 14-R and 16-R, but 15-R.

Since the problem reported in Xorg.0.log (see below), so added X11 folks 
for further investigation.

Thanks Hrant for pointing out a kludge solution to add 
EVDEV_RCPT_SYSMOUSE bit (1) in evdev_rcpt_mask (kern.evdev.rcpt_mask 12=>13)

USB wireless moused works in 15-R not but fully functioning --

     the roller runs opposite direction: rolling up makes page going 
down, rolling down makes page moving up.

Here is 15-R X11 mouse information (failure) vs. 14-R (successful)

----- Begin 15-R Xorg.0.log mouse section -------

1471:[   297.623] (II) config/udev: Adding input device System mouse 
(/dev/input/event1)
1472:[   297.624] (**) System mouse: Applying InputClass "libinput 
pointer catchall"
1473:[   297.624] (II) Using input driver 'libinput' for 'System mouse'
1474:[   297.624] (**) System mouse: always reports core events
1476:[   297.625] (II) event1  - System mouse: is tagged by udev as: Mouse
1477:[   297.627] (II) event1  - System mouse: device is a pointer
1478:[   297.628] (II) event1  - System mouse: device removed
1479:[   297.628] (II) libinput: System mouse: Step value 0 was 
provided, libinput Fallback acceleration function is used.
1480:[   297.628] (II) libinput: System mouse: Step value 0 was 
provided, libinput Fallback acceleration function is used.
1481:[   297.628] (II) libinput: System mouse: Step value 0 was 
provided, libinput Fallback acceleration function is used.
1483:[   297.628] (II) XINPUT: Adding extended input device "System 
mouse" (type: MOUSE, id 7)
1485:[   297.628] (**) System mouse: (accel) selected scheme none/0
1486:[   297.628] (**) System mouse: (accel) acceleration factor: 2.000
1487:[   297.628] (**) System mouse: (accel) acceleration threshold: 4
1488:[   297.630] (II) event1  - System mouse: is tagged by udev as: Mouse
1489:[   297.632] (II) event1  - System mouse: device is a pointer
1527:[   297.655] (II) event5  - ETPS/2 Elantech Touchpad: is tagged by 
udev as: Mouse Touchpad
1539:[   297.679] (II) event5  - ETPS/2 Elantech Touchpad: is tagged by 
udev as: Mouse Touchpad
1555:[   297.704] (II) config/udev: Adding input device Compx 2.4G 
Receiver Mouse (/dev/input/event7)
1556:[   297.704] (**) Compx 2.4G Receiver Mouse: Applying InputClass 
"libinput pointer catchall"
1557:[   297.704] (II) Using input driver 'libinput' for 'Compx 2.4G 
Receiver Mouse'
1558:[   297.704] (**) Compx 2.4G Receiver Mouse: always reports core events
1560:[   297.706] (II) event7  - Compx 2.4G Receiver Mouse: is tagged by 
udev as: Mouse
1561:[   297.707] (II) event7  - Compx 2.4G Receiver Mouse: device is a 
pointer
1562:[   297.709] (II) event7  - Compx 2.4G Receiver Mouse: device removed
1563:[   297.709] (II) libinput: Compx 2.4G Receiver Mouse: Step value 0 
was provided, libinput Fallback acceleration function is used.
1564:[   297.709] (II) libinput: Compx 2.4G Receiver Mouse: Step value 0 
was provided, libinput Fallback acceleration function is used.
1565:[   297.709] (II) libinput: Compx 2.4G Receiver Mouse: Step value 0 
was provided, libinput Fallback acceleration function is used.
1567:[   297.709] (II) XINPUT: Adding extended input device "Compx 2.4G 
Receiver Mouse" (type: MOUSE, id 12)
1569:[   297.709] (**) Compx 2.4G Receiver Mouse: (accel) selected 
scheme none/0
1570:[   297.709] (**) Compx 2.4G Receiver Mouse: (accel) acceleration 
factor: 2.000
1571:[   297.709] (**) Compx 2.4G Receiver Mouse: (accel) acceleration 
threshold: 4
1572:[   297.711] (II) event7  - Compx 2.4G Receiver Mouse: not tagged 
as supported input device
1575:[   297.711] (EE) Couldn't init device "Compx 2.4G Receiver Mouse"
----- End 15-R Xorg.0.log mouse section -------

----- Begin 14-R Xorg.0.log mouse section -------

19:[    29.368] (**) |-->Input Device "Mouse0"
43:[    29.372] (WW) Hotplugging is on, devices using drivers 'kbd', 
'mouse' or 'vmmouse' will be disabled.
44:[    29.372] (WW) Disabling Mouse0
129:[    30.571] (==) NVIDIA(0): Silken mouse enabled
190:[    30.756] (II) config/udev: Adding input device System mouse 
(/dev/input/event1)
191:[    30.756] (**) System mouse: Applying InputClass "libinput 
pointer catchall"
192:[    30.756] (II) Using input driver 'libinput' for 'System mouse'
193:[    30.756] (**) System mouse: always reports core events
195:[    30.757] (II) event1  - System mouse: is tagged by udev as: Mouse
196:[    30.757] (II) event1  - System mouse: device is a pointer
197:[    30.758] (II) event1  - System mouse: device removed
198:[    30.758] (II) libinput: System mouse: Step value 0 was provided, 
libinput Fallback acceleration function is used.
199:[    30.758] (II) libinput: System mouse: Step value 0 was provided, 
libinput Fallback acceleration function is used.
200:[    30.758] (II) libinput: System mouse: Step value 0 was provided, 
libinput Fallback acceleration function is used.
202:[    30.758] (II) XINPUT: Adding extended input device "System 
mouse" (type: MOUSE, id 7)
204:[    30.758] (**) System mouse: (accel) selected scheme none/0
205:[    30.758] (**) System mouse: (accel) acceleration factor: 2.000
206:[    30.758] (**) System mouse: (accel) acceleration threshold: 4
207:[    30.759] (II) event1  - System mouse: is tagged by udev as: Mouse
208:[    30.759] (II) event1  - System mouse: device is a pointer
284:[    30.784] (II) event7  - Compx 2.4G Receiver, class 0/0, rev 
1.10/6.23, addr 4: is tagged by udev as: Mouse
291:[    30.785] (II) XINPUT: Adding extended input device "Compx 2.4G 
Receiver" (type: MOUSE, id 13)
296:[    30.786] (II) event7  - Compx 2.4G Receiver, class 0/0, rev 
1.10/6.23, addr 4: is tagged by udev as: Mouse
----- End 14-R Xorg.0.log mouse section -------

>> On 2/19/26 20:10, Hrant Dadivanyan wrote:
>>>
>>> Hi, this sounds close to my experience with similar mouse.
>>> Did you try to play with kern.evdev.rcpt_mask sysctl?
>>>
>>> Hrant
>>>
>>> On 2/20/26 00:22, Jin Guojun[VFF] wrote:
>>>> On 2/18/26 02:39, Tijl Coosemans wrote:
>>>>> On Sun, 15 Feb 2026 21:04:41 -0800 Jin Guojun[VFF] wrote:
>>>>>> I have a Lenovo G505S laptop was running 14.3. After upgrade to 
>>>>>> 15.0,
>>>>>> the USB mouse stops working.
>>>>>>
>>>>>> The touchpad still works. Below are mouse related information:
>>>>>>
>>>>>> # ps uxagww | grep mouse
>>>>>> root  4767   0.0  0.0    14520   2824  -  Is   19:45  0:00.30
>>>>>> /usr/sbin/moused -p /dev/input/event7 -t evdev -I /var/run/ 
>>>>>> moused.event7.pid
>>>>>> root  5046   0.0  0.0    14520   2824  -  Ss   19:45  0:01.25
>>>>>> /usr/sbin/moused -p /dev/psm0
>>>>>>
>>>>>> # moused -i all
>>>>>> /dev/input/event7 evdev mouse Compx 2.4G Receiver Mouse
>>>>>> /dev/input/event5 evdev touchpad ETPS/2 Elantech Touchpad
>>>>>>
>>>>>> # cat /dev/input/event7
>>>>>>
>>>>>> we can see output to the screen (garbage code) when operating USB 
>>>>>> mouse
>>>>>> (click buttons or move mouse), but the cursor does not move.
>>>>>>
>>>>>> What additional configuration is required for making USB mouse to 
>>>>>> work
>>>>>> in 15.0-R?
>>>>> In FreeBSD 15 there's a new USB HID driver and you're supposed to use
>>>>> hkbd and hms now instead of ukbd and ums.  So if you have ums in your
>>>>> kernel config or are loading the module from /boot/loader.conf, 
>>>>> replace
>>>>> that with hms.
>>>>
>>>> It looks like this is a defect in 15-R between the hms and X11.
>>>>
>>>> I further installed Current snapshot and 16 snapshot; 15 snapshot 
>>>> has the same issue as 15.0-R, but 16.0 snapshot work flawless.
>>>>
>>>> Both has the same input/event[6-9] for 2.4G Receiver, and moused in 
>>>> both snapshots use the same parameters.
>>>>
>>>> hms.ko is loaded by default. The wireless mouse works on the text 
>>>> console in 15.0-R, but when Xwindow starts, the mouse no longer works.
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.