windows 10 as USBIP client #6
Comments
Yes.. I had focused to windows usbip server and something in vhci driver went wrong. |
|
Are there compatibility issues with USBIP between linux and windows version. As in linux its showing version : usbip (usbip-utils 2.0) |
|
#3 may answer your question. Protocol negotiation will fail between different versions. |
|
Thank you for your answer. I understand that more testing is needed but I m trying to help in any way possible. I can test some devices if you don't mind :). So from my understanding your Bluetooth dongle in I used Kernel debugging to get access log output from VHCI it seems that the BUS_PNP = STATUS_NOT_SUPPORTED in four cases. Are they cause for the issue ?
|
|
I don't mind but your help makes me be hasty. ^^;; Many thanks to you. Serious error or warning logs have (E) or (W) prefix. If up-to-date vhci codes still have "USB Device Over IP" in device manager, |
|
Thank you. I m happy that your working on this! :) No there is no severe error or warning with a prefix (E) or (W) in my log. The only issue is that the "USB Device Over IP" is classified by windows under other devices. The status of this device drivers is " device is not installed"(see the 1st picture in this post). When checking a bit closer in the events tab (USB Device Over IP Properties), we see that the device has not acquired any configurations. That confirms my suspension that that vhci_pdo.c does not initialize the new device correctly. Based on the log I trace the messages back to the following functions in the code. The status STATUS_NOT_SUPPORTED can be tracked back to the file vhci_pdo.c spesificly those three cases below. //Line 1255 in vhci_pdo.c
case IRP_MN_QUERY_INTERFACE:
//
// This request enables a driver to export a direct-call
// interface to other drivers. A bus driver that exports
// an interface must handle this request for its child
// devices (child PDOs).
//
status = Bus_PDO_QueryInterface(DeviceData, Irp);
break;//Line 1194 in vhci_pdo.c
case IRP_MN_QUERY_ID:
DBGI(DBG_PNP, "QueryId Type: %s\n", dbg_bus_query_id_type(IrpStack->Parameters.QueryId.IdType));
status = Bus_PDO_QueryDeviceId(DeviceData, Irp);
break;//Line 1209 in vhci_pdo.c
case IRP_MN_QUERY_RESOURCES:
status = Bus_PDO_QueryResources(DeviceData, Irp);
break;As mentioned in the earlier post here i still see the same When I right click to check the events of the USB Device over IP, I see the following. There is no configuration for the devices. |
|
Below is my log when a bluetooth dongle in linux is successfully attached from win10. |
|
@wrenchonline: I'm not sure but problems at IRP_MN_QUERY_DEVICE_RELATIONS or IRP_MN_QUERY_CAPABILITIES may not be related to this issue. and |
|
With my usb stick, I have the same result with logs from @wrenchonline. I'll modify userland usbip code. |
|
@wrenchonline and @cezuni I think the issues start from the usbip.exe file. When debuging usbip i see that the issues start in the userspace. User ip>usbip.exe --debug attach -r -b 1-1
|
|
@yelfarri You can test with a following workaround. The values are from my USB stick. |
|
9d72a1a makes a device to be recognized. |
|
@wrenchonline that is odd, can you test with a mouse or keyboard ? i have the follow configurations. Do you have the same issue mouse or keyboard ? /*3 - Human Interface Device */
BDeviceClass = 3;
/* 1 - Boot Interface Subclass */
BDeviceSubClass = 1;
/* 1 - Keyboard*/
/* 2 - Mouse */
BDeviceProtocol = 2;@wrenchonlin for usbip in server mode Linux does not assign values for BDeviceClass , BDeviceSubClass, and BDeviceprotocol . It is the client that signs those values. When running Linux-host to Linux-client, you can notice the same behavior where the client sets those values. From @Oxalin usbip I understood that earlier Linux-host set values than send them over to the client. I have tested that approach, and it worked for a short period but...... both windows and Linux becomes unstable (BSOD@windows and Linux crashes). |
|
@cezuni i have downloaded your latest commit 9d72a1a and done testing on your user code. Its definitly regonising the device now. Mouse and keyboard keeping it simple at the moment. Does seems that the pdu header is getting wrong value. This values should be between 1-4 do you have the same issue ?
In my case the device is regonized as a HID device. There is some improvement that good :). Information from device manager-> usb input device properties
|
@wrenchonline Many devices have zeros in device descriptor.(I got to know through this issue)
@yelfarri AFAIK, original Linux code resolves those values via additional listing command when importing. But recent linux kernel(over 4.13 ??) does not seem to provide interface info when a device is not configured. So listing command does not help. 9d72a1a code assigns class/subclass/protocol values from direct usbip protocol. |
|
@yelfarri I think that there's no problem in usbip protocol related code.
Improved but windows vhci driver still is not working. I'm working. 😅 |
|
@cezuni I have some good news and some bad news. Today i have been doing some testing on the system. I decided that I will reinstall the driver and test again. I m using a USB mouse in Linux host with windows client. And it worked!! It is stilling working after 3 hours running. One thing i reliazed when i attach the device on windows i have to move the mouse so windows driver manage to recognized it as a hid device. |
|
@yelfarri , @wrenchonline : You mean that it takes too long to work? 3 hours or 20 minutes. |
|
@cezuni my bad I mean, it works at once and I had a connection running for 3 hours and everything was ok. I will add logs tomorrow :) if u need to take a look at them. I was going to test a USB storage tomorrow. |
|
Yeah, my mouse works after seconds too. I will take a look at USB storage tomorrow. Can you provide the device descriptor you are testing? I will try to find something similar to test |
|
@yelfarri : I cannot acquire exact device descriptors. Those devices are unplugged now.(I am at home) I think that a specific device does not incur a problem. |
@wrenchonline what devices do you need do you have a list that we might need to work our way through? @cezuni will create a test plan that will go through a certain type of devices classes so we will try to expose any type of bugs or issues in the system. |
|
Hello, As I try to attach a device I'm getting following errors: Attaching the same device from a linux machine works fine. You can see a screenshot from my output below: |
|
@maurice-stegmann : What is a version of linux box? Can you share a linux kernel log? |
|
@wrenchonline : I think that usb speed mismatch is not the problem.
You can increase queue length from below code but it will not resolve the problem. What is a compatible id of usbip device which can be obtained from detailed tab of property sheet ? |
|
@wrenchonline : Well, if larger queue length helps, there's a significant speed gap between usbip server and client. 2048 queue size would be sufficiently large but waiting for a free usbip command seq slot instead of returning with error will be a more desirable approach. This can be a new issue.
Is the meaning of "pop" in pop tests "unplugging" a USB device? |
|
@cezuni : My Linux box is a RaspberryPi 3b+ running kernel 4.9.80 and Raspbian Stretch. Here's an output of my kernel log: |
|
@maurice-stegmann I need to ask first did you do the following steps? |
|
@yelfarri : I've installed the driver by adding a legacy device in device manager. I've also copied checked wether the correct files are in the same folder as usbip.exe. Still getting the same error... Is it possible that I did something wrong during building? |
|
@yelfarri : This morning, testing attaching the pendrive I've tried before:
resulted in:
|
|
@maurice-stegmann sorry for the slow replay I was busy moving to a new apartment and as well trying to find the issue. I installed clean windows and did the same steps to install the driver. I have got the same issue as you did. I fixed it by doing the following. Delete your old driver
Verify that your driver is removed. run cmd as administrator and paste those commands
Than restart... Install usbip_vhci certificate, to local machine. Certificate should be installed into "Trusted Root Certification Authority" and "Trusted Publishers" Install driver/usbip_test.pfx(password: usbip) Copy usbip.exe, usbip_vhci.sys, usbip_vhci.inf, usbip_vhci.cer, usbip_vhci.cat into a folder in target machine. The files should be in the same folder Install USBIP vhci driver Than restart... |
|
@yelfarri : I've tried your fix but I'm getting the same result as it was before. I've tested an USB pen drive, a mouse and a com to usb adaptor. Wich types of devices where you testing? |
|
@maurice-stegmann i have tested a mouse, keyboard and joystick. Seems that issue happen when the driver is not installed properly. But i really have no idea why it happens in your pc. you get the follow water mark on the bottom right corner of your windows ?
|
|
@yelfarri Yes, I get this watermark. |
|
@maurice-stegmann : If a mouse pointer is not moved on usbip client, something goes wrong.
Windows and linux kernel logs would be helpful to find the problem. Or usbip forwarding debugging logs. You can just define DEBUG_PDU in following code. |
|
@maurice-stegmann at least we went through every configuration I could think of. Yeah, I manage to use them as if they were connected to the client pc. Can you provide the debugging logs as @cezuni suggested? |
|
@cezuni excuse me, how do i define DEBUG_PDU? I've removed the # wich resulted in build errors |
|
@maurice-stegmann just add
|
this project Oxalin/usbip_windows#12，I would like to know if the usb camera can work in windows client successsfully? |
|
@hubbybob2015 Sorry but I have no idea... Maybe @wrenchonline can answer that |
|
@cezuni can you close this issue it seems that it is resolved :). The USBIP client works as a client |
|
hello, |
|
hello |
|
@keirlessmi : There's builtin binaries. Check release page. And Readme.md is the best for usbip-win build guide. 😄 |
|
@cezuni thank you for the answer |
|
Hello, |
|
Hello everybody. Sorry if it is such a bother, but I got a similar problem like you guys and have tried all solutions you wrote here but still stuck with the same problem. Can anyone help me with it? Thank you in advance. |
|
@muhammadhaqyaunoora : What's your device ? This issue is too old. You'd better add a comment on a recent similar issue or create a new your own issue. |
|
Sorry for the late reply. I use a Raspberry Pi 3 for the server and an Asus laptop for the client. I tried to connect to Arduino Uno and the device manager only read it as a USB over IP. Also, when I checked on the list the information is just all unknown wherein the raspberry pi all of the information showed up. Does it counts as a new issue though? Sorry for the bother |
|
@muhammadhaqyaunoora : New issue would be preferable. |
|
Alright, I will create new issue then. Thank you |
and others
I am configuring my windows 10 as client using this repository. And Raspberry Pi 3 ( Linux raspberrypi 4.4.50-v7+ ) as server using steps given in link.
USBIP version of server is 2.0
I am able to list the usb drive shared by server on windows. But unable to connect to it.
In device manager it is showing an unknown device named 'USB Device over IP'.
Is this ab bug of this repository as you mentioned in last line of README that it did not work?
The text was updated successfully, but these errors were encountered: