On 3/27/06, Michael Krufky <mkrufky@xxxxxxxxxxx> wrote:
Yes, this did fix the mismatch in ivtv, so that seems to work fine. It did do something to my lirc, haven't taken any time to figure out what. Unfortunately, it still does not fix the PVR-350 vs DViCO FusionHDTV 5 Lite problem.
>
> First, remove the old ivtv modules.... I think you can find them in
> /lib/modules/`uname -r`/ivtv
>
> then:
>
> hg clone http://linuxtv.org/hg/v4l-dvb
> cd v4l-dvb
> make ivtv
> make
> make install
>
> I wonder if this will help
>
>
>
> I will give this a try tomorrow, after the day's recordings are
> finished. FYI, I've been using Axel's ivtv rpms from atrpms.net
> <http://atrpms.net> since about 0.4.1? or so. I wasn't seeing any
> difference between that and building myself and decided to take the
> easy route. Recently there have been some issues with getting the
> ivtv driver to play nice with dvb, due to some mismatches. See:
> http://www.gossamer-threads.com/lists/ivtv/devel/28632?search_string=0.4.3%20and%202.6.15.5;#28632
> Any thoughts? Thanks,
> bttv: disagrees about version of symbol tveeprom_hauppauge_analog
> bttv: Unknown symbol tveeprom_hauppauge_analog
> bttv: disagrees about version of symbol tveeprom_hauppauge_analog
This is exactly what we can avoid by using the build method that I
described above. All of the ivtv modules are built together with all of
their dependencies, including all of the v4l and dvb trees. This
happens when the wrong combination of modules become mixed up.
Yes, this did fix the mismatch in ivtv, so that seems to work fine. It did do something to my lirc, haven't taken any time to figure out what. Unfortunately, it still does not fix the PVR-350 vs DViCO FusionHDTV 5 Lite problem.
_______________________________________________ linux-dvb@xxxxxxxxxxx http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
