Closed myisaak closed 3 years ago
@MyIsaak : If you copy a up-to-date usb.ids
, your list would have no unknown. See #151 .
Yes, usbip-win has too old usb.ids
. I promise to update at next release.
FIX: I was wrong. usb.ids
in usbip-win is a quite up-to-date version.
Hi @cezanne thanks for the tip. Unfortunately I think the issue lies somewhere else, because I've some of my devices manually in the list. The first one for example 8087:0029 can be found in the current list.
8087 Intel Corp.
// ...
0029 AX200 Bluetooth
To be sure my build isn't the problem, I've reproduced this issue using the precompiled builds on the release page. Could there be any other reason the software isn't reading the ids properly?
@MyIsaak : Maybe, the parsing routine(userspace/lib/names.c
) for usb.ids has a problem. Can you investigate it?
@MyIsaak : I've checked the parsing routine is not a problem. A wrong format usb.ids
might incur your issue. usbip.ids
in v0.3.5 had a wrong format by my mistake. I have uploaded the corrected version.
Ok great. I've tested the build in the release page and now works, therefore I'm closing this issue. Thanks!
When running the command
usbip list -l
I receive on my Windows 10 19043 the following result:Normally one would expect to see actual USB device names, as described in the README.
Here is my environment: