That would be a REALLY useful function, but alas.. FC3 doesn't use it..
>> With Debian-based distros, the *proper* way to load a hardware module
>> at boot time is to add the module's name to the list in /etc/modules
>> and allow the /etc/init.d/module-init-tools script load it at the
>> appro
On 6/29/05, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> On Wed, Jun 29, 2005 at 12:40:12AM +0100, Nick wrote:
> > > Is there a correct way to load the module WAY earlier? I'm thinking
> > > there's
> > > a more correct way to get it to load first.. before any of the /etc/init.d
> > > stuff run
On Wed, Jun 29, 2005 at 12:40:12AM +0100, Nick wrote:
> > Is there a correct way to load the module WAY earlier? I'm thinking there's
> > a more correct way to get it to load first.. before any of the /etc/init.d
> > stuff runs.
> I run the modprobes (2 cards) and start mythbackend from rc.local (
Nick wrote:
On 6/29/05, Michael T. Dean <[EMAIL PROTECTED]> wrote:
Nick wrote:
On 6/28/05, Michael Jones <[EMAIL PROTECTED]> wrote:
The problem was that the command modprobe ivtv was being executed after
mythbackend was started. (hmm.. what a surprise)
I run the modprobes (2 cards) an
On 6/29/05, Michael T. Dean <[EMAIL PROTECTED]> wrote:
> Nick wrote:
>
> >On 6/28/05, Michael Jones <[EMAIL PROTECTED]> wrote:
> >
> >
> >>The problem was that the command modprobe ivtv was being executed after
> >>mythbackend was started. (hmm.. what a surprise)
> >>
> >>
> >I run the modprobes
Nick wrote:
On 6/28/05, Michael Jones <[EMAIL PROTECTED]> wrote:
The problem was that the command modprobe ivtv was being executed after
mythbackend was started. (hmm.. what a surprise)
I run the modprobes (2 cards) and start mythbackend from rc.local (you
could prob do it from rc.sys
On 6/27/05, Michael Jones <[EMAIL PROTECTED]> wrote:
> [EMAIL PROTECTED] ~]$ su -
> Password:
> [EMAIL PROTECTED] ~]# ps ax | grep mythba
> 24775 ?Ssl0:00 /usr/bin/mythbackend --daemon --logfile
> /var/log/mythtv/mythbackend.log --pidfile /var/run/mythbackend.pid
>
> Anything helpful?
On 6/28/05, Michael Jones <[EMAIL PROTECTED]> wrote:
> HAHAHHAHAHA
>
> Found it..
>
> The problem was that the command modprobe ivtv was being executed after
> mythbackend was started. (hmm.. what a surprise)
>
> Someone instructed me on how to adjust the /etc/init.d/mythbackend fil
Wot are you smoking? The minus gives you root env variables.
obviously su is not doing the right thing, so bump up the priviliages
a little more by using su -
> you do _not_ need to add the minus to do what is suggested here.
>
> > you forgot the minus after su so it should be su -
> >
> > > su
>
it.d
stuff runs.
> From: Nick Rout <[EMAIL PROTECTED]>
> Reply-To: Discussion about mythtv
> Date: Mon, 27 Jun 2005 11:04:58 +1200
> To:
> Subject: Re: [mythtv-users] TV won't play unless you run mythbackend manually
> from a console
>
> you do _not_
rebooting..
everything works.
> From: Kevin Saenz <[EMAIL PROTECTED]>
> Reply-To: Kevin Saenz <[EMAIL PROTECTED]>, Discussion about mythtv
>
> Date: Mon, 27 Jun 2005 08:38:14 +1000
> To: Discussion about mythtv
> Subject: Re: [mythtv-users] TV won't play unless yo
you do _not_ need to add the minus to do what is suggested here.
On Mon, 27 Jun 2005 08:38:14 +1000
Kevin Saenz wrote:
> you forgot the minus after su so it should be su -
>
> > su
> >
> > /etc/init.d/mythbackend stop
> > /etc/init.d/mythbackend start
> >
> >
> then run ps ax|grep mythbac
you forgot the minus after su so it should be su -
> su
>
> /etc/init.d/mythbackend stop
> /etc/init.d/mythbackend start
>
>
then run ps ax|grep mythbac
___
mythtv-users mailing list
mythtv-users@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/m
Thanks..
but Nope..
- Michael
> From: Robert Kulagowski <[EMAIL PROTECTED]>
> Reply-To: Discussion about mythtv
> Date: Fri, 24 Jun 2005 12:24:35 -0500
> To: Discussion about mythtv
> Subject: Re: [mythtv-users] TV won't play unless you run mythbackend manuall
As root:
$ su
# rm /var/lock/subsys/mythbackend
Does that help?
___
mythtv-users mailing list
mythtv-users@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Open Terminal
su
/etc/init.d/mythbackend stop
/etc/init.d/mythbackend start
which mythbackend
returns:
/usr/bin/mythbackend (same as in the script)
I've hunted through the logs and no errors are being generated.
> open a terminal type
> su -
>
> su terminals suck ;-p
>
> then try it aga
open a terminal type
su -
su terminals suck ;-p
then try it again.
> Ok.. We may be getting somewhere?
>
> Rebooted so everything was fresh..
>
> At a su terminal window (gave me permission errors if I did it as a non su
> user):
>
> /etc/init.d/mythbackend stop
> /etc/init.d/mythbackend sta
open a terminal type
su -
su terminals suck ;-p
then try it again.
> Ok.. We may be getting somewhere?
>
> Rebooted so everything was fresh..
>
> At a su terminal window (gave me permission errors if I did it as a non su
> user):
>
> /etc/init.d/mythbackend stop
> /etc/init.d/mythbackend sta
2005 14:38:46 +1000
> To: Discussion about mythtv
> Subject: Re: [mythtv-users] TV won't play unless you run mythbackend manually
> from a console
>
>> mythbackend 0:off 1:off 2:on3:on4:on5:on6:off
>>
> Ok what happens when you run
&g
> mythbackend 0:off 1:off 2:on3:on4:on5:on6:off
>
Ok what happens when you run
/etc/init.d/mythbackend stop
then
/etc/init.d/mythbackend start
?
if you type
where mythbackend
is that the same location as what is entered into /etc/init.d/mythbackend
?
__
I'm almost thinking that I should nuke my installation and start over
again..
> Stupid question why are you running mythtv in root? why are you
> symlinking a directory to / ? that is like creating a directory in
> windows and shortcutting it to c:\ You are not running windows here.
> :) set you
Stupid question why are you running mythtv in root? why are you
symlinking a directory to / ? that is like creating a directory in
windows and shortcutting it to c:\ You are not running windows here.
:) set your system to autologon as a gumby user, and autolaunch
mythfrontend.
do you have mythback
: Wed, 22 Jun 2005 20:42:05 -0500 (CDT)
> To: Discussion about mythtv
> Subject: Re: [mythtv-users] TV won't play unless you run mythbackend manually
> from a console
>
>
>> If I open a console window as root and run it manually:
>>
>>
>> #mythbacken
> From: "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>
> Reply-To: <[EMAIL PROTECTED]>, Discussion about mythtv
>
> Date: Wed, 22 Jun 2005 19:27:59 -0700
> To: Discussion about mythtv
> Subject: Re: [mythtv-users] TV won't play unless you run mythbackend
I've had something similar happen. When you run it as a service, is
your mythbackend service still running? When I run 'service
mythbackend status', I usually get a 'pid file exists, but mythbackend
is dead' message. When that happens, I find out it's because
mythbackend is looking for its setti
> If I open a console window as root and run it manually:
>
>
> #mythbackend &
>
>
> everything works. If I run it as a service and start live tv, the live
> tv screen shows up runs for about 1-2 sec and then freezes, the system
> then waits about 60sec and then returns to the main menu by itsel
I'm pretty new to this whole thing so be gentle with me ;)
Just finished putting together a MythTV/Fedora3 box with Jarod Wilson's
instructions.
Everything works well except if I run mythbackend as a service watching live
tv doesn't work.
If I open a console window as root and run it manually
27 matches
Mail list logo
