cezuni
commented
5 years ago On attach I get pop-ups saying that USBIP is being setup and then it mentions that it's all ready. I don't get a command prompt back and I have no messages relating the setup of the actual device nor any new device appearing in the Device Manager.
Unlike linux version, attach of usbip-win is blocking because processing protocol is done in userspace without a dedicated daemon. This behavior should be improved by using kernel daemon. Anyway, there seems to be an error if no new device is appeared in device manager.
Checking on the USBIP on the Debian host, I see working responses from the server with 'received request' 0x8005 (5) on the listing remotely and the connection request which responds with a 0x8003(5) complete.
usbipd output looks good.
M0CRT
Hi. First, thank you for this great work. I've been working on this all weekend and today to get this working; really appreciate you help.
Running the 2.0 USBIP tools from Debian 9 (not the buggy version). All works great re the setup on the Debian host and I can share the devices.
From Windows I can see the devices with the correct USB.IDS. Looks fine.
Latest 0.4 version and have installed the driver correctly after cert install and dropping the Windows 10 x64 host into 'Test' Mode. Driver installs with no errors.
On attach I get pop-ups saying that USBIP is being setup and then it mentions that it's all ready. I don't get a command prompt back and I have no messages relating the setup of the actual device nor any new device appearing in the Device Manager.
Checking on the USBIP on the Debian host, I see working responses from the server with 'received request' 0x8005 (5) on the listing remotely and the connection request which responds with a 0x8003(5) complete.
Any ideas? I'm going mad! ;-)
I do now see to get the 'USB Device Over IP' 'device' in the correct category of Device Manager for the device I am attempting to connect, but I get a 'This device cannot start (Code 10).
Mo