Re: Logitech Quick Cam driver
On Sat, Feb 27, 2010 at 1:44 PM, J.C. Roberts list-...@designtools.org wrote: *BUT* a particular vendor or model name doesn't really mean very much since the internal components are constantly changed by vendors without changing the product model name... hence, the need for a dmesg (and `usbdevs -v` is also nice). Hi JC, I got my PC re-installed again here is the info :-) #usbdevs -v Controller /dev/usb0: addr 1: high speed, self powered, config 1, EHCI root hub(0x), VIA(0x1106), rev 1.00 port 1 powered port 2 powered port 3 powered port 4 powered port 5 powered port 6 powered port 7 powered port 8 powered Controller /dev/usb1: addr 1: full speed, self powered, config 1, UHCI root hub(0x), VIA(0x1106), rev 1.00 port 1 addr 2: full speed, power 100 mA, config 1, product 0x08af(0x08af), Logitech(0x046d), rev 1.00 port 2 powered Controller /dev/usb2: addr 1: full speed, self powered, config 1, UHCI root hub(0x), VIA(0x1106), rev 1.00 port 1 powered port 2 powered Controller /dev/usb3: addr 1: full speed, self powered, config 1, UHCI root hub(0x), VIA(0x1106), rev 1.00 port 1 powered port 2 powered Controller /dev/usb4: addr 1: full speed, self powered, config 1, UHCI root hub(0x), VIA(0x1106), rev 1.00 port 1 powered port 2 powered dmesg == OpenBSD 4.6 (GENERIC) #53: Thu Jul 9 21:19:22 MDT 2009 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC real mem = 468385792 (446MB) avail mem = 441716736 (421MB) mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.3 @ 0xf0730 (54 entries) bios0: vendor American Megatrends Inc. version 080012 date 06/19/2006 bios0: ASUSTeK Computer INC. A8V-VM acpi0 at bios0: rev 0 acpi0: tables DSDT FACP APIC MCFG OEMB acpi0: wakeup devices PCI0(S4) PS2K(S4) PS2M(S4) UAR2(S4) USB1(S4) USB2(S4) USB3(S4) USB4(S4) ILAN(S4) PCI1(S4) PCI2(S4) SLPB(S4) PWRB(S4) acpitimer0 at acpi0: 3579545 Hz, 24 bits acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: AMD Athlon(tm) 64 Processor 3500+, 2200.47 MHz cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,SSE3,NXE,MMXX,FFXSR,LONG,3DNOW2,3DNOW cpu0: 64KB 64b/line 2-way I-cache, 64KB 64b/line 2-way D-cache, 512KB 64b/line 16-way L2 cache cpu0: ITLB 32 4KB entries fully associative, 8 4MB entries fully associative cpu0: DTLB 32 4KB entries fully associative, 8 4MB entries fully associative cpu0: AMD erratum 89 present, BIOS upgrade may be required cpu0: apic clock running at 200MHz ioapic0 at mainbus0 apid 1 pa 0xfec0, version 3, 24 pins ioapic1 at mainbus0 apid 2 pa 0xfecc, version 3, 24 pins acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus 1 (P0P1) acpiprt2 at acpi0: bus -1 (NBPG) acpiprt3 at acpi0: bus -1 (NBP0) acpiprt4 at acpi0: bus 4 (P0P7) acpiprt5 at acpi0: bus 5 (P0PA) acpicpu0 at acpi0: C3, C2 acpibtn0 at acpi0: SLPB acpibtn1 at acpi0: PWRB pci0 at mainbus0 bus 0 pchb0 at pci0 dev 0 function 0 VIA K8M890 Host rev 0x00 agp at pchb0 not configured pchb1 at pci0 dev 0 function 1 VIA K8M890 Host rev 0x00 pchb2 at pci0 dev 0 function 2 VIA K8M890 Host rev 0x00 pchb3 at pci0 dev 0 function 3 VIA K8M890 Host rev 0x00 pchb4 at pci0 dev 0 function 4 VIA K8M890 Host rev 0x00 VIA K8M890 IOAPIC rev 0x00 at pci0 dev 0 function 5 not configured pchb5 at pci0 dev 0 function 6 VIA K8M890 Host rev 0x00 pchb6 at pci0 dev 0 function 7 VIA K8M890 Host rev 0x00 ppb0 at pci0 dev 1 function 0 VIA K8HTB AGP rev 0x00 pci1 at ppb0 bus 1 vga1 at pci1 dev 0 function 0 VIA DeltaChrome Video rev 0x01 wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation) wsdisplay0: screen 1-5 added (80x25, vt100 emulation) pciide0 at pci0 dev 15 function 0 VIA VT8251 SATA rev 0x00: DMA pciide0: using apic 1 int 21 (irq 5) for native-PCI interrupt pciide1 at pci0 dev 15 function 1 VIA VT82C571 IDE rev 0x07: DMA, channel 0 configured to compatibility, channel 1 configured to compatibility wd0 at pciide1 channel 0 drive 0: ST340014A wd0: 16-sector PIO, LBA48, 38166MB, 78165360 sectors wd0(pciide1:0:0): using PIO mode 4, DMA mode 2 atapiscsi0 at pciide1 channel 1 drive 1 scsibus0 at atapiscsi0: 2 targets cd0 at scsibus0 targ 0 lun 0: Optiarc, DVD RW AD-7190A, 1.02 ATAPI 5/cdrom removable cd0(pciide1:1:1): using PIO mode 4, DMA mode 2 uhci0 at pci0 dev 16 function 0 VIA VT83C572 USB rev 0x90: apic 1 int 20 (irq 11) uhci1 at pci0 dev 16 function 1 VIA VT83C572 USB rev 0x90: apic 1 int 22 (irq 4) uhci2 at pci0 dev 16 function 2 VIA VT83C572 USB rev 0x90: apic 1 int 21 (irq 5) uhci3 at pci0 dev 16 function 3 VIA VT83C572 USB rev 0x90: apic 1 int 23 (irq 5) ehci0 at pci0 dev 16 function 4 VIA VT6202 USB rev 0x90: apic 1 int 22 (irq 4) usb0 at ehci0: USB revision 2.0 uhub0 at usb0 VIA EHCI root hub rev 2.00/1.00 addr 1 viapm0 at pci0 dev 17 function 0 VIA VT8251 ISA rev 0x00 iic0 at viapm0 spdmem0 at iic0 addr 0x51: 512MB DDR SDRAM non-parity PC3200CL3.0 pchb7 at pci0 dev 17 function 7 VIA VT8251 VLINK rev 0x00 vr0
Re: Logitech Quick Cam driver
On Mon, 8 Mar 2010 23:06:30 +0530 Siju George sgeorge...@gmail.com wrote: On Sat, Feb 27, 2010 at 1:44 PM, J.C. Roberts list-...@designtools.org wrote: *BUT* a particular vendor or model name doesn't really mean very much since the internal components are constantly changed by vendors without changing the product model name... hence, the need for a dmesg (and `usbdevs -v` is also nice). Hi JC, I got my PC re-installed again here is the info :-) #usbdevs -v Controller /dev/usb0: addr 1: high speed, self powered, config 1, EHCI root hub(0x), VIA(0x1106), rev 1.00 port 1 powered port 2 powered port 3 powered port 4 powered port 5 powered port 6 powered port 7 powered port 8 powered Controller /dev/usb1: addr 1: full speed, self powered, config 1, UHCI root hub(0x), VIA(0x1106), rev 1.00 port 1 addr 2: full speed, power 100 mA, config 1, product 0x08af(0x08af), Logitech(0x046d), rev 1.00 port 2 powered Controller /dev/usb2: I wonder why your cam is showing up as a Full Speed device (e.g. the slower 12 MiBit/s USB v1.0/1.1)? Of course, it really could be an older USB 1.0/1,1 device, but I just haven't seen one yet. Also, since the Product ID is not recognized, it could be due to taking the conservative approach in speed assignment. You *SHOULD* send in your dmesg to dm...@openbsd !!! dmesg == OpenBSD 4.6 (GENERIC) #53: Thu Jul 9 21:19:22 MDT 2009 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC ugen0 at uhub1 port 1 Logitech product 0x08af rev 1.10/1.00 addr 2 any hope? There's always hope! I just checked my -current system, and the Product ID above (0x08af) is not listed in usbdevs. The closest is the Logictech QuickCam Notebook Deluxe with a Product ID of 0x08a9 which is also listed in the video(4) man page as supported. Of course, this means it could be as simple as adding the Product ID to usbdevs and rebuilding, or it could be as difficult as needing additional, specific support in the driver. Give it a try and see what happens. jcr
Re: Logitech Quick Cam driver
On Thu, 25 Feb 2010 13:25:04 +0530 Siju George sgeorge...@gmail.com wrote: Hi, Any body running Ligitech QuickCam on OpenBSD 4.6 using http://tamentis.com/projects/openqce/ or any other driver? I have a QuickCam messenger. Thanks --Siju Come on Siju... where's the dmesg? The supported Logitech QuickCam models/versions/variations are listed in uvideo(1) along with other supported devices... *BUT* a particular vendor or model name doesn't really mean very much since the internal components are constantly changed by vendors without changing the product model name... hence, the need for a dmesg (and `usbdevs -v` is also nice). -jon
Re: Logitech Quick Cam driver
On Sat, Feb 27, 2010 at 1:44 PM, J.C. Roberts list-...@designtools.org wrote: On Thu, 25 Feb 2010 13:25:04 +0530 Siju George sgeorge...@gmail.com The supported Logitech QuickCam models/versions/variations are listed in uvideo(1) along with other supported devices... *BUT* a particular vendor or model name doesn't really mean very much since the internal components are constantly changed by vendors without changing the product model name... hence, the need for a dmesg (and `usbdevs -v` is also nice). ok that is good news :-) unfortunately i wrecked the installation will send the dmesg after re install :-) thanks --Siju
Re: Logitech Quick Cam driver
On Thu, Feb 25, 2010 at 6:07 PM, Bertrand Janin tamen...@neopulsar.org wrote: This stuff was an experiment, the code is awful and I don't recommend using it for anything but morbid curiosity. It only works with the Express version of the webcam, it doesn't integrate with anything and will only let you capture still frames (it does not even adjust the luminosity). Thank you so much Tomas, Thomas and Bertrand for the advice :-) --Siju
Logitech Quick Cam driver
Hi, Any body running Ligitech QuickCam on OpenBSD 4.6 using http://tamentis.com/projects/openqce/ or any other driver? I have a QuickCam messenger. Thanks --Siju
Re: Logitech Quick Cam driver
You can use webcams which use UVC standard http://en.wikipedia.org/wiki/USB_video_device_class . There is a lot of them. Mostly you can recognize them by Certifed for Vista/Windows 7 logo. Those cams are supported in OpenBSD, OpenSolaris and others. Linux has drivers for other cameras too, but support for them is sometimes problematic like broken support in some versions of kernel and so on. On Thu, Feb 25, 2010 at 8:55 AM, Siju George sgeorge...@gmail.com wrote: Hi, Any body running Ligitech QuickCam on OpenBSD 4.6 using http://tamentis.com/projects/openqce/ or any other driver? I have a QuickCam messenger. Thanks --Siju -- http://www.openbsd.org/lyrics.html
Re: Logitech Quick Cam driver
On Thu, 25 Feb 2010 13:25:04 +0530 Siju George sgeorge...@gmail.com wrote: Hi, Any body running Ligitech QuickCam on OpenBSD 4.6 using http://tamentis.com/projects/openqce/ or any other driver? As far as I know, there are no drivers for cameras other than the uvideo(4) driver that /should/ work with most UVC cameras (e.g. any camera that is certified for Windows Vista or later). You can get one of these starting at about 20 EUR.
Re: Logitech Quick Cam driver
Any body running Ligitech QuickCam on OpenBSD 4.6 using http://tamentis.com/projects/openqce/ or any other driver? I have a QuickCam messenger. This stuff was an experiment, the code is awful and I don't recommend using it for anything but morbid curiosity. It only works with the Express version of the webcam, it doesn't integrate with anything and will only let you capture still frames (it does not even adjust the luminosity). Bertrand
