On 9/18/07, Mike Fenston <[EMAIL PROTECTED]> wrote: > Unfortunately your answer is not true ... the ATrpms do not contain > all the necessary ivtv modules for PVR-350 tv out. ivtv-fb.ko is > missing ...
Yes it does. Which architecture are you on? For example on i386 ivtv-fb.ko is in the ivtv-kmdl-2.6.22.1-32.fc6-1.0.2-134.fc6.i686.rpm. > v4l-cx2341x-init.mpg is missing ... I have pulled the > latest updates for FC6. This is in ivtv-firmware-20070217-13.noarch.rpm which I would expect would be pulled in by ivtv-kmdl. > when I built ivtv-fb.ko manually I am now running into this problem: > > (EE) ivtvHWProvbe failed to do IVTVFB_IOCTL_GET_STATE for device /dev/fb0 Are you sure it is /dev/fb0 and not /dev/fb1 (cat /proc/fb). Is the module loaded at all? > I have the ivtv_xdriver from ATrpms ... is that good enough now or do > I need to manually compile something here too? From reading other > posts even if I get X up and running I will have to remove the ATrpms > mythtv and compile it on my own from the revision control repositories > (is this still true?) Does anyone have a stable PVR-350 TV-out now on > the 2.6.22.5-49 kernel? It was rock solid with FC5 ... even when it > flaked out the picture it would self recover. The Xdriver has received much love from the developers lately and if you want to use the version currently in svn trunk you will need to rebuild mythtv with a patch. This only applies if you want to use the build in support for the tv-out in mythtv not when you only use the Xdriver. The one that is in the ATrpms repo should work fine with ivtv-fb. Can you please stop top posting, thanks. Greets Sander _______________________________________________ ivtv-users mailing list [email protected] http://ivtvdriver.org/mailman/listinfo/ivtv-users
