A bit of background: I'm running RHL9, a WinTV PVR-250, a GeForce 4 Ti
for s-video out to my TV and MythTV out of CVS...
I've been busy trying to verify the correctness/completeness of the
guide I've been putting together (you can find the work-in-progress
here: http://pvrhw.goldfish.org/tiki-page.php?pageName=rh9pvr250 ), and
I've found a relatively major problem with this whole setup... If the
mythbackend loads before X, all I get is channel 4 in MythTV, I can't
change the channel, and I don't get any OSD show info (but the box at
the bottom and the time show up).
It states in the /etc/init.d/mythbackend script that it loads after X,
but this is not the case (at least not under RHL9). It is loading up
well before X, which is the only reason I can figure out for it not
working (it still fails if called from rc.local, the last init script
run). If I disable the init script from loading it at startup, then
manually start it up (from a root shell) after X loads, everything is
fine...
However, I'm not sure why this would end up being the case, because the
frontend and backend can be on different computers, and the backend
doesn't even have to run X, so why would proper functionality of the
backend require that X was already loaded?
I haven't figured out a workaround just yet, since daemonizing the
mythbackend requires root privileges, and there's no easy way to get an
automated root-enabled launching after a non-privileged user's login
starts (my mythtv user). Perhaps it is a problem with the cvs version...
Anyone have any ideas?
for s-video out to my TV and MythTV out of CVS...
I've been busy trying to verify the correctness/completeness of the
guide I've been putting together (you can find the work-in-progress
here: http://pvrhw.goldfish.org/tiki-page.php?pageName=rh9pvr250 ), and
I've found a relatively major problem with this whole setup... If the
mythbackend loads before X, all I get is channel 4 in MythTV, I can't
change the channel, and I don't get any OSD show info (but the box at
the bottom and the time show up).
It states in the /etc/init.d/mythbackend script that it loads after X,
but this is not the case (at least not under RHL9). It is loading up
well before X, which is the only reason I can figure out for it not
working (it still fails if called from rc.local, the last init script
run). If I disable the init script from loading it at startup, then
manually start it up (from a root shell) after X loads, everything is
fine...
However, I'm not sure why this would end up being the case, because the
frontend and backend can be on different computers, and the backend
doesn't even have to run X, so why would proper functionality of the
backend require that X was already loaded?
I haven't figured out a workaround just yet, since daemonizing the
mythbackend requires root privileges, and there's no easy way to get an
automated root-enabled launching after a non-privileged user's login
starts (my mythtv user). Perhaps it is a problem with the cvs version...
Anyone have any ideas?