<!DOCTYPE html><html><head><style type="text/css">body { font-family:'DejaVu Sans Mono'; font-size:12px}</style></head><body><div><br>>> The HDHR tuners work fine too.<br>>> The Backend takes a long time to start,now.About 1.5 mins.It seems the<br>>> tuner cards are holding things up.I can probably live with it.<br>>> Here's a section from syslog:<br>>><br>>> Aug 13 11:02:33 mythpc kernel: [ 17.539314] DVB: registering new <br>>> adapter<br>>> (saa7164)<br>>> Aug 13 11:02:33 mythpc kernel: [ 17.539319] saa7164 0000:03:00.0: DVB:<br>>> registering adapter 1 frontend 0 (NXP TDA10048HN DVB-T)...<br>>> Aug 13 11:02:34 mythpc kernel: [ 17.575686] saa7164[0]: registered<br>>> device video0 [mpeg]<br>>> Aug 13 11:02:34 mythpc kernel: [ 17.802040] saa7164[0]: registered<br>>> device video1 [mpeg]<br>>> Aug 13 11:02:34 mythpc kernel: [ 18.013816] saa7164[0]: registered<br>>> device vbi0 [vbi]<br>>> Aug 13 11:02:34 mythpc kernel: [ 18.013964] saa7164[0]: registered<br>>> device vbi1 [vbi]<br>>> Aug 13 11:03:48 mythpc systemd[1]: dev-dvb-adapter1-frontend0.device: <br>>> Job<br>>> dev-dvb-adapter1-frontend0.device/start timed out.<br>>> Aug 13 11:03:48 mythpc systemd[1]: Timed out waiting for device<br>>> dev-dvb-adapter1-frontend0.device.<br>>> Aug 13 11:03:48 mythpc systemd[1]: dev-dvb-adapter1-frontend0.device: <br>>> Job<br>>> dev-dvb-adapter1-frontend0.device/start failed with result 'timeout'.<br>>> Aug 13 11:03:48 mythpc systemd[1]: dev-dvb-adapter0-frontend0.device: <br>>> Job<br>>> dev-dvb-adapter0-frontend0.device/start timed out.<br>>> Aug 13 11:03:48 mythpc systemd[1]: Timed out waiting for device<br>>> dev-dvb-adapter0-frontend0.device.<br>>> Aug 13 11:03:48 mythpc systemd[1]: dev-dvb-adapter0-frontend0.device: <br>>> Job<br>>> dev-dvb-adapter0-frontend0.device/start failed with result 'timeout'.<br>><br>> That is not good. The new systemd jobs to detect the creation of the<br>> tuners are not actually working. Instead, they are timing out. The<br>> timeout is long enough so that when mythbackend gets started, the<br>> tuner devices are actually present, so mythbackend seems to be seeing<br>> working tuners once it gets started, but the timeouts likely slow down<br>> booting much more than needs to happen.<br>><br>>> Aug 13 11:03:48 mythpc systemd[1]: Started MythTV Backend.<br>>> Aug 13 11:03:48 mythpc systemd[1]: Reached target Multi-User System.<br>>> Aug 13 11:03:48 mythpc systemd[1]: Reached target Graphical Interface.<br>>> Aug 13 11:03:48 mythpc systemd[1]: Started Stop ureadahead data <br>>> collection<br>>> 45s after completed startup.<br>>> Aug 13 11:03:48 mythpc systemd[1]: Starting Update UTMP about System<br>>> Runlevel Changes...<br>>> Aug 13 11:03:48 mythpc systemd[1]: Started Update UTMP about System<br>>> Runlevel Changes.<br>>> Aug 13 11:03:48 mythpc systemd[1]: Startup finished in 1.798s (kernel) +<br>>> 1min 30.619s (userspace) = 1min 32.418s.<br>>> Aug 13 11:03:49 mythpc kernel: [ 92.670822] tda10048_firmware_upload:<br>>> waiting for firmware upload (dvb-fe-tda10048-1.0.fw)...<br>>> Aug 13 11:03:49 mythpc kernel: [ 92.671115] tda10048_firmware_upload:<br>>> firmware read 24878 bytes.<br>>> Aug 13 11:03:49 mythpc kernel: [ 92.671118] tda10048_firmware_upload:<br>>> firmware uploading<br>>> Aug 13 11:03:52 mythpc kernel: [ 95.647746] tda10048_firmware_upload:<br>>> firmware uploaded<br>>> Aug 13 11:03:52 mythpc kernel: [ 95.718869] tda18271: performing RF<br>>> tracking filter calibration<br>>> Aug 13 11:03:54 mythpc kernel: [ 98.071954] tda18271: RF tracking <br>>> filter<br>>> calibration complete<br>>> Aug 13 11:03:56 mythpc kernel: [ 99.888159] tda10048_firmware_upload:<br>>> waiting for firmware upload (dvb-fe-tda10048-1.0.fw)...<br>>> Aug 13 11:03:56 mythpc kernel: [ 99.888203] tda10048_firmware_upload:<br>>> firmware read 24878 bytes.<br>>> Aug 13 11:03:56 mythpc kernel: [ 99.888204] tda10048_firmware_upload:<br>>> firmware uploading<br>>> Aug 13 11:03:59 mythpc kernel: [ 102.851201] tda10048_firmware_upload:<br>>> firmware uploaded<br>><br>> And here more firmware is loaded for the HVR-2200 tuners, AFTER<br>> mythbackend has been started. So the HVR-2200 tuners may not actually<br>> have been fully working when mythbackend was started. On the LinuxTV<br>> Wiki page:<br>><br>> <a href="https://www.linuxtv.org/wiki/index.php/Hauppauge_WinTV-HVR-2200">https://www.linuxtv.org/wiki/index.php/Hauppauge_WinTV-HVR-2200</a><br>><br>> there are reports that recording has problems every half an hour or so<br>> without the dvb-fe-tda10048-1.0.fw file being loaded, so it may be<br>> that having loaded late is OK, but it is still a bad idea. But it may<br>> also be that the dvb-fe-tda10048-1.0.fw firmware file never gets<br>> loaded until something tries to use the HVR-2200 tuners, which<br>> mythbackend does at startup.<br><br>Yes,I know of this problem.I had it happen to me on 12.04 so I make sure all the driver files are where they should be.<br>><br>> Please do two test runs, where you boot, wait for everything to start<br>> up, then run LiveTV on a channel, watch for a few seconds, then stop<br>> it. Do that in both 12.04 and 16.04 and post the complete syslog and<br>> mythbackend.log file from start of booting until LiveTV is finished.<br>><br>>> Aug 13 11:04:34 mythpc systemd[1]: Starting Stop ureadahead data<br>>> collection...<br>>> Aug 13 11:04:34 mythpc systemd[1]: Stopped Read required files in <br>>> advance.<br>>> Aug 13 11:04:34 mythpc systemd[1]: Started Stop ureadahead data <br>>> collection.<br>>><br>>><br>>><br>>> Also, the reboot and shutdown options in frontend have ceased to<br>>> function.These are performed by /sbin/reboot and /sbin/poweroff <br>>> correct?<br>><br>> Yes and no. Before systemd, the reboot command was a real executable<br>> file and poweroff was a link to the reboot file. The reboot file<br>> detected whether it was called via the poweroff link or directly in<br>> order to decide whether it should just power off or reboot. Now, that<br>> function is done by systemctl and both reboot and poweroff are links<br>> to /bin/systemctl and systemctl detects whether it is being run via a<br>> link as to which function it should perform. So if the /sbin links to<br>> systemctl do not work now for some reason when used from MythTV, you<br>> should probably just put the base command into the MythTV settings<br>> instead of using the links:<br>><br>> /bin/systemctl reboot<br>> /bin/systemctl poweroff<br>><br>> _______________________________________________<br>Here's a link to a text file with the log snippets you requested:</div><div><a href="https://drive.google.com/open?id=0B5RRWPLTmilhLUFhLTFkN3dEeUU">https://drive.google.com/open?id=0B5RRWPLTmilhLUFhLTFkN3dEeUU</a><br><br></div></body></html>