I'm having the same problem. First time installing KM (downloaded R5D1).
I've never used MythTV and can't wait to see it.

Waiting patiently.
-- omnivore

omnivore,

Download R5C7 for now and use that. Once this is sorted out you can upgrade which is fairly painless.

R5C7 isn't working for me. I can't get the 350 to find any channels when I setup the card. Also when I start myth it complains the backend server isn't running.
R5D1 had not of these problems but just won't work after rebooting...

After reading this thread I tried R5C7. Unfortunately, on reboot R5C7 locked up while loading some ivtv driver.

I seem to get further with R5D1. At least I can ssh in and poke around.

Make sure you have your TV on and hooked up to the TV out on the PVR-350. I rebooted twice until I realized it wasn't locked up.

Still isn't working but hey..

You think R5C7 didn't boot properly because my tv wasn't on?
If that is the case, perhaps I'll try loading it again.

I think what he meant is that the monitor looks like it freezes up once you have rebooted machine and really the output is on the tv screen.
I had the same issue it looked like the monitor locked up and I could SSH into the box but all the output was running on my TV

Cool! Can't wait to try that this weekend.

Has anyone made any progress with the R5D1 and first reboot problem?

afraid not. But hoping to get at go at it thus weekend. I suspect that it's only a matter of the script containing the framebuffer module of the ivtv driver, not being run after first reboot when answering "yes" to "use pvr-350 tv out" during installation.

Either it's not being executed, or it's beeing executed at the wrong time.

Well, just some thoughts. Anyone having done any elimination by trail, pls note it in this tread. Successful or not, dosen't matter, no reason we should all make the same mistakes

oh, btw. you will have to excuse my poor english. doing my best really

Good news, everyone! I've solved my problem and got tv-out on the 350 working in R5D1. Here's how:

root@mythtv:~# nano /etc/init.d/local

This file should look like:


Then

root@mythtv:~# chmod +x /etc/init.d/local
root@mythtv:~# update-rc.d local start 95 2 3 4 5 .

Finally, the crucial part was in XF86Config-4:


Restart X and all should be well.

The fbdev line turned out to be the important part that was missing. I believe someone else got it working earlier by adding that line but for some reason it didn't work for me at the time. The 'local' startup script is a bit of a cheat to get the ivtv-fb module loaded but I couldn't find another way to get it to load correctly. My system has bootsplash enabled which is why I'm using 'fb1' above. If you don't have bootsplash then you should use 'fb0'.

My system will now bootup and the frontend will come up on the 350's tv-out without any sort of manual intervention just like it did in previous releases. I suspect the above steps may be the solution for others as well. Will some other people try this and post their results?

I installed R5D1 again and made the changes your described.
Now when I reboot the computer crashes when it tries to output video to the tv.
What can I do to prevent the crash so I can ssh in?

omnivore, you could try booting with the install CD or any live CD for that matter. Once you get the system up and running, mount the KnoppMyth root partition. Try removing the 'local' script that loads ivtv-fb. Previously, I experience similar crashes because of that module. After you've removed the script, reboot into KnoppMyth and see if you can ssh in. Once you're logged in you can play with manually inserting the ivtv-fb module and see if that gets you anywhere. Good luck.

It didn't work for me.
It booted and appeared if X was going to start with the 350 output. However the screen went black and nothing appeared to start.

I can ssh into the machine but that is about it.

eqnox1, you say it appeared that X was going to start and then the screen went black. Did both the output from your video card and the 350 go black? I ask because if you're watching the system bootup, ie on your computer monitor, you will see the screen go black and stay that way. At the same time, you should see X and mythfrontend start on the 350's output. Also, if you're using the S-video output of the 350, try switching to the composite output which is the default I think.