TVHeadend42 - no USB devices after reboot

jochen02 · November 30, 2017 at 9:06 AM

Hello,

I am running LibreELEC (community): 8.2.1.1 (S905.arm) on Odroid C2 with tvheadend42 server. 2 USB DVB-T2 receivers are connected using an USB hub with external power. After reboot the USB devices remains disconnected. I have to manually pull and plug the USB sticks to have tvheadend to discover them.

What might be the reason? I can live with some code in autostart.sh but I am not experienced in tweaking systemd.

**CvH** · November 30, 2017 at 10:42 AM Official Post

go to tvh addon settings at kodi and then

if this don't work you can also use the delay the start of tvh and add 1-2sec

jochen02 · November 30, 2017 at 11:20 AM

Thank you, it works. Didn't expect that it is that easy. How can I have overlooked that?

jochen02 · December 1, 2017 at 9:46 AM

Well, it worked only once.

tvheadend service does not start because it's waiting for the number of configured USB dvb-t receivers.

Therefore I need to re-init USB from shell. Something comparable to unplug - plug the USB sticks.

How is that be done with systemd? I've digged in the internet how this can be achieved but I may not have used the right search terms.

Summary of the problem:

1. If I remove and plug in the DVB-T USB sticks it works reliable.

2. If I reboot it remains most of the times disconnected.

Help needed (please!)

**CvH** · December 1, 2017 at 10:35 AM Official Post

Is it at restart or do you use suspend/standby?

Pls also try to just use the delayed start of Tvh instead to wait for the tuners.

jochen02 · December 1, 2017 at 11:33 AM

It's on restart. With the most recent built of LibreELEC 8.2 for Odroid C2 tvheadend server seems to be a bit unstabile. I don't be fully sure if this build is to blame therefore I don't raise a bug report for now.

That's the reason for nightly reboots.

I'll try to delay start of tvheadend. What do you suggest? Would 5 Sek. be a good value to start with?

EDIT: Tried it with 5 sec., but wait a few days (and restarts) until reporting success...

**CvH** · December 1, 2017 at 12:00 PM Official Post

Normally 1sec is already enough BUT who knows what's wrong so try 5sec. If this works reliable lower the value.

Even with fu slow devices 5dec should be more then enough.

If you still get the problems try to get a log after the problem appears.

dmesg | paste via shell

jochen02 · December 2, 2017 at 10:58 AM

Hello,

O.k., today I rebooted and found the system without DVB-T2 devices.

Output of dmesg: gQEO

After replugging one of the USB adapters these lines are added: XTYN

It's no special magic reconnecting the USB sticks. Just pull and plug without waiting.

Does that give hints?

**CvH** · December 2, 2017 at 8:05 PM Official Post

Code

usb 1-1.3.2: device descriptor read/64, error -110
usb 1-1.3.2: new high-speed USB device number 8 using dwc_otg
usb 1-1.3.2: device descriptor read/64, error -110
usb 1-1.3.2: device descriptor read/64, error -110
usb 1-1.3.2: new high-speed USB device number 9 using dwc_otg
usb 1-1.3.2: device descriptor read/8, error -110
usb 1-1.3.2: device descriptor read/8, error -110
usb 1-1.3.2: new high-speed USB device number 10 using dwc_otg
usb 1-1.3.2: device descriptor read/8, error -110
usb 1-1.3.2: device descriptor read/8, error -110
hub 1-1.3:1.0: unable to enumerate USB device on port 2
usb 1-1.3.3: new high-speed USB device number 11 using dwc_otg
usb 1-1.3.3: device descriptor read/64, error -110
usb 1-1.3.3: device descriptor read/64, error -110
usb 1-1.3.3: new high-speed USB device number 12 using dwc_otg
usb 1-1.3.3: device descriptor read/64, error -110
usb 1-1.3.3: device descriptor read/64, error -110
usb 1-1.3.3: new high-speed USB device number 13 using dwc_otg
usb 1-1.3.3: device descriptor read/8, error -110
usb 1-1.3.3: device descriptor read/8, error -110
usb 1-1.3.3: new high-speed USB device number 14 using dwc_otg
usb 1-1.3.3: device descriptor read/8, error -110
usb 1-1.3.3: device descriptor read/8, error -110
hub 1-1.3:1.0: unable to enumerate USB device on port 3

Display More

... hmm looks like driver error

at S905x not much I can do

**kszaq** · December 2, 2017 at 9:06 PM

jochen02 Try using official LE build or Raybuntu's build if you need media_build drivers.

jochen02 · December 3, 2017 at 1:42 PM

O.k., I just installed Raybuntu's build hoping it solves my problems.

I'll report here. Thank you for your help.