On 09/01/2010 07:22 AM, Daniel Drake wrote:
Hi,
Hi Daniel,
first of all - thanks for your excellent work!
After seeing the community help significantly with F11-on-XO
development, I'm wondering if we can do something similar for a future
release. So, I've taken the first few steps in
The XO-1.5 build does not boot for me, I get the following after
flashing the image:
Boot device: /wlan Argumenst:
Scan for: OLPCOFW not found
Scan for: school-mesh-0 not found
Scan for: school-mesh-1 not found
Scan for: school-mesh-2 not found
buf...@ff83b080:0:
Can't open boot device
On 09/11/2010 04:20 PM, Jon Nettleton wrote:
The XO-1.5 build does not boot for me, I get the following after
flashing the image:
Boot device: /wlan Argumenst:
Scan for: OLPCOFW not found
Scan for: school-mesh-0 not found
Scan for: school-mesh-1 not found
Scan for: school-mesh-2 not found
On 09/02/2010 07:43 PM, Mikus Grinbergs wrote:
In Terminal, cursor movement keys don't work. [I also saw interference
to Terminal (white background) from dmesg? lines (black background),
after each boot -- but these would go away if I just restarted Sugar.]
This could be X using the xfree86
Chat fails because no attribute _pservice.
This has been fixed in git:
http://git.sugarlabs.org/projects/chat/repos/mainline/commits/997ca380edbc59bbae1da9950369d3f50ffa6991
With that change applied on an XO-1 system to the Chat-66 on os1, I was
able to collaborate with an XO-1 system
On Sat, 2010-09-11 at 16:47 -0500, Mikus Grinbergs wrote:
With that change applied on an XO-1 system to the Chat-66 on os1, I was
able to collaborate with an XO-1 system running Chat-66 on os604dx, plus
an XO-1 system running Chat-65 on os856, plus an XO-1 system running
Chat-48 on build 802
Out of curiosity... what's build os604dx?
I meant os406dx. I'm getting frequent senior moments - and more and
more often I don't spot that what I've actually typed is not what I
should have typed.
mikus
___
Devel mailing list
Devel@lists.laptop.org
On Sun, Sep 5, 2010 at 10:57 AM, Bernie Innocenti ber...@codewiz.org wrote:
El Sun, 05-09-2010 a las 00:53 +0100, pbrobin...@gmail.com escribió:
Well I am for SoaS related things which while isn't XO hardware
related it does affect everything further up the stack does that
not count :-(
El Mon, 06-09-2010 a las 11:49 +0100, pbrobin...@gmail.com escribió:
Done, but I'm afraid I had to give it negative karma:
Looking at the upstream GIT of evince it looks like this is another of
the apis that have been deprecated upstream and Read needs to be
updated to fix the issue
On Mon, Sep 6, 2010 at 10:46 PM, Bernie Innocenti ber...@codewiz.org wrote:
El Mon, 06-09-2010 a las 11:49 +0100, pbrobin...@gmail.com escribió:
Done, but I'm afraid I had to give it negative karma:
Looking at the upstream GIT of evince it looks like this is another of
the apis that have
On 6 September 2010 15:59, pbrobin...@gmail.com pbrobin...@gmail.com wrote:
The problem isn't evince or gnome-python2 but that Read needs to be
updated again for the new upstream evince api changes (again).
You're right in that Read changes are needed, but there is already a
git tree floating
El Mon, 06-09-2010 a las 22:59 +0100, pbrobin...@gmail.com escribió:
I don't maintain that package. I also don't maintain Read. The
gnome-python2 package I did update was just re-enabling the upstream.
In that regard i did test the gnome-python2 package but but not
against Read as where I was
El Sun, 05-09-2010 a las 00:53 +0100, pbrobin...@gmail.com escribió:
Well I am for SoaS related things which while isn't XO hardware
related it does affect everything further up the stack does that
not count :-(
Such parallel efforts are indeed mutually beneficial.
Dextrose also enjoyed
For now, please don't file bugs unless you include patches.
I can understand not wanting bug reports against items which OLPC/Sugar
are still in the process of changing. But why defer reporting problems
which might not be addressed unless there was a report ?
For instance, Read-87 fails to
On Sat, Sep 4, 2010 at 4:24 AM, Mikus Grinbergs mi...@bga.com wrote:
For now, please don't file bugs unless you include patches.
I can understand not wanting bug reports against items which OLPC/Sugar
are still in the process of changing. But why defer reporting problems
which might not be
But why defer reporting problems
which might not be addressed unless there was a report ?
Just to take a stab at answer Because Daniel is tired.
Are other developers really so tied up that THEY can't look at bug
reports ? Why would Daniel need to be involved when (for instance) an
On 4 September 2010 03:24, Mikus Grinbergs mi...@bga.com wrote:
For now, please don't file bugs unless you include patches.
I can understand not wanting bug reports against items which OLPC/Sugar
are still in the process of changing. But why defer reporting problems
which might not be
Hi Mikus,
On 4 Sep 2010, at 10:24, Mikus Grinbergs mi...@bga.com wrote:
For instance, Read-87 fails to launch on XO-1 os1 (F14) when it tries to
'import evince'. Though the necessary gnome-python2-evince package was
not included in the os1 build, when I manually install that package from
For instance, Read-87 fails to launch on XO-1 os1 (F14) when it tries to
'import evince'. Though the necessary gnome-python2-evince package was
not included in the os1 build, when I manually install that package from
the yum Fedora-14 repositories, the import statement still fails --
On Sat, Sep 4, 2010 at 10:24 AM, Mikus Grinbergs mi...@bga.com wrote:
For now, please don't file bugs unless you include patches.
I can understand not wanting bug reports against items which OLPC/Sugar
are still in the process of changing. But why defer reporting problems
which might not be
On Sat, Sep 4, 2010 at 3:56 PM, Daniel Drake d...@laptop.org wrote:
On 4 September 2010 03:24, Mikus Grinbergs mi...@bga.com wrote:
For now, please don't file bugs unless you include patches.
I can understand not wanting bug reports against items which OLPC/Sugar
are still in the process of
El Wed, 01-09-2010 a las 07:57 -0500, Mikus Grinbergs escribió:
the XO-1.5 camera doesn't work, there are some funky graphics bugs on
XO-1, no power management, DCON doesn't work right on either laptop,
desktop switching lands you at a blank screen.
I recommend rebasing on the geode
El Wed, 01-09-2010 a las 05:03 -0500, Mikus Grinbergs escribió:
In Terminal, cursor movement keys don't work. [I also saw interference
to Terminal (white background) from dmesg? lines (black background),
after each boot -- but these would go away if I just restarted Sugar.]
This could be X
In Terminal, cursor movement keys don't work. [I also saw interference
to Terminal (white background) from dmesg? lines (black background),
after each boot -- but these would go away if I just restarted Sugar.]
This could be X using the xfree86 keycodes instead of the evdev ones.
What does
Disclaimer: I am not asking for help; I am just sharing my experience.
I noticed - perhaps because of the Sugar 0.90 'Remove_Presence_Service'
feature - THREE separate icons in F14 Neighborhood for one-and-the-same
XO-1 system (which runs os852). Admittedly, that system can be
simultaneously
El Thu, 02-09-2010 a las 01:07 +0200, Bernie Innocenti escribió:
rpm -Uvh
http://download.sugarlabs.org/dextrose/testing/dxo2/rpms/i386/os/xorg-x11-drv-geode-2.11.9-1.fc14.i586.rpm
The .fc14 is my mistake, this package is actually built for Fedora 11.
--
// Bernie Innocenti -
On Thu, Sep 2, 2010 at 4:26 PM, Bernie Innocenti ber...@codewiz.org wrote:
El Thu, 02-09-2010 a las 01:07 +0200, Bernie Innocenti escribió:
rpm -Uvh
http://download.sugarlabs.org/dextrose/testing/dxo2/rpms/i386/os/xorg-x11-drv-geode-2.11.9-1.fc14.i586.rpm
The .fc14 is my mistake, this
Hey Daniel,
Yippee! I suspect the sugar starting issues is the same one we're
seeing in SoaS for F-14. I'm very busy until Sunday but i hope to have
at least some time to be able to look at that problem and help you out
where possibly as no doubt both SoaS and the builds for the XO will
share a
This is awesome news, kudos to Daniel.
On Wed, Sep 1, 2010 at 08:49, pbrobin...@gmail.com pbrobin...@gmail.com wrote:
Hey Daniel,
Yippee! I suspect the sugar starting issues is the same one we're
seeing in SoaS for F-14.
Hmm, I had some trouble on mainstream F-14 booting both Sugar and
GNOME
Booted ok on XO-1. At its current level, this system is already usable.
[Was even able to apply my customizations, except for doing editing.]
In Terminal, cursor movement keys don't work. [I also saw interference
to Terminal (white background) from dmesg? lines (black background),
after each
El Tue, 31-08-2010 a las 23:22 -0600, Daniel Drake escribió:
Things are in such an early stage that I'm labelling this as a
developers-only release. To name a few: Sugar crashes all the time,
the XO-1.5 camera doesn't work, there are some funky graphics bugs on
XO-1, no power management, DCON
the XO-1.5 camera doesn't work, there are some funky graphics bugs on
XO-1, no power management, DCON doesn't work right on either laptop,
desktop switching lands you at a blank screen.
I recommend rebasing on the geode driver 2.11.9, which was just released
by upstream. I've been testing
On 1 September 2010 00:49, pbrobin...@gmail.com pbrobin...@gmail.com wrote:
With the kernel nearing a recent release is there any plans to get a
chunk of the kernel patches upstream to ease on going maintenance?
I cleaned up the history a lot, which is the first big step in doing this.
It's a
--- On Wed, 9/1/10, Mikus Grinbergs mi...@bga.com wrote:
I recommend rebasing on the geode driver 2.11.9, which
was just released
by upstream. I've been testing it in Dextrose for
about 3 weeks: it
fixes all the known rendering bugs and has no
regressions.
The XO-1 os1 build
On 1 September 2010 10:14, Yioryos Asprobounitis mavrot...@yahoo.com wrote:
This driver should be ported to F11/10.1.2 ASAP. Is day and night compared to
2.11.8 when I run it in puppy. The XO-1 is like a new machine.
pls do _not_ wait for 10.1.3
That's impossible. 10.1.2 has been released.
--- On Wed, 9/1/10, Daniel Drake d...@laptop.org wrote:
From: Daniel Drake d...@laptop.org
Subject: Re: Initial F14 developers-only release for XO and XO-1.5
To: Yioryos Asprobounitis mavrot...@yahoo.com
Cc: Bernie Innocenti ber...@codewiz.org, mi...@bga.com, OLPC Devel
devel
On Wed, Sep 1, 2010 at 2:30 PM, Yioryos Asprobounitis
mavrot...@yahoo.com wrote:
This driver should be ported to F11/10.1.2 ASAP. Is
day and night compared to 2.11.8 when I run it in puppy. The
XO-1 is like a new machine.
pls do _not_ wait for 10.1.3
That's impossible. 10.1.2 has been
--- On Wed, 9/1/10, Martin Langhoff martin.langh...@gmail.com wrote:
From: Martin Langhoff martin.langh...@gmail.com
Subject: Re: Initial F14 developers-only release for XO and XO-1.5
To: Yioryos Asprobounitis mavrot...@yahoo.com
Cc: Daniel Drake d...@laptop.org, OLPC Devel devel
El Wed, 01-09-2010 a las 15:55 -0300, Martin Langhoff escribió:
can you spin a F11 RPM of 2.11.9? If it's much improved, and a good
testing shows it has no regressions, it's a candidate for 10.1.3.
Enjoy:
rpm -Uvh
Hi,
After seeing the community help significantly with F11-on-XO
development, I'm wondering if we can do something similar for a future
release. So, I've taken the first few steps in getting OLPC's
technologies rebased on Fedora 14 and Linux v2.6.35.
The result has lots of problems, but I figure
40 matches
Mail list logo
