On 2/18/06, Axel Thimm <[EMAIL PROTECTED]> wrote:
> Hi,
>
> in the last weeks I have seen several bug reports on the usage of ivtv
> on Fedora Core/RHEL. I just edited the wiki pages to reflect this:
>
> http://ivtvdriver.org/index.php?title=Howto%3AFedora&diff=1881&oldid=1485
>
> To sum it up:
>
> o ATrpms always shipped modules that would conflict with kernel or v4l
>   with a different name (e.g. foo was named foo-ivtv). The default
>   setup was therefore to use what the kernel provides.
>
> o If a user required the use of the ivtv supporting module he would
>   have to add an "alias foo foo-ivtv" line to divert the module to the
>   ivtv one. Almost all modules were required until 0.4.x.
>
> o With 0.4.x some modules/fixes made it into the kernel, ivtv detects
>   this and doesn't build them (for newer kernels).
>
> That means that if you previously had to use alias lines to enforce
> the usage of ivtv's versions of these modules, now the same lines
> disable those modules completely if ivtv doesn't ship them anymore.
>
> Check your ivtv's kmdl contents with
>
> rpm -ql ivtv-kmdl-`uname -r`
>
> If there is more than ivtv.ko in them (there currently still is) you
> *can* use alias lines to override the kernel's with ivtv's.
>
> Make sure you don't have alias lines pointing to non-existent ivtv
> kernel modules!
>
> Future kernels will have even better support for ivtv, so always
> perform the above check when upgrading your kernel (e.g. 2.6.16 will
> most probably have everything in place, so ivtv package will have no
> supporting modules at all anymore => no alias lines at all, too).

Yes - I got bitten by this when I upgraded kernel and ivtv on Friday.
I always test the decoding after an upgrade (usually even after a
reboot), but didn't think to test the tuning. Fortunately there are
informative error messages in /var/log/messages, so once I realised it
was broken, fixing it was straightforward.

Regards,

Chris

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

Reply via email to