[ivtv-users] Just getting started, need pointers HVR-1600

[Andy Walls]

On Wed, 2008-10-08 at 20:18 -0400, Richard Ayotte wrote:
> It looks like the driver that you built is not for the kernel that you
> are running.
>         1. Boot with the kernel that you will be using
>         2. As root run modprobe -d cx18

On Fedora, 'modprobe -r cx18' removes the module.  I guess Mandriva uses
something slightly different?

>         3. Download a fresh copy of the driver at
>         http://www.linuxtv.org/hg/v4l-dvb/archive/tip.tar.gz
>         4. Extract it to a directory. (Don't use the same one that you
>         just used.)
>         5. From the directory that you extracted the driver run make
>         and then as root run make install; depmod -a
>         6. Download the firmware from
>         http://dl.ivtvdriver.org/ivtv/firmware/cx18-firmware.tar.gz
>         7.Extract the files and put all the *.fw into your firmware
>         directory. I'm not sure where that is in Mandriva but you
>         might want to look under /lib/firmware
>         or /lib/firmware/[kernel-version]. You can get your kernel
>         version by running the uname -a command.
>         8. As root run modprobe cx18
>         9. Run dmesg|grep cx18 to see what happened
> --
> Richard

Those look like good instructions for a clean rebuild of the latest.
Hopefully that works.


> 
> On Wed, Oct 8, 2008 at 2:51 PM, Carl L. Gilbert
> <clg-social at rigidsoftware.com> wrote:
>         Im just getting started here and trying to get the driver
>         loaded so I can use MythTV.  I was told the ivtv driver is the
>         one to use for my card which is the Hauppauge HVR-1600.  I
>         tried to simply download and build and install the driver.  I
>         have Mandriva 2008.  I managed to get it to make and
>         appearantly install, but when I go to 
>         
>         modprobe cx18
>         
>         I get some error messages and it does not seem to load.
>         
>         
>         videodev: exports duplicate symbol v4l_printk_ioctl (owned by
>         v4l2_common)

You have an old version of v4l2-common.ko lying around.  Obviously
something went wrong with the build & install of the latest v4l-dvb
repository.

On my system:

$ find /lib/modules/ -name 'videodev.ko'
/lib/modules/2.6.25.10-86.fc9.x86_64/kernel/drivers/media/video/videodev.ko
/lib/modules/2.6.26.5-45.fc9.x86_64/kernel/drivers/media/video/videodev.ko

$ nm /lib/modules/2.6.26.5-45.fc9.x86_64/kernel/drivers/media/video/videodev.ko | grep ioctl
00000000000000b7 r __kstrtab_v4l_printk_ioctl
000000000000009b r __kstrtab_video_ioctl2
0000000000000090 r __ksymtab_v4l_printk_ioctl
0000000000000070 r __ksymtab_video_ioctl2
0000000000000a7c t __video_do_ioctl
0000000000000850 r v4l1_ioctls
0000000000000240 r v4l2_int_ioctls
0000000000000940 r v4l2_ioctls
                 U v4l_compat_translate_ioctl
00000000000007de T v4l_printk_ioctl       <------ T == machine code (Text) exists here
0000000000003f4d T video_ioctl2


$ find /lib/modules/ -name 'v4l2-common.ko'
/lib/modules/2.6.25.10-86.fc9.x86_64/kernel/drivers/media/video/v4l2-common.ko
/lib/modules/2.6.26.5-45.fc9.x86_64/kernel/drivers/media/video/v4l2-common.ko

$ nm /lib/modules/2.6.26.5-45.fc9.x86_64/kernel/drivers/media/video/v4l2-common.ko | less
(no output)


The symbol should be defined in videodev.ko and not exists in v4l2-common.ko


>         cx18: Unknown symbol video_ioctl2
>         cx18: Unknown symbol video_devdata
>         cx18: Unknown symbol video_unregister_device
>         cx18: Unknown symbol video_device_alloc
>         cx18: Unknown symbol video_register_device
>         cx18: Unknown symbol video_device_release

All these missing symbols exist in the videodev.ko module (I think), so
that module didn't load due to the symbol collision with the
(apparently) old v4l2-common.ko module.


>         Any idea what I could have done wrong.

Something went wrong with the: 


$ make
$ su root
# make unload
# make install

After a quick skim, I think Richard's steps above should get you a fresh
start at things.

As a troubleshooting step, ensure you do *not* manually do a 'make
menuconfig' or similar.  Sure, you'll build lots of modules you don't
need, but you won't need to hunt down things like this either.


Regards,
Andy

>           I have been into the guts of Linux back in the day, but its
>         been a while.  OS just runs and since im not fixing on it all
>         the time I tend to forget stuff.  If you could point me to
>         some info or give me some tips I would appreciate it.
>         
>         
>         
>         Thanks!
>         
>         
>         
>         Carl

>