Mailing List Archive: atrpms: users

Compro VideoMate S350

Index | Next | Previous | View Threaded

kens at kensnet

Mar 18, 2011, 8:50 AM

Post #1 of 5 (532 views)
Permalink

Compro VideoMate S350

Hi, I posted this is the Linux-Media list but has no reply there as yet
so please forgive the x post

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 RPM from ATRPMS

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 the package with the plain Centos kernel
build, as I read about module conflicts on various web pages and lists.
The Nova T 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

As far as I can tell video-buf.ko comes with the kernel RPM.

I'm sure I have missed something obvious, I'd appreciate any suggestions.

Thanks

Ken

--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

_______________________________________________
atrpms-users mailing list
atrpms-users [at] atrpms
http://lists.atrpms.net/mailman/listinfo/atrpms-users

J.Pilk at tesco

Mar 19, 2011, 12:57 PM

Post #2 of 5 (502 views)
Permalink

Re: Compro VideoMate S350 [In reply to]

On 18/03/11 15:50, Ken Smith wrote:
>
> Hi, I posted this is the Linux-Media list but has no reply there as yet
> so please forgive the x post
>
> 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 RPM from ATRPMS
>
> 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 the package with the plain Centos kernel
> build, as I read about module conflicts on various web pages and lists.
> The Nova T 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
>
This looks reminiscent of the longstanding module-init-tools problem:
you probably need to find an earlier version. It's been covered several
times in this list, most recently here:

http://www.gossamer-threads.com/lists/atrpms/users/15104#15104

I see the duplicate symbol message too but the system still works.

> As far as I can tell video-buf.ko comes with the kernel RPM.
>
> I'm sure I have missed something obvious, I'd appreciate any suggestions.
>
> Thanks
>
> Ken
>
>
>
>
>

_______________________________________________
atrpms-users mailing list
atrpms-users [at] atrpms
http://lists.atrpms.net/mailman/listinfo/atrpms-users

kens at kensnet

Mar 19, 2011, 4:21 PM

Post #3 of 5 (498 views)
Permalink

Re: Compro VideoMate S350 [In reply to]

John Pilkington wrote:
> On 18/03/11 15:50, Ken Smith wrote:
>>
>> {snip}
>>
>> 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.
>>

>> {snip}

>>
>> I know that the centos.plus distribution includes some (if not all of)
>> the v4l modules, so I tried the package with the plain Centos kernel
>> build, as I read about module conflicts on various web pages and lists.
>> The Nova T 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
>>
> This looks reminiscent of the longstanding module-init-tools problem:
> you probably need to find an earlier version. It's been covered
> several times in this list, most recently here:
>
> http://www.gossamer-threads.com/lists/atrpms/users/15104#15104
>
> I see the duplicate symbol message too but the system still works.
>
{snip}

Thanks for this info. I have been doing some digging and it appears that
both modules

/lib/modules/2.6.18-194.32.1.el5/kernel/drivers/media/video/video-buf.ko
and
/lib/modules/2.6.18-194.32.1.el5/updates/drivers/media/video/videobuf-core.ko

export the same symbol

nm
/lib/modules/2.6.18-194.32.1.el5/kernel/drivers/media/video/video-buf.ko
| grep videobuf_mmap_mapper
00000565 T videobuf_mmap_mapper

and

nm
/lib/modules/2.6.18-194.32.1.el5/updates/drivers/media/video/videobuf-core.ko
| grep videobuf_mmap_mapper
000002ac T videobuf_mmap_mapper

Which makes insmod puke

The former comes with the Kernel and the latter with V4L

I'll checkout your module-init-tools suggestion.

Thanks

Ken

--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

_______________________________________________
atrpms-users mailing list
atrpms-users [at] atrpms
http://lists.atrpms.net/mailman/listinfo/atrpms-users

J.Pilk at tesco

Mar 20, 2011, 1:38 PM

Post #4 of 5 (488 views)
Permalink

Re: Compro VideoMate S350 [In reply to]

On 19/03/11 23:21, Ken Smith wrote:
>
>
> John Pilkington wrote:
>> On 18/03/11 15:50, Ken Smith wrote:
>>>
>>> {snip}
>>>
>>> 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.
>>>
>
>>> {snip}
>
>>>
>>> I know that the centos.plus distribution includes some (if not all of)
>>> the v4l modules, so I tried the package with the plain Centos kernel
>>> build, as I read about module conflicts on various web pages and lists.
>>> The Nova T 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
>>>
>> This looks reminiscent of the longstanding module-init-tools problem:
>> you probably need to find an earlier version. It's been covered
>> several times in this list, most recently here:
>>
>> http://www.gossamer-threads.com/lists/atrpms/users/15104#15104
>>
>> I see the duplicate symbol message too but the system still works.
>>
> {snip}
>
> Thanks for this info. I have been doing some digging and it appears that
> both modules
>
> /lib/modules/2.6.18-194.32.1.el5/kernel/drivers/media/video/video-buf.ko
> and
> /lib/modules/2.6.18-194.32.1.el5/updates/drivers/media/video/videobuf-core.ko
>
>
>
> export the same symbol
>
> nm
> /lib/modules/2.6.18-194.32.1.el5/kernel/drivers/media/video/video-buf.ko
> | grep videobuf_mmap_mapper
> 00000565 T videobuf_mmap_mapper
>
> and
>
> nm
> /lib/modules/2.6.18-194.32.1.el5/updates/drivers/media/video/videobuf-core.ko
> | grep videobuf_mmap_mapper
> 000002ac T videobuf_mmap_mapper
>
> Which makes insmod puke
>
> The former comes with the Kernel and the latter with V4L
>
> I'll checkout your module-init-tools suggestion.
>
> Thanks
>
> Ken
>
I haven't experimented with my el5 box recently because the facilities I
have wanted to use have Just Worked with the older version of
module-init-tools, but before Paulo recommended that solution I was told
to rename the video-buf.ko module so that it wouldn't be loaded. ISTR
that that worked too, with 2.6.18-53.1.13, but of course the effect may
depend on the hardware involved, and the v4l/kernel relationship has
probably changed too.

John P

_______________________________________________
atrpms-users mailing list
atrpms-users [at] atrpms
http://lists.atrpms.net/mailman/listinfo/atrpms-users

Axel.Thimm at ATrpms

Apr 4, 2011, 10:58 AM

Post #5 of 5 (452 views)
Permalink

Re: Compro VideoMate S350 [In reply to]

On Sat, 2011-03-19 at 23:21 +0000, Ken Smith wrote:
> John Pilkington wrote:
> > On 18/03/11 15:50, Ken Smith wrote:
> >> 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.

> >> 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
> >>
> > This looks reminiscent of the longstanding module-init-tools problem:
> > you probably need to find an earlier version. It's been covered
> > several times in this list, most recently here:
> >
> > http://www.gossamer-threads.com/lists/atrpms/users/15104#15104
> >
> > I see the duplicate symbol message too but the system still works.

> Thanks for this info. I have been doing some digging and it appears that
> both modules
>
> /lib/modules/2.6.18-194.32.1.el5/kernel/drivers/media/video/video-buf.ko
> and
> /lib/modules/2.6.18-194.32.1.el5/updates/drivers/media/video/videobuf-core.ko
>
>
> export the same symbol
>
> nm
> /lib/modules/2.6.18-194.32.1.el5/kernel/drivers/media/video/video-buf.ko
> | grep videobuf_mmap_mapper
> 00000565 T videobuf_mmap_mapper
>
> and
>
> nm
> /lib/modules/2.6.18-194.32.1.el5/updates/drivers/media/video/videobuf-core.ko
> | grep videobuf_mmap_mapper
> 000002ac T videobuf_mmap_mapper
>
> Which makes insmod puke
>
> The former comes with the Kernel and the latter with V4L
>
> I'll checkout your module-init-tools suggestion.

module-init-tools is supposed to give priority to updates before the
built in ("kernel") modules. Some of the patches in RHEL5 broke this
setup. See also the contents of

/etc/depmod.d/depmod.conf*

Maybe it is worth filing a bugzilla against RHEL 5.6? It certainly isn't
the desired/intended behaviour the RHEL team was aiming at.
--
http://thimm.gr/ - http://ATrpms.net/

Attachments:

signature.asc (0.19 KB)

Index | Next | Previous | View Threaded

Interested in having your list archived? Contact Gossamer Threads