<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p><br>
</p>
<div class="moz-cite-prefix">On 7/27/20 12:34 PM, James Abernathy
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CANFv2E=Rb=B_AuHSJ4u-Mu+C6jLQ7cSFxwH0hRcaQa7Hy1z-_Q@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="ltr">
<div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left:1px solid
rgb(204,204,204);padding-left:1ex">
<br>
You will have created those udev rules and the override file
manually.<br>
<br>
Those udev rules create the .device targets. The reason for
having<br>
those targets is that it is possible for mythbackend to
start before<br>
the tuners are created, and having it wait on the device
targets<br>
prevents that. If mythbackend starts before a tuner is
working, when<br>
it tests the tuner at startup that tuner will not work and
mythbackend<br>
will mark it as failed and not test it again until the next
startup of<br>
mythbackend.<br>
<br>
If you only have the one tuner in the 20.04 system, you need
to<br>
comment out all the Wants/After lines referring to
non-existent<br>
tuners. Otherwise mythbackend will only start after a very
long<br>
timeout waiting for those tuners.<br>
<br>
</blockquote>
<div>It was very interesting when I deleted all my backend
tuners recently and added them back in on my 18.04 v31
system, I ended up with only one adapter name and when I
added all 4 there was only one name repeated 4 times.</div>
<div> </div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left:1px solid
rgb(204,204,204);padding-left:1ex">
If you are using networked tuners such as HDHomeruns, you
should have<br>
one of the fixes (such as mine) that prevents mythbackend
from<br>
starting before the network us up enough for it to access
the<br>
networked tuners. Waiting for
NetworkManager-wait-online.service is<br>
not sufficient to ensure that, and each version of Ubuntu
tends to<br>
start up faster than the previous version, so mythbackend is
getting<br>
started earlier and earlier. So if it was working OK
without such a<br>
fix in 18.04, it may not in 20.04. It is best to use
something that<br>
pings a networked tuner before it allows mythbackend to be
started.<br>
Search this list's archives for "wait-until-pingable.py" to
find the<br>
threads for my fix.<br>
<br>
And the speed of the SSD you have the system on also affects
the<br>
startup speed. A new system with a super fast M.2 NVMe SSD
and lots<br>
of RAM can cause interesting surprises with how fast things
start up.<br>
<br>
</blockquote>
<div>So it sounds like for 20.04, I'll continue to create the
udev rules and to be safe put back in the wait-for-ping
stuff I had back in the v29 days.</div>
<div><br>
</div>
<div>I also noticed that Hauppauge Linux has added Ubuntu
20.04 to their list on supported O/S's on their PPA (<a
href="https://hauppauge.com/pages/support/support_linux.html"
moz-do-not-send="true">https://hauppauge.com/pages/support/support_linux.html</a>)</div>
<div> </div>
<div>Jim A<br>
</div>
</div>
</div>
</blockquote>
<p>Stephen,<br>
</p>
<p>So I've created the wait-for-ping stuff from your server. Do I
still need my override conf file with:</p>
<blockquote>
<p>[Unit]<br>
Wants=dev-dvb-adapter0-frontend0.device<br>
After=dev-dvb-adapter0-frontend0.device<br>
Wants=dev-dvb-adapter1-frontend0.device<br>
After=dev-dvb-adapter1-frontend0.device<br>
Wants=dev-dvb-adapter2-frontend0.device<br>
After=dev-dvb-adapter2-frontend0.device<br>
Wants=dev-dvb-adapter3-frontend0.device<br>
After=dev-dvb-adapter3-frontend0.device<br>
<br>
After=NetworkManager-wait-online.service<br>
</p>
</blockquote>
<br>
My guess is I don't need the
After=NetworkManager-wait-online.serivce since I have the wait for
ping stuff.
<p>Jim A</p>
<p><br>
</p>
<p><br>
</p>
</body>
</html>