1 Temat przez Wally

  • Wally
  • Wally
  • Użytkownik
  • Nieaktywny
  • Zarejestrowany: 2013-01-21
  • Posty: 202

Temat: LCD po usbip pomiędzy dwoma Gargoyle?

Próbuję podłączyć wyświetlacz LCD (ramka na st2205) poprzez usbip (wiem, kombinuję wink )i jeden ruter ładnie binduje urządzenie a drugi ładnie robi attach

[  110.560000] IMQ driver loaded successfully. (numdevs = 1, numqueues = 1)
[  241.450000] vhci_hcd vhci_hcd: rhport(0) sockfd(3) devid(65538) speed(2)
[  241.450000] vhci_hcd: changed 1

ale teraz pytanie - jak to ładnie podłączyć pod LCD4LINUX?

Wally

2 Odpowiedź przez Cezary

  • Skąd: Warszawa
  • Zarejestrowany: 2006-02-25
  • Posty: 115,883

Odp: LCD po usbip pomiędzy dwoma Gargoyle?

Tzn? Na jednym serwer, na drugim klient i tyle. Choć ciekawe czy zadziała to w ramką. Zrób lsusb na drugim i zobacz czy jest urządzenie.

Masz niepotrzebny router, uszkodzony czy nie - chętnie przygarnę go.

Cezary's Strona

3 Odpowiedź przez Cezary

  • Skąd: Warszawa
  • Zarejestrowany: 2006-02-25
  • Posty: 115,883

Odp: LCD po usbip pomiędzy dwoma Gargoyle?

Tzn? Na jednym serwer, na drugim klient i tyle. Choć ciekawe czy zadziała to w ramką. Zrób lsusb na drugim i zobacz czy jest urządzenie.

Masz niepotrzebny router, uszkodzony czy nie - chętnie przygarnę go.

Cezary's Strona

4 Odpowiedź przez Wally

  • Wally
  • Wally
  • Użytkownik
  • Nieaktywny
  • Zarejestrowany: 2013-01-21
  • Posty: 202

Odp: LCD po usbip pomiędzy dwoma Gargoyle?

No właśnie - na kliencie jest tylko:

Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. USB-2.0 4-Port HUB
Bus 001 Device 004: ID 12d1:1506 Huawei Technologies Co., Ltd. E398 LTE/UMTS/GSM Modem/Networkcard
Bus 001 Device 005: ID 154b:005b PNY
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Tak jakby driver vhci_vhd nie wystawiał urządzenia. Na pewno na kliencie wystarczy usbip, kmod-usbip, kmod-usbip-client, usbip-client?

Wally

5 Odpowiedź przez Cezary

  • Skąd: Warszawa
  • Zarejestrowany: 2006-02-25
  • Posty: 115,883

Odp: LCD po usbip pomiędzy dwoma Gargoyle?

Na pewno podłączyłeś usbip na drugim urządzeniu?

Masz niepotrzebny router, uszkodzony czy nie - chętnie przygarnę go.

Cezary's Strona

6 Odpowiedź przez Wally (edytowany przez Wally 2013-04-12 19:43:43)

  • Wally
  • Wally
  • Użytkownik
  • Nieaktywny
  • Zarejestrowany: 2013-01-21
  • Posty: 202

Odp: LCD po usbip pomiędzy dwoma Gargoyle?

Dobre smile Jest podłączone. Bez tego nie byłoby co bindować.

# usbip list -r 192.168.1.10
Exportable USB devices
======================
 - 192.168.1.10
        1-1: GEMBIRD : unknown product (1908:0102)
           : /sys/devices/platform/ehci-platform/usb1/1-1
           : Vendor Specific Class / Vendor Specific Subclass / Vendor Specific Protocol (ff/ff/ff)
           :  0 - Vendor Specific Class / unknown subclass / unknown protocol (ff/00/00)

a na drugim:

# usbip list -l
Local USB devices
=================
 - busid 1-1 (1908:0102)
         1-1:1.0 -> usbip-host

Chyba problem leży w driverze - podczas attacha debug wyrzuca na końcu:

libusbip: debug: vhci_driver.c:475:[usbip_vhci_attach_device2] attached port: 0
usbip: error: record connection

Pełny debug:

# usbip --debug attach -h 192.168.1.10 -b 1-1
usbip: debug: usbip.c:134:[run_command] running command: `attach'
libusbip: debug: vhci_driver.c:264:[get_nports] name: status  path: /sys/devices/platform/vhci_hcd/status  len: 377  method: 1  value: prt sta spd bus dev socket           local_busid
000 004 000 000 000 0000000000000000 0-0
001 004 000 000 000 0000000000000000 0-0
002 004 000 000 000 0000000000000000 0-0
003 004 000 000 000 0000000000000000 0-0
004 004 000 000 000 0000000000000000 0-0
005 004 000 000 000 0000000000000000 0-0
006 004 000 000 000 0000000000000000 0-0
007 004 000 000 000 0000000000000000 0-0

libusbip: debug: vhci_driver.c:356:[usbip_vhci_driver_open] available ports: 8
libusbip: debug: vhci_driver.c:166:[search_class_for_usbip_device] class: bdi
libusbip: debug: vhci_driver.c:174:[search_class_for_usbip_device] cdev: 0
libusbip: debug: vhci_driver.c:174:[search_class_for_usbip_device] cdev: 0
libusbip: debug: vhci_driver.c:174:[search_class_for_usbip_device] cdev: 1
libusbip: debug: vhci_driver.c:174:[search_class_for_usbip_device] cdev: 16
libusbip: debug: vhci_driver.c:174:[search_class_for_usbip_device] cdev: 2
libusbip: debug: vhci_driver.c:174:[search_class_for_usbip_device] cdev: 3
libusbip: debug: vhci_driver.c:174:[search_class_for_usbip_device] cdev: 4
libusbip: debug: vhci_driver.c:174:[search_class_for_usbip_device] cdev: 5
libusbip: debug: vhci_driver.c:174:[search_class_for_usbip_device] cdev: default
libusbip: debug: vhci_driver.c:174:[search_class_for_usbip_device] cdev: mtd-romap
libusbip: debug: vhci_driver.c:174:[search_class_for_usbip_device] cdev: mtd-rwmap
libusbip: debug: vhci_driver.c:174:[search_class_for_usbip_device] cdev: mtd-unmap
libusbip: debug: vhci_driver.c:166:[search_class_for_usbip_device] class: block
libusbip: debug: vhci_driver.c:174:[search_class_for_usbip_device] cdev: mtdblock0
libusbip: debug: vhci_driver.c:174:[search_class_for_usbip_device] cdev: mtdblock1
libusbip: debug: vhci_driver.c:174:[search_class_for_usbip_device] cdev: mtdblock2
libusbip: debug: vhci_driver.c:174:[search_class_for_usbip_device] cdev: mtdblock3
libusbip: debug: vhci_driver.c:174:[search_class_for_usbip_device] cdev: mtdblock4
libusbip: debug: vhci_driver.c:174:[search_class_for_usbip_device] cdev: mtdblock5
libusbip: debug: vhci_driver.c:174:[search_class_for_usbip_device] cdev: sda
libusbip: debug: vhci_driver.c:174:[search_class_for_usbip_device] cdev: sdb
libusbip: debug: vhci_driver.c:166:[search_class_for_usbip_device] class: bsg
libusbip: debug: vhci_driver.c:174:[search_class_for_usbip_device] cdev: 0:0:0
libusbip: debug: vhci_driver.c:174:[search_class_for_usbip_device] cdev: 0:0:0
libusbip: debug: vhci_driver.c:166:[search_class_for_usbip_device] class: firmware
libusbip: debug: vhci_driver.c:166:[search_class_for_usbip_device] class: gpio
libusbip: debug: vhci_driver.c:174:[search_class_for_usbip_device] cdev: gpio21
libusbip: debug: vhci_driver.c:174:[search_class_for_usbip_device] cdev: gpio22
libusbip: debug: vhci_driver.c:174:[search_class_for_usbip_device] cdev: gpiochip0
libusbip: debug: vhci_driver.c:166:[search_class_for_usbip_device] class: ieee80211
libusbip: debug: vhci_driver.c:174:[search_class_for_usbip_device] cdev: phy0
libusbip: debug: vhci_driver.c:174:[search_class_for_usbip_device] cdev: phy1
libusbip: debug: vhci_driver.c:166:[search_class_for_usbip_device] class: leds
libusbip: debug: vhci_driver.c:174:[search_class_for_usbip_device] cdev: ath9k-phy0
libusbip: debug: vhci_driver.c:174:[search_class_for_usbip_device] cdev: ath9k-phy1
libusbip: debug: vhci_driver.c:174:[search_class_for_usbip_device] cdev: blue:qss
libusbip: debug: vhci_driver.c:174:[search_class_for_usbip_device] cdev: blue:system
libusbip: debug: vhci_driver.c:174:[search_class_for_usbip_device] cdev: blue:wlan2g
libusbip: debug: vhci_driver.c:174:[search_class_for_usbip_device] cdev: green:usb1
libusbip: debug: vhci_driver.c:174:[search_class_for_usbip_device] cdev: green:usb2
libusbip: debug: vhci_driver.c:166:[search_class_for_usbip_device] class: mdio_bus
libusbip: debug: vhci_driver.c:174:[search_class_for_usbip_device] cdev: ag71xx-mdio.0
libusbip: debug: vhci_driver.c:166:[search_class_for_usbip_device] class: mem
libusbip: debug: vhci_driver.c:174:[search_class_for_usbip_device] cdev: full
libusbip: debug: vhci_driver.c:174:[search_class_for_usbip_device] cdev: kmsg
libusbip: debug: vhci_driver.c:174:[search_class_for_usbip_device] cdev: mem
libusbip: debug: vhci_driver.c:174:[search_class_for_usbip_device] cdev: null
libusbip: debug: vhci_driver.c:174:[search_class_for_usbip_device] cdev: port
libusbip: debug: vhci_driver.c:174:[search_class_for_usbip_device] cdev: random
libusbip: debug: vhci_driver.c:174:[search_class_for_usbip_device] cdev: urandom
libusbip: debug: vhci_driver.c:174:[search_class_for_usbip_device] cdev: zero
libusbip: debug: vhci_driver.c:166:[search_class_for_usbip_device] class: misc
libusbip: debug: vhci_driver.c:174:[search_class_for_usbip_device] cdev: fuse
libusbip: debug: vhci_driver.c:174:[search_class_for_usbip_device] cdev: tun
libusbip: debug: vhci_driver.c:174:[search_class_for_usbip_device] cdev: watchdog
libusbip: debug: vhci_driver.c:166:[search_class_for_usbip_device] class: mtd
libusbip: debug: vhci_driver.c:174:[search_class_for_usbip_device] cdev: mtd0
libusbip: debug: vhci_driver.c:174:[search_class_for_usbip_device] cdev: mtd0ro
libusbip: debug: vhci_driver.c:174:[search_class_for_usbip_device] cdev: mtd1
libusbip: debug: vhci_driver.c:174:[search_class_for_usbip_device] cdev: mtd1ro
libusbip: debug: vhci_driver.c:174:[search_class_for_usbip_device] cdev: mtd2
libusbip: debug: vhci_driver.c:174:[search_class_for_usbip_device] cdev: mtd2ro
libusbip: debug: vhci_driver.c:174:[search_class_for_usbip_device] cdev: mtd3
libusbip: debug: vhci_driver.c:174:[search_class_for_usbip_device] cdev: mtd3ro
libusbip: debug: vhci_driver.c:174:[search_class_for_usbip_device] cdev: mtd4
libusbip: debug: vhci_driver.c:174:[search_class_for_usbip_device] cdev: mtd4ro
libusbip: debug: vhci_driver.c:174:[search_class_for_usbip_device] cdev: mtd5
libusbip: debug: vhci_driver.c:174:[search_class_for_usbip_device] cdev: mtd5ro
libusbip: debug: vhci_driver.c:166:[search_class_for_usbip_device] class: net
libusbip: debug: vhci_driver.c:174:[search_class_for_usbip_device] cdev: 3g-wan
libusbip: debug: vhci_driver.c:174:[search_class_for_usbip_device] cdev: br-lan
libusbip: debug: vhci_driver.c:174:[search_class_for_usbip_device] cdev: eth0
libusbip: debug: vhci_driver.c:174:[search_class_for_usbip_device] cdev: eth0.1
libusbip: debug: vhci_driver.c:174:[search_class_for_usbip_device] cdev: eth0.2
libusbip: debug: vhci_driver.c:174:[search_class_for_usbip_device] cdev: imq0
libusbip: debug: vhci_driver.c:174:[search_class_for_usbip_device] cdev: lo
libusbip: debug: vhci_driver.c:174:[search_class_for_usbip_device] cdev: wlan0
libusbip: debug: vhci_driver.c:174:[search_class_for_usbip_device] cdev: wwan0
libusbip: debug: vhci_driver.c:166:[search_class_for_usbip_device] class: pci_bus
libusbip: debug: vhci_driver.c:174:[search_class_for_usbip_device] cdev: 00
libusbip: debug: vhci_driver.c:166:[search_class_for_usbip_device] class: ppp
libusbip: debug: vhci_driver.c:174:[search_class_for_usbip_device] cdev: ppp
libusbip: debug: vhci_driver.c:166:[search_class_for_usbip_device] class: scsi_device
libusbip: debug: vhci_driver.c:174:[search_class_for_usbip_device] cdev: 0:0:0
libusbip: debug: vhci_driver.c:174:[search_class_for_usbip_device] cdev: 0:0:0
libusbip: debug: vhci_driver.c:166:[search_class_for_usbip_device] class: scsi_disk
libusbip: debug: vhci_driver.c:174:[search_class_for_usbip_device] cdev: 0:0:0
libusbip: debug: vhci_driver.c:174:[search_class_for_usbip_device] cdev: 0:0:0
libusbip: debug: vhci_driver.c:166:[search_class_for_usbip_device] class: scsi_host
libusbip: debug: vhci_driver.c:174:[search_class_for_usbip_device] cdev: host2
libusbip: debug: vhci_driver.c:174:[search_class_for_usbip_device] cdev: host3
libusbip: debug: vhci_driver.c:166:[search_class_for_usbip_device] class: spi_master
libusbip: debug: vhci_driver.c:174:[search_class_for_usbip_device] cdev: spi0
libusbip: debug: vhci_driver.c:166:[search_class_for_usbip_device] class: tty
libusbip: debug: vhci_driver.c:174:[search_class_for_usbip_device] cdev: console
libusbip: debug: vhci_driver.c:174:[search_class_for_usbip_device] cdev: ptmx
libusbip: debug: vhci_driver.c:174:[search_class_for_usbip_device] cdev: tty
libusbip: debug: vhci_driver.c:174:[search_class_for_usbip_device] cdev: ttyS0
libusbip: debug: vhci_driver.c:174:[search_class_for_usbip_device] cdev: ttyS1
libusbip: debug: vhci_driver.c:174:[search_class_for_usbip_device] cdev: ttyS10
libusbip: debug: vhci_driver.c:174:[search_class_for_usbip_device] cdev: ttyS11
libusbip: debug: vhci_driver.c:174:[search_class_for_usbip_device] cdev: ttyS12
libusbip: debug: vhci_driver.c:174:[search_class_for_usbip_device] cdev: ttyS13
libusbip: debug: vhci_driver.c:174:[search_class_for_usbip_device] cdev: ttyS14
libusbip: debug: vhci_driver.c:174:[search_class_for_usbip_device] cdev: ttyS15
libusbip: debug: vhci_driver.c:174:[search_class_for_usbip_device] cdev: ttyS2
libusbip: debug: vhci_driver.c:174:[search_class_for_usbip_device] cdev: ttyS3
libusbip: debug: vhci_driver.c:174:[search_class_for_usbip_device] cdev: ttyS4
libusbip: debug: vhci_driver.c:174:[search_class_for_usbip_device] cdev: ttyS5
libusbip: debug: vhci_driver.c:174:[search_class_for_usbip_device] cdev: ttyS6
libusbip: debug: vhci_driver.c:174:[search_class_for_usbip_device] cdev: ttyS7
libusbip: debug: vhci_driver.c:174:[search_class_for_usbip_device] cdev: ttyS8
libusbip: debug: vhci_driver.c:174:[search_class_for_usbip_device] cdev: ttyS9
libusbip: debug: vhci_driver.c:174:[search_class_for_usbip_device] cdev: ttyUSB0
libusbip: debug: vhci_driver.c:174:[search_class_for_usbip_device] cdev: ttyUSB1
libusbip: debug: vhci_driver.c:174:[search_class_for_usbip_device] cdev: ttyUSB2
libusbip: debug: vhci_driver.c:166:[search_class_for_usbip_device] class: block
libusbip: debug: vhci_driver.c:174:[search_class_for_usbip_device] cdev: mtdblock0
libusbip: debug: vhci_driver.c:174:[search_class_for_usbip_device] cdev: mtdblock1
libusbip: debug: vhci_driver.c:174:[search_class_for_usbip_device] cdev: mtdblock2
libusbip: debug: vhci_driver.c:174:[search_class_for_usbip_device] cdev: mtdblock3
libusbip: debug: vhci_driver.c:174:[search_class_for_usbip_device] cdev: mtdblock4
libusbip: debug: vhci_driver.c:174:[search_class_for_usbip_device] cdev: mtdblock5
libusbip: debug: vhci_driver.c:174:[search_class_for_usbip_device] cdev: sda
libusbip: debug: vhci_driver.c:174:[search_class_for_usbip_device] cdev: sdb
libusbip: debug: vhci_driver.c:244:[refresh_imported_device_list] name: status  path: /sys/devices/platform/vhci_hcd/status  len: 377  method: 1  value: prt sta spd bus dev socket           local_busid
000 004 000 000 000 0000000000000000 0-0
001 004 000 000 000 0000000000000000 0-0
002 004 000 000 000 0000000000000000 0-0
003 004 000 000 000 0000000000000000 0-0
004 004 000 000 000 0000000000000000 0-0
005 004 000 000 000 0000000000000000 0-0
006 004 000 000 000 0000000000000000 0-0
007 004 000 000 000 0000000000000000 0-0

libusbip: debug: vhci_driver.c:79:[parse_status] port 0 status 4 speed 0 devid 0
libusbip: debug: vhci_driver.c:80:[parse_status] socket 0 lbusid 0000000000000000
libusbip: debug: vhci_driver.c:79:[parse_status] port 1 status 4 speed 0 devid 0
libusbip: debug: vhci_driver.c:80:[parse_status] socket 0 lbusid 0000000000000000
libusbip: debug: vhci_driver.c:79:[parse_status] port 2 status 4 speed 0 devid 0
libusbip: debug: vhci_driver.c:80:[parse_status] socket 0 lbusid 0000000000000000
libusbip: debug: vhci_driver.c:79:[parse_status] port 3 status 4 speed 0 devid 0
libusbip: debug: vhci_driver.c:80:[parse_status] socket 0 lbusid 0000000000000000
libusbip: debug: vhci_driver.c:79:[parse_status] port 4 status 4 speed 0 devid 0
libusbip: debug: vhci_driver.c:80:[parse_status] socket 0 lbusid 0000000000000000
libusbip: debug: vhci_driver.c:79:[parse_status] port 5 status 4 speed 0 devid 0
libusbip: debug: vhci_driver.c:80:[parse_status] socket 0 lbusid 0000000000000000
libusbip: debug: vhci_driver.c:79:[parse_status] port 6 status 4 speed 0 devid 0
libusbip: debug: vhci_driver.c:80:[parse_status] socket 0 lbusid 0000000000000000
libusbip: debug: vhci_driver.c:79:[parse_status] port 7 status 4 speed 0 devid 0
libusbip: debug: vhci_driver.c:80:[parse_status] socket 0 lbusid 0000000000000000
libusbip: debug: vhci_driver.c:115:[parse_status] exit
libusbip: debug: vhci_driver.c:467:[usbip_vhci_attach_device2] writing: 0 3 65538 2
libusbip: debug: vhci_driver.c:475:[usbip_vhci_attach_device2] attached port: 0
usbip: error: record connection

EDIT:
Podłączyłem brelok bezpośrednio pod ruter z LCD4LINUX i nadal nie ma urządzenia (?) jest za to komunikat:

kern.info kernel: [ 9049.140000] usb 1-1.2.3: new full-speed USB device number 9 using ehci-platform
user.notice usb-modeswitch: 1-1.2.3:1.0: Manufacturer=hackfin Product=USB-Display Serial=001

Potrzebuję podpowiedzi, jaki port wpisać w konfigu (nie pojawił się żaden nowy dysk)?

Wally

7 Odpowiedź przez Wally

  • Wally
  • Wally
  • Użytkownik
  • Nieaktywny
  • Zarejestrowany: 2013-01-21
  • Posty: 202

Odp: LCD po usbip pomiędzy dwoma Gargoyle?

OK, nie działa bo nie ładuje sterownika. Jednak musi być DPF a nie st2205 - http://forum.openwrt.org/viewtopic.php?id=34133
A w repo niestety nie ma i tu mała prośba o kompilację LCD4Linux-dpf (jak opisane w powyższym linku).

Wally