[ivtv-users] Nova-T and PVR-350 conflicts: A world of tveeprom

[Keith C]

On Dec 20, 2005, at 3:50 PM, Jono Bacon wrote:

> Hello folks,
>
> New to the list, and I hope you can help.
>
> I have recently built a spanking gorgeous MythTV box. Inside it is a
> Nova-T (the new version which requires the cx88 driver) and a PVR-350
> which obviously uses the glorius ivtv. I first installed the PVR-350
> as per the instructions and then I later added the Nova-T which uses
> the cx88 driver from my 2.2.12-9 kernel on my Ubuntu Breezy box.
>
> Anyway, when I added the Nova-T, it threw a load of errors such as:
>
> [4294695.684000] cx88xx: disagrees about version of symbol
> tveeprom_hauppauge_analog
> [4294695.684000] cx88xx: Unknown symbol tveeprom_hauppauge_analog
> [4294695.685000] cx8800: Unknown symbol cx88_reset
> [4294695.685000] cx8800: Unknown symbol cx88_call_i2c_clients
>
> After some googling and discussion on #mythtv-users, it seems that the
> reason for this fault is that the tveeprom.ko module that I compiled
> in ivtv that replaces the kernel version, is incompatible when using
> the cx88 driver. I was also told that the ivtv tveeprom driver
> actually doesnt do anything different for the PVR-350, and using the
> stock kernel tveeprom just drive both the cards just fine.
>
> With a skip in my step I reverted to the kernel tveeprom driver, and
> from the boot messages it seemed that both the DVB and PVR-350 cards
> loaded fine. I tried the DVB card and it seemed to work fine (albeit
> if a little out of sync with the sound), but the PVR-350 gave no
> output.
>
> Digging a bit deeper it seemed that /dev/video0 was assigned to the
> cx88 driver, but there was no report in /var/log/messages that
> /dev/video1 was assigned to the ivtv driver. To test both video0 and
> video1 I run:
>
>   cat /dev/video[number] > foo.mpg
>
>> From /dev/video1 I got some static displayed.
>
> So my question is:
>
>  - Is there a simple fix to solve this problem? I have tried renaming
> the ivtv module tveeprom-ivtv and also tried a tveeprom-ivtv module
> alias, but this didnt work.

I think you'll also want to use the kernel version of the tuner  
module if you're using it's tveeprom.  You should also probably set  
ivtv_first_minor to 1 in your modprobe.conf :

options ivtv ivtv_first_minor=1

This will make sure ivtv always lets your dvb card grab video0.

>
>  - I have heard that this is all resolved with ivtv 0.4.1 and kernel
> 2.6.14 and later. Is this true, and if so, could someone explain to me
> how this is resolved? Will I need two tveeprom version, and if not,
> which one do I need - the ivtv or kernel one?

The ivtv versions do a little more identification than the kernel  
versions, but thats going away in the 0.5.x series, as their goal is  
merging with v4l, and thus the kernel.

Keith C