USB Keyboard not picked up

[gnod...@gmail.com]

Hey,

as soon as I leave the GRUB-menu, my (USB) keyboard powers off, and I can't enter my decrypt. password for the HDD. Is this a common issue?
I tried multiple keyboards - doesn't work.
I'm using Qubes 3.1rc1, CPU: Intel Skylake i7-6700k, Mainboard: MSI Gaming M5.
Haven't had any issues during the install, but now I can't login.

Any ideas?

[Marek Marczykowski-Górecki]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Did you get into firstboot (where you select which VMs you want to
create), or not even there?

- --
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQEcBAEBCAAGBQJWeFHbAAoJENuP0xzK19csuvsH/iSyzRhsOHZqnORrqv+bx2hQ
NvcYFzf07PWAc7fRWSyOZuuUEA0uZPiv2fSELyhOr8eOy7S/A0jFr+q9RVD5+099
Q/wt9NPPDeGAYLtO4Crna9s+HbcqGWrJzEDaWSfKy4qV2quco1sSfMIFQ9/f0Xym
Db3NOfeAWxwhg7HL1W8aROakf75daf1jxVwBSZ9rKLnMLozsiV30dhMfpzEOTTjz
5SpNWaZGITRB+npZKF3dgZ8rFvwdAy8SMSnbhGVg3bsBRmHrN4yfDJtqmDk2cb3P
xmUST/7r5BgqfbN+BShZ9C4HMFtDoUZm1nbOKGNZS2OcPjo6eTff5SMpdpjBMAA=
=I1RQ
-----END PGP SIGNATURE-----

[gnod...@gmail.com]

Thanks for your answer!

No, as soon as I edit the option to fit in the command so that my Skylake GPU is supported ('i915.preliminary_hw_support=1') and I boot, my keyboard turns black. If I leave out this option, the same thing happens, it's just in text mode then. As said, I tried multiple ones, but it doesn't seen to work.

Essentially, the screen, where I'm promted to enter the password to decrypt my hdd doesn't work with my usb keyboard.

Should I post some logs? And if so, what and how?

[Eric Shelton]

On Monday, December 21, 2015 at 2:24:18 PM UTC-5, Marek Marczykowski-Górecki wrote:

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On Mon, Dec 21, 2015 at 10:13:24AM -0800, gnod...@gmail.com wrote:
> Hey,
>
> as soon as I leave the GRUB-menu, my (USB) keyboard powers off, and I can't enter my decrypt. password for the HDD. Is this a common issue?
> I tried multiple keyboards - doesn't work.
> I'm using Qubes 3.1rc1, CPU: Intel Skylake i7-6700k, Mainboard: MSI Gaming M5.
> Haven't had any issues during the install, but now I can't login.
>
> Any ideas?

Did you get into firstboot (where you select which VMs you want to
create), or not even there?

I have heard the same issue with USB keyboard reported by a different Skylake user.  For what it is worth, the Skylake systems generally only have USB 3 ports, whereas older systems usually have a mix of USB 2 and USB 3 ports.

This issue seems to extend beyond just keyboards/input devices.  As I noted previously (https://groups.google.com/d/msg/qubes-users/lxo1nkw3w0U/9aYfMXGhBwAJ), I saw similar USB-related problems on R3.1-rc1.  On a Haswell system, I was able to successfully run through the installer (which was on a USB flash drive) to install to an external USB drive (SATA drive attached via USB-SATA adapater).  On firstboot, Grub would do its thing, but an LED on the external drive that shows whether the USB interface is active would turn off as soon as the kernel booted.  The messages output by the kernel would show that the USB controller was detected, but did not show sda (the USB drive) being detected.  On Qubes R2, I had no problem installing to, and running from, an external USB drive on the same system.

https://groups.google.com/d/msg/qubes-users/lxo1nkw3w0U/yxlMWXmUBwAJ has some logs for a problem booting from a USB flash drive that sound similar, although that user may have had some other problems going on with the Qubes ISO he downloaded...

My hunch was that dracut is not putting something into initramfs that is needed to make devices plugged into the USB ports work, but I was too busy dealing with other things to investigate.

Eric

[Frank]

On 21.12..2015, at 21:16, Eric Shelton knockknock-at-gmail.com |qubes-mailing-list/Example Allow| <8211c...@sneakemail.com> wrote:

On Monday, December 21, 2015 at 2:24:18 PM UTC-5, Marek Marczykowski-Górecki wrote:

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On Mon, Dec 21, 2015 at 10:13:24AM -0800, gnod...@gmail.com wrote:
> Hey,
>
> as soon as I leave the GRUB-menu, my (USB) keyboard powers off, and I can't enter my decrypt. password for the HDD. Is this a common issue?
> I tried multiple keyboards - doesn't work.
> I'm using Qubes 3.1rc1, CPU: Intel Skylake i7-6700k, Mainboard: MSI Gaming M5.
> Haven't had any issues during the install, but now I can't login.
>
> Any ideas?

I installed my Qubes 3.1rc1 system (a Lenovo ThinkPad W530) with sys-usb VM and can charge my phone on the USB ports assigned to it only if and when the sys-usb VM is started... I'll give it a try and see what happens during the boot phase...

Did you get into firstboot (where you select which VMs you want to
create), or not even there?

I have heard the same issue with USB keyboard reported by a different Skylake user.  For what it is worth, the Skylake systems generally only have USB 3 ports, whereas older systems usually have a mix of USB 2 and USB 3 ports.

This issue seems to extend beyond just keyboards/input devices.  As I noted previously (https://groups.google.com/d/msg/qubes-users/lxo1nkw3w0U/9aYfMXGhBwAJ), I saw similar USB-related problems on R3.1-rc1.  On a Haswell system, I was able to successfully run through the installer (which was on a USB flash drive) to install to an external USB drive (SATA drive attached via USB-SATA adapater).  On firstboot, Grub would do its thing, but an LED on the external drive that shows whether the USB interface is active would turn off as soon as the kernel booted.  The messages output by the kernel would show that the USB controller was detected, but did not show sda (the USB drive) being detected.  On Qubes R2, I had no problem installing to, and running from, an external USB drive on the same system.

https://groups.google.com/d/msg/qubes-users/lxo1nkw3w0U/yxlMWXmUBwAJ has some logs for a problem booting from a USB flash drive that sound similar, although that user may have had some other problems going on with the Qubes ISO he downloaded...

My hunch was that dracut is not putting something into initramfs that is needed to make devices plugged into the USB ports work, but I was too busy dealing with other things to investigate.

Eric

--
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 qubes-users...@googlegroups.com.
To post to this group, send email to qubes...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/2017503d-5112-4d2a-a342-fc67f8eada08%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Marek Marczykowski-Górecki]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

I guess it's about missing xhcd-pci module in initramfs...

You can use installation ISO to mount your system, then call:

chroot /mnt/sysimage dracut -f -d xhci-pci

Assuming the system was mounted at /mnt/sysimage. Also make sure that
/boot (/mnt/sysimage/boot) is mounted.

In the meantime I'll fix that in initramfs generating script.

- --
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQEcBAEBCAAGBQJWeHfaAAoJENuP0xzK19csjDsH/3ki7QhQmZpARNfpqka01hRz
bf2/ubd26ZNqZ9MbmJo2pzYvz7iGIaB2JQyqPB1SR7enIrI4kKr/bTTanxwpFifF
OPCXOSm0CgmxNzoosMib/IZQ8xAro5wh3DvVIiJhs5+U4//WstCrAGUPC4L56Vji
Sb3wspcWb8C2K0SP0cIMSzalLTQABm3ijZORS8BBOF4qwcxyjnC+Fyv1nUMw8ZO3
9hn+4VTKf6sgBTY29iwtQxf2LDRr6wIglS8K38u7Jfc/7m1SERgX6/uJLyG0kWfJ
xgdzrqOnRHH8sU9H01hcvUMhaqdB7FmroPTdcLGx1mW59ysl6IVOc9LsEdIgxUg=
=HQKJ
-----END PGP SIGNATURE-----

[gnod...@gmail.com]

Thank you, Frank and Eric, I'll give that a try, I hope I understood everything :D

[Jason M]

On Monday, 21 December 2015 17:06:24 UTC-5, Marek Marczykowski-Górecki wrote:

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On Mon, Dec 21, 2015 at 11:40:25AM -0800, gnod...@gmail.com wrote:
> Thanks for your answer!
>
> No, as soon as I edit the option to fit in the command so that my Skylake GPU is supported ('i915.preliminary_hw_support=1') and I boot, my keyboard turns black. If I leave out this option, the same thing happens, it's just in text mode then. As said, I tried multiple ones, but it doesn't seen to work.
>
> Essentially, the screen, where I'm promted to enter the password to decrypt my hdd doesn't work with my usb keyboard.
>
> Should I post some logs? And if so, what and how?

I guess it's about missing xhcd-pci module in initramfs...

You can use installation ISO to mount your system, then call:

chroot /mnt/sysimage dracut -f -d xhci-pci

Assuming the system was mounted at /mnt/sysimage. Also make sure that
/boot (/mnt/sysimage/boot) is mounted.

In the meantime I'll fix that in initramfs generating script.

Marek,

Can you also make sure the Logitech USB drivers (hid-logitech-hidpp)are also added in?
https://github.com/QubesOS/qubes-issues/issues/1516

Thanks!

[gnod...@gmail.com]

I'm mainly using Logitech HW, where should I add this option?

[gnod...@gmail.com]

As soon as I try the suggested commands, I get "cat: write error: Broken pipe".
Tried soma variation on those commands, but it doesn't seem to work.

[Eric Shelton]

On Monday, December 21, 2015 at 5:06:24 PM UTC-5, Marek Marczykowski-Górecki wrote:

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On Mon, Dec 21, 2015 at 11:40:25AM -0800, gnod...@gmail.com wrote:
> Thanks for your answer!
>
> No, as soon as I edit the option to fit in the command so that my Skylake GPU is supported ('i915.preliminary_hw_support=1') and I boot, my keyboard turns black. If I leave out this option, the same thing happens, it's just in text mode then. As said, I tried multiple ones, but it doesn't seen to work.
>
> Essentially, the screen, where I'm promted to enter the password to decrypt my hdd doesn't work with my usb keyboard.
>
> Should I post some logs? And if so, what and how?

I guess it's about missing xhcd-pci module in initramfs...

You can use installation ISO to mount your system, then call:

chroot /mnt/sysimage dracut -f -d xhci-pci

Assuming the system was mounted at /mnt/sysimage. Also make sure that
/boot (/mnt/sysimage/boot) is mounted.

In the meantime I'll fix that in initramfs generating script.

Although the above may work (I have not tried it), it looks like someone identified a better fix last week:

https://github.com/QubesOS/qubes-issues/issues/1517

I understand that it is not easy moving dom0 off of fc20, but these kinds of issues are where it keeps showing its age.

Eric

[marmarek]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On Wed, Dec 23, 2015 at 05:07:04PM -0800, Eric Shelton wrote:
> On Monday, December 21, 2015 at 5:06:24 PM UTC-5, Marek
> Marczykowski-Górecki wrote:
> >
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA256
> >

> > On Mon, Dec 21, 2015 at 11:40:25AM -0800, gnod...@gmail.com <javascript:>

> > wrote:
> > > Thanks for your answer!
> > >
> > > No, as soon as I edit the option to fit in the command so that my
> > Skylake GPU is supported ('i915.preliminary_hw_support=1') and I boot, my
> > keyboard turns black. If I leave out this option, the same thing happens,
> > it's just in text mode then. As said, I tried multiple ones, but it doesn't
> > seen to work.
> > >
> > > Essentially, the screen, where I'm promted to enter the password to
> > decrypt my hdd doesn't work with my usb keyboard.
> > >
> > > Should I post some logs? And if so, what and how?
> >
> > I guess it's about missing xhcd-pci module in initramfs...
> >
> > You can use installation ISO to mount your system, then call:
> >
> > chroot /mnt/sysimage dracut -f -d xhci-pci
> >
> > Assuming the system was mounted at /mnt/sysimage. Also make sure that
> > /boot (/mnt/sysimage/boot) is mounted.
> >
> > In the meantime I'll fix that in initramfs generating script.
> >
>
> Although the above may work (I have not tried it), it looks like someone
> identified a better fix last week:
>
> https://github.com/QubesOS/qubes-issues/issues/1517
>
> I understand that it is not easy moving dom0 off of fc20, but these kinds
> of issues are where it keeps showing its age.

It ends up with the same effect - newer dracut have this module
included. And we already have place to add such modules:
https://github.com/QubesOS/qubes-core-admin-linux/tree/master/dracut

- --
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQEcBAEBCAAGBQJWe0kJAAoJENuP0xzK19csIrkIAI2HEzhTnhmG3gEmMeg1ApgT
6P1fhomiytGHdkwOf6CN9yI/zP0jeN/847GTuSTW2MU9Rf1tjRt7cd28bLa40hvX
/Hm5EgXKs1mgNOcgrRqafFNAPJIdUIJnn9LKQas0Gkupg+2CxOed5mr+kbL/gdrt
tuhh1O5f3Xe3eF4Z7iGQtT74IEOTANGdfocv6XC7fNZQr7JBY2vRbrIRgq9IW0hG
CZyblE58NExSdLjml74a/pBxAdMQmjofYhUb0WQ/3MAG63PDaCvhIxE40OnDsILy
lcm/oUiqZPZNDkXqTsU9va4odwmjG2Slbj3zuL2g9S1GKgc3zWZXGLoM4lO3iP4=
=IW0R
-----END PGP SIGNATURE-----

[John Doe]

I was having the same issue, and "dracut -f -d xhci-pci" solved the
problem, i can now enter luks passphrase on boot using the usb keyboard.

Thanks!

[ryne.k...@gmail.com]

GA-H170M-D3H (DDR4)
i5-6400
M.2 SATA SSD
Add-On Front Panel 4 Port USB3
Both USB3 headers on Motherboard occupied, 1 of 2 USB2 Mobo headers occupied

I don't think the rest should be relevant considering the completely empty PCI and PCIe slots that I have at this time.

When installing Qubes OS 3.1 installer working fine. Get all the way into OS (not enabling the sys-usb vm because no ps2 input devices to play with and lack of experience). In the OS I can do (as far as I can tell) all of the things I should be able to.

Update Dom0 using:

sudo qubes-dom0-update

Works, no errors, some warning about using yum.

Keeps working until restart

Upon restart I get usb functionality until the Linux kernel loads and then usb powers off before the prompt for disk encryption pass code is on screen.

This is consistent across multiple trials.

I use workaround from marmarek @ https://github.com/QubesOS/qubes-issues/issues/1517

Working now.

To clarify the easiest thing I found to fix, for fresh install, is just run the command from last commit to add testing repo to the dom0 update when you do it.

Thanks a lot for this.