[linux-dvb] Mercurial builds causing unknown symbols in cam drivers?

Markus Rechberger mrechberger at gmail.com
Mon Aug 13 05:30:03 CEST 2007


On 8/13/07, Dave Richards <dave at slavesoftware.co.uk> wrote:
> Hi.
>
> I have a Hauppage WintvNova-T USB 2 stick that I use the recent
> Mercurial drop of v4l-dvb to fix the DiB0700 I2C read fails.
> The new drop of v4l-dvb and the new firmware works like a charm and a
> big thanks for all the work with that.
>
> Unfortunately this breaks my USB web cam (a Creative Logic Optia) that
> used the out of kernel Linux UVC driver.
> The result is dmesg showing unknown symbols when the cam is plugged in.
> Dmesg output follows at the bottom of this post.
>
> My understanding was that this is caused as the cam driver and dvb have
> effectively been compiled against a different kernel, dvb is being
> pulled from Mercurial and the cam driver was compiled against the stock
> source. I'm using Ubuntu Feisty 2.6.20-16-generic.
> I've run 'make kernel-links' from within the v4l-dvb source to update
> the kernel source and recompiled the UVC driver; Unfortunately this
> doesn't provide the fix I was hoping it would.
>
> I've looked back through some mailing list archives, this list and the
> UVC and video4linux archives. I can see there has been some debate about
> API changes that are planned and a move to video_ioctl2. From what I can
> see just quickly looking through the source pulled from Mercurial the
> parts of the API that the UVC driver still needs are still present so I
> don't believe that's the problem at the moment.
>
> I have asked on the UVC list and the suggestion was I post here.
>
> Any help greatfully recieved. Thanks for your time.
>
>
>
> [21400.572000] usb 5-4: new high speed USB device using ehci_hcd and
> address 9
> [21400.996000] usb 5-4: configuration #1 chosen from 1 choice
> [21401.048000] uvcvideo: disagrees about version of symbol video_devdata
> [21401.048000] uvcvideo: Unknown symbol video_devdata
> [21401.048000] uvcvideo: disagrees about version of symbol
> video_unregister_device
> [21401.048000] uvcvideo: Unknown symbol video_unregister_device
> [21401.048000] uvcvideo: disagrees about version of symbol
> video_device_alloc
> [21401.048000] uvcvideo: Unknown symbol video_device_alloc
> [21401.048000] uvcvideo: disagrees about version of symbol
> video_register_device
> [21401.048000] uvcvideo: Unknown symbol video_register_device
> [21401.048000] uvcvideo: disagrees about version of symbol
> video_device_release
> [21401.048000] uvcvideo: Unknown symbol video_device_release
> [21401.052000] uvcvideo: disagrees about version of symbol video_devdata
> [21401.052000] uvcvideo: Unknown symbol video_devdata
> [21401.052000] uvcvideo: disagrees about version of symbol
> video_unregister_device
> [21401.052000] uvcvideo: Unknown symbol video_unregister_device
> [21401.052000] uvcvideo: disagrees about version of symbol
> video_device_alloc
> [21401.052000] uvcvideo: Unknown symbol video_device_alloc
> [21401.052000] uvcvideo: disagrees about version of symbol
> video_register_device
> [21401.052000] uvcvideo: Unknown symbol video_register_device
> [21401.052000] uvcvideo: disagrees about version of symbol
> video_device_release
> [21401.052000] uvcvideo: Unknown symbol video_device_release
>
>
>

Hi Dave,

you have to run "make kernel-links", this will update your kernel
sourcetree with the latest v4l-dvb sources.
After this if you rebuild your camdrivers they will use the latest
sources and everything should work out fine. You cannot mix cam
drivers which are build with older v4l-dvb inkernelsources with the
latest v4l-dvb sources from linuxtv.org.

Markus



More information about the linux-dvb mailing list