[mythtv-users] My last few steps to FC3 success :)

Chris Lynch tsw at one.net
Thu Dec 16 02:00:58 UTC 2004

Thanks for the advice - this worked!

I added the following line in my /etc/rc.d/rc.local:
/sbin/service mythbackend restart

That seemed to solve the problem and got me thinking of if there was
something similar I could do with my nvidia settings.  I added the
"nvidia-settings --load-config-only &" line to a startup script in my mythtv
user's KDE autostart directory.  That seemed to solve that as well.

Thanks for the help - I only have one outstanding problem and that is that
it seems Myth is crashing if I'm watching Live TV when a scheduled recording
comes on.  Has anyone else experienced this?



-----Original Message-----
From: mythtv-users-bounces at mythtv.org
[mailto:mythtv-users-bounces at mythtv.org] On Behalf Of Dan Boger
Sent: Wednesday, December 15, 2004 4:59 AM
To: Discussion about mythtv
Subject: Re: [mythtv-users] My last few steps to FC3 success :)

On Tue, Dec 14, 2004 at 11:45:14PM -0800, Chris Lynch wrote:
> - If a restart the box and go to Live TV, I cannot change channels.
>   The OSD shows up totally blank and it pauses for a moment and then
>   stays on the same channel. Now, if I close out of live TV, then
>   bring up a terminal and do a "/sbin/service mythbackend restart" as
>   root, all is well. My channels then show in the OSD and I can change
>   channels without issue. This seems like I may have some sort of
>   timing issue problem as to when the backend is starting up since it
>   does work if I restart the backend?

I've run into this.  I believe what happens is that the mythbackend starts
before the user mythtv autologins to the box, so it's before mythtv assumed
ownership of the console devices - including /dev/video0.
That's why a restart fixes the problem - you're restarting the backend AFTER
mythtv logged in, and so there's no permission issues.

I think you can find the indicator in the mythbackend.log file, something
about permission denied when opening video0.

My fix was just to have the backend restart (as root) in mythtv's login



More information about the mythtv-users mailing list