<div dir="ltr"><div dir="ltr"><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, Jul 27, 2020 at 11:55 AM Mike Bibbings <<a href="mailto:mike.bibbings@gmail.com">mike.bibbings@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On 27/07/2020 15:43, James Abernathy wrote:<br>
> I'm doing some planning for moving from MythTV v31 on Ubuntu 18.04 to <br>
> MythTV v31 on Ubuntu 20.04. There are a lot of considerations, like <br>
> my current system using MariaDB and the current issue regarding that <br>
> on Ubuntu 20.04.<br>
><br>
> However, my concerns today are related to udev rules and systemd <br>
> overrides.<br>
><br>
> On my 18.04 system, I have one udev rule related to mythtv; <br>
> 99-mythbackend.rules<br>
><br>
> SUBSYSTEM=="video4linux", TAG+="systemd"<br>
> SUBSYSTEM=="dvb", TAG+="systemd"<br>
> SUBSYSTEM=="firewire", TAG+="systemd"<br>
><br>
> When I installed mythtv v31 on a virtual machine of Ubuntu 20.04, this <br>
> file was not there. I probably created it myself because of the <br>
> Hauppauge WinTV HD Quad PCIe tuner card I was using.<br>
><br>
> So is this still necessary for Ubuntu 20.04 and mythtv v31?<br>
><br>
> Also, on my current system I have an override file in <br>
> /etc/systemd/system/mythtv-backend.service.d/ythtv-backend-override.conf:<br>
> [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>
><br>
> I figure this is also related to the Hauppauge card and also my <br>
> HDHomerun tuner.<br>
><br>
> Again I think I did this back with mythtv29 and it's stayed through <br>
> the upgrades to v31.<br>
><br>
> Do I need any of this in mythtv v31 on Ubuntu 20.04?<br>
><br>
> On the Ubuntu 20.04 test virtual machine I have only the HDHR tuner <br>
> and it works fine but I have no udev rules or systemd override file.<br>
><br>
> Thoughts?<br>
><br>
> Jim A<br>
><br>
Jim,<br>
<br>
Yes, you did setup those entries for your PCI-e tuner, they make sure <br>
mythtvbackend starts only when the card has been fully setup during boot.<br>
<br>
<br>
For network tuners e.g. HDHOMERUN there is a different problem in that <br>
mythtv-backend can start before networking is fully established see <br>
<a href="https://lists.gt.net/mythtv/users/625986#625986" rel="noreferrer" target="_blank">https://lists.gt.net/mythtv/users/625986#625986</a><br>
<br>
<br>
Mike<br></blockquote><div><br></div><div>So it seems the udev rules for the PCIe cards are still required in Ubuntu 20.04, right?</div><div><br></div><div>I'm aware of the systemd stuff for networked tuners that you linked to. In fact I had to use that back with v29 when you had to use external recorders in mythtv-setup in the card section for TCP communication to HDHomerun tuners, because that software took a while to start up. However, for some reason when I upgraded to v30/31 I removed that and now am left with what I showed above.</div><div><br></div><div>I know that with my HDHR4-2US and HDHR5-4US networked tuners I don't need anything in systemd for either Ubuntu 20.04 or Raspberry Pi OS on RPi4.</div><div><br></div><div>At least I've been lucky. Everytime I reboot my tuners are available and working in mythtv-backend without systemd overrides.</div><div><br></div><div>Jim A</div><div><br></div></div></div>