HD Homerun not detected / lost at boot / reboot

Thanks for taking the time to report the bug. This was supposed to be
resolved with a patch sometime ago as I recall. Since it appear to not have
been we can look into the issue. We will be needing more infomation from you
as the bug is investigated.

However in the mean time the process you described to get your HDHR device
back online is outdated/inncorrect. A very simple way to get the HDHR device
back online when this occurs:

1) hdhomerun_config discover
2) sudo /etc/init.d/mythtv-backend restart

This can be completed via ssh to yor mythtv box o from a terminal on the
machine itself.

-Nick

On Sun, Jun 7, 2009 at 12:07 PM, Ian Story <email address hidden> wrote:

> Public bug reported:
>
> I am using mythbuntu 9.04.
>
> Per the thread below, it seems to be a well documented issue, and I have
> seen it personally since 7.10 - while the HD Homerun is supported, it is
> not detected at startup or restart. This means, frustratingly, that for
> HD Homerun users, you have to exit the frontend, run mythtv-setup, and
> re-add your tuners, on every boot or reboot. The fix would appear to be
> to start Myth later in the boot process, long after the network is
> started up, etc.
>
> http://ubuntuforums.org/showthread.php?t=683389
>
> Thank you for your consideration, I know that not everyone has the HD
> Homerun, but for those of us that do, it would be a very big help to
> have it fixed in the next release, rather than us manually hacking our
> installs.
>
> Ian Story
>
> ** Affects: mythbuntu
> Importance: Undecided
> Status: New
>
>
> ** Tags: forget hd hdhomerun home homerun lost reboot restart run
>
> --
> HD Homerun not detected / lost at boot / reboot
> https://bugs.launchpad.net/bugs/384556
> You received this bug notification because you are a member of Mythbuntu
> Developers, which is subscribed to Mythbuntu.
>

Thank you Nick! I will try those out the next time I reboot (and will do that deliberately sometime today when nothing is recording to try it out) and report back. I would be glad to provide any other information that would help in solving the problem as you look further into it, just let me know!

Best,

Ian

I have this bug worked around with a script that polls until the HDHomeRuns show up on the network before allowing mythbackend to start.

#!/bin/bash
let retries=0
echo "Waiting for network to reach HDHomeRun"
until hdhomerun_config discover >/dev/null
do
  if [ $retries -gt 15 ]
    then
    echo "Timed out, no HDHomeRun found"
    exit 1
  fi
  echo -n "-"
  sleep 1
  let retries=retries+1
done
echo "HDHomeRun found"

This is is the RC2.d directory with a S# lower than the one used by S#mythtv-backend

@Nick Fox:
Thanks Nick! I did a reboot just now and when I rebooted, as expected, the HDHomeRun was not there...then I ran the two commands you suggested in the terminal:

1) hdhomerun_config discover
2) sudo /etc/init.d/mythtv-backend restart

And presto, there it was! Happy about that.

@DAP:
That doesn't look too scary, I will think about that as a workaround...at the same time, it is good that you have the same problem (a little confirmation for me and my other friend who also sees this that it isn't specific to us and is working for the rest of the world :) If I implement that your suggestion, I will also reply here.

Thanks again to both of you!

Ian

One other comment, when looking into DAP's suggestion, I noticed that the current order of items in my /etc/rc2.d has S24mythtv-backend and S50NetworkManager.

From what (little) I understand of the problem, it seems that if you start mythtv-backend prior to the NetworkManager, that it can't find your HDHomeRuns since the network isn't up yet and they are network devices. Perhaps changing S24mythtv-backend to S51mythtv-backend (which I think would make it start after the NetworkManager), would work?

I am hesitant to just do that though, not knowing if there are other things that come after S24mythtv-backend and before S50NetworkManager (like S30gdm, S50acpid, S50avahi-daemon, on my system at least) would freak out if mythtv-backend isn't started yet...I wouldn't think so, but since this is the first time I've even looked in here, don't want to change things and screw something up on a box that I (and my family) depend on so much! :)

At any rate, to DAP's suggestion, my fear is that if I put that in place as say, S22fixHDHomeRun that it wouldn't work, as even then, the network isn't starting until S50NetworkManager (again, if I understand correctly)...so it seems the best thing would be to just move S24mythtv-backed further back in the process...?

Thanks,

Ian

Ian,

Try this:

sudo mv /etc/rc2.d/S24mythtv-backend /etc/rc2.d/S99mythtv-backend

Then reboot and see if things are happy.

-Nick

On Sun, Jun 7, 2009 at 7:05 PM, Ian Story <email address hidden> wrote:

> One other comment, when looking into DAP's suggestion, I noticed that
> the current order of items in my /etc/rc2.d has S24mythtv-backend and
> S50NetworkManager.
>
> >From what (little) I understand of the problem, it seems that if you
> start mythtv-backend prior to the NetworkManager, that it can't find
> your HDHomeRuns since the network isn't up yet and they are network
> devices. Perhaps changing S24mythtv-backend to S51mythtv-backend (which
> I think would make it start after the NetworkManager), would work?
>
> I am hesitant to just do that though, not knowing if there are other
> things that come after S24mythtv-backend and before S50NetworkManager
> (like S30gdm, S50acpid, S50avahi-daemon, on my system at least) would
> freak out if mythtv-backend isn't started yet...I wouldn't think so, but
> since this is the first time I've even looked in here, don't want to
> change things and screw something up on a box that I (and my family)
> depend on so much! :)
>
> At any rate, to DAP's suggestion, my fear is that if I put that in place
> as say, S22fixHDHomeRun that it wouldn't work, as even then, the network
> isn't starting until S50NetworkManager (again, if I understand
> correctly)...so it seems the best thing would be to just move S24mythtv-
> backed further back in the process...?
>
> Thanks,
>
> Ian
>
> --
> HD Homerun not detected / lost at boot / reboot
> https://bugs.launchpad.net/bugs/384556
> You received this bug notification because you are a member of Mythbuntu
> Developers, which is subscribed to Mythbuntu.
>

Nick, that does indeed solve the problem, changing it to start in S99 instead of S24 fixed it...I shutdown and then did a cold boot, it worked, I did a warm boot (restart) and it worked, and then just to be safe, I set my frontend to auto start at login again (yay! was really missing that, but having it run at login before was dumb since I'd then just have to quit it and go into the setup anyway), and it still worked. I feel pretty good about it!

Hopefully this fix can be merged into the next release of Mythbuntu and make a lot of people happy - or me at least (not that I couldn't just do it manually again).

Thank you very much (and DAP, thanks to you too, your suggestion put us on the path of delaying it a bit, not script needed though, thankfully).

Best,

Ian

So we're hopefully switching to an upstart script. If we don't, then we need to get this done.

Thanks Mario - that would be real nice, but like you said, if you don't make the switch, it should be fixed.

That said, fixing it hopefully wouldn't be a big deal, as Nick's suggestion above (post #6 - https://bugs.launchpad.net/mythbuntu/+bug/384556/comments/6 ) has indeed fixed it, and now stood the test of time (well, at least the last few months, with some reboots thrown in (both warm and cold) for good measure, has been very good.

Best,

Ian

--- On Sun, 8/9/09, Mario Limonciello <email address hidden> wrote:

> From: Mario Limonciello <email address hidden>
> Subject: [Bug 384556] Re: HD Homerun not detected / lost at boot / reboot
> To: <email address hidden>
> Date: Sunday, August 9, 2009, 8:15 PM
> So we're hopefully switching to an
> upstart script.  If we don't, then we
> need to get this done.
>
> ** Also affects: mythtv (Ubuntu)
>    Importance: Undecided
>        Status: New
>
> --
> HD Homerun not detected / lost at boot / reboot
> https://bugs.launchpad.net/bugs/384556
> You received this bug notification because you are a direct
> subscriber
> of the bug.
>
> Status in Mythbuntu, Ubuntu derivative focused upon MythTV:
> New
> Status in “mythtv” package in Ubuntu: New
>
> Bug description:
> I am using mythbuntu 9.04.
>
> Per the thread below, it seems to be a well documented
> issue, and I have seen it personally since 7.10 - while the
> HD Homerun is supported, it is not detected at startup or
> restart.  This means, frustratingly, that for HD
> Homerun users, you have to exit the frontend, run
> mythtv-setup, and re-add your tuners, on every boot or
> reboot.  The fix would appear to be to start Myth later
> in the boot process, long after the network is started up,
> etc.
>
> http://ubuntuforums.org/showthread.php?t=683389
>
> Thank you for your consideration, I know that not everyone
> has the HD Homerun, but for those of us that do, it would be
> a very big help to have it fixed in the next release, rather
> than us manually hacking our installs.
>
> Ian Story
>

The problem is within MythTV, it establishes a connection once when the backend starts and makes no attempt to reconnect; this was fixed in MythTV last month -

http://svn.mythtv.org/trac/ticket/6672

Suggest updating the MythTV package.

Hi Mike:

That's great! We're hopefully jumping to 0.22 for karmic (provided it's out
in a timely fashion), but this patch would do the trick in the interim or in
case that doesn't happen.

On Mon, Aug 10, 2009 at 04:03, Mike Baker <email address hidden> wrote:

> The problem is within MythTV, it establishes a connection once when the
> backend starts and makes no attempt to reconnect; this was fixed in
> MythTV last month -
>
> http://svn.mythtv.org/trac/ticket/6672
>
> Suggest updating the MythTV package.
>
> ** Bug watch added: mythtv.org bug tracker #6672
> http://svn.mythtv.org/trac/ticket/6672
>
> --
> HD Homerun not detected / lost at boot / reboot
> https://bugs.launchpad.net/bugs/384556
> You received this bug notification because you are a member of Mythbuntu
> Developers, which is subscribed to Mythbuntu.
>

--
Mario Limonciello
<email address hidden>

This bug was fixed in the package mythtv - 0.21.0+fixes21261-0ubuntu1

---------------
mythtv (0.21.0+fixes21261-0ubuntu1) karmic; urgency=low

  * New upstream -fixes snapshot (21261)
    - Fixes HDHomerun compatibility issues with reboot. (LP: #384556)
    - LCDproc compatibility. (LP: #392362)
  * debian/control:
    - Build depends on libpulse0 so that pulseaudio disabling code works.
  * debian/rules:
    - Don't compress perl and python scripts that are installed. (LP: #380812)
  * debian/mythtv-backend.init:
    - If for some reason $USER_HOME doesn't exist, make it. (LP: #326702)

 -- Mario Limonciello <email address hidden> Sun, 16 Aug 2009 00:26:55 -0500

http://laroyaleseresienne.be/product.php?page=6fa