Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
lucview. That's mildly interesting and verifies a few things.
gspca module. How does lucview do it? Otherwise I would expect some camera module.
Libraries: Probably no libs in /usr/lib64 is a problem, and you will know if everything else has their libs there. I should explain
/begin history lesson
On the making of 64-bit distros, most people left 32 bit libs in /usr/lib for compatability with existing software, and put 64-bit ones in/usr/lib64#
Somebody, (Debian, afaik) felt that 'native' libs should go in /usr/lib (64-bit in the case of a 64 bit system) and invented /usr/lib32 for 32 bit libs. A 64 bit system usually needs some of both.
/end history lesson
Try
file /usr/lib/vl412.*
file /usr/lib32/vl412.*
Watch for 32 bit or 64 bit. Then try 'ls /usr/lib64' & 'ls /usr/lib32'
ONE of those will have very few libs, and they are misplaced. If you have Debian, it will be /usr/lib64. Otherwise, /usr/lib32 are the orphans. They will have to go to/usr/lib, and the equivelants in /usr/lib to /usr/lib64. Then run ldconfig.
It wasn't your directory structure I was worried about.
Your library search path would not have /usr/lib32 and /usr/lib64. That's the issue
One of them is wrong. either that or add them both to /etc/ld.so,conf & run ldconfig
ERROR: ld.so: object '/usr/lib32/libv4l/v4l1compat.so' from LD_PRELOAD cannot be preloaded: ignored.
Well it has told you what's wrong, so we don't have to.
Check /usr/lib32/libv4l/v4l1compat.so. run
ls /usr/lib32/libv4l/ (should show files)
ldconfig ( should show nothing but is a good idea)
ldd /usr/lib32/libv4l/v4l1compat.so and look for things not found
is the one in red the errorenous part? do i do a ln -s?
Beware that the standard layout of libs is as follows
libGL.so => a symlink to libGL.so.1
libGL.so.1 => a symlink to libGL.so.1.2
libGL.so.1.2 => The actual lib
so the real test is to check
ls -l /usr/lib32/libv4l/v4l1compat.*, and make sure one of them pointed to by the symlinks is an actual lib.
Also confusion is possible with 32/64 bit issues. If you have a 64 bit executable, ldd might point to a 32 bit lib cheerfully enough, but it will barf if you run it. (NOT FOUND errors). Run file on things to check that.
ls -l /usr/lib32/libv4l/v4l1compat.*
-rw-r--r-- 1 root root 5408 2009-07-21 00:33 /usr/lib32/libv4l/v4l1compat.so
i think 64 bit is not an issue cause i remember readin in ubuntu forums that v4l2 works only for 32 bit..the person under query was using 64bit distro
I would expect it to be 32 bit in /usr/lib32. Is there another in /usr/lib, or /usr/lib64?
That should work IF AND ONLY IF everything in the chain is 32 bit
e.g. 32 bit browser-->32bit webcam executable using 32 bit library
check with file
file /usr/lib32/libv4l/v4l1compat.so
will show you 32 bit. Check the others.
Elabhorate. Whhat have you checked? What can you say for certain? Whatt errors show? etc. You have the info in front of you - you have to tell us.
Have you Skype? That's 32 bit. There is a test mode for the video cam. You don't need lib4l to see yourself in that. I've been through this, and you can compile libv4l as 32 bit or 64 bit.
Last edited by business_kid; 02-15-2010 at 03:02 AM.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.