added these 2 bolded lines to /etc/mythtv/modules/ivtv

alias char-major-81 videodev
alias char-major-61 lirc_i2c
options ivtv debug=1
options ivtv card=85 type=39
options ivtv tuner=39
options tuner type=2
options msp3400 once=1 simple=1
add below ivtv msp3400 saa7115 tuner
add above ivtv lirc_dev lirc_i2c

Rebooted
start mythfrontend from xterm and get following errors

sh-2.05b$ mythfrontend
2004-11-22 20:23:18 mythfrontend version: 0.16.20040906-1 www.mythtv.org
2004-11-22 20:23:18 Enabled verbose msgs : important general
2004-11-22 20:23:19 Registering Internal as a media playback plugin.
2004-11-22 20:23:19 Registering MythDVD DVD Media Handler as a media handler
2004-11-22 20:23:19 Registering MythDVD VCD Media Handler as a media handler
Failed to run 'cdrecord --scanbus'
2004-11-22 20:23:19 Registering MythMusic Media Handler as a media handler
2004-11-22 20:23:19 Mediamonitor: Adding /dev/cdrom
2004-11-22 20:23:19 Mediamonitor: Adding /dev/dvd
2004-11-22 20:23:19 Starting media monitor.
2004-11-22 20:23:23 Connecting to backend server: 127.0.0.1:6543 (try 1 of 5)
2004-11-22 20:23:31 ReadStringList timeout (quick).
2004-11-22 20:23:31 Unexpected response to MYTH_PROTO_VERSION:
2004-11-22 20:23:31 Changing from None to None
2004-11-22 20:23:35 Connecting to backend server: 127.0.0.1:6543 (try 1 of 5)
2004-11-22 20:23:43 ReadStringList timeout (quick).
2004-11-22 20:23:43 Unexpected response to MYTH_PROTO_VERSION:

I thought so too. Why does his mythbackend log say his one and only backend is starting as a slave? Is this a symptom of his problem, or a red herring? What would cause this system to mistakenly think it was a slave backend?

_________________
Do you code to live, or live to code?
Search LinHES forum through Google

Interesting... missed that the first time around. Without checking my own log... Could be because he has different IPs defined in mythtv-setup.

_________________
cesman

When the source is open, the possibilities are endless!

is there a problem with leaving 127.0.0.1 in the mythsetup or should I set it to my real IP?

If you only have 1 backend leave both as 127.0.0.1.

_________________
cesman

When the source is open, the possibilities are endless!

For comparison, when I start my backend my log says:

I left my IP address set to 127.0.0.1 (i.e. localhost) and my box is a combined FE/BE system on one computer.

_________________
Do you code to live, or live to code?
Search LinHES forum through Google

Ok, I think that I have resolved all of the issues that I have been experiencing. I started off by doing tons of reading in the forums. Found lots of info that was not exactly like my problem but with a combo of many I found some things to try.

First fix.....re-ran mythtv-setup, said yes and yes to clear all settings. At the first screen where you fill out your IP and port info I saw that I had filled out the top ip with my real ip and the bottom with the loopback 127.0.0.1. This time I left them both at 127.0.0.1 Once I finished the setup I started the front end and was able to use mythweb as well as schedule recordings.

Live tv was still not working but I decide to try to schedule a program. I did a tail -f /var/log/mythtv/mythbackend.log as the recording was supposed to start and it just said that the tuner was not responding and had an I/O error.

After some more research in the forums I finally tweaked my /etc/mythtv/modules/ivtv file to be as follows:

root@kmythtv:~ # cat /etc/mythtv/modules/ivtv
alias char-major-81 videodev
alias char-major-61 lirc_i2c
options ivtv debug=1
options ivtv card=85 type=39
options ivtv tuner=39
options tuner type=39
options msp3400 once=1 simple=1
add below ivtv msp3400 saa7115 tuner
add above ivtv lirc_dev lirc_i2c


Tried livetv again and IT WORKED!!!!

Thanks for all the tips and help guys.

Next project, add my other pvr250 to the box....it is a different revision number so I will have to add mulitple tuner types.