Hi Juho, On Monday 17 November 2008, Juho Vähä-Herttua wrote: > Laurent Pinchart wrote: > > I sense some bitterness here ;-) I'll try to help you (please remember > > I'm quite new to v4l trees as well, so this might require a few > > iterations). > > Damn, I tried to hide it since I'm not really entitled to, but it seems > I failed. :p > > > The most usual source of dependency errors when installing v4l from > > sources is old modules lying around in /lib/modules/`uname -r`/. Could > > you try to manually move them out of the way ? If I remember well Ubuntu > > installs in-tree modules in /lib/modules/`uname -r`/kernel and > > out-of-tree modules in /lib/modules/`uname -r`/ubuntu, so make sure you > > look into both locations for v4l modules. > > Yes, I think this probably had something to do with the modprobe > failing, I should try to hunt down all outdated versions. > > > You could also try to load the new modules with insmod. You will have to > > resolve dependencies yourself (i.e. load the modules in the correct > > order), but you will be able to make sure the new modules are loaded and > > not some old ones lying around in a corner. This might give you some > > interesting hints. > > In fact, what I tried to do first, was to remove all v4l related modules > and start to insmod them one by one. Now that I tried again, I think it > was my fault (naturally) and I think I had wrong version of > v4l1_compat.ko loaded. It's a bit funny that videodev.ko depends on > v4l1_compat.ko, but that's another issue. > > Just for documentation if someone else has similar problems, the correct > order to load modules is: > > insmod v4l1-compat.ko > insmod videodev.ko > insmod v4l2-compat-ioctl32.ko > insmod uvcvideo.ko
Thanks for the tip. > And apparently the v4l2_common.ko I mentioned before is not used at > all... I'm not sure if the ioctl32 compat is required because I'm > running on x86-64, but anyway at least I needed it. > > Thank you again a lot for your help, I hope this information is helpful > for someone, at least now I know the dependencies. Stupid mistake in the > beginning again, but I had just missed the v4l1 when grepping for v4l2... You're welcome. I'm glad you fixed your problem, as I'm still a bit worried that the move to Mercurial might not be easy for some users. Best regards, Laurent Pinchart _______________________________________________ Linux-uvc-devel mailing list [email protected] https://lists.berlios.de/mailman/listinfo/linux-uvc-devel
