wsmithjr at gmail
Sep 21, 2007, 8:05 AM
Post #2 of 2
(360 views)
Permalink
|
|
Re: updated to FC6 - looking for path of least resistance to PVR-350 output
[In reply to]
|
|
Larry wrote:
> Sander Sweers wrote:
>
>> On 9/18/07, Mike Fenston <altmcf [at] gmail> 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.
>>
> OK,
>
> The ivtv driver isn't the problem, its the xdriver (ivtvdev in older
> kernels, renamed to ivtv in newer ones) has a new API structure which
> mythtv isn't built around yet.
>
> There is a patch as has been mentioned that fixes the issue, but its not
> in the ATRPMS version of myth yet. So while its true that ATRPMS has
> all the necessary ivtv stuff it doesn't have the necessary update to
> myth ready yet.
>
> (and to be honest, with Axels issues around moving and a sick child I
> haven't really thought of it as important in the grand schemes of things)
>
>
>>> 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.
>>
>>
> Perhaps you would like to lend a hand and tell him (and others) HOW to
> use the xdriver, not the PVR's IVTV out.
>
>
>> 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
>> ivtv-users [at] ivtvdriver
>> http://ivtvdriver.org/mailman/listinfo/ivtv-users
>>
>
> _______________________________________________
> ivtv-users mailing list
> ivtv-users [at] ivtvdriver
> http://ivtvdriver.org/mailman/listinfo/ivtv-users
>
>
IT took me a bit to figure it all out... but the quickest solution for
me was MythDora, since it already has most of what you need (a version
of Mythtv, Kernel, etc to get the PVR-350 out working). The rest was
trail and error, but nothing too difficult (even I got it to work...).
Check the message archives for "PVR-350 stutters and fast audio".
Schedules Direct also works with a script/update on the MythDora
website, without upgrading Myth.
-Bill
_______________________________________________
ivtv-users mailing list
ivtv-users [at] ivtvdriver
http://ivtvdriver.org/mailman/listinfo/ivtv-users
|
