Issue using Yubikeys on Qubes as GPG smart card: "selecting card failed: No such device"

tzwcfq · May 11, 2022, 7:03am

You need to create sys-usb.
Since your PC has 3 USB controllers then the best way is to dedicate 1 USB controller to dom0 and connect your USB keyboard and USB mouse to it and create sys-usb with other 2 USB controllers.
Here is the guide:

Qubes 4.1: How to enable a USB keyboard on a separate USB controller

https://www.qubes-os.org/doc/usb-qubes/#qubes-41-how-to-enable-a-usb-keyboard-on-a-separate-usb-controller

simonflex · May 11, 2022, 7:07am

Good. I will try again. The first time when creating everything ended badly
Thank

simonflex · May 11, 2022, 7:52am

Add usbcore.authorized_default=0 and rd.qubes.dom0_usb=<BDF> to that line, where <BDF> is the USB controller identifier.


ID 1532:0083 Razer USA Ltd Raser Basilic X HyperSpeed
ID 1532:025a Razer USA Ltd Raser BlackWidow V3 Pro

Tell me how to correctly register the identifier for the keyboard and mouse, the manufacturer is one (Razer)

tzwcfq · May 11, 2022, 7:54am

There is a link to the guide on how to identify the right USB controller in the first step of the guide above:

Find the controller used for input devices.

simonflex · May 11, 2022, 8:29am

after this procedure, this is what happened

tzwcfq · May 11, 2022, 8:35am

After you performed all these steps?

Find the controller used for input devices.

Open the file /etc/default/grub in dom0.

Find the line that begins with GRUB_CMDLINE_LINUX .

Add usbcore.authorized_default=0 and rd.qubes.dom0_usb=<BDF> to that line, where <BDF> is the USB controller identifier.

Save and close the file.

Run the command grub2-mkconfig -o /boot/grub2/grub.cfg (legacy boot) or grub2-mkconfig -o /boot/efi/EFI/qubes/grub.cfg (EFI) in dom0.

Reboot.

That’s the expected result. Now you need to perform last 8th step:

Proceed with creating a USB qube normally. The selected USB controller will remain in dom0.

And create sys-usb. There is a link in the step on how to do it. You need to run this command in dom0:
sudo qubesctl state.sls qvm.sys-usb

simonflex · May 11, 2022, 8:41am

sysusb.log (4.5 KB)

tzwcfq · May 11, 2022, 8:54am

Here seems to be the same problem:

github.com/QubesOS/qubes-issues

sys-usb not correctly created on install

opened 12:59AM - 01 Jul 21 UTC

eloquence

T: bug C: installer P: major diagnosed

**Qubes OS version** 4.0.4 **Affected component(s) or functionality** sys-…usb **Summary** In a default install on a ThinkPad T490, `sys-usb` was not created as expected, even though the installation defaults were not modified (`sys-net-usb` was also _not_ created; the USB controller was not attached to anything.) Subsequent attempts to create it via `sudo qubesctl state.sls qvm.sys-usb` failed with a state failure on the ID `sys-net-usb`, as illustrated below. <details> <summary>Screenshot</summary> ![qubes-sls-failure](https://user-images.githubusercontent.com/213636/124049121-a9c8d880-d9cc-11eb-9341-0c3350db2402.png) </details> Creating the `sys-usb` Qube manually partially resolved, but `sys-usb` would not start, failing with "Unable to reset PCI device". Following the instructions in https://www.qubes-os.org/doc/pci-troubleshooting/#domain--has-failed-to-start-internal-error-unable-to-reset-pci-device--no-flr-pm-reset-or-bus-reset-available appears to finally have resolved.

Check the output of this command in dom0:
sudo qubesctl top.enabled pillar=True

simonflex · May 11, 2022, 9:01am

tzwcfq · May 11, 2022, 9:02am

Run this command in dom0:
sudo qubesctl top.disable qvm.sys-net-as-usbvm pillar=True
Then try to create sys-usb again:
sudo qubesctl state.sls qvm.sys-usb

simonflex · May 11, 2022, 9:08am

simonflex · May 11, 2022, 9:11am

github.com/QubesOS/qubes-issues

qvm.sys-net-with-usb no longer exists

opened 05:06AM - 02 Apr 21 UTC

ArtificialAmateur

T: bug C: doc C: mgmt P: default needs diagnosis

**Qubes OS version** Qubes release 4.0 (R4.0) **Affected component(s) or… functionality** - qubesctl (salt-stack) - sys-net - sys-usb **Brief summary** [qvm.sys-net-with-usb](https://github.com/QubesOS/qubes-mgmt-salt-dom0-virtual-machines/commit/8b219ee528ae052c209db70ed92c543a71cc75a6) state no longer exists, removed and replaced with [pillar sys-net-as-usbvm](https://github.com/QubesOS/qubes-mgmt-salt-dom0-virtual-machines/commit/c21c87215c08ba25a9b2c560cc8e7c99dd26edc4). Documentation has not been updated [1](https://www.qubes-os.org/doc/salt/#qvmsys-net-with-usb) & [2](https://www.qubes-os.org/doc/installation-guide/). No existing documentation on how to use sys-net for usb devices for relying "on a USB device for network access, such as a USB modem or a USB Wi-Fi adapter". **To Reproduce** Steps to reproduce the behavior: 1. Install Qubes 4.0 2. Remove sys-usb 3. Attempt to create conjoined sys-net/sys-usb. **Additional context** I'd like sys-net to be the default VM with USB devices and not dom0, in order to properly use my USB WiFi adapter. **Solutions you've tried** 1. Create sys-usb through `qubesctl` 2. Start NetworkManager 3. Open network connection. 4. (Works but is not persistent). **Relevant [documentation](https://www.qubes-os.org/doc/) you've consulted** https://www.qubes-os.org/doc/salt/#qvmsys-net-with-usb https://www.qubes-os.org/doc/installation-guide/ **Related, [non-duplicate](https://www.qubes-os.org/doc/reporting-bugs/#new-issues-should-not-be-duplicates-of-existing-issues) issues** #2860

simonflex · May 11, 2022, 9:12am

tzwcfq · May 11, 2022, 9:24am

Do you have sys-net-usb VM?

simonflex · May 11, 2022, 9:27am

no. only sys-net

simonflex · May 11, 2022, 9:30am

tzwcfq · May 11, 2022, 9:30am

Then it’s better to address this issue to @marmarek here:

github.com/QubesOS/qubes-issues

sys-usb not correctly created on install

opened 12:59AM - 01 Jul 21 UTC

eloquence

T: bug C: installer P: major diagnosed

**Qubes OS version** 4.0.4 **Affected component(s) or functionality** sys-…usb **Summary** In a default install on a ThinkPad T490, `sys-usb` was not created as expected, even though the installation defaults were not modified (`sys-net-usb` was also _not_ created; the USB controller was not attached to anything.) Subsequent attempts to create it via `sudo qubesctl state.sls qvm.sys-usb` failed with a state failure on the ID `sys-net-usb`, as illustrated below. <details> <summary>Screenshot</summary> ![qubes-sls-failure](https://user-images.githubusercontent.com/213636/124049121-a9c8d880-d9cc-11eb-9341-0c3350db2402.png) </details> Creating the `sys-usb` Qube manually partially resolved, but `sys-usb` would not start, failing with "Unable to reset PCI device". Following the instructions in https://www.qubes-os.org/doc/pci-troubleshooting/#domain--has-failed-to-start-internal-error-unable-to-reset-pci-device--no-flr-pm-reset-or-bus-reset-available appears to finally have resolved.

I don’t have much knowledge at this and can’t help with this salt issue.

simonflex · May 11, 2022, 9:33am

Yeah. I think there are a lot of bugs in this system. Some are resolved in the unstable branch. I seem to be stable. When to solve problems dick knows. )) Thank you very much for your help.

simonflex · May 11, 2022, 9:47am

sudo qubesctl state.sls qvm.sys-usb
created a virtual machine sys-usb
what to do next ?

tzwcfq · May 11, 2022, 9:57am

Do you see your USB devices (not keyboard/mouse) when you run this command in dom0?
qvm-usb