On Sun, 2006-05-14 at 20:03 +0200, Axel Thimm wrote:
> > > > > What version of X would I have to degrade to for this driver ?
> > > > 
> > > > I am running xorg-x11-server-Xorg-1.0.1-8 in combination with the same
> > > > ivtv_dr version as you have, without any problems. I am running FC5. 
> > > > Either the x-version is the same one as distributed in FC5, or it is
> > > > the result of running yum (I do not remember).
> 
> > > It is unlikely that the ABI changed from release to the updates, I'm
> > > not sure why Steve has issues with it (?)
> 
> > If the ABI hasn't changed, perhaps the check routine has.
> > 
> > Current:
> > xorg-x11-server-Xorg-1.0.99.901-6
> > 
> > To be precise xorg-x11-server-Xorg-1.0.99.901-6.x86_64.rpm from
> > redhat-development, or whatever it is called currently.
> 
> You made me go through loops to detect the problem while it has
> nothing to do with FC5. :(

I'm sorry. In my mind it was a yum upgraded FC5.

In attempting to install xorg-x11-server-Xorg-1.0.1-9.fc5.1.1 i
discovered that my rpm futex problem was solved with the reboot, but
that yum (yum-2.6.1-0.fc5) still crashed after 2 attempts to get a lock
on an nfs filesystem. Don't know why this stopped working, but I moved
the directory tree local and it worked fine again.

I removed all xorg* rpm's from the system, and for good measure all
other rpm's from development repos (strangely few). After disabling the
development repos in yum I reinstalled the removed rpm's and for good
measure did a yum upgrade.

The result is a perfectly working ivtv xdriver.
(ivtv_xdriver-0.10.6-5.rhfc5.at)

Thanks for your help, Axel, and again sorry for the loops.

Can my system now safely be described as FC5 ? - I must admit to
currently compiling a few sources locally whilst trying to solve a
recent dvd-menu generation problem.

stv
-- 
Steve Peterson <[EMAIL PROTECTED]>
Thot System Consultants Ltd.


_______________________________________________
ivtv-devel mailing list
[email protected]
http://ivtvdriver.org/mailman/listinfo/ivtv-devel

Reply via email to