Bug 265823 - mouse doesn't work in freebsd 13, Hyper-V, Windows 10 Pro
Summary: mouse doesn't work in freebsd 13, Hyper-V, Windows 10 Pro
Status: New
Alias: None
Product: Base System
Classification: Unclassified
Component: conf (show other bugs)
Version: 13.1-RELEASE
Hardware: amd64 Any
: --- Affects Some People
Assignee: freebsd-bugs (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-08-13 20:10 UTC by Michael Faklis
Modified: 2022-11-08 16:29 UTC (History)
3 users (show)

See Also:


Attachments
xorg.conf.d, console log, Xorg.0.log (95.43 KB, text/plain)
2022-08-13 20:10 UTC, Michael Faklis
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Michael Faklis 2022-08-13 20:10:42 UTC
Created attachment 235888 [details]
xorg.conf.d, console log, Xorg.0.log

I am building a new FreeBSD 13.1 Workstation on a Windows 10 machine under Hyper-V.  I have been successful doing this with previous version of FreeBSD, back to releases 6, and previous releases of Windows back to XP Pro.
I have a couple problems with recognizing my mouse.  I am using a Logitech M217 wireless mouse, which I expect to be seen as a Hyper-V mouse.  
I expect the mouse to work in any Xorg window manager.   The mouse does work in Xorg under 12.3.  Also the mouse isn’t working on the console, outside of Xorg.    It should be able to select/cut/past because ‘allscreens_flags=”-m on”’ is in /etc/rc.conf.  It should work with text-based terminals and in xterm.  It doesn’t work with release 13.1 or release 12.3.
In /var/log/console.log, I’m troubled with the following lines;
•	FreeBSD13 kernel: [: mouse: unexpected operator
•	FreeBSD13 kernel: Starting default mousedmoused: unable to open /dev/psm0: No such file or directory
•	FreeBSD13 kernel: Starting default mousedmoused: unable to open /dev/cuau0: No such file or directory
In /var/log/Xorg.0.log;(off topic) The messages about Card0 confuse me because I never declared it.  It should be the Hyper-V video adapter
•	393.644] (**) |   |-->Device "Card0"
•	[   393.684] (EE) open /dev/dri/card0: No such file or directory
These are the messages about the mouse;
o	Line  22: [   393.644] (**) |-->Input Device "Mouse0"
o	Line  78: [   393.664] (WW) Hotplugging is on, devices using drivers 'kbd', 'mouse' or 'vmmouse' will be disabled.
o	Line  79: [   393.664] (WW) Disabling Mouse0
o	Line 193: [   394.394] (II) config/udev: Adding input device System mouse (/dev/input/event0)
o	Line 194: [   394.394] (**) System mouse: Applying InputClass "evdev pointer catchall"
o	Line 195: [   394.394] (**) System mouse: Applying InputClass "libinput pointer catchall"
o	Line 202: [   394.424] (II) Using input driver 'libinput' for 'System mouse'
o	Line 203: [   394.424] (**) System mouse: always reports core events
o	Line 206: [   394.454] (II) event0  - System mouse: is tagged by udev as: Mouse
o	Line 207: [   394.454] (II) event0  - System mouse: device is a pointer
o	Line 208: [   394.454] (II) event0  - System mouse: device removed
o	Line 210: [   394.454] (II) XINPUT: Adding extended input device "System mouse" (type: MOUSE, id 6)
o	Line 212: [   394.454] (**) System mouse: (accel) selected scheme none/0
o	Line 213: [   394.454] (**) System mouse: (accel) acceleration factor: 2.000
o	Line 214: [   394.454] (**) System mouse: (accel) acceleration threshold: 4
o	Line 215: [   394.454] (II) event0  - System mouse: is tagged by udev as: Mouse
o	Line 216: [   394.464] (II) event0  - System mouse: device is a pointer
o	Line 235: [   787.134] (II) event0  - System mouse: device removed

Below are the contents of /usr/local/share/X11/xorg.conf.d as text attachments;
Comment 1 Li-Wen Hsu freebsd_committer freebsd_triage 2022-11-08 04:47:03 UTC
(In reply to Michael Faklis from comment #0)
Are you using gen2 VM? If so, I think it's the same as bug 210175
Comment 2 Michael Faklis 2022-11-08 16:29:38 UTC
I know about the gen2 problem, so I've been using gen1.