| LinHES Forums http://forums.linhes.org/ |
|
| ivtv0-osd problem http://forums.linhes.org/viewtopic.php?f=17&t=8824 |
Page 1 of 1 |
| Author: | mac [ Sun Mar 05, 2006 1:15 am ] |
| Post subject: | ivtv0-osd problem |
Hello there! I put this in the hardware forum yesterday.. don't think it was the correct place for it. I am lost. I would love it someone could give me some ideas. My mythtv works well except for the OSD. Whenever the OSD should be showing up on the screen I get this message in syslog: ivtv0-osd warning: Size is overflowing the framebuffer 1638400, only 1382400 available and this one in the X server log: (EE) IVTVDEV(0): FBIOBLANK: Invalid argument I think---- fb0 is 1638400 -- vesafb fb1 is 1382400 -- pvr350 tvout -- Thanks, Martin kernel: vesafb: framebuffer at 0xf6000000, mapped to 0xe0880000, using 6144k, total 16320k kernel: vesafb: mode is 1024x768x16, linelength=2048, pages=8 kernel: vesafb: protected mode interface info at c000:03b8 kernel: vesafb: scrolling: redraw kernel: ivtv: ==================== START INIT IVTV ==================== kernel: ivtv: version 0.4.0 (tagged release) loading kernel: ivtv: Linux version: 2.6.11.9-chw-2 preempt 586 gcc-3.3 kernel: ivtv: In case of problems please include the debug info kernel: ivtv: between the START INIT IVTV and END INIT IVTV lines when kernel: ivtv: mailing the ivtv-devel mailinglist. kernel: ivtv0: Autodetected WinTV PVR 350 card (iTVC15 based) kernel: ACPI: PCI Interrupt Link [LNKA] enabled at IRQ 10 kernel: PCI: setting IRQ 10 as level-triggered kernel: ACPI: PCI interrupt 0000:00:0d.0[A] -> GSI 10 (level, low) -> IRQ 10 kernel: tveeprom: ivtv version kernel: tveeprom: Hauppauge: model = 48132, rev = K268, serial# = 8208257 kernel: tveeprom: tuner = LG TAPE H001F MK3 (idx = 68, type = 47) kernel: tveeprom: tuner fmt = NTSC(M) (eeprom = 0x08, v4l2 = 0x00001000) kernel: tveeprom: audio processor = MSP4448 (type = 1b) kernel: tveeprom: decoder processor = SAA7115 (type = 13) kernel: ivtv0: i2c attach to card #0 ok [client=tveeprom, addr=50] kernel: tuner: chip found at addr 0xc2 i2c-bus ivtv i2c driver #0 kernel: ivtv0: i2c attach to card #0 ok [client=(tuner unset), addr=61] kernel: msp34xx: ivtv version kernel: msp34xx: init: chip=MSP3448W-A2, has NICAM support, simple (D) mode, simpler (G) no-thread mode kernel: msp34xx: $Id$ compiled on: Nov 25 2005 19:04:01 kernel: ivtv0: i2c attach to card #0 ok [client=MSP3448W-A2, addr=40] kernel: saa7115 0-0021: saa7115 found @ 0x42 (ivtv i2c driver #0) kernel: ivtv0: i2c attach to card #0 ok [client=saa7115, addr=21] kernel: saa7127 0-0044: saa7129 found @ 0x88 (ivtv i2c driver #0) kernel: ivtv0: i2c attach to card #0 ok [client=saa7127, addr=44] kernel: ivtv0: loading /lib/modules/ivtv-fw-enc.bin kernel: ivtv0: loading /lib/modules/ivtv-fw-dec.bin kernel: ivtv0: Encoder revision: 0x02050032 kernel: ivtv0: Decoder revision: 0x02020023 kernel: ivtv0: Allocate DMA encoder MPEG stream: 128 x 32768 buffers (4096KB total) kernel: ivtv0: Allocate DMA encoder YUV stream: 194 x 10800 buffers (2048KB total) kernel: ivtv0: Allocate DMA encoder VBI stream: 120 x 17472 buffers (2048KB total) kernel: ivtv0: Allocate DMA encoder PCM audio stream: 455 x 4608 buffers (2048KB total) kernel: ivtv0: Create encoder radio stream kernel: ivtv0: Allocate DMA decoder MPEG stream: 16 x 65536 buffers (1024KB total) kernel: ivtv0: Allocate DMA decoder VBI stream: 512 x 2048 buffers (1024KB total) kernel: ivtv0: Create decoder VOUT stream kernel: ivtv0: Allocate DMA decoder YUV stream: 24 x 43200 buffers (1024KB total) kernel: ivtv0: loading /lib/modules/ivtv_init_mpeg.bin kernel: tuner: type set to 47 (LG NTSC (TAPE series)) by ivtv i2c driver #0 kernel: ivtv0: Initialized WinTV PVR 350, card #0 kernel: ivtv: ==================== END INIT IVTV ==================== kernel: ivtv0-osd: Framebuffer module loaded (attached to ivtv card id 0) kernel: ivtv0-osd warning: Framebuffer is at decoder-relative address 0x00510000 and has 1704960 bytes. kernel: ivtv0-osd: screen coords: [0 0] -> [720 480] kernel: ivtv0-osd: original global alpha = 208 kernel: ivtv0-osd: current OSD state = 39 kernel: ivtv0-osd: new global alpha = 208 (1 255 0) kernel: ivtv0-osd: framebuffer at 0xed510000, mapped to 0xe2010000, size 1350k kernel: ivtv0-osd: mode is 720x480x32, linelength=2880 kernel: ivtv0-osd: fb1: iTVC15 TV out frame buffer device kernel: ivtv0: Allocate DMA decoder OSD stream: 16 x 65536 buffers (1024KB total) kernel: cx2388x v4l2 driver version 0.0.4 loaded kernel: lirc_i2c: chip found @ 0x18 (Hauppauge IR) kernel: ivtv0: i2c attach to card #0 ok [client=Hauppauge IR, addr=18] ================ Section "Monitor" Identifier "NTSC Monitor" HorizSync 30-68 VertRefresh 50-120 Mode "720x480" # D: 34.563 MHz, H: 37.244 kHz, V: 73.897 Hz DotClock 34.564 HTimings 720 752 840 928 VTimings 480 484 488 504 Flags "-HSync" "-VSync" EndMode Option "DPMS" EndSection Section "Device" Identifier "Hauppauge PVR 350 iTVC15 Framebuffer" Driver "ivtvdev" Option "fbdev" "/dev/fb1" Option "ivtv" "/dev/fb1" Option "TVOverscan" "0.3" BusID "PCI:0:13:0" EndSection Section "Screen" Identifier "TV Screen" Device "Hauppauge PVR 350 iTVC15 Framebuffer" Monitor "NTSC Monitor" DefaultDepth 24 DefaultFbbpp 32 Subsection "Display" Depth 24 FbBpp 32 Modes "720x480" EndSubsection EndSection =============== |
|
| Author: | mac [ Mon Mar 06, 2006 8:54 am ] |
| Post subject: | fixed by upgrading ivtv |
I upgraded the firmware and ivtv driver to 0.4.3 and it solved the OSD issue. http://ivtvdriver.org/index.php/Main_Page |
|
| Author: | Fidelis [ Mon Mar 13, 2006 5:20 pm ] |
| Post subject: | |
Glad you solved it, but I must ask, was your text weirdly wrapping on your OSD? While the MythTV frontend is displayed correctly on my TV (thru TV-out), my OSD on my computer is frozen while displaying the startup messages after ivtv initialization. I'm using R5Alpha30.2 with a 350 using the composite out. Just wondering if this fix would work for me, too. |
|
| Author: | mac [ Mon Mar 13, 2006 5:40 pm ] |
| Post subject: | |
Nope, I didn't/don't have the problem with the OSD text wrapping. prior to the upgrade, OSD was not working at all for me. I have another post related to this here: http://mysettopbox.tv/phpBB2/viewtopic. ... highlight= |
|
| Author: | Fidelis [ Mon Mar 13, 2006 6:28 pm ] |
| Post subject: | |
Crap. Well, thanks for replying so quickly. I'll keep looking around to see why my OSD is hanging while my tv-out boot myth frontend so nicely. Maybe due to my OSD being hooked up to onboard video? Currently, I'm quite clueless, but at least you eliminated another thing for me to try 
|
|
| Page 1 of 1 | All times are UTC - 6 hours |
| Powered by phpBB® Forum Software © phpBB Group http://www.phpbb.com/ |
|