The xo1 image boots into sugar (latest from git) and wifi works. I'm now
building xo4 images
On 12 May 2014 02:12, Daniel Narvaez dwnarv...@gmail.com 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
On Mon, May 12, 2014 at 11:01 AM, Daniel Narvaez dwnarv...@gmail.comwrote:
The xo1 image boots into sugar (latest from git) and wifi works. I'm now
building xo4 images
nice.
On 12 May 2014 02:12, Daniel Narvaez dwnarv...@gmail.com wrote:
A couple more images, for xo1 and xo1.5. They
Hello everyone,
I was playing around with things and unfortunately had to finally setup the
development environment again but this time I got the following error when
with the command ./osbuild build.
* Building sugar-web
Command failed: volo -nostamp -f add
Error: connect ECONNREFUSED
xo-1.5 image do not boot, and show a strange gey patterns in the screen.
Gonzalo
On Mon, May 12, 2014 at 8:01 AM, Daniel Narvaez dwnarv...@gmail.com wrote:
The xo1 image boots into sugar (latest from git) and wifi works. I'm now
building xo4 images
On 12 May 2014 02:12, Daniel Narvaez
Looks like a network error, either on your side or github. I'd make sure
your connection works and retry (maybe in a bit).
On Monday, 12 May 2014, Athar Haque findat...@gmail.com wrote:
Hello everyone,
I was playing around with things and unfortunately had to finally setup
the development
How far does it get? What are the last messages you see?
Mostly I wonder if it's the partitions issue that tch reported yesterday or
if we fail when running X.
On Monday, 12 May 2014, Gonzalo Odiard godi...@sugarlabs.org wrote:
xo-1.5 image do not boot, and show a strange gey patterns in the
I will attach a serial cable later and report.
Gonzalo
On Mon, May 12, 2014 at 8:51 AM, Daniel Narvaez dwnarv...@gmail.com wrote:
How far does it get? What are the last messages you see?
Mostly I wonder if it's the partitions issue that tch reported yesterday
or if we fail when running X.
Regarding XO 1.5 image, no more kernel panic, but as Gonzalo mentioned the
fading problem is still present.
On Mon, May 12, 2014 at 7:53 AM, Gonzalo Odiard godi...@sugarlabs.orgwrote:
I will attach a serial cable later and report.
Gonzalo
On Mon, May 12, 2014 at 8:51 AM, Daniel Narvaez
Ok, at least the partitions problem is fixed then. If Gonzalo can look at
the logs with a serial port that might tell what is going on. I susoect the
X driver but hard to say blindly :)
On 12 May 2014 14:34, Martin Abente martin.abente.lah...@gmail.com wrote:
Regarding XO 1.5 image, no more
log from xo-1.5
Looks like eth0 is not initialized and all stop there.
Probably you already know that, but xo-1 and xo-1.5 have a 8686 wireless
card, different to the 8787 in the xo-4
Gonzalo
On Mon, May 12, 2014 at 9:36 AM, Daniel Narvaez dwnarv...@gmail.com wrote:
Ok, at least the
I'm not quite convinced this is due to the not initialized eth0 (I'm not
sure what that is due too though). From the serial console are you able to
see the content of /var/log/Xorg.0.log (assuming there is one)?
On 12 May 2014 15:08, Gonzalo Odiard godi...@sugarlabs.org wrote:
log from xo-1.5
bash-4.2# cat /var/log/Xorg.0.log
[32.666]
X.Org X Server 1.14.4
Release Date: 2013-10-31
[32.666] X Protocol Version 11, Revision 0
[32.666] Build Operating System: 3.12.8-300.fc20.x86_64
[32.666] Current Operating System: Linux xo-a7-32-6d.localdomain
I haven't really looked into this yet, but I wonder about this
[32.849] [drm] failed to load kernel module chrome
[32.849] (EE) [drm] drmOpen failed.
Can you also post dmesg? I suppose it might have info about why loading the
module failed.
On 12 May 2014 16:16, Gonzalo Odiard
I suspect the Xorg ABI has changed from F-18 - F-20 so I suspect
someone with access to the appropriate driver source will need to
rebuild the rpm for the new Xorg ABI.
Peter
On Mon, May 12, 2014 at 3:16 PM, Gonzalo Odiard godi...@sugarlabs.org wrote:
bash-4.2# cat /var/log/Xorg.0.log
[
Hi,
github recently open sourced the shell they used to build the atom editor
https://github.com/atom/atom-shell
It sounds like it would be a pretty cool base for a future html5 only
sugar. Or event just mostly-html5, it seems like this could be easily
integrated with python stuff.
Also it
I rebuilt the X driver and the build succeeded with no changes. I suppose
it might need modifications to really work...
On 12 May 2014 16:25, Peter Robinson pbrobin...@gmail.com wrote:
I suspect the Xorg ABI has changed from F-18 - F-20 so I suspect
someone with access to the appropriate
This use node.js too, right?
Gonzalo
On Mon, May 12, 2014 at 11:26 AM, Daniel Narvaez dwnarv...@gmail.comwrote:
Hi,
github recently open sourced the shell they used to build the atom editor
https://github.com/atom/atom-shell
It sounds like it would be a pretty cool base for a future
Yes it's basically node.js + chrome + some custom bits to integrate the
two. It would be perfect to write an OS fully in js (dream or nightmare?
:P).
On 12 May 2014 16:33, Gonzalo Odiard godi...@sugarlabs.org wrote:
This use node.js too, right?
Gonzalo
On Mon, May 12, 2014 at 11:26 AM,
The same error persists till now.
Error: connect ECONNREFUSED
On Mon, May 12, 2014 at 7:27 PM, Daniel Narvaez dwnarv...@gmail.com wrote:
Maybe your error is different because you are behind a proxy. I'm also
having issues running volo add right now, I just get different errors. I
would retry
At some point, the ctl+alt+backspace signal to restart was dropped. This was
a very handy way
to get out of dead-ends caused by starting too many activities.
What I would like to do is have this signal show a screen similar to the
switch desktop screen but with
a set of options:
Hi,
The Ctl-Alt-Backspace thing was dropped upstream with xorg, the
graphical server.
It can be restored to its original function, by means of a
configuration on xorg.conf
(look for DontZap option).
In order to get what you want, more or less, and without any coding,
you'd need to use a
Hello,
things are looking good so far, we already have all the models booting into
sugar 0.101 with wif apparentlyi working. I would like to take a step back
and understand a bit better where we want to go with this. Some random
thoughts and questions.
* To really understand how much work is
On Mon, May 12, 2014 at 3:02 PM, Daniel Narvaez dwnarv...@gmail.com wrote:
Hello,
things are looking good so far, we already have all the models booting
into sugar 0.101 with wif apparentlyi working.
First, thanks for doing this work.
I would like to take a step back and understand a
Hi,
to be honest I haven't even evaluated alternative distributions because I
don't think we would have enough resources to do it anyway. We are making
minor changes to olpc-os-builder, rewriting it for another distribution
would be a lot of work.
On 12 May 2014 20:11, Jon Nettleton
+1
On Mon, May 12, 2014 at 6:37 PM, Daniel Narvaez dwnarv...@gmail.com wrote:
Hi,
to be honest I haven't even evaluated alternative distributions because I
don't think we would have enough resources to do it anyway. We are making
minor changes to olpc-os-builder, rewriting it for another
On 12 May 2014 21:07, Gonzalo Odiard godi...@sugarlabs.org wrote:
First, thanks for doing this work.
Thanks for helping out.
I would like to take a step back and understand a bit better where we
want to go with this. Some random thoughts and questions.
* To really understand how much
daniel wrote:
* Should we contribute the olpc-os-builder changes back to OLPC or fork it?
I don't know if OLPC will do any active development on the linux side of
things, if not maybe better to turn this into a sugarlabs thing.
...
Yes. I don't really have a strong feeling one way or
On 13 May 2014 00:43, Paul Fox p...@laptop.org wrote:
daniel wrote:
* Should we contribute the olpc-os-builder changes back to OLPC or fork
it?
I don't know if OLPC will do any active development on the linux side
of
things, if not maybe better to turn this into a sugarlabs thing.
The Zap feature to kill X server. It was disabled upstream. Cascaded
to OLPC OS in in 11.3.0. Raised as #11202 [1], as a regression, but
not resolved.
It can be easily restored [2], and some deployments have done that.
The other functions you desire can be implemented by replacing olpc-dm
On Mon, May 12, 2014 at 10:08:41AM -0300, Gonzalo Odiard wrote:
Probably you already know that, but xo-1 and xo-1.5 have a 8686
wireless card, different to the 8787 in the xo-4
Actually, XO-1 has 8388 and is soldered down card.
--
James Cameron
http://quozl.linux.org.au/
On Mon, May 12, 2014 at 08:02:22PM +0200, Daniel Narvaez wrote:
things are looking good so far, we already have all the models
booting into sugar 0.101 with wif apparentlyi working.
I agree, well done. Why is it everybody named Daniel does development
so fast? ;-)
* Should we contribute the
Downloading!
On Mon, May 12, 2014 at 8:54 PM, Daniel Narvaez dwnarv...@gmail.com wrote:
xo4 image finally built (untested yet)
http://bender.sugarlabs.org:3000/images/xo4/2/
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
On May 12, 2014, at 7:34 PM, James Cameron wrote:
On Mon, May 12, 2014 at 10:08:41AM -0300, Gonzalo Odiard wrote:
Probably you already know that, but xo-1 and xo-1.5 have a 8686
wireless card, different to the 8787 in the xo-4
Actually, XO-1 has 8388 and is soldered down card.
XO-1:
33 matches
Mail list logo
