hey! so i’m new to qubes and just did a new install with the keyboard being ps2 and the mouse being usb. the installation went ok and at the end i think it rebooted and a window popped up for dom0 operation execution for the source sys-usb and the operation quabes inputmouse for dom0 so i did OK and the mouse works no problem.
then i did a shutdown and then when i powered back on and logged in the popup for the mouse does not appear so i tried rebooting and shutting down multiple times and the popup never appears again.
so then i did another new installation and at the end of the config i selected for the system to automatically remember/detect the mouse (i think that is what the description i checked was) and it said this option was not a preferred method but i tried to see if the mouse would work and it never did.
so i did another new installation same as the original and exact same thing happened again.
so how can i get the mouse to work after a new installation and then shutdown? Or how can i get the popup window to appear to select sys-usb for mouse?
ok thanks! it’ll take me a while to check, i have to shut down this computer and switch hard drive to the one with qubes installed since i only have one comuter to use…
so i got to the setting and it was on “always ask” but it still did not give me the popup window after logging in. so i changed the setting to “enable” and the mouse began to work instantly. i did a shutdown to see what happens after a new start and the mouse did not work after the shutdown again.
i tried changing the setting between “always ask” and “enbale” again to see if the mouse would begin to work but nothing now, it won’t work.
What version of Qubes OS did you install? And do you know if the ‘sys-usb’ Qube (VM) is starting on boot-up? Is there another USB port you can plug the mouse? Maybe a different mouse?
the version is R4.2.4. i tried using all of the usb ports and also a different mouse. i dont know if the vm is starting on boot-up but i will go and see if there is a setting i can find to know this, i didnt think to look for this since the mouse works after the reboot with the install but then doesn’t work after a shutdown after the initial reboot. i’ll update you in a bit after i log into qubes to check.
[user@sys-usb ~]$ lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU Tablet
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 003: ID 27c6:6594 Shenzhen Goodix Technology Co.,Ltd. Goodix USB2.0 MISC
Bus 004 Device 005: ID 04f2:b74f Chicony Electronics Co., Ltd Integrated Camera
Bus 004 Device 007: ID 8087:0033 Intel Corp. AX211 Bluetooth
Bus 004 Device 008: ID 0bda:5411 Realtek Semiconductor Corp. RTS5411 Hub
Bus 004 Device 009: ID 0c45:8033 Microdia AK820MAX
Bus 004 Device 010: ID 258a:0036 SINOWEALTH Wired Gaming Mouse
Bus 005 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 005 Device 003: ID 0bda:0411 Realtek Semiconductor Corp. Hub
[user@sys-usb ~]$
for me it’s:
keyboard - Bus 004 Device 009: ID 0c45:8033 Microdia AK820MAX
mouse - Bus 004 Device 010: ID 258a:0036 SINOWEALTH Wired Gaming Mouse
More…
lshw in dom0:
[r00t@dom0 ~]$ sudo lshw -short |grep -i "mouse\|keyboard"
/a input3 input AT Translated Set 2 keyboard
/b input49 input sys-usb: Glorious Model O Keyboard
/e input51 input sys-usb: KEYBOARD AK820MAX System Control
/f input52 input sys-usb: KEYBOARD AK820MAX
/10 input53 input sys-usb: KEYBOARD AK820MAX Keyboard
/11 input54 input sys-usb: KEYBOARD AK820MAX Mouse
/12 input55 input sys-usb: KEYBOARD AK820MAX Consumer Control
/13 input9 input ELAN0676:00 04F3:3195 Mouse
[r00t@dom0 ~]$
UDEV event in dom0 when connecting mouse:
[r00t@dom0 ~]$ udevadm monitor
monitor will print the received events for:
UDEV - the event which udev sends out after rule processing
KERNEL - the kernel uevent
KERNEL[44979.566436] add /devices/virtual/input/input49 (input)
KERNEL[44979.566494] add /devices/virtual/input/input49/event14 (input)
UDEV [44979.571113] add /devices/virtual/input/input49 (input)
UDEV [44979.680919] add /devices/virtual/input/input49/event14 (input)
KERNEL[44979.872271] add /devices/virtual/input/input50 (input)
KERNEL[44979.872319] add /devices/virtual/input/input50/mouse4 (input)
KERNEL[44979.872374] add /devices/virtual/input/input50/event16 (input)
UDEV [44979.873968] add /devices/virtual/input/input50 (input)
UDEV [44979.875260] add /devices/virtual/input/input50/mouse4 (input)
UDEV [44980.009350] add /devices/virtual/input/input50/event16 (input)
^C
[r00t@dom0 ~]$
i used the alt+F3 from before and opened the qubes manager and the sys-usb is empty instead of having a green dot so i think this means it is not on but i couldnt figure out how to manually start the qube with the keyboard so the only thing i know to do is to reinstall again and when the mouse is working ill see if there is a setting to make the qube auto start i think i saw this somewhere before in a setting. im thinking you are on to something here & i hope this is the fix, will update on how this goes.
is it possible to start the sys-usb qube from the dom0 terminal if i use the alt+f3/terminal?
what is the command i would use to start the qube?
so i did another new install and the mouse worked after the install auto reboot to i checked the sys-usb qube settings and the “start qube automaticaly on boot” has a check mark to enable this feature. i did a shutdown and then started the computer again and the same thing no mouse and when i checked the qubes manager the status is empty (no green dot). maybe theres a bug?
i thought maybe i could manually start the qube via the dom0 terminal but i dont know what command to enter.
thanks again for the help…
it seems like this may be a sys-usb qube issue because it is not starting after the initial shutdown. i’m trying to figure out what the command would be to manually start the sys-usb to see if that solves the problem but i’m not smart with knowing commands. the sys-usb has the box checked for starting qube automatically at boot and does start after the reboot during the installation but once the system is shutdown the qube does not auto start.
i will try your commands if i cannot start the qube manually but it takes me a lot of time to do these things because i only have 1 computer so i have to shutdown and change drives for the qubesos and the one i’m using now. thanks for helping me! i hope its as simple as having to just manually start the sys-usb manually if possible.
You should check logs for why your sys-usb is not starting.
I suspect that you’ve added something in Devices tab in qube setting that is not ready when sys-usb starts, hence it runs when installing because every device is running but refuse to start after reboot because one device isn’t ready to work yet.
the start command you provided worked! at least i can manually get the mouse working via the keyboard/terminal…
i didn’t add anything in devices to cause this, i did a new install with the mouse and keyboard connected and everything works during the installation process and after the computer reboots during the installation process the mouse works. i immediately did a shutdown each time after the installation was complete without doing anything else so everything configured should be the system defaults. the mouse is not working after the system is shutdown, when i power on the sys-usb does not get enabled and i checked and the setting is enabled to automatically start the qube when system is booted. i have installed the system many times now and the same thing happens each time and i’m not doing anything other than answering the quetions during the installation so i don’t think it is me doing anything after this many times of trying.
i would look at the logs to try and figure this out but i’m not smart with knowing what all that info is, i can enter a command if someone tells me what to do but not much more…
THANK YOU so much for helping me and giving me the start command!!! i will just use this method of getting the mouse to work for now and hope that the next release does not do this same thing for me. i’m just happy to have a workaround to get the mouse working…
i can get the mouse to work with the alt +F3/terminal method you taught me and the “qvm-start sys-usb” command that KitsuneNoBaka taught me.
this does not find out the cause of the problem but after many attemps/installations with the same result i’m happy with this workaround and hope that the issue (bug?) is fixed with the next release.
