Qubes OS 4.3 - sys-usb - Error: Got empty response from qubesd - After Firmware Update of BitBox

User Support
1

Hello Team,

I have a problem with USB device detection in the VM.
In the VM, I installed the BitBoxApp, and it worked when connecting the BitBox Stick via USB‑C. After upgrading the BitBox firmware, however, the BitBox App can no longer detect the connected device.

Is this a known issue?

What I tried:

a) qvm-device usb list --assignments (I can see the BitBox listed)
b) qvm-device usb attach --ro apps sys-usb:4-5
I get this error: Error: Got empty response from qubesd. See journalctl in dom0 for details
c) I also restarted sys-usb - no success.

It seems like this might be related to a qubesd issue. I noticed that after the firmware update, the USB IDs changed, and Qubes may not be able to apply the previous device assignment / mapping.

Any experience with that issue? What could I try?

Thanks in advance for your support.

2

What I did try:

a) I can see BitBox there

qvm-usb list ---assignments

b) qvm-usb detach apps sys-usb:4-6.1

type or paste code here

c) Increase Memory to 400 MB for sys-usb

d) Restart sys-usb

e) Or with command:

qvm-shutdown sys-usb --wait
qvm-start sys-usb

f) Attach BitBox to apps (AppVM)

Still that error: Error: Got empty response from qubesd. See journalctl in dom0 for details.

g) Even with that via Terminal:

qvm-usb attach apps sys-usb:4-6.1
3

This also did not help:

Via Terminal (dom0):

sudo qubes-dom0-update kernel-latest
4

I also did:

Shutdown sys-usb.

sudo qvm-remove -f sys-usb

sudo qubesctl state.sls qvm.sys-usb

Still no success. Still same protocol error. I think that the bug is still there on Qubes OS 4.3.

5

Probably the same issue: Can't passthrough CUL868 DFU usb · Issue #10861 · QubesOS/qubes-issues · GitHub

6

This probably causes: Since we know the error occurs because Qubes OS 4.3 cannot process the modified hardware ID after the firmware update of Bitbox (with USB-C), I also could not completely reset the Qubes USB subssystem once successfully. So the old, blocking entries are still not cleared.

7

Any idea how to solve this issue?

8

On dom0:

sudo journalctl -fu qubesd

And run the command that is failing.

9

I got that:


WARNING: protocol error for call b'admin.vm.device.usb.Attach'+b'sys-usb-4-5+03eb+2403+v9.26.3-pre+cbb40634cc+u030000' (b'dom0' - b'apps') with payload of 143 bytes
10

I can see via:

qvm-device usb list that input:

sys-usb:4-5 Input: bitboxswiss v9.xx.x-pre+xxx

@ben-grande

11

Can you try this: Can't passthrough CUL868 DFU usb · Issue #10861 · QubesOS/qubes-issues · GitHub

If the results are the same as from the thread you linked above, I can link this forum thread to the github issue. If they are different results, I’m going to ask you to create a new issue on github.

1 Like
12

Thanks for your response. The results are the same, so feel free to link this forum thread to the GitHub issue. Would you be able to do that?

Thanks a lot @ben-grande

13

Done.

14

Can you share more information? Can't passthrough CUL868 DFU usb · Issue #10861 · QubesOS/qubes-issues · GitHub

15

Yes, I will add there some more information related that issue. Thanks for this hint.