Alright, I got some more data: 1) The halt-on-switching-off-liveTV: there are no entries in /var/log/messages at or around the time the frontend reports that RingBuf error. Furthermore, I got no errors when testing normal capture or the tv-out. So this seems a Mythtv issue.
2) The teletext: I used Alevt to test and it works fine. Another Mythtv issue, it seems. 3) That leaves the inproper shutdown, which is certainly an issue with the ivtvfb module. Any ideas to debug this? Thanks so far, Paul On Wed, Dec 31, 2008 at 1:12 PM, Sander Sweers <[email protected]>wrote: > On Tue, Dec 30, 2008 at 14:03, Paul van Gerven > <[email protected]> wrote: > > Oops, typo! It is indeed a recent kernel: 2.6.27-9. > > Good :-) > > > but the little dmesg script does not output anything. > > That is because the output of ivtv changed. This needs fixing on the wiki. > > > Here's what I feel is the relevant part of the dmesg output: > > Indeed and it looks good. > > > Here's the Xorg.log for the framebuffer (as I said, on a separate X > server). > > I left out a part for mouse and keyboard. > > I see nothing weird, is there no backtrace at the end of the previous log? > > > The stalling when stopping live TV seems to be related to this (bold text > is > > mine): > > <snip> > > > RingBuf(/media/mythtv/intrepid/1007_20081230132120.mpg): Waited 8.0 > seconds > > for data to become available... > > 2008-12-30 13:21:43.762 Checking to see if there's a new livetv program > to > > switch to.. > > 2008-12-30 13:21:51.763 > > RingBuf(/media/mythtv/intrepid/1007_20081230132120.mpg) Error: Waited 16 > > seconds for data, aborting. > > When you see these is there anything in /var/log/messages at the same > time for ivtv or ivtvfb? > > > To rule out ivtv can you do some tests *without* having mythtv > running? When you do the tests please keep an eye on .var.log.messages > for errors from ivtv. > > To test normal capuring please run "cat /dev/video0 > test.mpg" and > check if it keeps working and that the file is playing properly. You > can also redirect it to /dev/null if you do not have a lot of space > but preferably not. > > To test the tv-out you can run "dd if=/dev/video of=/dev/video16 bs=64k". > > If these 2 tests work without issue it likely is not ivtv that is > causing issues. It might be ivtvfb but if it is then the logs should > have something of an error (backtrace maybe?). > > Greets > Sander > > <---- ivtv output ----> > > [ 19.036515] ivtv: Start initialization, version 1.4.0 > > [ 19.037286] ivtv0: Initializing card #0 > > [ 19.037290] ivtv0: Autodetected Hauppauge card (cx23415 based) > > [ 19.037335] ivtv 0000:07:05.0: PCI INT A -> GSI 21 (level, low) -> IRQ > 21 > > [ 19.090615] tveeprom 0-0050: Hauppauge model 48139, rev K2B7, serial# > > 9924044 > > [ 19.090618] tveeprom 0-0050: tuner model is Philips FM1216ME MK5 (idx > > 117, type 38) > > [ 19.090620] tveeprom 0-0050: TV standards PAL(B/G) PAL(I) SECAM(L/L') > > PAL(D/D1/K) (eeprom 0x74) > > [ 19.090623] tveeprom 0-0050: audio processor is MSP4418 (idx 25) > > [ 19.090624] tveeprom 0-0050: decoder processor is SAA7115 (idx 19) > > [ 19.090627] tveeprom 0-0050: has radio, has IR receiver, has no IR > > transmitter > > [ 19.090629] ivtv0: Autodetected Hauppauge WinTV PVR-350 > > [ 19.398871] saa7115 0-0021: saa7115 found (1f7115d0e100000) @ 0x42 > (ivtv > > i2c driver #0) > > [ 19.596209] saa7127 0-0044: saa7129 found @ 0x88 (ivtv i2c driver #0) > > [ 19.605966] msp3400 0-0040: MSP4418G-B3 found @ 0x80 (ivtv i2c driver > #0) > > [ 19.605968] msp3400 0-0040: msp3400 supports nicam and radio, mode is > > autodetect and autoselect > > [ 19.740163] tuner 0-0043: chip found @ 0x86 (ivtv i2c driver #0) > > [ 19.754048] tda9887 0-0043: creating new instance > > [ 19.754051] tda9887 0-0043: tda988[5/6/7] found > > [ 19.755341] tuner 0-0061: chip found @ 0xc2 (ivtv i2c driver #0) > > [ 19.770596] tuner-simple 0-0061: creating new instance > > [ 19.770599] tuner-simple 0-0061: type set to 38 (Philips PAL/SECAM > multi > > (FM1216ME MK3)) > > [ 19.782987] ivtv0: Registered device video0 for encoder MPG (4096 kB) > > [ 19.783016] ivtv0: Registered device video32 for encoder YUV (2048 kB) > > [ 19.783041] ivtv0: Registered device vbi0 for encoder VBI (1024 kB) > > [ 19.783066] ivtv0: Registered device video24 for encoder PCM (320 kB) > > [ 19.783091] ivtv0: Registered device radio0 for encoder radio > > [ 19.783116] ivtv0: Registered device video16 for decoder MPG (1024 kB) > > [ 19.783142] ivtv0: Registered device vbi8 for decoder VBI (64 kB) > > [ 19.783167] ivtv0: Registered device vbi16 for decoder VOUT > > [ 19.783193] ivtv0: Registered device video48 for decoder YUV (1024 kB) > > [ 19.783195] ivtv0: Initialized card #0: Hauppauge WinTV PVR-350 > > [ 19.783221] ivtv: End initialization > > [ 21.009585] loop: module loaded > > [ 21.740171] firmware: requesting v4l-cx2341x-enc.fw > > [ 21.802303] ivtv0: Loaded v4l-cx2341x-enc.fw firmware (376836 bytes) > > [ 21.802323] firmware: requesting v4l-cx2341x-dec.fw > > [ 21.818066] ivtv0: Loaded v4l-cx2341x-dec.fw firmware (262144 bytes) > > [ 22.016406] ivtv0: Encoder revision: 0x02060039 > > [ 22.016529] ivtv0: Decoder revision: 0x02020023 > > [ 22.068105] firmware: requesting v4l-cx2341x-init.mpg > > [ 22.109812] ivtv0: Loaded v4l-cx2341x-init.mpg firmware (155648 bytes) > > [ 22.304178] ivtvfb0: Framebuffer at 0xf5510000, mapped to 0xfa710000, > > size 1665k > > [ 22.379198] Console: switching to colour frame buffer device 80x30 > > [ 22.412114] ivtvfb0: Framebuffer registered on ivtv card id 0 > > _______________________________________________ > ivtv-users mailing list > [email protected] > http://ivtvdriver.org/mailman/listinfo/ivtv-users >
_______________________________________________ ivtv-users mailing list [email protected] http://ivtvdriver.org/mailman/listinfo/ivtv-users
