[mythtv] [mythtv-dev] r14971 issues w/ CPU and remote

Michael Wisniewski wiz561 at gmail.com
Thu Nov 29 04:05:09 UTC 2007


Alright...  Here's what's going on.

I checked out rev 14949 and the remote works.  When I checked out
14963, it breaks the remote.

There must be something between 49 and 63 that breaks the remote.  I
haven't done much research more than this....but just thought others
might have an idea.


Thanks!!!



On Nov 28, 2007 9:11 PM, Michael Wisniewski <wiz561 at gmail.com> wrote:
> Well, it seems like the latest revision I just checked out tonight
> fixed the high cpu problem.  However, the remote definitely does not
> work with it.  If I run 'irw', I can see commands from the remote
> working properly...
>
> I'm checking out rev 14963 to see if it works with the remote or not.
>
> Also, did I happen to miss something just to make sure the lircrc
> config didn't change?
>
>
> Thanks!
>
> Mike
>
>
>
> On Nov 28, 2007 8:06 PM, Michael Wisniewski <wiz561 at gmail.com> wrote:
> > Ah, thank you for the response.  I'm glad to see that I wasn't the
> > only person having problems.
> >
> > If I get some time after my show is on, I'll try to compile the latest
> > version in svn and see what happens.  Who knows, maybe the remote will
> > start working again!!!
> >
> > I'll report back a little later on...  :-)
> >
> >
> > thanks,
> > mike
> >
> >
> >
> > On Nov 28, 2007 7:44 PM, Nigel Pearson <nigel at ind.tansu.com.au> wrote:
> > > > I too had this exact problem: The cause was the new improved upnp
> > > > code in
> > > > 14964.  Rolling that changeset back (svn merge -c -14964
> > > > http://svn.mythtv.org/svn/trunk/mythtv) fixed everything up.
> > >
> > > Just committed a quick fix, which should rectify the CPU problem.
> > >
> > >
> > > Not sure you mean by the "remote" issue.
> > > Hopefully these are the same problem?
> > >
> > >
> > >
> > > > Also, with verbose logging, I was getting some messages about upnp,
> > > > even with
> > > > the --noupnp switch, and the same CPU problem.  Is this option being
> > > > respected with the new code?
> > >
> > > There are two flags.
> > >
> > > --noupnp  to prevent a backend from publishing
> > >            itself on the network as a UPnP server, and
> > >
> > > --disable-autodiscovery
> > > which prevents the UPnP Backend Selection chooser window
> > > from being displayed.
> > >
> > >
> > > The latter flag does _not_ prevent UPnP autodiscovery.
> > >
> > > Having your database on localhost, or a valid mysql.txt,
> > > are meant to be the way to eliminate any UPnP searching
> > > (but my skills don't seem to be matching my goals lately)
> > >
> > > --
> > > Nigel Pearson, nigel at ind.tansu.com.au| $50 million worth of
> > > Telstra Net. Eng., Sydney, Australia | hardware and you didn't
> > > Office: 9202 3900    Fax:  9261 3912 | think we'd throw in a GPS?
> > > Mobile: 0408 664435  Home: 9792 6998 |  - Jonas, Bionic Woman
> > >
> > >
> > >
> > > _______________________________________________
> > > mythtv-dev mailing list
> > > mythtv-dev at mythtv.org
> > > http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev
> > >
> >
>


More information about the mythtv-dev mailing list