2009/12/9 Valerio Bontempi <valerio.bontempi@xxxxxxxxx>: > 2009/12/9 Paulo Assis <pj.assis@xxxxxxxxx>: >> Hi, >> I've just responded to a similar issue in the linux-uvc list: >> https://lists.berlios.de/pipermail/linux-uvc-devel/2009-December/005391.html >> >> Do you also have insertion errors when modprobing the driver under opensuse? >> If so just follow the instructions :D, they worked in the above case. >> >> Best regards, >> Paulo >> >> 2009/12/9 Valerio Bontempi <valerio.bontempi@xxxxxxxxx>: >>> Hi all, >>> >>> I am trying to install v4l-dvb drivers from source because my device >>> (Terratec Cinergy T XS, usb device DVB only) isn't supported by >>> official v4l-dvb released in last kernel version yet: it is simply >>> detected with the wrong firmware, but modifing the source code of the >>> driver is works fine, tested successfully on ubuntu 9.10 (I have >>> already submitted the patch to v4l team). >>> >>> I compiled v4l-dvb drivers and installed them through make install, >>> but then v4l-dvb driver is not working anymore: the video device is >>> not created, and I don't find any information about my device in dmesg >>> (neither the message about the wrong firmware). So I am supposing that >>> v4l-dvb is not working at all. >>> >>> Does someone know how I can understand where is the problem? >>> >>> Best regards >>> >>> Valerio >>> -- >>> To unsubscribe from this list: send the line "unsubscribe linux-media" in >>> the body of a message to majordomo@xxxxxxxxxxxxxxx >>> More majordomo info at http://vger.kernel.org/majordomo-info.html >>> >> > > I checked I have no .gz file in whole /lib/modules dir and in its subdirectories > but the ouput of 'modprobe em28xx' is > > #modprobe em28xx > WARNING: Error inserting ir_common > (/lib/modules/2.6.31.5-0.1-desktop/updates/kernel/drivers/media/common/ir-common.ko): > Unknown symbol in module, or unknown parameter (see dmesg) > WARNING: Error inserting v4l2_compat_ioctl32 > (/lib/modules/2.6.31.5-0.1-desktop/updates/kernel/drivers/media/video/v4l2-compat-ioctl32.ko): > Unknown symbol in module, or unknown parameter (see dmesg) > WARNING: Error inserting v4l1_compat > (/lib/modules/2.6.31.5-0.1-desktop/updates/kernel/drivers/media/video/v4l1-compat.ko): > Unknown symbol in module, or unknown parameter (see dmesg) > WARNING: Error inserting videodev > (/lib/modules/2.6.31.5-0.1-desktop/updates/kernel/drivers/media/video/videodev.ko): > Unknown symbol in module, or unknown parameter (see dmesg) > WARNING: Error inserting v4l2_common > (/lib/modules/2.6.31.5-0.1-desktop/updates/kernel/drivers/media/video/v4l2-common.ko): > Unknown symbol in module, or unknown parameter (see dmesg) > FATAL: Error inserting em28xx > (/lib/modules/2.6.31.5-0.1-desktop/updates/kernel/drivers/media/video/em28xx/em28xx.ko): > Unknown symbol in module, or unknown parameter (see dmesg) > > and from dmesg > > [ 2080.998842] videobuf_vmalloc: disagrees about version of symbol > videobuf_queue_core_init > [ 2080.998864] videobuf_vmalloc: Unknown symbol videobuf_queue_core_init > [ 2080.999053] videobuf_vmalloc: disagrees about version of symbol > videobuf_queue_cancel > [ 2080.999064] videobuf_vmalloc: Unknown symbol videobuf_queue_cancel > [ 2476.403046] videobuf_vmalloc: disagrees about version of symbol > videobuf_queue_core_init > [ 2476.403066] videobuf_vmalloc: Unknown symbol videobuf_queue_core_init > [ 2476.403277] videobuf_vmalloc: disagrees about version of symbol > videobuf_queue_cancel > [ 2476.403290] videobuf_vmalloc: Unknown symbol videobuf_queue_cancel > Valerio, This is clearly caused by old modules still laying around. In the case of Chris he just uninstalled then reinstalled everything related to v4l then build v4l-dvb by following the instructions on the v4l-dvb wiki (http://www.linuxtv.org/wiki/index.php/How_to_Obtain,_Build_and_Install_V4L-DVB_Device_Drivers): # make distclean # make menuconfig [this is optional] # make # make install # make unload # modprobe em28xx That solved is problem. Best regards, Paulo -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
