Hi,
The problem with the camera seems to be the xf86-video-geode package.
The cafe_ccic module is loaded automatically. Cheese and recordactivity
crashed right before show any picture. Then I tested remotely with ssh
-X and it worked for olpc and root user and it works.
This test was done with:
* XO-1 kernel: 2.6.31_xo1-20091214.1334.1.olpc.49c30d0
* os10
Even if it works remotely, there are a lots of warning messages on
the /var/log/messages:
Dec 16 19:09:35 xo-37-a0-b9 kernel: [ 1218.250879] cafe1000-ccic
0000:00:0c.2: Frame overrun on 1, frames lost
Dec 16 19:09:36 xo-37-a0-b9 kernel: [ 1218.284198] cafe1000-ccic
0000:00:0c.2: Frame overrun on 2, frames lost
Dec 16 19:09:36 xo-37-a0-b9 kernel: [ 1218.317524] cafe1000-ccic
0000:00:0c.2: Frame overrun on 0, frames lost
Dec 16 19:09:36 xo-37-a0-b9 kernel: [ 1218.350843] cafe1000-ccic
0000:00:0c.2: Frame overrun on 1, frames lost
Dec 16 19:09:36 xo-37-a0-b9 kernel: [ 1218.384170] cafe1000-ccic
0000:00:0c.2: Frame overrun on 2, frames lost
Dec 16 19:09:36 xo-37-a0-b9 kernel: [ 1218.417498] cafe1000-ccic
0000:00:0c.2: Frame overrun on 0, frames lost
Dec 16 19:09:36 xo-37-a0-b9 kernel: [ 1218.450817] cafe1000-ccic
0000:00:0c.2: Frame overrun on 1, frames lost
Dec 16 19:09:36 xo-37-a0-b9 kernel: [ 1218.484134] cafe1000-ccic
0000:00:0c.2: Frame overrun on 2, frames lost
Dec 16 19:09:36 xo-37-a0-b9 kernel: [ 1218.517459] cafe1000-ccic
0000:00:0c.2: Frame overrun on 0, frames lost
Dec 16 19:09:41 xo-37-a0-b9 kernel: [ 1223.282572] __ratelimit: 142
callbacks suppressed
Dec 16 19:09:41 xo-37-a0-b9 kernel: [ 1223.282599] cafe1000-ccic
0000:00:0c.2: Frame overrun on 2, frames lost
Dec 16 19:09:41 xo-37-a0-b9 kernel: [ 1223.315900] cafe1000-ccic
0000:00:0c.2: Frame overrun on 0, frames lost
Dec 16 19:09:41 xo-37-a0-b9 kernel: [ 1223.349218] cafe1000-ccic
0000:00:0c.2: Frame overrun on 1, frames lost
Dec 16 19:09:41 xo-37-a0-b9 kernel: [ 1223.382540] cafe1000-ccic
0000:00:0c.2: Frame overrun on 2, frames lost
Dec 16 19:09:41 xo-37-a0-b9 kernel: [ 1223.415857] cafe1000-ccic
0000:00:0c.2: Frame overrun on 0, frames lost
Dec 16 19:09:41 xo-37-a0-b9 kernel: [ 1223.449178] cafe1000-ccic
0000:00:0c.2: Frame overrun on 1, frames lost
Dec 16 19:09:41 xo-37-a0-b9 kernel: [ 1223.480217] cafe1000-ccic
0000:00:0c.2: Frame overrun on 2, frames lost
Dec 16 19:09:41 xo-37-a0-b9 kernel: [ 1223.510492] cafe1000-ccic
0000:00:0c.2: Frame overrun on 0, frames lost
Dec 16 19:09:41 xo-37-a0-b9 kernel: [ 1223.549157] cafe1000-ccic
0000:00:0c.2: Frame overrun on 1, frames lost
Dec 16 19:09:41 xo-37-a0-b9 kernel: [ 1223.582476] cafe1000-ccic
0000:00:0c.2: Frame overrun on 2, frames lost
Regards,
On Sat, 2009-12-12 at 20:16 +0000, Daniel Drake wrote:
> Hi,
>
> Jon Corbet's been working on the XO-1.5 camera driver for us, and
while
> doing so he found a V4L2 bug which is probably one of the reasons that
> we're having problems with XO-1 camera on all post-8.2 builds.
>
> The workaround is to build the sensor driver into the kernel, and the
> camera driver as a module.
>
> I've made the equivalent change for the kernel that has been built
here:
>
>
http://xs-dev.laptop.org/~dsd/repos/f11-xo1/kernel-2.6.31_xo1-20091211.1834.1.olpc.813348c.i586.rpm
>
> Untested, just wanted to get the word out.
>
> Note that you may have to load the camera driver (cafe_ccic) manually,
> if it doesn't automatically get loaded.
>
> Word is going round that on a SoaS build for XO (which uses something
> close to OLPC's 2.6.30 kernel, I think), someone recently managed to
> capture a photo from the command line.
>
> If someone is up for a small task, it would be good to start changing
> these "words going round" to some actual solid information. Anyone
want
> to head up these efforts and to start
> http://wiki.laptop.org/go/Reviving_XO1_camera ?
> At the very least it would be nice to have some solid documentation on
> where the problem is (and isn't). Is it in ov7670, cafe_ccic, v4l2,
> gstreamer, xf86-video-geode, or..? How can you tell? Does the above
> kernel help? What's the exact command you can use on F12 SoasXO to
take
> a photo? What's the corresponding error if you do that on F11? etc.
>
> Daniel
>
>
> _______________________________________________
> Devel mailing list
> Devel@lists.laptop.org
> http://lists.laptop.org/listinfo/devel
>
_______________________________________________
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel
