I'm curious what is the device id?
post the output of lsusb
WEBCAM USB(64 posts) (10 voices)
@gibor, it is
Bus 004 Device 002: ID 046d:08b2 Logitech, Inc. QuickCam Pro 4000
EDIT: tried it on another machine, Dell Optiplex GLX260 running Slitaz 4.0 with a Radeon card and the result is even uglier. The moment I run fswebcam or mplayer the entire system crashes with kernel error messages which is almost the same I used to get on my Dimension 9150 (it did not crash though). Unfortunately, short of writing down half a screen of error messages by hand there is no way to capture it.
Thank for the reply, I think the way forward could be this.
If you try to recompile the kernel modules with the parameters described here that I look good
or read this for more information
good luck :)
@gdesilva yes I'm afraid I'm at a loss... especially with no camera to do testing.
A few small things... these alternative methods of launching mplayer appear frequently and may be worth trying (now and when your webcam problem is resolved):
LD_PRELOAD=/usr/lib/libv4l/v4l1compat.so mplayer tv:// -tv driver=v4l:device=/dev/video0
LD_PRELOAD=/usr/lib/libv4l/v4l2convert.so mplayer tv:// -tv driver=v4l2:device=/dev/video0
The libv4l package adds "export LD_PRELOAD=/usr/lib/libv4l/v4l1compat.so" to /etc/profile, so the LD_PRELOAD might be redundant in the first method (above).
Perhaps fswebcam needs v4l2convert.so preloaded too?
Good luck gdesilva and gibor. Please report back good or bad results for the benefit of others following the topic.
Hey my friends,
I build the kernel from scratch with support to many webcams and worked for me.
1st) Just do this http://doc.slitaz.org/en:guides:kernel till # make menuconfig step.
2nd) In menuconfig check: Device Drivers > Multimedia Devices > Video Capture Adapters > V4L USB Devices (as told here: http://forums.gentoo.org/viewtopic-t-826370-highlight-quickcam+4000.html ) and create the .config file.
3rd) Continue http://doc.slitaz.org/en:guides:kernel steps...
# make modules
# make modules_install
4th) Point grub's menu.lst to your brandnew kernel
5th) Reboot and select your new kernel.
After that plug the webcam, it'll work like a charm.
@t0n1 congrats on getting your webcam(s) working.
To document things for the benefit of other people who end up here, can you please provide some more details like these:
- what make/model of webcams are you using successfully?
- what driver do they use (pwc, uvcvideo, etc)?
- before compiling your new kernel, did you try gibor's media-001.tazpkg or the v4l-dvb-development_2.6.37.tazpkg?
- what applications are you successfully using your webcams in (and are they from tazpkgs)?
Those details will help answer current/future questions and may help narrow down the problem some people are experiencing.
Also, you mention in another topic that you were getting a segfault after doing modprobe uvcvideo for your webcam. If this is no longer the case, can you please update that topic too.
Thanks again for helping.
I used some chinese cameras like 0ac8:3420 (Venus USB 2.0 Camera) , 090c:037b (Feiya Technology Corp.) , and others. You can figured out these cheap cameras here: http://www.dealextreme.com/p/usb-pc-webcam-300k-pixel-with-6-led-13?item=4 and in others sites like eBay, FocalPrice and AliExpress.
They use many diferent modules like you said, but mainly: uvcvideo, pwc and linux-video
Before I compiled the kernel I've already tested everything that I found in internet: gibor's media-001, v4l-dev, another 5 tips/tricks, and no success. I'm using Slitaz 4.0 version with no big modifications, I just installed from repositories and configured Firefox, X11VNC, Skype and enabled the SSH via dropbear.
I'm using successfully: zbarcam (an app to read barcodes), fswebcam (simple webcam viewer), motion (security cam app, like a dvr) and skype.
- - -
!!! I AM NOT RESPONSIBLE FOR ANY INJURY OR DAMAGE TO YOUR OR TO ANY OTHER PERSON'S COMPUTER RELATED TO OR RESULTING FROM PARTICIPATING OR DOWNLOADING CONTENT OR MATERIALS FROM OR IN CONNECTION WITH THE FOLLING PROCEADURE OR ANY LINKS TO OTHER WEBSITES CONTAINED THEREIN. IT'S YOUR OWN RISK. AND I'LL NOT GIVE SUPPORT TO YOUR PROBLEMS :P !!!
As I told before, I did exactly what they said here http://doc.slitaz.org/en:guides:kernel and http://forums.gentoo.org/viewtopic-t-826370-highlight-quickcam+4000.html , but for didactic purposes, I'll detail everything here (sorry moderators about my long text):
1) I installed Slitaz 4.0 (congrats, great distro!) into my dev PC (ASUS P5G41T-M LX2/BR Motherboard, Intel E3500 3GHz 750BGA CPU, Kingston 1GB DDR3 RAM, Old Seagate 80GB SATA HDD on sda, Samsung External DVD USB Drive). I was using a SSD/DOM with 1GB but it didn't support enought space to compile the kernel.
- put the CD Image into DVD Drive and run the slitaz, select the keyboard, and language.
- format the HD in ext3 with Gparted
- open the terminal with Sakura and install with tazinst [ http://hg.slitaz.org/slitaz-tools/raw-file/b57a0839c0d4/doc/tazinst.en.html ] typing (as you can see, do it as root--> # ):
# tazinst new tazconfig
# nano tazconfig
- find and replace the instalation target with your hdd partition, in my case, /dev/sda1
- select to install grub
- Ctrl+X and Yes to quit and save everything
# tazinst tazconfig
- wait to format (again), install everything...
2) Mount the hd, change grub and boot stuffs
# mkdir /mnt/target
# mount /dev/sda1 /mnt/target
# nano /mnt/target/boot/grub/menu.lst
- check if the target is right, in my case it was wrong (/dev/hda1)... changed to /dev/sda1
- change timeout to 0s (I hate to wait...)
# nano /mnt/target/etc/rcS.conf
- add dropbear to daemons (in the EOF)
# cd / && umount /mnt/target
3) After reboot, install with TazPanel : Firefox, X11VNC, and whatever you want...
4) I proceadure from here with ssh, but you can use the Sakura as well, after configure IP (172.16.0.1), Gateway, DNS, etc.. I conected with my notebook(172.16.0.2):
# ssh firstname.lastname@example.org
- password is tux
- password is root
And now as root under devpc I follow http://doc.slitaz.org/en:guides:kernel steps... so:
5) Building the compilation enviroment under devpc:
# tazpkg get-install slitaz-toolchain
# tazpkg get-install ncurses-dev
# tazpkg get-install perl
# tazpkg get-install linux-source
# cd /usr/src/linux
# make oldconfig && make prepare
# make menuconfig
6) Now pay attention, I followed what this guy (MotivatedTea) said http://forums.gentoo.org/viewtopic-t-826370-highlight-quickcam+4000.html and figured out the place that modules and other webcam stuff was ( is the shortcut letter for this option under menuconfig):
Device Drivers [D] > Multimedia Support [u] > Video Capture Adapters [V] > and select with SPACEBAR everything till change to <M> or [*]
select EXIT on the bottom of the screen, and return to main menu and select: Save an Alternate Configuration File , give a name to the file or leave the default name... this will be the name of conf file to make prg work to us ;)
7) Now, back to terminal screen, type the greatest commands ever seen:
# make modules
# make modules_install
8) Copy the file created and change grub stuff
# cp arch/x86/boot/bzImage /boot
# nano /boot/grub/menu.lst
- include a line with the new kernel: kernel /boot/bzImage root=/dev/sda1
- save and exit
9) Reboot and select the new grub option ;)
My terrible english you can try to understand but wrong commands will not work. So...
# tazinst tazconfig
# tazinst install tazconfig
Followed t0n1's procedure and the good news is that I now have a working Logitech camera!
I did a new installation, did the tazpanel upgrades (about 6 packages), then installed the nVidia non-free driver. Straight after this, I did the kernel reconfiguration outlined by t0n1 above.
The make process did throw up some warnings and so did the make modules_install. Copied bzImage and rebooted.
However, when booted, slim failed with unable to load nVidia message.
Logged back in again and re-installed nVidia and rebooted with the camera plugged in. Installed vlc and pointed to /dev/video0 as the capture device and lo and behold the camera came alive. No errors reported in /var/log/messages.
I guess the only hickup was crashing of nVidia which required re-installation of the nVidia driver something others may want to watch out for.
Many many thanks to t0n1 and to pipein - great to have your support, you guys rock!
Well I have given the right idea and someone has made good use, better that way, I pretended not sure that I will nominate.
For sure! You gibor and other guys did it all! I just tested and typed ;-)
In advance, tks to you my friend and many others gurus here in Stz Forum!
@gibor - I ditto t0n1's comment above - thanks for your suggestion.
Pardon me for my ignorance, but I am just curious to know why kernel reconfiguration is necessary? Why was it possible to insert pwc module in the first place if the original kernel was unaware of devices requiring pwc? In my case, pwc got loaded automatically although the kernel was spitting out error messages. Would appreciate if someone can shed some light on this issue.
I think simply because they had the pwc module, and not having tried it generated errors.
Now that you've created by searching in / lib / module transfer to another PC in exactly the same folder, and then load it with prevent depmod -a and modprobe.
With this system I had created media001 but I had not enabled pwc.
@gibor, I was glad when I read your comment about porting the pwc module to other machines but came across some issues. Here is my setup....
I have a Slitaz 4 on /dev/hda1 (internal HDD) and another for testing purposes on an external USB HDD /dev/hdc3. I did the kernel reconfiguration on /dev/hdc3 and got the webcam working on that installation.
As per your comment above, renamed the existing pwc.ko.gz to orig-pwc.ko.gz and then I copied the newly created pwc.ko (on /dev/hdc3)file to /lib/modules/...../pwc directory on /dev/hda1. Booted off /dev/hda1 but pwc module is not loaded. Try to do a modprobe pwc but resulted in an 'incorrect format' message.
Ideally, it will be great if I do not have to do kernel reconfigurations on all my machines and it would be nice to be able to do what you have suggested above. Any ideas what I am doing wrong here?
Rename file is wrong, but tried another method very simple.
On installation on kernel rebuild, open terminal and then “tazpkg repack linux” close terminal and on this directory find new linux tazpkg, move on new installation and install from terminal then linux...tazpkg –forced at reboot select new kernel (above same name).
if you during repack problem with md5sum then upgrade md5sum from /var/lib/tazpkg/installed/linux.
You must log in to post.