There is no need to use v4l-dvb, you can just compile against your
current kernel (provided it is a 2.6.18 kernel).
It is module versioning problems, you can try modprobe -f ivtv to force
the ivtv load regardless of module version mismatches.
Hans
On Friday 03 November 2006 21:46, Kirk Bocek wrote:
> Hans,
> I downloaded your new driver, updated v4l, compiled and installed.
> When I modprobe ivtv I get:
>
> ivtv: disagrees about version of symbol video_unregister_device
> ivtv: Unknown symbol video_unregister_device
> ivtv: disagrees about version of symbol video_device_alloc
> ivtv: Unknown symbol video_device_alloc
> ivtv: disagrees about version of symbol video_register_device
> ivtv: Unknown symbol video_register_device
> ivtv: disagrees about version of symbol video_device_release
> ivtv: Unknown symbol video_device_release
>
> The steps I followed were:
>
> 1. untar your source.
> 2. Copy the v4l-dvb directory from my last trunk copy
> 3. make v4l-update
> 4. make clean v4l-distclean
> 5. make v4l
> 6. make v4l-install
> 7. make
> 8. make install
>
> Is there anything I missed?
>
> Kirk Bocek
>
> Hans Verkuil wrote:
> > Hi all,
> >
> > A week later than intended, but here is a new beta to test with:
> >
> > If you are running a 2.6.18 kernel with ivtv-0.8, then I'd
> > appreciate it if you can test the following beta driver:
> >
> > http://dl.ivtvdriver.org/ivtv/unstable/ivtv-b3508.tar.gz
>
> _______________________________________________
> ivtv-users mailing list
> [email protected]
> http://ivtvdriver.org/mailman/listinfo/ivtv-users
_______________________________________________
ivtv-users mailing list
[email protected]
http://ivtvdriver.org/mailman/listinfo/ivtv-users
