[ATrpms-users] MythTV is on helium - F7 + bleeding MythTV RPMS

Void Main voidmain_isageek at yahoo.com
Thu Jun 7 02:41:22 CEST 2007


Hmmm, looks like this guy had the same problem on FC6
and seems to have a solution:

http://www.gossamer-threads.com/lists/ivtv/users/35411

We'll see.

--- Void Main <voidmain_isageek at yahoo.com> wrote:

> I just upgraded my FC6 + Myth (0.21 from bleeding)
> to
> F7 + bleeding. Actually I did a fresh F7 install on
> a
> new hard drive in the same box that ran FC6. I am
> running a PVR-350 and a PVR-500 in the box. When I
> watch live TV or play back new recordings it sounds
> like the people have just sucked helium very much
> like
> what this guy describes:
> 
>
http://www.gossamer-threads.com/lists/ivtv/users/35078
> 
> I wasn't on the very latest bleeding RPMS on my FC6
> box, in fact I was running myth
> 0.21-155_trunk_r13045.fc6 and ivtv 0.10.1-126.fc6
> where now I am running 0.21-159_trunk_r13460.fc7 and
> ivtv 0.10.3-129.fc7. At first I thought the problem
> may have been in playback but it seems to play back
> the older transcoded videos without this problem so
> I
> think it must be in the capture. I suppose if it
> drops
> frames in the capture and plays back at a normal
> frame
> rate it would actually appear to be in fast motion
> (don't know if this is possible).
> 
> I don't see any indication of a problem in the myth
> log. Looks pretty much the same as my log from the
> FC6
> setup. I thought maybe the firmware was different
> but
> I look back and see the firmware is identical,
> *however* in my /var/log/messages from the FC6
> install
> it reports a different size for the "enc" firmware
> that what it does on my F7 log:
> 
> FC6:
> ivtv0: loaded v4l-cx2341x-enc.fw firmware (262144
> bytes)
> ivtv0: loaded v4l-cx2341x-dec.fw firmware (262144
> bytes)
> ivtv0: loaded v4l-cx2341x-init.mpg firmware (155648
> bytes)
> ivtv1: loaded v4l-cx2341x-enc.fw firmware (262144
> bytes)
> cx25840 3-0044: loaded v4l-cx25840.fw firmware
> (16382
> bytes)
> ivtv2: loaded v4l-cx2341x-enc.fw firmware (262144
> bytes)
> cx25840 4-0044: loaded v4l-cx25840.fw firmware
> (16382
> bytes)
> 
> F7:
> ivtv0: loaded v4l-cx2341x-enc.fw firmware (376836
> bytes)
> ivtv0: loaded v4l-cx2341x-dec.fw firmware (262144
> bytes)
> ivtv0: loaded v4l-cx2341x-init.mpg firmware (155648
> bytes)
> ivtv1: loaded v4l-cx2341x-enc.fw firmware (376836
> bytes)
> cx25840 3-0044: loaded v4l-cx25840.fw firmware
> (16382
> bytes)
> ivtv2: loaded v4l-cx2341x-enc.fw firmware (376836
> bytes)
> cx25840 4-0044: loaded v4l-cx25840.fw firmware
> (16382
> bytes)
> 
> I compared the firmware in /lib/firmware (and
> /lib/modules) for both and they are identical in
> size
> and the md5sums match. The only thing different is
> the
> date/time stamp. What I did just notice is that in
> the
> FC6 log the load size appears to be the same for
> both
> the "enc" and the "dec" and that size matches the
> "dec" firmware size. It appears to be loading the
> "dec" for both encode and decode but reporting that
> it
> loaded each individual file. How can that be
> possible?
> I just triple checked the file names, sizes and
> symbolic links in /lib/firmware and /lib/modules and
> they are correct. The symbolic links point to the
> proper files. I don't know if that is causing my
> "helium" problem. Anyone run into this or have some
> trouble-shooting pointers?
> 
> Thanks!
> Void
> 
> 
>        
>
____________________________________________________________________________________
> Looking for a deal? Find great prices on flights and
> hotels with Yahoo! FareChase.
> http://farechase.yahoo.com/
> 



      ____________________________________________________________________________________
Luggage? GPS? Comic books? 
Check out fitting gifts for grads at Yahoo! Search
http://search.yahoo.com/search?fr=oni_on_mail&p=graduation+gifts&cs=bz



More information about the atrpms-users mailing list