Re: [Motion-user] Lumenera problem on v3.2.3

[aaron b. <as_...@ya...>]

> At this point, no ideas.  Could you try running it again, this time with the
> additional flag "-d 1" (i.e. "# motion -s -d 1") and post the results?  That
> should (hopefully) give some more information as to where the trouble is
> coming from (you could also try higher "debug levels", but level '1' should be
> sufficient for now).

Grrr . . . No level of debug provides additional output - it is identical to running it without
the -d flag.  Running with debug=5 on a functioning camera doesn't create any additional debug
between "Processing thread 0" and "Boundary string" either.  But after that, the functioning one
looks like:

[1] Boundary string [--video boundary--]
[1] Camera handler thread [2]  started
[1] vid_return_code 6
[1] Raw changes: 307171 - changes after 'EeDdl':     0 - labels:   0

So the lumenera is not getting to the next step of "Camera handler thread [2] started".

Thanks for any help you can provide!



		
____________________________________________________
Start your day with Yahoo! - make it your home page 
http://www.yahoo.com/r/hs