Kurt Struevy

Hi, I solved this problem by using usbip v 0.3.0. https://github.com/cezanne/usbip-win/releases/tag/v0.3.0 Thanks a lot to cezanne! Kurt

Hi David, thanks a lot for your answer. I bound the device. It is now visible on the client. { "data": { "busid": "1-1", "pname": "RTL2838 DVB-T", "product": "2838", "vendor": "0bda", "vname": "Realtek Semiconductor Corp." } , "host": "192.168.180.22", "process": "datagram" } { "data": { "process": "usbip-bind-ack", "recieved": -4 }, "host": "192.168.180.22", "process": "datagram" } And now I can use the usb device. But the raspberry zero is to slow for doing my work. I have to go to a raspberry...

Hi David, thanks a lot for your answer. I bound the device. It is now visible on the client. { "data": { "busid": "1-1", "pname": "RTL2838 DVB-T", "product": "2838", "vendor": "0bda", "vname": "Realtek Semiconductor Corp." } , "host": "192.168.180.22", "process": "datagram" } { "data": { "process": "usbip-bind-ack", "recieved": -4 }, "host": "192.168.180.22", "process": "datagram" } And now I can use the usb device. Great work! Thank you. Kurt

Hi David, thanks a lot for your answer. I bound the device but I do not know if it's relly available. { "data": { "busid": "1-1", "pname": "RTL2838 DVB-T", "product": "2838", "vendor": "0bda", "vname": "Realtek Semiconductor Corp." } , "host": "192.168.180.22", "process": "datagram" } { "data": { "process": "usbip-bind-ack", "recieved": -4 }, "host": "192.168.180.22", "process": "datagram" } What must I do tu use the remote device? Kurt

Hi David, thanks a lot for your help. Yes it works almost. Here the output of when I perform a "raw call": { "devices": [ { "busid": "1-1", "interfaces": [], "path": "/sys/devices/platform/soc/20980000.usb/usb1/1-1", "product_name": "Genesys Logic, Inc. : USB 2.0 IDE Adapter [GL811E] (05e3:0702)" } ], "host": "raspberrypi" } But it doesn't show it in the HOST VIEW. Are there other things missing?

Hi David, thanks a lot for your answer! I made everything again and checked it on the raspberry. This is the output: pi@raspberrypi:~ $ sudo systemctl start qusbipserver pi@raspberrypi:~ $ sudo systemctl status qusbipserver ● qusbipserver.service - qUsbipServer Loaded: loaded (/usr/lib/systemd/system/qusbipserver.service; enabled; vendor preset: enabled) Active: failed (Result: signal) since Fri 2020-07-10 10:45:35 BST; 296ms ago Process: 14244 ExecStart=/usr/sbin/qusbipserver (code=killed, signal=SEGV)...

Hi David, thanks a lot for your answer! I made everything again and checked it on the raspberry. This is the output: pi@raspberrypi:~ $ sudo systemctl start qusbipserver pi@raspberrypi:~ $ sudo systemctl status qusbipserver ● qusbipserver.service - qUsbipServer Loaded: loaded (/usr/lib/systemd/system/qusbipserver.service; enabled; vendor preset: enabled) Active: failed (Result: signal) since Fri 2020-07-10 10:45:35 BST; 296ms ago Process: 14244 ExecStart=/usr/sbin/qusbipserver (code=killed, signal=SEGV)...

Hi David, thanks a lot for your answer! I made everything again and checked it on the raspberry. This is the output: pi@raspberrypi:~ $ sudo systemctl start qusbipserver pi@raspberrypi:~ $ sudo systemctl status qusbipserver ● qusbipserver.service - qUsbipServer Loaded: loaded (/usr/lib/systemd/system/qusbipserver.service; enabled; vendor preset: enabled) Active: failed (Result: signal) since Fri 2020-07-10 10:45:35 BST; 296ms ago Process: 14244 ExecStart=/usr/sbin/qusbipserver (code=killed, signal=SEGV)...