Date: Tue, 18 Apr 2023 23:25:34 +0000 From: bugzilla-noreply@freebsd.org To: usb@FreeBSD.org Subject: [Bug 270883] Enable mouse on Hyper-V 2022 Gen2 VM Message-ID: <bug-270883-19105-txD7lJbU0l@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-270883-19105@https.bugs.freebsd.org/bugzilla/> References: <bug-270883-19105@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D270883 --- Comment #3 from fgorter <fgorter@gmail.com> --- Same behavior is not entirely unexpected, to be honest. Just-in-case, what happens if you remove dbus_enable from rc.conf as well? I've experienced something roughly similar some years ago with some recently released (2014/2015) Xeon CPUs. Executing a normal reboot from console (on = bare metal), would lead to the machine to shutdown normally (somewhat...) but not actually boot after BIOS POST. It required a hard reset -- press and hold p= ower button -- to start correctly again. Recalling from memory, I believe a switch in /boot/device.hints was require= d. I forget exactly which, but I think it was to one of the hint.atrtc* knobs, to deal with some (unclean) ACPI state quirks. What is the make/model of your hardware? Motherboard / CPU combo. If this is a AMD Ryzen based system, not that "hw.vmm.amdvi.enable=3D1" sho= uld probably be present in /boot/loader.conf -- default FreeBSD install ships w= ith this knob disabled. With it disabled does allow a normal install, but with = some more advanced features switched off. Please also double check the system BIOS for any USB-specific (legacy) switches. --=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-270883-19105-txD7lJbU0l>