Problems installing Chicony USB 2.0 camera in Toshiba Laptop - Distro: Slackware 12
Linux - Laptop and NetbookHaving a problem installing or configuring Linux on your laptop? Need help running Linux on your netbook? This forum is for you. This forum is for any topics relating to Linux and either traditional laptops or netbooks (such as the Asus EEE PC, Everex CloudBook or MSI Wind).
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.
Problems installing Chicony USB 2.0 camera in Toshiba Laptop - Distro: Slackware 12
Hi all,
I think now is well posted. Sorry.
I have installed slackware 12 in my laptop toshiba A200. This laptop has a chicony usb 2.0 webcam built in. I read about a uvc driver in berlios, and I have tried to install this driver. The simple instructions are:
Code:
%svn checkout svn://svn.berlios.de/linux-uvc/linux-uvc/trunk
%make && make install
%modprobe uvcvideo
I have downloaded trunk folder to /usr/src/linux/trunk. However, I got just following error messages,
Code:
root@slackw:/usr/src/linux/trunk# make && make install
Building USB Video Class driver...
make[1]: Entering directory `/usr/src/linux-2.6.21.5'
CC [M] /usr/src/linux-2.6.21.5/trunk/uvc_driver.o
CC [M] /usr/src/linux-2.6.21.5/trunk/uvc_queue.o
CC [M] /usr/src/linux-2.6.21.5/trunk/uvc_v4l2.o
CC [M] /usr/src/linux-2.6.21.5/trunk/uvc_video.o
CC [M] /usr/src/linux-2.6.21.5/trunk/uvc_ctrl.o
CC [M] /usr/src/linux-2.6.21.5/trunk/uvc_status.o
/usr/src/linux-2.6.21.5/trunk/uvc_status.c: In function 'uvc_input_init':
/usr/src/linux-2.6.21.5/trunk/uvc_status.c:46: error: 'struct input_dev' has no member named 'dev'
make[2]: *** [/usr/src/linux-2.6.21.5/trunk/uvc_status.o] Error 1
make[1]: *** [_module_/usr/src/linux-2.6.21.5/trunk] Error 2
make[1]: Leaving directory `/usr/src/linux-2.6.21.5'
make: *** [uvcvideo] Error 2
I have checked if the camera is being recognized by linux, with
Code:
root@slackw:/usr/src/linux/trunk# lsusb
Bus 7 Device 1: ID 0000:0000
Bus 1 Device 1: ID 0000:0000
Bus 1 Device 2: ID 04f2:b008 Chicony Electronics Co., Ltd
Bus 2 Device 1: ID 0000:0000
Bus 6 Device 1: ID 0000:0000
Bus 5 Device 2: ID 046d:c521 Logitech, Inc.
Bus 5 Device 1: ID 0000:0000
Bus 4 Device 1: ID 0000:0000
Bus 3 Device 1: ID 0000:0000
So my camera is there, but I don't get it.
Please, If any have an idea to solve this, I really will appreciate it.
Do you have the kernel headers and source installed properly ?
TeXMeX,
I don't really know. Where must they be installed?...
I have just downloaded the trunk folder to a desktop folder, I log on as su in a terminal and I have tried with make n' make install, but just there, in the folder under home user path.
Well, both the source and headers seem to be installed.
What I would do is re-install the kernel headers, just 'installpkg kernel-headers-2.6.21.5_smp-i386-2.tgz' the package from the install dvd or after downloading it. Also make sure you have the latest cvs version of uvc.
Thanks for your help TeXMeX. I was able to put in function the camera chicony in my Toshiba. However, Your procedure still gave me problems. I did indeed a little different procedure, but based in your advice.
All my problems were solved when I update my kernel to 2.6.24.4. So, I installed not only the headers, but all the kernel. Whole problem was based on that in my old kernel (2.6.21.5, which is slackware original kernel), gives support to video for linux based in v4l, but uvcvideo (berlios drivers) and luvcview (software offered by Laurent Pinchart et al.) are both based in v4l2 (is it well said?... I'm newbie, please remember that
So, I have installed and compiled my new kernel in the following way:
---Please, I am giving this procedure just for feedback, and not as an expert or even mini - HOW TO. If you use this procedure, and it is good for you, I mean, it gives you none problem, please let me know. I have tested it several times (sadly... not for experience but for errors.. ), but I have finally obtained a respectable, fine-works, and updated kernel. This procedure has (finally) always worked for me, to ensure a bootable kernel. So, here you go ----
#!/bin/bash
# Obtaining new kernel from kernel.org, just I have put it in
cd /usr/src/
tar -xzvf linux-2.6.24.4.tar.gz
# I made a safe copy. Even after each rebuild of my kernel,
# and checked well operation, I did this procedure...
cp -pr linux-2.6.24.4/ linux-2.6.24.4-clean/
# I use my old config file (from 2.6.21.5 kernel)
cp /usr/src/linux/.config /usr/src/linux-2.6.24.4/.configold
#!Most of examples in web and books indicate that following step
# only the first time of new kernel source build.
# However, I´ve done this ever.
make mrproper
cp .configold .config
#!Modify extraversion line, if needed. In my case, I didn't this,
# and for that reason my link is always to -2.4.24.4, and not to.
pico Makefile
# Use a config tool to check your .config file.
# In this moment you must check that v4l2 is enabled, even though
# this the default option in kernel 2.6.24.4.
make menuconfig - or xconfig (from an X console) - or make oldconfig
# Please, check all your options as you maybe came from a kernel that
# had not images for all options in the new kernel... as always, be
# careful. I tell you, it may cost you several additional hours !!!.
# Next, I compile my kernel. I made a check of this, but this is up to you
nohup make bZimage &
tail -f nohup.out &
# Now, I made modules and installed them, only if everything was OK.
nohup make modules 1> modules.out 2> modules.err &
tail -f modules.out & !Check progress in building modules.
# Then, when it's finished...
pico modules.err
#!If not errors in modules.err (or in modules.out) then,
make modules_install
# Then, ...
cp -p arch/<$ARCH>/boot/bzImage /boot/vmlinuz-2.6.24.4
#!< ----- $ARCH can be read in last line in nohup.out ----- >
cp -p System.map /boot/System.map-2.6.24.4
cp -p .config /boot/config-2.6.24.4
#!If your boot manager is LILO, edit your lilo.conf to include the new kernel.
# If your boot manager is GRUB... I don'n know (sorry...)
# <--- Put this lines in your /etc/lilo.conf --->
#Linux bootable partition config begins
image = /boot/vmlinuz-2.6.24.4
root = /dev/sda4
label = Linux2
read-only
#Linux bootable partition config ends
# Finally, install new lilo.conf..
/sbin/lilo
reboot
And then, hopefully, you will get a new and video for linux 2 enabled kernel installed!!!!
With this done, then I was to trunk folder, and I realize that also I have old object files (already include in trunk folder from berlios), so what I did was:
Code:
make clean && make && make install
Now everythig works fine with my webcam... it's really awesome...
Just to try my camera, I have installed luvcview from berlios, and everything worked well.
Thanks for your help. I hope this could help anyelse.
Yep... you are right, I have checked config of my early kernel... and that lines appear there. Sorry, but then I don't understand why I didn't get "v4l2_common" with lsmod before... hmmm.
Any way, thanks... the important (for me... ) is that now I have my camera operating.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.