4 Hauppauge USB tuners connected to Libreelec, only one listed in /dev/dvb and tvheadend

undrwater · September 1, 2018 at 11:08 PM

As above including devices are plugged into powered usb hub. Here's lsusb:

Code

Bus 002 Device 003: ID 0bda:0411 Realtek Semiconductor Corp. 
Bus 002 Device 002: ID 0bda:0411 Realtek Semiconductor Corp. 
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 009: ID 13d3:3393 IMC Networks 
Bus 001 Device 008: ID 2040:7200 Hauppauge 
Bus 001 Device 007: ID 2040:7200 Hauppauge 
Bus 001 Device 006: ID 0bda:5411 Realtek Semiconductor Corp. 
Bus 001 Device 005: ID 2040:7200 Hauppauge 
Bus 001 Device 004: ID 2040:7200 Hauppauge 
Bus 001 Device 002: ID 0bda:5411 Realtek Semiconductor Corp. 
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Display More

Here's ls /dev/dvb:

Code

adapter0

and dmesg | grep au0828:

Code

[    4.887425] au0828: au0828 driver loaded
[    5.280473] au0828: i2c bus registered
[    5.340398] au0828: hauppauge_eeprom: hauppauge eeprom: model=72001
[    5.634596] dvbdev: DVB: registering new adapter (au0828)
[    5.820082] rc rc0: au0828 IR (Hauppauge HVR950Q) as /devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2.1/rc/rc0
[    5.820139] input: au0828 IR (Hauppauge HVR950Q) as /devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2.1/rc/rc0/input11
[    5.825400] rc rc0: lirc_dev: driver au0828-input registered at minor = 0
[    5.825640] au0828: Remote controller au0828 IR (Hauppauge HVR950Q) initialized
[    5.825643] au0828: Registered device AU0828 [Hauppauge HVR950Q]
[    6.213643] au0828: i2c bus registered
[    6.250840] au0828: hauppauge_eeprom: hauppauge eeprom: model=72001
[    6.259023] au0828: Failure setting usb interface0 to as5
[    6.259024] au0828: au0828_usb_probe() au0282_dev_register failed to register on V4L2
[    6.259038] Modules linked in: ir_rc5_decoder rc_hauppauge wl(PO) au8522_dig ath9k ath9k_common ath9k_hw ath xc5000 mac80211 tuner au8522_decoder au8522_common intel_rapl intel_powerclamp cfg80211 snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic rfkill snd_hda_intel snd_hda_codec snd_hda_core au0828(+) videobuf2_vmalloc rc_core videobuf2_memops videobuf2_v4l2 videobuf2_common tveeprom v4l2_common snd_usb_audio videodev dvb_core snd_usbmidi_lib snd_hwdep snd_rawmidi
[    6.259146]  au0828_usb_disconnect+0x4f/0x80 [au0828]
[    6.259154]  au0828_usb_probe.cold.14+0x30/0xdc [au0828]
[    6.259212]  au0828_init+0xbc/0x1000 [au0828]
[    8.751834] Modules linked in: 8021q ir_rc5_decoder rc_hauppauge wl(PO) au8522_dig ath9k ath9k_common ath9k_hw ath xc5000 mac80211 tuner au8522_decoder au8522_common intel_rapl intel_powerclamp cfg80211 snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic rfkill snd_hda_intel snd_hda_codec snd_hda_core au0828(+) videobuf2_vmalloc rc_core videobuf2_memops videobuf2_v4l2 videobuf2_common tveeprom v4l2_common snd_usb_audio videodev dvb_core snd_usbmidi_lib snd_hwdep snd_rawmidi
[    8.792952] Modules linked in: 8021q ir_rc5_decoder rc_hauppauge wl(PO) au8522_dig ath9k ath9k_common ath9k_hw ath xc5000 mac80211 tuner au8522_decoder au8522_common intel_rapl intel_powerclamp cfg80211 snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic rfkill snd_hda_intel snd_hda_codec snd_hda_core au0828(+) videobuf2_vmalloc rc_core videobuf2_memops videobuf2_v4l2 videobuf2_common tveeprom v4l2_common snd_usb_audio videodev dvb_core snd_usbmidi_lib snd_hwdep snd_rawmidi
[  366.462146] Modules linked in: btusb btrtl btbcm btintel ath3k bluetooth ecdh_generic 8021q ir_rc5_decoder rc_hauppauge wl(PO) au8522_dig ath9k ath9k_common ath9k_hw ath xc5000 mac80211 tuner au8522_decoder au8522_common intel_rapl intel_powerclamp cfg80211 snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic rfkill snd_hda_intel snd_hda_codec snd_hda_core au0828(+) videobuf2_vmalloc rc_core videobuf2_memops videobuf2_v4l2 videobuf2_common tveeprom v4l2_common snd_usb_audio videodev dvb_core snd_usbmidi_lib snd_hwdep snd_rawmidi
[  366.464423] Modules linked in: btusb btrtl btbcm btintel ath3k bluetooth ecdh_generic 8021q ir_rc5_decoder rc_hauppauge wl(PO) au8522_dig ath9k ath9k_common ath9k_hw ath xc5000 mac80211 tuner au8522_decoder au8522_common intel_rapl intel_powerclamp cfg80211 snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic rfkill snd_hda_intel snd_hda_codec snd_hda_core au0828(+) videobuf2_vmalloc rc_core videobuf2_memops videobuf2_v4l2 videobuf2_common tveeprom v4l2_common snd_usb_audio videodev dvb_core snd_usbmidi_lib snd_hwdep snd_rawmidi

Display More

I see the failures and disconnects, but not sure why it's happening. The usb hub is new and supposed to be rated high power. Earlier versions of libreelec would enumerate all 4.

Any clues?

Thanks in advance.

Edited to add:

HTS Tvheadend 4.2.6-7 ~ LibreELEC Tvh-addon v9.0.115

Code

LibreELEC (official): 8.90.003 (Generic.x86_64)

**CvH** · September 2, 2018 at 7:18 AM Official Post

try 8.90.004 and try to activate "latest kernel" drivers at the driver chooser addon

and pls do a dmesg | paste

undrwater · September 4, 2018 at 5:49 PM

Quote from CvH

try 8.90.004 and try to activate "latest kernel" drivers at the driver chooser addon

and pls do a dmesg | paste

Thanks for your reply!

I've done the two top things, but still get only one reported adapter.

Here's dmesg |paste:

http://ix.io/1lyc

**CvH** · September 5, 2018 at 8:24 AM Official Post

outch

could you try - disconnect every dvb adapter, reboot

attach all adaptors after reboot (wait 2-3 sec between echt adaptor)

then dmesg | paste again, first best guess is that the driver crashs

I try to report it to the dev (Issue #52 · b-rad-NDi/Ubuntu-media-tree-kernel-builder · GitHub).

undrwater · September 7, 2018 at 6:38 PM

OK. When I plugged them in one at at time, they were enumerated (except one, but I suspect it may be bad). Here's the dmesg | paste:

http://ix.io/1mbh

I hope this helps.

Edited to add: Upon reboot, only one device is enumerated. I must unplug and add each one at at time.

**CvH** · September 8, 2018 at 10:36 PM Official Post

tx reported it, maybe we get a fix

**CvH** · September 19, 2018 at 9:08 PM Official Post

could you try Index of /test/hauppauge/ if it works btw repeat the tests ?

undrwater · September 20, 2018 at 12:59 AM

dmesg | paste:

http://ix.io/1n4t

Still just one device showing.

**CvH** · September 20, 2018 at 7:18 PM Official Post

tx could you try again with the new image from Index of /test/hauppauge/

dmesg | paste

as usual

there is now some logging activated and should better show whats wrong

-questions from the hauppauge dev

do you use the sticks at an usb hub ? if so pls try without hub too as USB hubs are known as problematic (dmesg | paste ... )

undrwater · September 21, 2018 at 5:17 PM

http://ix.io/1ncw

I am using a super special powered USB hub. I'd like to continue using a hub as I won't have access to all the tuners without it. Also, since the tuners work when plugged into the hub after LE boots, I'd assume (perhaps incorrectly) that the problem isn't one of the hub.

Anyway, here's the dmesg | paste with tuners plugged directly into the Chromebox:

http://ix.io/1ncf

So the tuners are showing. Humbug. I'm not sure there's a way to get the driver working with the hub, as that's my preference (it was also working in an earlier version of LE).

Thanks for looking into it!

**CvH** · September 28, 2018 at 10:14 PM Official Post

could you try to attach all usb dvb devices to the device WITHOUT an hub ?

if this works the hub drivers are the problem that are not fixable with the dvb drivers

undrwater · September 29, 2018 at 12:42 AM

The second link above is with devices plugged into chromebox directly. No hub.

I suspect you may be right about it being the hub driver. One thing I may try is to start up without the hub plugged in, then plug in and see if all devices get enumerated. If they do, do you think it may be a timing issue?

**CvH** · September 29, 2018 at 8:48 AM Official Post

Quote from undrwater

If they do, do you think it may be a timing issue?

quite possible, tbh this wouldn't be the first issue with usb hubs in general

so to wrap up, all 4 sticks connected to the box directly working like expected !?

undrwater · October 24, 2018 at 2:41 AM

Quote from CvH

quite possible, tbh this wouldn't be the first issue with usb hubs in general

so to wrap up, all 4 sticks connected to the box directly working like expected !?

Sorry to have left this to languish for so long. Yes, sticks connected directly to the box work as expected. I also just tried plugging the hub in after booting, and only one device enumerated. Ah well...I'll just have to remember to plug in one at at time on each reboot.

**CvH** · October 24, 2018 at 8:16 AM Official Post

oki, so its an problem from the usb hub drivers

sadly nothing we can help