The last 3 successful boots took 10 tries. This is a Toshiba laptop (satellite). It has run Windows 8 & 10. Debian 8 & 9, Qubes-OS v3.2, v4.0 rc1. v4.0 rc two also had intermittent keyboard support. v4.0rc3 is a little more predictable, 2 out of 3 failed boots.
Reading forum messages, suggests this might be some kind of race on who gets control of the USB controller first. I looked in /etc/qubes-rpc/policy/InputKeyboard and it contains: $anyvm $anyvm deny OK, maybe that is not valuable. One message said that the USB keyboard and mouse could be hidden during boot so it would be available for dom0. In order to do that, it seems I should open a terminal in USBvm and see what ports are there and what is connected. So I clicked on applications, scrolled down to USBvm | terminal and selected it. Nothing happened. I opened xl top to see all vms. dom0 was there and the net family but they were all blocked probably because my network is down; I don't have my AP with me. So I went back and tried to start USBvm. It shows up in xl top as paused. After about 1 min, it disappear. So I closed all vms and tried to start USBvm. I got the same result. I can't tell what is going on. What might be stopping USBvm from running? When it is running, I believe I can use lsusb to see what is connected. So I can plug USB sticks into the available ports to see what the system calls those ports. I expect that what is left over is the keyboard and mouse internal ports. I would appreciate any information the help correct my understanding and solution method. Ray -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/761da9f3-5836-4932-91b3-fda1f95e12f9%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
