Must recall my previous message.
I've removed the following lines from xorg.conf and OSD en EPG are working
again
Option "VideoOverlay" "on"
Option "XVideo" "on"
The only issue at this moment is that lirc is not working with mplayer.
Will try later on with Xine.
Gr
Patrick
P.s. found it. was looking in messages.log .....
(II) Loading /usr/X11R6/lib/modules/drivers/ivtvdev_drv.o
(II) Module ivtv: vendor="The XFree86 Project"
compiled for 4.3.0, module version = 0.10.0
ABI class: XFree86 Video Driver, version 0.6
> -----Oorspronkelijk bericht-----
> Van: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] Namens John Harvey
> Verzonden: dinsdag 24 mei 2005 19:11
> Aan: [email protected]
> Onderwerp: RE: [ivtv-devel] .3.5f report. YUV working well,
> getting crashes though.
>
> The ivtvdev version is printed in the X log file (just after
> it loads it).
> The main version is 10.0
> The version i pushed out last night identifies itself as 10.1
> & also the messages in the X log file say IVTVDEV_TST instead
> of just IVTVDEV so i can identify if that variant is being used.
>
> John
>
> --- "Patrick de Brabander [mythtv]"
> <[EMAIL PROTECTED]> wrote:
>
> > Mine experience is that livetv is working, but the controls are
> > extremly slow.
> > Also OSD and EPG are not showing on the screen.
> > YUV is working fine, i can switch between livetv and video.
> >
> > I've attached a piece of my messages.log. No strange errors noticed.
> >
> > Using 0.3.5f and iivtvdev 1.0 (i believe, no version
> > attached)
> >
> > Maybe it is possible to let show a version number in the
> log file like
> > ivtv.
> >
> > Gr.
> >
> > Patrick
> >
> >
> > > -----Oorspronkelijk bericht-----
> > > Van: [EMAIL PROTECTED]
> > > [mailto:[EMAIL PROTECTED]
> > Namens John Harvey
> > > Verzonden: dinsdag 24 mei 2005 12:53
> > > Aan: [email protected]
> > > Onderwerp: Re: [ivtv-devel] .3.5f report. YUV
> > working well,
> > > getting crashes though.
> > >
> > > With Myth it's getting the vbi insertion stuff
> > enabled which
> > > is asking for more memory which is failing. With
> > just dd'ing
> > > i doubt it is doing that.
> > > As for the 2nd crash i have no idea but i may look
> > later tonight.
> > >
> > > Can you send me a complete log from ivtv_init to
> > the first
> > > crash and i'll take a look through the buffer
> > allocation.
> > > Since i don't actually need any buffers in the Xv
> > case for
> > > YUV output i will probably try to stop it
> > allocating it for that case.
> > >
> > > John
> > > --- Lucas Meijer <[EMAIL PROTECTED]> wrote:
> > > > Heya.
> > > >
> > > > With 3.5f I can switch between mpeg decoding,
> > yuv decoding
> > > as much as
> > > > I like. Whenever I throw in myth's livetv
> > however, things go bad.
> > > > Either I crash when starting up livetv, or the
> > next
> > > recording I watch
> > > > after having been in livetv. I've tried a lot of
> > times, and
> > > have seen
> > > > two different looking types of problems in
> > dmesg.
> > > > Both of them pasted
> > > > below:
> > > >
> > > > ivtv: Allocate DMA stream 0 using 128 16384 byte
> > buffers 2097152
> > > > kbytes total
> > > > ivtv: Allocate DMA stream 2 using 41 50540 byte
> > buffers 2097152
> > > > kbytes total
> > > > ivtv: Setup VBI API header 0x0000bd06 pkts 1
> > buffs
> > > > 48 ln 34 sz 64
> > > > ivtv: Setup VBI start 0x0018ea04 frames 48 fpi 1
> > lines 0x000000f1
> > > > saa7115: decoder disable output
> > > > saa7115: decoder enable output
> > > > ivtv: VBI insertion started
> > > > ivtv: Allocate DMA stream 5 using 16 65536 byte
> > buffers 1048576
> > > > .....................................
> > > May 24 18:44:21 localhost kernel: ivtv:
> > ==================== START INIT IVTV
> > ====================
> > May 24 18:44:21 localhost kernel: ivtv: version
> > 0.3.5 (f) loading
> > May 24 18:44:21 localhost kernel: ivtv: Linux
> > version: 2.6.10-1.771_FC2 686 REGPARM 4KSTACKS
> > gcc-3.3
> > May 24 18:44:21 localhost kernel: ivtv: In case of problems please
> > include the debug info May 24 18:44:21 localhost kernel:
> ivtv: between
> > the START INIT IVTV and END INIT IVTV lines when May 24 18:44:21
> > localhost kernel: ivtv: mailing the ivtv-devel mailinglist.
> > May 24 18:44:21 localhost kernel: ivtv: Autodetected WinTV PVR 350
> > card May 24 18:44:21 localhost kernel: ivtv: Found an
> > iTVC15 based chip
> > May 24 18:44:23 localhost kernel: PCI: Found IRQ 10 for device
> > 0000:02:0a.0 May 24 18:44:23 localhost kernel: ivtv: XXX PCI
> > device: 0x1130 vendor: 0x8086
> > May 24 18:44:23 localhost kernel: tveeprom:
> > Hauppauge: model = 48139, rev = K257, serial# =
> > 7596027
> > May 24 18:44:24 localhost kernel: tveeprom: tuner = Philips
> FM1216 ME
> > MK3 (idx = 57, type = 38) May 24 18:44:25 localhost kernel:
> tveeprom:
> > tuner fmt = PAL(B/G) PAL(I) SECAM(L/L) PAL(D/K) (eeprom =
> 0x74, v4l2 =
> > 0x00400e17) May 24 18:44:25 localhost kernel: tveeprom:
> > audio_processor = CS5331 (type = 9)
> > May 24 18:44:25 localhost kernel: ivtv: i2c attach
> > [client=tveeprom[50],ok] May 24 18:44:25 localhost kernel:
> ivtv: Tuner
> > Type 38, Tuner formats 0x00400e17, Radio: yes, Model 0x00ad2557,
> > Revision 0x00000001 May 24 18:44:25 localhost kernel: ivtv: Radio
> > detected May 24 18:44:25 localhost kernel: tuner: Ignoring
> new-style
> > parameters in presence of obsolete ones May 24 18:44:25 localhost
> > kernel: tuner: chip found at addr 0xc2 i2c-bus ivtv i2c
> driver #0 May
> > 24 18:44:25 localhost kernel: ivtv: i2c attach [client=(tuner
> > unset),ok] May 24 18:44:26 localhost kernel: saa7115:
> starting probe
> > for adapter ivtv i2c driver #0 (0x10005) May 24 18:44:26 localhost
> > kernel: saa7115: detecting
> > saa7115 client on address 0x42
> > May 24 18:44:26 localhost kernel: saa7115: writing init
> values May 24
> > 18:44:27 localhost kernel: ivtv: i2c attach [client=saa7115[50],ok]
> > May 24 18:44:27 localhost kernel: saa7115: status:
> > (1E) 0x00, (1F) 0xc0
> > May 24 18:44:27 localhost kernel: saa7127: Ignoring new-style
> > parameters in presence of obsolete ones May 24 18:44:27 localhost
> > kernel: saa7127: video encoder driver version V 0.3 loaded May 24
> > 18:44:27 localhost kernel: saa7127: detecting
> > saa7127 client on address 0x88
> > May 24 18:44:27 localhost kernel: saa7127: Selecting NTSC video
> > Standard May 24 18:44:27 localhost kernel: saa7127: Selecting
> > S-Video+Composite
> > May 24 18:44:27 localhost kernel: saa7127: Turn WSS off May 24
> > 18:44:27 localhost kernel: saa7127:
> > Widescreen Mode 4:3 Full Format
> > May 24 18:44:27 localhost lircd-0.7.1[2795]:
> > lircd(any) ready
> > May 24 18:44:27 localhost lircd: lircd start op succeeded May 24
> > 18:44:28 localhost kernel: saa7127: Selecting Normal
> Encoder Input May
> > 24 18:44:29 localhost lircd-0.7.1[2795]:
> > accepted new client on /dev/lircd
> > May 24 18:44:30 localhost kernel: saa7127: Enable Video
> Output May 24
> > 18:44:30 localhost kernel: ivtv: i2c attach [client=saa7127[50],ok]
> > May 24 18:44:30 localhost kernel: msp34xx: ivtv version May 24
> > 18:44:30 localhost kernel: msp34xx: init:
> > chip=MSP3418W-B3, has NICAM support, simple (D) mode, simpler (G)
> > no-thread mode May 24 18:44:30 localhost kernel: msp34xx: $Id$
> > compiled on: May 24 2005 18:38:25 May 24 18:44:30 localhost kernel:
> > ivtv: i2c attach [client=MSP3418W-B3,ok] May 24 18:44:30 localhost
> > kernel: tda9885/6/7: chip found @ 0x86 May 24 18:44:30 localhost
> > kernel: ivtv: i2c attach [client=tda9887,ok] May 24
> 18:44:30 localhost
> > kernel: ivtv: Encoder
> > revision: 0x02040011
> > May 24 18:44:30 localhost kernel: ivtv: Decoder
> > revision: 0x02020023
> > May 24 18:44:30 localhost kernel: ivtv: Configuring WinTV
> PVR 350 card
> > with 10 streams May 24 18:44:30 localhost kernel: ivtv: Registered
> > v4l2 device, streamtype 0 minor 0
> > May 24 18:44:30 localhost kernel: ivtv: Create DMA stream 0
> using 128
> > 16384 byte buffers 0 kbytes total May 24 18:44:30
> localhost kernel:
> > ivtv: Registered
> > v4l2 device, streamtype 1 minor 32
> > May 24 18:44:30 localhost kernel: ivtv: Create DMA stream 1
> using 80
> > 25920 byte buffers 0 kbytes total May 24 18:44:30
> localhost kernel:
> > ivtv: Registered
> > v4l2 device, streamtype 2 minor 224
> > May 24 18:44:30 localhost kernel: ivtv: Create DMA stream 2
> using 41
> > 50540 byte buffers 0 kbytes total May 24 18:44:30
> localhost kernel:
> > ivtv: Registered
> > v4l2 device, streamtype 3 minor 24
> > May 24 18:44:30 localhost kernel: ivtv: Create DMA stream 3
> using 455
> > 4608 byte buffers 0 kbytes total May 24 18:44:30 localhost kernel:
> > ivtv: Registered
> > v4l2 device, streamtype 4 minor 64
> > May 24 18:44:30 localhost kernel: ivtv: Create stream 4 May 24
> > 18:44:30 localhost kernel: ivtv: Registered
> > v4l2 device, streamtype 5 minor 16
> > May 24 18:44:30 localhost kernel: ivtv: Create DMA stream 5
> using 16
> > 65536 byte buffers 0 kbytes total May 24 18:44:30
> localhost kernel:
> > ivtv: Registered
> > v4l2 device, streamtype 6 minor 228
> > May 24 18:44:30 localhost kernel: ivtv: Create DMA stream 6
> using 1024
> > 2048 byte buffers 0 kbytes total May 24 18:44:30 localhost kernel:
> > ivtv: Registered
> > v4l2 device, streamtype 7 minor 232
> > May 24 18:44:30 localhost kernel: ivtv: Create stream 7 May 24
> > 18:44:30 localhost kernel: ivtv: Registered
> > v4l2 device, streamtype 8 minor 48
> > May 24 18:44:30 localhost kernel: ivtv: Create DMA stream 8
> using 80
> > 25920 byte buffers 0 kbytes total May 24 18:44:30
> localhost kernel:
> > ivtv: Create DMA stream 9 using 32 65536 byte buffers 0
> kbytes total
> > May 24 18:44:30 localhost kernel: ivtv: Setting Tuner 38 May 24
> > 18:44:30 localhost kernel: tuner: type set to
> > 38 (Philips PAL/SECAM multi (FM1216ME MK3)) by ivtv i2c
> driver #0 May
> > 24 18:44:30 localhost kernel: saa7115: decoder set norm PAL May 24
> > 18:44:30 localhost kernel: saa7115: set
> > audio: 0x01
> > May 24 18:44:30 localhost kernel: saa7115: decoder set
> input (4) May
> > 24 18:44:30 localhost kernel: saa7115: now setting
> Composite input May
> > 24 18:44:30 localhost kernel: ivtv: Setting audio matrix to
> input 3,
> > output 1 May 24 18:44:30 localhost kernel: ivtv: Switching
> standard to
> > PAL.
> > May 24 18:44:30 localhost kernel: ivtv:
> > ivtv_enc_thread: pid = 2566, itv = 0xe0dff6a0 May 24 18:44:30
> > localhost kernel: ivtv:
> > ivtv_enc_vbi_thread: pid = 2567, itv = 0xe0dff6a0 May 24 18:44:30
> > localhost kernel: ivtv:
> > ivtv_dec_thread: pid = 2568, itv = 0xe0dff6a0 May 24 18:44:30
> > localhost kernel: ivtv:
> > ivtv_dec_vbi_thread: pid = 2569, itv = 0xe0dff6a0 May 24 18:44:30
> > localhost kernel: saa7115: decoder set norm PAL May 24 18:44:30
> > localhost kernel: saa7115: set
> > audio: 0x01
> > May 24 18:44:30 localhost kernel: saa7127: Setting Encoder Video
> > Standard May 24 18:44:30 localhost kernel: saa7127: Set PAL
> Video Mode
> > May 24 18:44:30 localhost kernel: saa7127: Selecting PAL video
> > Standard May 24 18:44:30 localhost kernel: ivtv:
> Initialized WinTV PVR
> > 350, card #0 May 24 18:44:30 localhost kernel: ivtv:
> > ==================== END INIT IVTV
> > ====================
> > May 24 18:44:30 localhost kernel: ivtv-osd:
> > Framebuffer module loaded (attached to ivtv card id
> > 0)
> > May 24 18:44:30 localhost kernel: ivtv-osd:
> > Framebuffer is at decoder-relative address 0x00510000 and
> has 1704960
> > bytes.
> > May 24 18:44:30 localhost kernel: ivtv-osd: screen
> > coords: [0 0] -> [720 576]
> > May 24 18:44:30 localhost kernel: ivtv-osd: original global alpha =
> > 208 May 24 18:44:31 localhost kernel: ivtv-osd: current OSD
> state = 39
> > May 24 18:44:31 localhost kernel: ivtv-osd: new global
> alpha = 208 (1
> > 255 0) May 24 18:44:31 localhost kernel: ivtv-osd:
> > framebuffer at 0x45510000, mapped to 0xe1d10000, size 1620k May 24
> > 18:44:31 localhost kernel: ivtv-osd: mode is 720x576x32,
> > linelength=2880 May 24 18:44:31 localhost kernel: Console:
> switching
> > to colour frame buffer device 90x36
> >
> === message truncated ===
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by Yahoo.
> Introducing Yahoo! Search Developer Network - Create apps using Yahoo!
> Search APIs Find out how you can build Yahoo! directly into
> your own Applications - visit
> http://developer.yahoo.net/?fr=offad-ysdn-ostg-q22005
> _______________________________________________
> ivtv-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/ivtv-devel
-------------------------------------------------------
This SF.Net email is sponsored by Yahoo.
Introducing Yahoo! Search Developer Network - Create apps using Yahoo!
Search APIs Find out how you can build Yahoo! directly into your own
Applications - visit http://developer.yahoo.net/?fr=offad-ysdn-ostg-q22005
_______________________________________________
ivtv-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/ivtv-devel
