WinQuadHD Tuner 1609 - Only 1 Tuner Usable

[nocturnalcodehack]

Just built my first mythTV device. Love it as a replacement for the cable service we discontinued using Tivo--4 replacement boxes in 4 years. I bought the Hauppague Win QuadHD 1609 tuner card. I configured 4 Capture Cards, 1 Video Sources (using SchedulesDirect.org) and 4 Input Connections (one for each card each configured to the same 1 Video Source). The problem is I can only use one of the tuners. MythTV Version 0.29. Ubuntu 18.04. Intel i3, 8 GB Ram, 2TB Disk.

Frontend Tuner Status indicates:
Tuner 1 is not recording
Tuner 2 has an error
Tuner 3 has an error
Tuner 4 has an error

My adapters and Linux versions are:
m@dvr:~$ ls /dev/dvb
adapter0 adapter1 adapter2 adapter3
m@dvr:~$ uname -a
Linux dvr 4.18.0-20-generic #21~18.04.1-Ubuntu SMP Wed May 8 08:43:37 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
m@dvr:~$

My cardid's are:
1 | /dev/dvb/adapter0/frontend0
2 | /dev/dvb/adapter1/frontend0
3 | /dev/dvb/adapter2/frontend0
4 | /dev/dvb/adapter3/frontend0

I cannot determine what is the problem with the MythTV configuration, Linux Drivers or other. Myth-setup.log includes the following:

May 21 22:49:06 dvr mythtv-setup.real: mythtv-setup[3319]: W ScreenLoad diseqc.cpp:395 (Load) DiSEqCDevTree: No device tree for cardid 1
May 21 22:49:06 dvr mythtv-setup.real: mythtv-setup[3319]: W ScreenLoad diseqc.cpp:395 (Load) DiSEqCDevTree: No device tree for cardid 4
May 21 22:49:06 dvr mythtv-setup.real: mythtv-setup[3319]: W ScreenLoad diseqc.cpp:395 (Load) DiSEqCDevTree: No device tree for cardid 4
May 21 22:49:32 dvr mythtv-setup.real: mythtv-setup[3319]: W CoreContext diseqc.cpp:395 (Load) DiSEqCDevTree: No device tree for cardid 2
May 21 22:50:26 dvr mythtv-setup.real: mythtv-setup[3319]: I ScreenLoad recorders/vboxutils.cpp:49 (probeDevices) VBox: Using UPNP to search for Vboxes (3 secs)
May 21 22:50:29 dvr mythtv-setup.real: mythtv-setup[3319]: E ScreenLoad v4l2util.cpp:58 (Open) V4L2(): Could not open '': #012#011#011#011eno: No such file or directory (2)
May 21 22:50:29 dvr mythtv-setup.real: mythtv-setup[3319]: W ScreenLoad diseqc.cpp:395 (Load) DiSEqCDevTree: No device tree for cardid 1
May 21 22:50:29 dvr mythtv-setup.real: mythtv-setup[3319]: E ScreenLoad cardutil.cpp:504 (ProbeDVBType) Can't open DVB frontend (/dev/dvb/adapter0/frontend0) for /dev/dvb/adapter0/frontend0.
May 21 22:50:29 dvr mythtv-setup.real: mythtv-setup[3319]: W ScreenLoad diseqc.cpp:395 (Load) DiSEqCDevTree: No device tree for cardid 1
May 21 22:50:29 dvr mythtv-setup.real: mythtv-setup[3319]: W ScreenLoad diseqc.cpp:395 (Load) DiSEqCDevTree: No device tree for cardid 1
May 21 22:50:30 dvr mythtv-setup.real: mythtv-setup[3319]: I ScreenLoad recorders/vboxutils.cpp:49 (probeDevices) VBox: Using UPNP to search for Vboxes (3 secs)
May 21 22:50:33 dvr mythtv-setup.real: mythtv-setup[3319]: E ScreenLoad v4l2util.cpp:58 (Open) V4L2(): Could not open '': #012#011#011#011eno: No such file or directory (2)
.... THIS SOMEWHAT REPEATS A FEW TIMES... Thanks for your help.

[Manul]

I'm using the same card on Ubuntu 18.04 without problems. However, my Ubuntu installation is inside an lxd container on a Debian host so our situations might be quite different kernel-wise.

Do you see any dvb-related messages in the system logs? How do those look?

[wesnewell]

Try a warm reboot. If that doesn't fix it. Try upgrading the kernel to 5.1
wes@mythfe0:~$ uname -a
Linux mythfe0 5.1.4-050104-generic #201905220633 SMP Wed May 22 06:36:13 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

When I do a cold boot, I get the same problem since switching to fast booting ssd drive. Seems the boot is just too fast for all the cards to initialize fast enough from powerup. Another problem coulld be an older driver in older kernel. Install ukuu and upgrade to latest kernel may fix it.

[bill6502]

If using systemd, take a peek at this: https://www.mythtv.org/wiki/Systemd_myt ... nitialized

[nocturnalcodehack]

To Manul, wesnewell andbill6592: For your responses. I upgraded to Linux 5.1.5 and all 4 tuners were found. I appreciate the thoughts on implementing back-end delay--its great to have a second technique as so often first attempts don't work as expected. Thanks !.