\nThis is from www.verbraak.org\/wiki\/index.php\/Linux_Mantis_driver but his site seems to be down a lot so I have mirrored it here because I am trying to get my 1034 card to work with Linux.\n<\/p>\n
\n \n<\/p>\n
<\/p>\n
\nCurrently the Mantis chipset driver for linux is in Alpha state.\n<\/p>\n
\nThis Mantis chipset is used on DVB board for reception of DVB-T, DVB-S, DVB-S2, DVB-C signals.\n<\/p>\n
\nIn this small Howto i explain how I got the mantis driver up and
\nrunning in my vanilla linux kernel.
\nI had to do it in this way because I also own two Hauppauge PVR cards
\n(PVR-350 and PVR-150) which do not work well with the mantis module.\n<\/p>\n
\nThis example has been tested with linux kernel source 2.6.22
\nand the ivtv driver from the linuxtv.org hg reposititory and the one
\nincluded in the kernel on a Fedora Core 6 setup.\n<\/p>\n
\r\nWARNING:<\/strong> IVTV 0.10.3 and Mantis and kernel 2.6.21 and up do not work together.\r\nFrom kernel 2.6.22 the ivtv module is part of the kernel and you do not need to download it from the ivtvdriver.org website.\r\nTo get ivtv and the mantis working in kernel 2.6.21 and up you need to add extra<\/strong> module parameters to the saa7115<\/em> module. \r\nSee the instructions at the end for this.\r\n<\/pre>\n<\/a><\/p>\n
[edit<\/a>]<\/span> Following steps you need to take (short<\/strong> ways for kernel 2.6.23.1):<\/span><\/h3>\n
\n
- Download the patch file<\/a> for kernel 2.6.23.1.\n\t<\/li>\n
- use your current kernel or take a kernel source tree from http:\/\/www.kernel.org<\/a>. Make sure you have the kernel headers\/sources files\/packages installed and you have the kernel up and running.\n\t<\/li>\n
- Apply the patch.\n\t<\/li>\n<\/ul>\n
\r\n#> cd <path to kernel source>\r\n#> patch -p1 < <path to mantis-2.6.23.1.patch file>\/mantis-2.6.23.1.patch\r\n<\/pre>\n\n
- Activate the mantis modules in your kernel config. Answer yes to the Mantis parts.\n\t<\/li>\n<\/ul>\n
\r\n#> make oldconfig\r\n<\/pre>\n\n
- Compile.\n\t<\/li>\n<\/ul>\n
\r\n#> make\r\n#> make modules_install\r\n<\/pre>\n\n
- When you use your current kernel sources do load the modules\n\t<\/li>\n<\/ul>\n
\r\n#> modprobe mantis\r\n#> dmesg | grep -i dvb\r\nfound a VP-1034 PCI DVB-S\/DSS device on (02:05.0),\r\nDVB: registering new adapter (Mantis dvb adapter).\r\nmantis_frontend_init (0): Probing for MB86A16 (DVB-S\/DSS)\r\nmantis_frontend_init (0): found MB86A16 DVB-S\/DSS frontend @0x08\r\nDVB: registering frontend 0 (Fujitsu MB86A16 DVB-S)...\r\n<\/pre>\n<\/a><\/p>\n
[edit<\/a>]<\/span> Following steps you need to take (long<\/strong> way for kernels 2.6.21 and up):<\/span><\/h3>\n
\n
- use your current kernel or take a kernel source tree from http:\/\/www.kernel.org<\/a>. Make sure you have the kernel headers\/sources files\/packages installed and you have the kernel up and running.\n\t<\/li>\n
- Get the mantis dvb source tree from http:\/\/jusst.de\/hg\/mantis\/archive\/tip.tar.bz2<\/a>\n\t<\/li>\n
- Copy the directory <path to mantis
\n\ttree>\/linux\/drivers\/media\/dvb\/mantis to <path to kernel
\n\tsource>\/drivers\/media\/dvb\/\n\t<\/li>\n- Add the following three lines to the file <path to kernel
\n\tsource>\/drivers\/media\/dvb\/Kconfig. Add them before the last entry in
\n\tthis file.\n\t<\/li>\n<\/ul>\n\r\ncomment "Supported Mantis Adapters"\r\ndepends on DVB_CORE && PCI && I2C\r\nsource "drivers\/media\/dvb\/mantis\/Kconfig"\r\n<\/pre>\n\n
- Add the following option "mantis\/<\/strong>" to the file path to kernel source>\/drivers\/media\/dvb\/Makefile. It should look like this\n\t<\/li>\n<\/ul>\n
\r\n#\r\n# Makefile for the kernel multimedia device drivers.\r\n# \r\nobj-y \u00a0:= dvb-core\/ frontends\/ ttpci\/ ttusb-dec\/ ttusb-budget\/ b2c2\/ bt8xx\/ cinergyT2\/ dvb-usb\/ pluto2\/ mantis\/\r\n<\/pre>\n\n
- Copy the files <path to mantis
\n\ttree>\/linux\/drivers\/media\/dvb\/frontends\/mb86a16* to <path to
\n\tkernel source>\/drivers\/media\/dvb\/frontends\n\t<\/li>\n- Copy the files <path to mantis
\n\ttree>\/linux\/drivers\/media\/dvb\/frontends\/cu1216* to <path to
\n\tkernel source>\/drivers\/media\/dvb\/frontends\n\t<\/li>\n- Add the following lines to the file <path to kernel source>\/drivers\/media\/dvb\/frontends\/Kconfig just after the config DVB_TDA10086<\/strong>\n\t<\/li>\n<\/ul>\n
\r\nconfig DVB_MB86A16\r\ntristate "Fujitsu MB86A16 based"\r\ndepends on DVB_CORE && I2C\r\ndefault m\r\nhelp\r\nA DVB-S\/DSS tuner module. Say Y when you want to support this frontend.\r\nconfig DVB_CU1216\r\ntristate "Philips CU1216 tuner based"\r\ndepends on DVB_CORE && I2C\r\ndefault m\r\nhelp\r\nA DVB-C tuner module. Say Y when you want to support this frontend.\r\n<\/pre>\n\n
- Add the following two lines to the file <path to kernel source>\/drivers\/media\/dvb\/frontends\/Makefile\n\t<\/li>\n<\/ul>\n
\r\nobj-$(CONFIG_DVB_MB86A16) += mb86a16.o\r\nobj-$(CONFIG_DVB_CU1216) += cu1216.o\r\n<\/pre>\n\n
- Change in the file <path to kernel
\n\tsource>\/drivers\/media\/dvb\/frontends\/cu1216.c line 37 to look like
\n\tthis (ignore the line numbers)\n\t<\/li>\n<\/ul>\n\r\n 34 #include <linux\/slab.h>\r\n35 \r\n36 #include "dvb_frontend.h"\r\n37 #include "..\/mantis\/mantis_core.h"\r\n38 #include "cu1216.h"\r\n39 #include "cu1216_regs.h"\r\n<\/pre>\n\n
- You can now compile your kernel in the normal way and install
\n\tthe modules. If you wish to make sure the Mantis modules have been
\n\tselected do a make menuconfig<\/em>\n\t<\/li>\n<\/ul>\n\r\n#> cd <path to kernelsource>\r\n#> make menuconfig\r\n#> make\r\n#> make modules_install\r\n<\/pre>\n\n
- When you use your current kernel sources do load the modules\n\t<\/li>\n<\/ul>\n
\r\n#> modprobe mantis\r\n#> dmesg | grep -i dvb\r\nfound a VP-1034 PCI DVB-S\/DSS device on (02:05.0),\r\nDVB: registering new adapter (Mantis dvb adapter).\r\nmantis_frontend_init (0): Probing for MB86A16 (DVB-S\/DSS)\r\nmantis_frontend_init (0): found MB86A16 DVB-S\/DSS frontend @0x08\r\nDVB: registering frontend 0 (Fujitsu MB86A16 DVB-S)...\r\n<\/pre>\n\n
- Check the output of the dmesg command to see if the mantis modules loaded. Sometimes a reboot of the system is needed.\n\t<\/li>\n
- IMPORTANT:<\/strong> For kernels 2.6.21 and below the order in which you do the installations is also important. Every time you perform a make modules_install<\/strong> for the kernel you need to do the make install<\/strong> for the ivtv driver as well.\n\t<\/li>\n<\/ul>\n
\n
\nTo get the Hauppauge cards working do the following:\n<\/p>\n\n
- The ivtv module is now part of the kernel since 2.6.22. So
\n\tcheck your kernel. If you have a kernel below 2.6.22 then do the
\n\tfollowing <\/li>\n- Get the ivtv source from http:\/\/dl.ivtvdriver.org\/ivtv\/archive\/0.10.x\/ivtv-0.10.5.tar.gz<\/a>. See http:\/\/www.ivtvdriver.org<\/a> for latest version.\n\t<\/li>\n
- Extract the source, build and install it.\n\t<\/li>\n<\/ul>\n
\r\n#> tar -zxvpf ivtv-0.10.5.tar.gz\r\n#> cd ivtv-0.10.5\r\n#> make; make install\r\n<\/pre>\n\n
- Install the ivtv firmware<\/a> files in \/lib\/firmware\n\t<\/li>\n<\/ul>\n
\r\n#> cd \/lib\/firmware\r\n#> wget http:\/\/dl.ivtvdriver.org\/ivtv\/firmware\/firmware.tar.gz<\/a>\r\n#> tar -zxvpf firmware.tar.gz\r\n<\/pre>\n\n
- Load the ivtv modules:\n\t<\/li>\n<\/ul>\n
\r\n#> modprobe ivtv\r\n#> dmesg | grep -i ivtv\r\nivtv: ==================== START INIT IVTV ====================\r\nivtv: version 0.10.3 (development snapshot compiled on zo 20 mei 2007 08:57:55 CEST) loading\r\nivtv: Linux version: 2.6.21.1 SMP mod_unload PENTIUM4 4KSTACKS \r\nivtv: In case of problems please include the debug info between\r\nivtv: the START INIT IVTV and END INIT IVTV lines, along with\r\nivtv: any module options, when mailing the ivtv-users mailinglist.\r\nivtv0: Autodetected Hauppauge card (cx23415 based)\r\nivtv0: loaded v4l-cx2341x-enc.fw firmware (376836 bytes)\r\nivtv0: loaded v4l-cx2341x-dec.fw firmware (262144 bytes)\r\nivtv0: Encoder revision: 0x02060039\r\nivtv0: Decoder revision: 0x02020023\r\nivtv0: Autodetected Hauppauge WinTV PVR-350\r\ntuner 1-0061: chip found @ 0xc2 (ivtv i2c driver #0)\r\nsaa7115 1-0021: saa7115 found (1f7115d0e100000) @ 0x42 (ivtv i2c driver #0)\r\nsaa7127 1-0044: saa7127 found @ 0x88 (ivtv i2c driver #0)\r\nmsp3400 1-0040: MSP4418G-A2 found @ 0x80 (ivtv i2c driver #0)\r\nivtv0: Registered device video0 for encoder MPEG (4 MB)\r\nivtv0: Registered device video32 for encoder YUV (2 MB)\r\nivtv0: Registered device vbi0 for encoder VBI (1 MB)\r\nivtv0: Registered device video24 for encoder PCM audio (1 MB)\r\nivtv0: Registered device radio0 for encoder radio\r\nivtv0: Registered device video16 for decoder MPEG (1 MB)\r\nivtv0: Registered device vbi8 for decoder VBI (1 MB)\r\nivtv0: Registered device vbi16 for decoder VOUT\r\nivtv0: Registered device video48 for decoder YUV (1 MB)\r\nivtv0: loaded v4l-cx2341x-init.mpg firmware (155648 bytes)\r\nivtv0: Initialized Hauppauge WinTV PVR-350, card #0\r\nivtv: ====================== NEXT CARD ======================\r\nivtv1: Autodetected Hauppauge card (cx23416 based)\r\nivtv1: loaded v4l-cx2341x-enc.fw firmware (376836 bytes)\r\nivtv1: Encoder revision: 0x02060039\r\ntuner 2-0043: chip found @ 0x86 (ivtv i2c driver #1)\r\ntuner 2-0061: chip found @ 0xc2 (ivtv i2c driver #1)\r\nivtv1: Autodetected Hauppauge WinTV PVR-150\r\nivtv1: reopen i2c bus for IR-blaster support\r\ntuner 2-0043: chip found @ 0x86 (ivtv i2c driver #1)\r\ntuner 2-0061: chip found @ 0xc2 (ivtv i2c driver #1)\r\ncx25840 2-0044: cx25843-23 found @ 0x88 (ivtv i2c driver #1)\r\nwm8775 2-001b: chip found @ 0x36 (ivtv i2c driver #1)\r\nivtv1: Registered device video1 for encoder MPEG (4 MB)\r\nivtv1: Registered device video33 for encoder YUV (2 MB)\r\nivtv1: Registered device vbi1 for encoder VBI (1 MB)\r\nivtv1: Registered device video25 for encoder PCM audio (1 MB)\r\nivtv1: Initialized Hauppauge WinTV PVR-150, card #1\r\nivtv: ==================== END INIT IVTV ====================\r\n<\/pre>\n\n
- Check the output of the dmesg command. Sometimes a reboot is needed.\n\t<\/li>\n<\/ul>\n
\nWhen you are using kernel 2.6.21 and higher ivtv and mantis will
\nnog work together. Depening on which module loads first the mantis
\nmodule will freeze.<\/strong>\n<\/p>\n\nTo resolve this problem you will have to add extra module parameters to the saa7115 module.
\nDo the following to determine the values for the module parameters:\n<\/p>\n\n
- Get i2c bus number used by the Mantis driver.\n\t<\/li>\n<\/ul>\n
\r\n#> modprobe i2c-dev\r\n#> i2cdetect -l\r\ni2c-3 i2c ivtv i2c driver #1 I2C adapter\r\ni2c-2 i2c ivtv i2c driver #0 I2C adapter\r\ni2c-1 smbus Mantis I2C SMBus adapter\r\ni2c-0 smbus SMBus I801 adapter at 0400 SMBus adapter\r\n<\/pre>\n\n
- The i2c bus used by the Mantis driver is bus 1 (see i2c-1 part) in this example.\n\t<\/li>\n
- Add the following line to your \/etc\/modprobe.conf\n\t<\/li>\n<\/ul>\n
\r\noptions saa7115 ignore=1,0x25,1,0x24,1,0x21,1,0x20\r\n<\/pre>\n\n
- Replace all the 1’s (one’s) with your i2c bus number leave the hexadecimal numbers intact.\n\t<\/li>\n
- Now reboot your machine and both the mantis and the ivtv modules should load without a problem and work without a problem.\n\t<\/li>\n<\/ul>\n<\/div>\n","protected":false},"excerpt":{"rendered":"
\nThis is from www.verbraak.org\/wiki\/index.php\/Linux_Mantis_driver but his site seems to be down a lot so I have mirrored it here because I am trying to get my 1034 card to work with Linux.\n<\/p>\n
\n \n<\/p>\n
Linux Mantis driver<\/h1>\n
\nFrom My Interesting Version<\/h3>\n
\nJump to: navigation<\/a>, search<\/a>\n<\/div>\n<\/p>\n
\nCurrently the Mantis chipset driver for linux is in Alpha state.\n<\/p>\n
\nThis Mantis chipset is used on DVB board for reception of DVB-T, DVB-S, DVB-S2, DVB-C signals.\n<\/p>\n
\nIn this small Howto i explain how I got the mantis driver up and
\nrunning in my vanilla linux kernel.
\nI had to do it in this way because I also own two Hauppauge PVR cards
\n(PVR-350 and PVR-150) which do not work well with the mantis module.\n<\/p>\n\nThis example has been tested with linux kernel source 2.6.22
\nand the ivtv driver from the linuxtv.org hg reposititory and the one
\nincluded in the kernel on a Fedora Core 6 setup.\n<\/p>\n\r\nWARNING:<\/strong> IVTV 0.10.3 and Mantis and kernel 2.6.21 and up do not work together.\r\nFrom kernel 2.6.22 the ivtv module is part of the kernel and you do not need to download it from the ivtvdriver.org website.\r\nTo get ivtv and the mantis working in kernel 2.6.21 and up you need to add extra<\/strong> module parameters to the saa7115<\/em> module. \r\nSee the instructions at the end for this.\r\n<\/pre>\n<\/a><\/p>\n
[edit<\/a>]<\/span> Following steps you need to take (short<\/strong> ways for kernel 2.6.23.1):<\/span><\/h3>\n
\n
- Download the patch file<\/a> for kernel 2.6.23.1.\n\t<\/li>\n
- use your current kernel or take a kernel source tree from http:\/\/www.kernel.org<\/a>. Make sure you have the kernel headers\/sources files\/packages installed and you have the kernel up and running.\n\t<\/li>\n
- Apply the patch.\n\t<\/li>\n<\/ul>\n
\r\n#> cd <path to kernel source>\r\n#> patch -p1 < <path to mantis-2.6.23.1.patch file>\/mantis-2.6.23.1.patch\r\n<\/pre>\n\n
- Activate the mantis modules in your kernel config. Answer yes to the Mantis parts.\n\t<\/li>\n<\/ul>\n
\r\n#> make oldconfig\r\n<\/pre>\n\n
- Compile.\n\t<\/li>\n<\/ul>\n
\r\n#> make\r\n#> make modules_install\r\n<\/pre>\n\n
- When you use your current kernel sources do load the modules\n\t<\/li>\n<\/ul>\n
\r\n#> modprobe mantis\r\n#> dmesg | grep -i dvb\r\nfound a VP-1034 PCI DVB-S\/DSS device on (02:05.0),\r\nDVB: registering new adapter (Mantis dvb adapter).\r\nmantis_frontend_init (0): Probing for MB86A16 (DVB-S\/DSS)\r\nmantis_frontend_init (0): found MB86A16 DVB-S\/DSS frontend @0x08\r\nDVB: registering frontend 0 (Fujitsu MB86A16 DVB-S)...\r\n<\/pre>\n<\/a><\/p>\n
[edit<\/a>]<\/span> Following steps you need to take (long<\/strong> way for kernels 2.6.21 and up):<\/span><\/h3>\n
\n
- use your current kernel or take a kernel source tree from http:\/\/www.kernel.org<\/a>. Make sure you have the kernel headers\/sources files\/packages installed and you have the kernel up and running.\n\t<\/li>\n
- Get the mantis dvb source tree from http:\/\/jusst.de\/hg\/mantis\/archive\/tip.tar.bz2<\/a>\n\t<\/li>\n
- Copy the directory <path to mantis
\n\ttree>\/linux\/drivers\/media\/dvb\/mantis to <path to kernel
\n\tsource>\/drivers\/media\/dvb\/\n\t<\/li>\n- Add the following three lines to the file <path to kernel
\n\tsource>\/drivers\/media\/dvb\/Kconfig. Add them before the last entry in
\n\tthis file.\n\t<\/li>\n<\/ul>\n\r\ncomment "Supported Mantis Adapters"\r\ndepends on DVB_CORE && PCI && I2C\r\nsource "drivers\/media\/dvb\/mantis\/Kconfig"\r\n<\/pre>\n\n
- Add the following option "mantis\/<\/strong>" to the file path to kernel source>\/drivers\/media\/dvb\/Makefile. It should look like this\n\t<\/li>\n<\/ul>\n
\r\n#\r\n# Makefile for the kernel multimedia device drivers.\r\n# \r\nobj-y \u00a0:= dvb-core\/ frontends\/ ttpci\/ ttusb-dec\/ ttusb-budget\/ b2c2\/ bt8xx\/ cinergyT2\/ dvb-usb\/ pluto2\/ mantis\/\r\n<\/pre>\n\n
- Copy the files <path to mantis
\n\ttree>\/linux\/drivers\/media\/dvb\/frontends\/mb86a16* to <path to
\n\tkernel source>\/drivers\/media\/dvb\/frontends\n\t<\/li>\n- Copy the files <path to mantis
\n\ttree>\/linux\/drivers\/media\/dvb\/frontends\/cu1216* to <path to
\n\tkernel source>\/drivers\/media\/dvb\/frontends\n\t<\/li>\n- Add the following lines to the file <path to kernel source>\/drivers\/media\/dvb\/frontends\/Kconfig just after the config DVB_TDA10086<\/strong>\n\t<\/li>\n<\/ul>\n
\r\nconfig DVB_MB86A16\r\ntristate "Fujitsu MB86A16 based"\r\ndepends on DVB_CORE && I2C\r\ndefault m\r\nhelp\r\nA DVB-S\/DSS tuner module. Say Y when you want to support this frontend.\r\nconfig DVB_CU1216\r\ntristate "Philips CU1216 tuner based"\r\ndepends on DVB_CORE && I2C\r\ndefault m\r\nhelp\r\nA DVB-C tuner module. Say Y when you want to support this frontend.\r\n<\/pre>\n\n
- Add the following two lines to the file <path to kernel source>\/drivers\/media\/dvb\/frontends\/Makefile\n\t<\/li>\n<\/ul>\n
\r\nobj-$(CONFIG_DVB_MB86A16) += mb86a16.o\r\nobj-$(CONFIG_DVB_CU1216) += cu1216.o\r\n<\/pre>\n\n
- Change in the file <path to kernel
\n\tsource>\/drivers\/media\/dvb\/frontends\/cu1216.c line 37 to look like
\n\tthis (ignore the line numbers)\n\t<\/li>\n<\/ul>\n\r\n 34 #include <linux\/slab.h>\r\n35 \r\n36 #include "dvb_frontend.h"\r\n37 #include "..\/mantis\/mantis_core.h"\r\n38 #include "cu1216.h"\r\n39 #include "cu1216_regs.h"\r\n<\/pre>\n\n
- You can now compile your kernel in the normal way and install
\n\tthe modules. If you wish to make sure the Mantis modules have been
\n\tselected do a make menuconfig<\/em>\n\t<\/li>\n<\/ul>\n\r\n#> cd <path to kernelsource>\r\n#> make menuconfig\r\n#> make\r\n#> make modules_install\r\n<\/pre>\n\n
- When you use your current kernel sources do load the modules\n\t<\/li>\n<\/ul>\n
\r\n#> modprobe mantis\r\n#> dmesg | grep -i dvb\r\nfound a VP-1034 PCI DVB-S\/DSS device on (02:05.0),\r\nDVB: registering new adapter (Mantis dvb adapter).\r\nmantis_frontend_init (0): Probing for MB86A16 (DVB-S\/DSS)\r\nmantis_frontend_init (0): found MB86A16 DVB-S\/DSS frontend @0x08\r\nDVB: registering frontend 0 (Fujitsu MB86A16 DVB-S)...\r\n<\/pre>\n\n
- Check the output of the dmesg command to see if the mantis modules loaded. Sometimes a reboot of the system is needed.\n\t<\/li>\n
- IMPORTANT:<\/strong> For kernels 2.6.21 and below the order in which you do the installations is also important. Every time you perform a make modules_install<\/strong> for the kernel you need to do the make install<\/strong> for the ivtv driver as well.\n\t<\/li>\n<\/ul>\n
\n
\nTo get the Hauppauge cards working do the following:\n<\/p>\n\n
- The ivtv module is now part of the kernel since 2.6.22. So
\n\tcheck your kernel. If you have a kernel below 2.6.22 then do the
\n\tfollowing <\/li>\n- Get the ivtv source from http:\/\/dl.ivtvdriver.org\/ivtv\/archive\/0.10.x\/ivtv-0.10.5.tar.gz<\/a>. See http:\/\/www.ivtvdriver.org<\/a> for latest version.\n\t<\/li>\n
- Extract the source, build and install it.\n\t<\/li>\n<\/ul>\n
\r\n#> tar -zxvpf ivtv-0.10.5.tar.gz\r\n#> cd ivtv-0.10.5\r\n#> make; make install\r\n<\/pre>\n\n
- Install the ivtv firmware<\/a> files in \/lib\/firmware\n\t<\/li>\n<\/ul>\n
\r\n#> cd \/lib\/firmware\r\n#> wget http:\/\/dl.ivtvdriver.org\/ivtv\/firmware\/firmware.tar.gz<\/a>\r\n#> tar -zxvpf firmware.tar.gz\r\n<\/pre>\n\n
- Load the ivtv modules:\n\t<\/li>\n<\/ul>\n
\r\n#> modprobe ivtv\r\n#> dmesg | grep -i ivtv\r\nivtv: ==================== START INIT IVTV ====================\r\nivtv: version 0.10.3 (development snapshot compiled on zo 20 mei 2007 08:57:55 CEST) loading\r\nivtv: Linux version: 2.6.21.1 SMP mod_unload PENTIUM4 4KSTACKS \r\nivtv: In case of problems please include the debug info between\r\nivtv: the START INIT IVTV and END INIT IVTV lines, along with\r\nivtv: any module options, when mailing the ivtv-users mailinglist.\r\nivtv0: Autodetected Hauppauge card (cx23415 based)\r\nivtv0: loaded v4l-cx2341x-enc.fw firmware (376836 bytes)\r\nivtv0: loaded v4l-cx2341x-dec.fw firmware (262144 bytes)\r\nivtv0: Encoder revision: 0x02060039\r\nivtv0: Decoder revision: 0x02020023\r\nivtv0: Autodetected Hauppauge WinTV PVR-350\r\ntuner 1-0061: chip found @ 0xc2 (ivtv i2c driver #0)\r\nsaa7115 1-0021: saa7115 found (1f7115d0e100000) @ 0x42 (ivtv i2c driver #0)\r\nsaa7127 1-0044: saa7127 found @ 0x88 (ivtv i2c driver #0)\r\nmsp3400 1-0040: MSP4418G-A2 found @ 0x80 (ivtv i2c driver #0)\r\nivtv0: Registered device video0 for encoder MPEG (4 MB)\r\nivtv0: Registered device video32 for encoder YUV (2 MB)\r\nivtv0: Registered device vbi0 for encoder VBI (1 MB)\r\nivtv0: Registered device video24 for encoder PCM audio (1 MB)\r\nivtv0: Registered device radio0 for encoder radio\r\nivtv0: Registered device video16 for decoder MPEG (1 MB)\r\nivtv0: Registered device vbi8 for decoder VBI (1 MB)\r\nivtv0: Registered device vbi16 for decoder VOUT\r\nivtv0: Registered device video48 for decoder YUV (1 MB)\r\nivtv0: loaded v4l-cx2341x-init.mpg firmware (155648 bytes)\r\nivtv0: Initialized Hauppauge WinTV PVR-350, card #0\r\nivtv: ====================== NEXT CARD ======================\r\nivtv1: Autodetected Hauppauge card (cx23416 based)\r\nivtv1: loaded v4l-cx2341x-enc.fw firmware (376836 bytes)\r\nivtv1: Encoder revision: 0x02060039\r\ntuner 2-0043: chip found @ 0x86 (ivtv i2c driver #1)\r\ntuner 2-0061: chip found @ 0xc2 (ivtv i2c driver #1)\r\nivtv1: Autodetected Hauppauge WinTV PVR-150\r\nivtv1: reopen i2c bus for IR-blaster support\r\ntuner 2-0043: chip found @ 0x86 (ivtv i2c driver #1)\r\ntuner 2-0061: chip found @ 0xc2 (ivtv i2c driver #1)\r\ncx25840 2-0044: cx25843-23 found @ 0x88 (ivtv i2c driver #1)\r\nwm8775 2-001b: chip found @ 0x36 (ivtv i2c driver #1)\r\nivtv1: Registered device video1 for encoder MPEG (4 MB)\r\nivtv1: Registered device video33 for encoder YUV (2 MB)\r\nivtv1: Registered device vbi1 for encoder VBI (1 MB)\r\nivtv1: Registered device video25 for encoder PCM audio (1 MB)\r\nivtv1: Initialized Hauppauge WinTV PVR-150, card #1\r\nivtv: ==================== END INIT IVTV ====================\r\n<\/pre>\n\n
- Check the output of the dmesg command. Sometimes a reboot is needed.\n\t<\/li>\n<\/ul>\n
\nWhen you are using kernel 2.6.21 and higher ivtv and mantis will
\nnog work together. Depening on which module loads first the mantis
\nmodule will freeze.<\/strong>\n<\/p>\n\nTo resolve this problem you will have to add extra module parameters to the saa7115 module.
\nDo the following to determine the values for the module parameters:\n<\/p>\n\n
- Get i2c bus number used by the Mantis driver.\n\t<\/li>\n<\/ul>\n
\r\n#> modprobe i2c-dev\r\n#> i2cdetect -l\r\ni2c-3 i2c ivtv i2c driver #1 I2C adapter\r\ni2c-2 i2c ivtv i2c driver #0 I2C adapter\r\ni2c-1 smbus Mantis I2C SMBus adapter\r\ni2c-0 smbus SMBus I801 adapter at 0400 SMBus adapter\r\n<\/pre>\n\n
- The i2c bus used by the Mantis driver is bus 1 (see i2c-1 part) in this example.\n\t<\/li>\n
- Add the following line to your \/etc\/modprobe.conf\n\t<\/li>\n<\/ul>\n
\r\noptions saa7115 ignore=1,0x25,1,0x24,1,0x21,1,0x20\r\n<\/pre>\n\n
- Replace all the 1’s (one’s) with your i2c bus number leave the hexadecimal numbers intact.\n\t<\/li>\n
- Now reboot your machine and both the mantis and the ivtv modules should load without a problem and work without a problem.\n\t<\/li>\n<\/ul>\n<\/div>\n