On 12/16/06, Axel Thimm <[EMAIL PROTECTED]> wrote: > On Sat, Dec 16, 2006 at 06:24:21PM +0100, Hans Verkuil wrote: > > On Saturday 16 December 2006 18:11, Kyrre Ness Sjobak wrote: > > > Yup, that seems to be the problem: > > > ivtv-tune 1.50 > > > > Unfortunately, this doesn't mean much since the version number wasn't > > updated :-( > > > > The change was from June 5th 2006. So if the app is older, then it is > > certainly wrong. > > Kyrre, try rpm -qf `which ivtv-tune` to find out which package you > have installed.
Can we please stop top posting? Thanks! > > > Is Axel Thim still on this list? I think he's got a bug, as the > > > yum.log output shows i have installed the newest ivtv package. > > > > > > Thanks! Now that i know what the problem is, i'll just wait and see > > > if some updated packages shows up. Btw, does v4l-ctl work? Can i (in > > > the meantime) just use ivtv-tune to get the frequencies, and then use > > > v4l-ctl to tune to them? > > > > Yes, that will work. If changing the tuner with v4l2-ctl works but not > > with ivtv-tune, then you must be using an older ivtv-tune. Also check > > with 'which -a ivtv-tune' whether you have multiple ivtv-tune apps. > > If I understand correct this is because of the new api which got merged in 2.6.18. One thing that is unclear is if the newer >=June 5th 2006 ivtv-tune versions also work with the old api? I want to make this clear on the troubleshooting page? Thanks Sander _______________________________________________ ivtv-users mailing list [email protected] http://ivtvdriver.org/mailman/listinfo/ivtv-users
