I has a similar problem with a black box in the middle of the screen, Knoppmyth R5F1.
I put the options ivtv_fb osd_compat=1 in the /etc/mythtv/modules/ivtv file. Then it worked. mielikki g wrote: > I had the exact same problem (gentoo kernel 2.6.22 with itvt, the > gentoo package for ivtv-fb wouldn't work so I got the tar ball and > manually copied the ivtv-driver.h header over). The same black > rectangle problem as described. (I'm not using X over the framebuffer > though -- I have X and mythtv on a small LCD monitor next to the TV. > The PVR-350 output goes to the TV.) > > If I have "options ivtv_fb osd_compat=1" then I get no video -- the > entire screen is black. If I leave off the "options ivtv_fb > osd_compat=1" then I get video but with a large black rectange > obscuring most of the video. > > Unfortunately, the ivtvfbctl program does not get built (and I read > something that said it isn't updated for ivtv-1.0.x yet). Fortunately > I found pointers on using v4l2-ctl. > > Looking at the current settings, I see: > > # v4l2-ctl --get-fmt-output-overlay > Format Video Output Overlay: > Left/Top : 0/0 > Width/Height: 0/0 > Field : Any > Chroma Key : 0x00000000 > Global Alpha: 0xff > Clip Count : 0 > Clip Bitmap : No > # v4l2-ctl --get-fbuf > Framebuffer Format: > Capability : Extern Overlay > Chromakey > Global Alpha > Local Alpha > Flags : Global Alpha > Base : 0x0xed510000 > Width : 0 > Height : 0 > Pixel Format : > > So I did "v4l2-ctl --set-fmt-output-overlay=global_alpha=0" and that > got rid of the black rectangle. Does that sound right? > > I still can't use it with mythtv yet (Can't initialize video / IVD > Error: Framebuffer number query failed. / eno: Invalid argument (22) / > Did you load the ivtv-fb Linux kernel module?) but that's another > error for another time. > > > > On 9/10/07, Stanley Merkx <[EMAIL PROTECTED]> wrote: > >>> I am trying to upgrade my mythtv box to the latest 2.6.22 kernel and >>> latest >>> ivtv drivers and latest myth. But I'm having a little trouble with the >>> ivtv_fb driver... >>> >>> Here is what I've got running now. >>> >>> --> ivtv drivers from the 2.6.22 kernel. ( these load without errors and >>> look to be working ok ) >>> >>> --> ivtv-fb compiled from the 1.0.2 tar ball -- ( NOTE: I did have to >>> manually copy the correct ivtv-driver2.h to ivtv-driver.h because it >>> wouldn't load when it used the ivtv-driver1.h -- I think this has >>> something >>> to do with the way detection of the 2.6.22 kernel is done. I'm running >>> GENTOO BTW.) But the frame buffer loads now without errors >>> >>> --> IVTV X driver compiled from source downloaded from subversion >>> >>> X and mythfront end run great over the frame buffer, but playback using >>> the >>> PVR-350 decoder doesn't work.. >>> >>> Trying to troubleshoot the problem -- I went back to the command prompt >>> and >>> played the video using >>> >>> cat file.mpg > /dev/video16 >>> >>> This works great before I load the ivtv-fb driver, BUT once I load the >>> ivtv-fb driver ( with modules.conf: options ivtv_fb osd_compat=1 ) >>> >>> The playback gives me a just a black screen -- although I can hear the >>> audio... >>> >>> So I think the problem is the ivtv-fb driver... -- >>> >>> Am I testing this properly?? Or am I missing some command that needs to be >>> run to tell the fb to switch from showing the X content to allow the video >>> to be played?? >>> >>> This all worked under earlier kernel and older ivtv versions ( actually I >>> think I was using ivtvdev driver not the X ivtv driver... ) >>> >>> I saw some people saying Xv with ivtv would allow playback over the ivtv >>> frame buffer without using the PVR-350 decoder, but I don't know how to >>> get >>> Xv working with the ivtv-fb. If anyone can explain that I'll give that a >>> try, but when I tried running myth playback without the 350 decoder to the >>> ivtv X driver the video is very very choppy.. Maybe Xv would help that, >>> but the way I had it working before with the HW decoding was so nice I'd >>> really rather get that working. >>> >>> >>> DMESG OUTPUT looks clean to me.. >>> ----------------------------------------------------- >>> ivtv0-fb: === Display mode change === >>> ivtv0-fb: Display size 720x480 (720x480 Virtual) @ 32bpp >>> ivtv0-fb: Display position 1,1 >>> ivtv0-fb: Display filter : on >>> ivtv0-fb: Color space : RGB >>> ivtv0-fb: Running in compatibility mode. Display resize & mode change >>> disabled >>> ivtv0-fb: Framebuffer registered on ivtv card id 0 >>> ----------------------------------------------------- >>> >>> >>> Appreciate any suggestions... >>> _______________________________________________ >>> ivtv-users mailing list >>> [email protected] >>> http://ivtvdriver.org/mailman/listinfo/ivtv-users >>> >> Probably the OSD (=X) is covering the output produced by the decoder. >> >> Try this: >> ivtvfbctl -d /dev/fb0 -l off >> ivtvfbctl -d /dev/fb0 -g off >> >> Hope this helps... >> >> Regards, >> Stanley. >> >> >> _______________________________________________ >> 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 > > > _______________________________________________ ivtv-users mailing list [email protected] http://ivtvdriver.org/mailman/listinfo/ivtv-users
