Hello everyone, I recently upgraded to the 0.3.7 series from previously using 0.2.x series.... previously it was extremely stable, but no YUV support, hence nothing but mpeg output on my 350. Now with the latest 0.3.7 series of the driver, everything I attempt to play simply works! It's so wonderful! ...other than the random system freezing I've been experiencing. They are complete system lockups that require a power off and power on (I also wait 30 sec between in case 350 needs time to clear itself).
I have a few theories, but unfortunately there's so many variables I'm not sure which way I should be pursing harder. 1) heat: I'm using an Antec Aria case, which is a small case and can get quite warm. The only card I have in the sytem is the 350, everything is onboard. Is it possible the new drivers are working the card harder and is generating more heat and causing random freezes? Note: 0.2.x series drivers never cause a complete system freeze for me ever. 2) ivtv configuration: The relevant part of /etc/modules.conf looks like this: -[snip]- alias char-major-81 videodev alias char-major-81-0 ivtv alias char-major-61 lirc_i2c install ivtv /sbin/modprobe --ignore-install ivtv ; /sbin/modprobe ivtv-fb install ivtv /sbin/modprobe bttv; /sbin/modprobe --ignore-install ivtv -[snip]- I took these lines from somewhere in the mailing archives... curiously, does that last line with bttv need to be there? I also notice a few lines that say "Ignoring new-style parameters in presence of obsolete ones", not sure if this is working as intended as I don't think I've specified any options unless I did it somewhere else and it's finding it somehow. Also, is this the proper way to install the drivers? And is that last line bttv required? 3) mythtv configuration: I'm using the latest bleeding edge version of mythtv grabbed with svn. The freezing seems to occur when I'm moving around the menu's in myth, rarely when I'm just watching tv and not pressing anything - but it has happened as well. I've disabled the closed caption options as I read the VBI stuff is still work in progress and as so as far as I know mythtv has been setup correctly. I'm wondering if there's anything configuration specifically in myth I should be looking out for... again, i had no problems with 0.2.x ivtv drivers for over a year. Finally... sorry for the long post, I'm just trying to make sure I include all the relevant info here and if I haven't please feel free to ask. Thanks. Grant ------------------ Other info: I'm using Debian with 2.6.8 kernel. Dmesg output: ivtv: ==================== START INIT IVTV ==================== ivtv: version 0.3.7 (k) loading ivtv: Linux version: 2.6.8-1-386 preempt 386 gcc-3.3 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. ivtv: Autodetected WinTV PVR 350 card (iTVC15 based) ACPI: PCI interrupt 0000:02:07.0[A] -> GSI 19 (level, low) -> IRQ 177 tuner: chip found at addr 0xc2 i2c-bus ivtv i2c driver #0 ivtv: i2c attach to card #0 ok [client=(tuner unset), addr=61] tveeprom: Ignoring new-style parameters in presence of obsolete ones tveeprom: Hauppauge: model = 48132, rev = K168, serial# = 7391267 tveeprom: tuner = LG TAPE H001F MK3 (idx = 68, type = 47) tveeprom: tuner fmt = NTSC(M) (eeprom = 0x08, v4l2 = 0x00001000) tveeprom: audio processor = MSP4448 (type = 1b) tveeprom: decoder processor = SAA7115 (type = 13) ivtv: i2c attach to card #0 ok [client=tveeprom[50], addr=50] saa7115: Ignoring new-style parameters in presence of obsolete ones ivtv: i2c attach to card #0 ok [client=saa7115[50], addr=21] saa7127: Ignoring new-style parameters in presence of obsolete ones ivtv: i2c attach to card #0 ok [client=saa7127[50], addr=44] msp3400: Ignoring new-style parameters in presence of obsolete ones msp34xx: ivtv version msp34xx: init: chip=MSP3448W-A2, has NICAM support, simple (D) mode, simpler (G) no-thread mode msp34xx: $Id$ compiled on: Aug 29 2005 00:29:41 ivtv: i2c attach to card #0 ok [client=MSP3448W-A2, addr=40] ivtv: Encoder revision: 0x02040011 ivtv: Decoder revision: 0x02020023 ivtv: Create DMA encoder MPEG stream: 0 x 32768 buffers (0KB total) ivtv: Create DMA encoder YUV stream: 0 x 10800 buffers (0KB total) ivtv: Create DMA encoder VBI stream: 0 x 17472 buffers (0KB total) ivtv: Create DMA encoder PCM audio stream: 0 x 4608 buffers (0KB total) ivtv: Create encoder radio stream ivtv: Create DMA decoder MPEG stream: 0 x 65536 buffers (0KB total) ivtv: Create DMA decoder VBI stream: 0 x 2048 buffers (0KB total) ivtv: Create decoder VOUT stream ivtv: Create DMA decoder YUV stream: 0 x 43200 buffers (0KB total) ivtv: Create DMA decoder OSD stream: 0 x 65536 buffers (0KB total) tuner: type set to 47 (LG NTSC (TAPE series)) by ivtv i2c driver #0 ivtv: Initialized WinTV PVR 350, card #0 ivtv: ==================== END INIT IVTV ==================== ivtv-osd: Framebuffer module loaded (attached to ivtv card id 0) ivtv-osd warning: Framebuffer is at decoder-relative address 0x00510000 and has 1704960 bytes. ivtv-osd: screen coords: [0 0] -> [720 480] ivtv-osd: original global alpha = 208 ivtv-osd: current OSD state = 39 ivtv-osd: new global alpha = 208 (1 255 0) ivtv-osd: framebuffer at 0xe9510000, mapped to 0xdd692000, size 1350k ivtv-osd: mode is 720x480x32, linelength=2880 ivtv-osd: fb0: iTVC15 TV out frame buffer device ivtv: Allocate DMA decoder OSD stream: 16 x 65536 buffers (1024KB total) ------------------------------------------------------- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf _______________________________________________ ivtv-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ivtv-devel
