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.
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
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.