Is there a way to force HID mode on model T / Safe 3 / Safe 5? Currently WebUSB is giving issues when used along USB/IP (see USBIP protocol errors - General - Qubes OS Forum). Given the issue seems to be complex and possibly related to hardware, an option to force the device to use HID protocol would be a good workaround.
I’ve read the thread on qubes forum. The conclusions are wrong: both Trezor One and Trezor core family runs over the same webusb mode. (furthermore, on the wire “hid” and “webusb” are the same thing, the only difference is (a) USB descriptor data and (b) which drivers the OS loads by default)
Electrum is communicating via libusb directly, Chrome/Electron (and thus Suite) have their own intermediate USB layer. So any problems you are experiencing come down to some interplay of:
- what the Electron USB layer is doing, and
- the differences between USB implementation for the legacy (Trezor One) and core codebases. Very likely it in fact boils down to difference between the STM32F2 MCU family (trezor one) and the F4/U5 families.
Switching to HID on the trezor core models amounts to “say a different thing when host asks what you are” and is very unlikely to fix the problem.
I won’t be registering to the qubes forum but feel free to point the other participants here.
Thanks for your input, we came to the same conclusion here → USBIP protocol errors - #33 by equbes - General - Qubes OS Forum so this thread can be closed. The issue was with trezord which defaults to reset on session adquiring, setting it to false solved the issue completely (For some reason the reset doesn’t play nicely with USB/IP, but that’s another issue).
Only thing relevant is Add option to set `reset=false` on embedded `trezord` · Issue #17852 · trezor/trezor-suite · GitHub which can be tracked in github.