Page 1 of 2
NEW GUIDE TO USING WEBCAMS IN PUPPY PLUS COMPILED DRIVERS!
Posted: Tue 11 Apr 2006, 12:07
by NickBiker
Hi
I have just finished the first version of my Guide for installing Webcams on puppy - along with ready-compiled drivers tested and working on Puppy.
Go to my web page:
www.moyo.me.uk/pupplinux
Here is a simple guide for various webcams and the drivers for puppy to download.
I am working on a simple DotPup package and script to automate the process.
Let me know if this is of any help/works. If you have a camera that is not listed in my guide, contact me and I will see if I can find a suitable driver etc and get it going!
Good luck!!
[/url]
We are not worthy
Posted: Tue 11 Apr 2006, 12:35
by Lobster
You are a star!
Many thanks NickBiker I am off to get my Logitech working. I have every hope of success.
We are not worthy
We are not worthy
sorry I get a little carried away sometimes - will report back
Re: We are not worthy
Posted: Tue 11 Apr 2006, 13:02
by NickBiker
Lobster wrote:
I have every hope of success.
Hi
Thanks for the kind words! Check Section 2.2 of my Guide, you need to get your Vendor and ProdID. Hopefully these will match those I have tested in the table given - if not, let me know what these are and I will try to locate a suitable driver!
good luck!
space shuttle
Posted: Tue 11 Apr 2006, 14:31
by Lobster
Very nice PDF manual - Did you do it in Abiword?
This is my product info
(I hope)
As far as I am aware it is a logitech - it has "space shuttle" written on the cable
Code: Select all
D: Ver= 1.00 Cls=ff(vend.) Sub=ff Prot=ff MxPS= 8 #Cfgs= 1
P: Vendor=046d ProdID=0840 Rev= 1.00
S: Product=Camera
first two in your series of commands worked
not the third
but I am hopeful you can help
I am in Puppy2 Alpha 5 incidentally - would that make a difference . . . not sure . . .
Anyway here is what happened:
Code: Select all
sh-3.00# depmod -a
sh-3.00# modprobe videodev
sh-3.00# modprobe quickcam
modprobe: Can't locate module quickcam
Do I need a different driver?
- I have another challange later - a camera that can be used as a webcam - however that may be too obscure to work with . . . and I would be pleased to get the logitech running . . .
many thanks
USB P/C camera
Posted: Tue 11 Apr 2006, 15:06
by eccentric
Well done Nick,
My camera is a Vimicro corp.
Ver=1.10 class=ff(vend)
Vendor=0ac8 prod. ID 301b rev.=1.0
The shape is like a turtle and is sold over here with other names on the box, so i think the chip is common to many. The shape will upset mr. Lobster.
Control panel / usbveiw USB info. can see it is pluged in.
Thank you for your work so far Michael. an eccentric.
Re: space shuttle
Posted: Tue 11 Apr 2006, 15:21
by NickBiker
Lobster wrote:Very nice PDF manual - Did you do it in Abiword?
Thanks - I wrote it in Word (I know, sorry!)
Code: Select all
D: Ver= 1.00 Cls=ff(vend.) Sub=ff Prot=ff MxPS= 8 #Cfgs= 1
P: Vendor=046d ProdID=0840 Rev= 1.00
S: Product=Camera
This is a LOGITECH camera, but will NOT work with the drivers I have tested. I have a driver for this camera and have compiled this in Puppy - I will uodate my site soon!
Lobster wrote:
I am in Puppy2 Alpha 5 incidentally - would that make a difference . . . not sure . . .
Did you read Section 1.1?
Check the Kernel version of Puppy usin
If it is not 2.4.x then none of the drivers will work as they are all specific to that version. Let me know!
I would need to upgrade to the new Puppy this end, and then re-compile everything for a new kernel. I am happy to do this but it will take me some time!
Re: USB P/C camera
Posted: Tue 11 Apr 2006, 16:17
by NickBiker
eccentric wrote:Vendor=0ac8 prod. ID 301b rev.=1.0
The shape is like a turtle and is sold over here with other names on the box
Hi
I have located and compiled the driver for this camera and will post a link on my web site in a few hours. Could you test it for me and let me know?
Please confirm you are running Puppy 1.08, with Kernel 2.4.29 - please type
In console and let me know!
Posted: Tue 11 Apr 2006, 16:28
by jcoder24
I'll try this when i get home tonight. One thing i've notice about your puppy-qc-usb-messenger-1.2.tar.gz is that it has a /lib folder. This lib folder would only persist after a reboot if you are using puppy2 or if you have done a hard drive install.
Posted: Tue 11 Apr 2006, 19:01
by NickBiker
jcoder24 wrote:I'll try this when i get home tonight. One thing i've notice about your puppy-qc-usb-messenger-1.2.tar.gz is that it has a /lib folder. This lib folder would only persist after a reboot if you are using puppy2 or if you have done a hard drive install.
Hi
You are right the module will not persist in a non-hd installation. I will update the initialisation script to copy the module from /usr (which is persistent) and then copy it to /lib/modules ...
I will create a GetPup package for each as well to make it easier.
Next step will then be a script that autodetects the USB camera, looks up in a smal database the vendor/product and selects the driver, downloads this, tests it etc....
Good luck - let me know.
Posted: Tue 11 Apr 2006, 20:10
by Lobster
Thanks for reply - this is from Puppy2 Alpha 5 - it is the 2.4 kernel
installed the new driver
then got this:
sh-3.00# depmod -a
sh-3.00# modprobe videodev
sh-3.00# modprobe qcam
modprobe: Can't locate module qcam
awaiting further instructions
Posted: Wed 12 Apr 2006, 04:54
by Sage
Well done, Nick!
Next trick is to tackle some of the sensors that have defied other penguin lovers.
You will find that many of these will sign up as Vendor - 0000 and ID = ditto.
I have a Creative with the notorious PD1001 sensor that does this and has not responded so far to any previous suggestions given on the Web.
Posted: Wed 12 Apr 2006, 04:58
by jcoder24
I am testing with an older logitech webcam (vendor:046D product:0870), prob 2 years old. All goes well up until you have to load the drivers for the camera.
depmod -a
modprobe videodev
modprobe qcam
Code: Select all
Apr 12 00:03:54 (none) user.info kernel: Linux video capture interface: v1.00
Apr 12 00:04:00 (none) user.info kernel: usb.c: registered new driver quickcam
Apr 12 00:04:00 (none) user.info kernel: quickcam: QuickCam USB camera found (driver version QuickCam USB $Date: 2004/07/29 18:12:39 $)
Apr 12 00:04:00 (none) user.info kernel: quickcam: Kernel:2.4.29 bus:3 class:FF subclass:FF vendor:046D product:0870
Apr 12 00:04:00 (none) user.debug kernel: quickcam [ 0.582440]: poisoning qc in qc_usb_init
Apr 12 00:04:00 (none) user.info kernel: quickcam: Probing HDCS-1000/1100: expecting 08, got 70
Apr 12 00:04:00 (none) user.info kernel: quickcam: Probing HDCS-1020: expecting 10, got 70
Apr 12 00:04:00 (none) user.info kernel: quickcam: Probing PB-0100/0101: expecting 64, got 00
Apr 12 00:04:00 (none) user.info kernel: quickcam: Probing VV6410: expecting 19, got 70
Apr 12 00:04:00 (none) user.info kernel: quickcam: Probing VV6450: expecting F0, got 70
Apr 12 00:04:00 (none) user.info kernel: quickcam: unsupported sensor
Apr 12 00:04:00 (none) user.info kernel: quickcam: QuickCam USB camera found (driver version QuickCam USB $Date: 2004/07/29 18:12:39 $)
Apr 12 00:04:00 (none) user.info kernel: quickcam: Kernel:2.4.29 bus:3 class:FF subclass:FF vendor:046D product:0870
Apr 12 00:04:00 (none) user.debug kernel: quickcam [ 0.589152]: poisoning qc in qc_usb_init
Apr 12 00:04:00 (none) user.info kernel: quickcam: Probing HDCS-1000/1100: expecting 08, got 70
Apr 12 00:04:00 (none) user.info kernel: quickcam: Probing HDCS-1020: expecting 10, got 70
Apr 12 00:04:00 (none) user.info kernel: quickcam: Probing PB-0100/0101: expecting 64, got 00
Apr 12 00:04:00 (none) user.info kernel: quickcam: Probing VV6410: expecting 19, got 70
Apr 12 00:04:00 (none) user.info kernel: quickcam: Probing VV6450: expecting F0, got 70
Apr 12 00:04:00 (none) user.info kernel: quickcam: unsupported sensor
depmod -a
modprobe videodev
modprobe quickcam
Code: Select all
Apr 12 00:14:34 (none) user.debug kernel: quickcam [34.642477]: ----------LOADING QUICKCAM MODULE------------
Apr 12 00:14:34 (none) user.debug kernel: quickcam [34.642498]: struct quickcam size: 3084
Apr 12 00:14:34 (none) user.info kernel: usb.c: registered new driver quickcam
Apr 12 00:14:34 (none) user.info kernel: quickcam: QuickCam USB camera found (driver version QuickCam USB $Date: 2004/07/29 18:12:39 $)
Apr 12 00:14:34 (none) user.info kernel: quickcam: Kernel:2.4.29 bus:3 class:FF subclass:FF vendor:046D product:0870
Apr 12 00:14:34 (none) user.debug kernel: quickcam [34.642599]: poisoning qc in qc_usb_init
Apr 12 00:14:34 (none) user.info kernel: quickcam: Probing HDCS-1000/1100: expecting 08, got 70
Apr 12 00:14:34 (none) user.info kernel: quickcam: Probing HDCS-1020: expecting 10, got 70
Apr 12 00:14:34 (none) user.info kernel: quickcam: Probing PB-0100/0101: expecting 64, got 00
Apr 12 00:14:34 (none) user.info kernel: quickcam: Probing VV6410: expecting 19, got 70
Apr 12 00:14:34 (none) user.info kernel: quickcam: Probing VV6450: expecting F0, got 70
Apr 12 00:14:34 (none) user.info kernel: quickcam: unsupported sensor
Apr 12 00:14:34 (none) user.info kernel: quickcam: QuickCam USB camera found (driver version QuickCam USB $Date: 2004/07/29 18:12:39 $)
Apr 12 00:14:34 (none) user.info kernel: quickcam: Kernel:2.4.29 bus:3 class:FF subclass:FF vendor:046D product:0870
Apr 12 00:14:34 (none) user.debug kernel: quickcam [34.655087]: poisoning qc in qc_usb_init
Apr 12 00:14:34 (none) user.info kernel: quickcam: Probing HDCS-1000/1100: expecting 08, got 70
Apr 12 00:14:34 (none) user.info kernel: quickcam: Probing HDCS-1020: expecting 10, got 70
Apr 12 00:14:34 (none) user.info kernel: quickcam: Probing PB-0100/0101: expecting 64, got 00
Apr 12 00:14:34 (none) user.info kernel: quickcam: Probing VV6410: expecting 19, got 70
Apr 12 00:14:34 (none) user.info kernel: quickcam: Probing VV6450: expecting F0, got 70
Apr 12 00:14:34 (none) user.info kernel: quickcam: unsupported sensor
Posted: Wed 12 Apr 2006, 06:05
by tempestuous
Lobster wrote:I am in Puppy2 Alpha 5 incidentally - would that make a difference
Modules are kernel-specific.
Puppy 1.0.4 - 1.0.8 = kernel 2.4.29
Puppy 2 = kernel 2.4.31
It's great that we have a broad selection of add-on modules to support all manner of exotic hardware out there, but it's worth noting that this collection (including all 17 of my wifi packages) will become redundant with the release of Puppy2.
Posted: Wed 12 Apr 2006, 07:39
by Lobster
thanks for that temp - will go back to 1.08 and try again
Posted: Wed 12 Apr 2006, 08:11
by NickBiker
tempestuous wrote:Lobster wrote:I am in Puppy2 Alpha 5 incidentally - would that make a difference
Modules are kernel-specific.
Puppy 1.0.4 - 1.0.8 = kernel 2.4.29
Puppy 2 = kernel 2.4.31
It's great that we have a broad selection of add-on modules to support all manner of exotic hardware out there, but it's worth noting that this collection (including all 17 of my wifi packages) will become redundant with the release of Puppy2.
Hi!
Is this because they will all be included in Puppy 2?
Although I am sure it is debated here, why is puppy 2 not Kernel 2.6 - it is supposed to be much more efficient?
Posted: Wed 12 Apr 2006, 08:19
by Lobster
This is my latest results (back in 108r1) using the same kernel as you have compiled in
Code: Select all
# depmod -a
depmod: *** Unresolved symbols in /lib/modules/2.4.29/sound/oss/viaudiocombo.o.gz
# modprobe videodev
# modprobe qcam
# cat /proc/bus/usb/devices
T: Bus=02 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=12 MxCh= 2
B: Alloc= 0/900 us ( 0%), #Int= 0, #Iso= 0
D: Ver= 1.00 Cls=09(hub ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1
P: Vendor=0000 ProdID=0000 Rev= 0.00
S: Product=USB UHCI Root Hub
S: SerialNumber=d800
C:* #Ifs= 1 Cfg#= 1 Atr=40 MxPwr= 0mA
I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub
E: Ad=81(I) Atr=03(Int.) MxPS= 8 Ivl=255ms
T: Bus=02 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#= 2 Spd=12 MxCh= 0
D: Ver= 1.00 Cls=ff(vend.) Sub=ff Prot=ff MxPS= 8 #Cfgs= 1
P: Vendor=046d ProdID=0840 Rev= 1.00
S: Product=Camera
C:* #Ifs= 1 Cfg#= 1 Atr=80 MxPwr=500mA
I: If#= 0 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none)
E: Ad=81(I) Atr=01(Isoc) MxPS= 0 Ivl=1ms
E: Ad=82(I) Atr=03(Int.) MxPS= 1 Ivl=16ms
I: If#= 0 Alt= 1 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none)
E: Ad=81(I) Atr=01(Isoc) MxPS=1023 Ivl=1ms
E: Ad=82(I) Atr=03(Int.) MxPS= 1 Ivl=16ms
T: Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=12 MxCh= 2
B: Alloc= 0/900 us ( 0%), #Int= 0, #Iso= 0
D: Ver= 1.00 Cls=09(hub ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1
P: Vendor=0000 ProdID=0000 Rev= 0.00
S: Product=USB UHCI Root Hub
S: SerialNumber=d400
C:* #Ifs= 1 Cfg#= 1 Atr=40 MxPwr= 0mA
I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub
E: Ad=81(I) Atr=03(Int.) MxPS= 8 Ivl=255ms
For some reason the driver is not being added?
I followed the instructions OK (I think) and installed in the Home directory
Will have another go later . . .
Any suggestions
and finally .. .
Many reasons not to move to 2.6 (it is Barry plan to eventualy move to 2.6)
it is to do with smallness, compatibility and reliability (the 2.4 is still being developed) One aim was to allow a choice of 2.4 or 2.6 but I suppose we will move eventually. Also Puppy2 is not yet in Beta (5 Alpha just released)
latest 2.6 kernel for those interested
http://lwn.net/Articles/179437/
Posted: Wed 12 Apr 2006, 09:13
by tempestuous
Sorry, "redundant" is the wrong word. I was trying to avoid "unusable" or "useless", but these are correct.
A 2.6 kernel was used in Puppy 1.0.2/1.0.3. You can read Barry's 2005 news page about the reasons for changing back, and this subject is discussed in several forum posts, too.
problems with the PDF
Posted: Wed 12 Apr 2006, 11:08
by Lobster
Nickbiker - having problems with the PDF - see here:
http://www.murga.org/%7Epuppy/viewtopic ... 5612#45612
We are probably using quite an old viewer so - hey I thought of a solution - I will load it into Abiword
Did not load into Abiword - waited 5 mins - should be long enough . . . even for an MS PDF
check out this PDF creator - any good?
http://www.expresspdf.com/
OK I will await any advisement before proceeding in my webcam adventures
Posted: Wed 12 Apr 2006, 12:06
by NickBiker
Lobster wrote:
For some reason the driver is not being added?
I followed the instructions OK (I think) and installed in the Home directory
Hi
Can you run:
Code: Select all
cat /var/log/messages | grep -a20 QUICKCAM
after you have done the modprobe.
This should show you a number of messages generated from the driver, mine shows:
Code: Select all
Apr 12 11:29:26 (none) user.debug kernel: quickcam [26.940566]: ----------LOADING QUICKCAM MODULE------------
Apr 12 11:29:26 (none) user.debug kernel: quickcam [26.940577]: struct quickcam size: 3084
Apr 12 11:29:26 (none) user.info kernel: usb.c: registered new driver quickcam
Apr 12 11:29:26 (none) user.debug kernel: quickcam [26.940596]: qc_usb_probe ifacenum=0
Apr 12 11:29:26 (none) user.info kernel: quickcam: QuickCam USB camera found (driver version QuickCam Messenger/Communicate USB $Date: 2004/12/30 10:00:00 $)
Apr 12 11:29:26 (none) user.info kernel: quickcam: Kernel:2.4.29 bus:2 class:FF subclass:FF vendor:046D product:08F5
Apr 12 11:29:26 (none) user.debug kernel: quickcam [26.940612]: poisoning qc in qc_usb_init
Apr 12 11:29:26 (none) user.debug kernel: quickcam [26.943940]: E00A contains 08F5
Apr 12 11:29:26 (none) user.info kernel: quickcam: Sensor VV6450 detected
Apr 12 11:29:26 (none) user.debug kernel: quickcam [26.944950]: Quickcam snapshot button registered as /dev/input/event0
Apr 12 11:29:26 (none) user.info kernel: quickcam: Registered device: /dev/video0
Apr 12 11:29:26 (none) user.debug kernel: quickcam [26.944967]: qc_usb_probe ifacenum=1
Apr 12 11:29:26 (none) user.debug kernel: quickcam [26.944970]: qc_usb_probe ifacenum=2
Apr 12 11:29:26 (none) user.debug kernel: quickcam [26.944972]: qc_usb_probe ifacenum=2
Yours wil hopefully show us why it is not working - probably an unrecognised sensor!
Let me know - good luck
Puppy TV
Posted: Wed 12 Apr 2006, 12:55
by Lobster
Thanks Nick
have added a .doc to Pdf online creator in my previous post
This is the code
Code: Select all
# depmod -a
depmod: *** Unresolved symbols in /lib/modules/2.4.29/sound/oss/viaudiocombo.o.gz
# modprobe videodev
# modprobe qcam
modprobe: Can't locate module qcam
# cat /var/log/messages | grep -a20 QUICKCAM
#
Do I have the qcam wrongly named or in the wrong place (possibly) where should it be?
. . . coming soon . . .
Puppy TV just when you thought it was safe . . .