I have the same issue with card ordering as bruce_s01. After a reboot, sometimes my backend can't be found even though it is running. I have 2 hd5500's and 2 pvr250s. Stopping the back end and re-doing mythtv-setup shows that the systems thinks that my /dev/video2 is a HD5500 when it is really a PVR250.

This wouldn't normally be a problem except that I have to reboot fairly regularly due to ivtv dma errors.

can someone post their working (modified) /etc/init.d/mythtv-backend file? I think I fubared somthing when I was doing the edit, I really don't want to have to reload just to get the original file back.

Thanks

The whole file is available over in the R5E50 Upgrade Hints thread.

I had this problem too and it was that after a dirty shutdown and reboot, it thought that the backend was running, so "mythtv-backend start" didn't work.

My solution was to edit \etc\init.d\mythtv-backend and change
start)
to
startold)

and
restart|force-reload)
to
start|restart|force-reload)

You will get a little warning from it on startup because you will now be doing the restart code on startup.

Cliffsjunk - FINALLY - A true fix!!! Thanks man! I just verified this, my backend finally starts up after a reboot!!!

Hi,

I have a FE/BE box and a couple of days ago I tried booting my laptop as a frontend to see if it would connect. Well, after fiddling with all kinds of IP addressing issues it still wouldn't connect, but now when I reboot the backend doesn't start. I have to open a terminal window and type "mythbackend" and then everything works fine.

It seems my problem should be fixed by undoing some setting I changed, except I don't know what that might be. Having to manually start mythbackend has to be because of what I did to try to get a separate frontend working, that was the only thing I did to my box.

TIA for any ideas or help, before I start changing scripts that were working fine before.

Steve

- Hopefully when you open that terminal window you're not running the backend as root...

- Try killing the one you started manually and running:

This should (temporarily at least) clean up the stale PID file issue.

- If you _did_ run the backend as root you may need to clean up any ownership issues that caused...