[ATrpms-users] Packages required for working ivtv-fb

[Axel Thimm]

On Tue, Jun 05, 2007 at 09:18:13AM -0700, Schlaegel wrote:
> On 6/4/07, Axel Thimm <Axel.Thimm at atrpms.net> wrote:
> > You should also tell us what is broken. :)
> 
> (Sorry for my rabbit trail/hijack of this thread. I am truly curious
> if there is a blessed F7 setup, because I would like to update my own
> systems as well.)
> 
> Well, I had some free time last night, so I checked out the broken
> system. I eventually did get it working, but I am still curious what
> your recommended setup is.

Well, since you got it working, your setup at least belongs to the
recommended ones.

> As best I can tell, I encountered two main problems when I yum
> upgraded. First, the new ivtv would cause the system to hang during
> boot at udev, because the modprobe entries that were previously
> required, now freeze the system.

Which ones were required? The ivtv options in modprobe.conf had been
deprecated since quite some time, do you mean these options?

> Eventually, I removed those, entries and it worked. Second, mythtv
> seemed to lock up with the new ivtv when starting to watch video. I
> believe this was really just a problem with the frame buffer
> covering up the video and not showing the osd.  Eventually, I added
> a new modprobe "options ivtv-fb osd_compat=1" which took care of it.
> 
> So now my system works, but these simple fixes were very hard to
> discover, and documented incorrectly at numerous places
> (recommendations to downgrade udev, to manually change udev rules, and
> statements that mythtv was simply incompatible with the new ivtv).
> 
> When I originally yum updated my system and it froze, I was very
> shocked, and stopped updating the other system. I didn't have time to
> explore the multiple options and combinations that seemed to be
> available. I spent quite some time with the system hang issue, but
> eventually gave up. I would still like to know what your recommend
> setup is for F6.
> 
> Also, perhaps package changes that cannot work with settings required
> for previous packages should be handled differently so they aren't
> automatically handled by an update.

Well, you often don't have a choice as the updates are dictated by the
kernel itself. I wouldn't had minded staying with ivtv 0.8.x for a
while longer, but it only worked for 2.6.18. Every new kernel has been
requiring a new ivtv version.

> And also, I know I would greatly appreciate a simple page explaining
> the current working combinations available. This said, I greatly
> appreciate your work, and my two mythboxes would not exist if it
> were not for your repository.

For F7 given that it is that new, one will still have to explore what
works and what not. Your PVR350 setup seems to "only" need
osd_compat=1, other setups like go7007 may need other tweaks.

But what is true is that there is an ATrpms wiki missing to put that
info into. :/

> *boring details follow*
> 
> My new current, up-to-date, working setup is:
> 
>   kernel-2.6.20-1.2952.fc6.i686
> 
>   video4linux-kmdl-2.6.20-1.2952.fc6-20070420-80.fc6.i686
> 
>   ivtv-0.10.3-129.fc6.i386
>   ivtv_xdriver-0.10.7-8_r3843.fc6.at.i386
>   ivtv-kmdl-2.6.20-1.2952.fc6-0.10.3-129.fc6.i686
>   ivtv-firmware-20070217-13.at.noarch
>   perl-Video-ivtv-0.13-8.fc6.at.i386
> 
>   lirc-0.8.2-66_cvs20070301.fc6.at.i386
>   lirc-kmdl-2.6.20-1.2952.fc6-0.8.2-67_cvs20070301.fc6.i686
>   lirc-devices-0.8-3.fc6.at.noarch
>   lirc-lib-0.8.2-67_cvs20070301.fc6.i386
> 
>   mythtv-0.20.1-157.fc6.i386
> 
> 
> -Schlaegel
> 
> _______________________________________________
> atrpms-users mailing list
> atrpms-users at atrpms.net
> http://lists.atrpms.net/mailman/listinfo/atrpms-users

-- 
Axel.Thimm at ATrpms.net
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://lists.atrpms.net/pipermail/atrpms-users/attachments/20070605/198e2fba/attachment.bin