[Bug 265823] mouse doesn't work in freebsd 13, Hyper-V, Windows 10 Pro
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 265823] mouse doesn't work in freebsd 13, Hyper-V, Windows 10 Pro"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 265823] mouse doesn't work in freebsd 13, Hyper-V, Windows 10 Pro"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 265823] mouse doesn't work in freebsd 13, Hyper-V, Windows 10 Pro"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 265823] mouse doesn't work in freebsd 13, Hyper-V, Windows 10 Pro"
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Sat, 13 Aug 2022 20:10:42 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=265823
Bug ID: 265823
Summary: mouse doesn't work in freebsd 13, Hyper-V, Windows 10
Pro
Product: Base System
Version: 13.1-RELEASE
Hardware: amd64
OS: Any
Status: New
Severity: Affects Some People
Priority: ---
Component: conf
Assignee: bugs@FreeBSD.org
Reporter: MFaklis@ACM.org
Created attachment 235888
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=235888&action=edit
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;
--
You are receiving this mail because:
You are the assignee for the bug.