Closed ivanjx closed 2 years ago
I'm waiting for release of WDK for VS-2022. I don't want to install preview versions of SDK/WDK.
VS2022 can be used to build "develop" branch.
1、 windows 10 professional 2004(for this wsk version,I reinstall my windows to this version) Microsoft Visual Studio Enterprise 2022 (64 bit) - Current - version 17.2.2 sdk version 10.0.22621.0 wdk version 10.0.22621.0 2、 Install driver/usbip_test.pfx (password: usbip) "Trusted Root Certification Authority" in "Local Computer" (not current user) and "Trusted Publishers" in "Local Computer" (not current user) Set certificate driver signing for usbip_vhci project bcdedit.exe /set TESTSIGNING ON and reboot 3、 in cmd with administrator priviledge devcon.exe install usbip_root.inf USBIPWIN\root after that in device manager,it looks like somethings wrong
and the property details: Windows cannot load the device driver for this hardware. The driver may be damaged or missing. (Code 39) {driver input point not found} %hs device driver cannot find the input point %hs in the driver %hs. any suggestions? and the previous develop version(not wsk) ok for me
The build should create an installer, you don't have to install the driver manually. Readme.md describes everything.
userspace/src/innosetup/setup.iss executes commands which you could run yourself.
yes,I also try that to but the problem the same
InnoSetup executes these commands
certutil.exe -f -p usbip -importPFX Root usbip_test.pfx FriendlyName="USBIP Test"
certutil.exe -f -p usbip -importPFX TrustedPublisher usbip_test.pfx FriendlyName="USBIP Test"
pnputil.exe /add-driver usbip_vhci.inf /install
devnode.exe install usbip_root.inf USBIPWIN\root
I don't have Win10 to test this issue, it works on Win11.
1、 I set this,and it works now! 2、 in my win10 2004 attach,detach are ok,but when I reattach the same device it will be BSOD(I've tried many times),and the log BSOD.log 3、 my uac first attach I've hearded unnormal sound,and the traceview print lots of info,after that,in the task bar I change the sound volume,no sound Name Filename Line# System Time Message Unknown 16 06\02\2022-14:19:14:540 Unknown( 16): GUID=8a5fa127-5168-34fa-c75d-e92ce166ec49 (No Format Information found).
Use debug build and get full log as described in Readme.md, please.
!analyze -v
!wmitrace.searchpath %TEMP%\tmfs
!wmitrace.setprefix [%9]%3!04x! %!LEVEL! %!FUNC!:
!wmitrace.logdump usbip-vhci
I'm testing the driver using driver verifier from WDK. Several issues were found for two hours :) I want to finish this testing before dealing with these bsods.
I've fixed several bugs that cause BSOD. I'm testing vhci driver using Driver Verifier and there are no issues so far. Could you please try your devices with new build?
Please, make logs exactly as described in "Obtaining USB/IP logs on Windows". Your logs are hard to understand due to another TRACE_FORMAT_PREFIX.
BSOD4-attach-detach-attach.txt caused by NT_ASSERT, I've commented it. BSOD3.txt is very similar to behavior of the driver before recent fixes, make sure that you are building and testing the latest develop branch.
I've fixed a bug that was found in BSOD5-change.vol.txt, thank you! copy_isoc_data:src_offset(0) != src_len(192)
I don't have a device to test the fix, but it should work.
I've tried,when attach it will failed on sending and then auto unplug,here is the etl log file LogSession_20220610_093143.zip I am used to using the traceview.exe,You can navigate to the following line vhci wsk.events.cpp 634 WskDisconnectEvent 06\10\2022-09:34:03:423 vpdo 49ccb420, Flags 0x9
I can't and won't view binary file.
I've just tried again the strange thing is the device name in device manager,now it's it used to be "AUCTOPUS I-65" but the sound is ok now : )
Do you notice a difference between this WSK build and old version that uses usbip_xfer.exe ?
xfer first connect to server and get the device-configration descriptor and then create vpdo wsk first create vpdo and then connect but when plugin xfer is not use the already got descrptor info after IoInvalidateDeviceRelations the upper driver will URB_FUNCTION_GET_DESCRIPTOR_FROM_DEVICE I know the sting "AUCTOPUS I-65" is frome iProduct string in device descriptor,but I don't know the string "USB Audio Device" from where?
Fixed
im wondering if visual studio 2022 with the preview sdk and wdk are supported. or do i need to use visual studio 2019? thanks.