Re: Logjam vulnerability and epiphany.

[Samuel Greenfeld]

While it is possible to partially fix the LogJam vulnerability, are there
plans to declare end-of-life or end-of-support for the older XO's?

A few years ago, we talked about ending support in 2020 when other Linux
distributions would stop distributing x86 processor builds.

And OLPC is not like the OpenWRT project, where developers have kept things
up-to-date even for legacy hardware.

---
SJG


On Sun, Aug 30, 2020 at 5:21 PM James Cameron  wrote:

> Yes, wikimedia servers will be unreachable.  That is their decision.
>
> Many other servers already do not permit connection, and this varies by
> geography of IP address, based on local laws or a server owner's assessment
> of market value.
>
> We have no plans to upgrade for XO-1.5.
>
> Is not a problem on NL3 or ED20 models with OLPC OS 20.04.
>
> On Sun, Aug 30, 2020 at 06:57:09AM -0700, pe...@easthope.ca wrote:
> > Hi,
> >
> > System 13.2.8 on a XO 1.5 here.
> >
> > Open epiphany and open
> > https://clienttest.ssllabs.com:8443/ssltest/viewMyClient.html .
> >
> > Logjam vulnerability is reported.
> > https://en.wikipedia.org/wiki/Logjam_(computer_security)
> >
> > A specific consequence is that a wikimedia server will not permit a
> > connection from this epiphany after September 25, 2020. Ie. Wikipedia
> > & etc. will become inaccessible with this browser.  =8~(
> >
> > I guess you fellas are aware of all that.  Is there any plan to
> > introduce an appropriate upgrade?
> >
> > Thanks,  ... Peter E.
> >
> > --
> > https://en.wikibooks.org/wiki/Medical_Machines
> > https://en.wikibooks.org/wiki/Oberon
> > Tel: +1 604 670 0140Bcc: peter at easthope. ca
> >
> > ___
> > Devel mailing list
> > Devel@lists.laptop.org
> > http://lists.laptop.org/listinfo/devel
>
> --
> James Cameron
> http://quozl.netrek.org/
> ___
> 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

Porting XO laptops to newer Linux kernels

[Samuel Greenfeld]

It has been a few years (Fedora 18) since the original XO Laptop series has
had any sort of major Operating System update.

In order to support newer versions of Systemd, features found in newer
versions of the Linux kernel are required.  And from limited exploratory
work done years ago, the XO-1 mesh networking & XO-1.5 Camera drivers may
need fixing even though they are in upstream kernels.

Are there any low-level kernel developers out there interested in porting
XO laptops (both x86 & ARM) to a Linux 4.x kernel or a later 3.x kernel so
they can be used with newer Linux distributions?  Or should we presume that
all public XO laptop development (apart from minor patching) is officially
dead at this point?

I presume hardware can be made available provided someone has the interest.

---
SJG
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Re: [UKids] re:new member

[Samuel Greenfeld]

The XO-4 is the only XO to have been officially sold with a touchscreen
option.

XO-4s use the same screen as other XOs, but with an independent infrared
touchscreen on top of it.

There were some XO-1.75s that were modified to have more traditional
touchscreens to help with Sugar & XO-4 touch development.  These are mostly
in the hands of developers, and are rare.

Over time durability enhancements have been made to XOs.  But I don't
recall when what changes were made to the display.

In general I would recommend using a newer display with touch XO-4s to
reduce the risk of hard presses breaking the screen.


On Sun, Apr 24, 2016 at 11:13 AM, robb  wrote:

> Sure the XO1 has no touch screen but was it the XO1.75 that had an option
> to have a touch screen? I don know if the xo1.75 and the xo4 have the same
> dimentions and connectors for the screens? Maybe you could fit an xo1.75
> screen on an xo4?
>
> Op 24-04-16 om 15:07 schreef Dave Crossland:
>
>
> On 24 April 2016 at 07:34, Xo Tom  wrote:
>
>> I would like to use the Lcd of the Xo1 in the Xo4, replacing them. Do you
>> think that works or could there be a problem with the touch function?
>>
>
> The XO-1 screen has no touch function
> --
> Unsung Heroes of OLPC, interviewed live @ 
> http://unleashkids.org !
> ---
> You received this message because you are subscribed to the Google Groups
> "Unleash Kids" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to unleashkids+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>
> --
> This message has been scanned for viruses and
> dangerous content by *MailScanner* , and is
> believed to be clean.
>
>
>
> --
> This message has been scanned for viruses and
> dangerous content by *MailScanner* , and is
> believed to be clean.
>
> --
> Unsung Heroes of OLPC, interviewed live @ http://unleashkids.org !
> ---
> You received this message because you are subscribed to the Google Groups
> "Unleash Kids" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to unleashkids+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Re: Compatibility of serial adapters

[Samuel Greenfeld]

If I recall correctly, the XO-1.5's serial adapter shares some circuitry
with the camera.  Booting an XO-1.5 with a serial adapter means you cannot
use the latter.

To do this, the XO-1.5 looks for a resistor placed across two of the wires
to see if a serial adapter is present.  No other XO laptop model has this
restriction.

Perhaps the older serial adapter simply lacks the sense resistor required
for the XO-1.5 to switch modes.



On Wed, Oct 21, 2015 at 5:15 PM, James Cameron  wrote:

> On Wed, Oct 21, 2015 at 11:38:02AM -0500, Peter Easthope wrote:
> > Seems that an adapter such as http://www.ebay.ca/itm/381346598663 ,
> > similar to the first generation adapter, might work.  [...]
>
> Doubt it.  The product description is inadequate, it does not state
> the serial voltage.  It does say supply voltage range.  It does not
> have any serial control signal strapping.  And it has an RS232
> connector, which nobody should need these days.  ;-}
>
> Get a USB adapter instead.  As long as the adapter is for 3.3V serial,
> it will work with the XO-1 host serial port.  The adapter is powered
> from the USB host.
>
> The same seller has a more appropriate adapter for a lower price:
>
>
> http://www.ebay.com/itm/USB-TTL-Converter-Module-LED-CP2102-RX-TX-3-3V-5V-Output-/381153344387?hash=item58be827b83
>
> There are now very many alternative adapters that are compatible.
>
> --
> James Cameron
> http://quozl.linux.org.au/
> ___
> 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: [XSCE] sdcard for /opt and /library on xo 1.5

[Samuel Greenfeld]

Would periodically erasing SD cards and eMMC storage help to extend their
useful life?  Or is this potentially dangerous for chips known to be used
which implement these instructions incorrectly?

A few years ago, XO firmware would erase the SD card prior to running
fs-update.  But if I recall correctly this was disabled because it caused
certain SD cards to hang.

It might also be possible to enable the eMMC equivalent of TRIM in XO
software builds provided XO eMMC's don't accidentally discard the wrong
block.




On Wed, Jul 15, 2015 at 12:09 AM, James Cameron  wrote:

> On Tue, Jul 14, 2015 at 11:49:29PM -0400, Tim Moody wrote:
> > I think the bottom line is that on this xo1.5 I need to use a usb thumb
> > drive instead of this micro sdcard and its holder.
> >
> > > -Original Message-
> > > From: xsce-de...@googlegroups.com [mailto:xsce-
> > > de...@googlegroups.com] On Behalf Of James Cameron
> > > Sent: Tuesday, July 14, 2015 8:14 PM
> > > To: Tim Moody
> > > Cc: server-de...@lists.laptop.org; devel@lists.laptop.org; xsce-
> > > de...@googlegroups.com
> > > Subject: Re: [XSCE] sdcard for /opt and /library on xo 1.5
> > >
> > > G'day Tim,
> > >
> > > Thanks, that's interesting.
> > >
> > > My best guess is you have a bad connector and the 24-hour thermal test
> you
> > > did fixed it.  The problem may return.
> > >
> > > Another guess is that the card has the production state awareness
> feature
> > > [1], part of e.MMC v5.0, which uses the storage cells differently
> before
> > they
> > > are enabled for normal use.  The state can be changed with suitable
> tools,
> > or
> > > will clear itself once enough data is written; followed by a power
> cycle.
> > The
> > > result is a sudden increase in performance after that power cycle.
> > >
> > interesting ideas.  I have no way of judging either.
> >
> > My guess is that I tried so many different ways of partitioning it from
> > fdisk to parted that it was so messed up that an xo 1.5, a nuc, and a
> dell
> > all found it corrupt, compounded by the fact that systemd has it in use
> even
> > if it is not actually mounted.
>
> Yes, it sounds like you lost track of the provenance.
>
> At heart though, an SD card is just a set of blocks, so I always make
> a copy of it before writing.  The copy usually compresses really well
> for permanent storage.
>
> >
> > The sdcard holder is also looking pretty suspect as used with the card
> slot
> > on the xo.  I put the micro sd in the holder back into the xo 1.5 and it
> > reported two devices with pttype of "dos", but gave unknown file system
> when
> > I tried to mount
> >
> > -bash-4.2# mount
> > /dev/mmcblk1p1 on /bootpart type ext4 (rw,relatime,user_xattr,barrier=1)
> > /dev/mmcblk1p2 on / type ext4
> (rw,noatime,user_xattr,barrier=1,data=ordered)
> > devtmpfs on /dev type devtmpfs
> > (rw,nosuid,relatime,size=475460k,nr_inodes=118865,mode=755)
> > /dev/mmcblk1p2 on /home type ext4
> > (rw,relatime,user_xattr,barrier=1,data=ordered)
> > /dev/mmcblk1p2 on /versions type ext4
> > (rw,relatime,user_xattr,barrier=1,data=ordered)
> > /dev/mmcblk1p1 on /security type ext4 (rw,relatime,user_xattr,barrier=1)
> > proc on /proc type proc (rw,relatime)
> > sysfs on /sys type sysfs (rw,relatime)
> > tmpfs on /dev/shm type tmpfs (rw,relatime,size=51200k)
> > devpts on /dev/pts type devpts (rw,relatime,gid=5,mode=620)
> > tmpfs on /run type tmpfs (rw,nosuid,nodev,mode=755)
> > tmpfs on /sys/fs/cgroup type tmpfs (rw,nosuid,nodev,noexec,mode=755)
> > cgroup on /sys/fs/cgroup/systemd type cgroup
> >
> (rw,nosuid,nodev,noexec,relatime,release_agent=/usr/lib/systemd/systemd-cgro
> > ups-agent,name=systemd)
> > cgroup on /sys/fs/cgroup/cpu type cgroup
> > (rw,nosuid,nodev,noexec,relatime,cpu)
> > systemd-1 on /proc/sys/fs/binfmt_misc type autofs
> > (rw,relatime,fd=27,pgrp=1,timeout=300,minproto=5,maxproto=5,direct)
> > hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime)
> > debugfs on /sys/kernel/debug type debugfs (rw,relatime)
> > mqueue on /dev/mqueue type mqueue (rw,relatime)
> > vartmp on /var/tmp type tmpfs (rw,relatime,size=51200k)
> > /tmp on /tmp type tmpfs (rw,relatime,size=204800k)
> > none on /var/lib/stateless/writable type tmpfs
> > (rw,relatime,size=4096k,nr_inodes=2048)
> > none on /var/cache/man type tmpfs (rw,relatime,size=4096k,nr_inodes=2048)
> > none on /var/lib/xkb type tmpfs (rw,relatime,size=4096k,nr_inodes=2048)
> > none on /var/cache/httpd/ssl type tmpfs
> > (rw,relatime,size=4096k,nr_inodes=2048)
> > none on /var/cache/httpd/proxy type tmpfs
> > (rw,relatime,size=4096k,nr_inodes=2048)
> > none on /var/cache/php-pear type tmpfs
> > (rw,relatime,size=4096k,nr_inodes=2048)
> > none on /var/lib/dav type tmpfs (rw,relatime,size=4096k,nr_inodes=2048)
> > none on /var/lib/dhclient type tmpfs
> (rw,relatime,size=4096k,nr_inodes=2048)
> > none on /etc/adjtime type tmpfs (rw,relatime,size=4096k,nr_inodes=2048)
> > none on /var/lib/logrotate.status type tmpfs
> > (rw,relatime,size=4096k,nr_inodes=2048)

Re: Two (minimal) goals for a kernel for XO1.5 based upon fc22?

[Samuel Greenfeld]

Given I looked into this before with F22 Beta(*), I ran OLPC OS Builder
tonight, excluding nothing from all repositories, and let it loose.

There were a few more minor issues found with the build process.  But I
managed to build an image with the stock Fedora 4.x kernel, and primarily
F22 parts.

However the stock Fedora kernel does not have a hardcoded kernel command
line like OLPC kernels do, and trying to manually provide the command line
to boot a Fedora kernel still hung for me after OFW stated the ramdisk was
being loaded.

I may look into this a bit more before resorting back to OLPC's 3.10 kernel
and seeing what works with that.

(*) http://lists.sugarlabs.org/archive/sugar-devel/2015-April/050035.html

On Wed, May 27, 2015 at 6:28 PM, James Cameron  wrote:

> On Wed, May 27, 2015 at 06:31:28AM -0700, George Hunt wrote:
> > If I set just the goals of getting keyboard input, and display output,
> what
> > problems will I face trying to use defconfig_xo1.5 from [1]
> dev.laptop.org
> > (x86-3.3 branch)?
> >
> > Does anyone have a config file that works on the XO1.5 on a Fedora
> release
> > later than FC18 that I might springboard from?
>
> We used the olpc-3.10 branch to generate kernels for systems later
> than Fedora 18.
>
> --
> James Cameron
> http://quozl.linux.org.au/
> ___
> 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: [Sugar-devel] Community XO software builds

[Samuel Greenfeld]

There are at least two types of "deployments"/"customers" that Sugar has.

The first is the small, volunteer group.  To them, it doesn't matter what
OS they actually are using, or (to some extent) how well tested things
are.  They just want to come in, try something with their students, and if
they need to tweak something or something breaks, it's no big deal.

The second is the large deployment.  And large deployments, like large
corporations, do not want to deploy Sugar widely unless they have a chance
to thoroughly check it out.


First, they might investigate a bit to see who currently uses Sugar, and if
there are any other users they can get recommendations from.  Then they
might look into Sugar Labs, asking about Sugar's history, what warranties
were available, the future roadmap for features, etc.  They may insist on
having a face-to-face meeting with a Sugar representative, where they could
ask detailed questions.

You might laugh but when the OLPC Association was actively answering bids
for laptops, this dance happened all the time.

When large corporations sell things to each other, support can be
everything.  It doesn't mean that they are going to use it.  But if they
need a patch for critical bug on the President's laptop, or the latest
Shellshock or Heartbleed that their bosses' boss' saw in the news, they
want to have something or someone they can point to definitely get support.

Very few deployments have invested in the resources to internally make
their own OS images at that level of detail.


I don't want to go into it too much in this email, but dealing with large
organizations can be a very different thing.



On Fri, May 8, 2015 at 1:37 AM, Tony Anderson  wrote:

> I don't know what is puzzling. I can understand a deployment wanting
> assurance of long-term support for Sugar. I doubt there are many
> deployments that even know what Fedora or Ubuntu means. Even fewer that
> understand the difference between SugarLabs and Red Hat or Canonical as
> sources of this support.
>
> The word deployment may be a puzzle, In some cases it as a national
> ministry or OLPC Australia. For most of us, it is a school or other
> institution which has acquired OLPC laptops and is attempting to make use
> of them.
>
> There are many deployments which have never updated their image. In
> general, an update to an XO requires someone to come to the school
> with the technical expertise to do so. I am sure there are schools which
> have never seen such a visitor since they received their laptops.
> The positive element is that the laptops work as they always have. The
> downside, of course, is that the users have no chance to benefit from
> the new capabilities available from current releases.
>
> Finally, what urgent security fixes are required by a deployment with no
> access to the internet?
>
> Tony
>
>
> On 05/08/2015 12:55 AM, sugar-devel-requ...@lists.sugarlabs.org wrote:
>
>> When I talked with deployments and they ask for Ubuntu,
>>> >and I ask why, what they really want is Long Time Support.
>>> >No deployment change their image more than once a year.
>>> >In fact, change a image is a logistic challenge for most of
>>> >the big/middle size deployments.?
>>>
>> This continues to puzzle me.  LTS is a stream of security updates, and
>> you say the deployments do not apply them until the next year?
>>
>> And yet they want them?
>>
>> They want something they don't use?
>>
>
> ___
> Sugar-devel mailing list
> sugar-de...@lists.sugarlabs.org
> http://lists.sugarlabs.org/listinfo/sugar-devel
>
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Re: [Sugar-devel] Community XO software builds

[Samuel Greenfeld]

The obvious counterargument would be that a deployment might want to deploy
your XO-Next (whatever it is) alongside existing XO laptops, allowing all
of them to have the same configuration.

There's plenty of blame to go around in terms of re-inventing the wheel and
lack of communication.

There simply (and correct me if I'm wrong) are not the resources inside of
OLPC, outside, or combined at this time to maintain and update two separate
builds & build systems.

It amazes me how far we bend over backwards to avoid saying "end of life"
and "end of support".


I have seen a fair amount of interest, both publicly and privately, for
newer XO laptop builds.  But I don't think the requesters realize how much
work it takes to make one.

And I do not forsee anyone stepping up to get the XO-1.75 and XO-4 kernel &
drivers into a state they can be upstreamed or upgraded for newer Fedoras
unless a deployment really wants this instead of newer equipment.

Newer operating systems tend to require more disk space and RAM than the
predecessors.  We have seen this even within Fedora's lineage.


Since OLPC already appears to be going the Ubuntu LTS route, I would argue
it would be easiest to take everything that way, porting utilities as
required, and make that the final image & build system for XOs.

I only have a limited number of hours per week I can look into OLPC things,
but I'm tempted to take a look.






On Wed, May 6, 2015 at 10:50 PM, James Cameron  wrote:

> On Wed, May 06, 2015 at 09:29:46PM -0400, Samuel Greenfeld wrote:
> > It might be possible for this new builder to be eventually taught to
> > handle XOs.
>
> There was no significant interest in my previous builder uxo, which
> already knows how to handle XOs.  The recent posts on devel@ of people
> trying something similar without looking at uxo is further evidence of
> that.
>
> So for the moment, there seems to be no need for my new builder to
> handle XO-1, XO-1.5, XO-1.75 or XO-4 laptops.  The Fedora based
> builder is working fine for those laptops.
>
> --
> James Cameron
> http://quozl.linux.org.au/
>
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Re: [Sugar-devel] Community XO software builds

[Samuel Greenfeld]

I will try to answer some questions.  But my last two points will only
raise new ones.


   1. There are a few purposes for the community build.  The first is that
   for a while, all the OLPC builds announced seemed to be private ones
   available upon request.  It therefore was necessary to see if builds were
   still possible without the private extensions, and how well they worked.

   A second is that I actually build against a local mirror.  This mirror
   was created back when it was uncertain if OLPC would keep the MIT servers,
   and expanded when said servers started running into problems.  (These
   issues have since been resolved.)

   OLPC has and may still have an automatic backup; but I recall others
   having to stop it from accidentally pulling corrupted data in the past.

   Although it only has a subset of the public OLPC content available
   anonymously, building against my mirror makes sure that it still works and
   that it is periodically made up to date.


   2. I have uploaded the .ini files I use to
   http://www.greenfeld.org/xo/community/builds/14.1.0/olpc-os-builder/ .
   But there is nothing in them that you could not derive from the
   olpc-14.1.0*.ini files already in olpc-os-builder.

   The .zd SD card image for XO-1 build 2 is next to it's .img file.

   I added a pause at the end of kspost.75.install_bundles.inc so I can
   tweak the XO-1 image and remove some of the larger activities.  But this is
   temporary for debugging only.


   3. Since I am based in the US, I cannot generate images with the
   multimedia items due to patents.  At best I could give you instructions
   similar to how OLPC already does.

   I vaguely recall all XO-4's might be licensed for many multimedia codecs
   but it would be up to OLPC to make those images more widely available.


   4. Personally I would argue that a CentOS or another long-term build may
   be the best approach for XOs.  Sugar is in EPEL 6, and likely could be
   added to EPEL 7.

   It should surprise no one at this point that the list of personnel on
   OLPC's web site is years out of date.  There may be more people working on
   XSCE at the moment than XO laptop software.

   Given the lack of personnel and resources I believe it would be best to
   do one final build for XO-1 through XO-4 based on a LTS distribution
   supported to at least 2020, and then only minor security/fixes after that.


   5. OLPC already is looking beyond the XO, and beyond Fedora.  If you
   look at dev.laptop.org closely, you might notice a bunch of tickets
   targeted for "su-15.1" as well as a new olpc-ubuntu-sugar-builder git tree
   meant for standard PCs.

   This appears to be an Sugar 0.104/Ubuntu 14.04 LTS build with anti-theft
   provided by a secure-boot-based EFI bootloader, not Open Firmware.

   While I am not thrilled that this has been done without the historical
   community's involvement, it likely matches the need of the XO Infinity or
   another client who currently pays the bills.

   It might be possible for this new builder to be eventually taught to
   handle XOs.

   But if OLPC is looking beyond the XO-4, perhaps it's time that Sugar do
   so as well.

   More information can be found at http://dev.laptop.org/ticket/12881





On Wed, May 6, 2015 at 7:18 PM, James Cameron  wrote:

> On Wed, May 06, 2015 at 10:49:47AM -0400, Adam Holt wrote:
> > They all seem to want a better browser and better codec support to
> > view various+sundry videos, within Sugar ideally, but if that's not
> > possible then within Gnome.  One group per week asks me for the
> > above, above all else (often more than one deployment/group per
> > week).
>
> Why isn't this reaching me and the people who would do something about
> it?  Please count these requests, deidentify and aggregate them, and
> report them monthly on devel@ or sugar-devel@
>
> > But if CentOS is not realistically achievable, F22 might be more
> > appropriate, given it's final freeze is supposed to be less than 1
> > week away?
>
> The size of this task (F22) has not yet been estimated, but based on
> Samuel's write up, my guess is between 10 and 50 engineer hours.
>
> There may be other problems lurking.
>
> The Fedora 20 port just on XO-4 has consumed way more than this.
>
> --
> James Cameron
> http://quozl.linux.org.au/
> ___
> Sugar-devel mailing list
> sugar-de...@lists.sugarlabs.org
> http://lists.sugarlabs.org/listinfo/sugar-devel
>
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Community XO software builds

[Samuel Greenfeld]

I saw some discussion last week about the community XO software builds.

This seems to be something which gets many people excited.

However according to my web server, there have not been very many downloads
of them.

If I may ask:

   - Who actually is using/testing these images?
   - Why?
   - Is there a reason you are not looking into using an official (OLPC or
   deployment) build?
   - Have you engaged OLPC or another party to work on changes?
   - What direction do you believe the builds should go?

Building XO builds by repacking existing work is relatively trivial.

But the low-level kernel, driver, and OS work necessary to support XOs with
newer operating systems (as well as newer XO batteries) is something I
cannot do, and where we really need help.

Without guidance from OLPC or others, I could build thousands of XO-#
laptop images.  But unless it looks like a significant number of
deployments/children actually would benefit, there really is no point.

---
SJG
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Re: XO Fedora 22 Beta work

[Samuel Greenfeld]

James and I looked a bit into the systemd issue last night & discovered the
same.  This was discussed at
http://lists.sugarlabs.org/archive/sugar-devel/2014-May/048180.html

A solution to solve this may be tricky.  Currently no one may be available
to look into getting newer Linux kernels working on XOs.  And if a newer
kernel was tweaked for XOs and brought in, extensive testing against
multiple XO models & variants (wireless cards/cameras/memory chips/etc.)
would be required.

Bringing in an older systemd with userspace firmware loading support might
be easier in the short term, but could break RPMs dependent on newer
systemd versions.

I don't know what resources OLPC has internally at the moment, but this may
be beyond what part-time volunteers can do, especially if support is
desired for XO models which OLPC no longer sells.


On Sat, Apr 25, 2015 at 6:05 PM, Dennis Gilmore  wrote:

> On Saturday, April 25, 2015 10:36:49 PM Peter Robinson wrote:
> > On Sat, Apr 25, 2015 at 5:10 AM, Samuel Greenfeld 
> wrote:
> > > At James' suggestion I looked a bit into a Fedora 22 beta build.  I
> have
> > > found the following problems so far getting the RPM dependencies worked
> > > out:
> > >
> > > olpc-library needs to depend on python-jinja2, not python-jinja.  The
> > > olpc-library RPM also was removed from Fedora, perhaps due to lack of
> > > changes & abandonment.
> >
> > Likely, I didn't even know it existed.
> >
> > > totem-mozplugin no longer exists and was intentionally removed.  Given
> > > Firefox supports various media codecs internally this might not be a
> > > problem for it (apart for vmeta?); but I don't know what webkit-based
> > > Browse uses for media players.
> >
> > Gstreamer based as well so I don't see any major issue there except if
> > vmeta doesn't support gstreamer 1.0
> >
> > > xorg-x11-drv-keyboard and -mouse have been replaced by
> > > xorg-x11-drv-libinput.  See
> > > https://fedoraproject.org/wiki/Changes/LibinputForXorg
> >
> > Works fine on SoaS, although I think there might be a need to migrate
> > Control Panel bits, I did send an email about it some time ago to
> > devel@
> >
> > > 14.1.0 has custom F20 systemd binaries, but I am having trouble finding
> > > information as to why.  If they have relevant changes they need to be
> > > ported to F22 if not already present because using the F20 systemd
> > > binaries breaks all sorts of library dependencies.
> >
> > The reason is due to changes in firmware loading changes in the kernel
> > and the fact the XO kernels haven't been rebased to something more
> > modern than 3.0+
> >
> > > Patches have been written for the first three that I could submit.
> > >
> > > We need to come up with a clear direction as to what volunteers and/or
> > > OLPC
> > > want & would actually use for updated XO builds.  I only have the time
> to
> > > focus on one set of images.
> >
> > I can help on anything needed that's in Fedora in terms of adding
> > patches there so you don't need to fork but similarly I don't have
> > much time.
>
> with Fedora.NEXT we may be able to look at making OLPC builds be an
> official
> part of Fedora, tirckiest bit I think would be the kernel. Long term I
> think
> it would be good for both OLPC and Fedora for this to happen.
>
> Dennis
> ___
> 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

XO Fedora 22 Beta work

[Samuel Greenfeld]

At James' suggestion I looked a bit into a Fedora 22 beta build.  I have
found the following problems so far getting the RPM dependencies worked out:

   - olpc-library needs to depend on python-jinja2, not python-jinja.  The
   olpc-library RPM also was removed from Fedora, perhaps due to lack of
   changes & abandonment.
   - totem-mozplugin no longer exists and was intentionally removed.  Given
   Firefox supports various media codecs internally this might not be a
   problem for it (apart for vmeta?); but I don't know what webkit-based
   Browse uses for media players.
   - xorg-x11-drv-keyboard and -mouse have been replaced by
   xorg-x11-drv-libinput.  See
   https://fedoraproject.org/wiki/Changes/LibinputForXorg
   - 14.1.0 has custom F20 systemd binaries, but I am having trouble
   finding information as to why.  If they have relevant changes they need to
   be ported to F22 if not already present because using the F20 systemd
   binaries breaks all sorts of library dependencies.

Patches have been written for the first three that I could submit.

We need to come up with a clear direction as to what volunteers and/or OLPC
want & would actually use for updated XO builds.  I only have the time to
focus on one set of images.
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Re: [UKids] Re: "XOs cannot act as WiFi access points"

[Samuel Greenfeld]

If I recall correctly, Android devices cannot connect to Ad-hoc networks
out-of-the-box.  There may be some third party utilities which allow
certain devices to do this with varying levels of success.

Instead, either one device is configured as an AP, or a newer-than-Adhoc
standard called WiFi Direct is used.

Android devices may also communicate amongst themselves using Bluetooth,
although creating mesh networks/Internet gateways again would require
third-party utilities.  One such utility (Open Garden) partnered with OLPC
for the XO Tablet (
http://www.prnewswire.com/news-releases/one-laptop-per-child-partners-with-open-garden-to-grow-internet-everywhere-220497161.html
).

In general, generic Android to Android device communication was an unsolved
problem the last time I looked into this.


On Mon, Mar 16, 2015 at 10:42 PM, Adam Holt  wrote:

> On Mon, Mar 16, 2015 at 10:36 PM, James Cameron  wrote:
>
>> On Mon, Mar 16, 2015 at 09:30:30PM -0500, Jerry Vonau wrote:
>> > On March 16, 2015 at 9:23 PM James Cameron  wrote:
>> > >
>> > > There's no need to go as far as configuring as an access point when
>> > > ad-hoc networking will work, with suitable configuration of the other
>> > > laptops connecting to it.
>> >
>> > Has sugar addressed http://bugs.sugarlabs.org/ticket/3708?
>>
>> Why would you use Sugar?
>>
>
> We'd love to keep some/any version of Sugar on the XO if possible, even if
> just so the librarian can putter.
>
> Important: how compatible is the XO's Ad-Hoc networking with generic
> Android tablets/phones and generic/vintage cheap laptops already out there
> in the world?  Any other low-to-medium complexity protocols we should be
> considering, for XO-1.5 and higher especially, that might plausibly sail
> with a few weeks of hacking?  (that is if a genuine WiFi hotspot brings
> more compatibility)
>
> Anyway: scalability's not a requirement (in this case!) as such community
> libraries are tiny, having a couple WiFi devices attached generally, rarely
> more.
>
> --
> Unsung Heroes of OLPC, interviewed live @ http://unleashkids.org !
> ---
> You received this message because you are subscribed to the Google Groups
> "Unleash Kids" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to unleashkids+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Re: [Sugar-devel] Community OS 14.1.0 Version 2

[Samuel Greenfeld]

No; these are unsigned images which only can be installed on unlocked
laptops via fs-update (such as "fs-update u:\41002qq4.zd" if the image is
in the root directory of a USB stick).

These images also do not have the licensed codecs or accelerated video
drivers OLPC has obtained for XO-4s and certain deployment's older XOs, as
these are not distributed publicly.

The activities I have are what James chose at
wiki.laptop.org/go/Activities/14.1.0 , minus Wikipedia and Physics on the
XO-1.

In general we need to determine what should be include in the XO-1 builds,
as the internal flash storage only has 1 GB of space.  Over time newer
versions of Fedora have resulted in larger XO images, and there is only so
much we can do to compensate for that.


On Thu, Mar 5, 2015 at 9:30 AM, Thomas Gilliard 
wrote:

>  Don't I need a fs4.zip also?
>
> Tom Gilliard
>
> On 03/05/2015 06:25 AM, Samuel Greenfeld wrote:
>
>  No this isn't the build that runs off an SD card.
>
>  If there is that much interest I will re-build the XO-1 image with the
> additional SD card image tonight.
>
>  Apart from the XO-1, the olpc-os-builder configurations I am using are
> basically what you see in OLPC's Git repository, with the "xx" changed to
> "qq" and "Community Build" added as the name of the deployment.
>
>
> On Thu, Mar 5, 2015 at 9:20 AM, Sebastian Silva  > wrote:
>
>> Downloading
>>
>> http://www.greenfeld.org/xo/community/builds/14.1.0/build_2/xo-1/41002qq0.img
>> for XO1 now.
>>
>> Is this the one that runs off of SD card?
>>
>> I'm interested for Perú, but as you can imagine, it doesn't depend on
>> me. Our team (Platform team + SomosAzucar) did build the last official
>> image Peru is using so who knows.
>>
>> Just for your reference, we built the image in 2011, they tested it (and
>> we fixed it) all 2012 and they deployed it in 2013-2014.
>>
>> It would be good to make something available that is more up to date,
>> even if it's not an "official" update.
>>
>> Regards,
>> Sebastian
>>
>>
>> El 05/03/15 a las 07:06, James Cameron escibió:
>>  > On Thu, Mar 05, 2015 at 06:55:13AM -0500, Samuel Greenfeld wrote:
>> >> The updated images can be found at
>> http://www.greenfeld.org/xo/community/
>> >> builds/14.1.0/build_2/
>> > I've heard there may be one or two microdeployments some interested in
>> > SD card builds on XO-1.  If you want to cover that, add the module
>> > [sd_card_image] to your .ini file.  Let me know if it is broken.
>> >
>>
>>
>
>
> ___
> Devel mailing listDevel@lists.laptop.orghttp://lists.laptop.org/listinfo/devel
>
>
>
> ___
> 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: [Sugar-devel] Community OS 14.1.0 Version 2

[Samuel Greenfeld]

No this isn't the build that runs off an SD card.

If there is that much interest I will re-build the XO-1 image with the
additional SD card image tonight.

Apart from the XO-1, the olpc-os-builder configurations I am using are
basically what you see in OLPC's Git repository, with the "xx" changed to
"qq" and "Community Build" added as the name of the deployment.


On Thu, Mar 5, 2015 at 9:20 AM, Sebastian Silva 
wrote:

> Downloading
>
> http://www.greenfeld.org/xo/community/builds/14.1.0/build_2/xo-1/41002qq0.img
> for XO1 now.
>
> Is this the one that runs off of SD card?
>
> I'm interested for Perú, but as you can imagine, it doesn't depend on
> me. Our team (Platform team + SomosAzucar) did build the last official
> image Peru is using so who knows.
>
> Just for your reference, we built the image in 2011, they tested it (and
> we fixed it) all 2012 and they deployed it in 2013-2014.
>
> It would be good to make something available that is more up to date,
> even if it's not an "official" update.
>
> Regards,
> Sebastian
>
>
> El 05/03/15 a las 07:06, James Cameron escibió:
> > On Thu, Mar 05, 2015 at 06:55:13AM -0500, Samuel Greenfeld wrote:
> >> The updated images can be found at
> http://www.greenfeld.org/xo/community/
> >> builds/14.1.0/build_2/
> > I've heard there may be one or two microdeployments some interested in
> > SD card builds on XO-1.  If you want to cover that, add the module
> > [sd_card_image] to your .ini file.  Let me know if it is broken.
> >
>
>
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Community OS 14.1.0 Version 2

[Samuel Greenfeld]

I have updated the XO-1/1.5/1.75/4 images I previously made.

The updated images can be found at
http://www.greenfeld.org/xo/community/builds/14.1.0/build_2/

Again, these images are not supported by OLPC.

It would be useful to know who actually might actually deploy these images,
as there has not been much of a response so far.  There are relatively few
people working on XO software at the moment, and we need more help in order
to create a polished release.

Bug reports about these images can be filed in dev.laptop.org with the
"commbuild" keyword.

Changes from the last build:

   - Sugar 0.104 is now included.
   - The language control panel problem appears to just be a first-boot
   issue.  If broken, rebooting should allow the language control panel to
   work.
   - On XO-1, the Linux kernel has been downgraded to a Fedora 18/Linux 3.8
   OLPC/XO kernel to solve the excess CPU usage.  But mesh networking is not
   coming online, and collaboration on XO-1 may be more generally broken.

Known major issues still outstanding:

   - The XO-1.5 camera (OLPC #12858) and suspend (OLPC #12859) problems
   still exist.
   - On XO-4, programs may randomly crash (OLPC #12837).
   - On XO-4, the on-screen keyboard does not appear in ebook mode, and
   cannot be used (OLPC #12865).
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Re: Firmware q7c04

[Samuel Greenfeld]

>From the "community build" perspective, I am waiting to see how many people
download and/or provide feedback before making a significant number of them.

So far, more search engines than users have downloaded the build I released
on Monday.

Given the significant barrier to entry (you must have an XO to use them) I
don't know how many volunteers remain who are willing to help test &
maintain builds other than those officially supported by OLPC.  And it is
unclear how much help OLPC can provide except in areas which they are
actively engaged with deployments to work on.



On Sat, Feb 14, 2015 at 8:55 AM, Yioryos Asprobounitis 
wrote:

> Nice to see the list back up and running.
> According to the info XO4 firmware q7c04 "support(s) booting legacy
> android kernel"
> However both os32013a4 and 3214a4 fail to boot under q7c04.
> Do they qualify as "legacy android kernel"?
>
> BTW is there any official or community SMP android/sugar builds in the
> works?
> ___
> 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

Community OS 14.1.0 Version 1

[Samuel Greenfeld]

I spent a few hours this past weekend looking into if third-party XO OS
builds were still possible.

The result is a set of unsigned XO laptop images for XO-1/1.5/1.75/4 I have
uploaded to http://www.greenfeld.org/xo/community/builds/14/1/

This is the first time images may have been made for certain models this
release cycle.   So this release has bugs, and is meant only for testing.
The XO-1 image in particular should be avoided unless you are trying to
solve its performance problems.

These images were created independently of OLPC and are not supported by
OLPC.

Bug reports about these images can be filed in dev.laptop.org with the
"commbuild" keyword.  However other members of the community are needed to
help fix problems as my skills are limited.


If you would prefer to use the latest OLPC-provided open-source build, it
can be found at http://build.laptop.org/14.1.0/os8/


Known improvements (from usage/researching changelogs):

   - All: The GNOME desktop has been replaced by MATE.
   - All: Wikipedia EN and ES have been replaced by the Simple English
   Wikipedia activity.
   - All: The latest Open Firmware for each platform.
   - All: Based on Fedora 20 & Sugar 0.103.2 with most Fedora updates as of
   early February 2015.
   - All (userland)/XO-4(OFW): Brightness adjustments for an upcoming
   manufacturing backlight LED change.  Laptops with new backlights will be
   identified by a "BL" manufacturing tag.   Routines to handle earlier
   backlights exist.  Note there may be some more backlight tweaks in the next
   version of powerd.
   - XO-4: Support for newer and larger eMMC internal storage options.
   - XO-4: LiPoly battery support (instead of NiMH).
   - XO-4: Dual core CPU Support.

Known issues:

   - All: This is not a "restricted" build, and does not have any licensed
   codec/binaries/video drivers some deployments may want.
   - All: Sugar asks for a user's grade and gender.  If this is sent over
   the Internet, this may not be legal in many countries without the
   appropriate parent/school permissions.

   These images therefore probably should not be given to children until we
   have a better understanding of what is going on.
   - All: The Sugar Language control panel appears to be broken.
   - All: MATE has the same large text/dpi display problems GNOME had if
   not worse.
   - All: Originally a private RPM repository was created for several x86
   RPMs where only ARM ones existed.  The relevant x86 ones have since been
   built and the last RPM I'm told isn't needed, so a private repository
   should not be required going forward.

   - XO-1: NetworkManager and systemd-journald use up most of the CPU
   logging repeated failed actions against the mesh(?) network adapter,
   leaving too little CPU for Sugar to work with.

   Some other services may also be using CPU, but these seem to be the most
   persistent (OLPC #12860).
   - XO-1: MATE, Simple English Wikipedia, and Physics were removed to
   conserve space while debugging the above.  There may only be room for
   either MATE or Simple Wikipedia with a more complete build, as this only
   leaves ~100 MB free.
   - XO-1: There is no "G1G1Lite"-style activity set at this time.

   - XO-1.5: Camera and/or video overlay support appears to be broken (OLPC
   #12858).
   - XO-1.5: Automatic suspend is disabled in this build due to the DCON
   freezing the text console instead of the graphical UI (OLPC #12859).
   - XO-1.5: This build may be too large for 2 GB SD cards (not tested, but
   observed).

   - XO-1.75: If you have one of the rare XO-1.75s with a touchscreen, the
   latest versions of OFW do not have "test /touchscreen" support (and may not
   have for some time).

   - XO-4: Programs may randomly crash due to OLPC #12837.  So building
   14.1.0 on an XO-4 using 14.1.0 currently is not supported.
   - XO-4: Due to Open Firmware and EC updates to support LiPoly batteries,
   XO-4s with newer firmware no longer are compatible with NiMH batteries
   (rare and should only affect users with pre-release SKUs).
   - XO-4: If you wish to downgrade from this OS to 13.2.2 or prior, you
   need to reinstall an Open Firmware version in the Q7B* series, such as
   Q7B44 or earlier (Q7B40 or earlier with NiMH).
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Re: [XSCE] Large groups of XO-1 do not work with access points

[Samuel Greenfeld]

I would also point out that if you have 20+ clients at a location you
should consider using commercial or enterprise-grade access points.

Companies like Aruba Networks make APs which each can contain multiple
radios, and support handing off clients between radios and access points
depending on available load.

This functionality does not come cheap.  The last time I talked to someone
from Aruba at a trade show their cheapest access point that could
self-configure itself with others on the same network (to avoid paying for
a centralized controller) was a few hundred dollars per AP.



On Fri, Feb 7, 2014 at 5:22 PM, James Cameron  wrote:

> On Fri, Feb 07, 2014 at 09:29:46AM -0500, Tim Moody wrote:
> > [Don't forget that James wrote:]
> > >If you choose to deploy with interfering channels for some reason,
> >
> > Many routers support narrowing the band around channels.
>
> No, it is more correct to say that many routers support widening the
> band around channels, to achieve a higher data rate.
>
> Consider a spectrum; the X axis is frequency, the Y axis is signal
> strength.  The bandwidth of the transmitter is a curve shaped like a
> hill.  The bandwidth of the receiver is another curve.  The channel
> selects the centre X position of the hill.
>
> The certification defines an area as a rectangle, and routers and
> devices pass certification based on spectrum analysis of the
> transmission, not of reception.
>
> There is always an interference between all channels, but the standard
> defines the limits on the interference in quantifiable terms.  But
> these can be translated simply as:
>
> - the interference between 1 and 11 is trivial,
>
> - the interference between 1 and 6 is low,
>
> - the interference between 1 and 2 is significant.
>
> - the interference between 1 and 1 is extreme.
>
> The interference causes backoff, where a node that would transmit
> waits a bit longer, and collisions, where a node receives a corrupted
> transmission.  Both of these act to reduce total system data
> bandwidth.
>
> Given fixed channels, the interference increases as the distance
> between the interfering devices decreases.
>
> > Are you of the opinion that this is ineffective and that there is
> > always a 5 channel overlap?
>
> I'm of the opinion that widening the bandwidth used around channel 6
> will impact channel 1 more.
>
> > Of course, we do not always have control over the entire
> > environment, so 1, 6, and 11 may already be taken and we have no say
> > in the matter.
>
> It is more complex than that.  While you might see another access
> point on a channel, you might still be able to deploy your own access
> point on the same channel, and the two access points will cooperate in
> a limited fashion.  They listen before they transmit.  So too do the
> laptops.  The TCP/IP rates are reduced.
>
> If you are faced with 1, 6, and 11 all taken, and you wish to run
> one access point, then find which of 1, 6 and 11 have the least
> received power, and use that.
>
> If you are faced with 1, 6, and 11 all taken, and you wish to run two
> access points, then find which two of 1, 6 and 11 have the least
> received power, and use them.
>
> If you are faced with 1, 6, and 11 all taken, and you wish to run
> three access points, use 1, 6, and 11.
>
> If you wish to use a channel outside 1, 6, and 11, then you would do a
> more complex survey, to find the channel with the least received power
> for both your access point and your devices.  Then measure the TCP/IP
> rates you get.
>
> That survey is invalidated every time someone walks in with an Android
> or iOS phone or a portable hotspot; these act as an access point.
>
> --
> James Cameron
> http://quozl.linux.org.au/
>
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Re: [Sugar-devel] seeking help to enable nepali keyboard input for XO-4

[Samuel Greenfeld]

If these are the SKU 311 units the Manufacturing Data on the wiki implies
they have membrane keyboards.

If so I don't see any reason using the keyboard manufacturing tags used for
previous Nepali manufacturing runs (or used testing out the settings in
/etc/sysconfig/keyboard manually) shouldn't work.  The %/X key will just
become the language key again.

But if no virtual keyboard exists for Nepali you will not have
touchscreen/virtual keyboard access to that language.



On Fri, Nov 8, 2013 at 11:41 AM, Walter Bender wrote:

> I believe Basanta said that they were the hard click keyboards
>
> On Fri, Nov 8, 2013 at 11:39 AM, Daniel Drake  wrote:
> > On Thu, Nov 7, 2013 at 11:23 PM, Basanta Shrestha
> >  wrote:
> >> But for XO-4 we will just be getting ones with English layout. I was
> >> wondering how we can enable nepali keyboard input on it.
> >
> > Are these keyboards hard/clicky/high-school style, or soft/membrane?
> >
> > Daniel
> > ___
> > Devel mailing list
> > Devel@lists.laptop.org
> > http://lists.laptop.org/listinfo/devel
>
>
>
> --
> Walter Bender
> Sugar Labs
> http://www.sugarlabs.org
> ___
> Sugar-devel mailing list
> sugar-de...@lists.sugarlabs.org
> http://lists.sugarlabs.org/listinfo/sugar-devel
>
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Re: [Sugar-devel] Activity Central's Sugar related priorities.

[Samuel Greenfeld]

This actually is kind of what I meant (and perhaps should be a separate
thread).

My understanding is that deployments nowadays are the primary parties
funding Sugar development.  And the deployments or their contractors
sometimes duplicate work, run into debates upstreaming things, and/or may
choose to keep some things semi-private to differentiate their products.

So apart from major functionality like HTML5 activities, a lot of
peripheral development is happening downstream-first.  And when we do try
to do major cross-group development like the GTK3 port, this has lead to
finger-pointing behind the scenes where it is claimed others are not doing
what they promised.

To the best of my knowledge no single organization currently employs enough
developers and/or contractors to keep Sugar development alive.  I am not
certain what the best approach to take is when this is the case.


On Mon, Oct 7, 2013 at 6:22 PM, James Cameron  wrote:

> On Tue, Oct 08, 2013 at 12:00:47AM +0200, Daniel Narvaez wrote:
> > Well "everyone seems to be developing their own version of Sugar"
> > seems to be more than that. But maybe I'm just reading too much into
> > it.
> >
> > There aren't multiple groups of people or individuals developing
> > sugar on their own. As far as I know all the work that is being done
> > these days is going upstream.
>
> Good.  I only know of four Sugars.  Sugar upstream, Dextrose, what is
> in OLPC OS, and what is in the Australian builds.  There might be
> more, but I'm not aware of them.  I also don't know the difference
> between each.
>
> --
> James Cameron
> http://quozl.linux.org.au/
> ___
> 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: Activity Central's Sugar related priorities.

[Samuel Greenfeld]

Disclaimer: These are my personal views, and are not the official views of
OLPC.


   - It should be fine to discuss anything Sugar-related on the
   sugarlabs.org development lists.  Sugar Labs does not use any OLPC
   hosting services, and is an independent group as part of the Software
   Freedom Conservancy.

   - I cannot comment on future OLPC hardware plans.  If OLPC was to
   publicly announce their intent to go in a similar direction the
   laptop.org mailing lists might be appropriate; however otherwise they
   may not be.

   It sounds like you are discussing a software change for different
   hardware than anything OLPC related though.

   Other vendors besides OLPC have sold laptops with Sugar preinstalled on
   top of Fedora or Ubuntu in the past, so you are not breaking new ground.

   - Updating the Sugar release in Ubuntu sounds like something everyone
   could benefit from, not just Dextrose users.  Is there any reason not to
   base most of this work starting with upstream Sugar & existing Ubuntu
   packages?

   - In general one of my frustrations lately is that now that we no longer
   publicly review patches on this mailing list, everyone seems to be
   developing their own version of Sugar.

   While some of these changes may make it back upstream it would be nice
   to see EduJAM and OLPC-SF discussion about trying to limit this.

   I know Activity Central is trying to publicly state a bit what they're
   up to, and Walter does his weekly "state of the union" reports.  I also
   personally hear some private updates as well.  But the different working
   styles of the various groups is starting to confuse me as to which way
   Sugar is going as a whole.




On Mon, Oct 7, 2013 at 12:41 PM, David Farning  wrote:

> As a data point for other decision makers and a follow up to some of
> the recent threads on the future of Sugar, I would like to share
> Activity Central's Sugar priorities for the next six months.
>
> Activity Central supports the recent HTML5 + JS work that is going
> into sugar .100. It has the potential to take the OLPC vision to any
> device which runs a browser while simultaneously increasing the
> potential activity developer pool by several orders of magnitude. This
> is an excellent area for community lead research. Activity Central
> will be doing activity side work to test the viability of the
> framework for client deployments.
>
> As a more incremental approach, Activity Central will continue our
> deployment-centric work by porting Dextrose to Ubuntu. A concern among
> deployments is the future availability of hardware to support their
> current investment. Deployments are concerned that laptop support will
> stop before tablets are ready for use in the field. Because of the
> controversial nature of this work and the potential for disruption it
> may cause to the Association, we understand if some people would
> prefer to sit this out.
>
> Would either of these list be appropriate to continue these
> discussions about this downstream efforts to port sugar to Ubuntu for
> use on hardware not sold by the Association?
>
> Phase one has been a poof of concept as seen at
> http://wiki.sugarlabs.org/go/Ubuntu (ongoing)
> Phase two will be opening the project to the community.
> Phases three will be testing and piloting by deployments.
>
> --
> David Farning
> Activity Central: http://www.activitycentral.com
> ___
> 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: adding a new CA root certificate

[Samuel Greenfeld]

Unlike Firefox (which has its own PKI and certificate authority support),
Webkit uses the system CA database.

You therefore should add the desired CA to the directory of system CA
certificates, the location of which varies a bit by distribution and
version.

With Fedora 19 (not yet used for a XO laptop release) the new Shared
Systems Certificates feature (
http://fedoraproject.org/wiki/Features/SharedSystemCertificates) also comes
into play.



On Wed, Aug 21, 2013 at 1:22 PM, Jerry Vonau  wrote:

> Hi all:
>
> What steps must I take to install a new root CA certificate so Browse
> can use it? When I click on the hyperlink of the certificate it gets
> downloaded to the journal unlike firefox or older Browse where you are
> prompted.
>
> Thanks for any hints,
>
> Jerry
>
> PS, this is a resend of an email that was sent to sugar-devel &
> olpc-devel, this list doesn't like having 2 email addresses in the "To"
> line.
>
> ___
> 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: [Sugar-devel] Fwd: [XSCE] Re: Client side Moodle transparent auth broken in 13.2.0 stable

[Samuel Greenfeld]

I reimaged & registered a XO-1.75 and a XO-4 with 13.2.0 to a XS-0.7
schoolserver.  Afterwards I opened Browse, and was able to open
http://schoolserver/ to login to Moodle without problems.

This does not mean that there is not a bug with 13.2.0, XS, and/or XSCE;
but one thing you could try is to fully stop and restart the Browse
activity after registering if the first login attempt does not work.
Sometimes I have found this helps.


On Tue, Aug 6, 2013 at 11:14 AM, Gonzalo Odiard  wrote:

> I don't have a school server to try.
> You should fill a ticket on bugs.sugarlabs.org
> cced: Manuel Quiñones, who maintain Browse activity.
>
> Gonzalo
>
>
> On Tue, Aug 6, 2013 at 12:08 PM, Jerry Vonau  wrote:
>
>> Think it's more of a question of looking for confirmation. Is anybody
>> else seeing this behavior on 13.2.0-13 on XO-1s when used with any version
>> of school-servers? I'm at a loss trying to explain why this is occurring to
>> Anna. With the noted behavior where would you file the bug report? OLPC is
>> what I'm thinking but looking if someone else might be impacted also or can
>> confirm this.
>>
>> Jerry
>>
>>
>> On 6 August 2013 05:12, Gonzalo Odiard  wrote:
>>
>>> There are a ticket filled?
>>>
>>> Gonzalo
>>>
>>>
>>> On Tue, Aug 6, 2013 at 4:27 AM, Jerry Vonau  wrote:
>>>
 Great piece of deductive testing Anna, way to go. Forwarding for
 further investigation.

 Jerry

 -- Forwarded message --
 From: Anna 
 Date: 5 August 2013 15:02
 Subject: [XSCE] Re: Client side Moodle transparent auth broken in
 13.2.0 stable
 To: xsce-devel 


 I just realized that someone will probably ask what's the most recent
 build where Moodle transparent auth did work.  Lucky for me, I just had to
 test one older.  Moodle transparent auth DOES work in 13.2.0-12.

 So whatever broke client side Moodle transparent auth should be
 confined to 13.2.0-13.


 On Mon, Aug 5, 2013 at 2:19 PM, Anna  wrote:

> I very recently upgraded my little herd of XOs to the latest stable
> build 13.2.0-13.  Unfortunately, something in that build has broken
> Moodle's transparent authentication.  When a registered client goes to
> http://schoolserver/moodle, all it gets is the login page.
>
> Now, that's not unheard of, you can usually just click the "Home"
> button and get automatically logged in.  But when I've seen that before,
> the XO's SN is filled out in the Username field on the login page.  The
> 13.2.0-13 XO doesn't show that.  No matter what you click on in the Moodle
> login page, it never logs in.
>
> To verify it was a client side issue, I flashed an XO-1 with 13.1.0
> stable, and registered first to be admin.  I also registered a 13.2.0-13 
> as
> the second client.  On the 13.1.0, I can go to the Moodle homepage and it
> automatically logged me in.  I tried again to access the Moodle homepage 
> on
> the 13.2.0-13 XO-1, but yep, still just got the login page.  On the admin
> XO, I went to Site Administration -> Users -> Accounts -> Browse list of
> users and saw both XOs listed.  It indicated that the 13.2.0-13 client had
> never logged in.
>
> So, the user account is being created on the server for the 13.2.0-13
> XO upon registration, but client side transparent authentication is not
> working.
>
> To verify the 13.2.0-13 XO's Browse Activity is accepting cookies, I
> went to
> http://www.bu.edu/htbin/computing/browsers/troubleshooting/cookietest.pland
>  the test was successful.
>
> Now, I have successfully tested Moodle transparent auth with previous
> iterations of 13.2.0, perhaps 8 or 9?  So whatever change on 13.2.0 that
> broke transparent auth must have been relatively recent.
>
> I took a look at the Browse Activity version between the two clients:
> 13.1.0 = Browse 149
> 13.2.0-13 = Browse 149.3
>
> I knew it wouldn't make a difference, but I also tested the 13.2.0-13
> as first registration and it doesn't care that its the admin user.  And
> also tested with a fresh flash to make sure there wasn't something sticky
> in there from a previous registration gumming things up.
>
> I've tested this with the XSCE installed a couple days ago
> (xs-config-0.8.4.123.gda5e8e3-1) and the latest DXS from this morning.  I
> also remembered I have an XS 0.6 (duh, Anna) and the results were the 
> same.
>  I don't have an XS 0.7 installation, but I would expect the same results.
>
> Since this is a client side issue, I'm not sure where to go from here
> as far as troubleshooting.
>
> Anna
>



 ___
 Sugar-devel mailing list
 sugar-de...@lists.sugarlabs.org
 http://lists.sugarlabs.org/listinfo/sugar-devel


>>>
>>
>
> ___

Re: Request for mDNS name resolution from Internet-in-a-Box project

[Samuel Greenfeld]

Looking into this a bit more, what I am seeing may be dependency specific.

If you are lucky enough to have a XO image that has extra items added,
nss-mdns may be present as a dependency.  Otherwise it is not.

I could have sworn this worked at one point in this past though because I
have definitely pinged .local addresses when testing collaboration.



On Wed, Jul 31, 2013 at 6:39 PM, James Cameron  wrote:

> Thanks.  I hit this yesterday.
>
> We already have some mDNS support present for Sugar collaboration in a
> network when a School Server is absent; we have the Avahi packages,
> but as you rightly point out we don't have the name service switch
> module for mDNS, and so a gethostbyname(3) doesn't look at that
> namespace.
>
> I have looked for but cannot see evidence of it being removed, it
> seems it was simply not included.
>
> Does mDNS for Internet-in-a-Box work for you in the face of the
> enthusiastic suspend of our automatic power management feature?
>
> What would prevent a network intruder, or a malicious user of OLPC OS,
> from supplanting http://know.local ?
>
> Installing nss-mdns as an RPM during XO customisation is practical if
> you use the right customisation tools, which in order of complexity
> are:
>
> - unlock the laptops and use the xo-custom script in mktinycorexo,
>   thanks to Jerry,
>
> - unlock the laptops and make your own build, with the patch below,
>
> - sign an xo-custom script with deployment keys.
>
> Waiting for the next OLPC OS build is an option, but I don't know when
> that will be.  I've raised ticket #12730 to track the enhancement request.
>
>
> From bc224068e4976fce2cbbc4de9378f4cb425027fe Mon Sep 17 00:00:00 2001
> From: James Cameron 
> Date: Thu, 1 Aug 2013 08:31:01 +1000
> Subject: [PATCH] add mDNS support for host name resolution
>
> ---
>  modules/base/kspkglist.10.core.inc | 3 +++
>  1 file changed, 3 insertions(+)
>
> diff --git a/modules/base/kspkglist.10.core.inc
> b/modules/base/kspkglist.10.core.inc
> index 857157c..1ff5b4c 100644
> --- a/modules/base/kspkglist.10.core.inc
> +++ b/modules/base/kspkglist.10.core.inc
> @@ -55,3 +55,6 @@ usb_modeswitch-data
>
>  # provides firewall-offline-cmd, needed for kickstart
>  firewalld
> +
> +# support mDNS name resolution for local network content repositories
> +nss-mdns
> --
> 1.8.1.2
>
>
> --
> James Cameron
> http://quozl.linux.org.au/
> ___
> 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: Request for mDNS name resolution from Internet-in-a-Box project

[Samuel Greenfeld]

Are you sure a change is required?

I just tried connecting using a randomly-grabbed 12.1.0 machine to a
network-connected printer (http://hp-model_id.local/) via HTTP and it
worked fine.


On Wed, Jul 31, 2013 at 6:20 PM, Braddock  wrote:

> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 07/31/2013 03:17 PM, Paul Fox wrote:
> > Fedora and most Linux distros (not to mention Macs) support mDNS
> > out of the box, yet for some reason it is turned off in OLPC OS.
> > I believe all that is required is the addition of the nss-mdns
> > package to the OLPC OS build.
> >
> >> if it's that simple, can your deployments simply do that
> >> installation with yum?  or is there something else missing,
> >> either from the laptop, or from my understanding?
>
> That would require installing nss-mdns on each and every XO laptop in
> each school, and doing it again every time an XO was upgraded.  Not
> feasible.  It needs to be done upstream.
>
> - -braddock
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v1.4.11 (GNU/Linux)
> Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
>
> iQEcBAEBAgAGBQJR+Y3IAAoJEHWLR/DQzlZuETIH/j+0Glx3vNu/wjlmb3oEyRVz
> pQ6ONyu7ESAcnqE1WWfx70BNW5lpuaFsLbuUKHrR3s7IqmsdTYV7nUCtSnKZOAR1
> DtJ1gtP1JQXIPirDC1wPvp3CdgLPGrt/YLlmOhYGZRXUabJamQS0bzvk7z0qq2f4
> S2hHEB7xpMCvrWLdRxUJvMl4a/I7IedlK3y34nicS2nRGHefiE/gAHyyXHPXj08p
> JtDxm0ycmOKCaPipGfKOX54aazhRs4aZLSrUKfChaJg3E1TTdHMSPUilrC/kivpg
> /NzROcCUQc0Jk0I+zcustLtyPsMkFz7i34vlUHn+bRo9NMg+koXUcaxuzCBOgmM=
> =UVWi
> -END PGP SIGNATURE-
> ___
> 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: Sound issue with XO 1.75 related to OFW version

[Samuel Greenfeld]

It sounds like you are trying to upgrade firmware without upgrading your OS.

As of Q4D26 the startup sound was moved to be stored on the internal
storage instead of in the firmware.  The two beeps therefore are expected
if the OS does not have a copy of the startup sound on disk to use.

Which OS are you trying to run?  If you use the version of firmware include
with the sound within the operating system should work properly.

There was an issue with some older firmware versions where if you muted the
startup sound by turning down the audio level all the way down when the
system was first booting, then audio in Linux would not work.  So make sure
you hear at least something during startup.



On Sun, Jul 21, 2013 at 9:38 AM,  wrote:

> ** **
>
> Hi all,
>
> ** **
>
> I’ve got a sound issue on a XO 1.75 that seems to be related to firmware
> version.
>
> ** **
>
> In Q4D34
>
> The sound test on firmware works perfectly: both playing and recording.***
> *
>
> At startup, instead of the sweet XO sound I’ve got two short Beep.
>
> No activity can’t play sound: neither Tam-Tam mini, Speak, Browse, …
>
> I’ve tested the FixSound activity (http://wiki.laptop.org/go/FixSound)
> without more luck.
>
> ** **
>
> When I downgrade firmware to Q4B10, the sound work normally both in
> firmware test and in Sugar activities.
>
> Q4B10 is mentioned to be the last firmware for A2 and A3 (
> http://wiki.laptop.org/go/Firmware#XO-1.75). 
>
> Does it mean that the XO is an A2 or A3 model?
>
> Is there any way to check it?
>
> ** **
>
> The XO is a reference SKU203 and have serial SHC20600096.
>
> ** **
>
> Best regards from France.
>
> ** **
>
> Lionel.
>
> ** **
>
> ** **
>
> ___
> 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: [support-gang] [Server-devel] 1TB drive of quality open content on XO/XS--won't boot

[Samuel Greenfeld]

NTFS is supported in OLPC builds, just not by the OS Kernel itself.

The ntfs-3g "filesystem in userspace" package can be used to mount NTFS
drives.  So you should be able to use a command like "mount -t ntfs-3g
/dev/ntfs_partition /mnt/mountpoint" if Sugar or GNOME do not automatically
mount the filesystem for you.

In general many Linux distributions seem to currently consider using
ntfs-3g a better approach than using the kernel driver.  The in-kernel
driver still may not have full NTFS write support, while ntfs-3g does.



On Mon, May 13, 2013 at 9:32 AM, Yioryos Asprobounitis
wrote:

> OLPC kernels do *not* support NTFS (# CONFIG_NTFS_FS is not set).
> It either should be activated in future builds or use another FS.
> I believe tha FAT32 (VFAT) can handle big drives and  is universal.
> However it has a number of other problems that may not suit your needs
> (reliability, permissions etc)
>
>
> --- On Mon, 5/13/13, Braddock  wrote:
>
> > From: Braddock 
> > Subject: Re: [support-gang] [Server-devel] 1TB drive of quality open
> content on XO/XS--won't boot
> > To: "James Cameron" , "Holt" , "XS
> Devel" , "Support Gangsters" <
> support-g...@laptop.org>, "Devel's in the Details"  >
> > Date: Monday, May 13, 2013, 8:02 AM
> > Hi James
> > I'm using OpenFirmware Q7B26  EC Firmware 0.4.03
> >
> > I have tried turning the "boot" flag off on the NTFS
> > partition, but it
> > still dumps me to the OpenFirmware ok prompt.
> >
> > I can reproduce the problem by formatting a USB stick to
> > NTFS and trying
> > to boot with it plugged in.
> >
> > So it is reacting badly to the mere presence of NTFS on USB
> > media.
> >
> > -braddock
> >
> > On 05/12/2013 03:40 PM, James Cameron wrote:
> > > On Sat, May 11, 2013 at 03:44:18PM -0400, Holt wrote:
> > >> Is there a way to boot a large USB hard drive
> > attached to an XO?
> > >> At our XS Community Sprint this week outside
> > Toronto, we've been
> > >> unable to boot XOs with the 700+ GB drive(s)
> > containing very
> > >> polished open content provided by http://internet-in-a-box.org
> > >> The XOs (eg. XO-4 etc) refuse to auto-boot, leaving
> > the screen at
> > >> the OK prompt.
> > >>
> > >> FYI our 1TB disk is a nearly complete snapshot of:
> > >> * Wikipedia-in-41-languages, thumbnails for most
> > all images
> > >> * OpenStreetMap for the whole world cached at all
> > zoom levels for
> > >> fast display
> > >> * Gutenberg Prjct's full collection of 40,000+
> > books, images
> > >> * Khan Academy's ~4000 video classes, etc
> > >>
> > >> Does firmware currently block the mounting of all
> > large USB drives
> > >> -- NTFS in this case if not other filesystems?
> > > Open Firmware tries the first partition that is marked
> > bootable.
> > >
> > > Exactly what it does next depends on the firmware
> > version, but clearly
> > > in your case it stops booting.
> > >
> > >> Might there be a workaround so isolated XO servers
> > in Haiti (etc!)
> > >> can hopefully auto-boot with this quality free
> > content?
> > > Turn off the bootable flag using a partitioning
> > program, ensure you
> > > are using latest firmware Q7B30, and attach a serial
> > console for
> > > further debugging.
> > >
> > > If you can tell me how to reproduce the symptom, then
> > I'm quite sure I
> > > can get it fixed.  I certainly can't afford to
> > download 700 GB or 1 TB
> > > to do that though.
> > >
> > > I'm happy to work with whoever has the drive and an
> > XO-4.
> > >
> > > The nature and value of the content has no relationship
> > to the
> > > diagnosis process, but is interesting regardless.
> > >
> >
> > ___
> > support-gang mailing list
> > support-g...@lists.laptop.org
> > http://lists.laptop.org/listinfo/support-gang
> >
> ___
> support-gang mailing list
> support-g...@lists.laptop.org
> http://lists.laptop.org/listinfo/support-gang
>
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Re: OS Builder output img ?

[Samuel Greenfeld]

The "fs0.zip" file would only appear if you configured everything to make a
signed build.  You would only be able to make a signed build if you had a
copy of the private keys for the deployment you are making the signed build
for.   Only OLPC has the keys to make a signed build that pretty much any
XO-1 will accept.

The .crc and .img files, when copied to USB, etc., are enough to install
the image on a unlocked XO-1 with a command like "copy-nand
u:\21007xx0.img" from the "ok" Open Firmware prompt (available if you press
the "ESC"/(X) key while the startup sound plays on unlocked units).



On Sun, Mar 24, 2013 at 4:53 AM,  wrote:

> Hi all,
>
> ** **
>
> Thanks to the nice documentation on the Wiki, I’ve successfully created my
> first OS Build.
>
> For the moment, it’s just a 12.1.0 without any customization but I’m very
> proud of this first step! :-)
>
> Now I want to deploy it on my unlock XO-1 but I’m slightly disappointed by
> the output of the build.
>
> I expected to have something like a “fs0.zip” file and a “21021o0.img”
> file but here is the content of the output directory:
>
> ** **
>
> total 2124968
>
> -rw-r--r--. 1 root root383 Mar 22 22:37 21007xx0.activities.txt***
> *
>
> -rw-r--r--. 1 root root  46485 Mar 22 22:25 21007xx0.crc
>
> -rw-r--r--. 1 root root 694986 Mar 22 22:37 21007xx0.files.txt.gz
>
> -rw-r--r--. 1 root root  676986880 Mar 22 22:25 21007xx0.img
>
> -rw-r--r--. 1 root root 47 Mar 22 22:26 21007xx0.img.md5
>
> -rw-r--r--. 1 root root150 Mar 22 22:37 21007xx0.libraries.txt
>
> -rw-r--r--. 1 root root  22541 Mar 22 22:36 21007xx0.packages.txt
>
> -rw-r--r--. 1 root root8348832 Mar 22 22:11 21007xx0.toc
>
> -rw-r--r--. 1 root root  448624505 Mar 22 22:36 21007xx0.tree.tar.lzma
>
> -rw-r--r--. 1 root root 57 Mar 22 22:36 21007xx0.tree.tar.lzma.md5
> 
>
> -rw-r--r--. 1 root root 1041203200 Mar 22 22:29 21007xx0.usb
>
> ** **
>
> I guess that the “21007xx0.img” file is the “21021o0.img” file I’m looking
> for but where is the “fs0.zip” file?
>
> Sorry, it’s probably a stupid question but I’m an absolute beginner on
> that!
>
> ** **
>
> Best regards from France.
>
> ** **
>
> Lionel.
>
> ** **
>
> ** **
>
> ___
> 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: 13.1.0 build 36 released for XO-4

[Samuel Greenfeld]

Write can collaborate with os36, although it looks like you might be able
to share things from the sharing XO-4 and not get data back from joining
XOs.

Distance when shared over ad-hoc works as well as Chat and Maze through a
schoolserver.  The distances shown look like they might be close to
correct.  When registered to a schoolserver Browse logs into Moodle as
expected.

A secured 1.2 GHz C1 XO-4 can activate itself over wifi from a XS with a
delegated lease as well as get updates when "olpc-update-query" is manually
run after schoolserver registration.

While two activities can play audio at the same time, this does not mean
that you can play music in one and record it in Record.  Some activities
(like TamTam) may try to quiet themselves shortly after you switch focus
away from them.

Wifi (WMM or similar) power saving is turned off, so the wifi LED will not
flash while associated to an AP which supports doing this at this time.
Aggressive suspending while the laptop is off is also turned off.

There still are some video driver issues like the corrupted cursor upon a
full lid-close-using suspend & resume cycle.


On Fri, Mar 8, 2013 at 4:03 PM, Daniel Drake  wrote:

> Hi,
>
> Here's an XO-4 build with some new fixes.
>
> http://download.laptop.org/xo-4/os/candidate/13.1.0-36/
>
> Changes are:
>
> Write-87 fixes collaboration (SL#4436)
>
> Simultaneous audio recording/playback should be working now (#12606).
> The Distance activity is working.
>
> Wireless 8787 power saving is disabled, matching 8686. Solves some
> unreliability issues with collaboration.
>
> Automatic power management is temporarily disabled by default. We are
> still battling some stability issues with suspend/resume and wakeups.
>
>
> Thanks for testing!
> 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

Re: 13.1.0 build 32 for XO-4 released

[Samuel Greenfeld]

This build is basically usable.  Graphics glitches still exist, as the
video driver has not been updated yet.  The Record activity can now record
audio on XO-4, although Scratch cannot.

If you are working with collaboration with this XO-4 build you should turn
off automatic power management in Sugar.  The disabling of Wake on LAN
support causes the wifi card is powered down every suspend cycle, and
therefore cannot sense if another user does something while the first XO
aggressively suspends.

I saw a case where the 8787 card in a XO-4 C1 claimed to be busy (as seen
by "iwlist scan") and could not scan or associate to an AP until
NetworkManager was shutdown & restarted.  This may have caused due to
disconnecting from one AP to connect to another, but nothing obvious was
seen in /var/log/messages to explain the situation.


On Tue, Feb 26, 2013 at 5:44 PM, Daniel Drake  wrote:

> Hi,
>
> Another XO-4-only build is available.
>
> http://download.laptop.org/xo-4/os/candidate/13.1.0-32/
>
> (build 31 was an internal-only release and was broken)
>
> Changes since build 30 are:
>
> Wake-on-WLAN is temporarily disabled (in /etc/powerd/powerd.conf)
> while we work on stabilising it.
>
> XO-4 8787 wireless now responds to the packet that woke the system (#12554)
>
> XO-4 Audio recording works in the record activity (#12889)
>
> powerd-109: avoid suspending when HDMI is connected
>
> The system should now then suspend when idle again. (#12538)
>
> Latest runin tests (#12576)
>
> Bluetooth tests added to OFW (#12489)
>
> Latest OFW Q7B19.
> ___
> 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: 13.1.0 release candidate 6 (build 30) released

[Samuel Greenfeld]

I do not see one so I filed #12560.


On Sun, Feb 17, 2013 at 5:18 PM, James Cameron  wrote:

> On Fri, Feb 15, 2013 at 09:55:44AM -0500, Samuel Greenfeld wrote:
> > Do not install Q7B16 when using this build on a XO-4 as that can
> > cause the wifi card to fail to resume after suspend cycles.
>
> Is there a ticket for this one?
>
> --
> James Cameron
> http://quozl.linux.org.au/
>
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Re: 13.1.0 release candidate 6 (build 30) released

[Samuel Greenfeld]

This build generally works on XO-1, XO-1.5, XO-1.75, and XO-4.

On XO-1.75 I ran into problems with applications that use audio (especially
while recording) after running a variety of sound-using applications in a
row.

On XO-4 this build does not fix the graphics corruption or keyboard-induced
suspend/resume hangs previously seen with os29.

Do not install Q7B16 when using this build on a XO-4 as that can cause the
wifi card to fail to resume after suspend cycles.



On Thu, Feb 14, 2013 at 6:38 PM, Daniel Drake  wrote:

> Hi,
>
> We're pleased to announce the next release candidate of our new 13.1.0
> software release.
>
> Information and installation instructions can be found here:
> http://wiki.laptop.org/go/Release_notes/13.1.0
>
> Quick links for those who know which files need to be grabbed and save
> to USB disks:
> http://download.laptop.org/xo-4/os/candidate/13.1.0-30
> http://download.laptop.org/xo-1.75/os/candidate/13.1.0-30
> http://download.laptop.org/xo-1.5/os/candidate/13.1.0-30
> http://download.laptop.org/xo-1/os/candidate/13.1.0-30
>
> This is a signed release candidate that can be installed on all XOs,
> even those with security enabled.
>
> We're looking for testing and feedback on all aspects of the system.
> Thanks for any help you can offer, and for all the feedback that was
> received throughout development.
>
> Please review the "Known problems" section of the release notes. Some
> documented issues are carried over from previous releases, but others
> are new and are things that we will aim to fix in the few weeks before
> release.
>
> XO-4 automatic power management is enabled by default, but this is
> still a work in progress. There are still various instabilities which
> may make this build feel more unstable than earlier ones. You can
> disable automatic power management in sugar's Settings panel to
> restore previous behaviour.
>
> Compared to the previous release candidate, we have changed:
>
> Latest wake-on-WLAN fixes for 8787 wireless. The C1 machines should
> now have somewhat reliable wake-on-WLAN.
>
> The no-mouse-on-boot problem should be finally resolved (#12101).
> Please shout if you see further cases of dead touchpad upon boot.
>
> systemd no longer conflicts with powerd's lid handling (#12504)
>
> olpc-dev-kernel works on XO-1.75 (#12531)
>
> Wikipedia now works when offline (#12479)
>
> Thanks!
> ___
> 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: 13.1.0 build 29 for XO-4 released

[Samuel Greenfeld]

The os29 build has a few known issues related to suspend & resume, such as
a failure to wake up if you catch the system just as it is trying to
suspend (#12541).

If you have problems with a XO-4 repetitively hanging while you are trying
to use it and you do not want to test wakeups, try disabling "Automatic
power management" in Sugar's control panel until the next build is made.


On Tue, Feb 12, 2013 at 1:59 PM, Jon Nettleton wrote:

> On Tue, Feb 12, 2013 at 7:42 PM, Martin Langhoff
>  wrote:
> > On Tue, Feb 12, 2013 at 1:33 PM, Gary Martin 
> wrote:
> >>> This is a known issue. Next release will have a better fix.
> >>
> >> Does this fix also resolve the small random graphic corruptions to the
> first boot welcome content?
> >
> > AIUI, Jon is working on sorting all the corruption fixes he can, so
> > the answer should be yes, but the work isn't finished yet... :-)
> >
>
> Yep known about and working on it.  Will have them fixed for the next
> build.
> ___
> 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: Is gabble not working correctly?

[Samuel Greenfeld]

Thanks for the report.

This has been confirmed and filed as http://bugs.sugarlabs.org/ticket/4369

I will get some debugging information on the ticket in a bit.


On Tue, Jan 8, 2013 at 11:48 AM, rihowa...@gmail.com wrote:

> Jerry,
>
> I had been meaning to send an email regarding this and file a bug report.
> With 13.1.0 build 22, and possibly earlier builds, I cannot make a
> connection to an XS.
> (I use Anna's XS for testing). I see this with both an XO-1 and and an XO
> 1.75 running 13.1.0
>
> If I have both XOs running 13.1.0 booted they connect directly to each
> other.
> Running olpc-netstatus indicates they are not connecting to the school
> server
>
> I can connect to the XS using 12.1.0 with both an XO-1 and an XO 1.75.
>
> rihowa...@gmail.com
>
> linux - the best things in life are free
>
>
>
>
>
> On Jan 7, 2013, at 5:12 PM, Jerry Vonau wrote:
>
> > Hi All:
> >
> > I'm having some difficulties in having the XOs connect when booting. I
> > can use the "register with schoolserver" method or populating
> > collaboration server, which will cause the neighbourhood view to become
> > populated until rebooted. Once rebooted the neighbourhood view doesn't
> > become populated and the XO is running salut according to ps -A and
> > netstat has no connection to the jabber server but salut is running. Can
> > anybody else confirm this behaviour?
> >
> > Jerry
> >
> >
> > ___
> > 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
>
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Re: [TRANSIENT] Peer XOs NOT shown in Neighborhood view when Power Management is enabled

[Samuel Greenfeld]

On Wed, Jan 2, 2013 at 10:21 AM, Paul Fox  wrote:

> samuel wrote:
>  > On Tue, Jan 1, 2013 at 7:34 PM, Jerry Vonau  wrote:
>  >
>  > > On Wed, 2012-12-19 at 09:48 -0500, Martin Langhoff wrote:
>  > > > On Wed, Dec 19, 2012 at 5:14 AM, Jerry Vonau 
> wrote:
>  > > > > Think I found the problem, in powerd we're setting WOL based on
> this
>  > > > > string:
>  > > > >
>  > > > > if grep -qi ": :14B2" /proc/net/tcp
>  > > > >
>  > > > > but that string is not present in /proc/net/tcp so WOL is not set
>  > > > > according to ethtool, but that string can be found in
> /proc/net/tcp6
>  > > > >
>  > > > > avahi is bound to tcp6 when viewed with 'netstat -nat'
>  > > > >
>  > > > > This is reproducible in 12.1.0 and 13.1.0
>  > > >
>  > > > Arghhh. Ouch.
>  > > >
>  > > > Does it behave better with:
>  > > >
>  > > >   if grep -qi ": :14B2" /proc/net/tcp*
>  > >
>  >
>  > This does not work because IPv6 addresses are longer (and therefore have
>  > more octets).
>  >
>  > The variant I came up with (if we want to support both v4 and v6
> listeners)
>  > is
>  >
>  > if grep -qiE ": +:14B2" /proc/net/tcp?
>  >
>  > Simply removing the ": " check on its own might be sufficient for our
>  > purposes but could falsely return true in a few cases.
>  >
>  > If IPv4 backward compatibility on the listener check is not a concern,
> then
>  > you should just match on the longer string of zeros:14B6 in
> /proc/net/tcp6
>  > and not check both files for speed.
>
> why would ipv4 backward compatibility not be a concern?
>

The ::0 (0.0.0.0 in IPv4 netstat speak) listener for telepathy-salut is
bound on the IPv6 socket, but still handles IPv4 requests.  So just
/proc/net/tcp6 can be looked at in 13.1.0/Fedora 18 as we ship it.

But if there is an option to tell telepathy-salut to bind to 0.0.0.0
instead of ::0 and force the listener to use IPv4 binding, then both
/proc/net/tcp and /proc/net/tcp6 have to be checked if we wanted to be
backward-compatible, or just paranoid in case something we don't know or
don't expect can tell telepathy-salut to do that.
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Re: [TRANSIENT] Peer XOs NOT shown in Neighborhood view when Power Management is enabled

[Samuel Greenfeld]

On Tue, Jan 1, 2013 at 7:34 PM, Jerry Vonau  wrote:

> On Wed, 2012-12-19 at 09:48 -0500, Martin Langhoff wrote:
> > On Wed, Dec 19, 2012 at 5:14 AM, Jerry Vonau  wrote:
> > > Think I found the problem, in powerd we're setting WOL based on this
> > > string:
> > >
> > > if grep -qi ": :14B2" /proc/net/tcp
> > >
> > > but that string is not present in /proc/net/tcp so WOL is not set
> > > according to ethtool, but that string can be found in /proc/net/tcp6
> > >
> > > avahi is bound to tcp6 when viewed with 'netstat -nat'
> > >
> > > This is reproducible in 12.1.0 and 13.1.0
> >
> > Arghhh. Ouch.
> >
> > Does it behave better with:
> >
> >   if grep -qi ": :14B2" /proc/net/tcp*
>

This does not work because IPv6 addresses are longer (and therefore have
more octets).

The variant I came up with (if we want to support both v4 and v6 listeners)
is

if grep -qiE ": +:14B2" /proc/net/tcp?

Simply removing the ": " check on its own might be sufficient for our
purposes but could falsely return true in a few cases.

If IPv4 backward compatibility on the listener check is not a concern, then
you should just match on the longer string of zeros:14B6 in /proc/net/tcp6
and not check both files for speed.
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Re: F18's firewalld in 13.1.0

[Samuel Greenfeld]

Thank you for the report.

I have confirmed this and filed http://dev.laptop.org/ticket/12430


On Tue, Jan 1, 2013 at 6:53 PM, Jerry Vonau  wrote:

> Hi all,
>
> With F18 moving to firewalld as the default firewalling method this has
> rendered powerd's netactivity iptables chain to NOT be loaded at all.
>
> How to reproduce:
>
> sudo iptables -S
> note that netactivity chain is not present.
>
> sudo rpm -e firewalld
> reboot
>
> sudo iptables -S
> note that netactivity chain is present.
>
> Think the easy fix for right now is to exclude firewalld from the build
> image in OOB.
>
> Jerry
>
>
>
>
> ___
> 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: Adobe Flash for XO-4 and XO-1.75

[Samuel Greenfeld]

To the best of my knowledge, the XO-1.75 and XO-4 have no hardware-level
x86 compatibility.  They use processors that use the ARM architecture.

If you absolutely need x86 support on these platforms and cannot
recompile/rebuild code, the qemu platform might be able to help.

In the past OLPC has worked with deployments to get their custom activities
updated to be more platform independent.  In general most applications
available in Fedora are now compiled for ARM automatically as well.

Adobe Flash support is available for 11.3.1 and 12.1.0 for XO-1.75 (along
with accelerated video playback in the latter) but I would not be the
person to know their licensing.  Contact whomever you are working with at
OLPC (for sales/deployment/etc.) for details.



On Tue, Jan 1, 2013 at 5:49 AM, Roshan Karki  wrote:

> I'm pretty sure the answer is no, but just to confirm is there Adobe Flash
> support for either XO-4 or XO-1.75? Also is there x86 compatible XO-4 or
> XO-1.75 in production?
>
> Thanks and happy new year.
>
> ___
> 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: 13.1.0 release candidate 1 (build 20) released

[Samuel Greenfeld]

I looked at os20 on Friday as well as over the weekend, and in general we
are getting a bit more stable and closer to release.

Measure on XO-1.75 needs to not record while playing tuning tones as the
current Linux sound driver on XO-1.75 cannot simulaneously playback and
record (SL #4353).  XO-4 audio also still needs work.

I did see the failure to wake on multicast issue with a bunch of XOs at
home where the network environment was quieter, so I will research
potential fixes there.

If you are looking to verify antitheft on XO-4, please make sure to have
Q7B09 or higher installed.  Also note that OLPCs automated license key
server does not know about XO-4s yet, so please stick to simulated testing
or using your own custom keys for now.

---
SJG


On Sat, Dec 22, 2012 at 11:13 AM, Daniel Drake  wrote:

> Hi,
>
> We're pleased to announce our first release candidate of our new
> 13.1.0 software release.
>
> Information and installation instructions can be found here:
> http://wiki.laptop.org/go/Release_notes/13.1.0
>
> Quick links for those who know which files need to be grabbed and save
> to USB disks:
> http://download.laptop.org/xo-4/os/candidate/13.1.0-20/
> http://download.laptop.org/xo-1.75/os/candidate/13.1.0-20/
> http://download.laptop.org/xo-1.5/os/candidate/13.1.0-20/
> http://download.laptop.org/xo-1/os/candidate/13.1.0-20/
>
> This is a signed release candidate that can be installed on all XOs,
> even those with security enabled.
>
> We're looking for testing and feedback on all aspects of the system.
> Thanks for any help you can offer, and for all the feedback that was
> received throughout development.
>
> Our scheduled release date is January 7th.
>
> Please review the "Known problems" section of the release notes. Some
> documented issues are carried over from previous releases, but others
> are new and are things that we will aim to fix in the few weeks before
> release.
>
> Compared to the last 13.1.0 development release (build 19), we have fixed:
>
> Clock-12 fixes broken talking clock mode (SL#4079)
>
> Physics-11 fixes broken input in activity title area (SL#4193)
>
> Write now works again on XO-1/XO-1.5 (#12412)
>
> sugar-0.98.2:
> - Icons on the neighborhood screen should not collide as often with
> the central buddy (SL#3944)
> - Buddy icon layout on the journal list view should be fixed (SL#4331,
> SL#4335)
> - "Send to friend" file transfer is working again (SL#4242)
> - The Journal no longer crashes when dealing with right-to-left
> languages (SL#4328)
> - Modem connections should now complete successfully (SL#4255)
> - Clicking on activity icons in the neighborhood view works again (SL#4283)
> - alt-tab switching through activities now works again (SL#3895)
>
> sugar-toolkit-gtk3-0.98.2:
> - Bookmark tray layout in Browse is fixed (SL#4279)
> - Icons in the Journal's Documents views are no longer incorrect (SL#4276)
> - Border in the pop-up palette menus is no longer inconsistent (SL#4295)
>
> sugar-artwork-0.98.2 fixes the appearance of the journal's favorite
> icon (SL#4304).
>
> sugar-datastore-0.98.1 fixes bad activity ordering in the journal (SL#4305)
>
> Clipboard operation in Sugar is still not working right, but we have
> included the gtk3 and pygobject3 fundamental fixes from SL#4307;
> hopefully we're not far from finishing this.
>
> A bug where the mouse cursor would frequently disappear has been
> solved (#12411). Note that it is normal and intended for the mouse
> cursor to disappear when using the XO-4 touchscreen.
>
> XO-4 .zd file no longer produces a strange warning upon flashing (#12402)
>
> Audacity no longer causes a kernel crash on XO-4 (#12367)
>
>
> I accidently missed the latest handful of XO-4 kernel commits in this
> build; I'll be sure to include the latest one in the next build, which
> is not far off.
>
> Thanks!
> 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

Re: [TRANSIENT] Peer XOs NOT shown in Neighborhood view when Power Management is enabled

[Samuel Greenfeld]

It sounds like you are having issues with multicast packet wakeups, which
have always been a bit of a sore spot.

I presume you are using ad-hoc networking, and have not left the XOs idling
to the point they shutdown their screen turns black and the wifi card is
turned off (~20 minutes?).  If this is with a schoolserver it still could
be a known issue but might be worth raising again.

Wake-on-LAN behavior with the 8686 wireless card is not as reliable at it
should be.  XOs need to wake up on multicast events to receive data
(multicast DNS) about the network neighborhood, but need to clearly hear
such announcements {i.e. no collisions with another data packet}, and
sometimes don't get them even if the XO is awake.  In crowded cities where
there are lots of access points and other computers nearby this becomes
more of a problem.

And since updates are only sent every few minutes, it could take quite a
while for everything to get synched up, with things lost along the way.

Schoolservers/Jabber servers use TCP connections, should be retrying at the
TCP level, and should not run into these issues unless a XO went fully into
suspend (black screen/etc.) with the wifi card off.  If a XO is connected
to a schoolserver/Jabber it will not show ad-hoc users even if they are on
the same network.

The ad-hoc networking model definitely could be improved but I do not know
if anyone has ever taken up that task.

There are several tickets on the subject; I do not recall filing any
against 13.1.0 yet though.


On Tue, Dec 18, 2012 at 12:40 PM, nitika.mail wrote:

> Hi All,
>
>Peer XOs are NOT shown in Neighborhood view  when Power Management is
> enabled.
>
> Tested on 31016o2 OLPC Image (Build 16) on two XO-1.75's... one Touch and
> the other Non-Touch. Following observations were made:
>
> 1. Having connected both the XO's to a network, when neighborhood view was
> seen on both the XO's, only one XO displayed the other in its neighborhood
> view. The second XO was all alone in the neighborhood view.
>
> 2. At some point, due to suspending an XO (or network re-connect), same
> thing can be observed on either of the XO's
>
> 3. When Power management was disabled and system rebooted, this issue was
> not observed.
>
> 4. This has yet been observed only on XO-1.75's.
>
> If anyone has observed this issue, please do advise.
>
> Also, does this call for raising a bug?
>
> Thanks and Regards,
>
> Nitika Mangal
> QA Manager
> Activity Central: http://activitycentral.com
>
> ___
> 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: Auckland Testing Summary 15 November 2012

[Samuel Greenfeld]

The most generic ticket I know of is http://bugs.sugarlabs.org/ticket/2974 .

In general the false failed to start report has been a problem for at least
as long as I've used Sugar.


On Sat, Dec 15, 2012 at 8:15 PM, Tom Parker  wrote:

> On 16/12/12 13:34, Gonzalo Odiard wrote:
>
>> Thanks Tom for testing,
>> and specially by filling tickets, is the way to have the issues solved.
>>
>
> I generally only raise tickets if I have a reproducible problem to report.
> That said, we should probably raise a ticket complaining about the whole
> "failed to start" problem, where that message appears even though the
> activity has started. I've never made any sense of this, it happens quite
> frequently but I have no reliable steps to reproduce. (I looked at the
> tracker has many failed to start tickets, but I didn't find one that
> describes this problem.)
>
> __**_
> 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: 13.1.0 development build 18 released

[Samuel Greenfeld]

My experience is that Speak and TamTam work, but Record, Scratch, and eToys
do not.

I suspect this is either an interface approach or a sampling rate issue.
If I try to sample at the wrong rates with arecord & aplay I get no audio
back at all.  Attempting to change the dmix rate from 44.1 kHz to 48 kHz
does not solve the problem.

On XO-1.75 I believe we resorted to software resampling; I do not know if
this is in place for XO-4 or not.

Something also seems to be writing over the Mic Gain state as I found it at
zero once although it was about a third of the way up when checked earlier
in the same boot cycle.  Personally I like bumping it up pretty high.


On Tue, Dec 11, 2012 at 1:10 PM, Bert Freudenberg wrote:

> On 2012-12-11, at 15:41, Daniel Drake  wrote:
>
> > The Sugar welcome screen activates again on first boot.
>
>
> Not for me ... or maybe it's a different problem.
>
> Tried to olpc-update my new XO-4 (with XOrduino and XOstick boards! Yay!)
> from whatever came pre-installed. After restarting it flashed a new
> firmware (twice? didn't pay too much attention) and proceded to boot,
> blinking circle od dots, but that stopped at some point and it didn't do
> anything visible anymore. No mouse/keyboard/VT switching, so had to
> power-cycle.
>
> On second boot it was fine though, it asked for activity updates, which
> worked fine.
>
> I tried sound in Etoys and Scratch, which didn't work but just made a
> screetching noise (after turning up the volume). But Record does the same,
> and froze while trying to play back a recorded video, so maybe it's a wider
> problem.
>
> - Bert -
>
>
> ___
> 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: 13.1.0 development build 18 released

[Samuel Greenfeld]

My experience is that OFW warns if no external power is present.  But it
seems to be silent on the main display about the low battery reflash
failure condition unless you attempt to reflash firmware from the "ok"
prompt, or are not in the TS=SHIP (and therefore in a verbose boot) state.


On Tue, Dec 11, 2012 at 6:18 PM, James Cameron  wrote:

> On Tue, Dec 11, 2012 at 04:58:11PM -0600, Jerry Vonau wrote:
> > Hi all,
> >
> > SKU 296 hand written tag attached when received states C2
> >
> > olpc-update from pre-installed build 15, rebooted on AC firmware
> > update skipped. Checked battery level in frame 28% was displayed.
> > Offered activity update, was able to de-select activities.  Let XO
> > charge for a bit rebooted, firmware updated to Q7B08.  Wireless
> > firmware info not available in "about my computer" but wireless
> > works.
> >
> > What's the battery threshold set at in OFW? Looks to be around 30%
>
> No.  There is no such threshold in Open Firmware.
>
> Open Firmware does not check the state of charge when assessing
> whether there is enough power for reflashing firmware.
>
> Instead, Open Firmware relies on the battery status flags provided by
> the embedded controller:
>
> - external power must be present,
>
> - a battery must be present,
>
> - the battery low status bit must be cleared.
>
> Therefore on your SKU296 the battery low status bit must have been
> set.
>
> Can you provide power logs from the duration of the olpc-update?
>
> You can find further information in the embedded controller source,
> for the bit name bat_low
>
> http://dev.laptop.org/git/users/rsmith/ec-cl4-mmp3/tree/battery.c
>
> >
> > Didn't connect to ejabberd with a pre-existing registration on the
> > schoolserver that was working pre-upgrade.
> >
> > Didn't expect the welcome activity to appear as this was olpc-update'd.
> >
> > Jerry
> >
> >
> >
> > On Tue, 2012-12-11 at 14:41 +, Daniel Drake wrote:
> > > Hi,
> > >
> > > A new 13.1.0 development build is available.
> > >
> > > http://wiki.laptop.org/go/13.1.0
> > > http://build.laptop.org/13.1.0/os18
> > >
> > > Changes:
> > >
> > > XO-4 kernel fixes:
> > > - Camera works again (#12380)
> > > - DCON and pretty boot works again (#12378), no need to boot in
> > > verbose mode like in build 17
> > > - Power button works again (#12379)
> > > - USB unreliability should be fixed (#12158)
> > >
> > > Fixed bitfrost problem in activation initramfs (#12376)
> > >
> > > GNOME can be launched on XO-1.75/XO-4 again without error (#12381)
> > >
> > > The Sugar welcome screen activates again on first boot.
> > >
> > > sugar activity updater fixes:
> > > - UI no longer hangs strangely (#12272)
> > > - Select/deselect of specific updates works again (SL#4274)
> > > - Activity group URLs can be modified again (SL#4275)
> > >
> > > sugar-artwork-0.98.1:
> > > - Get back margin of toolbuttons (SL#3936)
> > > - Style GtkProgressBar (SL#4249)
> > >
> > > sugar-toolkit-gtk3-0.98.1
> > > - Popdown the palette if an item in the content box gets activated
> > > (SL#4191, SL#4253)
> > > - TrayIcon: get the black background and outline for palette popup
> (SL#4089)
> > > - RadioToolButton: draw the outline properly (SL#3936)
> > > - CanvasIcon: do not keep it ACTIVE when right-click twice (SL#4224)
> > >
> > > sugar-0.98.1
> > > - Adapt to PaletteMenu changes for popdown on item activation
> (SL#4191, SL#4253)
> > > - Fix XO-4 all-black screenshots (SL#4104)
> > > - Journal details: make buddies appear (SL#4282)
> > >
> > > Paint-53
> > > - Fix "Opacity does change while drawing" (SL#4237)
> > > - Fix "Paint cut/paste duplicates first pasted item in top-left
> > > corner." (SL#4250)
> > >
> > > Thanks for any testing and feedback!
> > > ___
> > > 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
>
> --
> James Cameron
> http://quozl.linux.org.au/
> ___
> 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: HDMI port

[Samuel Greenfeld]

The connector on XO-4 B1 motherboards is a bit further in than it should
be.  You might not be able to establish a reliable connection to it without
increasing the size of the opening in the case.

The connector on XO-4 C1 motherboards has been moved a bit further out.

In terms of using the smaller connector, for users upgrading motherboards,
there has been discussion about including an adapter to make the existing
hole for a third USB port micro HDMI-size.  I have not seen one of these
adapters yet so I cannot comment much about it.


On Sun, Dec 2, 2012 at 5:06 AM, Sameer Verma  wrote:

> I was looking for a cable for the micro HDMI port on the XO4. I couldn't
> find it locally, so I bought it online. The connector is similar to a micro
> USB on my phone (size wise) but after plugging it into the XO, I realized
> that the connector is very flimsy. I suppose the bit sticking inside the XO
> doesn't feel robust enough to forgive any major movement of the cable on
> the outside.
>
> A type A HDMI cable connector seems to be quite robust, like a USB A
> connector. What was the thinking behind picking a micro HDMI connector?
>
> A regular HDMI connector seems more robust and easily available (my
> experience...yours may vary).
>
> cheers,
> Sameer
>
> ___
> 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: 13.1.0 development build 14 released

[Samuel Greenfeld]

I looked at os14 this weekend on XO-1.75 and XO-4 (as well as looked at
os12 on XO-1 and XO-1.5 in the past).

In general the builds are getting to be reasonably stable, although still a
bit rough around the edges.  I did not see any XO-1.75 or XO-4
manufacturing test issues with os12 or os13.

XO-4 audio & suspend/resume support still needs to finish being
implemented, along with the accelerated/rotatable video driver.

Abiword still crashes on ARM (#12311).  I also had Write crash once with a
Segmentation fault when touching the screen of a XO-4, but I need to
reproduce this with core dumps.

Something to consider taking is a new version of Measure as the frequency
display mode broke (SL #4254).   This already should be fixed in git.

---
SJG


On Thu, Nov 22, 2012 at 9:47 AM, Daniel Drake  wrote:

> Hi,
>
> A new 13.1.0 development build is available.
>
> http://wiki.laptop.org/go/13.1.0
> http://build.laptop.org/13.1.0/os14
>
> Changes/fixes:
> - A handful of activity updates
> - Newer touchscreen fixes from Carlos Garnacho (SL#4132)
> - XO-4 ebook switch state incorrectly initialized at boot (#12326)
> - olpc-dev-kernel needs to learn about runos4 and runrd4 (#12333)
> - Fix geode all-black composite issue (#11979)
>
> Thanks for any testing and feedback!
> 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

Re: 13.1.0 development build 12 released

[Samuel Greenfeld]

The update is done by olpc.fth if the XO is not secured, and we just
re-enabled the ability to do this on XO-4 in os12.A battery/power icon
will appear if the XO is running without external power and the firmware
cannot be safely updated.

As I understand it, the auto-firmware reflash process was temporarily
disabled to avoid an issue with XO-4 A2 prototypes.  Re-enabling the
reflash process means we can no longer support these early prototypes going
forward.

Very few people outside of OLPC likely have XO-4 A2 units.

---
SJG


On Fri, Nov 16, 2012 at 6:59 PM, Hal Murray  wrote:

>
> w...@laptop.org said:
> > More importantly, occasionally boot with two sources of power (battery
> and
> > DC). Q7B01 should have been replaced automatically a number of builds
> ago.
>
> What chunk of code does the update?  Could it display a reminder for a few
> seconds if there is new code that hasn't been applied yet?
>
>
> --
> These are my opinions.  I hate spam.
>
>
>
> ___
> 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: [Techteam] 13.1.0 development build 11 released

[Samuel Greenfeld]

I looked at 13.1.0 os11 on the XO-1.5, XO-1.75, and XO-4.

   - This build is usable in a similar manner to the previous build.
   - Collaboration over ad-hoc works although I could not get users to see
   each other once registered to a schoolserver.
   - XO-1.75 audio is back to its previous state.
   - No XO-4 audio is available yet.
   - We still have abiword crashing on ARM.
   - Gnome notification pop-up dialogs overflow offscreen.
   - When sharing an activity its activity icon duplicates at an offset
   leaving an overlapped copy of itself similar to #3635, but when the
   activity is shared.  This then persists until the activity is quit.



On Mon, Nov 12, 2012 at 6:02 AM, Peter Robinson wrote:

>
> On 12 Nov 2012 11:18, "Simon Schampijer"  wrote:
> >
> > On 11/11/2012 11:18 PM, Peter Robinson wrote:
> >>
> >> A new 13.1.0 development build is available.
> >>
> >> http://wiki.laptop.org/go/13.1.0
> >> http://build.laptop.org/13.1.0/os11/
> >>
> >> Changes:
> >> - The latest sugar component versions that were released on Thursday
> >
> >
> > Actually, the package list [1] shows that Saturday's releases went in as
> well. Thanks a lot for that!
>
> Oh yes, I forgot those ones were the ones I meant... all the releases are
> blending into one!
>
> > Cheers,
> >Simon
> >
> > [1] http://build.laptop.org/13.1.0/os11/xo-4/31011o4.packages.txt
> >
> >
>
> ___
> 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: 13.1.0 development build 10 released

[Samuel Greenfeld]

I looked at os10 on XO-1.5 and XO-4 with Q7B05.

The build generally works.  The Sugar pop-menus place items a bit closer
together though, which is not good for touch usage.

There still is no XO-4 sound support.

You can see other Sugar systems in the network view but as soon as you
share an activity the sharing user disappears.

As Yioryos noted for os9, Abiword crashes on ARM but does not crash on x86
systems.

The hang exiting GNOME seems to be related to some sort of CPU
spinning/race/unclean shutdown between gnome-session (using 2/3 of CPU) and
maliit-server (using 1/3 of CPU).   On the x86 builds without Maliit
installed there is no delay exiting GNOME.



On Fri, Nov 9, 2012 at 9:20 AM, Manuel Quiñones  wrote:

> Thanks a lot Alan for the olpc-network bug report and patch.  Pushed it.
>
> 2012/11/9 Alan Jhonn Aguiar Schwyn :
> > Hi,
> >
> > Quick tests:
> >
> > - In the "neighborhood" when you click on AP with password, not appears
> the
> > window
> > to enter the password. If you make a right click and select "connect"
> (that
> > I supose that
> > continues being "connect" because only see a black frame) the window
> > appears.
> > Attach "neighborhood.png"
> > In the shell appears some error of this.. attach the log file..
> >
> > HOW TO FIX:
> >
> > file: "/usr/lib/python2.7/site-packages/jarabe/desktop/networkviews.py"
> > line:  648
> > change:
> >
> >  _palette_
> >
> > by:
> >
> >  _palette
> >
> > And Works!!   ;-)
> >
> > - Copy an entry to a Pendrive (or similar). Continues with problem. No
> copy!
> > If you use the secondary menu: copy to.. it works..
> >
> > - The activities works.. I'm only check the basic..
> >
> > Regards!
> >
> > Alan
> >
> >
> >> Date: Thu, 8 Nov 2012 13:31:41 -0600
> >> Subject: 13.1.0 development build 10 released
> >> From: d...@laptop.org
> >> To: devel@lists.laptop.org
> >
> >>
> >> A new 13.1.0 development build is available.
> >>
> >> http://wiki.laptop.org/go/13.1.0
> >> http://build.laptop.org/13.1.0/os10/
> >>
> >> Changes:
> >> - The latest sugar component versions that were released on Wednesday
> >> - A handful of activity updates
> >> - XO-4 bluez command-line utility added to allow the factory to test
> >> bluetooth support on the XO-4 8787 wireless card
> >> - Latest XO-4 kernel work for suspend/resume
> >> - XO-1.75 audio recording works again (#12199)
> >>
> >> Thanks for any testing and feedback!
> >>
> >> 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
> >
>
>
>
> --
> .. manuq ..
> ___
> 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: 13.1.0 development build 9 released

[Samuel Greenfeld]

I have looked primarily at the XO-1.75 and XO-4 images, but also a bit at
the XO-1.5 image since it came out this morning.

The ability to use the GNOME menus is back along with the icons that
previously disappeared in Sugar.

XO-1.75 audio is still poor in quality (especially recording; #12199), and
XO-4 audio does not exist yet.  Using a (non-released, test) XO-4 firmware
image past q7b04 risks having os9 not boot until Linux & OFW get synced up
again (#12271).

The "cannot determine a method resolution order" error still occasionally
happens on XO-4.

Occasionally when using touch I get a secondary (right-click) menu with no
items in it (completely black), but sized like it has the normal list of
items.  This has happened in the Network view (Access points) as well as in
the spiral view (central XO character).  This might be touch related or
just a video driver bug.

Once I had no secondary menus/palettes show up at all in all of the main
Sugar views until I restarted Sugar, although things initially worked.  I
could not start any new activities either.  The exception in Sugar
suggested a byte to Unicode conversion error.  I need to file a ticket on
this and try and reproduce it.


SJG

On Mon, Nov 5, 2012 at 3:41 PM, Daniel Drake  wrote:

> On Sun, Nov 4, 2012 at 5:08 AM, Peter Robinson 
> wrote:
> > - The some activity updates
> > - XO-4 kernel work for 8787/mwifiex wireless, touchscreen improvement,
> and I
> > believe some suspend/resume work
> >
> > Thanks for any testing and feedback!
>
> Thanks Peter for the builds. The XO-1 and XO-1.5 images are now there too:
> http://build.laptop.org/13.1.0/os9/
>
> Testing appreciated, since I haven't tested them :)
>
> Since build 8 we have fixed:
> #12259 Support systemd-195's depreciation/migration of various
> configuration settings
> #12246 OS8 Gnome Applications menu is empty
> #12137 Tap-to-click enabled on some XO4s
> #12244 Browse homepage not touch-friendly
> #12227 XO-4 build lacks latest runin
> #12044 XO-1 glyph rendering bugs in X
> #12138 Incorrect repeat rendering on XO-1.5
> #12171 XO-4: X11 segfault triggered by touch input
>
> The "invisible" sugar icon issue seen in build 8 is also fixed.
>
> Thanks,
> Daniel
> ___
> olpc mailing list
> o...@lists.fedoraproject.org
> https://admin.fedoraproject.org/mailman/listinfo/olpc
>
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Re: [Testing] 13.1.0 development build 8 released

[Samuel Greenfeld]

I did not see this installing os8 on XO-1.5 on a 4 GB unit, although this
could be a sign we exceeded the limit of a 2 GB one.  This also sometimes
means that the internal SD card is not working or plugged in correctly (the
OFW banner will show a 0 GB internal device).

I looked at os8 on XO-1, XO-1.75, and XO-4 and have not found any major
breaks yet which have not already been mentioned.

There is a minor break in Paint where a few things are not themed properly
in submenus.


On Fri, Oct 26, 2012 at 10:44 AM, Walter Bender wrote:

> On Fri, Oct 26, 2012 at 10:34 AM, Daniel Drake  wrote:
> > Hi,
> >
> > On Fri, Oct 26, 2012 at 6:58 AM, Walter Bender 
> wrote:
> >> I was unable to reflash os8 onto an XO 1.5 that I had just flashed
> >> with os7. "Not enough space".
> >
> > Can you please explain how you flashed it? Was that the exact error
> > message? What context did it appear in?
>
> from OFW:
>
> fs-update u:\31008o1.zd
>
> u:\31008o1.zd:1: Image size is larger than output device
>
> -walter
>
> >
> > Thanks
> > Daniel
>
>
>
> --
> Walter Bender
> Sugar Labs
> http://www.sugarlabs.org
> ___
> 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: 13.1.0 development build 7 released

[Samuel Greenfeld]

I looked at os7 on XO-1.5 and XO-1.75.


   - XO-1.75 has some audio issues (especially with recording) that are a
   regression to os5 (#12199).
   - XO-1.75 also has a graphics corruption issue which may be related to
   rotation visible in certain activities like eToys and Calculate.  I need to
   do more research to limit this down.
   - Cut and paste support within Sugar activities is still generally
   broken.
   - Browse's embedded media player (Totem) fails to open ogg files.  It
   briefly appears only to be replaced by a "file not found" message (SL
   #4045).


On Wed, Oct 17, 2012 at 11:45 AM, Daniel Drake  wrote:

> Hi,
>
> http://build.laptop.org/13.1.0/os7
> http://wiki.laptop.org/go/13.1.0
>
> Some feature work wasn't completed quite in time for the last build,
> but is now ready.
> So here is the final build from our feature development stage.
>
> - Hide mouse cursor when touchscreen is used (SL#4032)
> - Auto-scroll the window canvas to avoid the on-screen keyboard hiding
> the selected text input area (not quite working yet)
> - Touch gestures in Browse (SL#3997)
> - Improved spiral layout (#4027)
>
> Includes the latest Sugar, with a handful of fixes. And:
>
> #12203 13.1.0 os6 omits 'Software update' image from graphical control
> panel
> #12188 NetworkManager crashing with segmentation fault
>
> Wireless networking should now work reliably - fingers crossed.
>
> Thanks
> 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

Re: Using ext4 usb drive to go to 13.1.0

[Samuel Greenfeld]

You are correct that I am confusing things.

12.1.0 os21 has Q4D17 (
http://download.laptop.org/xo-1.75/os/official/12.1.0-21/21021o2.packages.txt
).

13.1.0 os3 has Q4D21 (
http://build.laptop.org/13.1.0/os3/xo-1.75/31003o2.packages.txt - os1 & os2
also have similar).

For some reason I keep ending up off-by-one while trying to parse our new
versioning scheme; sorry.


On Sun, Sep 23, 2012 at 9:41 PM, James Cameron  wrote:

> Oops, have I got my versions mixed?  I thought it was 12.1.0 (os12)
> that shipped with Q4D17, and 13.1.0 (os2/os3) that currently has
> Q4D21.
>
> On Sun, Sep 23, 2012 at 09:37:57PM -0400, Samuel Greenfeld wrote:
> > The final version of 13.1.0 (os21) only ships with Q4D17 for XO-1.75
> (Q3C07 for
> > XO-1.5, Q2F12 on XO-1).
> >
> > I am aware that at least one USB glitch (#12034 on XO-1.5) is present in
> the
> > final release, but given this seemed non-fatal the release freeze was not
> > lifted to take a new firmware build.
> >
> > If you believe updated firmware builds are required if we release a
> 13.1.1
> > build (and not just 14.1.0) I would recommend filing a ticket.
> >
> >
> > On Sun, Sep 23, 2012 at 9:28 PM, James Cameron  wrote:
> >
> > On Sun, Sep 23, 2012 at 07:55:28PM -0500, Bruno Wolff III wrote:
> > > On Mon, Sep 24, 2012 at 09:28:12 +1000, James Cameron
> > >  wrote:
> > > > G'day Bruno,
> > > >
> > > > Thank you for your problem report.  It is interesting.
> > >
> > > I updated the trac ticket with most of what was requested.
> >
> > Thanks.  I'll use the ticket for summary only.
> >
> > > > The install method hasn't changed.  Our development builds are
> > > > installed using fs-update rather than the zsp file and holding
> > > > four game keys down.  Once 13.1.0 is released, the method will be
> > > > the same as before.
> > >
> > > When going to 12.1.0 I held down the four buttons above the power
> > > switch while booting. When going to 13.1.0 I used fs-update. I was
> > > going by the instructions on the wiki for doing the updates.
> >
> > Yes, the instructions are different, but they will be the same as
> > before ... once 13.1.0 is released.  13.1.0 is not yet released; you
> > were using a development build which requires special use of
> > fs-update.
> >
> > > > When you upgraded your XO-1.75 to 12.1.0 an old version of Open
> > > > Firmware might have been present.  After the upgrade, the next
> > > > time you had two sources of power, Open Firmware would have been
> > > > upgraded.
> > >
> > > I also didn't have two sources of power when I did the fs-update to
> > > 13.1.0, so maybe that's why the open firmware is still at Q4D17.
> >
> > Yes.
> >
> > There is a separate command to upgrade Open Firmware, but the
> > operating system boot does this automatically if two sources of power
> > are available ... normally at the first boot after upgrade.  With
> only
> > one source of power, it will be delayed until a boot with two sources
> > of power.
> >
> > Holding down the four buttons doesn't upgrade both the operating
> > system and the firmware at once, but it does upgrade the operating
> > system, and then the operating system upgrades the firmware at the
> > first available opportunity.
> >
> > (In the release notes we ask for two sources of power before using
> the
> > four game keys method.
> > http://wiki.laptop.org/go/Release_notes/12.1.0#XO-1.75 ... but for
> > development builds we expect users may manage their systems
> > differently.)
> >
> > Using fs-update to upgrade the operating system should eventually
> > cause the firmware to upgrade.  If this isn't happening with two
> > sources of power, it is a separate problem we should investigate.
> >
> > > > a.  what version of Open Firmware was on the XO-1.75 before the
> > > > upgrade to 12.1.0?  I cannot guess what this was.
> > >
> > > I don't know, but probably whatever you were shipping with the
> > > devices a few weeks ago. Mine shipped shortly before 12.1.0 was
> > > released.
> >
> > Thanks.  I acknowledge you don't know what version worked with your
> > USB drive before the upgrade.
> >
> > Please

Re: Using ext4 usb drive to go to 13.1.0

[Samuel Greenfeld]

The final version of 13.1.0 (os21) only ships with Q4D17 for XO-1.75 (Q3C07
for XO-1.5, Q2F12 on XO-1).

I am aware that at least one USB glitch (#12034 on XO-1.5) is present in
the final release, but given this seemed non-fatal the release freeze was
not lifted to take a new firmware build.

If you believe updated firmware builds are required if we release a 13.1.1
build (and not just 14.1.0) I would recommend filing a ticket.


On Sun, Sep 23, 2012 at 9:28 PM, James Cameron  wrote:

> On Sun, Sep 23, 2012 at 07:55:28PM -0500, Bruno Wolff III wrote:
> > On Mon, Sep 24, 2012 at 09:28:12 +1000, James Cameron
> >  wrote:
> > > G'day Bruno,
> > >
> > > Thank you for your problem report.  It is interesting.
> >
> > I updated the trac ticket with most of what was requested.
>
> Thanks.  I'll use the ticket for summary only.
>
> > > The install method hasn't changed.  Our development builds are
> > > installed using fs-update rather than the zsp file and holding
> > > four game keys down.  Once 13.1.0 is released, the method will be
> > > the same as before.
> >
> > When going to 12.1.0 I held down the four buttons above the power
> > switch while booting. When going to 13.1.0 I used fs-update. I was
> > going by the instructions on the wiki for doing the updates.
>
> Yes, the instructions are different, but they will be the same as
> before ... once 13.1.0 is released.  13.1.0 is not yet released; you
> were using a development build which requires special use of
> fs-update.
>
> > > When you upgraded your XO-1.75 to 12.1.0 an old version of Open
> > > Firmware might have been present.  After the upgrade, the next
> > > time you had two sources of power, Open Firmware would have been
> > > upgraded.
> >
> > I also didn't have two sources of power when I did the fs-update to
> > 13.1.0, so maybe that's why the open firmware is still at Q4D17.
>
> Yes.
>
> There is a separate command to upgrade Open Firmware, but the
> operating system boot does this automatically if two sources of power
> are available ... normally at the first boot after upgrade.  With only
> one source of power, it will be delayed until a boot with two sources
> of power.
>
> Holding down the four buttons doesn't upgrade both the operating
> system and the firmware at once, but it does upgrade the operating
> system, and then the operating system upgrades the firmware at the
> first available opportunity.
>
> (In the release notes we ask for two sources of power before using the
> four game keys method.
> http://wiki.laptop.org/go/Release_notes/12.1.0#XO-1.75 ... but for
> development builds we expect users may manage their systems
> differently.)
>
> Using fs-update to upgrade the operating system should eventually
> cause the firmware to upgrade.  If this isn't happening with two
> sources of power, it is a separate problem we should investigate.
>
> > > a.  what version of Open Firmware was on the XO-1.75 before the
> > > upgrade to 12.1.0?  I cannot guess what this was.
> >
> > I don't know, but probably whatever you were shipping with the
> > devices a few weeks ago. Mine shipped shortly before 12.1.0 was
> > released.
>
> Thanks.  I acknowledge you don't know what version worked with your
> USB drive before the upgrade.
>
> Please provide the serial number, so that I can take a guess at a
> minimum firmware version.  Please also use the .mfg-data command at
> the ok prompt and look for the BV tag, which should list the base
> firmware version used.  .mfg-data also displays the SN or serial
> number tag.
>
> > > b.  what version of Open Firmware was on the XO-1.75 at the time
> > > of the problem in ticket #12123?  I expect it was Q4D17 as this
> > > was 12.1.0 build 21 contained.
> >
> > I can reproduce the issue on Q4D17.
>
> Good, thanks.
>
> > > c.  what version of Open Firmware is on the XO-1.75 after the
> > > upgrade to 13.1.0?  I expect it will be Q4D21.
> >
> > It is still Q4D17.
> >
> > > d.  if you downgrade to the version of Open Firmware you had
> > > before the upgrade to 12.1.0, and then try the fs-update for
> > > 13.1.0, does the problem in ticket #12123 occur?
> >
> > I can't refer to u: successfully if I don't plug in the drive after
> > booting.
> >
> > > e.  on Q4D21 please attach the USB drive, turn on the laptop, get
> > > to the ok prompt, type p2, and tell me what is printed.
> >
> > I haven't got Q4D21 yet, so I can't do these tests just yet.
> >
> > > f.  on Q4D21 please detach the USB drive, turn on the laptop, get
> > > to the ok prompt, type p2, and tell me what is printed.
> > >
> > > g.  on Q4D21 please attach the USB drive, turn on the laptop, get
> > > to the ok prompt, type
> >
> > There were differences for the p2 command under Q4D17 depending on
> > whether the drive was plugged in before or after boot.
>
> Your p2 and scan-subtree output shows that the device does not respond
> to probes if it was already plugged in when the laptop powered on.
> This seems like a power on or reset problem for the driv

Re: 13.1.0 development build 2 released

[Samuel Greenfeld]

Besides the Control Panel issues (missing or unwrapped text/Switch to GNOME
crashes Sugar/etc.) the two major issues I believe exist with os2 are the
inability to use external media (SL #3911) and the inability to collaborate
(SL #3939).

If you can collaborate with 13.1.0 os2 please let me know; our urban
network conditions are not always favorable, but in this case I simply
cannot see users & shared activities regardless of network type or location.


On Sat, Sep 15, 2012 at 3:06 PM, Hal Murray  wrote:

>
> d...@laptop.org said:
> > Bug/testing reports accepted and appreciated - either on the appropriate
> > trac, or on this list.
>
> On a XO-1, there are several/many examples in My Settings
>
> Network:
>   There is no text next to the check-box.
>
> Power, Software Update
>   The header is there, but the page/contents aren't.
>
> Switch Desktop:
>   The display stuff crashes and restarts Sugar.
>
> Modem, Language:
>   You can't exit.  The X and check-mark are too far to the right.  In
> Modem,
> you can just see (and click) the edge of something.  I have to reboot to
> get
> out of Language
>
>
>
>
>
> --
> These are my opinions.  I hate spam.
>
>
>
> ___
> 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: [Sugar-devel] Problem downloading a lease.sig file on an XO

[Samuel Greenfeld]

This might be a better question for the OLPC development lists.

On Wed, Sep 12, 2012 at 8:39 PM, Juan Cubillo wrote:

> Hello,
>
> Our project would like to give kids the posibility of downloading a
> lease.sig file and unlock a friends or family XO without having to contact
> our tech support team. In order to do this, I setup a public dropbox link
> to a nightly generated lease.sig file that gives the XOs some extra
> activation time.
> Problem is that when an XO downloads the file, its name gets and extra
> .asc extension so it ends up as  lease.sig.asc.
> Since kids will be doing this, I wanted to give them only the basic steps
> to be able to re-activate laptops: 1-Download file. 2-place it on an empty
> usb memory. 3-Conect to xo and turn on.
> Re-naming the file would mean that they have to go to terminal, cd into
> the thumbdrive directory, change filename, etc... it's just way too much.
>
> So... couple questions:
> 1. Is there a security problem/concern with having our project's lease.sig
> file publicly available? (we only generate activations for non-stolen XOs)
>

I will leave it this to deployment staff to answer authoritatively, but the
only practical attack I can think of is thieves will know where to find a
lease if a XO is not reported stolen, or before it is reported stolen.
They can then use this lease to use or sell the XO.

Theoretically it might be possible to reverse engineer your private lease
key given lots and lots of sample leases but I seriously doubt any real
thief can do that.  The mathematics skills required to do this are not
trivial.

2. Why is the XO adding this .asc extension or how can it be avoided?
>

Are you having the students download the lease in Browse from within
Sugar?  If so Sugar's journal internally uses mime types, not file
extensions, until a file is written to an external device or folder.  The
extension ".asc" is one possible choice for plain text.(*)   I was able to
reproduce this problem given this approach.

I agree that this is not the best behavior, especially if Browse can
potentially determine the original extension while downloading.

If your XO images have the GNOME desktop in them, using the web browser
included for GNOME (Firefox or Epiphany) to download the file to USB should
not alter the file name.  Just make sure the kids know how to "eject" the
USB stick when they are done.

(*) The ".asc" choice could be due to
http://bugs.sugarlabs.org/ticket/2267(also
http://bugs.sugarlabs.org/ticket/3226)


> Regards,
>
>  - Juan Cubillo
> __**_
> Sugar-devel mailing list
> Sugar-devel@lists.sugarlabs.**org 
> http://lists.sugarlabs.org/**listinfo/sugar-devel
>
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Re: Announcing Q3C09 for XO-1.5

[Samuel Greenfeld]

On Aug 31, 2012 4:16 PM, "Mikus Grinbergs"  wrote:
>
> Edit after having written up the text below the  divider:
>
>   Have swapped XO-1.5s, adapters, hubs.  The "no root device" kernel
panic shows up with q3c09 wherever a particular Belkin F5U 234 (Rev 3)
external USB hub is plugged in.  [With other hubs, of the same or different
models, the problem does not show up.]

So this a problem with the USB hub and not the network adapter?

>
> ----
>
>
> On 08/31/2012 09:09 AM, Samuel Greenfeld wrote:
>>
>> Open Firmware knows how to use certain types of USB Ethernet adapters in
>> addition to the internal Wifi adapter, and supports accessing files via
>> many network protocols in addition to local means.  You can tell OFW to
>> "fs-updatehttp:\\download.laptop.org
\xo-1.5\os\candidate\12.1.0-21\21021o1.zd"
>>
>> (with the slashes intentionally backwards) and it would try to get on a
>> network and install the build that way.
>
>
>> Does your network provide network-based boot services ?
>
>
> In this instance I was merely attempting to __boot__ the XO-1.5, and had
not specified any URLs to the firmware (had not stopped at the ok prompt;
had not typed in anything).
>
> My assumption is that if I do not explicitly tell the firmware to access
an external resource, it will __not__ go looking for one.
> Is my assumption wrong?

James would know about the firmware's default boot path better than I
would. I would expect that all local devices would be tried before network
ones if they are in the default search path.

> The XO is using whatever /bootpart contents os21 installs - including
that build's original '/bootpart/boot-versions/21/olpc.fth' file.  My
assumption is that OFW isn't attempting any "fully network boot".
> [Besides - how would OFW know the passphrase for the wireless network ?]

If the USB Ethernet adapter is plugged in and recognized by OFW then it
would be used instead of the wireless card.

In any case it is unlikely that your XO is trying to boot off of the
network unless something really strange is happening. I have never seen a
XO try to boot off of a network except if was setup to do so after earlier
attempts to boot off of other devices have failed.

>
> mikus
>
>
> p.s.  By the way, my XO-1.5 configuration is :
> External SD card plugged in at bottom of XO
>   Contains one data partition (ext2) and one swap partition
> USB hub plugged in at left side of XO
>   Keyboard plugged in to USB hub
>   Mouse plugged in to USB hub
> USB ethernet adapter plugged in at right side of XO
>
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Re: Announcing Q3C09 for XO-1.5

[Samuel Greenfeld]

On Thu, Aug 30, 2012 at 9:50 PM, Mikus Grinbergs  wrote:

> On 08/30/2012 11:53 AM, Samuel Greenfeld wrote:
>
>> what version of Open Firmware are you using that you are
>> replying to the Q3C09 thread?
>>
>
> q3c09
>
> The reason I posted to this thread is -- I did NOT have the described
> kernel panic when booting os21 on the XO-1.5 with q3c08


I apologize for asking; but in some cases people post to the wrong thread.

 What make and model of USB Ethernet adapter are you using?
>

SMC2208
>
> Do you think this matters?  I have been using these USB ethernet adapters
> for four years now, and have never had any problems using them (on XO-1 and
> XO-1.5) with any build.  [In the past I sometimes have had firmware
> failures (particularly with q2b firmware - which sometimes would "hang" in
> the firmware when I was trying to boot (unless the USB ethernet adapter was
> unplugged from the XO before the XO was booted).]
>

Open Firmware knows how to use certain types of USB Ethernet adapters in
addition to the internal Wifi adapter, and supports accessing files via
many network protocols in addition to local means.  You can tell OFW to
"fs-update http:\\download.laptop.org\xo-1.5\os\candidate\12.1.0-21\21021o1.zd"
(with the slashes intentionally backwards) and it would try to get on a
network and install the build that way.

We also have been tweaking USB timings related to probing; I have 4 GB USB
sticks that Q3C07 has to probe twice in OFW but Q3C08 handles the first
time.

Newer USB adapters also often simulate USB "sticks" or "CD-ROMs" with
driver software.  In this situation that does not appear to be the case.


 Does your network provide network-based boot services ?
>>
>
> No.  When I am using an ethernet-based LAN, that network provides __NO__
> services - not even DHCP.
>
> But I think this question is irrelevant - the described panic occurred
> while trying to load kernel software -- long before the build would get
> around to attempting any initialization of network services.
>

Linux needs to be told what the root device is.  OLPC OS builds rely on
Open Firmware to tell it where the kernel was loaded from so it knows if it
should mount partitions from the internal or external SD card, etc.

Although I have never tried it, OFW can fully network boot; which is why I
needed more information to figure out if it was trying to do so.


In any case I have upgraded a XO-1.5 to Q3C09 and I did not encounter this
issue with my USB adapter.  I was concerned about Q3C07 because we were
hoping to release the final version of 12.1.0 in the immediate future and
it includes Q3C07.

This does not mean you do not have a problem that needs to be fixed.  Given
Open Firmware probes all USB ports, and can use certain types of USB
Ethernet adapters in addition to the internal Wifi card, a bad attempt at
checking a USB Ethernet adapter could mess up futher booting.

---
SJG
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Re: Announcing Q3C09 for XO-1.5

[Samuel Greenfeld]

What make and model of USB Ethernet adapter are you using?  And what
version of Open Firmware are you using that you are replying to the Q3C09
thread?

I have tried all three USB ports with a network cable both connected and
disconnected to a asix-based Zoltantech ZU-80, and I could not hang a
XO-1.5 with os21 & Q3C07 (included in the build).

Does your network provide network-based boot services (besides DHCP) to any
computers?


On Thu, Aug 30, 2012 at 12:30 PM, Mikus Grinbergs  wrote:

> With my setup I can only boot os21 on an XO-1.5 with the front panel
> 'check' button pressed.  If I try to boot without pressing any buttons, the
> boot process gets a kernel panic:  "Unable to mount root fs on
> unknown-block(0.0)".  [There is also a message "RAMDISK: Couldn't find
> valid RAM disk image starting at 0."]
>
> If I unplug my USB-ethernet adapter from the XO-1.5 before booting, the
> boot process runs correctly even when I do not press any panel buttons.
>
> mikus
>
> __**_
> 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: Setting the time

[Samuel Greenfeld]

If anti-theft is used with delegated leases (so the school server can give
leases for a few weeks at a time), the XOs will trust a signed timestamp
provided from the school server.   However olpc-update-query will only
reset the XO's clock if it is off by more than a day.

According to a comment in the code this is done to avoid messing with NTP,
except our OS builds don't currently have NTP in them.

School servers run NTP servers which NTP clients can connect to.  These are
not currently configured to support running without an external NTP source,
although they can be configured to do so.

If a locally accurate clock at the XS site is required and Internet is not
available, NTP can use a cheap USB or serial GPS unit as a time source.
Running gpsd or similar may be required depending on the GPS's supported
protocol(s).

In any case if OLPC or Sugarlabs wants to formally integrate NTP services
into our products, we should be polite and ask ntp.pool.org if we need our
own vendor subdomain.  These allow the NTP pool to shut off misbehaving
clients without affecting other users, and Fedora and CentOS already have
their own.


On Mon, Aug 27, 2012 at 9:39 AM, Tony Anderson wrote:

> Hi,
>
> In a school deployment, it is desirable that all of the XOs have the same
> time. This time should be synchronized with/by the school server (even if
> the school server is wrong). It is not reasonable to base this capability
> on access to the internet.
>
> Casio sells 'atomic' watches that synchronize to Ft. Collins by radio.
> Neat, but how does this work in Rwanda?
>
> Tony
>
> On 08/27/2012 03:19 PM, devel-requ...@lists.laptop.org wrote:
>
>> Send Devel mailing list submissions to
>> devel@lists.laptop.org
>>
>> To subscribe or unsubscribe via the World Wide Web, visit
>> 
>> http://lists.laptop.org/**listinfo/devel<http://lists.laptop.org/listinfo/devel>
>> or, via email, send a message with subject or body 'help' to
>> devel-requ...@lists.laptop.org
>>
>> You can reach the person managing the list at
>> devel-ow...@lists.laptop.org
>>
>> When replying, please edit your Subject line so it is more specific
>> than "Re: Contents of Devel digest..."
>>
>>
>> Today's Topics:
>>
>> 1. Re: Impossible to set date in 11.3.0? (James Cameron)
>> 2. Re: Firmware issu (Kevin Gordon)
>> 3. Re: Firmware issu (Kevin Gordon)
>> 4. Re: Impossible to set date in 11.3.0? (Kevin Gordon)
>>
>>
>> --**--**
>> --
>>
>> Message: 1
>> Date: Mon, 27 Aug 2012 18:43:39 +1000
>> From: James Cameron
>> To: devel@lists.laptop.org
>> Subject: Re: Impossible to set date in 11.3.0?
>> Message-ID:<20120827084339.**gh7...@us.netrek.org<20120827084339.gh7...@us.netrek.org>
>> >
>> Content-Type: text/plain; charset=us-ascii
>>
>> On Sat, Aug 25, 2012 at 01:07:35PM -0400, Samuel Greenfeld wrote:
>>
>>> To the best of my knowledge this is an intentional omission for
>>> antitheft reasons.  Instructions on how to set the clock from OFW or
>>> the command line are at 
>>> http://wiki.laptop.org/go/Fix_**Clock<http://wiki.laptop.org/go/Fix_Clock>.
>>>
>>
>> I think the task of setting the clock should be split from the
>> problems that lead to it described in that page.  It is far too scary
>> looking.
>>
>>  If using the "date" command is not sufficient to permanently store
>>> the change, "hwclock --systohc" or similar may also need to be used.
>>>
>>
>> "date" followed by a successful normal shutdown should work, because a
>> normal shutdown runs hwclock ... but "hwclock --systohc" is handy in
>> case you aren't sure that a normal shutdown will happen next.
>>
>>  In newer firmware builds (potentially newer than 11.3.0's), Open
>>> Firmware can log into a Open, WEP, or WPA-PSK secured access point
>>> and use NTP to set the time.  To do this use the "essid" command
>>> followed by the actual ESSID to set the ESSID, "wep" or "wpa" to set
>>> the password, and "ntp-set-clock" (without any parameters) to query
>>> a server from the public NTP pool and get the current time.
>>>
>>
>> The firmware included with 11.3.0 can already do ntp-set-clock with
>> open wireless access points and USB Ethernet adapters.  More recent
>> firmware fixed WEP and WPA-PSK, if I recall correctly.
>>
>> (Nothing to do with WEP and WPA-PSK in Linux though, you can stay on
>> older firmware for that.)
>>
>>
> __**_
> Devel mailing list
> Devel@lists.laptop.org
> http://lists.laptop.org/**listinfo/devel<http://lists.laptop.org/listinfo/devel>
>
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Re: Impossible to set date in 11.3.0?

[Samuel Greenfeld]

To the best of my knowledge this is an intentional omission for antitheft
reasons.  Instructions on how to set the clock from OFW or the command line
are at http://wiki.laptop.org/go/Fix_Clock .  If using the "date" command
is not sufficient to permanently store the change, "hwclock --systohc" or
similar may also need to be used.

In newer firmware builds (potentially newer than 11.3.0's), Open Firmware
can log into a Open, WEP, or WPA-PSK secured access point and use NTP to
set the time.  To do this use the "essid" command followed by the actual
ESSID to set the ESSID, "wep" or "wpa" to set the password, and
"ntp-set-clock" (without any parameters) to query a server from the public
NTP pool and get the current time.

In all cases the XO presumes the hardware clock stores time in UTC,
although some OS builds have problems if Sugar's time zone is set to
something other than UTC.

On Sat, Aug 25, 2012 at 12:05 PM, C. Scott Ananian wrote:

> A friend has 11.3.0 installed on his son's XO 1.5.  The kid complained
> that the date was wrong on his XO, and he couldn't figure out how to
> set it.  Indeed, the "Time and Date" control panel only has time zone
> selection, and no sort of network time program seems to be included in
> the build.  Was this an intentional omission?  How is the date
> supposed to be set in 11.3?
>   --scott
>
> --
>   ( http://cscott.net )
> ___
> 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: 12.1.0

[Samuel Greenfeld]

Build 20 exists for XO-1.5 but has not been released yet.  It has a
significant driver design change to prevent hanging the laptop over a
suspend/resume cycle (#12027).

Given there have not been any reports of the refactored driver crashing or
causing major issues, os20 likely will be published as a release candidate
for everyone within the next day or two.

Other that that os20 should be essentially identical to os19.

---
SJG


On Sun, Aug 19, 2012 at 1:46 PM, Kevin Gordon  wrote:

> Folks:
>
> I was reading the NZ testing email, and I think it said they were testing
> Build 20 on 12.1.0.  I can only seem to find build 19 on
> download.laptop.org.
>
> Is it somewhere else or do I just have an out-of-date mirror?
>
> Cheers
>
> KG
>
> ___
> 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: [Testing] Testing Summary, Auckland 14 July 2012

[Samuel Greenfeld]

On Sun, Jul 15, 2012 at 8:49 PM, James Cameron  wrote:

> On Sun, Jul 15, 2012 at 11:27:11PM +1200, Tom Parker wrote:
> > Rosella:
> > All the text is still tiny as reported previously. Sorry, we
> > haven???t taken it apart as recommended a while ago.
>
> You're referring to Daniel Drake's suggestions on 18th June.
> http://lists.laptop.org/pipermail/testing/2012-June/002757.html
>

This could be http://dev.laptop.org/ticket/12003 if the banner above the
OFW prompt states something like "DA" where the second letter is not a
digit.

If this is the case the XO is fine.  It just has a newer motherboard
version than what the current software build expects.

---
SJG
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Re: 12.1.0 release candidate 3 (build 16) released

[Samuel Greenfeld]

At this point in time there would have to be a significant reason to
include a full activity update as opposed to creating a new dotted activity
version with a specific fix.

As mentioned in Daniel's email the final release is currently scheduled for
July 9th.  The final build therefore needs to be tested before that date.

We are looking for versions we know are stable, not the most recent
bugfixes.

Do any of these updates have a particular fix you require or strongly
recommend?

---
SJG

On Tue, Jul 3, 2012 at 12:18 AM, Alan Jhonn Aguiar Schwyn <
alan...@hotmail.com> wrote:

>
> I forgot to mention the activities that need update (exist a newest
> version):
>
> from to
> Measure 37 42
> Portfolio21  26
> Implode 11.1  12
> Pippy 46  49
> Maze  20  21
> TurtleArt   143   148
> Terminal39 40
> Memorize  40 41
>
> Regards!
>
> Alan
>
> > Date: Mon, 2 Jul 2012 09:18:26 -0600
> > Subject: 12.1.0 release candidate 3 (build 16) released
> > From: d...@laptop.org
> > To: devel@lists.laptop.org
> >
> > Hi,
> >
> > We're pleased to announce the next release candidate of our new 12.1.0
> > software release.
> >
> > Information and installation instructions can be found here:
> > http://wiki.laptop.org/go/Release_notes/12.1.0
> >
> > Quick links for those who know which files need to be grabbed and save
> > to USB disks:
> > http://download.laptop.org/xo-1.75/os/candidate/12.1.0-16/
> > http://download.laptop.org/xo-1.5/os/candidate/12.1.0-16/
> > http://download.laptop.org/xo-1/os/candidate/12.1.0-16/
> >
> > This is a signed release candidate that can be installed on all XOs,
> > even those with security enabled.
> >
> > We're looking for testing and feedback on all aspects of the system.
> > Thanks for any help you can offer, and for all the feedback that was
> > received throughout development.
> >
> > Our scheduled release date is July 9th.
> >
> > Please review the "Known problems" section of the release notes. Some
> > documented issues are carried over from previous releases, but others
> > are new and are things that we will aim to fix in the time remaining
> > before release.
> >
> > Compared to 12.1.0 release candidate 2 (build 15), we have fixed and
> changed:
> >
> > The Welcome screen (and activity) has been updated with new content
> > providing a quick introduction on how to use Sugar and the XO.
> >
> > Implode has been fixed to show the animated help information again
> (SL#3463).
> >
> > Labyrinth can now resize images without hanging (SL#3669).
> >
> > A sugar-artwork update fixes drawing of the SpinButton widget in Read
> > and Abacus (SL#3406) and the bookmark edit area in Read (SL#3561).
> >
> > The totem media player in GNOME was failing to launch; we've reverted
> > to an older version to fix that.
> >
> > Ogg media on websites now works again: the totem-based media player
> > plugin has been fixed to display this media in most cases (#11963),
> > using WebKit's own media support in the other cases. When the webkit
> > internal audio support is used, we've fixed the display of the
> > playback controls (#11913).
> >
> > The battery meter now behaves better when plugging/unplugging AC power
> (#11957).
> >
> > Booting after activation no longer results in misnamed network devices
> > (#11967) and loss of mesh networking on XO-1 (#11975). After
> > activating, the black cursor no longer appears on top of the boot
> > animation or on the desktop (#11940).
> >
> > A new instability in the XO-1 wireless driver has been fixed (#11941).
> >
> > XO-1.5 has been fixed for manufacturing tests involving suspend/resume
> > (#11867, #11964). The manufacturing tests also exposed a bug in how
> > the wtmp file is updated on shutdown, that's been fixed too (#11952).
> >
> >
> > Thanks!
> > ___
> > 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
>
>
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Re: Outdoor Light Sensor

[Samuel Greenfeld]

Putting the light sensor only on the rear could run into issues if the
screen is facing the Sun and the rear of the XO creates a shadow.

An ugly yet isolated place to put the OLS might be in the neck of the
laptop.  But there isn't much room in that area.  You would need two
openings since the neck doesn't rotate for ebook mode, and therefore
the need to monitor the ebook switch or similar to know which
direction to trust.

It might also be possible to add one or two OLS sensors to the bottom
assembly -- one above the keyboard near the top of the slant, the
other (if necessary) in the rear above the battery.  But fixed sensors
in the bottom would not be exposed to light at the same angle as the
screen.

In any case if we move the OLS away from an obvious hole or light
pipe, children are going to have to know not to cover it with stickers
and similar.


On Wed, Jun 13, 2012 at 10:06 PM, James Cameron  wrote:
> The rear facing storage LED is of less use, since when storage latency
> is important to a user they are typically also operating the unit from
> the front.  There is no display backlight leakage that I can see
> through the rear facing light pipes.
>
> However, this mounting point would capture light behind the laptop,
> instead of light on the front.  This might also require two drivers
> for the storage LEDs instead of one.
>
> Otherwise, having disassembled the front face and thought through the
> mainframe volumes ... the only other place I can think of for a light
> pipe is ...
>
> Below the left lone USB socket, using the same front panel structure
> as for the microphone LED.  It looks to be about the same distance as
> the microphone LED is from the microphone mounting centre.
>
> However, the forward facing surface of the motherboard is certainly
> bathed in backlight.
>
> We might also do both, wiring the sensors in parallel.
>
> --
> James Cameron
> http://quozl.linux.org.au/
> ___
> 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: 12.1.0 devel build 13 released, for the XO-1, XO-1.5 and XO-1.75

[Samuel Greenfeld]

Due to a missing character in a change to olpc-os-builder[*], 12.1.0 os13
builds do not have any working Linux console terminals, and will repeatedly
try to set permissions on the /dev directory to 0600 (root-only read/write)
while trying to restart said terminals.

This permissions change on /dev will then break a lot of applications and
scripts.

To fix this, try to get into a Terminal program in Sugar or GNOME as fast
as you can, or use the serial port console (which is not time-restricted).

Then:

   1. As root or via sudo, edit the /usr/lib/systemd/system/getty@.service
   file.  Change the line:

   ExecStart=-/sbin/mingetty --loginpause --autologin root --noclear %

   to read

   ExecStart=-/sbin/mingetty --loginpause --autologin root --noclear %I

   by adding the capital letter "I" onto the end of the string.

   2. Run "sudo systemctl restart getty@tty2.service".  Repeat this
   replacing "tty2" with "tty3", then "tty4".

   3. Run "sudo chmod 755 /dev".

   4. Reboot your XO via the "reboot" command or the GUI to make sure
   nothing is hung waiting on something in the /dev directory.

[*]
http://dev.laptop.org/git/projects/olpc-os-builder/commit/?id=a9b4e062c9cbe809b26d97264068a6bc5c2e2824


On Fri, Jun 8, 2012 at 7:08 PM, James Cameron  wrote:

> For your interest, os13 for XO-1.75 contains firmware Q4D16, which
> incorrectly displays the processor core frequency.  The core continues
> to run at 800 MHz even though it may show as either 910 MHz or 800
> MHz.
>
> http://lists.laptop.org/pipermail/devel/2012-June/035324.html
>
> --
> James Cameron
> http://quozl.linux.org.au/
> ___
> 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: How-to make the XS appear in the neighbourhood view of the XOs

[Samuel Greenfeld]

I have pondered this, along with "enterprise" (larger school) XS
installations in general.

The XS typically does not control its wifi AP, so it can only be easily
shown when when users associate to its AP.  This is not necessarily a
problem, as XOs only see each other on the same network in a similar manner.

Re-enabling the Avahi service on XS 0.7 would allow the server to be
visible to XOs running Salut, as long as they were on the same network.
(It's possible to work around this same-network limit; but that would be a
kludge.)

It then would be a matter of incorporating the XS's mDNS entry it into the
network view.

However this seems somewhat silly to do for one XS.  Several support
utilities also would have to be altered to respect Sugar's choice.
Depending how XO's are setup they might accept DNS lookups via mDNS(*); so
I might take a stab at seeing what happens when an XS advertises
"schoolserver" locally even though the more formal DNS system disagrees
with that.

Something else I've thought about (which would take more work) is exposing
any classes the XS knows about so students easily can "Join" a class that
is currently in session.  This would be especially helpful if students move
from teacher to teacher during the day and do not stay in one group.

(*) I don't see this supported on recent 11.3.1 or 12.1.0 builds; but for
some reason I'm thinking this is either a regression or intentional change.


On Sun, Jun 3, 2012 at 7:46 PM, Jerry Vonau  wrote:

> Hi All:
>
> I was thinking that since the XOs uses two different methods to display
> what is seen in the neighbourhood view, how can I make the XS appear
> when using salut? I'm thinking if that can occur then maybe we could
> advertise that this is an XS. We then could have the "register to
> schoolserver" menu occur at that point, in place of using hard-coded
> names that depend on dns to work. Any thoughts on the subject?
>
> Jerry
>
> ___
> 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: XO battery/performance

[Samuel Greenfeld]

On Fri, Jun 1, 2012 at 8:07 PM, Richard A. Smith  wrote:

> On 05/30/2012 03:34 AM, Yioryos Asprobounitis wrote:
>
>  Most of the test had empty values but the informative ones (below) show
>> that the XO-1.5 is better in basic integer operations and memory bandwidth
>> while the XO-1.75 is better in float and double operations as well as in
>> memory latency.
>> I'm not sure how much this means for real life usage :-/
>>
>
> I'm very suspect of this measurement.  The 1.5 has a hardware floating
> point unit and the 1.75 is still using soft-float.  Its extremely unlikely
> that the floating point performance on 1.75 is better than the 1.5.
>

Hard FP status depends on if Yioryos is running 11.3.1 or 12.1.0.  Since he
said "os10" by today's date I'm presuming 12.1.0.

The Fedora 17 builds should be hard fp (armv7hl).  The Fedora 14-based
11.3.1 builds are not (armv5tel / armv7l kernel).
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Re: 12.1.0 devel build 12 released, for the XO-1, XO-1.5 and XO-1.75

[Samuel Greenfeld]

On Mon, May 28, 2012 at 8:02 PM, Alan Jhonn Aguiar Schwyn <
alan...@hotmail.com> wrote:

>
> Yes, I have 114 mb free.. (flash_df.png)
>
> Antoher thing:
>
> /etc/udev/rules.d/
>
> are empty. Fedora moves the rules to to other folder? Or not are any rule?
>
> I like the new menu for tests :-)  ( IMG_0069.jpg)
>
> I have problem when try to make: fs-update, not recognize the file..
> (IMG_0071.jpg)
>
>
The file name to use is 21012o2.zd, where the second zero is actually the
letter "O".  You appear to be typing two zeros.

I have asked about this ambiguity in the past; but for now we seem to be
staying with our current naming scheme.

Open Firmware distinguishes the two with a dot in the zeros visible in the
screenshot.
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Re: legousbtower kernel module

[Samuel Greenfeld]

I plugged a Belkin (Broadcom-based) USB Bluetooth adapter into two XO-1.75s
running reasonably current 3.0.19 kernels (on 11.3.1 os3x builds), as well
a XO-1.5 running a 3.3.2 kernel (on 12.1.0 os8), and all of them recognized
the adapter.

The driver used was btusb.

What build are you using and is this the Lego-supplied Bluetooth dongle not
working?

If it is the latter, I do not believe I have one available for me to test
with.

---
SJG


On Tue, May 8, 2012 at 7:08 PM, Alan Jhonn Aguiar Schwyn <
alan...@hotmail.com> wrote:

>
>
> > To: alan...@hotmail.com
>
> > Subject: Re: legousbtower kernel module
> > From: p...@laptop.org
> > CC: walter.ben...@gmail.com; b...@freudenbergs.de; aagui...@fing.edu.uy;
> devel@lists.laptop.org
> > Date: Tue, 8 May 2012 17:39:14 -0400
>
> >
> > alan jhonn aguiar schwyn wrote:
> > >
> > >
> > > > Date: Tue, 8 May 2012 14:37:29 -0400
> > > > Subject: Re: legousbtower kernel module
> > > > From: walter.ben...@gmail.com
> > > > To: b...@freudenbergs.de
> > > > CC: d...@laptop.org; devel@lists.laptop.org; alan...@hotmail.com;
> > > aagui...@fing.edu.uy
> > > >
> > > > On Tue, May 8, 2012 at 2:30 PM, Bert Freudenberg <
> b...@freudenbergs.de> wrote:
> > > > >
> > > > > On 08.05.2012, at 20:09, Walter Bender wrote:
> > > > >
> > > > >> On Mon, May 7, 2012 at 3:56 PM, Daniel Drake 
> wrote:
> > > > >>> On Mon, May 7, 2012 at 10:13 AM, Bert Freudenberg <
> b...@freudenbergs.de>
> > > wrote:
> > > >  However, /dev/usb/lego0 is not created. The corresponding udev
> rule is
> > > installed by Fedora's "nqc" rpm, but it relies on the "legousbtower"
> kernel
> > > module.
> > > > 
> > > >  Am I doing something wrong, or is it really just that the OLPC
> kernel is
> > > missing that module? If so, where can I get it? Or do I have to try
> compiling
> > > myself?
> > > > >>>
> > > > >>> I just added it for the next 12.1.0 build.
> > > > >>>
> > > > >>> Thanks
> > > > >>> Daniel
> > > > >>> ___
> > > > >>> Devel mailing list
> > > > >>> Devel@lists.laptop.org
> > > > >>> http://lists.laptop.org/listinfo/devel
> > > > >>
> > > > >> I can talk to NXT and WeDo without the kernel mode... just some
> udev
> > > > >> rules as per:
> > > > >>
> > > > >> https://github.com/itdaniher/WeDoMore/tree/master/udev
> > > > >>
> > > > >> I think these rules are already in place??? (haven't tested on
> 12.x.x)
> > > > >
> > > > > RCX 1.0 = Infrared via serial (launched 1998)
> > > > > RCX 2.0 = Infrared via USB tower (2001)
> > > > > NXT = Bluetooth (2006)
> > > > > WeDO = USB (2009)
> > > > >
> > > > > The "legousbtower" module is needed for the RCX 2.0 Infrared Tower.
> > > > >
> > > > > Including a udev rule might be a good idea though. Currently it is
> provided
> > > by the "nqc" rpm.
> > > > >
> > > > > OTOH, there is no Sugar activity that uses the RCX, AFAIK. Worse,
> I don't
> > > even know any graphical Linux application to talk to the RCX. Do you?
> > > >
> > > > Will ask the Butia team. They may have done something.
> > > >
> > >
> > > We use the Butia 1.0 with arduino board. For it, we don't need any
> special
> > > thing, because itis used with the usb like a serial device.
> > > The 2.0 version of Butia, uses a PIC18F.. that we need a udev
> rules.Someone
> > > like this:
> > > BUS=="usb", ATTRS{idVendor}=="04d8", ATTRS{idProduct}=="000[bc]",
> MODE="0666"
> >
> > so this is new since the last we discussed special rules. okay.
> >
> > > The latest build of Sugar have the udev for WeDo.Could be added the
> NXT rules.
> > > In other way, the problem with Lego is the Bluetooth dongle.The kernel
> not have
> > > the bluetooth kernel.
> >
> > which kernel doesn't have bluetooth? i thought we added bluetooth
> > support some time ago.
>
>
> The 3.0.19 for XO 1.75 not have.. In others.. I don't know..
>
>
>
> ___
> 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: [Sugar-devel] Wanting to know a bit of (NetworkManager) workflow upon resume-from-suspend

[Samuel Greenfeld]

It's worth noting that half the battle can be won by overriding the
following XO-1 specific line in OLPC OS Builder's kspost.50.xo1-tweaks.inc:

gconftool-2 --direct --config-source
xml:readwrite:/etc/gconf/gconf.xml.defaults --type bool --set
/desktop/sugar/network/adhoc false

Setting this to "true", or letting it default to such will show the Ad-hoc
networks by default on XO-1.  It also will cause XO-1's to default to
Ad-hoc if no preferred network is found.

The mesh networks will still be there for manual use; but right now they
seem semi-broken anyway on 12.1.0 as we attempt to connect to "Mesh Network
0" and don't set a channel on the Interface.


On Wed, May 2, 2012 at 10:29 AM, Martin Langhoff
wrote:

> On Wed, May 2, 2012 at 10:18 AM, Ajay Garg  wrote:
> > Good News.
> >
> > I managed to get this working (albeit via changes in sugar).
> >
> > The details are at ::
> >
> http://git.sugarlabs.org/dextrose/mainline/commit/4ac1a5300f4c43608b0f009a23d966d404a15632
>
> The patch seems fairly wrong to me. You are hiding the mesh icons in
> sugar, but the mesh is active. Packet forwarding is still happening.
>
> One of the top reasons we stopped using mesh is because it saturates
> the RF spectrum, which is a bad thing to do when you have many users
> in a small space (ie: in a school).
>
> You had the mesh disable trick working on F11, and (I assume) happy
> users of that feature. With this, the feature is broken, but you're
> making the UI look right...
>
> cheers,
>
>
>
> m
> --
>  martin.langh...@gmail.com
>  mar...@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
> ___
> 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: CliqueRM / telepathy-salut capture file request

[Samuel Greenfeld]

I uploaded a packet dump for you of two XOs sharing a simple Chat Activity
over Salut, which uses Clique.  The Second XO shares the activity, and the
First one joins it.  They then alternate sending messages back and forth
twice.   The First system then leaves the activity followed by the Second
system shutting the activity down.

http://dev.laptop.org/~greenfeld/temp/clique/filtered.cap

This capture has been filtered by MAC address to only show the two XOs in
use.  They were on an Ad-hoc wireless network with no other systems
connected.

Normally I work at much higher level, but if there is specific information
that you need I will try and get it for you.


On Mon, Apr 2, 2012 at 1:46 PM, Gerald Combs  wrote:

> Hi,
>
> A patch to add CliqueRM support to Wireshark has been sitting in our
> queue for the past four years:
>
>https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=2076
>
> We typically don't add a dissector to Wireshark unless we have a sample
> packet capture to use for fuzz testing. Would it be possible for someone
> to generate a capture and attach it to the bug? Otherwise I'll have to
> reject the patch due to a lack of response.
>
>
> --
> Join us for Sharkfest ’12! · Wireshark® Developer and User Conference
> Berkeley, CA, June 24-27 · sharkfest.wireshark.org
> ___
> 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: Multi-laptop naming scheme for build files

[Samuel Greenfeld]

Personally I think the convention should be the same, even if we have to
add a dash, or reverse the historical build numbering approach (e.g.
880os1.zd4 -- presuming 8.3 filenames legally can start with a number).

Telling a non-technical user to "copy all the files ending in 0 & 2" is a
lot easier than telling them that some files have an "a" and some have an
"0", and that they may also need "c" and "2" files.

On Wed, Mar 14, 2012 at 8:00 PM, Daniel Drake  wrote:

> On Wed, Mar 14, 2012 at 5:53 PM, Samuel Greenfeld 
> wrote:
> > For example:  If fs.zip is not found, an XO-1 will try fs0.zip, an XO-1.5
> > will try fs1.zip, and an XO-1.75 will try fs2.zip.  The same is true with
> > bootfw.zip & other files used by XOs when security is enabled.
>
> Yes, I agree. My thread is about naming of the other file needed for
> imaging - the .zd file in the XO-1.5/XO-1.75 case. This is not only
> for unsecure flashing, it is also needed in the secure path.
>
> Daniel
>
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Re: Multi-laptop naming scheme for build files

[Samuel Greenfeld]

What James is referring to is that newer Open Firmware builds *already*
know to use 0,1,2 to distinguish signed XO-1, 1.5, & 1.75 installation
files respectively.

The unsigned files still need a scheme to be made distinguishable; but
unless we want to change OFW we should stick with what it knows.

For example:  If fs.zip is not found, an XO-1 will try fs0.zip, an XO-1.5
will try fs1.zip, and an XO-1.75 will try fs2.zip.  The same is true with
bootfw.zip & other files used by XOs when security is enabled.


On Wed, Mar 14, 2012 at 7:39 PM, Gonzalo Odiard  wrote:

> Why not use the same prexix as in the firmware:
>
> XO-3 = Q5
> XO-1.75 = Q4
> XO-1.5 = Q3
> XO-1 = Q2
>
> Is not better, but value is having a single convention.
>
> Gonzalo
>
>
> On Wed, Mar 14, 2012 at 6:29 PM, Daniel Drake  wrote:
>
>> Hi,
>>
>> Right now, build files for XO-1.5 and XO-1.75 have the same filename
>> (#11226). There have been a few requests that we move to a naming
>> scheme that has a different filename in this case so that the files
>> can live together on a USB disk and generally not be so easily
>> confused.
>>
>> Some work needs to be done before that is possible, but we also need a
>> naming scheme. I think the key considerations for this are:
>>
>> 1. Future proofing. It should be resilient to the introduction of
>> future products that use the same architecture and disk image format.
>>
>> 2. Short names. OFW only understands 8.3 for FAT. Also, deployments
>> sometimes like to customise the 8 part too e.g. per703-2.img for Peru,
>> and I've seen others putting codes after the osXXX part, e.g.
>> os880j.img. Let's try and leave space for customisation here.
>>
>> 3. Uses only file name (the 8 part), not the extension (the 3 part).
>> This sticks with general computing world conventions and agrees with
>> some olpc-os-builder implementation details which allow the user to
>> customise the name but not extension, where olpc-os-builder can
>> guarantee that output files from different modules do not have
>> conflicting names.
>>
>>
>> Based on this and previous discussions I think we could go with something
>> like:
>>
>> 1. single-character ID for product type. 'a' for XO-1, 'b' for XO-1.5,
>> 'c' for XO-1.75, ...
>> 2. build number
>> 3. a "."
>> 4. extension
>>
>> e.g.
>>
>> 'a900.img' - build 900 copy-nand image for XO-1
>> 'b900.zd4' - build 900 4GB image for XO-1.5
>> 'c900.zd4' - build 900 4GB image for XO-1.75
>>
>> Thoughts/other ideas?
>>
>> Thanks,
>> 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
>
>
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Re: Impacts of disabling Automatic Power Management

[Samuel Greenfeld]

Disabling suspend during collaboration was discussed a year ago, but as far
as I know this has not made it into any 11.3.x build:
http://dev.laptop.org/ticket/10363

There might be a few 10.x.x builds with this change but I would have to
research this to confirm one way or another.


I could easily see USB GSM modems being unhappy about repeatedly losing
power, as my USB CDMA modem resets itself every time that happens.  This
then requires it to reacquire a connection to the tower, reset the
computer's PPP link to the modem, etc.  This may require the XO to stay
powered on via a usb-inhibits rule, network manager script, or Sugar's
GSM/NM monitor whenever the connection is active.

But unless the GSM/3G connection is being used to contact a school or other
collaboration server I think these are two independent problems.


On Sat, Feb 4, 2012 at 7:45 AM, Richard A. Smith  wrote:

> On 02/04/2012 12:28 AM, Sridhar Dhanapalan wrote:
>
>  Let's _not_ include it in the development builds, so developers and
>>> testers suffer (and fix).
>>>
>>> end users need not suffer.
>>>
>>
>> +1 for this. This is negatively impacting classrooms. Teachers are
>> shying away from using collaboration. We don't have time to wait for a
>> 'perfect' solution.
>>
>
> I wasn't suggesting that we don't come up with a workaround for your
> current problem.  I was commenting that adding a hook into sugars API that
> globally disables suspend while collaboration is active is headed in the
> wrong direction.
>
>
> --
> Richard A. Smith  
> One Laptop per Child
> __**_
> 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: XULRunner Version 1.9 Issue Reading Local Files With No Internet Connectivity

[Samuel Greenfeld]

I'm not very familiar with xulrunner, but are you running a local webserver
in your application?

If your application does not have its own webserver, I would expect you
would have to use the file:// URI handler, like the Browse activity does.
You may have to dynamically create this URI after determining the path the
content is stored in, as there is no guarantee besides on XOs of all
content being somewhere below /home/olpc.



On Wed, Jan 11, 2012 at 4:37 PM,  wrote:

> I am aware that the OLPC project is moving into Webkit for future
> projects. However, it is necessary to complete a current project on
> XULRunner.
>
> With the OLPC laptop disconnected from the Internet, I try to startup
> XULRunner and read local files using the browser tag like this:
>   src="http://localhost/myfile.**html"
> autoscroll="true" flex="1"/>
>
> With XULRunner 1.9, the screen remains blank, and the file is not loaded.
> I installed XULRunner 8.0 on the OLPC laptop. I am not able to replicate
> the problem with XULRunner version 8.0(that is, the application starts
> correctly and reads the local files as expected.)
>
> Given that XULRunner 8.0 may not be installed on the OLPC, are there any
> suggestions that I could use to get XULRunner 1.9 to read local files?
>
>
> __**_
> 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: 11.3.1 build 15 released for XO-1.75

[Samuel Greenfeld]

On Thu, Dec 1, 2011 at 1:23 PM, Frederick Grose  wrote:

> On Thu, Dec 1, 2011 at 12:23 PM, Martin Langhoff wrote:
>
>> OS 15 is additionally understood to fix
>>
>> #11416 C1 XO 1.75s may not wake up due to RTC from suspend
>> #11462 Kernel crash seen initializing EC support on a 1.75 B1
>>
>> Please help us test in build!
>>
>
> I shut down os15, but the power LED is still on.
>

This might be a case of #11359 (Psmouse kernel panic on shutdown) if your
laptop has an AVC (FSPPS/2) touchpad.

If the screen just is blank and you did not have a serial adapter connected
during shutdown, it may or may not be possible to figure out if it was
something else.

---
SJG
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Re: Activities won't auto-install from USB "bundles" folder onto 11.3.0?

[Samuel Greenfeld]

Thanks for the report; I filed a ticket found at
http://dev.laptop.org/ticket/11432 to track the issue.

If you can provide more information about how it fails that would be
appreciated.

---
SJG


On Wed, Nov 9, 2011 at 8:19 PM, Adam Holt  wrote:

>  Any reason auto-installation of Activities is failing on Release 11.3.0
> = Build 883 XO-1s, from a USB stick's "bundles" directory?
>
> The "bundles" & "boot" directories worked from the exact same USB stick
> onto build 860 (and build 874 too I think).  Very sadly these instructions
> suddenly seem not to work anymore: (for us!)
>
> http://wiki.laptop.org/go/Customization_stick
>
> I tried 4 different brands of USB memory sticks to be sure -- anything
> else I can try?  We've tried this both during the clean install to 11.3.0,
> and separately after completing these reflash steps:
>
> http://wiki.laptop.org/go/Release_notes/11.3.0#XO-1
>
> Manually installing our 16 custom Sugar Activities across 50 XOs will be a
> *huge* drag/drain overnight; we're rather desperate if folks have any ideas
> at all!
>
> --
> Help kids everywhere map their world, at http://olpcMAP.net 
> 
>
>
> ___
> 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

XO-1.5 microphone jack supports stereo recording

[Samuel Greenfeld]

Walter Bender recently pointed out to me that the Microphone jack on the
XO-1.5 supports stereo recording.  This is a bit unusual or at least
unexpected, as I have mostly seen monaural computer microphones.

I have since confirmed that this is true, and the stereo separation appears
to work properly with audio signals.  The functionality is actually
mentioned at http://wiki.laptop.org/go/XO_1.5#External_connectors , but easy
to glance over.

So feel free to make applications which use dual-channel or two analog
sensors, as they should work properly.

And if I'm incorrect or there is a limitation, I'm sure someone will
explain.

---
SJG
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Re: 11.3.0 build 4 released, for *XO-1.75*, XO-1.5 and XO-1

[Samuel Greenfeld]

The version logic is indeed present for all signed files (fs.zip bootfw.zip,
...) in newer XO firmware builds.  That is to say - if no fs.zip or similar
file without a digit is found, each platform will then look for an fs#.zip
file with the appropriate digit.   Older XO-1 and XO-1.5 firmware builds do
not have this logic, so people doing significant upgrades of these will
still need to only have one XO-1 or XO-1.5 fs.zip file on the USB stick at a
time.

But the signed files still reference unsigned files.  So the fs?.zip files
themselves will need to point to different file names.

Currently builds are unsigned.  To the best of my knowledge there is no
separate "developer unlocked" signing key we could use for wide-scale
testing.

---
SJG


On Fri, Sep 9, 2011 at 10:17 PM, James Cameron  wrote:

> On Fri, Sep 09, 2011 at 08:14:12PM -0400, Kevin Gordon wrote:
> > I have another silly request.  For those of us testing on multiple
> > platforms, the download file names for both the 1.75 and 1.5 image are
> > now the same: i.e.: os4.zd4.  It would be nice to be able to
> > differentiate between the two, as in the easy way it was for uim/onu
> > for XO-1 vs zd4/zsp for XO 1.5 on previous downloads.
>
> I'd prefer not to solve your problem in that way.  That difference was
> an accident of file format.  We use the same file format for XO-1.5 and
> XO-1.75.
>
> Rather, what we have is automatic installation using the four game keys
> method, which will search for a file name that matches the hardware,
> such as
>
> fs0.zip for XO-1
> fs1.zip for XO-1.5
> fs2.zip for XO-1.75
>
> So you could have on your USB drive the following files:
>
> os874.zd4 (from 11.2.0 for XO-1.5),
> os874.zd4.zsp.fs.zip, renamed to fs1.zip,
> os874.img (from 11.2.0 for XO-1),
> os874.img.fs.zip, renamed to fs0.zip,
> os880.zd4 (from 11.3.0 for XO-1.75),
> os880.zd4.zsp.fs.zip, renamed to fs2.zip,
>
> ... and then the USB drive would work for any model.
>
> To that end, I'd like to see the os${BUILD}.zd4.zsp.fs.zip files
> included on build.laptop.org.
>
> Non-technical users will need their USB drives prepared for them.
>
> --
> James Cameron
> http://quozl.linux.org.au/
> ___
> 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: booting issue with xo-1.75

[Samuel Greenfeld]

I think this is likely an audio issue; either you held down a key when
turning on an XO which open firmware from playing its startup sound, or you
turned the volume control for the startup chime all the way down.

http://dev.laptop.org/ticket/11082 states that the os41 software build
supposedly fixes this.  It should be run with the latest firmware, which is
currently Q4B08.

Since you are getting into Linux you should not have to open the XO to
reflash via the #11089 fix again.  You should be able to just break into OFW
by using the ESC key when the startup sound plays, insert a USB stick with
Q4B08, and type "flash u:\q4b08.rom" with external and battery power
present.

---
SJG


On Sun, Sep 4, 2011 at 1:09 PM, Bert Freudenberg wrote:

>
> On 04.09.2011, at 18:33, carcellelist wrote:
>
> > Dear xo developers,
> >
> > i received a xo-175 a few days ago and i got it to partially boot from
> the uart
> > interface with the serial adapter (using "boot" at the firmware "ok"
> prompt) but i get
> > stuck here :
> > ...
> > [  647.362835] mmc2: no vmmc regulator found
> > [  647.370325] mmc2: SDHCI controller on MMC [sdhci-pxa.2] using DMA
> > [  647.381468] drivers/usb/core/inode.c: creating file '002'
> > [  647.392072] usbcore: registered new interface driver usbhid
> > [  647.401205] usbhid: USB HID core driver
> >
> > Is anyone experiencing the same issue ? am i missing something during the
> boot ?
>
> You need to flash a newer firmware. This is explained here:
>
>http://wiki.laptop.org/go/XO_1.75_11089_Fix
>
> For more info on the XO-1.75, read
>
>http://wiki.laptop.org/go/XO_1.75_B1
>
> - Bert -
>
>
> ___
> 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: [Testing] A small deployment of 11.2.0

[Samuel Greenfeld]

No, it should not be an issue to add Labyrinth (a mind mapper) back on to an
XO-1, or most activities that used to work on it.

It was more a space constraint that anything else.

---
SJG
On Aug 24, 2011 12:34 AM, "Caryl Bigenho"  wrote:
>
> Hi Folks!
>
>
> You asked anyone who plans to deploy 11.2.0 to let you know so you can
keep them informed of fixes for remaining issues. That's me. I will be
collecting 10 XO-1s from a stalled Contributors Program project at Montana
State University and re-deploying them to a school in rural Montana. I plan
to reflash all of them with 11.2.0 this week before delivering them next
week.
>
>
> I will be meeting with 2 of the involved teachers next week to get them
oriented on the machines. Among other things, I plan to show them how to
update the software as new releases come out. When I am away in California
for the winter, I will be able to assist them via Skype as needed.
>
>
> We have discussed collaboration and they would like to use it, but we can
wait for that until it is more reliable. Any news on updates with fixes will
be greatly appreciated.
>
>
> I have one unrelated question for you folks. I notice Labyrinth is
included on the software for the XO-1.5 but not on the XO-1. Is this a space
issue? Will there be a problem if I add it? When we were visiting schools in
Uruguay we saw a lot of good of examples of ways to use Labyrinth. When I
asked one seven-year-old what his favorite program was I was very surprised
when he answered "Labyrintino!" It's a real winner!
>
>
> Caryl
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Re: [OLPC Engineering] [Techteam] New F14-arm build os40 - Almost in sync with x86!

[Samuel Greenfeld]

At this point (with my limited knowledge) I don't believe o-o-b uses the
Wiki at all.  It just looks straight at activities.sugarlabs.org for the
latest experimental activities compatible with Sugar 0.92.

See the [sugarlabs_activities] section of
http://dev.laptop.org/git/projects/olpc-os-builder/tree/examples/f14-xo1.5.ini,
which the git changelog says currently is the initial 11.3.0 XO-1.5
configuration.

The 11.2.0 INI examples in the same directory have an example of a
[sugar_activity_group] section being used, but the 11.3.0 config does not
have one yet as it is not frozen.


On Tue, Aug 23, 2011 at 9:36 AM, Chris Ball  wrote:

> Hi,
>
> On Tue, Aug 23 2011, Reuben K. Caron wrote:
> >> You should modify the subpage for the release you're working on --
> >> see e.g. http://wiki.laptop.org/go/Activities/G1G1/11.2
> >
> > In that case, the .ini should be altered:
> >
> > [sugar_activity_group]
> > url=http://wiki.laptop.org/go/Activities/G1G1
>
> No.  That string's just providing the base URL to use -- when o-o-b is
> looking for activities, it will append the major/minor/release version
> numbers to it.
>
> - Chris.
> --
> Chris Ball  
> One Laptop Per Child
> ___
> 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: [Testing] New prototype XO-1.75s in Auckland, New Zealand

[Samuel Greenfeld]

http://dev.laptop.org/ticket/10528 is one such ticket, although we have two
types of touchpads in production and two alternate candidates I am aware of
(samples of which should be at Cambridge office).

I would be cautious about attempting to identify touchpads via psmouse/DMI;
three of the four samples seem to identify themselves as some variant of
"IM{Ex}PS/2 Generic" just like web browsers tend to identify themselves as
"Mozilla compatible".


On Mon, Aug 22, 2011 at 8:30 AM, Paul Fox  wrote:

> kevin wrote:
>  > On Mon, Aug 22, 2011 at 7:54 AM,  wrote:
>  >
>  > >
>  > >
>  > > The mouse pad now registers clicks, can this be disabled? Needs a my
>  > > settings item.
>  > >
>  >
>  > I think a nice solid tap on my new 1.5 trackpad registers clicks too.  I
>  > agree that it would be best to be an optional setting, and as is, is
> very
>  > sensitive right now on the 1.75.
>
> i thought we had a new ticket open for this, but perhaps not.  the
> manufacturer has introduced a new touchpad once again (this is the
> third one (not counting the original ALPS dual-mode version), and
> once again we'll have to figure out how to disable tap-to-click.
> (but i'm not sure whether this new version will be used in production
> or not -- it might just be the B units.)
>
> paul
>
>  >
>  > >
>  > > ___
>  > > Devel mailing list
>  > > Devel@lists.laptop.org
>  > > http://lists.laptop.org/listinfo/devel
>  > >
>  > part 2 text/plain 135
>  > ___
>  > Testing mailing list
>  > test...@lists.laptop.org
>  > http://lists.laptop.org/listinfo/testing
>
> =-
>  paul fox, p...@laptop.org
> ___
> 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: XO 1.5 Solder Reflow in Toaster Oven

[Samuel Greenfeld]

It's probably also worth noting that to the best of my knowledge, no one at
OLPC would recommend to typical XO users sticking any part of an XO in a
toaster oven.

If we encounter a laptop which we believe has this soldering issue, we
usually send it back to the factory instead of attempting to repair it
ourselves.


On Sun, Aug 21, 2011 at 6:41 PM, James Cameron  wrote:

> Some meagre feedback ... remember to remove the real-time clock battery,
> the microSD card, the wireless card, and the camera.  Not suggesting
> this is an exclusive list; there are other things to remove.
>
> --
> James Cameron
> http://quozl.linux.org.au/
> ___
> 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: Registering to XS stable FC9 0.6 with XO stable FC14 11.2.0

[Samuel Greenfeld]

My guess would be it seems to depend on the schoolserver, at least from a
sampling of two schoolservers.

http://dev.laptop.org/ticket/11056 was filed because 11.2.0 XOs would not
register to a schoolserver I was running that 10.1.3 XOs historically have
had no issues with.  The error message provided would seem to match what you
are reporting.


In general 11.2.0 has been marked as a "preview" release, especially due to
collaboration issues.  But if you entered the schoolserver's FQDN in the
Control Panel (i.e. "schoolserver.example.net", not as a URL), that should
have allowed collaboration over Jabber to mostly work.


On Sun, Jul 24, 2011 at 9:36 PM, Anna  wrote:

> I was trying out 11.2.0 and attempted to register to my XS 0.6.  Sugar gave
> me "Registration Failed. Cannot connect to the server."
>
> However, when I open Browse and click on the "Local schoolserver" link, I
> get my XS homepage.  When I ping schoolserver, the XO knows the schoolserver
> is at 172.18.0.1.
>
> I can manually connect to Jabber over the LAN when I go to XO Guy -> My
> Settings -> Network -> Collaboration and enter in my XS URL.  But I can't
> see "XO Guys" in my network neighborhood.  I tested Chat and it works if I
> invite the FC14 XO from another machine and then click the chat invitation
> on the FC14 XO, but obviously that is not ideal.
>
> To be sure I didn't jack up something on my XS, I tested registration from
> a freshly flashed FC11 OS860.  Worked fine, saw "XO Guys" and all that.
>
> The XOs have cooperated great with XS 0.6 up until the FC14 11.2.0 build.
> Are there known issues or workarounds that I've missed?
>
> Has anyone been able to register to XS 0.6 with an XO running 11.2.0?
>
> Anna Schoolfield
> Birmingham
>
> ___
> 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: Reassembled XOs fail heat spreader test

[Samuel Greenfeld]

The "unused" hole actually is filled by one of the screws which holds in the
rear plastic panel.  That's why the screw holes which only secure the heat
spreader have arrows pointed at them.

The fanciest (newest?) XO-1.5 heat spreader design I've seen adds a support
bar up to the green screw hole above near your area of concern, again filled
by a screw used to secure the back cover.  I'm not certain though if this is
the design John is referring to, but I have seen a few XO-1.5s with it.

It may be possible to bend the existing heat spreader in a certain manner
which solves the problem.  But I would *not* be someone who could recommend
this approach for deployments.

Some of OLPC's hardware engineers may be traveling this weekend, so I'm just
trying to provide you with a quick explanation in the meantime.



On Fri, Jul 22, 2011 at 9:55 PM, Sridhar Dhanapalan
wrote:

> All of the XOs I've seen have three screws on their heat spreaders.
> I've attached an annotated image. Hopefully the lists don't strip it
> out.
>
> There is an unanchored screw point in the bottom-left. However, the
> danger area is at the top, particularly in the top-left. This affects
> contact between the heat spreader and the Companion Chip, and might
> also be affecting contact with the CPU. Do the four-screw versions of
> the heat spreader address this problem?
>
> Thanks,
> Sridhar
>
>
>
> On 23 July 2011 01:21, John Watlington  wrote:
> >
> > Do your heat spreaders have four screws or three ?
> >
> > The final heat spreader for XO-1.5 production had four screws
> > holding it down, to ensure a good fit.If your heat spreaders
> > only have three, OLPCA should be able to get proper replacements
> > from Quanta.
> >
> > Regards,
> > wad
> >
> > On Jul 22, 2011, at 10:35 AM, Sridhar Dhanapalan wrote:
> >
> >> We are currently engaged in changing the motherboards in over a
> >> hundred XO-1.5s. In many cases, the XOs are failing the heat spreader
> >> test afterwards.
> >>
> >> However, we can get the test to pass if we press down on the lid,
> >> behind the screen. This suggests to me that the heat spreader is not
> >> in proper contact with the chips.
> >>
> >> Without the lid plastic affixed (heat spreader exposed), we can see
> >> that the spreader is not touching the chips properly. We have tried
> >> bending the metal slightly near the screw points, but the contact
> >> doesn't last.
> >>
> >> Is there any way that we can deal with this better? We are changing
> >> the motherboards in these XOs because they have succumbed to
> >> overheating. I want to avoid that from happening again.
> >>
> >> Thanks,
> >> Sridhar
> >>
> >>
> >> Sridhar Dhanapalan
> >> Engineering Manager
> >> One Laptop per Child Australia
> >> M: +61 425 239 701
> >> E: srid...@laptop.org.au
> >> A: G.P.O. Box 731
> >>  Sydney, NSW 2001
> >> W: www.laptop.org.au
> >> ___
> >> 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
>
>
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Re: [Localization] Fwd: Updated 11.2.0 schedule

[Samuel Greenfeld]

I was writing a detailed reply, but Martin beat me to the Send button.

Just to clarify a few points (which I think you may have been asking):


   - The two main organizations within OLPC each have a test/QA engineer
   helping them.  James Cameron tends to focus more on the low-level hardware;
   I tend to focus more on the higher-level software.  Beyond that there is a
   test...@lists.laptop.org mailing list, and a volunteer test group in New
   Zealand as well as other groups/individuals that casually test and provide
   feedback as well.

   When possible, we do try to support upstream test efforts, and file bugs
   upstream when appropriate.  But I do not currently work on testing Sugar for
   non-related distributions like Ubuntu, although I do have one 10.04 LTS
   system with Sugar running in it.


   - If you are looking for a formal test case management system which can
   be used to store test cases, view things not yet done, and assign tasks,
   OLPC currently does not have one.  Various groups & people have proposed
   setting up these for OLPC, and some have used them amongst themselves.
   There is a crude TCMS within OLPC's wiki that can log results and show you
   that log, but I tend to avoid it due to its habit of caching stale results
   and personal frustration.

   One recent idea has been to try Fedora's Nitrate TCMS when that goes
   online, and ask them to support OLPC builds for test case plans in addition
   to Fedora versions.  But a preview version of that system is not available
   yet.


   - We do have a large number of test cases and a crude system within the
   Wiki, but they mostly have not been updated since 2008.  But I have tagged
   test cases in this system that I feel are still relevant for 11.2.x, and
   added a few new ones.

   In addition to these tests I keep a personal spreadsheet of general focus
   categories (clean start/stop, save/restore, collaboration, etc.) I would
   like to test with each activity as well as for the base system, and note
   with which build/activity/platform I last ran that task.  It's not perfect,
   but it saves me writing test cases for 40+ activities that only vary
   slightly in many ways.


   - There is a "1 hour" build verification/smoke test for 11.2.0 at
   http://wiki.laptop.org/go/Smoke_test/11.2.x/1_hour_smoke_test .  It is
   getting somewhat lengthy though since I was asked to include verification of
   all high-priority activities that kids commonly use.


   - For 11.2.0, I have gone through every activity on the XO-1 and XO-1.5
   and tested basic single-user functionally for all of them that worked at the
   time.  I am hoping that the collaboration stack gets reasonably stable soon
   so that multi-user functionality can be tested as well.

   The other main area I would like to check this time around is mime
   types.  Some activities tend to claim they can handle things like audio
   files, but are not well equipped to handle them if actually given to open,
   as they were only expecting to embed them into something else, etc.  There
   may also be some activities which should claim functionality that they
   don't, and some defaults applications for mime types that are undefined.


   - In general though I agree we need a better way to split the load if
   other formal test volunteers are available.  In addition to 11.2.0, I am
   often asked to look at the XO-1.75, new potential motherboard or firmware
   revisions before they are mass produced, or anything interesting thing of
   the moment (currently "How much of a speedup and/or RAM benefit do we really
   get by prelinking?").

   I would be open to hearing any ideas you may have as well.


---
SJG


On Sun, May 22, 2011 at 8:32 PM, Martin Langhoff
wrote:

> On Sun, May 22, 2011 at 1:26 AM, Edward Cherlin 
> wrote:
> > At the end of your e-mail, you wrote
> >> Testing is much appreciated.
> > It sounds as if there is no formal testing process for Sugar on XOs.
>
> Hi Ed - For Sugar on XO, we definitely have Sam Greenfeld (QA) and
> Gonzalo Odiard (lead Activity developer) doing a very good job of it.
> That's why we have the activities in very good shape (try one of our
> recent devel builds), and there's also lots of bugs filed, describing
> many issues in good detail.
>
> If you can help with testing, and want to coordinate to avoid
> duplicating work and picking interesting areas to focus on -
> coordinate with Sam.
>
> Other distros -- well, are up to other distros.
>
> > Where is the process from your point of view?
>
> Until now we've been grabing latest activity from ASLO. Now Daniel has
> switched to 'freeze' the activity versions. Sam will go through them
> once more, and bugs in activities will enter our triage selection. The
> activity maintainers and Gonzalo will work on fixing priority bugs,
> and a new version of the affected activities will be released which
> will be hand-picked to be updated in our builds.
>
> That's a short summary - I p

Re: Prelink

[Samuel Greenfeld]

In general every major Fedora jump we do risks running out of space.  In
addition to upgrades, they also did a mass recompile for the upcoming F15
release.  As long as we use a hardlink/multiple-root/rsync approach, I do
not see an easy answer to this.

What seems to be missing (in this discussion, and perhaps in the utility) is
support in the OS builder to incrementally update based on a previous
build.  Prelink is capable of keeping a cache of what was previously done,
and running in an incremental mode where only the necessary binaries are
updated.

This would solve much of the grief with minor updates, where we only pull in
selected RPMs.

An alternative which might be even less disruptive would be to run prelink
on 11.2.0, and use that image as the base to create future 11.2.x, builds.
We would then tolerate collisions due to updates pulled in past that point.
This has the downside though that changing something low level like glibc
could result in an across-the-board performance penalty.




On Wed, May 18, 2011 at 8:13 AM, Paul Fox  wrote:

> james wrote:
>  > On Wed, May 18, 2011 at 07:45:49AM -0400, Kevin Gordon wrote:
>  > > Might be over my head in the specific prelink OLPC talk here, but in
>  > > my experience on the iSeries - anything that optimizes a software
>  > > update process (which happens twice a year) at the expense of a
>  > > program loads or the object instantiation process (which happen
>  > > thousands of times an hour) is a bad trade-off.
>  >
>  > +1
>
> but unless i misunderstood dsd, prelink is making our update process
> non-functional.
>
> paul
> =-
>  paul fox, p...@laptop.org
> ___
> 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: [Sugar-devel] Lego WeDo with Scratch

[Samuel Greenfeld]

With the planned 11.2.0 release, the WeDo plugin should come included &
enabled by default.  Current 11.2.0 development builds include it.

I tested it a bit with a two-sensor+motor WeDo kit, although for some reason
I could only get it to control two devices at a time (passing a sensor
through the motor's connector didn't seem to work).


On Tue, May 17, 2011 at 5:54 PM, Claudia Urrea  wrote:

> Sameer, you will have to install the plugin. I would have expected that
> this was already included in the latest version.
>
> Open terminal and run
>
> cd /home/olpc/Activities/Scratch.activities
> sudo ./installWeDoRules.sh
> mv WeDoPlugin-disabled WeDoPlugin
>
> Let me know if this works!
>
> Claudia
>
> On Tue, May 17, 2011 at 3:56 PM, Sameer Verma  wrote:
>
>> Wondering if anyone has had success with running Lego WeDo sensors
>> with Scratch on a XO 1.5
>>
>> Once plugged, I see that the XO recognizes it, but I am unable to get
>> Scratch to show any input from  the sensors.
>>
>> cheers,
>> Sameer
>> ___
>> Sugar-devel mailing list
>> sugar-de...@lists.sugarlabs.org
>> http://lists.sugarlabs.org/listinfo/sugar-devel
>>
>
>
>
> --
> Claudia Urrea, PhD
> Director of Learning
> OLPCA
>
> ___
> 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: [Sugar-devel] [IAEP] XO power management hindering collaboration

[Samuel Greenfeld]

In what build(s) is this occurring?  And are you using a schoolserver or
not?

OLPC release 10.1.3 fixed some issues with XO 1.5's waking up in response to
multicast traffic on the network.  This is necessary for Salut/"under the
tree" usage to work with power management.  XO-1's with 10.1.3 are
configured by default to always stay on, as they (to the best of my
understanding) historically have had an occasional issue where the network
card might not reappear after suspending.

In 11.2.0 both XO-1's and 1.5's currently are allowed to suspend, although I
do not know if that will be the final setting.


On Sun, May 15, 2011 at 12:40 PM,  wrote:

> On Sat, May 14, 2011 10:04 am, Sridhar Dhanapalan wrote:
> > It's looking to us that the aggressive power management enabled on the
> > XO can sometimes create confusion when children are collaborating on
> > activities.
> >
> > Take for example a turn-based game like Memorise. If a child is
> > waiting for their turn, they might leave the XO untouched. In that
> > time, power management can kick in, and the XO stops communicating
> > over the wireless network. Waking up the XO (e.g. by touching the pad)
> > doesn't always rejoin the XO to the game properly. The whole game is
> > stalled because the turn cannot be completed.
>
> Is this in the bug tracking system? If not, please file a bug report. (We
> can help.) If it is, please add your experience to the existing bug
> report.
>
> > Are there any ways we can manage this in our deployments? Perhaps some
> > guidelines to give to teachers so that they have a reasonable
> > expectation?
>
> An obvious workaround is to keep touching the XO so that it does not go to
> sleep.
>
> The more clumsy process is for the active player to exit and save, then
> open the saved Journal entry and share again.
>
> > Thanks,
> > Sridhar
> >
> >
> >
> > Sridhar Dhanapalan
> > Technical Manager
> > One Laptop per Child Australia
> > M: +61 425 239 701
> > E: srid...@laptop.org.au
> > A: G.P.O. Box 731
> >  Sydney, NSW 2001
> > W: www.laptop.org.au
> > ___
> > IAEP -- It's An Education Project (not a laptop project!)
> > i...@lists.sugarlabs.org
> > http://lists.sugarlabs.org/listinfo/iaep
> >
>
>
> --
> Edward Mokurai
>
> (默雷/धर्ममेघशब्दगर्ज/دھرممیگھشبدگر
> ج) Cherlin
> Silent Thunder is my name, and Children are my nation.
> The Cosmos is my dwelling place, the Truth my destination.
> http://www.earthtreasury.org/
>
> ___
> Sugar-devel mailing list
> sugar-de...@lists.sugarlabs.org
> http://lists.sugarlabs.org/listinfo/sugar-devel
>
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Re: xkeyboard-config map for olpcm -- upstream discussion

[Samuel Greenfeld]

What is the current status of this effort?  While it looks like the work is
completed for most XO keyboard styles, the patch for the mechanical/HS
keyboards ( https://bugs.freedesktop.org/show_bug.cgi?id=34738 ) currently
is in a NEEDINFO state, and work on the Fulah keyboard (Freedesktop bug
#35813) might still be ongoing.


I have started a page http://wiki.laptop.org/go/11.2.0/Keyboard_Testing to
cover testing the upstream integration.  If you have an XO with an
internationalized keyboard and a similar keyboard for a non-XO computer, I
would especially appreciate if you could install the current 11.2.0
development build, look at the test steps currently suggested, and note your
results in the table near the bottom.

---
SJG


On Wed, Mar 2, 2011 at 3:27 PM, Martin Langhoff
wrote:

> Hi folks,
>
> you're in the To list if you've been hacking on keyboard maps,
> variants and whatnot. Don't hide. I know it was you.
>
> Sergey (upstream xkeyboard-config maintainer) is helping get things
> sorted and upstream. This has been good as he's spotted quite a few
> inconsistencies and stuff, _and_ it gets us upstreamed.
>
> But olpcm is non-trivial, and he has some questions.
>
> Please join the discussion at
> https://bugs.freedesktop.org/show_bug.cgi?id=34732 -- specially from
> comment 6 onwards.
>
> cheers,
>
>
> m
> --
>  martin.langh...@gmail.com
>  mar...@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
> ___
> 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: New XO 1.5 firmware with MPPT. Please test!

[Samuel Greenfeld]

Is there any expected impact to battery health or life from using a MPPT
(maximum power point tracking) charging technique?

How does this behave when it encounters an external charger which may be
inflexible in terms of voltage or current generated?


On Thu, Apr 7, 2011 at 2:59 PM, Richard A. Smith  wrote:

> On 04/05/2011 12:47 PM, Richard A. Smith wrote:
>
> Latest version.
>
> http://dev.laptop.org/~rsmith/q3a62e.rom
>
> This one really fixes the keyboard problem.  This is what I hope to be
> the final test release.
>
> In addition to the normal does this work for you. I need one specific test.
>
> Please flash then boot and stop at openfirmware.  Then run
> 'watch-battery'. Remove external power and  allow you battery to
> discharge to 60% or more. ie (<= 60%).
>
> Then re-plug up external power and watch what the battery current does.
>  It should pretty quickly go up to around 1A or more.  If it does not
> then please connect up a serial terminal with logging enabled. ( you
> will have to power cycle or reboot to get ofw serial) Remove external
> power and then rather than 'watch-battery' run 'watch-mppt' and then
> replug up power. Let it run for perhaps a minute or so and then send me
> the serial log.
>
> Thanks
> --
> Richard A. Smith  
> One Laptop per Child
> ___
> 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 XO Graphics Optimization Technique

[Samuel Greenfeld]

How did you do that?

I haven't implemented DEC ReGIS or Tektronix 4010/405x graphics support yet.


On Sat, Apr 2, 2011 at 10:41 AM, Walter Bender wrote:

>
> I have a version of Turtle Art that is working with the new graphics
> library as well.
>
> -walter
>
>
> --
> Walter Bender
> Sugar Labs
> http://www.sugarlabs.org
>
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Possible XO Graphics Optimization Technique

[Samuel Greenfeld]

Hello all:

As many of you are aware, work is being done to improve the graphics
performance of various XO laptop platforms.

So in an attempt to improve things further, I looked into optimizing the
data Sugar sends to the video subsystem itself.

I think I have made some improvements, and put up some samples of my Sugar
interface work at http://www.greenfeld.org/1April2011/ .  Feedback is
welcome.

But while I have drastically reduced the amount of bandwidth required to
display the Sugar interface, I fear I have significantly increased the
amount of power required for optimal rendering.

---
SJG
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Re: Discovering the XOs local timezone in a bash script

[Samuel Greenfeld]

The XO image OLPC supplies defaults to UTC.   Users can select a time 
zone offset in Sugar if they want, but it is purely a numerical control 
at last check and does not allow you to choose a setting that is 
regional (like "America/New York" or "EST5EDT", which include Daylight 
Savings support).

Sugar reports only relative times in its core GUI, so I don't know how 
common it is for deployments or other users to actually change this 
setting.  Setting a time zone other than UTC with 10.1.3 and prior may 
also expose a flaw where the offset is repetitively applied every 
reboot, shifting the clock.

Perhaps proper time zone support (with the optional frame clock some 
deployments like) could be part of the 11.2.0 release if there is a good 
reason to include it.  But that's a design discussion for the 
Sugar-devel list, as I don't quite know why Sugar avoids showing actual 
times in the first place.

If we decide to include a Calendar app in 11.2.0 that might also be good 
justification for making time zone support easier to use.

---
SJG

On 3/12/2011 10:05 PM, Richard A. Smith wrote:
> I've added a new feature in my power logging processor that allows the
> plotting of power input vs time of day.  To do this I have to know the
> local timzone so I can translate the UTC datestamp back to the local time.
>
> `date` says the XO's timezone is set to UTC so I'll have to get it from
> somewhere else.
>
> Can someone give me a quick rundown of how we are managing timezones so
> I know what to look at to determine this?
>

___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Re: [Testing] [support-gang] Lost Communication in 10.1.3?

[Samuel Greenfeld]

The XO-1 will only see Ad-hoc XO-1.5 networks which currently have XOs 
connected to them.  It will not show all three Mayan icons unless there 
is an XO-1.5 or other computers creating three Ad-hoc networks, one with 
each of the desired names.


You will have to manually connect the XO-1 to an Ad-hoc network; it will 
not automatically do so.


Unless you told them otherwise, by default all the XO-1.5s likely 
decided to use Ad-hoc channel 1 if they did not see a preferred access 
point, so you should go looking on the 10.1.3 XO-1 for a filled color 
circle with a single dot in it.  If the XO-1.5s were near an access 
point they were taught about, they may have connected to that instead.  
The ad-hoc networks on the XO-1 with 10.1.3 will look like the 
filled-color (active) networks on the XO-1.5 using the XO-1 user's 
colors to indicate that someone is listening on the channel.


It may take up to 30 or 60 seconds(?) from the time that an XO-1.5 
created the Ad-hoc network to the point that an XO-1 will decide to 
rescan to see what networks are out there.  I'm hoping there are no 
restrictions on rescanning once an XO-1 decides to connect to a Mesh 
network.


Admittedly the graphic 
http://wiki.sugarlabs.org/go/File:Adhoc_network_XO-1.png (available from 
http://wiki.sugarlabs.org/go/Features/Ad_hoc_Networking) is someone 
confusing, since the XO-1 in that screenshot actually is connected {has 
parenthesis} to a network which is neither the Ad-hoc network spotted 
(on channel 11 - a dot and two lines) nor the Mesh ones.




On 2/6/2011 12:58 PM, Caryl Bigenho wrote:
OK I think I know what happened.  First a question... how will the ad 
hoc networks look on the XO-1?  They were still targets on these.  
Maybe I grabbed the wrong usb stick and put 10.1.2 on them again... 
but I don't think so.


I didn't see any parenthesis... just that the 2 XO-1s could see each 
other fine, but they couldn't see the 1.5s, even with sharing on.  I 
started the Chat on a 1.5.  Maybe it has to start on a 1.0?


Caryl

> Date: Sun, 6 Feb 2011 12:52:01 -0500
> Subject: Re: [Testing] [support-gang] Lost Communication in 10.1.3?
> From: gerald.ard...@gmail.com
> To: cbige...@hotmail.com
> CC: gerald.ard...@gmail.com; support-g...@lists.laptop.org; 
devel@lists.laptop.org; test...@lists.laptop.org; support-g...@laptop.org

>
> Caryl,
>
> Once you connect to one of the ad-hoc networks, you will see the
> familiar parentheses surrounding it. Then, in the Neighborhood View on
> the the XOs, this network should appear as a wireless device.
>
> I would start troubleshooting by going o Settings and turning the
> radio off and then on again.
>
> Good luck.
>
> Gerald
>
> On Sunday, February 6, 2011, Caryl Bigenho  wrote:
> >
> >
> >
> >
> >
> > Hi Gerald,
> >
> > That was the first thing I tried and it didn't work for me.  I'll 
try it again when I get back from TX.  How did you connect the 1.0 to 
the network?  They are still showing as access points rather than the 
Mayan numerals on the 1.0s.  Maybe I need to do the install again.

> >
> > Caryl
> >
> >> Date: Sun, 6 Feb 2011 11:39:38 -0500
> >> From: gerald.ard...@gmail.com
> >> To: support-g...@lists.laptop.org
> >> CC: devel@lists.laptop.org; test...@lists.laptop.org; 
support-g...@laptop.org

> >> Subject: Re: [Testing] [support-gang] Lost Communication in 10.1.3?
> >>
> >> Caryl,
> >>
> >> I have been able to make this work. Here's what I did:
> >> 1. Create an ad-hoc network on one of the 1.5s.
> >> 2. Connect to it on the 1.0s.
> >> 3. Open Chat and make public.
> >>
> >> Hope this helps.
> >> Gerald
> >>
> >> On Sunday, February 6, 2011, Caryl Bigenho  
wrote:

> >> >
> >> >tee's what I
> >> >
> >> >
> >> >.
> >>
> >> H
> >> > Hi...
> >> >
> >> > Prepping some XOs for our booth at SCaLE 9X Feb 26-27.  When I 
first started charging and testing I was running 10.1.2.  I tried Chat 
and found that the XO-1s could easily chat with the XO-1.5s.

> >> >
> >> > Then I updated all of them to 10.1.3, and this ability seems to 
have been lost.  While the XO-1.5s connected right away to the ad hoc 
network, the XO-1s were totally left out.  They can only see each other.

> >> >
> >> > Is this an intentional change?  Is there a way for both models 
to communicate among themselves in 10.1.3?

> >> >
> >> > Caryl
> >> >
> >> ___
> >> Testing mailing list
> >> test...@lists.laptop.org
> >> http://lists.laptop.org/listinfo/testing
> >
> >


___
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: [support-gang] [IAEP] Google Art Project

[Samuel Greenfeld]

This may not always be guaranteed to be true, but I've noticed that the 
"older Flash plugin" removed by Adobe's Flash RPM is Gnash, with the 
uninstall done via a rather crude method (move the Netscape-style plugin 
library & repackage).

The yum/rpm uninstall probably cleans a bit more, and perhaps should be 
run first to avoid the conflicting uninstall routines.


On 2/3/2011 6:56 PM, James Cameron wrote:
> On Thu, Feb 03, 2011 at 01:56:37PM -0500, Nicholas Doiron wrote:
>> If you haven't uninstalled Gnash, which can interfere with Flash, it's
>> described in the same article on the wiki, and on the last step of
>> http://wiki.laptop.org/go/User:Ndoiron/MediaGuide
> I've followed this on 11.2.0 and it works in Firefox and in Browse.
> It didn't work in Firefox until Gnash was removed.
>
> In Browse, the white flash box appears asking you to click it to get it
> started.  I'm not sure why Browse does that.
>
> Caryl, make sure you click.
>

___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

11.2.0 Test cases

[Samuel Greenfeld]

I am starting work on a set of test cases to use for the Fedora 14 x86
(XO-1.0 & 1.5) 11.2.0 build.

Currently I am drafting a list of generic test scenarios we may wish to
consider testing.  That list is at
http://wiki.laptop.org/go/Test_cases/11.2.  Feel free to make
suggestions for additional things to test.

I also will be working on revamping, updating, and adding test cases to
better test the OLPC builds.  I'm not certain how to do this within the old
Wiki markup structure though without potentially breaking records (since the
test cases are stale, and newer builds often have different expected
behaviors), so I may end up creating a new set of them in the OLPC Wiki.

---
SJG
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Re: Version numbers for XO-1/XO-1.5 vs XO-1.75 releases

[Samuel Greenfeld]

I remember Slackware jumping from version 4 to 7 because the lower 
number led people to believe it was behind what then just "Red Hat Linux".

My one concern though is if Fedora ever decided to do a point release 
like Slackware does this would lead to confusion.


On 01/19/11 08:20, Daniel Drake wrote:
> On 18 January 2011 21:27, Peter Robinson  wrote:
>>> One option we have is to call the new XO-1/XO-1.5 release 11.2.x,
>>> leaving 11.1.x free for a possible OLPC XO-1.75 software release based
>>> on F12/F13. I think thats the best option we have right now, but might
>>> create a bit of confusion as "what happened to 11.1??"
>> What about bumping the major release to 14 for the stable XOs and to
>> 12/13 for the 1.75 reflecting the Fedora release that its based upon
>> and then use the usual 14.1 14.2 etc that way there's no confusion
>> based on the underlying os ages and allows the usual point releases.
> I like this idea.
>
> Michael/Scott, I'm sure you were immersed in this conversation the
> first time around, I don't suppose you have a little time to comment
> on this discussion? Original question:
> http://lists.laptop.org/pipermail/devel/2011-January/030848.html
>
> Thanks,
> 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