John, thank you. You solved it. For the benefit of
anyone else who may find these archives, I'll post
what I did to fix this problem.

If you follow Jarod's instructions on how to make a
custom boot image, you will apply the patch from his
site. This patch neglects to copy over the
ivtv_init_mpeg.bin file. To fix this, change the lines

if [ -n "$USE_IVTVDEV" ]; then
  mkdir -p $MNTIMAGE/lib/modules
  cp /lib/modules/ivtv-fw*.bin $MNTIMAGE/lib/modules/
fi

in the mkinitrd-ivtv file to

if [ -n "$USE_IVTVDEV" ]; then
  mkdir -p $MNTIMAGE/lib/modules
  cp /lib/modules/ivtv*.bin $MNTIMAGE/lib/modules/
fi

after applying the patch (or change the patch). Then
rebuilt the boot image.

That fixes it.

Best regards,
Daniel

--- John Harvey <[EMAIL PROTECTED]> wrote:

> Are you using a boot image built with mkinitrd? If
> so then then
> ivtv_init_mpeg.bin probably isn't in it.
> Failing to load this file is why you get the YUV
> message at the end of
> dmesg.
> 
> John
> 
> > -----Original Message-----
> > From: [EMAIL PROTECTED]
> [mailto:ivtv-devel-
> > [EMAIL PROTECTED] On Behalf Of Daniel
> > Sent: 02 November 2005 18:32
> > To: Discussion list for development of the IVTV
> driver
> > Subject: RE: [ivtv-devel] failed to read mpeg
> decoder initialisation file
> > 
> > Hi John. Thank you so much for replying.
> > 
> > > The file /lib/modules/ivtv_init_mpeg.bin is used
> to
> > > initialise the decoder
> > > so that xv playback works. It does not have any
> > > effect on decoding. Anyway
> > > does that file exist?
> > 
> > Yes, it does:
> > 
> > [EMAIL PROTECTED] ~]# ls -l /lib/modules/
> > total 688
> > drwxr-xr-x  3 root root   4096 Oct 25 21:58
> > 2.6.11-1.1369_FC4
> > drwxr-xr-x  5 root root   4096 Nov  2 10:24
> > 2.6.13-1.1532_FC4
> > -rw-r--r--  1 root root 262144 Oct 31  2004
> > ivtv-fw-dec.bin
> > -rw-r--r--  1 root root 262144 Oct 31  2004
> > ivtv-fw-enc.bin
> > -rw-r--r--  1 root root 155648 Oct 20 23:13
> > ivtv_init_mpeg.bin
> > 
> > > Then onto the decoding problem. You say it does
> not
> > > work but you don't say
> > > what happens or what you see. If this is from
> Mythtv
> > > is it set to use the
> > > 350 decoder for playback or is it using Xv?
> > 
> > I feel like a bit of an idiot. I spent 3 days
> > installing and uninstalling drivers because I had
> > convinced myself that the error below was causing
> > problems. Somewhere along the way, I must have
> > disabled the 350 out options in MythTV. I
> reinstalled
> > everything and re-enabled TV out on the 350 on
> Myth
> > and now it shows video. Before it gave a purple
> > screen.
> > 
> > Now I just have to figure out why recorded
> programs
> > have sound while live TV does not. Also, lirc is
> not
> > creating the /dev/lirc device (only /dev/lircd),
> but
> > these are not questions for this list, I don't
> think.
> > 
> > However, I do get these errors on bootup at the
> very
> > end of /var/log/messages. They may be of interest
> to
> > you all:
> > 
> > ivtv0: Tried to open YUV output device but need to
> > send data to mpeg decoder before it can be used
> > 
> > 
> > *Personal Feedback*
> > I do want to report that picture quality is many
> times
> > improved over the version of ivtv I was previously
> > using (don't know which, probably about a year
> old).
> > Before I had bad ghosting on my 350 recordings
> (the
> > 250 was fine). Now with the 0.4 drivers there is
> > almost no ghosting on either and the image is much
> > sharper. Also, the xdriver is much, much more
> > responsive. Using KDE on my TV through the 350 is
> > almost as nice and responsive as through my normal
> > graphics card. Excellent work! As far as
> useability,
> > these drivers have really come a long way.
> > 
> > Thanks again for bearing with me.
> 
> 
> 
> _______________________________________________
> ivtv-devel mailing list
> [email protected]
> http://ivtvdriver.org/mailman/listinfo/ivtv-devel
> 



        
                
__________________________________ 
Yahoo! Mail - PC Magazine Editors' Choice 2005 
http://mail.yahoo.com

_______________________________________________
ivtv-devel mailing list
[email protected]
http://ivtvdriver.org/mailman/listinfo/ivtv-devel

Reply via email to