usbip error open vhci driver

0

ATUALIZADO (veja abaixo)
Depois de instalar o pacote usbip no cliente e no servidor, carregando os módulos do kernel em ambos, iniciei o usbipd no servidor:

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

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

servidor:

usbipd: info: conexão de 192.168.1.2:40942 usbipd: info: pedido de recebido: 0x8003 (4) usbipd: info: encontrado dispositivo solicitado: 1-1 usbip: info: connect: 1-1 usbipd: info: request 0x8003 (4): completo

cliente:

sudo lsusb (o dispositivo usb esperado não é mostrado e também as ferramentas multimídia do KDE não mostram nenhum novo dispositivo de áudio)     usbipd: info: escutando em 0.0.0.0:3240     usbipd: erro: socket: ::: 3240: 97 (Família de endereços não suportada pelo protocolo)

Eu não olhei para o erro acima e não sei se é relevante, mas estou assumindo que não é.

Depois liguei o meu dispositivo usb:

sudo usbip bind -b 1-1

Em seguida, no cliente, anexei o dispositivo:

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

As seguintes mensagens foram mostradas no servidor para usbipd (tentei conectar duas vezes):

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 mostra que o cliente não anexou o dispositivo usb. Os erros relevantes no cliente são:

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

O cliente e o servidor estão executando estas versões:

sudo pacman -Qi usbip Nome: usbip Versão: 4.18-1

Linux 4.18.6-arch1-1-ARCH # 1 SMP PREEMPRE Quarta 5 11:54:09 UTC 2018 x86_64 GNU / Linux

Eu tenho a ajuda da instalação daqui: Tutorial - USB / IP »Revista Linux link

UPDATE: encontrei instruções melhores aqui: link

cliente:

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

servidor:

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

cliente:

sudo lsusb

(o dispositivo usb esperado não é mostrado e também as ferramentas multimídia do KDE não mostram nenhum novo dispositivo de áudio)

O diário no cliente mostra que o dispositivo usb está localizado, mas não está vinculado e não está claro para mim o motivo.

# 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>
    
por MountainX 23.09.2018 / 10:37

0 respostas

Tags