Instructions for “Unsupported Hardware Detected” error are insufficient or wrong

Feedback Website Feedback
1

I am a new user, moving from Windows 7.

My machine does not provide VT-d. That is obvious right from installation, the installer identifies the lack of this attribute, and allows to continue installation (coherent with UserFaq).

After installation, it is possible to successfully boot into the system, but only the 1st boot. All next boot attempts seem to “hang” (as we are somewhat used to in Windows, sometimes the system just does nothing, and there is no response to any input) at the login screen. But it does not “hang”, although any input seems not to have any effect. Upon rebooting, and editing the grub script with qubes.skip_autostart, both keyboard and mouse work as expected, everywhere. Thus, it is a problem with sys-usb and hardware passthrough.

The instructions for Installation troubleshooting — Qubes OS Documentation were followed. The advanced properties of the vms were altered, grub was edited, followed by sudo grub2-mkconfig -o /boot/efi/EFI/qubes/grub.cfg, and next, the undocumented sudo dracut -f for getting the LUKS nicer password screen. The problem persists. After the LUKS password is entered, both keyboard and mouse have no effect on the login screen.

The only method to login is rebooting, editing grub, and add qubes.skip_autostart.

Thus, the information provided in the documentation is insufficient (there are missing steps), or is wrong (this behaviour is expected, the documentation drifted from the design/implementation of Qubes OS itself).

1 Like
2

Hi @keyser_soze, welcome here and thanks for your feedback!

I’m not competent on this topic but I would like to let you know that sudo grub2-mkconfig -o /boot/efi/EFI/qubes/grub.cfg is an outdated command.

There is a pending pull request to update that.

So, your issue is not resolved so some points are not clear enough. But this is a summary of the current issues with the docs:

  • tell the user that no “hanging” is expected? (I think this is a wrong assumption caused by your Windows experience)
  • document the use of sudo dracut -f
3

Hi @parulin, sudo grub2-mkconfig -o /boot/efi/EFI/qubes/grub.cfg being outdated is unexpected. I am not familiar with Linux’s settings/implementation (yet), but it is reasonable the existence of 2 commands focused on different bios types. That command did have an effect in my machine, so its existence is justifiable in my view. Has it been demonstrated that the legacy command suffices for all cases?

Regarding how to update the documentation, adding sudo dracut -f is a necessary subsequent step. But not the “hanging” part. I don’t know yet what is the correct procedure, so I cannot make any suggestions. The most I could do for now is describe what could be witnessed, with the hope that those with knowledge or experience could suggest effective solutions.

4

Yes, old way works, but you change default way and from now you can’t use new default grub update.

1 Like