[Techteam] 12.1.0 devel build 1 released, for XO-1.5 and XO-1

Peter Robinson pbrobinson at gmail.com
Wed Nov 9 10:01:49 EST 2011


On Wed, Nov 9, 2011 at 2:33 PM, Kevin Gordon <kgordon420 at gmail.com> wrote:
>
>
> ---------- Forwarded message ----------
> From: Kevin Gordon <kgordon420 at gmail.com>
> Date: Wed, Nov 9, 2011 at 5:33 AM
> Subject: Re: Re: [Techteam] 12.1.0 devel build 1 released, for XO-1.5 and
> XO-1
> To: forster at ozonline.com.au
>
>
>
>
> On Tue, Nov 8, 2011 at 8:35 PM, <forster at ozonline.com.au> wrote:
>>
>> Some XO-1's can't handle ubifs
>> http://dev.laptop.org/ticket/11094
>> Is there any chance this is related?
>
> It would appear to be unrelated.  All three of these XO-1's  can run all
> previous ubifs developer builds.  They just cannot boot the 12.1.0  os/1.

I believe this was a problem with the build. I'll review and ensure
the next one will work

> Kidding aside on my quasi technical comment, on the previous ubifs, the blue
> squares on the re-flash install animation started on line 1, and continued
> for almost an entire row,  On this one, the squares now start mid-row 2 and
> are less than a quarter of a row long.  Perhaps in an effort to optimize the
> ubifs file system and reduce the footprint of the install, some important
> component necessary to boot has been omitted?

No, I think we actually got the wrong kernel. There's also some boot
issues with the 3.2 pre kernel in general that makes it look like the
kernel actually crashed before it got very far at all.

Basically wait until I build and announce os2. The build is primarily
aimed at core sugar developers at the moment to allow them to build
and test the latest gtk3 version of sugar.

Peter

>
> KG
>
>>
>> Tony
>>
>> >
>> > No joy on the XO-1 install.  After the update-nand,  the machine only
>> > boots
>> > to the OFW  OK prompt.  Tried again with Q2E47 (the one that ships with
>> > the
>> > build), Q2E48, and Q2F05.  Tried on multiple XO-1's, CSN7, SHC7, SHF8
>> > assemblies, same symptoms.
>> >
>> > Doing a check-mark boot gives "Can't open boot device" message.  Tried
>> > another download, another USB key, same symptoms.
>> >
>> > Now here's where my incredibly detailed technical analytical skills come
>> > to the fore: There seem to be a lot less of those little blue squares
>> > that
>> > come up during the install process, and they seem to come up in a
>> > different
>> > spot than they used to, compared to the previous os# ubifs developer
>> > builds.  :-)
>> >
>> > Cheers.
>> >
>
>



More information about the Devel mailing list