Re: Announcing another early Android build for XO-4

2014-05-11 Thread James Cameron
On Mon, May 12, 2014 at 11:35:12AM +1200, ben wrote:
> On 05/12/2014 11:26 AM, James Cameron wrote:
> >but i thought mmcblk0 is always the device booted from, regardless of
> >whether it is internal or external.
> Not on my XO-4. It maps external to mmcblk1 if booted from external.

Thanks, yes, that's what it looks like.  I don't think it is reliable
though, as it depends on the discovery order, which is not
predictable.  See commend in olpc-sd.rules in dracut-modules-olpc.

Looking at olpc-boot-cmdline.sh in dracut-modules-olpc, we use
/dev/disk/mmc references instead of the legacy /dev/mmcblk references.

-- 
James Cameron
http://quozl.linux.org.au/
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel


Re: [Sugar-devel] XO on Fedora 20 (was Re: [GSoC] Porting To Python3)

2014-05-11 Thread Martin Abente
Downloading!


On Sun, May 11, 2014 at 8:12 PM, Daniel Narvaez  wrote:

> A couple more images, for xo1 and xo1.5. They have sugar packages built
> from latest sugar git. I have not tested them yet so they might not even
> boot, but if someone gives them a try please let me know how they works.
>
> http://146.185.144.82:3000/images/xo1/1/
> http://146.185.144.82:3000/images/xo1.5/1/
>
> The xo1.5 one also *attempts* to fix the issue reported by Martin. The
> problem is that I'm running the x86 build slave inside docker.io, which
> doesn't like xpart. So I patched olpc-os-builder to manually losetup the
> partitions, but it's sort of tricky to get right. It will work eventually :)
>
> I have arm packages for latest git almost built, so tomorrow I should be
> able to build xo1.75 and xo4 images too. The oob configurations and some
> initial bits of automated builds infra are now here
>
> https://github.com/dnarvaez/xugar
>
>
>
> On 11 May 2014 20:49, Daniel Narvaez  wrote:
>
>> This could be a change I made. I will investigate and let you know.
>>
>>
>> On 11 May 2014 20:31, Martin Abente wrote:
>>
>>> Hey Daniel,
>>>
>>> Could you check if this is correct?
>>>
>>> $md5sum 10001xx1.zd
>>> $0cc8f3f71d636c8dc4464ffb8bf1847b  10001xx1.zd
>>>
>>>
>>> Tested with 2 different XOs 1.5 and I am getting kernel panic errors
>>> very early on the boot sequence, with message:
>>>
>>> tmpfs: No value for mount option 'strictatime'
>>> mount: mounting on /newrun failed: invalid argument
>>> mount used greatest stack depth 6752 bytes left.
>>>
>>>
>>>
>>>
>>>
>>> On Sun, May 11, 2014 at 12:47 PM, Gonzalo Odiard 
>>> wrote:
>>>
 Downloading...


 On Sun, May 11, 2014 at 1:31 PM, Martin Abente <
 martin.abente.lah...@gmail.com> wrote:

> Downloading 10001xx1.zd , will let you know how it goes soon.
>
>
> On Sun, May 11, 2014 at 12:19 PM, Daniel Narvaez 
> wrote:
>
>> I made builds for xo1 and xo1.5 with the firmware change
>>
>> http://sugarlabs.org/~dnarvaez/oob/images/
>>
>> The xo1 boots into sugar but there are no activities installed (I
>> probably got something wrong in the ini). Testing on the xo1.5 one would 
>> be
>> welcome, I'm curious if firmware solves the startup freeze.
>>
>>
>> On 11 May 2014 00:24, Martin Abente 
>> wrote:
>>
>>> great!! Let me know when you have an image with this!
>>>
>>>
>>> On Sat, May 10, 2014 at 4:36 PM, Daniel Narvaez >> > wrote:
>>>
 Firmware loading works with the rebuilt systemd! I have not tested
 much but wifi works now. Next step, build images with latest sugar...


 On 10 May 2014 01:22, Daniel Narvaez  wrote:

> I built a xo4 image, which like 1.75 boots fine into sugar
>
> http://sugarlabs.org/~dnarvaez/oob/images/xo4/
>
> The main problem, as discussed, is that firmwares are not loaded.
> I'm building a systemd rpm with firmware loading enabled. If we can 
> get
> wifi working then it should be easier to play with stuff, building in 
> the
> virtual machine takes really too long.
>
>
> On 9 May 2014 14:13, Daniel Narvaez  wrote:
>
>> I built an image for 1.75
>>
>> http://sugarlabs.org/~dnarvaez/oob/images/
>>
>> I've not been able to test yet. I don't have my usual usb stick
>> with me and having troubles finding something the XO likes.
>>
>>
>> On 8 May 2014 02:04, Daniel Narvaez  wrote:
>>
>>> As an update, I have patched xorg-x11-drv-dove and built rpms
>>> for it
>>>
>>> http://shell.sugarlabs.org/~dnarvaez/oob/f20-xo1.75/
>>>
>>> Now building an image with those.
>>>
>>>
>>> On 7 May 2014 15:18, Martin Abente <
>>> martin.abente.lah...@gmail.com> wrote:
>>>
 Great!

 I will try your oob branch for 1.5, I do have XOs 1.5 for
 testing :)



 On Wed, May 7, 2014 at 9:01 AM, Daniel Narvaez <
 dwnarv...@gmail.com> wrote:

> On 7 May 2014 01:44, James Cameron  wrote:
>
>> On Tue, May 06, 2014 at 04:24:39PM +0200, Daniel Narvaez
>> wrote:
>> > [...] And with the XO stuck on Fedora 18 we might not have
>> good
>> > enough introspection to make the port compatible with it.
>>
>> If anybody would like to work on moving olpc-os-builder to
>> something
>> more recent, feel free.  It isn't something OLPC is looking
>> at right
>> now, but it would be helpful to the users.
>>
>> Not the die hard 0.98 users, of course.  ;-)
>

Re: [Sugar-devel] XO on Fedora 20 (was Re: [GSoC] Porting To Python3)

2014-05-11 Thread Daniel Narvaez
A couple more images, for xo1 and xo1.5. They have sugar packages built
from latest sugar git. I have not tested them yet so they might not even
boot, but if someone gives them a try please let me know how they works.

http://146.185.144.82:3000/images/xo1/1/
http://146.185.144.82:3000/images/xo1.5/1/

The xo1.5 one also *attempts* to fix the issue reported by Martin. The
problem is that I'm running the x86 build slave inside docker.io, which
doesn't like xpart. So I patched olpc-os-builder to manually losetup the
partitions, but it's sort of tricky to get right. It will work eventually :)

I have arm packages for latest git almost built, so tomorrow I should be
able to build xo1.75 and xo4 images too. The oob configurations and some
initial bits of automated builds infra are now here

https://github.com/dnarvaez/xugar



On 11 May 2014 20:49, Daniel Narvaez  wrote:

> This could be a change I made. I will investigate and let you know.
>
>
> On 11 May 2014 20:31, Martin Abente wrote:
>
>> Hey Daniel,
>>
>> Could you check if this is correct?
>>
>> $md5sum 10001xx1.zd
>> $0cc8f3f71d636c8dc4464ffb8bf1847b  10001xx1.zd
>>
>>
>> Tested with 2 different XOs 1.5 and I am getting kernel panic errors very
>> early on the boot sequence, with message:
>>
>> tmpfs: No value for mount option 'strictatime'
>> mount: mounting on /newrun failed: invalid argument
>> mount used greatest stack depth 6752 bytes left.
>>
>>
>>
>>
>>
>> On Sun, May 11, 2014 at 12:47 PM, Gonzalo Odiard 
>> wrote:
>>
>>> Downloading...
>>>
>>>
>>> On Sun, May 11, 2014 at 1:31 PM, Martin Abente <
>>> martin.abente.lah...@gmail.com> wrote:
>>>
 Downloading 10001xx1.zd , will let you know how it goes soon.


 On Sun, May 11, 2014 at 12:19 PM, Daniel Narvaez 
 wrote:

> I made builds for xo1 and xo1.5 with the firmware change
>
> http://sugarlabs.org/~dnarvaez/oob/images/
>
> The xo1 boots into sugar but there are no activities installed (I
> probably got something wrong in the ini). Testing on the xo1.5 one would 
> be
> welcome, I'm curious if firmware solves the startup freeze.
>
>
> On 11 May 2014 00:24, Martin Abente wrote:
>
>> great!! Let me know when you have an image with this!
>>
>>
>> On Sat, May 10, 2014 at 4:36 PM, Daniel Narvaez 
>> wrote:
>>
>>> Firmware loading works with the rebuilt systemd! I have not tested
>>> much but wifi works now. Next step, build images with latest sugar...
>>>
>>>
>>> On 10 May 2014 01:22, Daniel Narvaez  wrote:
>>>
 I built a xo4 image, which like 1.75 boots fine into sugar

 http://sugarlabs.org/~dnarvaez/oob/images/xo4/

 The main problem, as discussed, is that firmwares are not loaded.
 I'm building a systemd rpm with firmware loading enabled. If we can get
 wifi working then it should be easier to play with stuff, building in 
 the
 virtual machine takes really too long.


 On 9 May 2014 14:13, Daniel Narvaez  wrote:

> I built an image for 1.75
>
> http://sugarlabs.org/~dnarvaez/oob/images/
>
> I've not been able to test yet. I don't have my usual usb stick
> with me and having troubles finding something the XO likes.
>
>
> On 8 May 2014 02:04, Daniel Narvaez  wrote:
>
>> As an update, I have patched xorg-x11-drv-dove and built rpms for
>> it
>>
>> http://shell.sugarlabs.org/~dnarvaez/oob/f20-xo1.75/
>>
>> Now building an image with those.
>>
>>
>> On 7 May 2014 15:18, Martin Abente <
>> martin.abente.lah...@gmail.com> wrote:
>>
>>> Great!
>>>
>>> I will try your oob branch for 1.5, I do have XOs 1.5 for
>>> testing :)
>>>
>>>
>>>
>>> On Wed, May 7, 2014 at 9:01 AM, Daniel Narvaez <
>>> dwnarv...@gmail.com> wrote:
>>>
 On 7 May 2014 01:44, James Cameron  wrote:

> On Tue, May 06, 2014 at 04:24:39PM +0200, Daniel Narvaez wrote:
> > [...] And with the XO stuck on Fedora 18 we might not have
> good
> > enough introspection to make the port compatible with it.
>
> If anybody would like to work on moving olpc-os-builder to
> something
> more recent, feel free.  It isn't something OLPC is looking at
> right
> now, but it would be helpful to the users.
>
> Not the die hard 0.98 users, of course.  ;-)


 I'm giving that a try. I was able to build a Fedora 20 image
 for XO 1.5

 https://github.com/dnarvaez/olpc-os-builder

 I don't have hardware to test that though... I'm now trying to
>>

Re: Announcing another early Android build for XO-4

2014-05-11 Thread ben

On 05/12/2014 11:26 AM, James Cameron wrote:

but i thought mmcblk0 is always the device booted from, regardless of
whether it is internal or external.

Not on my XO-4. It maps external to mmcblk1 if booted from external.




On Mon, May 12, 2014 at 11:19:25AM +1200, ben wrote:

Hi Paul,

Android has a fixed fstab configure file indicate partitions:

For example in internal eMMC
/dev/block/mmcblk0p3/system
/dev/block/mmcblk0p4/cache

But if it's booted from external SD card it should be
/dev/block/mmcblk1p3/system
/dev/block/mmcblk1p4/cache

There is no logic in Android to detect which one it should use, just
hard code to mmcblk0p3
Need kernel do a mapping or Android add a logic to know which one it
booted from I guess.

How does it work in sugar?

Ben


On 05/12/2014 11:02 AM, Paul Fox wrote:

james wrote:
  > Would be nice, yes, but not immediately planned.

do we have any idea why it doesn't work?

  > Meanwhile, if you would like to test and still retain an existing
  > install, learn how to backup and restore the internal storage:
  >
  > http://wiki.laptop.org/go/Backup#XO-1.5.2C_XO-1.75_and_XO-4
  > 
http://wiki.laptop.org/go/Firmware/Storage#How_to_make_an_image_copy_of_internal_storage

neither is very helpful in lowering the bar for someone that would
like to test without (even temporarily) destroying the content
of their laptop.

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: Announcing another early Android build for XO-4

2014-05-11 Thread James Cameron
but i thought mmcblk0 is always the device booted from, regardless of
whether it is internal or external.

On Mon, May 12, 2014 at 11:19:25AM +1200, ben wrote:
> Hi Paul,
> 
> Android has a fixed fstab configure file indicate partitions:
> 
> For example in internal eMMC
> /dev/block/mmcblk0p3/system
> /dev/block/mmcblk0p4/cache
> 
> But if it's booted from external SD card it should be
> /dev/block/mmcblk1p3/system
> /dev/block/mmcblk1p4/cache
> 
> There is no logic in Android to detect which one it should use, just
> hard code to mmcblk0p3
> Need kernel do a mapping or Android add a logic to know which one it
> booted from I guess.
> 
> How does it work in sugar?
> 
> Ben
> 
> 
> On 05/12/2014 11:02 AM, Paul Fox wrote:
> >james wrote:
> >  > Would be nice, yes, but not immediately planned.
> >
> >do we have any idea why it doesn't work?
> >
> >  > Meanwhile, if you would like to test and still retain an existing
> >  > install, learn how to backup and restore the internal storage:
> >  >
> >  > http://wiki.laptop.org/go/Backup#XO-1.5.2C_XO-1.75_and_XO-4
> >  > 
> > http://wiki.laptop.org/go/Firmware/Storage#How_to_make_an_image_copy_of_internal_storage
> >
> >neither is very helpful in lowering the bar for someone that would
> >like to test without (even temporarily) destroying the content
> >of their laptop.
> >
> >paul
> >=-
> >  paul fox, p...@laptop.org
> >___
> >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


Re: Announcing another early Android build for XO-4

2014-05-11 Thread James Cameron
On Sun, May 11, 2014 at 07:02:12PM -0400, Paul Fox wrote:
> james wrote:
>  > Would be nice, yes, but not immediately planned.
> 
> do we have any idea why it doesn't work?

no clear idea, just hasn't been studied.  the first blockage was an
old olpc.fth was used in the latest build by ben, because my git repo
fu was pathetic, and it was hard coded to use int:\ for the icons of
the menu.  the menu had actually been moved into the firmware.

subsequent blockages probably have to do with identifying the
partition to mount, avoiding mounting the internal partitions, and
dealing with keeping the external partitions mounted over suspend.

-- 
James Cameron
http://quozl.linux.org.au/
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel


Re: Announcing another early Android build for XO-4

2014-05-11 Thread ben

Hi Paul,

Android has a fixed fstab configure file indicate partitions:

For example in internal eMMC
/dev/block/mmcblk0p3/system
/dev/block/mmcblk0p4/cache

But if it's booted from external SD card it should be
/dev/block/mmcblk1p3/system
/dev/block/mmcblk1p4/cache

There is no logic in Android to detect which one it should use, just 
hard code to mmcblk0p3
Need kernel do a mapping or Android add a logic to know which one it 
booted from I guess.


How does it work in sugar?

Ben


On 05/12/2014 11:02 AM, Paul Fox wrote:

james wrote:
  > Would be nice, yes, but not immediately planned.

do we have any idea why it doesn't work?

  > Meanwhile, if you would like to test and still retain an existing
  > install, learn how to backup and restore the internal storage:
  >
  > http://wiki.laptop.org/go/Backup#XO-1.5.2C_XO-1.75_and_XO-4
  > 
http://wiki.laptop.org/go/Firmware/Storage#How_to_make_an_image_copy_of_internal_storage

neither is very helpful in lowering the bar for someone that would
like to test without (even temporarily) destroying the content
of their laptop.

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: gnome applet can't initialize Clutter

2014-05-11 Thread James Cameron
I never used the applet.

What I did was install gnome-bluetooth alone, then run
blueman-manager, which gave me a complaint about PulseAudio on stderr,
which was fixed by doing something with PulseAudio, then maybe
starting the systemd bluetooth service, then it worked.

It was back in October, so I don't have a good memory of it.  I did
get good data out of the Nintendo Wii Remote Plus that I was
experimenting with, so I know I had it working.

I did have to rebuild the kernel with

CONFIG_HIDRAW=y
CONFIG_HID_WIIMOTE=m
CONFIG_HID_WIIMOTE_EXT=y

but that was purely because of the Wii.

-- 
James Cameron
http://quozl.linux.org.au/
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel


Re: Announcing another early Android build for XO-4

2014-05-11 Thread Paul Fox
james wrote:
 > Would be nice, yes, but not immediately planned.

do we have any idea why it doesn't work?

 > Meanwhile, if you would like to test and still retain an existing
 > install, learn how to backup and restore the internal storage:
 > 
 > http://wiki.laptop.org/go/Backup#XO-1.5.2C_XO-1.75_and_XO-4
 > http://wiki.laptop.org/go/Firmware/Storage#How_to_make_an_image_copy_of_internal_storage

neither is very helpful in lowering the bar for someone that would
like to test without (even temporarily) destroying the content
of their laptop.

paul
=-
 paul fox, p...@laptop.org
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel


Re: Announcing another early Android build for XO-4

2014-05-11 Thread James Cameron
Would be nice, yes, but not immediately planned.

Meanwhile, if you would like to test and still retain an existing
install, learn how to backup and restore the internal storage:

http://wiki.laptop.org/go/Backup#XO-1.5.2C_XO-1.75_and_XO-4
http://wiki.laptop.org/go/Firmware/Storage#How_to_make_an_image_copy_of_internal_storage

-- 
James Cameron
http://quozl.linux.org.au/
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel


Re: [Sugar-devel] XO on Fedora 20 (was Re: [GSoC] Porting To Python3)

2014-05-11 Thread Daniel Narvaez
This could be a change I made. I will investigate and let you know.


On 11 May 2014 20:31, Martin Abente  wrote:

> Hey Daniel,
>
> Could you check if this is correct?
>
> $md5sum 10001xx1.zd
> $0cc8f3f71d636c8dc4464ffb8bf1847b  10001xx1.zd
>
>
> Tested with 2 different XOs 1.5 and I am getting kernel panic errors very
> early on the boot sequence, with message:
>
> tmpfs: No value for mount option 'strictatime'
> mount: mounting on /newrun failed: invalid argument
> mount used greatest stack depth 6752 bytes left.
>
>
>
>
>
> On Sun, May 11, 2014 at 12:47 PM, Gonzalo Odiard wrote:
>
>> Downloading...
>>
>>
>> On Sun, May 11, 2014 at 1:31 PM, Martin Abente <
>> martin.abente.lah...@gmail.com> wrote:
>>
>>> Downloading 10001xx1.zd , will let you know how it goes soon.
>>>
>>>
>>> On Sun, May 11, 2014 at 12:19 PM, Daniel Narvaez wrote:
>>>
 I made builds for xo1 and xo1.5 with the firmware change

 http://sugarlabs.org/~dnarvaez/oob/images/

 The xo1 boots into sugar but there are no activities installed (I
 probably got something wrong in the ini). Testing on the xo1.5 one would be
 welcome, I'm curious if firmware solves the startup freeze.


 On 11 May 2014 00:24, Martin Abente wrote:

> great!! Let me know when you have an image with this!
>
>
> On Sat, May 10, 2014 at 4:36 PM, Daniel Narvaez 
> wrote:
>
>> Firmware loading works with the rebuilt systemd! I have not tested
>> much but wifi works now. Next step, build images with latest sugar...
>>
>>
>> On 10 May 2014 01:22, Daniel Narvaez  wrote:
>>
>>> I built a xo4 image, which like 1.75 boots fine into sugar
>>>
>>> http://sugarlabs.org/~dnarvaez/oob/images/xo4/
>>>
>>> The main problem, as discussed, is that firmwares are not loaded.
>>> I'm building a systemd rpm with firmware loading enabled. If we can get
>>> wifi working then it should be easier to play with stuff, building in 
>>> the
>>> virtual machine takes really too long.
>>>
>>>
>>> On 9 May 2014 14:13, Daniel Narvaez  wrote:
>>>
 I built an image for 1.75

 http://sugarlabs.org/~dnarvaez/oob/images/

 I've not been able to test yet. I don't have my usual usb stick
 with me and having troubles finding something the XO likes.


 On 8 May 2014 02:04, Daniel Narvaez  wrote:

> As an update, I have patched xorg-x11-drv-dove and built rpms for
> it
>
> http://shell.sugarlabs.org/~dnarvaez/oob/f20-xo1.75/
>
> Now building an image with those.
>
>
> On 7 May 2014 15:18, Martin Abente  > wrote:
>
>> Great!
>>
>> I will try your oob branch for 1.5, I do have XOs 1.5 for testing
>> :)
>>
>>
>>
>> On Wed, May 7, 2014 at 9:01 AM, Daniel Narvaez <
>> dwnarv...@gmail.com> wrote:
>>
>>> On 7 May 2014 01:44, James Cameron  wrote:
>>>
 On Tue, May 06, 2014 at 04:24:39PM +0200, Daniel Narvaez wrote:
 > [...] And with the XO stuck on Fedora 18 we might not have
 good
 > enough introspection to make the port compatible with it.

 If anybody would like to work on moving olpc-os-builder to
 something
 more recent, feel free.  It isn't something OLPC is looking at
 right
 now, but it would be helpful to the users.

 Not the die hard 0.98 users, of course.  ;-)
>>>
>>>
>>> I'm giving that a try. I was able to build a Fedora 20 image for
>>> XO 1.5
>>>
>>> https://github.com/dnarvaez/olpc-os-builder
>>>
>>> I don't have hardware to test that though... I'm now trying to
>>> build for 1.75 which is harder but I can actually test. I need to 
>>> rebuild
>>> the X driver but I think that will require some patching, let's see 
>>> if I
>>> can get it to work...
>>>
>>> ___
>>> Devel mailing list
>>> Devel@lists.laptop.org
>>> http://lists.laptop.org/listinfo/devel
>>>
>>>
>>
>> ___
>> Sugar-devel mailing list
>> sugar-de...@lists.sugarlabs.org
>> http://lists.sugarlabs.org/listinfo/sugar-devel
>>
>>
>
>
> --
> Daniel Narvaez
>



 --
 Daniel Narvaez

>>>
>>>
>>>
>>> --
>>> Daniel Narvaez
>>>
>>
>>
>>
>> --
>> Daniel Narvaez
>>
>
>


 --
 Daniel Narvaez

>>>
>>>
>>
>>
>> --
>> Gonzalo Odiard
>>
>> SugarLabs - Software

Re: [Sugar-devel] XO on Fedora 20 (was Re: [GSoC] Porting To Python3)

2014-05-11 Thread Martin Abente
Hey Daniel,

Could you check if this is correct?

$md5sum 10001xx1.zd
$0cc8f3f71d636c8dc4464ffb8bf1847b  10001xx1.zd


Tested with 2 different XOs 1.5 and I am getting kernel panic errors very
early on the boot sequence, with message:

tmpfs: No value for mount option 'strictatime'
mount: mounting on /newrun failed: invalid argument
mount used greatest stack depth 6752 bytes left.





On Sun, May 11, 2014 at 12:47 PM, Gonzalo Odiard wrote:

> Downloading...
>
>
> On Sun, May 11, 2014 at 1:31 PM, Martin Abente <
> martin.abente.lah...@gmail.com> wrote:
>
>> Downloading 10001xx1.zd , will let you know how it goes soon.
>>
>>
>> On Sun, May 11, 2014 at 12:19 PM, Daniel Narvaez wrote:
>>
>>> I made builds for xo1 and xo1.5 with the firmware change
>>>
>>> http://sugarlabs.org/~dnarvaez/oob/images/
>>>
>>> The xo1 boots into sugar but there are no activities installed (I
>>> probably got something wrong in the ini). Testing on the xo1.5 one would be
>>> welcome, I'm curious if firmware solves the startup freeze.
>>>
>>>
>>> On 11 May 2014 00:24, Martin Abente wrote:
>>>
 great!! Let me know when you have an image with this!


 On Sat, May 10, 2014 at 4:36 PM, Daniel Narvaez wrote:

> Firmware loading works with the rebuilt systemd! I have not tested
> much but wifi works now. Next step, build images with latest sugar...
>
>
> On 10 May 2014 01:22, Daniel Narvaez  wrote:
>
>> I built a xo4 image, which like 1.75 boots fine into sugar
>>
>> http://sugarlabs.org/~dnarvaez/oob/images/xo4/
>>
>> The main problem, as discussed, is that firmwares are not loaded. I'm
>> building a systemd rpm with firmware loading enabled. If we can get wifi
>> working then it should be easier to play with stuff, building in the
>> virtual machine takes really too long.
>>
>>
>> On 9 May 2014 14:13, Daniel Narvaez  wrote:
>>
>>> I built an image for 1.75
>>>
>>> http://sugarlabs.org/~dnarvaez/oob/images/
>>>
>>> I've not been able to test yet. I don't have my usual usb stick with
>>> me and having troubles finding something the XO likes.
>>>
>>>
>>> On 8 May 2014 02:04, Daniel Narvaez  wrote:
>>>
 As an update, I have patched xorg-x11-drv-dove and built rpms for it

 http://shell.sugarlabs.org/~dnarvaez/oob/f20-xo1.75/

 Now building an image with those.


 On 7 May 2014 15:18, Martin Abente 
 wrote:

> Great!
>
> I will try your oob branch for 1.5, I do have XOs 1.5 for testing
> :)
>
>
>
> On Wed, May 7, 2014 at 9:01 AM, Daniel Narvaez <
> dwnarv...@gmail.com> wrote:
>
>> On 7 May 2014 01:44, James Cameron  wrote:
>>
>>> On Tue, May 06, 2014 at 04:24:39PM +0200, Daniel Narvaez wrote:
>>> > [...] And with the XO stuck on Fedora 18 we might not have good
>>> > enough introspection to make the port compatible with it.
>>>
>>> If anybody would like to work on moving olpc-os-builder to
>>> something
>>> more recent, feel free.  It isn't something OLPC is looking at
>>> right
>>> now, but it would be helpful to the users.
>>>
>>> Not the die hard 0.98 users, of course.  ;-)
>>
>>
>> I'm giving that a try. I was able to build a Fedora 20 image for
>> XO 1.5
>>
>> https://github.com/dnarvaez/olpc-os-builder
>>
>> I don't have hardware to test that though... I'm now trying to
>> build for 1.75 which is harder but I can actually test. I need to 
>> rebuild
>> the X driver but I think that will require some patching, let's see 
>> if I
>> can get it to work...
>>
>> ___
>> Devel mailing list
>> Devel@lists.laptop.org
>> http://lists.laptop.org/listinfo/devel
>>
>>
>
> ___
> Sugar-devel mailing list
> sugar-de...@lists.sugarlabs.org
> http://lists.sugarlabs.org/listinfo/sugar-devel
>
>


 --
 Daniel Narvaez

>>>
>>>
>>>
>>> --
>>> Daniel Narvaez
>>>
>>
>>
>>
>> --
>> Daniel Narvaez
>>
>
>
>
> --
> Daniel Narvaez
>


>>>
>>>
>>> --
>>> Daniel Narvaez
>>>
>>
>>
>
>
> --
> Gonzalo Odiard
>
> SugarLabs - Software for children learning
>
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel


Re: [Sugar-devel] XO on Fedora 20 (was Re: [GSoC] Porting To Python3)

2014-05-11 Thread Gonzalo Odiard
Downloading...


On Sun, May 11, 2014 at 1:31 PM, Martin Abente <
martin.abente.lah...@gmail.com> wrote:

> Downloading 10001xx1.zd , will let you know how it goes soon.
>
>
> On Sun, May 11, 2014 at 12:19 PM, Daniel Narvaez wrote:
>
>> I made builds for xo1 and xo1.5 with the firmware change
>>
>> http://sugarlabs.org/~dnarvaez/oob/images/
>>
>> The xo1 boots into sugar but there are no activities installed (I
>> probably got something wrong in the ini). Testing on the xo1.5 one would be
>> welcome, I'm curious if firmware solves the startup freeze.
>>
>>
>> On 11 May 2014 00:24, Martin Abente wrote:
>>
>>> great!! Let me know when you have an image with this!
>>>
>>>
>>> On Sat, May 10, 2014 at 4:36 PM, Daniel Narvaez wrote:
>>>
 Firmware loading works with the rebuilt systemd! I have not tested much
 but wifi works now. Next step, build images with latest sugar...


 On 10 May 2014 01:22, Daniel Narvaez  wrote:

> I built a xo4 image, which like 1.75 boots fine into sugar
>
> http://sugarlabs.org/~dnarvaez/oob/images/xo4/
>
> The main problem, as discussed, is that firmwares are not loaded. I'm
> building a systemd rpm with firmware loading enabled. If we can get wifi
> working then it should be easier to play with stuff, building in the
> virtual machine takes really too long.
>
>
> On 9 May 2014 14:13, Daniel Narvaez  wrote:
>
>> I built an image for 1.75
>>
>> http://sugarlabs.org/~dnarvaez/oob/images/
>>
>> I've not been able to test yet. I don't have my usual usb stick with
>> me and having troubles finding something the XO likes.
>>
>>
>> On 8 May 2014 02:04, Daniel Narvaez  wrote:
>>
>>> As an update, I have patched xorg-x11-drv-dove and built rpms for it
>>>
>>> http://shell.sugarlabs.org/~dnarvaez/oob/f20-xo1.75/
>>>
>>> Now building an image with those.
>>>
>>>
>>> On 7 May 2014 15:18, Martin Abente 
>>> wrote:
>>>
 Great!

 I will try your oob branch for 1.5, I do have XOs 1.5 for testing :)



 On Wed, May 7, 2014 at 9:01 AM, Daniel Narvaez >>> > wrote:

> On 7 May 2014 01:44, James Cameron  wrote:
>
>> On Tue, May 06, 2014 at 04:24:39PM +0200, Daniel Narvaez wrote:
>> > [...] And with the XO stuck on Fedora 18 we might not have good
>> > enough introspection to make the port compatible with it.
>>
>> If anybody would like to work on moving olpc-os-builder to
>> something
>> more recent, feel free.  It isn't something OLPC is looking at
>> right
>> now, but it would be helpful to the users.
>>
>> Not the die hard 0.98 users, of course.  ;-)
>
>
> I'm giving that a try. I was able to build a Fedora 20 image for
> XO 1.5
>
> https://github.com/dnarvaez/olpc-os-builder
>
> I don't have hardware to test that though... I'm now trying to
> build for 1.75 which is harder but I can actually test. I need to 
> rebuild
> the X driver but I think that will require some patching, let's see 
> if I
> can get it to work...
>
> ___
> Devel mailing list
> Devel@lists.laptop.org
> http://lists.laptop.org/listinfo/devel
>
>

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


>>>
>>>
>>> --
>>> Daniel Narvaez
>>>
>>
>>
>>
>> --
>> Daniel Narvaez
>>
>
>
>
> --
> Daniel Narvaez
>



 --
 Daniel Narvaez

>>>
>>>
>>
>>
>> --
>> Daniel Narvaez
>>
>
>


-- 
Gonzalo Odiard

SugarLabs - Software for children learning
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel


Re: [Sugar-devel] XO on Fedora 20 (was Re: [GSoC] Porting To Python3)

2014-05-11 Thread Martin Abente
Downloading 10001xx1.zd , will let you know how it goes soon.


On Sun, May 11, 2014 at 12:19 PM, Daniel Narvaez wrote:

> I made builds for xo1 and xo1.5 with the firmware change
>
> http://sugarlabs.org/~dnarvaez/oob/images/
>
> The xo1 boots into sugar but there are no activities installed (I probably
> got something wrong in the ini). Testing on the xo1.5 one would be welcome,
> I'm curious if firmware solves the startup freeze.
>
>
> On 11 May 2014 00:24, Martin Abente wrote:
>
>> great!! Let me know when you have an image with this!
>>
>>
>> On Sat, May 10, 2014 at 4:36 PM, Daniel Narvaez wrote:
>>
>>> Firmware loading works with the rebuilt systemd! I have not tested much
>>> but wifi works now. Next step, build images with latest sugar...
>>>
>>>
>>> On 10 May 2014 01:22, Daniel Narvaez  wrote:
>>>
 I built a xo4 image, which like 1.75 boots fine into sugar

 http://sugarlabs.org/~dnarvaez/oob/images/xo4/

 The main problem, as discussed, is that firmwares are not loaded. I'm
 building a systemd rpm with firmware loading enabled. If we can get wifi
 working then it should be easier to play with stuff, building in the
 virtual machine takes really too long.


 On 9 May 2014 14:13, Daniel Narvaez  wrote:

> I built an image for 1.75
>
> http://sugarlabs.org/~dnarvaez/oob/images/
>
> I've not been able to test yet. I don't have my usual usb stick with
> me and having troubles finding something the XO likes.
>
>
> On 8 May 2014 02:04, Daniel Narvaez  wrote:
>
>> As an update, I have patched xorg-x11-drv-dove and built rpms for it
>>
>> http://shell.sugarlabs.org/~dnarvaez/oob/f20-xo1.75/
>>
>> Now building an image with those.
>>
>>
>> On 7 May 2014 15:18, Martin Abente wrote:
>>
>>> Great!
>>>
>>> I will try your oob branch for 1.5, I do have XOs 1.5 for testing :)
>>>
>>>
>>>
>>> On Wed, May 7, 2014 at 9:01 AM, Daniel Narvaez 
>>> wrote:
>>>
 On 7 May 2014 01:44, James Cameron  wrote:

> On Tue, May 06, 2014 at 04:24:39PM +0200, Daniel Narvaez wrote:
> > [...] And with the XO stuck on Fedora 18 we might not have good
> > enough introspection to make the port compatible with it.
>
> If anybody would like to work on moving olpc-os-builder to
> something
> more recent, feel free.  It isn't something OLPC is looking at
> right
> now, but it would be helpful to the users.
>
> Not the die hard 0.98 users, of course.  ;-)


 I'm giving that a try. I was able to build a Fedora 20 image for XO
 1.5

 https://github.com/dnarvaez/olpc-os-builder

 I don't have hardware to test that though... I'm now trying to
 build for 1.75 which is harder but I can actually test. I need to 
 rebuild
 the X driver but I think that will require some patching, let's see if 
 I
 can get it to work...

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


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



 --
 Daniel Narvaez

>>>
>>>
>>>
>>> --
>>> Daniel Narvaez
>>>
>>
>>
>
>
> --
> Daniel Narvaez
>
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel


Re: [Sugar-devel] XO on Fedora 20 (was Re: [GSoC] Porting To Python3)

2014-05-11 Thread Daniel Narvaez
I made builds for xo1 and xo1.5 with the firmware change

http://sugarlabs.org/~dnarvaez/oob/images/

The xo1 boots into sugar but there are no activities installed (I probably
got something wrong in the ini). Testing on the xo1.5 one would be welcome,
I'm curious if firmware solves the startup freeze.


On 11 May 2014 00:24, Martin Abente  wrote:

> great!! Let me know when you have an image with this!
>
>
> On Sat, May 10, 2014 at 4:36 PM, Daniel Narvaez wrote:
>
>> Firmware loading works with the rebuilt systemd! I have not tested much
>> but wifi works now. Next step, build images with latest sugar...
>>
>>
>> On 10 May 2014 01:22, Daniel Narvaez  wrote:
>>
>>> I built a xo4 image, which like 1.75 boots fine into sugar
>>>
>>> http://sugarlabs.org/~dnarvaez/oob/images/xo4/
>>>
>>> The main problem, as discussed, is that firmwares are not loaded. I'm
>>> building a systemd rpm with firmware loading enabled. If we can get wifi
>>> working then it should be easier to play with stuff, building in the
>>> virtual machine takes really too long.
>>>
>>>
>>> On 9 May 2014 14:13, Daniel Narvaez  wrote:
>>>
 I built an image for 1.75

 http://sugarlabs.org/~dnarvaez/oob/images/

 I've not been able to test yet. I don't have my usual usb stick with me
 and having troubles finding something the XO likes.


 On 8 May 2014 02:04, Daniel Narvaez  wrote:

> As an update, I have patched xorg-x11-drv-dove and built rpms for it
>
> http://shell.sugarlabs.org/~dnarvaez/oob/f20-xo1.75/
>
> Now building an image with those.
>
>
> On 7 May 2014 15:18, Martin Abente wrote:
>
>> Great!
>>
>> I will try your oob branch for 1.5, I do have XOs 1.5 for testing :)
>>
>>
>>
>> On Wed, May 7, 2014 at 9:01 AM, Daniel Narvaez 
>> wrote:
>>
>>> On 7 May 2014 01:44, James Cameron  wrote:
>>>
 On Tue, May 06, 2014 at 04:24:39PM +0200, Daniel Narvaez wrote:
 > [...] And with the XO stuck on Fedora 18 we might not have good
 > enough introspection to make the port compatible with it.

 If anybody would like to work on moving olpc-os-builder to something
 more recent, feel free.  It isn't something OLPC is looking at right
 now, but it would be helpful to the users.

 Not the die hard 0.98 users, of course.  ;-)
>>>
>>>
>>> I'm giving that a try. I was able to build a Fedora 20 image for XO
>>> 1.5
>>>
>>> https://github.com/dnarvaez/olpc-os-builder
>>>
>>> I don't have hardware to test that though... I'm now trying to build
>>> for 1.75 which is harder but I can actually test. I need to rebuild the 
>>> X
>>> driver but I think that will require some patching, let's see if I can 
>>> get
>>> it to work...
>>>
>>> ___
>>> Devel mailing list
>>> Devel@lists.laptop.org
>>> http://lists.laptop.org/listinfo/devel
>>>
>>>
>>
>> ___
>> Sugar-devel mailing list
>> sugar-de...@lists.sugarlabs.org
>> http://lists.sugarlabs.org/listinfo/sugar-devel
>>
>>
>
>
> --
> Daniel Narvaez
>



 --
 Daniel Narvaez

>>>
>>>
>>>
>>> --
>>> Daniel Narvaez
>>>
>>
>>
>>
>> --
>> Daniel Narvaez
>>
>
>


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