Re: possible progress on XO-1 camera issues
On Tue, Dec 22, 2009 at 09:42:54PM -0300, Raul Gutierrez Segales wrote: > Is it cheating to change the screen depth? I change it to 24 bpp and now > cheese and totem work. Changes to /etc/X11/xorg.conf: That's odd. We changed the screen depth quite a bit with XO-1.5 development, I wonder if those changes accidentally reached XO-1 development builds? (For XO-1.5 we needed the firmware, the kernel, and X to all agree on depth so that suspend and resume would work nicely). -- James Cameron http://quozl.linux.org.au/ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: possible progress on XO-1 camera issues
Btw, Record in Sugar works with the same symptoms as Cheese in Gnome (that is, you can take pictures but you don't get a live feed). Hth, Raúl On Tue, 2009-12-22 at 21:42 -0300, Raul Gutierrez Segales wrote: > Hey guys, > > Is it cheating to change the screen depth? I change it to 24 bpp and now > cheese and totem work. Changes to /etc/X11/xorg.conf: > > (in the Screen Section) > > DefaultDepth 24 > > (in the Display SubSection) > > Depth 24 > > Cheese doesn't show live video from the camera but I am able to take > pictures. And totem reproduces video (no sound, but hey! that it is > another thread/ticket). > > Anything wrong with using X with 24bpp? > > I can feel F11 on the XO-1 near :) > > > > On Mon, 2009-12-21 at 23:21 +, Tomeu Vizoso wrote: > > Hmm, it's a bit hard to read with so many details, can you run it > > again without -v --leak-check=full --show-reachable=yes ? Those are > > useful when looking for memory leaks. > > > > I would expect that valgrind would complain when the uninitialized > > values get read. > > > > Thanks, > > > > Tomeu > > > > On Mon, Dec 21, 2009 at 20:13, crodas wrote: > > > Hi there, > > > On Sat, 19 Dec 2009 12:06:41 +, Tomeu Vizoso > > > wrote: > > >> On Sat, Dec 19, 2009 at 07:00, John Gilmore wrote: > > #10 0xb67fae59 in gst_xvimagesink_xvimage_put (xvimagesink=0x8364160) > > at xvimagesink.c:864 > > src = {x = 134867456, y = 140758336, w = -1259457208, h = 1} > > dst = {x = 137730309, y = 3, w = 0, h = 137691184} > > result = {x = 0, y = 0, w = 322, h = 241} > > draw_border = 322 > > __PRETTY_FUNCTION__ = "gst_xvimagesink_xvimage_put" > > > > The src.w value is in the same range as the Xlib function addresses; > > -1259457208 is 0x4B11CAB8 and as can be seen from the call frame #9 > > the XSync function is at 0x4b0eccf7. The other values seem > > irrational. This may be evidence that the stack has been corrupted > > somewhere else, or the values not initialised. > > >>> > > >>> Just to rule out going too far down a blind alley... > > >>> > > >>> Try adding a printf of these values to the code there, rather than or > > >>> in addition to using GDB. GDB may not be 100% reliable when accessing > > >>> variables from optimized code. (I used to maintain GDB, and I worked > > >>> very hard to make it never lie to you, but that precept hasn't always > > >>> been followed in the intervening decade, and optimizations have also > > >>> gotten a lot more complicated.) > > >>> > > >>> Or try compiling that code without -O and see if that changes either > > >>> its behavior, or what the debugger reports. > > >> > > >> At this point is when I would run totem in valgrind, I can help > > >> interpreting the output if it's not clear. > > >> > > >> # yum install valgrind > > >> $ valgrind totem > > > I hope it helps, > > > > > > http://oficina.paraguayeduca.org/~crodas/valgrind-debug.txt > > > > > > cheers, > > > > > >> > > >> Regards, > > >> > > >> Tomeu > > > > > > > > > > > ___ > 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
Re: possible progress on XO-1 camera issues
Hey guys, Is it cheating to change the screen depth? I change it to 24 bpp and now cheese and totem work. Changes to /etc/X11/xorg.conf: (in the Screen Section) DefaultDepth 24 (in the Display SubSection) Depth 24 Cheese doesn't show live video from the camera but I am able to take pictures. And totem reproduces video (no sound, but hey! that it is another thread/ticket). Anything wrong with using X with 24bpp? I can feel F11 on the XO-1 near :) On Mon, 2009-12-21 at 23:21 +, Tomeu Vizoso wrote: > Hmm, it's a bit hard to read with so many details, can you run it > again without -v --leak-check=full --show-reachable=yes ? Those are > useful when looking for memory leaks. > > I would expect that valgrind would complain when the uninitialized > values get read. > > Thanks, > > Tomeu > > On Mon, Dec 21, 2009 at 20:13, crodas wrote: > > Hi there, > > On Sat, 19 Dec 2009 12:06:41 +, Tomeu Vizoso > > wrote: > >> On Sat, Dec 19, 2009 at 07:00, John Gilmore wrote: > #10 0xb67fae59 in gst_xvimagesink_xvimage_put (xvimagesink=0x8364160) > at xvimagesink.c:864 > src = {x = 134867456, y = 140758336, w = -1259457208, h = 1} > dst = {x = 137730309, y = 3, w = 0, h = 137691184} > result = {x = 0, y = 0, w = 322, h = 241} > draw_border = 322 > __PRETTY_FUNCTION__ = "gst_xvimagesink_xvimage_put" > > The src.w value is in the same range as the Xlib function addresses; > -1259457208 is 0x4B11CAB8 and as can be seen from the call frame #9 > the XSync function is at 0x4b0eccf7. The other values seem > irrational. This may be evidence that the stack has been corrupted > somewhere else, or the values not initialised. > >>> > >>> Just to rule out going too far down a blind alley... > >>> > >>> Try adding a printf of these values to the code there, rather than or > >>> in addition to using GDB. GDB may not be 100% reliable when accessing > >>> variables from optimized code. (I used to maintain GDB, and I worked > >>> very hard to make it never lie to you, but that precept hasn't always > >>> been followed in the intervening decade, and optimizations have also > >>> gotten a lot more complicated.) > >>> > >>> Or try compiling that code without -O and see if that changes either > >>> its behavior, or what the debugger reports. > >> > >> At this point is when I would run totem in valgrind, I can help > >> interpreting the output if it's not clear. > >> > >> # yum install valgrind > >> $ valgrind totem > > I hope it helps, > > > > http://oficina.paraguayeduca.org/~crodas/valgrind-debug.txt > > > > cheers, > > > >> > >> Regards, > >> > >> Tomeu > > > > > ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
XO-3 official
http://www.forbes.com/2009/12/22/tablet-computer-negroponte-technology-cio-network-olpc.html "It aims to make its tablet PC highly durable, all plastic, waterproof, half the thickness of an iPhone and use less than a watt of power, despite an 8-gigaherz processor. The price: an unprecedented $75." Well, that's cool. Deciphering OLPC press releases sometimes feels like I'm playing chess with Picasso, and he keeps breaking the rules, and I can't tell whether this is some kind of art or he's just cheating. --Ben signature.asc Description: OpenPGP digital signature ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: powerd or ohm?
On Sunday 20 December 2009 10:28:53 Tomeu Vizoso wrote: > Hi, > > I think f11 for the XO 1.5 uses ohmd but from a recent message from > Paul I think the images for the XO-1 are configured to use powerd or > at least doesn't start ohmd by default. > > Steve, is there any plan on this? > > Thanks, > > Tomeu > The next release will have ohm by default Should be out early next week. Steven -- = Steven M. Parrish - gpg fingerprint: 4B6C 8357 059E B7ED 8095 0FD6 1F4B EDA0 A9A6 13C0 http://tuxbrewr.fedorapeople.org/ irc.freenode.net: Nickname: SMParrish Channels: #fedora-kde, #fedora-olpc, #fedora-edu, #sugar, #packagekit ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Fwd: Call for Proposals Now Open
Is anyone proposing sessions at OSCON 2010? Sameer -- Forwarded message -- From: O'Reilly Open Source Convention Date: Tue, Dec 22, 2009 at 9:06 AM Subject: Call for Proposals Now Open To: sve...@sfsu.edu OSCON, the O'Reilly Open Source Convention July 19 - 23, 2010 Oregon Convention Center Portland, OR http://post.oreilly.com/rd/9z1zqg35f3okn4qesojvehjcbgimp5vf30unksqjmog Faster, Freer, Smarter: Whatever your Goal, Make It Happen with Open Source More than 2,500 experts, developers, sys admins, and hackers will meet up at OSCON 2010 to explore the tools, services, and platforms that make up the vibrant open source ecosystem. Join us! The OSCON Call for Participation is now open. If you have winning techniques, favorite lifesavers, war stories, productivity tips, or other ideas to share, we want to hear from you. We're especially on the look-out for ways to do more with less, design and usability best practices, mobile device innovations, cloud computing, parallelization, open standards and data, open source in government, business models, and beyond. Speak up about the freedom--and opportunity--of open source at OSCON 2010. Submit your proposal by February 1, 2010 at: http://post.oreilly.com/rd/9z1zqdukhmk0ersdvuf0jrdsvnnrlket7uh2n1li7c8 -- You are receiving this message because you signed up to receive the OSCON newsletter. To change your newsletter subscription options, please visit http://post.oreilly.com/rd/9z1zj7b6hv78bichi8f6ecrppi4o5nbp8rfvrogt810. To ensure delivery to your inbox (not bulk or junk folders), please add conferen...@post.oreilly.com to your address book. Forward this announcement to a friend: http://post.oreilly.com/f2f/9z1z0l87haf88db1jf3ku3kc4kpbh39siafi9qbom30 If you would like to stop receiving any and all email announcements from O'Reilly, go to: http://post.oreilly.com/prefs/9z1zhvhfd17q0n1tq7n57t87s4q42kag6a7t34fbsg8. For assistance, email conf-ad...@oreilly.com O'Reilly Media, Inc. 1005 Gravenstein Highway North, Sebastopol, CA 95472 (707) 827-7000 / (800) 998-9938 -- ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Testing OS64 on XO1.5
On Tue, 2009-12-22 at 12:05 +, Ahmed MANSOUR wrote: > The network was working but after my upgrade to OS64, I can no longer > get connected so it is more a software issue and not only releasted to > B2 hardware. What type of network are you trying to connect to? What is the failure condition? (is there an error message?) Which version of the OS worked for you before? Are you 100% sure that the machine has not been into suspend before you try to connect to the network? Note that the screen is on as usual when the system is in suspend, and the machine immediately wakes up to keyboard and mouse activity -- it is not obvious that the suspend has actually taken place. Thanks, Daniel ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Testing OS64 on XO1.5
2009/12/20 James Cameron : > On Sun, Dec 20, 2009 at 01:20:37PM -0500, milan zimmermann wrote: >> 1) After reboot, or after a brief period of inactivity, the system >> sometimes does not connect to network, [...] > > Deficiency of the B2 hardware, won't be fixed in B2, but will be (is) > fixed in the next hardware revision. The network was working but after my upgrade to OS64, I can no longer get connected so it is more a software issue and not only releasted to B2 hardware. ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: ANN: rainbow-0.8.6 release.
On 22.12.2009, at 06:06, Michael Stone wrote: > > Friends, > > I am pleased to announce the release of rainbow-0.8.6. Rainbow implements > portions of the isolation shell described in the Bitfrost threat model and > security architecture. > > The key differences between this release and its predecessor include support > for garbage collection of uids, ui sugar for resuming uids, bug fixes to the > resume logic, and a simplified singly-linked list library. > > This release was made possible by encouragement and suggestions from Sascha > Silbe, Bernie Innocenti, and Benjamin Mako Hill. It has been (minimally) > tested > on Debian Sid, Ubuntu Karmic, and Fedora Rawhide and has been packaged in > Fedora Rawhide for your convenience. > > Interesting links for this release include: > > git:git://dev.laptop.org/users/mstone/security > tar: > http://dev.laptop.org/~mstone/releases/SOURCES/rainbow-0.8.6.tar.bz2 > browse: > http://dev.laptop.org/git/users/mstone/security/tree/?id=rainbow-0.8.6 > setup: http://wiki.laptop.org/go/Rainbow/Installation_Instructions > tests: http://wiki.laptop.org/go/Rainbow/Testing > > The shortlog from rainbow-0.8.5..rainbow-0.8.6 is: > > Bernie Innocenti (1): > Capture XAUTHORITY. > > Michael Stone (19): > Remove unused flexibility from the spool option parsing code. > First pass at updated rainbow-gc. > Clean up group membership. > Protect sticky uids from garbage collection. > Clean up some per-uid Xephyr data. > Improve spool detection checks. > Install rainbow-gc. > Add some logging to rainbow-gc. > Make xephyr usage resumable. > Teach rainbow to resume uids with more auxiliary groups. > Add a simple resume subcommand. > Add INIT() and COPY() operators from dnshash. > Add a novel singly-linked list implementation. > Add test_endgrent script. > Simplify list traversal logic. > Fix Karmic sudo segfault. > Tweak warnings and link flags. > Set default spool location in rainbow-gc. > rainbow-0.8.6. > > Kind regards, > > Michael Yay! - Bert - ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel