Problems with one USB devices

Submitted by hspjanssen on #1

Hello,

I have a problem with one USB device. It has worked for some days, but now for some reason, the device is recognized as an USB device, but after a few seconds it is gone. This is the "dmesg" log.

[25830.674061] vhci_hcd vhci_hcd: pdev(0) rhport(2) sockfd(13)
[25830.674064] vhci_hcd vhci_hcd: devid(6) speed(2) speed_str(full-speed)
[25830.936344] usb 3-3: new full-speed USB device number 10 using vhci_hcd
[25831.060315] usb 3-3: SetAddress Request (10) to port 2
[25831.148299] usb 3-3: New USB device found, idVendor=10ac, idProduct=0102
[25831.148302] usb 3-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[25831.148304] usb 3-3: Product: TUSB3410 Boot Device
[25831.148305] usb 3-3: Manufacturer: Texas Instruments
[25831.148307] usb 3-3: SerialNumber: TUSB3410
[25831.157644] ti_usb_3410_5052 3-3:1.0: TI USB 3410 1 port adapter converter detected
[25831.157666] ti_usb_3410_5052: probe of 3-3:1.0 failed with error -5
[25831.162633] ti_usb_3410_5052 3-3:2.0: TI USB 3410 1 port adapter converter detected
[25831.162810] usb 3-3: TI USB 3410 1 port adapter converter now attached to ttyUSB1
[25845.912222] vhci_hcd: dequeue a urb ffff93b9b4c26cc0
[25845.912225] vhci_hcd: device ffff93b9b84ca480 seems to be still connected
[25845.912253] vhci_hcd: unlink->seqnum 2041865
[25845.912254] vhci_hcd: the urb (seqnum 2041865) was already given back
[25845.917059] vhci_hcd: dequeue a urb ffff93b9b53ba9c0
[25845.917060] vhci_hcd: device ffff93b9b84ca480 seems to be still connected
[25845.917077] vhci_hcd: unlink->seqnum 2041868
[25845.917078] vhci_hcd: the urb (seqnum 2041868) was already given back
[25851.912205] vhci_hcd: dequeue a urb ffff93b9b4c26cc0
[25851.912208] vhci_hcd: device ffff93b9b84ca480 seems to be still connected
[25851.912239] vhci_hcd: unlink->seqnum 2042376
[25851.912240] vhci_hcd: the urb (seqnum 2042376) was already given back
[25851.916980] vhci_hcd: dequeue a urb ffff93b9b53ba9c0
[25851.916982] vhci_hcd: device ffff93b9b84ca480 seems to be still connected
[25851.917000] vhci_hcd: unlink->seqnum 2042379
[25851.917001] vhci_hcd: the urb (seqnum 2042379) was already given back
[25859.309566] ti_usb_3410_5052_1 ttyUSB1: ti_open - cannot clear output buffers, -32
[25859.309583] vhci_hcd: dequeue a urb ffff93b9b53ba9c0
[25859.309585] vhci_hcd: device ffff93b9b84ca480 seems to be still connected
[25859.309609] vhci_hcd: unlink->seqnum 2042973
[25859.309610] vhci_hcd: the urb (seqnum 2042973) was already given back
[25859.427813] vhci_hcd: connection closed
[25859.427846] vhci_hcd: stop threads
[25859.427847] vhci_hcd: release socket
[25859.427851] vhci_hcd: disconnect device
[25859.427880] usb 3-3: USB disconnect, device number 10
[25859.428021] ti_usb_3410_5052_1 ttyUSB1: TI USB 3410 1 port adapter converter now disconnected from ttyUSB1
[25859.428030] ti_usb_3410_5052 3-3:2.0: device disconnected

I see that the device is disconnected, but why?

I am using Debian 8.10 with kernel 4.9.0-0.bpo.4-amd64 #1 SMP Debian 4.9.65-3+deb9u1~bpo8+1 (2017-12-23) x86_64 GNU/Linux

Any idea?

Submitted by Michael on Mon, 2018/01/22 - 18:43

#2

Is there anything in the syslog about this time? the virtulhere client will write to syslog (if console) or to the system message dialog box in the USB Hubs menu for the GUI client.

Submitted by hspjanssen on Mon, 2018/01/22 - 19:58

#3

Hello,

Just reproduced the issue, this is the log of syslog on the client side of virtualhere:
Jan 22 10:40:12 domoticz kernel: [ 63.070534] usb 3-3: Product: TUSB3410 Boot Device
Jan 22 10:40:12 domoticz kernel: [ 63.070536] usb 3-3: Manufacturer: Texas Instruments
Jan 22 10:40:12 domoticz kernel: [ 63.070537] usb 3-3: SerialNumber: TUSB3410
Jan 22 10:40:12 domoticz kernel: [ 63.074126] ti_usb_3410_5052 3-3:1.0: TI USB 3410 1 port adapter converter detected
Jan 22 10:40:12 domoticz kernel: [ 63.076561] usb 3-3: firmware: failed to load ti_usb-v10ac-p0102.fw (-2)
Jan 22 10:40:12 domoticz kernel: [ 63.076565] usb 3-3: Direct firmware load for ti_usb-v10ac-p0102.fw failed with error -2
Jan 22 10:40:12 domoticz kernel: [ 63.077108] usb 3-3: firmware: direct-loading firmware ti_3410.fw
Jan 22 10:40:14 domoticz kernel: [ 64.524225] usb usb3-port3: Cannot enable. Maybe the USB cable is bad?
Jan 22 10:40:15 domoticz kernel: [ 65.416210] usb usb3-port3: Cannot enable. Maybe the USB cable is bad?
Jan 22 10:40:15 domoticz kernel: [ 66.308203] usb usb3-port3: Cannot enable. Maybe the USB cable is bad?
Jan 22 10:40:16 domoticz kernel: [ 67.200222] usb usb3-port3: Cannot enable. Maybe the USB cable is bad?
Jan 22 10:40:16 domoticz kernel: [ 67.200256] ti_usb_3410_5052: probe of 3-3:1.0 failed with error -5
Jan 22 10:40:16 domoticz kernel: [ 67.200334] usb 3-3: USB disconnect, device number 5
Jan 22 10:40:17 domoticz kernel: [ 68.092252] usb usb3-port3: Cannot enable. Maybe the USB cable is bad?
Jan 22 10:40:18 domoticz VirtualHere Client: Error 'Name does not resolve' getaddrinfo failed for virtualhere_01:7575
Jan 22 10:40:18 domoticz VirtualHere Client: Error 'Name does not resolve' getaddrinfo failed for virtualhere_02:7575
Jan 22 10:40:18 domoticz kernel: [ 68.984201] usb usb3-port3: Cannot enable. Maybe the USB cable is bad?
Jan 22 10:40:19 domoticz kernel: [ 69.876183] usb usb3-port3: Cannot enable. Maybe the USB cable is bad?
Jan 22 10:40:20 domoticz kernel: [ 70.768185] usb usb3-port3: Cannot enable. Maybe the USB cable is bad?
Jan 22 10:40:20 domoticz kernel: [ 70.768202] usb usb3-port3: unable to enumerate USB device
Jan 22 10:40:48 domoticz VirtualHere Client: Error 'Name does not resolve' getaddrinfo failed for virtualhere_02:7575
Jan 22 10:40:48 domoticz VirtualHere Client: Error 'Name does not resolve' getaddrinfo failed for virtualhere_01:7575
Jan 22 10:41:18 domoticz VirtualHere Client: Error 'Name does not resolve' getaddrinfo failed for virtualhere_02:7575
Jan 22 10:41:18 domoticz VirtualHere Client: Error 'Name does not resolve' getaddrinfo failed for virtualhere_01:7575
Jan 22 10:41:48 domoticz VirtualHere Client: Error 'Name does not resolve' getaddrinfo failed for virtualhere_02:7575
Jan 22 10:41:48 domoticz VirtualHere Client: Error 'Name does not resolve' getaddrinfo failed for virtualhere_01:7575
Jan 22 10:42:18 domoticz VirtualHere Client: Error 'Name does not resolve' getaddrinfo failed for virtualhere_01:7575
Jan 22 10:42:18 domoticz VirtualHere Client: Error 'Name does not resolve' getaddrinfo failed for virtualhere_02:7575
Jan 22 10:42:48 domoticz VirtualHere Client: Error 'Name does not resolve' getaddrinfo failed for virtualhere_01:7575
Jan 22 10:42:48 domoticz VirtualHere Client: Error 'Name does not resolve' getaddrinfo failed for virtualhere_02:7575
Jan 22 10:43:18 domoticz VirtualHere Client: Error 'Name does not resolve' getaddrinfo failed for virtualhere_01:7575
Jan 22 10:43:18 domoticz VirtualHere Client: Error 'Name does not resolve' getaddrinfo failed for virtualhere_02:7575
Jan 22 10:43:48 domoticz VirtualHere Client: Error 'Name does not resolve' getaddrinfo failed for virtualhere_02:7575
Jan 22 10:43:48 domoticz VirtualHere Client: Error 'Name does not resolve' getaddrinfo failed for virtualhere_01:7575
Jan 22 10:44:18 domoticz VirtualHere Client: Error 'Name does not resolve' getaddrinfo failed for virtualhere_02:7575
Jan 22 10:44:18 domoticz VirtualHere Client: Error 'Name does not resolve' getaddrinfo failed for virtualhere_01:7575
Jan 22 10:44:48 domoticz VirtualHere Client: Error 'Name does not resolve' getaddrinfo failed for virtualhere_01:7575
Jan 22 10:44:48 domoticz VirtualHere Client: Error 'Name does not resolve' getaddrinfo failed for virtualhere_02:7575
Jan 22 10:45:18 domoticz VirtualHere Client: Error 'Name does not resolve' getaddrinfo failed for virtualhere_02:7575
Jan 22 10:45:18 domoticz VirtualHere Client: Error 'Name does not resolve' getaddrinfo failed for virtualhere_01:7575
Jan 22 10:45:48 domoticz VirtualHere Client: Error 'Name does not resolve' getaddrinfo failed for virtualhere_02:7575
Jan 22 10:45:48 domoticz VirtualHere Client: Error 'Name does not resolve' getaddrinfo failed for virtualhere_01:7575
Jan 22 10:46:18 domoticz VirtualHere Client: Error 'Name does not resolve' getaddrinfo failed for virtualhere_01:7575
Jan 22 10:46:18 domoticz VirtualHere Client: Error 'Name does not resolve' getaddrinfo failed for virtualhere_02:7575
Jan 22 10:46:48 domoticz VirtualHere Client: Error 'Name does not resolve' getaddrinfo failed for virtualhere_02:7575
Jan 22 10:46:48 domoticz VirtualHere Client: Error 'Name does not resolve' getaddrinfo failed for virtualhere_01:7575
Jan 22 10:47:18 domoticz VirtualHere Client: Error 'Name does not resolve' getaddrinfo failed for virtualhere_02:7575
Jan 22 10:47:18 domoticz VirtualHere Client: Error 'Name does not resolve' getaddrinfo failed for virtualhere_01:7575
Jan 22 10:47:48 domoticz VirtualHere Client: Error 'Name does not resolve' getaddrinfo failed for virtualhere_02:7575
Jan 22 10:47:48 domoticz VirtualHere Client: Error 'Name does not resolve' getaddrinfo failed for virtualhere_01:7575
Jan 22 10:48:18 domoticz VirtualHere Client: Error 'Name does not resolve' getaddrinfo failed for virtualhere_02:7575
Jan 22 10:48:18 domoticz VirtualHere Client: Error 'Name does not resolve' getaddrinfo failed for virtualhere_01:7575
Jan 22 10:48:48 domoticz VirtualHere Client: Error 'Name does not resolve' getaddrinfo failed for virtualhere_01:7575
Jan 22 10:48:48 domoticz VirtualHere Client: Error 'Name does not resolve' getaddrinfo failed for virtualhere_02:7575
Jan 22 10:49:18 domoticz VirtualHere Client: Error 'Name does not resolve' getaddrinfo failed for virtualhere_02:7575
Jan 22 10:49:18 domoticz VirtualHere Client: Error 'Name does not resolve' getaddrinfo failed for virtualhere_01:7575
Jan 22 10:49:48 domoticz VirtualHere Client: Error 'Name does not resolve' getaddrinfo failed for virtualhere_01:7575
Jan 22 10:49:48 domoticz VirtualHere Client: Error 'Name does not resolve' getaddrinfo failed for virtualhere_02:7575
Jan 22 10:50:18 domoticz VirtualHere Client: Error 'Name does not resolve' getaddrinfo failed for virtualhere_02:7575
Jan 22 10:50:18 domoticz VirtualHere Client: Error 'Name does not resolve' getaddrinfo failed for virtualhere_01:7575
Jan 22 10:50:48 domoticz VirtualHere Client: Error 'Name does not resolve' getaddrinfo failed for virtualhere_02:7575
Jan 22 10:50:48 domoticz VirtualHere Client: Error 'Name does not resolve' getaddrinfo failed for virtualhere_01:7575

Just for information, the unit with the issue is on host virtualhere_01, this is the unit in the log:
Product: TUSB3410 Boot Device
[25831.148305] usb 3-3: Manufacturer: Texas Instruments
[25831.148307] usb 3-3: SerialNumber: TUSB3410
[25831.157644] ti_usb_3410_5052 3-3:1.0: TI USB 3410 1 port adapter converter detected

I connected this unit directly to a host with USB, then the unit is working without problems.

I have an other unit (virtualhere_02) connected, this unit is working properly.

Thanks

Submitted by Michael on Mon, 2018/01/22 - 20:04

#4

OK, so it seems that when that device is connected it needs firmware uploaded. And its not able to find the firmware (thats what error -2 means). Can you see if you can find the file ti_usb-v10ac-p0102.fw on virtualhere_02 as i think it might be missing from virtualhere_01 server.

Submitted by hspjanssen on Mon, 2018/01/22 - 20:14

#5

I saw that, but the strange thing is, that this firmware is not required when I am connecting the unit directly to the the virtualhere_01 server, the unit is then working ok. Searched the internet for it, but can not find this. I think I will try to request this at Texas Instruments.

Thanks

Submitted by hspjanssen on Mon, 2018/01/22 - 20:22

#6

For your information, a different device is connected to virtualhere_02, but I only mentioned that that one was working, because I saw this error in the log " Error 'Name does not resolve' getaddrinfo failed for virtualhere_02"

Submitted by Michael on Mon, 2018/01/22 - 20:32

#7

OK, perhaps this device needs the USB RESET command skipped then. I thought you said it was working on the other server... so if this is not the case then lets try removing the reset.

Can you stop the virtualhere server process.
edit the server config.ini file and add the line

onReset.10ac.0102=

then save the config.ini file
now start the virtualhere server again and unplug and replug the serial device.

Now try to use it again via the virtualhere client.

On the server log it should say custom Event handler onReset.10ac.0102 "" executed

does it work ok now?

Submitted by hspjanssen on Mon, 2018/01/22 - 20:39

#8

Hello,

I will try that, but for your information, an other USB device is running on the virtualhere server 01 without problems. So, I have two USB devices connected on virtual server 01 (one of them with the issue), an one USB device on virtual server 02.

When I add the information (onReset) above, it will also affect the other device on the server I assume? Is it possible to configure the onReset only for the device with issues?

Kind regards

Submitted by Michael on Mon, 2018/01/22 - 21:04

#9

If the other device has the same vendor id and product id (i.e its a duplicate device) then the reset will also be skipped for that as well, but it should be ok.

Submitted by hspjanssen on Tue, 2018/01/23 - 04:49

#10

Unfortunately, it does not work

On the server side:
Jan 22 19:26:03 virtualhere_01 vhusbdarm[660]: Executed "" for onReset.10ac.0102
Jan 22 19:26:03 virtualhere_01 vhusbdarm[660]: Device 115 [10ac:0102] BOUND to connection 1
Jan 22 19:26:05 virtualhere_01 kernel: [ 53.688449] usbcore: registered new interface driver usbserial
Jan 22 19:26:05 virtualhere_01 kernel: [ 53.688541] usbcore: registered new interface driver usbserial_generic
Jan 22 19:26:05 virtualhere_01 kernel: [ 53.688629] usbserial: USB Serial support registered for generic
Jan 22 19:26:05 virtualhere_01 kernel: [ 53.692920] usbcore: registered new interface driver ti_usb_3410_5052
Jan 22 19:26:05 virtualhere_01 kernel: [ 53.693057] usbserial: USB Serial support registered for TI USB 3410 1 port adapter
Jan 22 19:26:05 virtualhere_01 kernel: [ 53.693157] usbserial: USB Serial support registered for TI USB 5052 2 port adapter
Jan 22 19:26:11 virtualhere_01 crontab[880]: (pi) BEGIN EDIT (pi)
Jan 22 19:26:13 virtualhere_01 kernel: [ 62.040368] random: crng init done
Jan 22 19:26:19 virtualhere_01 crontab[880]: (pi) END EDIT (pi)
Jan 22 19:26:25 virtualhere_01 vhusbdarm[660]: Error 22 discarding urb 0x7ace90 for device /sys/bus/usb/devices/1-1.4, Invalid argument (abort endpoint)
Jan 22 19:26:25 virtualhere_01 vhusbdarm[660]: Error 22 discarding urb 0x7afea0 for device /sys/bus/usb/devices/1-1.4, Invalid argument (abort endpoint)
Jan 22 19:26:25 virtualhere_01 vhusbdarm[660]: Error 22 discarding urb 0x7b0080 for device /sys/bus/usb/devices/1-1.4, Invalid argument (abort endpoint)
Jan 22 19:26:25 virtualhere_01 vhusbdarm[660]: Error 22 discarding urb 0x792180 for device /sys/bus/usb/devices/1-1.4, Invalid argument (abort endpoint)
Jan 22 19:26:25 virtualhere_01 vhusbdarm[660]: Error 22 discarding urb 0x7aebd0 for device /sys/bus/usb/devices/1-1.4, Invalid argument (abort endpoint)
Jan 22 19:26:25 virtualhere_01 vhusbdarm[660]: Error 22 discarding urb 0x7aecb0 for device /sys/bus/usb/devices/1-1.4, Invalid argument (abort endpoint)
Jan 22 19:26:25 virtualhere_01 vhusbdarm[660]: Error 22 discarding urb 0x7aee70 for device /sys/bus/usb/devices/1-1.4, Invalid argument (abort endpoint)
Jan 22 19:26:25 virtualhere_01 vhusbdarm[660]: Error 22 discarding urb 0x7a6fa0 for device /sys/bus/usb/devices/1-1.4, Invalid argument (abort endpoint)
Jan 22 19:26:25 virtualhere_01 vhusbdarm[660]: Error 22 discarding urb 0x7af1d0 for device /sys/bus/usb/devices/1-1.4, Invalid argument (abort endpoint)
Jan 22 19:26:25 virtualhere_01 vhusbdarm[660]: Error 22 discarding urb 0x7af290 for device /sys/bus/usb/devices/1-1.4, Invalid argument (abort endpoint)
Jan 22 19:26:25 virtualhere_01 vhusbdarm[660]: Error 22 discarding urb 0x7af350 for device /sys/bus/usb/devices/1-1.4, Invalid argument (abort endpoint)
Jan 22 19:26:25 virtualhere_01 vhusbdarm[660]: Error 22 discarding urb 0x7af420 for device /sys/bus/usb/devices/1-1.4, Invalid argument (abort endpoint)
Jan 22 19:26:25 virtualhere_01 vhusbdarm[660]: Error 22 discarding urb 0x7922f0 for device /sys/bus/usb/devices/1-1.4, Invalid argument (abort endpoint)
Jan 22 19:26:25 virtualhere_01 vhusbdarm[660]: Error 22 discarding urb 0x7a7100 for device /sys/bus/usb/devices/1-1.4, Invalid argument (abort endpoint)
Jan 22 19:26:25 virtualhere_01 vhusbdarm[660]: Error 22 discarding urb 0x7a71d0 for device /sys/bus/usb/devices/1-1.4, Invalid argument (abort endpoint)
Jan 22 19:26:25 virtualhere_01 vhusbdarm[660]: Error 22 discarding urb 0x7a7290 for device /sys/bus/usb/devices/1-1.4, Invalid argument (abort endpoint)
Jan 22 19:27:45 virtualhere_01 kernel: [ 153.515750] usb 1-1.5: USB disconnect, device number 5
Jan 22 19:27:45 virtualhere_01 vhusbdarm[660]: Device 115 [10ac:0102] SURPRISE UNBOUND from connection 1
Jan 22 19:27:45 virtualhere_01 vhusbdarm[660]: Unmanaging device 115 [10ac:0102]
Jan 22 19:28:00 virtualhere_01 kernel: [ 168.916681] usb 1-1.5: new full-speed USB device number 6 using dwc_otg
Jan 22 19:28:00 virtualhere_01 vhusbdarm[660]: Found Full speed device [10ac:0102] "Texas Instruments, TUSB3410 Boot Device" at address 115
Jan 22 19:28:00 virtualhere_01 kernel: [ 169.091763] usb 1-1.5: New USB device found, idVendor=10ac, idProduct=0102
Jan 22 19:28:00 virtualhere_01 kernel: [ 169.091776] usb 1-1.5: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Jan 22 19:28:00 virtualhere_01 kernel: [ 169.091784] usb 1-1.5: Product: TUSB3410 Boot Device
Jan 22 19:28:00 virtualhere_01 kernel: [ 169.091792] usb 1-1.5: Manufacturer: Texas Instruments
Jan 22 19:28:00 virtualhere_01 kernel: [ 169.091800] usb 1-1.5: SerialNumber: TUSB3410
Jan 22 19:28:00 virtualhere_01 vhusbdarm[660]: Executed "" for onReset.10ac.0102
Jan 22 19:28:00 virtualhere_01 vhusbdarm[660]: Device 115 [10ac:0102] BOUND to connection 1

On the client side:
[ 95.014892] usb 3-2: USB disconnect, device number 3
[ 95.014948] vhci_hcd: dequeue a urb ffff94ae791d8900
[ 95.014950] vhci_hcd: device ffff94ae76fa23a8 seems to be disconnected
[ 95.014951] vhci_hcd: gives back urb ffff94ae791d8900
[ 95.014953] vhci_hcd: dequeue a urb ffff94ae784bb600
[ 95.014954] vhci_hcd: device ffff94ae76fa23a8 seems to be disconnected
[ 95.014955] vhci_hcd: gives back urb ffff94ae784bb600
[ 95.014980] ftdi_sio ttyUSB0: error from flowcontrol urb
[ 95.015159] ftdi_sio ttyUSB0: FTDI USB Serial Device converter now disconnected from ttyUSB0
[ 95.015166] ftdi_sio 3-2:1.0: device disconnected
[ 110.600373] vhci_hcd: connection closed
[ 110.600466] vhci_hcd: stop threads
[ 110.600470] vhci_hcd: release socket
[ 110.600475] vhci_hcd: disconnect device
[ 110.600516] usb 3-1: USB disconnect, device number 2
[ 126.950206] vhci_hcd vhci_hcd: pdev(0) rhport(0) sockfd(10)
[ 126.950213] vhci_hcd vhci_hcd: devid(4) speed(2) speed_str(full-speed)
[ 127.176301] usb 3-1: new full-speed USB device number 4 using vhci_hcd
[ 127.300274] usb 3-1: SetAddress Request (4) to port 0
[ 127.371722] usb 3-1: New USB device found, idVendor=10ac, idProduct=0102
[ 127.371725] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 127.371726] usb 3-1: Product: TUSB3410 Boot Device
[ 127.371728] usb 3-1: Manufacturer: Texas Instruments
[ 127.371730] usb 3-1: SerialNumber: TUSB3410
[ 127.376844] ti_usb_3410_5052 3-1:1.0: TI USB 3410 1 port adapter converter detected
[ 127.377935] usb 3-1: firmware: failed to load ti_usb-v10ac-p0102.fw (-2)
[ 127.377939] usb 3-1: Direct firmware load for ti_usb-v10ac-p0102.fw failed with error -2
[ 127.378718] usb 3-1: firmware: direct-loading firmware ti_3410.fw
[ 128.836317] usb usb3-port1: Cannot enable. Maybe the USB cable is bad?
[ 129.728330] usb usb3-port1: Cannot enable. Maybe the USB cable is bad?
[ 130.049295] vhci_hcd: connection closed
[ 130.049464] vhci_hcd: stop threads
[ 130.049466] vhci_hcd: release socket
[ 130.049471] vhci_hcd: disconnect device
[ 130.828369] ti_usb_3410_5052: probe of 3-1:1.0 failed with error -5
[ 130.828535] usb 3-1: USB disconnect, device number 4
[ 150.241462] vhci_hcd vhci_hcd: pdev(0) rhport(0) sockfd(10)
[ 150.241466] vhci_hcd vhci_hcd: devid(4) speed(2) speed_str(full-speed)
[ 150.468185] usb 3-1: new full-speed USB device number 5 using vhci_hcd
[ 150.592191] usb 3-1: SetAddress Request (5) to port 0
[ 150.663529] usb 3-1: New USB device found, idVendor=10ac, idProduct=0102
[ 150.663532] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 150.663534] usb 3-1: Product: TUSB3410 Boot Device
[ 150.663535] usb 3-1: Manufacturer: Texas Instruments
[ 150.663537] usb 3-1: SerialNumber: TUSB3410
[ 150.668314] ti_usb_3410_5052 3-1:1.0: TI USB 3410 1 port adapter converter detected
[ 150.668339] usb 3-1: firmware: failed to load ti_usb-v10ac-p0102.fw (-2)
[ 150.668346] usb 3-1: Direct firmware load for ti_usb-v10ac-p0102.fw failed with error -2
[ 150.668408] usb 3-1: firmware: direct-loading firmware ti_3410.fw
[ 152.144219] usb usb3-port1: Cannot enable. Maybe the USB cable is bad?
[ 153.036214] usb usb3-port1: Cannot enable. Maybe the USB cable is bad?
[ 153.928207] usb usb3-port1: Cannot enable. Maybe the USB cable is bad?
[ 154.820203] usb usb3-port1: Cannot enable. Maybe the USB cable is bad?
[ 154.820283] ti_usb_3410_5052: probe of 3-1:1.0 failed with error -5
[ 154.820473] usb 3-1: USB disconnect, device number 5
[ 155.712213] usb usb3-port1: Cannot enable. Maybe the USB cable is bad?
[ 156.604230] usb usb3-port1: Cannot enable. Maybe the USB cable is bad?
[ 157.496134] usb usb3-port1: Cannot enable. Maybe the USB cable is bad?
[ 158.388130] usb usb3-port1: Cannot enable. Maybe the USB cable is bad?
[ 158.388148] usb usb3-port1: unable to enumerate USB device
[ 159.388176] usb usb3-port1: Cannot enable. Maybe the USB cable is bad?
[ 160.280192] usb usb3-port1: Cannot enable. Maybe the USB cable is bad?
[ 161.172124] usb usb3-port1: Cannot enable. Maybe the USB cable is bad?
[ 162.064178] usb usb3-port1: Cannot enable. Maybe the USB cable is bad?
[ 162.064209] usb usb3-port1: unable to enumerate USB device
[ 163.064181] usb usb3-port1: Cannot enable. Maybe the USB cable is bad?
[ 163.956103] usb usb3-port1: Cannot enable. Maybe the USB cable is bad?
[ 164.848156] usb usb3-port1: Cannot enable. Maybe the USB cable is bad?
[ 165.740125] usb usb3-port1: Cannot enable. Maybe the USB cable is bad?

Any other suggestion (I think I still need the firmware?)

Thanks

Submitted by hspjanssen on Tue, 2018/01/23 - 05:40

#11

Tested it on the Linux server, log:

[ 402.849943] usb 1-1.5: USB disconnect, device number 5
[ 418.509895] usb 1-1.5: new full-speed USB device number 6 using dwc_otg
[ 418.684939] usb 1-1.5: New USB device found, idVendor=10ac, idProduct=0102
[ 418.684951] usb 1-1.5: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 418.684959] usb 1-1.5: Product: TUSB3410 Boot Device
[ 418.684967] usb 1-1.5: Manufacturer: Texas Instruments
[ 418.684975] usb 1-1.5: SerialNumber: TUSB3410
[ 418.688629] ti_usb_3410_5052 1-1.5:1.0: TI USB 3410 1 port adapter converter detected
[ 418.688705] usb 1-1.5: Direct firmware load for ti_usb-v10ac-p0102.fw failed with error -2
[ 419.479908] usb 1-1.5: reset full-speed USB device number 6 using dwc_otg
[ 419.615572] usb 1-1.5: device firmware changed
[ 419.615722] ti_usb_3410_5052: probe of 1-1.5:1.0 failed with error -5
[ 419.616179] usb 1-1.5: USB disconnect, device number 6
[ 419.709908] usb 1-1.5: new full-speed USB device number 7 using dwc_otg
[ 419.904064] usb 1-1.5: New USB device found, idVendor=10ac, idProduct=0102
[ 419.904077] usb 1-1.5: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 419.904085] usb 1-1.5: Product: TUSB3410 Boot Device
[ 419.904093] usb 1-1.5: Manufacturer: Texas Instruments
[ 419.904101] usb 1-1.5: SerialNumber: TUSB3410
[ 419.906440] ti_usb_3410_5052 1-1.5:1.0: TI USB 3410 1 port adapter converter detected
[ 419.906490] ti_usb_3410_5052: probe of 1-1.5:1.0 failed with error -5
[ 419.908770] ti_usb_3410_5052 1-1.5:2.0: TI USB 3410 1 port adapter converter detected
[ 419.909156] usb 1-1.5: TI USB 3410 1 port adapter converter now attached to ttyUSB0
[ 438.689932] usb 1-1.5: USB disconnect, device number 7
[ 438.691299] ti_usb_3410_5052_1 ttyUSB0: TI USB 3410 1 port adapter converter now disconnected from ttyUSB0
[ 438.691367] ti_usb_3410_5052 1-1.5:2.0: device disconnected
[ 458.440253] usb 1-1.5: new full-speed USB device number 8 using dwc_otg
[ 458.615315] usb 1-1.5: New USB device found, idVendor=10ac, idProduct=0102
[ 458.615326] usb 1-1.5: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 458.615334] usb 1-1.5: Product: TUSB3410 Boot Device
[ 458.615342] usb 1-1.5: Manufacturer: Texas Instruments
[ 458.615350] usb 1-1.5: SerialNumber: TUSB3410
[ 458.618993] ti_usb_3410_5052 1-1.5:1.0: TI USB 3410 1 port adapter converter detected
[ 458.619069] usb 1-1.5: Direct firmware load for ti_usb-v10ac-p0102.fw failed with error -2
[ 459.410261] usb 1-1.5: reset full-speed USB device number 8 using dwc_otg
[ 459.545936] usb 1-1.5: device firmware changed
[ 459.546084] ti_usb_3410_5052: probe of 1-1.5:1.0 failed with error -5
[ 459.546544] usb 1-1.5: USB disconnect, device number 8
[ 459.640270] usb 1-1.5: new full-speed USB device number 9 using dwc_otg
[ 459.832936] usb 1-1.5: New USB device found, idVendor=10ac, idProduct=0102
[ 459.832948] usb 1-1.5: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 459.832956] usb 1-1.5: Product: TUSB3410 Boot Device
[ 459.832964] usb 1-1.5: Manufacturer: Texas Instruments
[ 459.832972] usb 1-1.5: SerialNumber: TUSB3410
[ 459.835305] ti_usb_3410_5052 1-1.5:1.0: TI USB 3410 1 port adapter converter detected
[ 459.835355] ti_usb_3410_5052: probe of 1-1.5:1.0 failed with error -5
[ 459.837644] ti_usb_3410_5052 1-1.5:2.0: TI USB 3410 1 port adapter converter detected
[ 459.838020] usb 1-1.5: TI USB 3410 1 port adapter converter now attached to ttyUSB0

Syslog:
Jan 22 20:29:04 virtualhere_01 kernel: [ 419.906440] ti_usb_3410_5052 1-1.5:1.0: TI USB 3410 1 port adapter converter detected
Jan 22 20:29:04 virtualhere_01 kernel: [ 419.906490] ti_usb_3410_5052: probe of 1-1.5:1.0 failed with error -5
Jan 22 20:29:04 virtualhere_01 kernel: [ 419.908770] ti_usb_3410_5052 1-1.5:2.0: TI USB 3410 1 port adapter converter detected
Jan 22 20:29:04 virtualhere_01 kernel: [ 419.909156] usb 1-1.5: TI USB 3410 1 port adapter converter now attached to ttyUSB0
Jan 22 20:29:23 virtualhere_01 kernel: [ 438.689932] usb 1-1.5: USB disconnect, device number 7
Jan 22 20:29:23 virtualhere_01 kernel: [ 438.691299] ti_usb_3410_5052_1 ttyUSB0: TI USB 3410 1 port adapter converter now disconnected from ttyUSB0
Jan 22 20:29:23 virtualhere_01 kernel: [ 438.691367] ti_usb_3410_5052 1-1.5:2.0: device disconnected
Jan 22 20:29:42 virtualhere_01 kernel: [ 458.440253] usb 1-1.5: new full-speed USB device number 8 using dwc_otg
Jan 22 20:29:42 virtualhere_01 kernel: [ 458.615315] usb 1-1.5: New USB device found, idVendor=10ac, idProduct=0102
Jan 22 20:29:42 virtualhere_01 kernel: [ 458.615326] usb 1-1.5: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Jan 22 20:29:42 virtualhere_01 kernel: [ 458.615334] usb 1-1.5: Product: TUSB3410 Boot Device
Jan 22 20:29:42 virtualhere_01 kernel: [ 458.615342] usb 1-1.5: Manufacturer: Texas Instruments
Jan 22 20:29:42 virtualhere_01 kernel: [ 458.615350] usb 1-1.5: SerialNumber: TUSB3410
Jan 22 20:29:42 virtualhere_01 kernel: [ 458.618993] ti_usb_3410_5052 1-1.5:1.0: TI USB 3410 1 port adapter converter detected
Jan 22 20:29:42 virtualhere_01 kernel: [ 458.619069] usb 1-1.5: Direct firmware load for ti_usb-v10ac-p0102.fw failed with error -2
Jan 22 20:29:43 virtualhere_01 kernel: [ 459.410261] usb 1-1.5: reset full-speed USB device number 8 using dwc_otg
Jan 22 20:29:43 virtualhere_01 kernel: [ 459.545936] usb 1-1.5: device firmware changed
Jan 22 20:29:43 virtualhere_01 kernel: [ 459.546084] ti_usb_3410_5052: probe of 1-1.5:1.0 failed with error -5
Jan 22 20:29:43 virtualhere_01 kernel: [ 459.546544] usb 1-1.5: USB disconnect, device number 8
Jan 22 20:29:43 virtualhere_01 kernel: [ 459.640270] usb 1-1.5: new full-speed USB device number 9 using dwc_otg
Jan 22 20:29:44 virtualhere_01 kernel: [ 459.832936] usb 1-1.5: New USB device found, idVendor=10ac, idProduct=0102
Jan 22 20:29:44 virtualhere_01 kernel: [ 459.832948] usb 1-1.5: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Jan 22 20:29:44 virtualhere_01 kernel: [ 459.832956] usb 1-1.5: Product: TUSB3410 Boot Device
Jan 22 20:29:44 virtualhere_01 kernel: [ 459.832964] usb 1-1.5: Manufacturer: Texas Instruments
Jan 22 20:29:44 virtualhere_01 kernel: [ 459.832972] usb 1-1.5: SerialNumber: TUSB3410
Jan 22 20:29:44 virtualhere_01 kernel: [ 459.835305] ti_usb_3410_5052 1-1.5:1.0: TI USB 3410 1 port adapter converter detected
Jan 22 20:29:44 virtualhere_01 kernel: [ 459.835355] ti_usb_3410_5052: probe of 1-1.5:1.0 failed with error -5
Jan 22 20:29:44 virtualhere_01 kernel: [ 459.837644] ti_usb_3410_5052 1-1.5:2.0: TI USB 3410 1 port adapter converter detected
Jan 22 20:29:44 virtualhere_01 kernel: [ 459.838020] usb 1-1.5: TI USB 3410 1 port adapter converter now attached to ttyUSB0

Submitted by Michael on Tue, 2018/01/23 - 08:23

#12

OK from what i can see it looks like the usbserial driver is being bound on the server during the process of capture by virtualhere. Can you blacklist the usbserial driver on the server. ( https://askubuntu.com/questions/110341/how-to-blacklist-kernel-modules )

or

can you try this on the server

pkill the virtualhere server process. Then edit the config.ini file and add the line

ClaimPorts=1

then save and restart the server, now can you unplug and replug the serial device then use it via the virtualhere client.

Submitted by hspjanssen on Wed, 2018/01/24 - 08:10

#13

Hello Michael,

Tried the above, without success. I think I have to explain my previous posts a bit more.

Post from Mon, 2018-01-22 19:49 (post number 10)
This is what is happening on the server side and the client side, I tested it again a few minutes ago, this is what I see on the client side:

dmesg:
[ 768.120319] usb 3-1: new full-speed USB device number 21 using vhci_hcd
[ 768.244327] usb 3-1: SetAddress Request (21) to port 0
[ 768.312072] usb 3-1: New USB device found, idVendor=10ac, idProduct=0102
[ 768.312075] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 768.312077] usb 3-1: Product: TUSB3410 Boot Device
[ 768.312078] usb 3-1: Manufacturer: Texas Instruments
[ 768.312079] usb 3-1: SerialNumber: TUSB3410
[ 768.321191] ti_usb_3410_5052 3-1:1.0: TI USB 3410 1 port adapter converter detected
[ 768.321206] usb 3-1: firmware: failed to load ti_usb-v10ac-p0102.fw (-2)
[ 768.321209] usb 3-1: Direct firmware load for ti_usb-v10ac-p0102.fw failed with error -2
[ 768.321278] usb 3-1: firmware: direct-loading firmware ti_3410.fw
[ 769.836336] usb usb3-port1: Cannot enable. Maybe the USB cable is bad?
[ 770.728322] usb usb3-port1: Cannot enable. Maybe the USB cable is bad?
[ 771.620358] usb usb3-port1: Cannot enable. Maybe the USB cable is bad?
[ 772.512325] usb usb3-port1: Cannot enable. Maybe the USB cable is bad?
[ 772.512363] ti_usb_3410_5052: probe of 3-1:1.0 failed with error -5
[ 772.512466] usb 3-1: USB disconnect, device number 21
[ 773.404318] usb usb3-port1: Cannot enable. Maybe the USB cable is bad?
[ 774.296998] usb usb3-port1: Cannot enable. Maybe the USB cable is bad?
[ 775.188322] usb usb3-port1: Cannot enable. Maybe the USB cable is bad?
[ 776.080305] usb usb3-port1: Cannot enable. Maybe the USB cable is bad?
[ 776.080319] usb usb3-port1: unable to enumerate USB device

/var/log/syslog
Jan 23 22:57:59 domoticz kernel: [ 767.856828] vhci_hcd vhci_hcd: pdev(0) rhport(0) sockfd(12)
Jan 23 22:57:59 domoticz kernel: [ 767.856831] vhci_hcd vhci_hcd: devid(5) speed(2) speed_str(full-speed)
Jan 23 22:58:00 domoticz kernel: [ 768.120319] usb 3-1: new full-speed USB device number 21 using vhci_hcd
Jan 23 22:58:00 domoticz kernel: [ 768.244327] usb 3-1: SetAddress Request (21) to port 0
Jan 23 22:58:00 domoticz kernel: [ 768.312072] usb 3-1: New USB device found, idVendor=10ac, idProduct=0102
Jan 23 22:58:00 domoticz kernel: [ 768.312075] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Jan 23 22:58:00 domoticz kernel: [ 768.312077] usb 3-1: Product: TUSB3410 Boot Device
Jan 23 22:58:00 domoticz kernel: [ 768.312078] usb 3-1: Manufacturer: Texas Instruments
Jan 23 22:58:00 domoticz kernel: [ 768.312079] usb 3-1: SerialNumber: TUSB3410
Jan 23 22:58:00 domoticz kernel: [ 768.321191] ti_usb_3410_5052 3-1:1.0: TI USB 3410 1 port adapter converter detected
Jan 23 22:58:00 domoticz kernel: [ 768.321206] usb 3-1: firmware: failed to load ti_usb-v10ac-p0102.fw (-2)
Jan 23 22:58:00 domoticz kernel: [ 768.321209] usb 3-1: Direct firmware load for ti_usb-v10ac-p0102.fw failed with error -2
Jan 23 22:58:00 domoticz kernel: [ 768.321278] usb 3-1: firmware: direct-loading firmware ti_3410.fw
Jan 23 22:58:01 domoticz kernel: [ 769.836336] usb usb3-port1: Cannot enable. Maybe the USB cable is bad?
Jan 23 22:58:02 domoticz kernel: [ 770.728322] usb usb3-port1: Cannot enable. Maybe the USB cable is bad?
Jan 23 22:58:03 domoticz kernel: [ 771.620358] usb usb3-port1: Cannot enable. Maybe the USB cable is bad?
Jan 23 22:58:04 domoticz kernel: [ 772.512325] usb usb3-port1: Cannot enable. Maybe the USB cable is bad?
Jan 23 22:58:04 domoticz kernel: [ 772.512363] ti_usb_3410_5052: probe of 3-1:1.0 failed with error -5
Jan 23 22:58:04 domoticz kernel: [ 772.512466] usb 3-1: USB disconnect, device number 21
Jan 23 22:58:05 domoticz kernel: [ 773.404318] usb usb3-port1: Cannot enable. Maybe the USB cable is bad?
Jan 23 22:58:06 domoticz kernel: [ 774.296998] usb usb3-port1: Cannot enable. Maybe the USB cable is bad?
Jan 23 22:58:07 domoticz kernel: [ 775.188322] usb usb3-port1: Cannot enable. Maybe the USB cable is bad?
Jan 23 22:58:08 domoticz kernel: [ 776.080305] usb usb3-port1: Cannot enable. Maybe the USB cable is bad?
Jan 23 22:58:08 domoticz kernel: [ 776.080319] usb usb3-port1: unable to enumerate USB device
Jan 23 22:58:20 domoticz : Error 'Name does not resolve' getaddrinfo failed for virtualhere_02:7575
Jan 23 22:58:20 domoticz : Error 'Name does not resolve' getaddrinfo failed for virtualhere_01:7575
Jan 23 22:58:50 domoticz : Error 'Name does not resolve' getaddrinfo failed for virtualhere_02:7575
Jan 23 22:58:50 domoticz : Error 'Name does not resolve' getaddrinfo failed for virtualhere_01:7575
Jan 23 22:59:20 domoticz : Error 'Name does not resolve' getaddrinfo failed for virtualhere_02:7575
Jan 23 22:59:20 domoticz : Error 'Name does not resolve' getaddrinfo failed for virtualhere_01:7575
Jan 23 22:59:20 domoticz : ValidateParameters: Note: InterfaceID 0000000001216660 for question VirtualHere\032USB\032Sharing._vhusb._tcp.local. (SRV) not currently found in active interface list
Jan 23 22:59:20 domoticz : ValidateParameters: Note: InterfaceID 0000000001216660 for question VirtualHere\032USB\032Sharing._vhusb._tcp.local. (TXT) not currently found in active interface list
Jan 23 22:59:50 domoticz : Error 'Name does not resolve' getaddrinfo failed for virtualhere_02:7575
Jan 23 22:59:50 domoticz : Error 'Name does not resolve' getaddrinfo failed for virtualhere_01:7575
Jan 23 23:00:12 domoticz systemd[1]: Starting Cleanup of Temporary Directories...
Jan 23 23:00:12 domoticz systemd[1]: Started Cleanup of Temporary Directories.
Jan 23 23:00:20 domoticz : Error 'Name does not resolve' getaddrinfo failed for virtualhere_02:7575
Jan 23 23:00:20 domoticz : Error 'Name does not resolve' getaddrinfo failed for virtualhere_01:7575
Jan 23 23:00:50 domoticz : Error 'Name does not resolve' getaddrinfo failed for virtualhere_02:7575
Jan 23 23:00:50 domoticz : Error 'Name does not resolve' getaddrinfo failed for virtualhere_01:7575
Jan 23 23:01:20 domoticz : Error 'Name does not resolve' getaddrinfo failed for virtualhere_02:7575
Jan 23 23:01:20 domoticz : Error 'Name does not resolve' getaddrinfo failed for virtualhere_01:7575

Post Mon, 2018-01-22 20:40, number 11.
That output is the output of the device which is not working via virtualhere (see output above, or logging in post number 10), when I shutdown virtualhere on the server side, it then shows up correctly on that Linux device as an USB device. I posted this to show you that the device is working ok, when I connect it directly to the Linux device (when I shutdown virtualhere server).

That same device is causing the logging above on the client (in this post) when I start virtualhere server and the device is connected on the client side (the device is seen and is connected).

Any other idea, why this device (Honeywell HGI80 with Texas Instruments 3410 in it) is not working?

It is still asking for ti_usb-v10ac-p0102.fw, strange thing is that it does not need that firmware when I directly connect it to the Linux server side (when I disable virtualhere).

Many thanks

Submitted by Michael on Wed, 2018/01/24 - 10:54

#14

OK im out of ideas unfortunately...