Please see the directions on the wiki. http://www.knoppmythwiki.org/index.php?page=CompileIvtv I tested these with 0.7.1 last night. All you need to do is read the 0.7.1 related note at the top, and make the obvious substitutions of 0.4.6 -> 0.7.1 everywhere and the newer kernel name where the directions tell you to.

I'm rebooting again just to make sure it is really working. :)

I followed the steps above and did steps 1-3 on http://www.knoppmythwiki.org/index.php?page=CompileIvtv

Everything appears to be functioning. Channels in the 50-60 range are fuzzy but that is a different problem.

Thanks to everyone who helped fixed the problem..

Ok so followed the directions and can now see myth on my tv but when i hit watch tv or any thing else i get a cant connect to backend error. this happen to any one else? any have any idea how i can correct this? i notice that i can type mythtv-backend stop / start as many times as i want and it never gives me the myth is already running or myth is not runnin error!

AFter numerous attempts to fix the reboot issue I decided to just let my system run and pray that it never had to reboot but that only lasted about 3 days before I messed the power up and after following the directions I too am receiving the can't connect to backend error.

(What I did)
-Made a backup of /etc directory to /myth/etc_backup
root@mythtv:mkdir /myth/etc_backup
root@mythtv:cp -RP /etc /myth/etc_backup

-rebooted and selected autoupgrade from R5D1 disk

-setup system

-config pvr350

-config no boot splash

- ...
I had a problem getting to a command prompt after the auto upgrade configuration. So I had to select "knoppmyth:reboot" in order to get X to fail and I could then have a command prompt on the monitor that was attached and be able to continue with the "-Make Zaroffs stuff" step. Is that ok?

-Make Zaroffs stuff
(created the file /etc/init.d/local)
root@mythtv:~# vi /etc/init.d/local
(inserted the following into /etc/init.d/local)
#! /bin/sh
modprobe ivtv-fb
(modified permissions of /etc/init.d/local)
root@mythtv:chmod +x /etc/init.d/local

-Updated rc.d
root@mythtv:~# update-rc.d local start 95 2 3 4 5 .

-Edited /etc/X11/XF86Config-4 file so the seciont dealing with the
Hauppauge 350 looked like the following:
Section "Device"
Identifier "Hauppauge PVR 350 iTVC15 Framebuffer"
Driver "ivtvdev"

### change fb0 to whatever number you got in the previous section
Option "fbdev" "/dev/fb1"
Option "ivtv" "/dev/fb1"
Option "VideoOverlay" "on"
Option "XVideo" "1"

-Restart X and all should be well.
I did not restart X at this point as on a previous attempts I was unable to get a command promt if I quit at this point.

-Unpacked the Kernel
root@mythtv:cd /usr/src
root@mythtv:tar jxvf kernel-source-2.6.17-chw-8.tar.bz2

-Downloaded driver code
root@mythtv:wget http://dl.ivtvdriver.org/ivtv/archive/0 ... 7.1.tar.gz

-made the IVTV intsallation
root@mythtv:tar zxvf ivtv-0.7.1.tar.gz
root@mythtv:cd ivtv-0.7.1/
root@mythtv:make
root@mythtv:make install

-rebooted and now the tv is displaying Myth, remote is working, but I am receiving the can't connect to backend error when trying to watch tv or modify themes etc...

-Drop and recreate card config
I had trouble with the final step "-Drop and recreate card config" as I don't know how to do that yet? (newb, pls help!)


Thanks Zaroff, Silent and everyone else for helping me get to where it will display something after a reboot.

A very lazy hack for people that don't want to recompile the module:

I noticed that the ivtv_fb module would only take while X was running (using the monitor). So I wrote this script to start X using the old config in /etc/X11 on the monitor for 3 seconds while it loads the module. Then it switches the /etc/X11/XF86Config-4 sym link back to the config for the 350 and restarts X.

You should probably recompile the module and not do this.

to use:
Don't forget to set the correct PCI BusId in your /etc/X11/XF86Config.350 for your setup (my guess is its already set if it worked the first time)

save this script as /etc/init.d/IVTV-HACK


then as root run


Meant to be used on a R5D1 KnoppMyth install.
It worked for me before I found this thread.

edit: You may need to rename /etc/X11/XF86Config file (if it exists) to something else so that X doesnt load it instead of following the /etc/X11/XF86Config-4 link. I remember doing this at some point.

The easiest way to do this is:
1) Alt-2 to stop the backend.
2) Alt-S to run setup.
3) Go to #2, Capture Cards and choose "Delete all capture cards."
4) Re-add your card(s): "New capture card".
5) Exit out of setup and then Alt-3 to start the backend again.

Not quite complete silentaccord. When you delete and recreate the capture cards you also need to redo the input connections...

For several ways to get back into mythtv-setup see this wiki page - http://www.knoppmythwiki.org/index.php? ... MytTVsetup
For a complete list of steps for recreating you tuner card entries see item 11 on this wiki page - http://www.knoppmythwiki.org/index.php?page=CompileIvtv

Hi dvanced,

Nice hack Maybe the driver compile etc is the proper thing to do, however since it worked the first time it should have worked the second time also with what was installed. Your hack proved it so.

May be something is in the wrong startup order or something is in a list to early / too late. A fresh view is good.

Thank you
Mike

I had a a hell of a time getting my 350 tv out working with R5D1. In addition to Zaroffs's hack, I had to enable bootsplash. Otherwise modprobe ivtv-fb would crash the machine.

Then the key was adding this line to my XF1186Config-4:

Option "fbdev" "/dev/fb1"

This one didn't do anything for me:

Option "ivtv" "/dev/fb1"

I was able to solve all my pvr-350 woes using Zaroff's and Batkinson's directions.

I can confirm I followed the instructions in the directly above post and it worked for me. Two small changes:

1. I used ivtv-0.7.1.tar.gz, as mentioned above
2. I used /dev/fb0 instead of /dev/fb1 in the X config file

Has anyone noticed higher cpu usage with ivtv 0.7.1? I have an 866mhz pentium 3 and was seeing >50% cpu for mythfrontend during playback with 0.7.1. I reinstalled 0.7.0 and it's now less than 5% like it was in R5C7.

Wow. I had this problem earlier this week when I reinstalled R5D1, and I thought I'd wait a while to let the guinea pigs work through the initial troubleshooting!

...And by Guinea pigs, I mean those of you who are more knowledgable about Linux than I.

This thread unfolded like an epic saga, but it appears to be only on the first part of the trilogy...

Sorry if this post is useless babble, but I at least wanted to let you all know that your efforts are appreciated.

I am now going to try the Zaroff / Batkinson Solution, and see if that works for me.

Herr Schmeckendeugler

All Righty! I got as far as recompiling the ivtv module, and received an error. (Maybe I shoulda wrote down what it was... Oh well!) But, since it was a fresh install, I just rebooted to see what would happen! At worst, I gotta reinstall.

The result: The TV out appears to be getting... a signal, SOME type of signal, but just black. The Monitor displays some stuff going in a diagnal sloping-to-the-right fashion, as if the "Carriage Return" output were no longer functioning properly. The last thing to appear on the screen is...



...There it goes off the screen. FYI some other ivtv-0 stuff is indicated above that which may or may not be pertinent.

This wouldn't be so much of a problem if I could SSH in, or figure a way out to get to a command prompt! Perhaps the entire machine is just locked up? SHould CTRL+ALT+DEL do a reboot? Should any other Linux Keystrokes do anything that I might not know about (similar to the ALT+F2 or whatever to get another shell)?[/code]

SUCCESS!!!!

content deleted.

see later post for better description.