Quickcam Pro 5000 works and vanishes

[Steve Sisak]

At 6:28 PM +0000 1/2/07, David Brown wrote:
>	glad to hear I'm not the only one having problems. I send 
>mail to Steve on 12 Decmeber about this, but still no had any reply, 
>here's hoping we get something soon. I purchased a license 
>specifically to use with this camera, but don't remember when it 
>last work consistently for any period of time.

Hi David,

Sorry for the delay -- it looks like you sent your logs to the list 
and the message was held by the list server because it was too large 
-- the list has a message size limit of 40k.

In the future, it's better to send logs to me off list or, better 
yet, create a support ticket using the form:

  <http://www.ioxperts.com/support-request/support-request.html>

If you want to add an attachment (or don't like typing lots of 
details into a web form), just fill in the minimal details in the web 
form and reply to the confirmation email with any additional details, 
enclosures, etc.

As long as you retain the ticket number in the subject of the 
message, anything you send in reply will be appended to the original 
ticket, which makes it a lot easier to keep track of issues.

-----

That said, the log file you sent, contains evidence of a firmware 
problem I've been trying to isolate with help from Logitech -- once 
the camera gets into this state, it stops responding and we can no 
longer to it.

If anyone gets into this state with a logging version of the driver, 
look in the log for something that looks like this:

     alt= 4, attr=0x01, int=1, pkt= 640
     alt= 5, attr=0x01, int=1, pkt= 800
     alt= 6, attr=0x01, int=1, pkt= 944, 0:0 ERROR: -536870165(0xe00002eb)
       [0x05] processor info: sel=2, info=$0f, len=1
### Error initializing control 2, -536870165(0xe00002eb)
       [0x03] auto-exposure priority: sel=5, info=$01, len=2, 0:0 
ERROR: -536870165(0xe00002eb)
       [0x06] USB info:
### Error initializing control 2, -536870165(0xe00002eb)
       [0x03] auto-exposure priority: sel=3, info=$03, len=1
       [0x04] exposure time (absolute):
Found Input Stream: 533 bytes, 3 formats, endpt=81, info=00, term=5, 
still=2, trig=01,00 csiz=1 sel=6, info=$01, len=6, 0.0.0 ERROR: 
-536870165(0xe00002eb)
       [0x07] hardware revision: sel=3, info=$03, len=1
       [0x04] exposure time (absolute):
### Error initializing control 4, -536870165(0xe00002eb)
   Initializing processing unit id=2, 10 controls:
       [0x01] backlight compensation: sel=7, info=$01, len=2, 0.0 
ERROR: -536870165(0xe00002eb)
       [0x09] lens FOV: sel=4, info=$0f, len=2
### Error initializing control 1, -536870165(0xe00002eb)
       [0x02] brightness: sel=9, info=$01, len=2 sel=2, info=$03, len=2, 51x38

In this case 0xe00002eb is kIOReturnAborted -- the other error I've 
seen is 0xe00002ed a.k.a. kIOReturnNotResponding

If anyone gets into this state, I'd appreciate it if you could look 
in the log file for something that looks like this and send it to me.

Thanks,

-Steve

-- 
_________________________________________________________________________
Steve Sisak, CTO                                 steve.sisak at ioxperts.com
IOXperts, Inc.                                     voice: +1 617 876-2572
87 Bristol St #3A                                    fax: +1 617 876-2337
Cambridge, MA 02139                               mobile: +1 617 388-6476