Page 1 of 1

Mouse doesn't work-MX23XFCE on BHYVE hypervisor

Posted: Thu Jan 25, 2024 9:46 am
by Penobscot
I have been trying to install MX23XFCE on a BHYVE hypervisor. I've had a MX21 VM running on it for a couple of years. The mouse does not work. I've tried also tried AHS with the same results. Appreciate any assistance.

Code: Select all

System:
  Kernel: 6.1.0-17-amd64 [6.1.69-1] arch: x86_64 bits: 64 compiler: gcc v: 12.2.0
    parameters: BOOT_IMAGE=/antiX/vmlinuz quiet splasht nosplash checkmd5
  Desktop: Xfce v: 4.18.1 tk: Gtk v: 3.24.36 info: xfce4-panel wm: xfwm v: 4.18.0 vt: 7
    dm: LightDM v: 1.26.0 Distro: MX-23.2_x64 Libretto January 21  2024 base: Debian GNU/Linux 12
    (bookworm)
Machine:
  Type: Unknown Mobo: FreeBSD model: BHYVE v: 1.0 serial: <superuser required> UEFI: BHYVE v: 13.0
    date: 11/10/2020
CPU:
  Info: model: Intel Xeon E5-2620 v2 bits: 64 type: MCP arch: Ivy Bridge level: v2 built: 2012-15
    process: Intel 22nm family: 6 model-id: 0x3E (62) stepping: 4 microcode: N/A
  Topology: cpus: 1x cores: 2 smt: <unsupported> cache: L1: 128 KiB desc: d-2x32 KiB; i-2x32 KiB
    L2: 512 KiB desc: 2x256 KiB L3: 15 MiB desc: 1x15 MiB
  Speed (MHz): avg: 2098 min/max: N/A cores: 1: 2098 2: 2098 bogomips: 8393
  Flags: avx ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3
  Vulnerabilities:
  Type: gather_data_sampling status: Not affected
  Type: itlb_multihit status: KVM: VMX unsupported
  Type: l1tf mitigation: PTE Inversion
  Type: mds mitigation: Clear CPU buffers; SMT Host state unknown
  Type: meltdown mitigation: PTI
  Type: mmio_stale_data status: Unknown: No mitigations
  Type: retbleed status: Not affected
  Type: spec_rstack_overflow status: Not affected
  Type: spec_store_bypass status: Vulnerable
  Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization
  Type: spectre_v2 mitigation: Retpolines, STIBP: disabled, RSB filling, PBRSB-eIBRS: Not
    affected
  Type: srbds status: Not affected
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: driver: N/A bus-ID: 00:1d.0 chip-ID: fb5d:40fb class-ID: 0300
  Display: x11 server: X.Org v: 1.21.1.7 compositor: xfwm v: 4.18.0 driver: X: loaded: N/A
    unloaded: fbdev dri: swrast gpu: N/A display-ID: :0.0 screens: 1
  Screen-1: 0 s-res: 1024x768 s-dpi: 96 s-size: 271x203mm (10.67x7.99") s-diag: 339mm (13.33")
  Monitor-1: default res: 1024x768 hz: 76 size: N/A modes: N/A
  API: OpenGL v: 4.5 Mesa 22.3.6 renderer: llvmpipe (LLVM 15.0.6 256 bits) direct-render: Yes
Audio:
  Message: No device data found.
  API: ALSA v: k6.1.0-17-amd64 status: kernel-api tools: alsamixer,amixer
  Server-1: PipeWire v: 1.0.0 status: active with: 1: pipewire-pulse status: active
    2: wireplumber status: active 3: pipewire-alsa type: plugin 4: pw-jack type: plugin
    tools: pactl,pw-cat,pw-cli,wpctl
Network:
  Device-1: Red Hat Virtio network driver: virtio-pci v: 1 modules: virtio_pci port: 2080
    bus-ID: 00:05.0 chip-ID: 1af4:1000 class-ID: 0200
  IF: eth0 state: up speed: -1 duplex: unknown mac: <filter>
Drives:
  Local Storage: total: 40 GiB used: 0 KiB (0.0%)
  ID-1: /dev/vda maj-min: 254:0 model: N/A size: 40 GiB block-size: physical: 65536 B
    logical: 512 B type: N/A serial: N/A scheme: GPT
  SMART Message: Unknown smartctl error. Unable to generate data.
Partition:
  Message: No partition data found.
Swap:
  Alert: No swap data was found.
Sensors:
  Src: lm-sensors+/sys Message: No sensor data found using /sys/class/hwmon or lm-sensors.
Repos:
  Packages: pm: dpkg pkgs: 2047 libs: 1045 tools: apt,apt-get,aptitude,nala,synaptic pm: rpm
    pkgs: 0
  No active apt repos in: /etc/apt/sources.list
  Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list
    1: deb http://deb.debian.org/debian bookworm-updates main contrib non-free non-free-firmware
  Active apt repos in: /etc/apt/sources.list.d/debian.list
    1: deb http://deb.debian.org/debian bookworm main contrib non-free non-free-firmware
    2: deb http://security.debian.org/debian-security bookworm-security main contrib non-free non-free-firmware
  Active apt repos in: /etc/apt/sources.list.d/mx.list
    1: deb https://mxrepo.com/mx/repo/ bookworm main non-free
Info:
  Processes: 265 Uptime: 1m wakeups: 15 Memory: 3.82 GiB used: 914.3 MiB (23.4%) Init: SysVinit
  v: 3.06 runlevel: 5 default: graphical tool: systemctl Compilers: gcc: 12.2.0 alt: 12
  Client: shell wrapper v: 5.2.15-release inxi: 3.3.26
Boot Mode: UEFI
Video Tweaks:
No kernel video driver

Re: Mouse doesn't work-MX23XFCE on BHYVE hypervisor

Posted: Thu Jan 25, 2024 10:19 am
by Charlie Brown
Penobscot wrote: Thu Jan 25, 2024 9:46 am... I've had a MX21 VM running on it for a couple of years...
If you like you can turn back to the good old Synaptics driver (like I did), at least to try:

Code: Select all

sudo mv /etc/X11/xorg.conf.d/30-touchpad-libinput.conf{,.old} ; sudo apt update ; sudo apt install xserver-xorg-input-synaptics -y
Reboot.

___________

To revert back for whatever reason:

Code: Select all

sudo mv /etc/X11/xorg.conf.d/30-touchpad-libinput.conf.old /etc/X11/xorg.conf.d/30-touchpad-libinput.conf ; sudo apt remove xserver-xorg-input-synaptics -y

Re: Mouse doesn't work-MX23XFCE on BHYVE hypervisor

Posted: Thu Jan 25, 2024 7:50 pm
by Penobscot
No joy, but thanks.

Re: Mouse doesn't work-MX23XFCE on BHYVE hypervisor

Posted: Fri Jan 26, 2024 8:21 am
by Charlie Brown
Then, install the most recent Liquorix kernel, either from "MX Package Installer" (6.6.x for today) or this (which I'm on at the moment):

Code: Select all

mkdir Liquorix ; cd Liquorix ; wget https://liquorix.net/debian/pool/main/l/linux-liquorix/linux-headers-6.7.2-1-liquorix-amd64_6.7-2.1~bookworm_amd64.deb https://liquorix.net/debian/pool/main/l/linux-liquorix/linux-image-6.7.2-1-liquorix-amd64_6.7-2.1~bookworm_amd64.deb ; sudo apt install ./*.deb ; sudo update-grub ; cd .. ; rm -rf Liquorix ; echo 'blacklist ntfs3' | sudo tee /etc/modprobe.d/blacklist-ntfs3.conf
Reboot.

(Though it may be a bit difficult without the mouse working)

P.S. The last part of the command is just to prevent a known issue about ntfs, in case you wonder.