On 10/12/10 05:59 PM, Bob Hoekstra wrote:
On Tue, 12 Oct 2010 11:23:00 -0400 Albert Lee<tr...@opensolaris.org>
wrote:
On Tue, Oct 12, 2010 at 4:51 AM, Bob Hoekstra<bob.hoeks...@gmail.com>
wrote:
<trim>
I wanted to ask if anyone has any experience with the Acer Crystal Eye
webcam. This is built into my Laptop (Acer Aspire 5735) and has never
worked
with OpenSolaris. I have googled some users who have got it working with
Linux. It's a nice-to-have, and before I spend days on a fruitless
search,
perhaps there is someone who knows more than I about this. Any
comments/advice welcome.
Can you provide info about this webcam from 'echo ::prtusb | sudo mdb
-k'? The Acer Crystal Eye in my Aspire One works perfectly, as it is a
standard USB video class device.
-Albert
Thanks for the response Albert. This is what I get:
r...@breeze [/root] echo ::prtusb | mdb -k
INDEX DRIVER INST NODE VID.PID PRODUCT
1 ehci 0 pci1025,176 0000.0000 No Product String
2 ehci 1 pci1025,176 0000.0000 No Product String
3 uhci 0 pci1025,176 0000.0000 No Product String
4 uhci 1 pci1025,176 0000.0000 No Product String
5 uhci 2 pci1025,176 0000.0000 No Product String
6 uhci 3 pci1025,176 0000.0000 No Product String
7 uhci 4 pci1025,176 0000.0000 No Product String
8 uhci 5 pci1025,176 0000.0000 No Product String
9 scsa2usb 0 storage 0bda.0158 USB2.0-CRW
a scsa2usb 5 storage 18a5.0216 Desktop USB Drive
b usb_mid 1 device 046d.c51b USB Receiver
c usb_mid 0 miscellaneous 5986.0105 Acer Crystal Eye
webcam
I also note on boot up it is recognised as an "audio device"! I get lines
like this in messages:
Oct 12 17:34:17 breeze usba: [ID 349649 kern.notice] USB Audio Device
Acer Crystal Eye webcam
Is that normal?
Interestingly, I can access the webcam from a Windows VirtualBox VM, and it
seems to behave normally, so obviously the hardware itself is OK.
Perhaps take this to email between us? I doubt the rest of the readers are
overly excited about this. I can always post something if we/I find the
solution.
Bob
---
-----BEGIN GEEK CODE BLOCK-----
Version: 3.12
GO/! d- s++:+ a++ C++++ US++++$ UB++++ UI++++ UH++++ U*+++ P++++
L+++ E--- W+++ N++ o-- K? w--- O- M+ V- PS+ PE+ Y+ PGP++ t+ 5++
X R* tv b+ DI++ D G- e* h++/-- r+++ ys++++
------END GEEK CODE BLOCK------
-----------------------------------------------------
Bob Hoekstra: Unix Consultant
Telephone: +44 7710 562345 (UK)
+31 616 629217 (NL)
Email: bob.hoeks...@gmail.com
-----------------------------------------------------
_______________________________________________
OpenIndiana-discuss mailing list
OpenIndiana-discuss@openindiana.org
http://openindiana.org/mailman/listinfo/openindiana-discuss
as far I remember driver "usbvc" will be loaded due to class name on
uvc compliant devices, by "usbia,classe" entry on /etc/driver_aliases.
maybe that model is not fully compatible or not have uvc class name ,
eg for my logitech 9000:
r...@hydra:~# prtconf -v | grep "usbvc"
value='NAME= usbvc0 Power' + '0=USB D3
State' + '3=USB D0 State'
dev_path=/p...@0,0/pci1297,5...@1d,7/h...@5/miscellane...@2/vi...@0:usbvc
if is a class name issue maybe that device is not fully compatible, but
if it is listed as a uvc compliant, you can try attach by device id with:
# update_drv -a -i "<your camera device id>" usbvc
Regards,
Carlos Almeida,
_______________________________________________
OpenIndiana-discuss mailing list
OpenIndiana-discuss@openindiana.org
http://openindiana.org/mailman/listinfo/openindiana-discuss
