Hi folks, I have seen several reports about problems with PVR-350 TV output with the latest ivtv release. Are there any theories about why it is happening or what it might take to fix? My current status is below. Is there any benefit to performing a "yum upgrade" to the latest kernel? It seems the problem exists there too. If anyone sees something I can fix, please let me know. I appreciate your time. Also, apologies if you read this on the MythTV list.
Regards, Fred On 3/6/07, Fred Firestine <[EMAIL PROTECTED]> wrote: > Hi everyone, > > OK, I reinstalled FC 6 and now I am back to the the following config > (see below). I have no error messages I can see, I even have the > correct message > > ivtv0-fb: Running in compatibility mode. Display resize & mode change disabled > > In my dmesg output (not the section below). No more "no longer > supported" messages. If anyone can tell me based on the info below an > ivtv version that will let me get past this black screen problem, I > would appreciate it. Please include the steps to correctly remove the > current ivtv version. Until this issue gets resolved (since it is > happening to several people with PVR-350s) it would be good to know. > > Thanks! > > Fred > > Kernel 2.6.19-1.2911.fc6 > > ivtv-0.10.1-126.fc6.at > ivtv_xdriver-0.10.7-8_r3843.fc6.at > ivtv-firmware-20070217-13.at > ivtv-kmdl-2.6.19-1.2911.fc6-0.10.1-126.fc6.at > video4linux-kmdl-2.6.19-1.2911.fc6-20070302-78.fc6.at > > ivtv log messages: > > ivtv: ==================== START INIT IVTV ==================== > ivtv: version 0.10.1 (tagged release) loading > ivtv: Linux version: 2.6.19-1.2911.fc6 SMP mod_unload 686 REGPARM 4KSTACKS > ivtv: In case of problems please include the debug info between > ivtv: the START INIT IVTV and END INIT IVTV lines, along with > ivtv: any module options, when mailing the ivtv-users mailinglist. > ivtv0: Autodetected Hauppauge card (cx23415 based) > ACPI: PCI Interrupt 0000:02:07.0[A] -> Link [LNKA] -> GSI 7 (level, low) -> > IRQ > 7 > Floppy drive(s): fd0 is 1.44M > FDC 0 is a National Semiconductor PC87306 > ieee1394: Host added: ID:BUS[0-00:1023] GUID[00023c0020018f12] > ivtv0: loaded v4l-cx2341x-enc.fw firmware (376836 bytes) > ivtv0: loaded v4l-cx2341x-dec.fw firmware (262144 bytes) > ivtv0: Encoder revision: 0x02060039 > ivtv0: Decoder revision: 0x02020023 > saa7127 1-0044: saa7129 found @ 0x88 (ivtv i2c driver #0) > tveeprom 1-0050: Hauppauge model 48132, rev K268, serial# 8500007 > tveeprom 1-0050: tuner model is LG TAPE H001F MK3 (idx 68, type 47) > tveeprom 1-0050: TV standards NTSC(M) (eeprom 0x08) > tveeprom 1-0050: audio processor is MSP4448 (idx 27) > tveeprom 1-0050: decoder processor is SAA7115 (idx 19) > tveeprom 1-0050: has radio, has IR receiver, has no IR transmitter > ivtv0: Autodetected Hauppauge WinTV PVR-350 > tuner 1-0043: chip found @ 0x86 (ivtv i2c driver #0) > tda9887 1-0043: tda988[5/6/7] found @ 0x43 (tuner) > tuner 1-0061: chip found @ 0xc2 (ivtv i2c driver #0) > saa7115 1-0021: saa7115 found (1f7115d0e100000) @ 0x42 (ivtv i2c driver #0) > msp3400 1-0040: MSP4448G-A2 found @ 0x80 (ivtv i2c driver #0)hooting > msp3400 1-0040: MSP4448G-A2 supports radio, mode is autodetect and autoselect > ivtv0: Registered device video0 for encoder MPEG (4 MB) > ivtv0: Registered device video32 for encoder YUV (2 MB)686 REGPARM 4KSTACKS > ivtv0: Registered device vbi0 for encoder VBI (1 MB) > ivtv0: Registered device video24 for encoder PCM audio (1 MB) > ivtv0: Registered device radio0 for encoder radioug info between > ivtv0: Registered device video16 for decoder MPEG (1 MB)g with > ivtv0: Registered device vbi8 for decoder VBI (1 MB)rs mailinglist. > ivtv0: Registered device vbi16 for decoder VOUTed) > ivtv0: Registered device video48 for decoder YUV (1 MB) > ivtv0: loaded v4l-cx2341x-init.mpg firmware (155648 bytes) > tuner 1-0061: type set to 47 (LG NTSC (TAPE series))0020018f12] > ivtv0: Initialized Hauppauge WinTV PVR-350, card #0ytes) > ACPI: PCI Interrupt 0000:02:0a.0[A] -> Link [LNKD] -> GSI 11 (level, low) -> > IRQ > 11 > ivtv: ====================== NEXT CARD ====================== > ivtv1: Autodetected Hauppauge card (cx23416 based) > ACPI: PCI Interrupt 0000:02:0b.0[A] -> Link [LNKA] -> GSI 7 (level, low) -> > IRQ > 7 > tveeprom 1-0050: Hauppauge model 48132, rev K268, serial# 8500007 > ivtv1: loaded v4l-cx2341x-enc.fw firmware (376836 bytes) > ivtv1: Encoder revision: 0x02060039r encoder YUV (2 MB) > cx25840 2-0044: cx25841-23 found @ 0x88 (ivtv i2c driver #1) > cx25840 2-0044: loaded v4l-cx25840.fw firmware (16382 bytes)) > wm8775 2-001b: chip found @ 0x36 (ivtv i2c driver #1) > tuner 2-0061: chip found @ 0xc2 (ivtv i2c driver #1) > tveeprom 2-0050: Hauppauge model 26132, rev G1B2, serial# 9519117 > tveeprom 2-0050: tuner model is TCL M2523_5N_E (idx 112, type 50) > tveeprom 2-0050: TV standards NTSC(M) (eeprom 0x08) > tveeprom 2-0050: audio processor is CX25841 (idx 35) > tveeprom 2-0050: decoder processor is CX25841 (idx 28) > tveeprom 2-0050: has no radio, has IR receiver, has IR transmitter > ivtv1: Autodetected Hauppauge WinTV PVR-150 > ivtv1: reopen i2c bus for IR-blaster support > cx25840 2-0044: cx25841-23 found @ 0x88 (ivtv i2c driver #1) > cx25840 2-0044: loaded v4l-cx25840.fw firmware (16382 bytes) > wm8775 2-001b: chip found @ 0x36 (ivtv i2c driver #1) > tuner 2-0061: chip found @ 0xc2 (ivtv i2c driver #1) > ivtv1: Registered device video1 for encoder MPEG (4 MB) > ivtv1: Registered device video33 for encoder YUV (2 MB) > ivtv1: Registered device vbi1 for encoder VBI (1 MB) > ivtv1: Registered device video25 for encoder PCM audio (1 MB) > tuner 2-0061: type set to 50 (TCL 2002N) > ivtv1: Initialized Hauppauge WinTV PVR-150, card #1 > ivtv: ==================== END INIT IVTV ==================== > > On 3/3/07, Fred Firestine <[EMAIL PROTECTED]> wrote: > > So, do you or anyone else have any idea why this isn't option isn't > > being used? Here is the section from modprobe.conf: > > > > alias char-major-81 videodev > > alias char-major-81-0 ivtv > > alias char-major-81-1 ivtv > > options ivtv-fb osd_compat=1 > > install ivtv /sbin/modprobe saa7127; /sbin/modprobe cx25840; > > /sbin/modprobe wm8775; /sbin/modprobe --ignore-install ivtv; > > /sbin/modprobe ivtv-fb > > > > Is there something wrong with my syntax? Any other way to send this > > option to ivtv-fb? I really don't want to go back to Fedora Core 4; > > but I am not encouraged by all the posts I have seen about this in my > > research this week. > > > > On 3/3/07, Ian Armstrong <[EMAIL PROTECTED]> wrote: > > > On Saturday 03 March 2007 20:48, Fred Firestine wrote: > > > > Hi everyone, > > > > > > > > Apologies if you have seen this on the ivtv list... After being a big > > > > fan of MythTV for months on Fedora Core 4, I decided it was time to > > > > upgrade to Fedora Core 6 (actually a fresh install). Most of my > > > > settings, database info, etc. have been migrated properly, and > > > > everything is working, except for watching recorded programs. When I > > > > press play, sometimes I see a flash of the program followed by a black > > > > screen, most of the time just a black screen. Audio is fine. I have > > > > been searching around for several days now, and this seems to be a > > > > common problem. The IVTV Howto recommends the following in > > > > /etc/modprobe.conf: > > > > > > > > options ivtv-fb osd_compat=1 > > > > > > > > This does not work for me. Does anyone have any other suggestions? > > > > > > > > > > /var/log/messages output during playback: > > > > > > > > Mar 3 13:15:19 mythtv kernel: ivtv0: Stereo mode changed > > > > Mar 3 13:15:19 mythtv kernel: ivtv0-fb warning: ivtv_fb_prep_frame: > > > > Nothing to do. count = 0 > > > > Mar 3 13:15:40 mythtv last message repeated 610 times > > > > Mar 3 13:15:40 mythtv kernel: ivtv0-fb warning: > > > > IVTVFB_IOCTL_GET_ACTIVE_BUFFER no longer supported > > > > Mar 3 13:15:40 mythtv kernel: ivtv0-fb warning: - Please use > > > > FBIOGET_VSCREENINFO > > > > Mar 3 13:15:41 mythtv kernel: ivtv0-fb warning: ivtv_fb_prep_frame: > > > > Nothing to do. count = 0 > > > > > > The 'no longer supported' messages suggest the osd_compat option isn't > > > being > > > used. When the ivtv-fb module is loaded with osd_compat=1, you should see > > > something like this in the output from dmesg. > > > > > > ivtv0-fb: Running in compatibility mode. Display resize & mode change > > > disabled > > > > > > -- > > > Ian > > > _______________________________________________ > > > mythtv-users mailing list > > > [email protected] > > > http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users > > > > > > _______________________________________________ ivtv-users mailing list [email protected] http://ivtvdriver.org/mailman/listinfo/ivtv-users
