Hans Verkuil writes:
preliminary feedback. Don't forget to read the README! Esp. the required osd_compat=1 module option for those who use ivtv_fb with MythTV.
I'm looking at the notes in the README, and wondering if that might explain my problem with ivtv_fb in the 0.9.1 release. Does ivtv_fb in 0.9.1 only work with some specific vesa console mode?
I had 0.7.0 working with vga=792; after upgrading to 2.6.19 and 0.9.1, ivtv_fb loads without errors, and /proc/fb happily reports its presence, but TV-Out coming out of my PVR-350 remains a blue screen. I understand that, just like in 0.7.0, it should turn to black when ivtv_fb initializes.
ivtv_fb loads without reporting any errors. I succesfully built Ian Campbell's fixed ivtvdev driver for modular X, which appears to come up fine and then runs, blindly, on the TV-Out which still remains blue. It's as if everything is working -- X is talking to a functioning ivtvfb.ko and likes what it sees -- except that the TV-Out signal is not turned on. I'm guessing that ivtvfb.ko needs some specific vga mode, and just no-ops without reporting an error, if it's different. I tried a couple of other vesa modes, with no change.
I checked FC 6's 2.6.19 kernel config, it has CONFIG_FB_TRIDENT=m and CONFIG_FB_TRIDENT_ACCEL=y set, so I think I'm ok there.
It's a bit late for me to downgrade back down to FC 4 and 0.7.0; so I'll just run myth on my video card; the rest of ivtv works fine, just the framebuffer is out of commission.
P.S. I find no mention of the osd_compat flag documentation, scanning through the trunk tarball's READMEs. Where is it?
pgpBWNHvhJGGW.pgp
Description: PGP signature
_______________________________________________ ivtv-devel mailing list [email protected] http://ivtvdriver.org/mailman/listinfo/ivtv-devel
