Wow. Now, that's a fast reply! :) Okay, the *new* new initrd-ivtv script contains:
--------------------------------------- if [ -n "$USE_IVTVDEV" ]; then findmodule tda9887 findmodule cx2584 findmodule tveeprom findmodule msp3400 findmodule saa7115 findmodule tuner findmodule saa7127 findmodule ivtv findmodule ivtv-fb fi --------------------------------------- ...and: --------------------------------------- if [ -n "$USE_IVTVDEV" ]; then mkdir -p $MNTIMAGE/lib/modules cp /lib/modules/ivtv-fw*.bin $MNTIMAGE/lib/modules/ cp /lib/modules/ivtv_init_mpeg.bin $MNTIMAGE/lib/modules/ fi --------------------------------------- If this is good, I'll go ahead and run it at 11:30-ish (Myth is recording on the 350 right now...) and see if the problems magically disappear! Thanks again, Adam, for your (extremely speedy) reply! - brian -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Adam Forsyth Sent: Thursday, October 13, 2005 8:41 PM To: Discussion list for development of the IVTV driver Subject: Re: [ivtv-devel] New PVR-500MCE not working (either tuner) with ivtv0.4.0 > First, there are a few things that disturb me in the dmesg output (below). > For the 350, complaints arise about an inability to load > /lib/modules/ivtv_init_mpeg.bin -- the file is there, and has the same > permissions as ivtv-fw-enc.bin and ivtv-fw-dec.bin, both of which reside in > /lib/modules as well. I suspect this failure is what causes the ensuing > 'YUV' errors later on. This is caused by the initrd problem, same as your previous problems. Look in the mkinitrd-ivtv program you're using, and add that file to where it's copying in the ivtv*.bin firmware files. > > Second, while initializing both tuners in the PVR-500MCE, there's a string > of warnings "warning i2c address 0x44" (etc) produced, and these also repeat > later on in dmesg, outside of the [begin]/[end] ivtv startup. Also caused by your initrd. For the 150/550 you need to also include tda9887.ko and cx2584.ko as well as all the others. Jarod's guide really is geared towards the 250 / 350 only and needs to be updated for the 150 / 500. > > There are recurring errors that show up in dmesg during operation, as well > (also noted below). > > Now, reading through some of the other discussion here, I'm noticing that > I, also, have a cx88xx module being loaded (as well as a cx8800 module), and > I'm wondering if I need them (and if they're causing (some of) the problems > -- it looks (to me) like they are being loaded by v4l2 (which also loads a > few other things)... do I even need these? They apparently aren't causing > any major issues with the PVR-350, as it will record and play... They are pulled in by lirc on some kernel versions. If you upgrade to FC4 and the newest kernel there (2.6.13) it should stop this, but you don't really need to do that. > > I am not getting any video out of either tuner when I attempt to cat > /dev/video1 or /dev/video2 (the 350 is /dev/video0) > > I'm including the ivtv dmesg output here, as well as a few snippets > outside the ivtv load to illustrate what I describe above. I'm also > including my lsmod output, in case that helps in diagnosing what is > happening here... > > (and, although it's off-topic here) when I set up these two new tuners > (/dev/video1 and /dev/video2) in mythtv-setup, the 500 shows up as two > discrete PVR-150's. Do I choose "tuner 0" for both? "tuner 0" for the > first and "tuner 1" for the second? Or what? Yes, they are essentially two pvr-150s and you should treat them as such in mythtv. > > Color me confused... (and, of course, thanks in advance for any > help/guidance you can provide) Fixing your initrd should clear up all of your problems. _______________________________________________ ivtv-devel mailing list [email protected] http://ivtvdriver.org/mailman/listinfo/ivtv-devel _______________________________________________ ivtv-devel mailing list [email protected] http://ivtvdriver.org/mailman/listinfo/ivtv-devel
