-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
On 08/01/2016 04:19 PM, Marek Marczykowski-Górecki wrote: > On Mon, Aug 01, 2016 at 10:05:24AM +0200, donoban wrote: >> This could cause hilarious scenarios, you go with your cool >> ultra secure computer to show a friend how nice is Qubes and you >> end being unable to boot your computer. I think initramfs should >> include most keyboard drivers as possible... > > If you like to modify hardware, it's good idea to disable host-only > mode in /etc/dracut.conf. This will include most of the drivers. > > Otherwise, I think it's actually a feature to have as little as > possible drivers in initramfs, as sys-usb nor sys-net are running > yet. > I only want to unlock my hard disk if I'm using a different keyboard. Adding most common keyboard/USB HID drivers should be enough. I will look at it. >> After recreating the initramfs I could unlock my hard disk, but >> when I went to the login screen, the keyboard didn't work! And >> the mouse didn't work too! Well, I have a Dell monitor with USB >> ports. I have both keyboard and mouse connected directly to the >> monitor. I disconnected the keyboard from the monitor and >> connected it directly to the computer and I could login into my >> xfce session. Few seconds after login, the mouse started to work, >> I disconnected the keyboard from the computer and reconnected to >> the monitor and it worked fine. What could be happening? Is >> sys-usb supposed to wait for do something after login? > > It may be that the input proxy tried to start too early - which > would be a bug in service dependencies. Check logs with > `journalctl` in sys-usb, search for lines related to udev and/or > input-proxy. > > Anyway, in such a case, simply reconnecting the device (even to the > same port) should fix the issue. > I will check when I reboot because now my log is full of messages like this: sys-usb kernel: holtek_mouse 0003:04D9:A067.000C: control queue full When it happens the keyboard gets stuck on some key and the mouse goes very slow (50% of cpu usage on sys-usb), I need to disconnect and reconnect the mouse. Maybe it's something related to the linux kernel, I will investigate it. >> Last problem (maybe should be posted in a new thread): > >> the main motivation for testing Qubes 3.2 for me was the USB >> passtrough because it would nice for me to connect a WiFi dongle >> or a Android smartphone with tethering. After install it (on my >> parent's house), I tested the WiFi dongle. It was attached fine, >> but on the dest VM it complained about unexpected errors and >> suggested a cable problem. > > USB passthrough is quite tricky and unfortunately some devices may > not work. We just use USBIP driver, which according to our tests > behaves the best from available options. You may have better luck > asking on [email protected], for help with USBIP driver. > Include lsusb -v output for that device. If you decide so, please > cc me. Ok, I will consider when I stabilize other things :) >> With the Android tethering it worked fine. > >> But now, when I try to attach it to a VM it says: "ERROR: Device >> attach failed: Invalid speed recieved" > > I guess that "Invalid speed received" is actually nothing received > at all. It's probably some problem at sys-usb side, check logs > there, including ~user/.xsession-errors. > >> It also says when doing any qvm-usb command: "Invalid 3-7 device >> desc in VM 'sys-usb'" > >> It's my Microsoft keyboard, but I think the error doesn't has >> relation with the other error. > > That's interesting. Can you post output of: > > qubesdb-multiread /qubes-usb-devices/3-7 > > in sys-usb? > Yes, it says: user@sys-usb:~$ qubesdb-multiread /qubes-usb-devices/3-12_3 /desc = 045e:00db Microsoft_Natural\xc2\xae_Ergonomic_Keyboard_4000 /usb-ver = 2 Regards. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJXn2I6AAoJEBQTENjj7QilW28P/ij8uEOVdmoeDRKfPAFdjkZ5 3zB4C2h53j97kiLTKhYyFQcxMKp/HnRSee7FQf+WVwuXTDcyfZ7JOTkSV+DNHNbz FjEkoiRPT5eN+3K0y1vPS6IjA/S4W0pb0qkRWqofiUWAvehGpkI/aZu3zcaSAyWx JUzjCmnQu164o45M8AOoLBq1LHYP6nF+7mYgx2hH+igj2C33zAmv5fY5236MLxRP fxYqQk0QFtzgJ1I4QC+UKNFTJAQU18u5yxnWiG9tV4axQoEWX83502JfDwmxM3wX JgPkOd6ky/K4qRe+fwTen0RForAEOKQVpNxqbNFjDSLVO3jPLMr9gfv0NQDqAfhF gLvuse5pFz+4JpCThkWyh5qIo3BOqYdDZRMbQGNxn708t4BiQGGU/b3mBRIS4o51 UQINxicwFYBGL50etyxdNJvspCX6objqKuNkIWmc4adeSDaAbc7xfdbZ8nwt6k/z LbGiKExy3RQ5tu8bxK440PYfgcR+wAYCsgjWR2PIXoTPvzLOzSPVRtrg0w8cV4Wc WPmmVF+wJjRe2H1sseiSjmyu5KrcfDmFH3Gidu1ibp4jB4QYiEyqfsuJpResWX2C DgsrjrWex7oPf9WXbFrP0GKAgt9m/EXzazNlTOkfckQJzhmr3aGfW3Y2so/Ax+BE hkGJ1kotmkaLI1lGkFfB =oZ3+ -----END PGP SIGNATURE----- -- 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/297d7403-0a55-46fe-c4b6-aa5c732647d3%40riseup.net. For more options, visit https://groups.google.com/d/optout.
