Open bemo47 opened 2 years ago
try using sudo when you run usbipd on p4, i had the same issue , win11 starts and detects it but will never connect.
Unfortunately that's what i did, all commands done with sudo on pi side.
Le lun. 17 janv. 2022 à 10:00, renwar99 @.***> a écrit :
try using sudo when you run usbipd on p4, i had the same issue , win11 starts and detects it but will never connect.
— Reply to this email directly, view it on GitHub https://github.com/barbalion/usbip-win-client/issues/11#issuecomment-1014282903, or unsubscribe https://github.com/notifications/unsubscribe-auth/AKSF2YENQNYIXNZ4TARICHLUWPLBLANCNFSM5MDK4ZFA . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you authored the thread.Message ID: @.***>
i think i installed the usbip drivers for WSL , I am not sure if that changed anything,. but what i know you have to enable unsigned drivers. and after i run the usbipd with sudo on pi4 and it just worked. i had the exact same issue last night. i was testing and testing and it was not working. hence i found this thread. the following is my drive config and the pi4 interface
[Edit]
Sorry and one more thing: add this to your modules... not sure it it helps:
u mean enable unsigned drivers on pi side or on windows side ?
on windows 11 side. (normally unsigned drivers have a yellow triangular shape next to the driver icon. this means windows does not recognize or allow it in some cases.). and note this comes with some risk. try to see what are the risks. anyways here is the how to:
ok, so now i am in test mode but service not running and attach still failed
but at the end of the install.cmd, since the start i have this error
What i done is deleting the service coupe of times and start over fresh(i mean : delete everything unzip the original and start again from there ). in windows here is how to delete the service:
From Admin-Powershell-command
sc.exe delete "USBIPService"
Note: once it says the service is deleted , you actually have to go to services and stop it. then it will be deleted. also this version of usbip is trying to make the usbip an automated process. it has a lot of issues of detection. I will further debug tonight and see if i can find solutions for the common problems.
[Edit]
also reinstall the drivers if you can. delete all of them and install them from the install script
yes, not easy, i deleted the service, then restarted, then install.cmd again with install service, but service stays "paused"....
even unsinstalling all and reinstalling, same
You sure you deleted the service? Go to services and check the old service status , make sure it is deleted before you start fresh
Unfortunately, I don't have Win11 in my possession to test at the moment. Try rebooting the system before fresh install. Deleting services can leave traces in the running system.
Yes i did, deleted service, uninstall all, reboot, still in test mode, install again, test and same...
Hi, I have installe usbip on the Pi4 and succeed to bind one usb equipment, a usb key for test. On the Win11 i laso installed your solution, and succeeded to list the binded elements on the Pi4 from the Win11. But when i launch the attach command i get "failed to attach" I am not expert enough to understand what happens here, and what i did wrong... Hope i can get some help.