Jesse, Duncan, Thanks for your replies.
For me, the system does work, but feels a bit shakey. If I avoid certain actions, it all works very nice. These are the currently identifyable dagerous actions: 1. start X when recording after a boot. When the mythbackend immediately starts recording on boot (cold and warm), starting X on the PVR TV-out results in a frozen system. I tried starting X while doing a dd if=/dev/video0 of=/dev/null after having started X before and played livetv. This gave no problems, so it seems related to the first action after booting in this case. 2. switch to a virtual terminal when watching livetv Sometimes it is fine, but not always. Note that I have a framebuffer terminal, although I'm not sure it is related. Also, I start X with two screens, one on the TV (via PVR350) and one on the nvidia TNT card. I can move the mouse from monitor to TV and back. Very handy when installing mythtv. Finally, how does the mix of an EPIA SP13000 and either a PVR350 or PVR500 work together? I'm thinking of making that the target board for the final myth box. (The box must be super quiet.) Cheers, Luud On 2/15/06, Duncan Webb <[EMAIL PROTECTED]> wrote: > Luud Heck wrote: > > >Hi, > > > >I'm playing around with ivtv and mythtv and it is all looking very > >good. Well almost. > > > >I seem to be able to reproduce a system freeze when using the ivtv > >0.4.2 driver in combination with the X-driver for TV-out. As I have > >seen freezes with this driver without the X-Driver installed I think > >the problem lies somewhere in the ivtv driver. > > > > > I'm finding ivtv-0.4.0 very stable with the x-driver 0.10.6 and a recent > svn version. When I upgraded the ivtv to 0.4.2 lock-ups were quite > common, so I went back to 0.4.0 and everything is fine again. In fact, > the system was running ok so recording continued normally so the ivtv > driver was not dead and I could ssh from a different machine without any > problems so the machine wasn't dead and as you say a reboot was required > to reset the screen. > > Sorry doesn't help you much except to say your not alone. > Duncan > > >After a fresh reboot, when mythbackend is recording video on the > >PVR350 (in this case the only card in the system) starting X on the > >PVR350 TV-Out (framebuffer) results in a system freeze. The only thing > >left is pressing the reset button. > > > >Nothing works. Network is gone, terminals gone, the system is dead, or > >frozen. > > > >I have seen system freezes before, but I could not reproduce them. > >They would happen after a cold boot. After loading the ivtv drivers > >the system would sometimes freeze when the system was working hard > >(e.g. the famous gentoo emerge compiles), however, without ever having > >used the ivtv driver. > > > >There is nothing in the logs that could indicate the direct source of > >the freeze, although I have seen IVTV_IRQ_DEC_DMA_ERR messages in my > >system log. > > > >Now for some details: > > > >kernel: 2.6.14-gentoo-r5 > >firmware: pvr_1.18.21.22254_inf.zip and pvr_2.0.24.23035.zip > >ivtv driver: 0.4.2 > >x-driver: 0.10.6 > >mythtv: 0.19 > > > >System: ABIT BH7, with Celeron 700 (Coppermine) and 3x 128MB RAM, > >Diamond VIPER 550 (nvidia TNT) graphics (using the Xorg nv driver, not > >the nvida one), 3Com 3c905 ehternet and Abit HotRod Pro100 Highpoint > >HPT360 ATA1100. > > > > > >Feb 14 20:54:12 neon ivtv: ==================== START INIT IVTV > >==================== > >Feb 14 20:54:12 neon ivtv: version 0.4.2 (tagged release) loading > >Feb 14 20:54:12 neon ivtv: Linux version: 2.6.14-gentoo-r5-crypto > >preempt PENTIUMIII gcc-3.4 > >Feb 14 20:54:12 neon ivtv: In case of problems please include the > >debug info between > >Feb 14 20:54:12 neon ivtv: the START INIT IVTV and END INIT IVTV > >lines, along with > >Feb 14 20:54:12 neon ivtv: any module options, when mailing the > >ivtv-users mailinglist. > >Feb 14 20:54:12 neon ivtv0: Autodetected WinTV PVR 350 card (cx23415 based) > >Feb 14 20:54:12 neon PCI: Found IRQ 7 for device 0000:00:09.0 > >Feb 14 20:54:12 neon PCI: Sharing IRQ 7 with 0000:00:07.2 > >Feb 14 20:54:12 neon ivtv0: Unreasonably low latency timer, setting to > >64 (was 32) > >Feb 14 20:54:12 neon tveeprom: ivtv version > >Feb 14 20:54:12 neon tveeprom: Hauppauge: model = 48134, rev = J321, > >serial# = 2775820 > >Feb 14 20:54:12 neon tveeprom: tuner = Philips FM1216 (idx = 21, type = 5) > >Feb 14 20:54:12 neon tveeprom: tuner fmt = PAL(B/G) (eeprom = 0x04, > >v4l2 = 0x00000007) > >Feb 14 20:54:12 neon tveeprom: audio processor = MSP4418 (type = 19) > >Feb 14 20:54:12 neon tveeprom: decoder processor = SAA7115 (type = 13) > >Feb 14 20:54:12 neon ivtv0: i2c attach to card #0 ok [client=tveeprom, > >addr=50] > >Feb 14 20:54:12 neon tuner (ivtv): chip found at addr 0xc2 i2c-bus > >ivtv i2c driver #0 > >Feb 14 20:54:12 neon ivtv0: i2c attach to card #0 ok [client=(tuner > >unset), addr=61] > >Feb 14 20:54:12 neon saa7115 0-0021: ivtv driver > >Feb 14 20:54:12 neon saa7115 0-0021: saa7115 found @ 0x42 (ivtv i2c driver > >#0) > >Feb 14 20:54:12 neon ivtv0: i2c attach to card #0 ok [client=saa7115, > >addr=21] > >Feb 14 20:54:12 neon saa7127 0-0044: ivtv driver > >Feb 14 20:54:12 neon saa7127 0-0044: saa7127 found @ 0x88 (ivtv i2c driver > >#0) > >Feb 14 20:54:12 neon ivtv0: i2c attach to card #0 ok [client=saa7127, > >addr=44] > >Feb 14 20:54:12 neon msp3400 0-0040: ivtv driver > >Feb 14 20:54:12 neon msp3400 0-0040: chip=MSP4418G-A2 +nicam +simple > >+simpler +radio mode=simpler > >Feb 14 20:54:12 neon msp3400 0-0040: msp34xxg daemon started > >Feb 14 20:54:12 neon ivtv0: i2c attach to card #0 ok > >[client=MSP4418G-A2, addr=40] > >Feb 14 20:54:12 neon ivtv0: loaded v4l-cx2341x-enc.fw firmware (262144 bytes) > >Feb 14 20:54:12 neon ivtv0: loaded v4l-cx2341x-dec.fw firmware (262144 bytes) > >Feb 14 20:54:12 neon ivtv0: Encoder revision: 0x02050032 > >Feb 14 20:54:12 neon ivtv0: Decoder revision: 0x02020023 > >Feb 14 20:54:12 neon ivtv0: Allocate DMA encoder MPEG stream: 128 x > >32768 buffers (4096KB total) > >Feb 14 20:54:12 neon ivtv0: Allocate DMA encoder YUV stream: 161 x > >12960 buffers (2048KB total) > >Feb 14 20:54:12 neon ivtv0: Allocate DMA encoder VBI stream: 80 x > >26208 buffers (2048KB total) > >Feb 14 20:54:12 neon ivtv0: Allocate DMA encoder PCM audio stream: 455 > >x 4608 buffers (2048KB total) > >Feb 14 20:54:12 neon ivtv0: Create encoder radio stream > >Feb 14 20:54:12 neon ivtv0: Allocate DMA decoder MPEG stream: 16 x > >65536 buffers (1024KB total) > >Feb 14 20:54:12 neon ivtv0: Allocate DMA decoder VBI stream: 512 x > >2048 buffers (1024KB total) > >Feb 14 20:54:12 neon ivtv0: Create decoder VOUT stream > >Feb 14 20:54:12 neon ivtv0: Allocate DMA decoder YUV stream: 20 x > >51840 buffers (1024KB total) > >Feb 14 20:54:12 neon ivtv0: loaded v4l-cx2341x-init.mpg firmware (155648 > >bytes) > >Feb 14 20:54:12 neon tuner: type set to 5 (Philips PAL_BG (FI1216 and > >compatibles)) by ivtv i2c driver #0 > >Feb 14 20:54:12 neon ivtv0: Initialized WinTV PVR 350, card #0 > >Feb 14 20:54:12 neon ivtv: ==================== END INIT IVTV > >==================== > >Feb 14 20:54:12 neon lirc_i2c: chip found @ 0x18 (Hauppauge IR) > >Feb 14 20:54:12 neon ivtv0: i2c attach to card #0 ok [client=Hauppauge > >IR, addr=18] > >Feb 14 20:54:12 neon lirc_dev: lirc_register_plugin: sample_rate: 10 > >Feb 14 20:54:12 neon ivtv0-osd: Framebuffer module loaded (attached to > >ivtv card id 0) > >Feb 14 20:54:12 neon ivtv0-osd: screen coords: [0 0] -> [720 576] > >Feb 14 20:54:12 neon ivtv0-osd: original global alpha = 208 > >Feb 14 20:54:12 neon ivtv0-osd: current OSD state = 39 > >Feb 14 20:54:12 neon ivtv0-osd: new global alpha = 208 (1 255 0) > >Feb 14 20:54:12 neon ivtv0-osd: framebuffer at 0xd5510000, mapped to > >0xda610000, size 1665k > >Feb 14 20:54:12 neon ivtv0-osd: mode is 720x576x32, linelength=2880 > >Feb 14 20:54:12 neon ivtv0-osd: fb1: cx23415 TV out frame buffer device > >Feb 14 20:54:12 neon ivtv0: Allocate DMA decoder OSD stream: 16 x > >65536 buffers (1024KB total) > > > > > >Somewhat later I find in the log (I think this is when I started X, > >but without mythbackend running and the start of X was successful): > > > >Feb 14 21:36:03 neon ivtv0-osd warning: ivtvfb_check_var > >Feb 14 21:36:03 neon ivtv0 warning: IRQ: IVTV_IRQ_DEC_DMA_ERR > >Feb 14 21:36:03 neon ivtv0-osd warning: ivtvfb_check_var > >Feb 14 21:36:03 neon ivtv0-osd warning: ivtvfb_set_par > >Feb 14 21:36:59 neon lircd-0.8.0[6207]: accepted new client on /dev/lircd > > > >When starting mythfrontend and starting livetv (over PVR350 > >framebuffer out) there are no more messages in the log. > > > >It would be great if this freeze could be resolved, so if there is any > >more information I can give please let me know. > > > >Thanks for your help, > >Luud > > > >_______________________________________________ > >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 > _______________________________________________ ivtv-devel mailing list [email protected] http://ivtvdriver.org/mailman/listinfo/ivtv-devel
