Re: Invalid module format

[Devin Heitmueller <dheitmueller@kernellabs.com>]

On Wed, Sep 9, 2009 at 2:34 PM, animatrix30@gmail.com
<animatrix30@gmail.com> wrote:
>
> I have this error, when I load the module :
> [ 2122.708062] em28xx: Unknown symbol v4l2_i2c_new_probed_subdev
> [ 2122.708402] em28xx: disagrees about version of symbol v4l2_i2c_subdev_addr
> [ 2122.708404] em28xx: Unknown symbol v4l2_i2c_subdev_addr
> [ 2122.708680] em28xx: disagrees about version of symbol video_devdata
> [ 2122.708682] em28xx: Unknown symbol video_devdata
> [ 2122.708889] em28xx: Unknown symbol v4l_bound_align_image
> [ 2122.709594] em28xx: disagrees about version of symbol video_unregister_device
> [ 2122.709597] em28xx: Unknown symbol video_unregister_device
> [ 2122.709810] em28xx: disagrees about version of symbol video_device_alloc
> [ 2122.709813] em28xx: Unknown symbol video_device_alloc
> [ 2122.709886] em28xx: disagrees about version of symbol v4l2_device_disconnect
> [ 2122.709888] em28xx: Unknown symbol v4l2_device_disconnect
> [ 2122.709982] em28xx: disagrees about version of symbol video_register_device
> [ 2122.709985] em28xx: Unknown symbol video_register_device
> [ 2122.710090] em28xx: disagrees about version of symbol v4l2_device_register
> [ 2122.710093] em28xx: Unknown symbol v4l2_device_register
> [ 2122.710416] em28xx: Unknown symbol ir_codes_evga_indtube
> [ 2122.711104] em28xx: disagrees about version of symbol v4l2_device_unregister
> [ 2122.711106] em28xx: Unknown symbol v4l2_device_unregister
> [ 2122.711332] em28xx: disagrees about version of symbol video_device_release
> [ 2122.711335] em28xx: Unknown symbol video_device_release
> [ 2122.711406] em28xx: disagrees about version of symbol v4l2_i2c_new_subdev
> [ 2122.711408] em28xx: Unknown symbol v4l2_i2c_new_subdev
>
> Is it because of my (wrong) configuration or your code (debug) ?
> Thanks !
>
> (It seems that the mailing list is not working )
<snip>

Please stop top posting.

Did you build mrec's driver from source?  Or are you using a binary
package?  If you built it from source, then your problem has to do
with his code not finding the proper headers.  If you are using his
binary package, then you need to understand that the binary package
only works with whatever kernel he built against.

Either way, this is a problem with your environment and not with the
v4l-dvb code.

I'm not really in a position to help you debug problems getting mrec's
driver to work.

Devin

--
Devin J. Heitmueller - Kernel Labs
http://www.kernellabs.com