Peter Lee wrote:
On Sat, 18 Dec 2004 13:22:48 -0500, mielikki-ivtv
<[EMAIL PROTECTED]> wrote:
Peter Lee wrote:
The upgrade went smoothly, except for one thing: The OSD is not
working.
I had a similar problem with the OSD and it turned out to be a
permission problem. I do a
  chmod a+rw /dev/fb/2

Thanks for the tip, but forgive my ignorance: I don't know what /dev/fb/2 is! I have /dev/fb which is a link to /dev/fb0. I thought that /dev/fb0 was my framebuffer device. Am I wrong about that? At any rate, I did a chmod a+rw on /dev/fb0, but this did not have any effect on the osd.

In my system log file, after the END IVTV, ivtv-osd tells me which the frame buffer device is:


ivtv: ==================== END INIT IVTV ====================
ivtv-osd: Framebuffer module loaded (attached to ivtv card id 0)
ivtv-osd: Framebuffer is at decoder-relative address 0x00510000 and has 1704960 bytes.
ivtv-osd: screen coords: [0 0] -> [720 480]
ivtv-osd: original global alpha = 208
ivtv-osd: current OSD state = 39
ivtv-osd: new global alpha = 208 (1 255 0)
ivtv-osd: framebuffer at 0xed510000, mapped to 0xea061000, size 1350k
ivtv-osd: mode is 720x480x32, linelength=2880
ivtv-osd: fb2: iTVC15 TV out frame buffer device


My /dev/fb2 is a symbolic link to /dev/fb/2 so the permissions on /dev/fb/2 are the important ones for me. Your kernel might set things up differently.

Anyway, I am stumped on this.  Do I need a more recent ivtv?  I am
currently running ivtv-0.1.10-47_pre2_ck100zz.rhfc2.at.

I'm using the 2.0 drivers. Don't know if that makes a difference. _______________________________________________ mythtv-users mailing list [email protected] http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

Reply via email to