Logitech Quickcam on Slackware 12.2
in [Slackware]
|
From: Tuxedo on 8 Jan 2010 12:24 microsys wrote: [...] > It's been awhile since I set this cam up however this may be of some help > to you. > > For Slack-12.2 these packages are available at SBO.. > > CImg-1.2.9 > mjpegtools-1.9.0 > wxGTK-2.8.9 > wxcam-1.0.3 > xvidcore-1.2.1 > > I should note the cam I have does use the Zoom function and the drivers I > am using do not support the Zoom function. That being said, the cam works > quite well. I never did bother to see if the Zoom could be made to work. > > Here is the dmesg reporting when the cam gets plugged in. You will note > the Manufacturer selected is Phillips. They make the chip for Logitech > which I suspect is causing you some problems when looking for a solution. > > dmesg reports > > usb 2-1: new full speed USB device using uhci_hcd and address 2 > usb 2-1: configuration #1 chosen from 1 choice > usb 2-1: New USB device found, idVendor=046d, idProduct=08b4 > usb 2-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0 > Linux video capture interface: v2.00 > pwc: Philips webcam module version 10.0.13 loaded. > pwc: Supports Philips PCA645/646, PCVC675/680/690, PCVC720[40]/730/740/750 > & PCVC830/840. > pwc: Also supports the Askey VC010, various Logitech Quickcams, Samsung > MPC-C10 and MPC-C30, > pwc: the Creative WebCam 5 & Pro Ex, SOTEC Afina Eye and Visionite > VCS-UC300 and VCS-UM100. > pwc: Logitech QuickCam Zoom (new model) USB webcam detected. > pwc: Registered as /dev/video0. > usbcore: registered new interface driver Philips webcam > usbcore: registered new interface driver snd-usb-audio Thanks for posting the above and further adding to my confusion :-). None of the 'pwc', 'Philips', 'Logitech' stuff exist in my 'dmesg' output. Tuxedo
From: Tuxedo on 8 Jan 2010 12:30 Lew Pitcher wrote: > Tuxedo <tuxedo(a)mailinator.com> trolled: > > > It appears to be a driver error, or a missing driver. I found a driver > > named Quick Cam USB or QuickCam Express, but it does not install on > > Slackware 12.2. The driver appears to still be in alpha and have been > > abandoned. Last version is qc-usb-0.6.6.tar.gz (2006-11-04). > > Logitech hardware. This is just another reason why linux never > has, and never will, make the jump into mainstream. > > People like to talk about Windoze and the blue screen of death and > linux uptimes and the like. > > But the fact is, linux doesn't do half the stuff windoze does and > that's the only reason it doesn't get half the bugs. > > Face it guys, linux is amateur hour. Linux "Admins" are merely > hobbyists who remind us of those guys who put on train engineer > hats before playing with their Lionels. Surely Linux where everything works out of the box will one day become the most popular OS and then it will become mainstream, simply because it's better than Windows, and who knows, perhaps it will be Slackware based. Tuxedo
From: Bud on 8 Jan 2010 15:43 On 2010-01-08, Tuxedo wrote: > Jim Diamond wrote: > > My system doesn't have the command 'lsusb' but my USB cam device appears to > have the ID "USB Camera (046d:08d8)" as reported by the CamStream > application. The hardware works fine in Windows on the same machine. > > Will test another cam. > > Tuxedo You have to be root to use the command i.e. username]$lsusb -- Bud
From: Lew Pitcher on 8 Jan 2010 18:12 Tuxedo <tuxedo(a)mailinator.com> trolled: > Jim Diamond wrote: > > [...] > >> Logitech has the annoying habit of naming a lot of different webcams >> with very similar names. That's almost as annoying as their penchant for creating webcams that you simply plugin and use, at least if you are using a real OS. cordially, as always, rm
From: Mike Spencer on 9 Jan 2010 03:24
I haven't folowed all the details of this thread so this may be way off base, but... If you used the Logitech cam on Slack 11 or earlier and you have now ported the same driver to Slack 12, you may possibly be having problems with the libs used to compile the driver. Slack 12 switched to new versions of some libs (gnulibc? gnulic++?) and non-open source software compiled with the earlier libs may fail. This has really pissed me off because I have two commercial packages for which I'm compelled to stay with Slack 11 even when I've upgraded other boxen to Slack 12. Grrrrrrr.... -- Mike Spencer Nova Scotia, Canada |