usbip이 vhci 드라이버를 열 때 오류 발생

usbip이 vhci 드라이버를 열 때 오류 발생

업데이트(아래 참조)
클라이언트와 서버에 usbip 패키지를 설치하고 둘 다에 커널 모듈을 로드한 후 서버에서 usbipd를 시작했습니다.

sudo usbipd
usbipd: info: starting usbipd (usbip-utils 2.0)EDIT: I found better instructions here: https://github.com/torvalds/linux/tree/master/tools/usb/usbip

클라이언트: sudo modprobe vhci-hcd sudo usbip Attach -r 192.168.5.153 -b 1-1

섬기는 사람:

usbipd: INFO: 192.168.1.2:40942의 연결 usbipd: INFO: 요청 수신됨: 0x8003(4) usbipd: INFO: 요청된 장치 발견: 1-1 usbip: INFO: 연결: 1-1 usbipd: INFO: 요청 0x8003(4 ) ): 완벽한

고객:

sudo lsusb (예상 USB 장치가 표시되지 않고 KDE 멀티미디어 도구에 새 오디오 장치가 표시되지 않음) usbipd: info: Listening on 0.0.0.0:3240 usbipd: error: 소켓: :::3240: 97 (주소 제품군은 프로토콜을 지원하지 않습니다)

위의 오류를 조사하지 않았으며 관련이 있는지는 모르겠지만 관련이 없다고 가정합니다.

그런 다음 USB 장치를 바인딩했습니다.

sudo usbip bind -b 1-1

그런 다음 클라이언트에서 장치를 연결했습니다.

sudo usbip attach -r 192.168.1.153 -b 1-1
libusbip: error: udev_device_new_from_subsystem_sysname failed
usbip: error: open vhci_driver

usbipd 서버에 다음 메시지가 나타납니다(두 번 연결을 시도했습니다):

usbipd: info: connection from 192.168.1.2:40910
usbipd: info: received request: 0x8005(4)
usbipd: info: exportable devices: 1
usbipd: info: request 0x8005(4): complete
usbipd: info: connection from 192.168.1.2:40912
usbipd: info: received request: 0x8003(4)
usbipd: info: found requested device: 1-1
usbip: info: connect: 1-1
usbipd: info: request 0x8003(4): complete
usbipd: info: connection from 192.168.1.2:40918
usbipd: info: received request: 0x8003(4)
usbipd: info: found requested device: 1-1
usbip: info: connect: 1-1
usbipd: info: request 0x8003(4): complete

lsusb클라이언트에 USB 장치가 연결되어 있지 않음을 나타냅니다. 클라이언트의 관련 오류는 다음과 같습니다.

libusbip: error: udev_device_new_from_subsystem_sysname failed
usbip: error: open vhci_driver

클라이언트와 서버 모두 다음 버전을 실행합니다.

sudo pacman -Qi usbip 이름: usbip 버전: 4.18-1

Linux 4.18.6-arch1-1-ARCH #1 SMP PREEMPT 수요일 9월 5일 11:54:09 UTC 2018 x86_64 GNU/Linux

여기에서 설치 도움말을 얻었습니다: 튜토리얼 – USB/IP » Linux Magazinehttp://www.linux-magazine.com/Issues/2018/208/Tutorial-USB-IP

업데이트: 여기에서 더 나은 지침을 찾았습니다.https://github.com/torvalds/linux/tree/master/tools/usb/usbip

고객:

sudo modprobe vhci-hcd
sudo usbip attach -r 192.168.5.153 -b 1-1

섬기는 사람:

usbipd: info: connection from 192.168.1.2:40942
usbipd: info: received request: 0x8003(4)
usbipd: info: found requested device: 1-1
usbip: info: connect: 1-1
usbipd: info: request 0x8003(4): complete

고객:

sudo lsusb

(예상된 USB 장치가 표시되지 않았으며 KDE 멀티미디어 도구에도 새로운 오디오 장치가 표시되지 않았습니다)

클라이언트의 로그에는 USB 장치가 발견되었지만 즉시 바인딩이 해제되었다고 표시됩니다. 이유는 잘 모르겠습니다.

# journalctl -r
Sep 23 05:12:20 client kernel: usb 3-1: USB disconnect, device number 4
Sep 23 05:12:20 client kernel: vhci_hcd: disconnect device
Sep 23 05:12:20 client kernel: vhci_hcd: release socket
Sep 23 05:12:20 client kernel: vhci_hcd: stop threads
Sep 23 05:12:20 client kernel: vhci_hcd: connection closed
Sep 23 05:12:20 client krunner[993]: [05::12:20.748] unknown: UdevQt: unhandled device action "bind"
Sep 23 05:12:20 client org_kde_powerdevil[1022]: [05::12:20.748] unknown: UdevQt: unhandled device action "bind"
Sep 23 05:12:20 client kdeinit5[954]: [05::12:20.748] unknown: UdevQt: unhandled device action "bind"
Sep 23 05:12:20 client kate[4517]: [05::12:20.748] unknown: UdevQt: unhandled device action "bind"
Sep 23 05:12:20 client plasmashell[995]: [05::12:20.748] unknown: UdevQt: unhandled device action "bind"
Sep 23 05:12:20 client baloo_file[991]: [05::12:20.748] unknown: UdevQt: unhandled device action "bind"
Sep 23 05:12:20 client systemsettings5[1170]: [05::12:20.748] unknown: UdevQt: unhandled device action "bind"
Sep 23 05:12:20 client kdeinit5[954]: [05::12:20.748] unknown: UdevQt: unhandled device action "bind"
Sep 23 05:12:20 client kdeinit5[954]: [05::12:20.748] unknown: QObject::connect: invalid null parameter
Sep 23 05:12:20 client org_kde_powerdevil[1022]: [05::12:20.748] unknown: UdevQt: unhandled device action "bind"
Sep 23 05:12:20 client krunner[993]: [05::12:20.748] unknown: UdevQt: unhandled device action "bind"
Sep 23 05:12:20 client plasmashell[995]: [05::12:20.747] unknown: UdevQt: unhandled device action "bind"
Sep 23 05:12:20 client kate[4517]: [05::12:20.747] unknown: UdevQt: unhandled device action "bind"
Sep 23 05:12:20 client systemsettings5[1170]: [05::12:20.747] unknown: UdevQt: unhandled device action "bind"
Sep 23 05:12:20 client baloo_file[991]: [05::12:20.747] unknown: UdevQt: unhandled device action "bind"
Sep 23 05:12:20 client kdeinit5[954]: [05::12:20.747] unknown: UdevQt: unhandled device action "bind"
Sep 23 05:12:20 client kdeinit5[954]: [05::12:20.747] unknown: QObject::connect: invalid null parameter
Sep 23 05:12:20 client baloo_file[991]: [05::12:20.747] unknown: QObject::connect: invalid null parameter
Sep 23 05:12:20 client baloo_file[991]: [05::12:20.746] unknown: UdevQt: unhandled device action "bind"
Sep 23 05:12:20 client org_kde_powerdevil[1022]: [05::12:20.746] unknown: UdevQt: unhandled device action "bind"
Sep 23 05:12:20 client plasmashell[995]: [05::12:20.746] unknown: UdevQt: unhandled device action "bind"
Sep 23 05:12:20 client systemsettings5[1170]: [05::12:20.746] unknown: UdevQt: unhandled device action "bind"
Sep 23 05:12:20 client krunner[993]: [05::12:20.746] unknown: UdevQt: unhandled device action "bind"
Sep 23 05:12:20 client kate[4517]: [05::12:20.746] unknown: UdevQt: unhandled device action "bind"
Sep 23 05:12:20 client kdeinit5[954]: [05::12:20.746] unknown: QObject::connect: invalid null parameter
Sep 23 05:12:20 client baloo_file[991]: [05::12:20.746] unknown: QObject::connect: invalid null parameter
Sep 23 05:12:20 client baloo_file[991]: [05::12:20.745] unknown: QObject::connect: invalid null parameter
Sep 23 05:12:20 client kdeinit5[954]: [05::12:20.744] unknown: UdevQt: unhandled device action "bind"
Sep 23 05:12:20 client baloo_file[991]: [05::12:20.744] unknown: UdevQt: unhandled device action "bind"
Sep 23 05:12:20 client systemsettings5[1170]: [05::12:20.744] unknown: UdevQt: unhandled device action "bind"
Sep 23 05:12:20 client org_kde_powerdevil[1022]: [05::12:20.744] unknown: UdevQt: unhandled device action "bind"
Sep 23 05:12:20 client kdeinit5[954]: [05::12:20.744] unknown: QObject::connect: invalid null parameter
Sep 23 05:12:20 client krunner[993]: [05::12:20.744] unknown: UdevQt: unhandled device action "bind"
Sep 23 05:12:20 client plasmashell[995]: [05::12:20.744] unknown: UdevQt: unhandled device action "bind"
Sep 23 05:12:20 client kate[4517]: [05::12:20.744] unknown: UdevQt: unhandled device action "bind"
Sep 23 05:12:20 client baloo_file[991]: [05::12:20.743] unknown: QObject::connect: invalid null parameter
Sep 23 05:12:20 client mtp-probe[5684]: bus: 3, device: 4 was not an MTP device
Sep 23 05:12:20 client mtp-probe[5684]: checking bus 3, device 4: "/sys/devices/platform/vhci_hcd.0/usb3/3-1"
Sep 23 05:12:20 client kernel: hid-generic 0003:0746:3000.0003: hidraw0: USB HID v1.00 Device [ONKYO USB HS Audio Device] on usb-vhci_hcd.0-1/input2
Sep 23 05:12:20 client kernel: hid-generic 0003:0746:3000.0003: No inputs registered, leaving
Sep 23 05:12:20 client kernel: usb 3-1: Manufacturer: ONKYO
Sep 23 05:12:20 client kernel: usb 3-1: Product: USB HS Audio Device
Sep 23 05:12:20 client kernel: usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Sep 23 05:12:20 client kernel: usb 3-1: New USB device found, idVendor=0746, idProduct=3000, bcdDevice=22.04
Sep 23 05:12:20 client kernel: usb 3-1: SetAddress Request (4) to port 0
Sep 23 05:12:20 client kernel: usb 3-1: new high-speed USB device number 4 using vhci_hcd
Sep 23 05:12:20 client kernel: vhci_hcd vhci_hcd.0: devid(65544) speed(3) speed_str(high-speed)
Sep 23 05:12:20 client kernel: vhci_hcd vhci_hcd.0: pdev(0) rhport(0) sockfd(3)
Sep 23 05:10:53 client nm-dispatcher[5670]: req:1 'dhcp4-change' [wlan0]: completed: no scripts
Sep 23 05:10:53 client nm-dispatcher[5670]: req:1 'dhcp4-change' [wlan0]: new request (0 scripts)
Sep 23 05:10:53 client systemd[1]: Started Network Manager Script Dispatcher Service.
Sep 23 05:10:53 client dbus-daemon[478]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Sep 23 05:10:53 client systemd[1]: Starting Network Manager Script Dispatcher Service...
Sep 23 05:10:53 client dbus-daemon[478]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-disp>

답변1

이 오류가 발생할 때마다 원인은 다음과 같습니다.usbip 유틸리티클라이언트와 서버 버전이 일치하지 않습니다. 둘 다 확인하십시오. usbip version어느 것이 실행하여 이와 같은 것을 반환해야합니까?usbip (usbip-utils 2.0)

관련 정보