Re: [OLPC Engineering] [Techteam] New F14-arm build os21
by James Cameron
On Wed, Jul 20, 2011 at 06:40:55AM -0400, Martin Langhoff wrote:
> Once they learn that a particular key combination "finishes" runin
> earlier, accidents can happen with surprising frequency.
How is the power button being prevented?
If the problem is that an early termination is indistinguishable from a
test success, why not change runin accordingly? I'm happy to do that if
needed.
--
James Cameron
http://quozl.linux.org.au/
12 years, 4 months
[OLPC-SF] OLPC SF Community Summit 2011! Fri, Oct 21 - Sun, Oct 23
by rihoward1＠gmail.com
The OLPC_SF volunteers are planning the upcoming
OLPC SF Community Summit 2011.
The dates are
Oct 21 (registration and reception)
Oct 22 (full day)
Oct 23 (full day)
The web page will be activated in a couple of weeks.
Write back and let us know if you wish to help with organizing the event
or would like to be a presenter.
http://olpcsf.org/
12 years, 8 months
Re: [Techteam] New F14-arm build os31
by Peter Robinson
On Fri, Jul 29, 2011 at 5:34 AM, Gonzalo Odiard <gonzalo(a)laptop.org> wrote:
> Hey, no so bad :)
> The good news first:
> The following activities starts and works:
> TurtleArt, Speak, TypingTurtle, Labyrinth, Memorize,Browse, Log, Words,
> Help, Chat, Scratch, Distance, Finance,
> Infoslicer, Implode, Terminal, Calculate, Etoys and ImageViewer
>
> Activities with errors:
> GetBooks: no HAL (anyway we must substitute by udev)
>
Hal is built for F-14. I suspect nothing else is pulling it in. What does
GetBooks use HAL for?
> TamTam*: no blobs, probably only recompile
> Puppy: starts ok and many examples work, but no the camera and no sound
> examples (I have not tested all)
> Measure: no HAL
>
Hal is built for F-14. I suspect nothing else is pulling it in. What does
Puppy use HAL for?
> Stopwatch: do not start and do not write anything in the log file
> Write: no abiword module
>
Martin has a build, should be in the next release.
> Paint: no blobs, probably only recompile
> Moon: does not start, but with a python error in the activity, must try
> update it
> Jukebox, started but did not played a ogg file
> Record: starts but only with audio
> Physics: probably no binaries in egg, we must try with package pybox2d
>
I've pushed a F-14 build for this, is there a reason we can't use the distro
package so as to remove the binary module from the Activity?
> Maze: do not start and do not write anything in the log file
> Read: no module webkit
>
webkit is a real pain and causing me problems for building. It has a huge
and complex dependency chain that's failing. I'm getting there slowly but
its not a small package by any description.
>
> Gonzalo
>
>
>
> On Thu, Jul 28, 2011 at 5:35 PM, Martin Langhoff <martin(a)laptop.org>wrote:
>
>> On Thu, Jul 28, 2011 at 4:03 PM, Martin Langhoff <martin(a)laptop.org>
>> wrote:
>> > The "Switch to Fedora-14" build.
>> > http://build.laptop.org/F14-arm/os31/
>>
>> Looks like we have major framebuffer performance diference in F14.
>> Comparing os23 (f13) and os31 (f14), both with the same kernel...
>>
>> Camera to ximagesink is much better behaved. Quick test procedure
>>
>> - Boot into sugar
>> - open Teminal activity
>> - sudo /runin/runin-camera &
>> - click on terminal window, start top
>> - move pointer to a corner to get frame, bring forward the gts-launch
>> window, move it so that you can read top's top lines
>>
>> = os23 shows ~1% idle, 88.7user, 11%sys -- user time is split between
>> gst-launch (~70%) and X (~25%)
>> = os31 shows ~35% idle :-D -- 55% user, 6% sys -- gst-launch at 45%, X at
>> 2%
>>
>> Implode appears to be a bit faster too -- but it's hard to judge.
>>
>> cheers,
>>
>>
>>
>> m
>> --
>> martin(a)laptop.org -- Software Architect - OLPC
>> - ask interesting questions
>> - don't get distracted with shiny stuff - working code first
>> - http://wiki.laptop.org/go/User:Martinlanghoff
>> _______________________________________________
>> Techteam mailing list
>> Techteam(a)lists.laptop.org
>> http://lists.laptop.org/listinfo/techteam
>>
>
>
> _______________________________________________
> Techteam mailing list
> Techteam(a)lists.laptop.org
> http://lists.laptop.org/listinfo/techteam
>
>
12 years, 8 months
[Paris] SugarCamp the 10th and 11th of September
by Kévin Raymond
Hi there,
In case of interest, OLPC France NPO is organising a SugarCamp the
10th and 11th of September, in Paris, France. It is aimed to gather
foreign contributors from over the world in order to improve the
learning platform, focused on documentation. There will be a hack
session of course, ideas are welcome.
More information available in blog.laptop.org[1], and registration is
open at[2].
I am also planning to install Sugar on all computers of a workshop room.
I've seen that a new Sugar release is coming, do you have any
information about Sugar on a Stick under Fedora 16? I could install an
alpha in dual boot, and then update it before deploying the disk image
in every computers. But members here are more aware of the Fedora
Sugar implementation, any advices/links are welcome.
[1] http://blog.laptop.org/2011/07/20/registration-opens-for-sugarcamp-paris-...
[2] http://en.amiando.com/olpcfrance-sugarcamp2011.html?page=571392
Best Regards,
--
Kévin Raymond
User:shaiton
GPG-Key: A5BCB3A2
12 years, 8 months
Re: [fedora-arm] Confusion with arm koji
by Peter Robinson
On Tue, Jul 26, 2011 at 3:10 PM, Dan Horák <dan(a)danny.cz> wrote:
> Martin Langhoff píše v Út 26. 07. 2011 v 10:02 -0400:
> > On Tue, Jul 26, 2011 at 4:04 AM, Peter Robinson <pbrobinson(a)gmail.com>
> wrote:
> > > Its a known problem. Mash (or what ever it is that generates the koji
> build
> > > repo) uses some very random criteria for tagging packages into the
> build
> > > repo.
> >
> > It looks like the criteria is "most recently built" - which isn't very
> useful.
>
> the criteria is "most recently tagged" to be precise, the latest tagged
> build goes into the build repo
>
>
There's also added confusion with inheritance, so that a newer tagged
package on dist-f13 doesn't necessarily toast an older one on dist-f14.
Peter
12 years, 9 months
Confusion with arm koji
by Martin Langhoff
Peter, Fedorans,
I'm playing with test builds using F14 for arm. And I get strange
errors of f14 python packages that depend on python 2.6. And yet, when
I look at koji, it clearly has newer RPMs...
So for example, see python-decorator:
http://arm.koji.fedoraproject.org/koji/packageinfo?packageID=7698
Right now, it lists
python-decorator-3.2.0-2.fc14 pbrobinson 2011-07-23 10:55:56
python-decorator-3.2.0-3.fc14 pbrobinson 2011-05-25 19:47:30
The -3 package is newer, but was build earlier than the -2 package.
Looking at the changelog, the -3 rev is where the Python 2.7 rebuild
happened.
Now if I grab the pkg list, it offers python-decorator-3.2.0-2.fc14
http://arm.koji.fedoraproject.org/repos/dist-f14-build/latest/arm/pkglist
I've had similar problems with other Python packages. Anybody can help
me understand why? Any fixes? Workarounds?
cheers,
m
--
martin.langhoff(a)gmail.com
martin(a)laptop.org -- Software Architect - OLPC
- ask interesting questions
- don't get distracted with shiny stuff - working code first
- http://wiki.laptop.org/go/User:Martinlanghoff
12 years, 9 months
Contributors program - test and develop on XO-1.75 B1 prototypes
by Martin Langhoff
Hello developers!
Are you programming on XO hardware today? Working on Sugar core or
activities? Porting Fedora or other distros to ARM?
As I write this, XO-1.75 B1 prototypes are being assembled 20 meters
away from me. These are engineering samples -- some will go to drop
tests and mechanical and electrical torture tests. Luckier units will
go to the hands of passionate developers interested in helping us with XO-1.75.
To request one, please follow the instructions at
http://wiki.laptop.org/go/Contributors_program#FAQ
Be aware -- we cannot guarantee every request will be satisfied --
unfortunately, we have a limited number of units and we may have to
turn some requests down.
These units will be early samples: expect hardware and software bugs,
and be prepared to report them and help us in the diagnosis and fixing
(it wouldn't be fun otherwise!). We will be asking recipients to be
very proactive in reporting bugs and using the latest software for
them. And to remember that these machines are /on loan/: offer to pass
on your prototype if it is not being used.
It will be a fun 2011 -- our goal is to have a new hardware platform
and OS: XO-1.75 running XO OS-11.3.0, and there is a lot to do between
now and the end of the year.
hoping to hear from you -
martin
--
martin.langhoff(a)gmail.com
martin(a)laptop.org -- Software Architect - OLPC
- ask interesting questions
- don't get distracted with shiny stuff - working code first
- http://wiki.laptop.org/go/User:Martinlanghoff
12 years, 9 months
Announcing OLPC OS 11.2.0 for XO-1 and XO-1.5
by Daniel Drake
Hi,
We're pleased to announce the release of OLPC OS 11.2.0 for XO-1 and
XO-1.5. Details of new features, known issues, and how to
download/install/upgrade can all be found in the release notes:
http://wiki.laptop.org/go/Release_notes/11.2.0
Many thanks to all contributors, testers, upstreams, and those who
have provided feedback of any kind.
For those who were following the release candidate process in the last
few weeks: candidate build 874 is released as final with no changes.
Thanks and enjoy!
Daniel
12 years, 9 months
Re: New F14-arm build os21
by James Cameron
On Thu, Jul 21, 2011 at 12:14:14AM -0400, Martin Langhoff wrote:
> On Wed, Jul 20, 2011 at 6:04 AM, Martin Langhoff <martin(a)laptop.org> wrote:
> > On Wed, Jul 20, 2011 at 6:02 AM, Martin Langhoff <martin(a)laptop.org> wrote:
> >> ?- Updates olpc-utils to disable X zapping and fix serial port terminal
> >
> > Initial testing seems to indicate serial port needs a bit more
> > attention. I've also tested it with a newer kernel containing Paul's
> > tty config fix, and it doesn't make a difference.
>
> Looking at it again -- there is no apparent problem with using the
> serial port, only an early msg in var/log/messages
>
> Jul 21 04:07:36 localhost init: ttySx main process (33) terminated
> with status 1
I looked into this.
/etc/init/ttyS.conf says "start on startup", but if it is changed to
"start on runlevel [12345]" this strange message goes away. Perhaps it
is caused by some interaction with upstart's init, or perhaps we are not
following best practices in ttyS.conf.
(We have our own ttyS.conf, but curiously /etc/init/serial.conf might
have been starting a process, but it says it requires ttyS2 to be the
last or primary console in the kernel command line, and for it to be
listed in /etc/securetty. Doing those things doesn't cause serial.conf
to start a process though.)
> But nothing seems to be broken
>
> - shutdown/reboot works correctly (and the plymouth workaround has
> been removed)
> - switch to gnome / sugar works correctly
> - bash is respawned correctly if you exit
My gut feel is that we still have something lurking here, but nothing we
ship at the moment tries modem control on /dev/ttyS2. Not even
ModemManager, according to strace. (Pity it doesn't ignore USB serial
adapters as well.)
I looked briefly at the serial/pxa driver. When a user process
configures for modem control on /dev/ttyS2 via termios, the upshot is
the setting of bit AFE (Auto-flow Control Enable) in the UART MCR (modem
control register). Good.
During serial_pxa_startup, /dev/ttyS3 is configured for AFE
automatically. But I didn't see any obvious way at mmp2_add_uart time
to tell the driver not to bother setting UART_MCR_AFE for /dev/ttyS2.
The control lines themselves aren't exposed, which is presumably why
threads that do I/O hang.
But hey, the same thing happens on XO-1.5, just tested ... so we're good
to go. ;-)
--
James Cameron
http://quozl.linux.org.au/
12 years, 9 months
