1、server side
linux,kernel-3.18.20,usbipd,usbip bind,everythings were ok
2、client side
win10 pro 21H1 19043.1586,vhci-ude driver,usbip attach,everythings were ok too,the usb speaker and mic were show in the device manager,when I click on the volume bar in the taskbar,normally we should heart a "ding" sound,but it didn't
3、it seems like attach.exe miss one ctrl message----SET INTERFACE
the bus hound msg:
Device - Device ID (followed by the endpoint for USB devices)
(7) usbip-win VHCI(ude)
(12) USB Root Hub (USB 3.0)
(25) USB Composite Device
(26) AUCTOPUS I-65
ntoskrnl : NT Kernel & System 10.0.19041.1586 (WinBuild.160101.0800)
usbaudio : USB Audio Class Driver 10.0.19041.1202 (WinBuild.160101.0800)
Device Address Length Phase Data Description Cmd.Phase.Ofs(rep) Date Time Driver
12.0 CTL 01 0b 01 00 01 00 00 00 SET INTERFACE 4.1.0 2022/03/26 10:33:23.767 ntoskrnl
26.0 CTL 22 01 00 01 01 00 03 00 SET CUR 6.1.0 2022/03/26 10:33:23.767 usbaudio
here are the bushound pics
in traceview,why I can't see any URB_FUNCTION_ISOCH_TRANSFER,only URB_FUNCTION_CONTROL_TRANSFER
and who set the _URB_HEADER.Status to USBD_STATUS_INVALID_PARAMETER(0x80000300)
1、server side linux,kernel-3.18.20,usbipd,usbip bind,everythings were ok 2、client side win10 pro 21H1 19043.1586,vhci-ude driver,usbip attach,everythings were ok too,the usb speaker and mic were show in the device manager,when I click on the volume bar in the taskbar,normally we should heart a "ding" sound,but it didn't 3、it seems like attach.exe miss one ctrl message----SET INTERFACE the bus hound msg:
and the debug_pdu msg:
can't get the root hub(12) message