Closed probonopd closed 3 years ago
On helloSystem we have:
FreeBSD% ps ax | grep moused
743 - Ss 0:00,66 /usr/sbin/moused -p /dev/ums0 -t auto -I /var/run/moused.ums0.pid
On airyx, moused
seems not to be running and trying to start it results in moused: unable to open /dev/psm0: no such file or directory
.
Not sure if related.
Possibly related:
https://github.com/helloSystem/ISO/issues/4#issuecomment-787062758
Especially the part on unionfs and ums.
Thanks - that looks helpful. I hacked around it for now by adding ums.ko
in loader.conf
. You can probably get a mouse working from the terminal/console by just doing sudo kldload /boot/kernel/ums.ko
- it worked for me, anyway. Moused was running on my Inspiron but it has a PS2 trackpad rather than USB. I'm sure that's why it worked out of the box.
Will see what I can do to fix those.
I am also experiencing an issue with the mouse on 0.3.0pre. Proxmox 7 (Qemu/KVM) provides a USB Tablet device for the mouse. It also apparently has some sort of fallback mouse (PS2?) that works erratically. It doesn't sync up properly with the host mouse. I can make it work, but it is distracting.
I tried the ums.ko workaround above, but that doesn't seem to work in my situation.
Is moused
running or can you start it after loading ums.ko
?
I tried booting with the QEMU tablet disabled and then enabled it after loading ums.ko dmesg then shows: ugen0.2: \<QEMU QEMU USB Tablet> at usbus0
"ps ax | grep moused" shows: /usr/sbin/moused -p /dev/psm0 -t auto -I /var/run/moused.psm0.pid
No improvement in the erratic mouse behavior.
If Proxmox presents Spice consoles via virt-viewer or remote-viewer like ovirt or local libvirt does, this is probably a virt-viewer-ism. Console mouse is frequently unstable and erratic until the guest spice agent is started. No idea if a spice-vdagent package exists for whatever the underlying BSD is, here. You might also try switching the console type in proxmox, maybe VNC is better.
It's worth a shot. I tried fiddling around with the Display device config. I found it set to "Default" and the only viewer available was noVNC. I changed it to Standard VGA and still only noVNC available. Then I changed it to Spice (qxl) and the available viewers were noVNC and SPICE. However, when I select the SPICE viewer option, it downloads a text file named pve-spice.vv containing what appears to be connection config info for virt-viewer. Alas, I have no virt-viewer installed on the Windows 10 VM that I am browsing Proxmox with. Anyway, no change in mouse behavior under these various scenarios.
If Proxmox presents Spice consoles via virt-viewer or remote-viewer like ovirt or local libvirt does, this is probably a virt-viewer-ism.
Just for clarification, I encounter this issue on bare metal. No virtualization. Mouse does not work. Tested on 2 different machines, one with a USB mouse and one with an ELAN Touchpad.
What I think I understand from this thread is that:
I'll upload the new ISO later today with ums support - see if that helps. Also, @probonopd it has your region detection stuff with an extension of my own. Maybe it's useful? https://github.com/mszoek/ISO/blob/d84b54b759d782332048cf0ea1f5d250b28b82fa/overlays/uzip/localize/files/usr/sbin/localize#L98
Confirm that this is fixed. Thanks!
Mouse does not work. Tested on 2 different machine, one with a USB mouse and one with an ELAN Touchpad.
Re-plugging the USB mouse does not make it work.
dmesg
correctly shows the USB mouse, so it is detected on the USB bus.