[mythtvnz] New install setup - recording problem

[Nick Rout]

On Sat, Aug 27, 2016 at 9:23 AM, Paulgir <paulgir at gmail.com> wrote:

>
> The use of systemd in 16.04 is what makes the difference in booting.
>> Systemd works completely differently from upstart, and allows things
>> to start better in parallel, rather than having to wait and start in
>> sequence.  But because of that, you can get race conditions if you do
>> not set up the startup conditions properly.  The mythbackend startup
>> conditions in the package as installed are only OK for systems that do
>> not have external access to MythTV and which have very standard
>> tuners.  Putting in the right conditions (which is where I hope we
>> have arrived at now) should allow mythbackend to start at the right
>> time.
>>
>> The reports about mythtv-setup taking ages to get to the new capture
>> card page are likely what I saw when I first tried 0.28 on 16.04. That
>> is a problem with the code supporting the new VBox network tuners,
>> where the code involved takes a very long time to decide that there
>> are no VBoxes on the network.  In my case, that happened because I had
>> not set up my networking on my new test box at that point, so it was
>> not working properly.  Once I sorted out my network setup, the long
>> timeout waiting for VBox detection went away, although it still takes
>> longer than it used to.  The reason for the problem was quite visible
>> in the xterm window that pops up to run mythtv-setup.real - I could
>> see the messages about VBoxes when I swapped to that window while I
>> was waiting for mythtv-setup.real to open the new tuner page. VBox
>> support is new in 0.28 and I think this problem is just a bug, but I
>> have not checked to see if it has been reported yet.
>>
>
> In my case networking was the first thing I setup.I used remmina remote
> desktop to work on the PVR,so it is the first task on a new install.Then I
> tried HDHR configure GUI and that always worked so networking was
> functional.So I'm skeptical whether this applies to my situation.


The point is not whether networking works on your machine, but whether
networking is started when mythbackend starts. If networking isn't up when
mythbackend starts, it won't be able to see the networked HDHR.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ourshack.com/pipermail/mythtvnz/attachments/20160827/9390cc28/attachment.html>