Description of problem: With the current version of Fedora 32 kernel usbip bind doesn't work and the command gives an error. Version-Release number of selected component (if applicable): Fedora Kernel 5.7.8-200 usbip-utils 2.0 How reproducible: Always Steps to Reproduce: 1. Load usbip kernel modules modprobe usbip-core modprobe usbip-host 2. Load usbipd usbipd 3. bind an existing USB device usbip bind -b 2-2 Actual results: usbip: error: error binding device 2-2 to driver: No such device usbip: error: could not bind device to usbip-host Expected results: USB device bound to usbip Additional info:
FEDORA-2020-286a37944e has been submitted as an update to Fedora 32. https://bodhi.fedoraproject.org/updates/FEDORA-2020-286a37944e
Just to be clear, I have not actually tested this build. I just know that the usbip userspace can be somewhat coupled with the kernel, so hopefully a 5.7.x userspace will fix your problem. If it doesn't, please let me know.
FEDORA-2020-286a37944e has been pushed to the Fedora 32 testing repository. In short time you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-286a37944e` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-286a37944e See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Sorry but it didn't work. Same error when binding.
What's the output of "usbip list"?
I guess the command you want is 'usbip list -l' The output on this machine (I don't have access to the one with the bind 2-2 at the moment) with Fedora 32 and your usbip testing version is: [root@apc localuser]# usbip list -l - busid 3-1 (09fb:6001) Altera : Blaster (09fb:6001) - busid 3-2 (04b4:fd13) Cypress Semiconductor Corp. : Energenie EG-PMS (04b4:fd13) - busid 3-3 (0403:6001) Future Technology Devices International, Ltd : FT232 Serial (UART) IC (0403:6001) - busid 3-4 (04b4:fd13) Cypress Semiconductor Corp. : Energenie EG-PMS (04b4:fd13) - busid 1-1.2 (03fd:0008) Xilinx, Inc. : Platform Cable USB II (03fd:0008) - busid 1-1.4 (0403:6001) Future Technology Devices International, Ltd : FT232 Serial (UART) IC (0403:6001) - busid 2-1.6 (0bda:0129) Realtek Semiconductor Corp. : RTS5129 Card Reader Controller (0bda:0129) No matter which device I choose to bind, the error is always the same: [root@apc localuser]# usbip bind -b 3-1 usbip: error: error binding device 3-1 to driver: No such device usbip: error: could not bind device to usbip-host [root@apc localuser]# usbip bind -b 1-1.2 usbip: error: error binding device 1-1.2 to driver: No such device usbip: error: could not bind device to usbip-host
(In reply to m-brueckner from comment #6) > I guess the command you want is 'usbip list -l' Yep. Thanks for picking that up. :) > [root@apc localuser]# usbip bind -b 3-1 > usbip: error: error binding device 3-1 to driver: No such device > usbip: error: could not bind device to usbip-host > > [root@apc localuser]# usbip bind -b 1-1.2 > usbip: error: error binding device 1-1.2 to driver: No such device > usbip: error: could not bind device to usbip-host This looks like an upstream bug. See https://bugzilla.kernel.org/show_bug.cgi?id=208267
This is fixed in kernel-5.8.6 (in updates-testing): https://bodhi.fedoraproject.org/updates/FEDORA-2020-708b23f2ce Please test and verify that it fixes your problem
This should have been closed a while ago