On Sunday 19 Aug 2007, Michael Starks wrote: > Ian Armstrong wrote: > > If you run 'rmmod ivtv-fb;modprobe ivtv-fb osd_compat=1;dmesg'. The last > > lines from dmesg will contain the ivtv-fb module output, which should be > > similar to the following: > > > > ivtv0-fb: Framebuffer at 0xd1510000, mapped to 0xe2090000, size 1665k > > ivtv0-fb: === Validated display mode === > > ivtv0-fb: Display size 720x576 (720x576 Virtual) @ 32bpp > > ivtv0-fb: Display position 1,1 > > ivtv0-fb: Display filter : on > > ivtv0-fb: Color space : RGB > > ivtv0-fb: === Display mode change === > > ivtv0-fb: Display size 720x576 (720x576 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 > > Once again, thank you everyone for their help. > > I tried as you suggested but cannot unload the ivtv or ivtv_fb modules, > even if I comment that section out in modprobe.conf, they still load. I > get a message saying that they are in use. I even tried to comment out > the fbdevhw and v4l modules in xorg.conf, thinking that had something to > do with it. I'm not sure how they are even getting loaded...
Maybe I should have made it clear that you can't be running X when you try to rmmod, since X is using ivtv-fb preventing it from being unloaded. There's no need to rmmod the ivtv module itself. > Anyway, one thing I noticed was that it /dev/video49 was being linked to > /dev/fb0, whereas with my FC4 build it was /dev/video17. I changed that > in mythtvsetup and now get a very brief, pixelated image when going to > watch live tv, but no sound and it immediately goes to black as usual. video49 is for yuv only. For mpeg you should be using video17. > I think it's time to get back to basics and re-post some configs and > logs to see if there is something obvious I am doing wrong (sorry for > the verboseness, but I don't want to make assumptions). I'd also be > interested to know if *anyone* has the PVR350 xdriver working with > CentOS 5? On to the relevant stuff... > ivtv1-fb: Display size 640x400 (640x400 Virtual) @ 8bpp This isn't normal for the osd_compat option. > 2007-08-19 11:40:02.385 IVD Error: Failed to process frame > eno: Invalid argument (22) > 2007-08-19 11:40:02.420 IVD Error: Failed to process frame > eno: Invalid argument (22) This is normally caused by the lack of the osd_compat option. > (II) IVTVDEV(0): Enabling Xv support for PVR350 Your X driver has Xv overlay support. If you don't use the mpeg decoder, MythTV should be able to use the overlay instead. It may not be ideal for what you want, but you should at least be able to watch video full screen with this until you resolve the osd_compat problem. -- Ian _______________________________________________ ivtv-users mailing list [email protected] http://ivtvdriver.org/mailman/listinfo/ivtv-users
