Closed d0n13 closed 4 months ago
These lines may be the issue?
[11:30:15.493][2] Cannot find device entry while removing USB device 0x557cda3664d0 on location 0x10006
[11:30:15.493][2] Cannot find device entry while removing USB device 0x557cda3664d0 on location 0x10006
Following the troubleshooting steps to run usbipd on command line. USB capture attach.zip
> usbipd server Logging:LogLevel:Default=Trace
dbug: Microsoft.Extensions.Hosting.Internal.Host[1]
Hosting starting
dbug: Usbipd.PcapNg[1000]
usbipd:PcapNg:Path = ''
dbug: Usbipd.Server[1000]
usbipd:Port = 3240
dbug: Usbipd.Server[1000]
4.2.0+54.Branch.master.Sha.5b36605535dd52bc3d8a8e4bbaee7f4d480c86ad
info: Microsoft.Hosting.Lifetime[0]
Application started. Press Ctrl+C to shut down.
info: Microsoft.Hosting.Lifetime[0]
Hosting environment: Production
info: Microsoft.Hosting.Lifetime[0]
Content root path: C:\Users\donie\Documents\usbipd-win
dbug: Microsoft.Extensions.Hosting.Internal.Host[2]
Hosting started
dbug: Usbipd.Server[1000]
new connection from 172.29.100.120
dbug: Usbipd.Server[1000]
connection close: Unable to read beyond the end of the stream.
dbug: Usbipd.Server[1000]
connection closed
dbug: Usbipd.Server[1000]
new connection from 172.29.100.120
dbug: Usbipd.ConnectedClient[1000]
Received opcode: OP_REQ_IMPORT
dbug: Usbipd.ConnectedClient[1000]
Claiming took 216 ms
info: Usbipd.ConnectedClient[1]
Client 172.29.100.120 claimed device at 2-3 (USB\VID_05AC&PID_12A8\00008120001428D61EE8201E).
dbug: 2-3.0[1000]
Endpoint created
dbug: 2-3.0[1000]
Endpoint created
dbug: 2-3.0[1000]
Trapped SET_CONFIGURATION: 1
dbug: 2-3.0[1000]
Trapped SET_CONFIGURATION: 0
dbug: Usbipd.ConnectedClient[1000]
Unbind or unplug while attached
info: Usbipd.ConnectedClient[2]
Client 172.29.100.120 released device at 2-3 (USB\VID_05AC&PID_12A8\00008120001428D61EE8201E).
dbug: Usbipd.Server[1000]
connection close: The operation was canceled.
dbug: Usbipd.Server[1000]
connection closed
I reinstalled WSL and just used the distribution version of libmobieldevice and it worked again :(
Hi @dorssel
I've been having this exact issue on Linux so I switched to WSL to see if it worked. Not doing anything special but it just stopped working a few days ago and I've been trying to locate the issue.
I do a bind and an attach and it fails. No error on Windows side but no device on WSL side. This is what syslog on WSL is reporting... Thing is the log on the Linux machine was identical, so not sure where the issue is...
Any ideas? Thanks Donie