Hi Thomas, > just a question, i've checked out the sources and builded them, but i've > still no success. > > in my dmesg there's some lines like > Nov 22 13:56:22 atlantis kernel: [17180322.812000] uvcvideo: disagrees > about version of symbol video_devdata > > Nov 22 13:56:22 atlantis kernel: [17180322.812000] uvcvideo: Unknown > symbol video_devdata > > Nov 22 13:56:22 atlantis kernel: [17180322.812000] uvcvideo: disagrees > about version of symbol video_unregister_device > > Nov 22 13:56:22 atlantis kernel: [17180322.812000] uvcvideo: Unknown > symbol video_unregister_device > > Nov 22 13:56:22 atlantis kernel: [17180322.812000] uvcvideo: disagrees > about version of symbol video_device_alloc > > Nov 22 13:56:22 atlantis kernel: [17180322.812000] uvcvideo: Unknown > symbol video_device_alloc > > Nov 22 13:56:22 atlantis kernel: [17180322.812000] uvcvideo: disagrees > about version of symbol video_register_device > > Nov 22 13:56:22 atlantis kernel: [17180322.812000] uvcvideo: Unknown > symbol video_register_device > > Nov 22 13:56:22 atlantis kernel: [17180322.812000] uvcvideo: disagrees > about version of symbol video_device_release > > Nov 22 13:56:22 atlantis kernel: [17180322.812000] uvcvideo: Unknown > symbol video_device_release > > I also use a Hauppauge WinTVGo2 with the actuall dvb-tree sources, could > this be the problem?
Ah yes it probably is. The messages in the kernel log seems to indicate that the module has been linked against a different kernel tree that the one your are running. Cheers, Laurent Pinchart _______________________________________________ Linux-uvc-devel mailing list [email protected] https://lists.berlios.de/mailman/listinfo/linux-uvc-devel
