From: Ken Smith <kens@kensnet.org>
To: linux-media@vger.kernel.org
Subject: Re: Compro VideoMate S350
Date: Thu, 17 Mar 2011 18:51:19 +0000 [thread overview]
Message-ID: <4D825827.6000104@kensnet.org> (raw)
In-Reply-To: <4D8104E7.70607@kensnet.org>
Ken Smith wrote:
>
> First post to this list, but not new to Linux.
>
> I'm trying to get a Compro VideoMate S350 card to work in a 32bit
> Centos 5.5 system that also has a Hauppauge WinTV-NOVA-T-500 that uses
> the dvb-usb-dib0700.ko kernel module as its driver. The Nova-T appears
> to be working.
>
> I've used the v4l source RPM from ATRPMS to build an RPM of the v4l
> package. The RPM I compiled/built is called
> video4linux-kmdl-2.6.18-194.32.1.el5.centos.plus-20090907-93.RHL5.i386.rpm
>
>
> The build runs fine without issue.
>
> When I try to load the driver for the Compro with
>
> modprobe -v saa7134 card=169
>
> I get
>
>
> insmod
> /lib/modules/2.6.18-194.32.1.el5.centos.plus/kernel/drivers/media/video/video-buf.ko
>
> WARNING: Error inserting video_buf
> (/lib/modules/2.6.18-194.32.1.el5.centos.plus/kernel/drivers/media/video/video-buf.ko):
> Invalid module format
> WARNING: Error inserting videobuf_dma_sg
> (/lib/modules/2.6.18-194.32.1.el5.centos.plus/updates/drivers/media/video/videobuf-dma-sg.ko):
> Unknown symbol in module, or unknown parameter (see dmesg)
> WARNING: Error inserting v4l1_compat
> (/lib/modules/2.6.18-194.32.1.el5.centos.plus/updates/drivers/media/video/v4l1-compat.ko):
> Unknown symbol in module, or unknown parameter (see dmesg)
> WARNING: Error inserting videodev
> (/lib/modules/2.6.18-194.32.1.el5.centos.plus/updates/drivers/media/video/videodev.ko):
> Unknown symbol in module, or unknown parameter (see dmesg)
> WARNING: Error inserting v4l2_common
> (/lib/modules/2.6.18-194.32.1.el5.centos.plus/updates/drivers/media/video/v4l2-common.ko):
> Unknown symbol in module, or unknown parameter (see dmesg)
> WARNING: Error inserting ir_common
> (/lib/modules/2.6.18-194.32.1.el5.centos.plus/updates/drivers/media/common/ir-common.ko):
> Unknown symbol in module, or unknown parameter (see dmesg)
> FATAL: Error inserting saa7134
> (/lib/modules/2.6.18-194.32.1.el5.centos.plus/updates/drivers/media/video/saa7134/saa7134.ko):
> Unknown symbol in module, or unknown parameter (see dmesg)
>
>
> The line referred to in /var/log/messages is
>
> kernel: video_buf: exports duplicate symbol videobuf_mmap_mapper
> (owned by videobuf_core)
>
> I know that the centos.plus distribution includes some (if not all of)
> the v4l modules, so I tried my build of v4l with the plain Centos
> kernel build. The Nova T also runs fine, but I still get the error
>
> insmod
> /lib/modules/2.6.18-194.32.1.el5/kernel/drivers/media/video/video-buf.ko
> WARNING: Error inserting video_buf
> (/lib/modules/2.6.18-194.32.1.el5/kernel/drivers/media/video/video-buf.ko):
> Invalid module format
>
> I'm sure I have missed something obvious, I'd appreciate any suggestions.
>
> Thanks
>
> Ken
>
>
Apologies - have I sent this to the wrong list. Is there a more
appropriate forum?
Thanks
Ken
>
>
>
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
prev parent reply other threads:[~2011-03-17 18:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-16 18:43 Compro VideoMate S350 Ken Smith
2011-03-17 18:51 ` Ken Smith [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4D825827.6000104@kensnet.org \
--to=kens@kensnet.org \
--cc=linux-media@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox