I'm suffering from the exact same problem with FC4. I'd also appreciate hearing about the fix, if there is one.
Boris --- Daniel Tyreus <[EMAIL PROTECTED]> wrote: > I had a MythTV setup going on FC2 and then last week > I > did a clean install of FC4, mostly for the logical > volume management. My system has a PVR-350 and a > PVR-250. When I set up Myth/IVTV on FC2 a year ago, > the hard part was getting X to run on the 350 out. > Now > X runs fine, but I can't get mpeg decoded video out! > > The problem seems to be that IVTV cannot load > /lib/modules/ivtv_init_mpeg.bin. The file is there. > Any ideas? By the way, could someone post a correct > /etc/modprobe.conf file for the 0.4 IVTV drivers and > lirc? > > Regards, > Daniel > > [EMAIL PROTECTED] ~]# rpm -qa | grep ivtv > ivtv-firmware-1.8a-4.at > perl-Video-ivtv-0.13-7.rhfc4.at > ivtv_xdriver-0.10.6-3.rhfc4.at > ivtv-firmware-dec-2.02.023-4.at > ivtv-0.4.0-98.rhfc4.at > ivtv-kmdl-2.6.13-1.1532_FC4-0.4.0-98.rhfc4.at > ivtv-kernheaders-0.4.0-98.rhfc4.at > ivtv-firmware-enc-2.04.024-4.at > > [EMAIL PROTECTED] ~]# dmesg | grep ivtv > ivtv: ==================== START INIT IVTV > ==================== > ivtv: version 0.4.0 (tagged release) loading > ivtv: Linux version: 2.6.13-1.1532_FC4 686 REGPARM > 4KSTACKS gcc-4.0 > ivtv: In case of problems please include the debug > info > ivtv: between the START INIT IVTV and END INIT IVTV > lines when > ivtv: mailing the ivtv-devel mailinglist. > ivtv0: Autodetected WinTV PVR 350 card (iTVC15 > based) > ivtv0: Unreasonably low latency timer, setting to 64 > (was 32) > tveeprom: ivtv version > ivtv0: i2c attach to card #0 ok [client=tveeprom, > addr=50] > msp34xx: ivtv version > ivtv0: i2c attach to card #0 ok [client=MSP3448W-A2, > addr=40] > saa7115 0-0021: saa7115 found @ 0x42 (ivtv i2c > driver > #0) > ivtv0: i2c attach to card #0 ok [client=saa7115, > addr=21] > : chip found @ 0xc2 (ivtv i2c driver #0) > ivtv0: i2c attach to card #0 ok [client=(tuner > unset), > addr=61] > saa7127 0-0044: saa7127 found @ 0x88 (ivtv i2c > driver > #0) > ivtv0: i2c attach to card #0 ok [client=saa7127, > addr=44] > ivtv0: loading /lib/modules/ivtv-fw-enc.bin > ivtv0: loading /lib/modules/ivtv-fw-dec.bin > ivtv0: Encoder revision: 0x02040024 > ivtv0 warning: Encoder Firmware can be buggy, use > version 0x02040011 or 0x02050032. > ivtv0: Decoder revision: 0x02020023 > ivtv0: Allocate DMA encoder MPEG stream: 128 x 32768 > buffers (4096KB total) > ivtv0: Allocate DMA encoder YUV stream: 194 x 10800 > buffers (2048KB total) > ivtv0: Allocate DMA encoder VBI stream: 120 x 17472 > buffers (2048KB total) > ivtv0: Allocate DMA encoder PCM audio stream: 455 x > 4608 buffers (2048KB total) > ivtv0: Create encoder radio stream > ivtv0: Allocate DMA decoder MPEG stream: 16 x 65536 > buffers (1024KB total) > ivtv0: Allocate DMA decoder VBI stream: 512 x 2048 > buffers (1024KB total) > ivtv0: Create decoder VOUT stream > ivtv0: Allocate DMA decoder YUV stream: 24 x 43200 > buffers (1024KB total) > ivtv0: loading /lib/modules/ivtv_init_mpeg.bin > ivtv0: unable to open firmware > ivtv0: failed to read mpeg decoder initialisation > file > /lib/modules/ivtv_init_mpeg.bin > ivtv0: Initialized WinTV PVR 350, card #0 > ivtv: ====================== NEXT CARD > ====================== > ivtv1: Autodetected WinTV PVR 250 card (iTVC16 > based) > ivtv1: Unreasonably low latency timer, setting to 64 > (was 32) > tveeprom: ivtv version > ivtv1: i2c attach to card #1 ok [client=tveeprom, > addr=50] > msp34xx: ivtv version > ivtv1: i2c attach to card #1 ok [client=MSP3448W-B3, > addr=40] > saa7115 1-0021: saa7115 found @ 0x42 (ivtv i2c > driver > #1) > ivtv1: i2c attach to card #1 ok [client=saa7115, > addr=21] > : chip found @ 0xc2 (ivtv i2c driver #1) > ivtv1: i2c attach to card #1 ok [client=(tuner > unset), > addr=61] > ivtv1: loading /lib/modules/ivtv-fw-enc.bin > ivtv1: Encoder revision: 0x02040024 > ivtv1 warning: Encoder Firmware can be buggy, use > version 0x02040011 or 0x02050032. > ivtv1: Allocate DMA encoder MPEG stream: 128 x 32768 > buffers (4096KB total) > ivtv1: Allocate DMA encoder YUV stream: 194 x 10800 > buffers (2048KB total) > ivtv1: Allocate DMA encoder VBI stream: 120 x 17472 > buffers (2048KB total) > ivtv1: Allocate DMA encoder PCM audio stream: 455 x > 4608 buffers (2048KB total) > ivtv1: Create encoder radio stream > ivtv1: Initialized WinTV PVR 250, card #1 > ivtv: ==================== END INIT IVTV > ==================== > ivtv0-osd: Framebuffer module loaded (attached to > ivtv > card id 0) > ivtv0-osd warning: Framebuffer is at > decoder-relative > address 0x00510000 and has 1704960 bytes. > ivtv0-osd: screen coords: [0 0] -> [720 480] > ivtv0-osd: original global alpha = 208 > ivtv0-osd: current OSD state = 39 > ivtv0-osd: new global alpha = 208 (1 255 0) > ivtv0-osd: framebuffer at 0xd9510000, mapped to > 0xe9790000, size 1350k > ivtv0-osd: mode is 720x480x32, linelength=2880 > ivtv0-osd: fb0: iTVC15 TV out frame buffer device > ivtv0: Allocate DMA decoder OSD stream: 16 x 65536 > buffers (1024KB total) > ivtv0: Tried to open YUV output device but need to > send data to mpeg decoder before it can be used > ivtv0: Tried to open YUV output device but need to > send data to mpeg decoder before it can be used > > > > > __________________________________ > Yahoo! FareChase: Search multiple travel sites in > one click. > http://farechase.yahoo.com > > _______________________________________________ > ivtv-users mailing list > [email protected] > http://ivtvdriver.org/mailman/listinfo/ivtv-users > __________________________________ Start your day with Yahoo! - Make it your home page! http://www.yahoo.com/r/hs _______________________________________________ ivtv-users mailing list [email protected] http://ivtvdriver.org/mailman/listinfo/ivtv-users
