[mythtv-users] HDHR and SVN

Jake Palmer jakep_82 at hotmail.com
Thu Apr 5 20:34:09 UTC 2007


>From: Jarod Wilson <jarod at wilsonet.com>
>
>On Thursday 05 April 2007 13:16:29 Jake Palmer wrote:
> > >From: Jarod Wilson <jarod at wilsonet.com>
> > >
> > >On Thursday 05 April 2007 10:27:25 Tom Lichti wrote:
> > > > Willy Boyd wrote:
> > > > > On 4/5/07, William Munson <william_munson at bellsouth.net> wrote:
> > > > >> You do not need a specific version from svn, you need a version 
>that
> > >
> > >is
> > >
> > > > >> newer than 12618. If you follow the advise of the other poster 
>and
> > > > >> change your yum.conf settings, you will download a version which
> > > > >> will work just fine. Please note that for most people a hdhr will
> > > > >> not automatically assign the channels it finds with the correct
> > > > >> channel
> > >
> > >in
> > >
> > > > >> the zap2it lineup. You will need to do that manually. There are
> > >
> > >numerous
> > >
> > > > >> howto and newsgroup postings on how to do that association.
> > > > >>
> > > > >> You do not need to compile the latest svn to get support for the
> > > > >> hdhr however it would not hurt anything if you decided to "roll 
>your
> > > > >> own". There are also many howto on setting up and using svn.
> > > > >>
> > > > >> Good luck,
> > > > >> William
> > > > >
> > > > > If I'm not mistaken, it's the other way around.  The advice
> > > > > concerning revision 12618 was to use that one (or older), because
> > > > > something that got checked in after that is causing problems for 
>some
> > > > > people with the HDHR.  Anything newer has that same issue.  BUT,
> > > > > current results seem that if you enable "quick tuning" in
> > > > > mythtv-setup for your HDHR, it seems to resolve the issue.
> > > > >
> > > > > I just got my HDHR a few days ago and I'm still going through the 
>80%
> > > > > or so channels that the scanner "found" but aren't tunable, and
> > > > > putting in xmltvid's for the rest.  So I haven't personally
> > > > > encountered the PMT bug that supposedly 12619+ introduces.
> > > >
> > > > That is correct, but may be moot. I had the problem with anything 
>past
> > > > 12618 not working right, so I reverted to 12618, did the channel 
>scan,
> > > > fixed all the lineups, and I am now running current SVN with the 
>latest
> > > > HDHR firmware, with quicktune enabled, and I am not experiencing any
> > > > problems. I have not tried a channel scan with current SVN, so I 
>can't
> > > > comment on whether or not that works.
> > >
> > >Channel scanning is currently hosed in the release-0-20-fixes branch,
> > > which is
> > >what ATrpms tracks, and that's for both DVB cards and the HDHomeRun. I
> > >haven't had time to dig into why that is yet (still catching up on list
> > >mail
> > >to see if someone else has). At the very least, I'm positive things 
>worked
> > >at
> > >least as recently as 12782 and 12783, as I'm the one who checked those 
>in
> > >after testing them with my own HDHomeRun. I've got the day off 
>tomorrow,
> > >hopefully I'll find some time to get around to tracking down the fix 
>and
> > >checking it in...
> >
> > So the scanning issue is unrelated to the PMT issue in bug 3031?
>
>Yep, unrelated. Been poking at it some with Janne's help, and it looks like 
>we
>*are* finding channels, but they're not being properly parsed and added to
>the database.
>
>2007-04-05 13:14:37.654 SIScan(0): HandlePostInsertion() pat(1)
>2007-04-05 13:14:37.654 SIScan(0): Post insertion found PAT..
>2007-04-05 13:14:37.654 SIScan(0): UpdatePATinDB(): tsid: 0x82c2  mplex: 4
>2007-04-05 13:14:37.655 UpdatePATinDB(): Prog 8 PID 48: PMT @0x123b180
>2007-04-05 13:14:37.655 UpdatePATinDB(): Prog 5 PID 49: PMT @0x2f90480
>2007-04-05 13:14:37.655 UpdatePATinDB(): Prog 2 PID 50: PMT @0x37fbcd0
>2007-04-05 13:14:37.655 UpdatePATinDB(): Prog 3 PID 51: PMT @0x3f7a0c0
>2007-04-05 13:14:37.655 UpdatePATinDB(): Prog 4 PID 53: PMT @0x113f5e0
>2007-04-05 13:14:37.655 UpdatePATinDB(): Prog 1 PID 55: PMT @0x49c4bc0
>2007-04-05 13:14:37.656 UpdatePATinDB(): Prog 6 PID 52: PMT @0x4245e30
>2007-04-05 13:14:37.656 UpdatePATinDB(): Prog 7 PID 54: PMT @0x48d4cc0
>
>In my case, this seems to have something to do with the fact Comcast 
>decided
>to start sending channel names and program info down the pipe.
>
>--
>Jarod Wilson
>jarod at wilsonet.com

Darn!  I have a couple DVB cards and I've been stuck at 12618 for more than 
2 months.  I was hoping your work might help to resolve the PMT problem.

Jake

_________________________________________________________________
Download Messenger. Join the iím Initiative. Help make a difference today. 
http://im.live.com/messenger/im/home/?source=TAGHM_APR07



More information about the mythtv-users mailing list