12:05 a.m.
Hi,
I just built 2 images of F11-for-XO1 on OLPC infrastructure according
to my own instructions.
http://wiki.laptop.org/go/F11_for_XO-1
The first one is based on the backport that I built and tested before
(a few weeks ago), so it will probably work:
http://dev.laptop.org/~dsd/f11-xo1/os1
and the second one is updated with all of the recent changes that have
been happening in XO-1.5 software development, bringing the 2 trees in
sync at the present time
http://dev.laptop.org/~dsd/f11-xo1/os2
Neither have been tested since the internet connection here in Nepal
is very slow - I will download them over the weekend.
It would be great if anyone is interested in testing during that time
though. I would suggest starting with os2 and falling back on os1 if
it doesn't work.
I'm still looking for people to take on the role of making these
builds on a regular basis - for me, these builds are just a one-off
for now.
The usual cautions apply: this is development code, there will be
bugs. Installation instructions: use copy-nand to install osX.img with
osX.crc.
Daniel
7:37 a.m.
Tested os2 on XO-1 C2.
0. the boot animation seen with 802 was missing,
1. font size changed on console during boot, but it went back to normal
before X started,
2. X and Sugar started fine,
3. the Sugar Neighbourhood view showed only my access point, not the
usual three mesh icons,
4. associating with my access point worked fine,
5. starting activities worked; Moon, Maze, Terminal, Speak (audio
output worked), Measure (audio input worked), IRC, Browse (googling
worked), TamTamMini, and Write.
6. Record only offered Audio input, no camera input,
7. volume control keys worked okay,
8. brightness control keys did nothing,
9. power button did not suspend,
10. screen rotate button caused screen to go black. That's puzzling, I'll
try to reproduce. Yep, the screen rotate button causes the screen to go
black (unlit, no image), and nothing but a power cycle seems to fix it.
Rebooting ... automatically reassociated with access point, other XOs
seen in Neighbourhood view.
Hope this helps.
--
James Cameron
http://quozl.linux.org.au/
12:31 p.m.
2009/7/24 James Cameron <quozl(a)laptop.org>:
Tested os2 on XO-1 C2.
Thanks James! All of those except for #0 were as I would expect. I
should have os2 downloaded by monday, and hopefully I'll have some
spare time to investigate that one at least.
1. font size changed on console during boot, but it went back to
normal
before X started,
What do you mean by "normal"? I assume it went big-to-small-to-big --
to be expected. On all subsequent boots it will be big.
3. the Sugar Neighbourhood view showed only my access point, not
the
usual three mesh icons,
Mesh support is not yet present in the newest NetworkManager although
we've made a lot of progress.
6. Record only offered Audio input, no camera input,
Known (but larlgely uninvestigated) kernel bug for XO-1.
8. brightness control keys did nothing,
9. power button did not suspend,
We're still pondering the implementation of power management, even on
XO-1.5. Hence we aren't expecting this to work just yet.
10. screen rotate button caused screen to go black. That's
puzzling, I'll
try to reproduce. Yep, the screen rotate button causes the screen to go
black (unlit, no image), and nothing but a power cycle seems to fix it.
Known X11 geode driver bug.
Hope this helps.
Very much so!
Cheers
Daniel
5:27 p.m.
On Fri, Jul 24, 2009 at 11:16:45PM +0545, Daniel Drake wrote:
2009/7/24 James Cameron <quozl(a)laptop.org>:
> 1. ?font size changed on console during boot, but it went back to normal
> before X started,
What do you mean by "normal"? I assume it went big-to-small-to-big --
to be expected. On all subsequent boots it will be big.
Yes, it went small for a time, on subsequent boots it remained a single
size.
By the way, manual brightness changes via
/sys/devices/platform/dcon/backlight/dcon-bl/brightness worked fine.
I don't see ohm running, I guess that's why.
--
James Cameron
http://quozl.linux.org.au/
8:52 p.m.
On Fri, Jul 24, 2009 at 11:16:45PM +0545, Daniel Drake wrote:
2009/7/24 James Cameron <quozl(a)laptop.org>:
> Tested os2 on XO-1 C2.
> 10. screen rotate button caused screen to go black. ?That's puzzling, I'll
> try to reproduce. ?Yep, the screen rotate button causes the screen to go
> black (unlit, no image), and nothing but a power cycle seems to fix it.
Known X11 geode driver bug.
Do you happen to know where it is known?
Someone else has logged it as #9590 on OLPC Trac.
--
James Cameron
http://quozl.linux.org.au/
10:24 a.m.
Hi,
I just built 2 images of F11-for-XO1 on OLPC infrastructure according
to my own instructions.
http://wiki.laptop.org/go/F11_for_XO-1
The first one is based on the backport that I built and tested before
(a few weeks ago), so it will probably work:
http://dev.laptop.org/~dsd/f11-xo1/os1
and the second one is updated with all of the recent changes that have
been happening in XO-1.5 software development, bringing the 2 trees in
sync at the present time
http://dev.laptop.org/~dsd/f11-xo1/os2
Neither have been tested since the internet connection here in Nepal
is very slow - I will download them over the weekend.
It would be great if anyone is interested in testing during that time
though. I would suggest starting with os2 and falling back on os1 if
it doesn't work.
I'm still looking for people to take on the role of making these
builds on a regular basis - for me, these builds are just a one-off
for now.
The usual cautions apply: this is development code, there will be
bugs. Installation instructions: use copy-nand to install osX.img with
osX.crc.
Daniel
_______________________________________________
Fedora-olpc-list mailing list
Fedora-olpc-list(a)redhat.com
https://www.redhat.com/mailman/listinfo/fedora-olpc-list
Install went just fine.
Have an issue doing Activity updates in Sugar. Looks like the system
completes the update, however it then comes back and lists the same Activity
as still needing to be updated.
I know that with the increased memory/cpu on the XO-1..5 running Firefox is
trivial, however with the limited memory of the XO-1, Midori may be a better
option.
When using Gnome having issues with screen brightness.
That's all for now but will keep testing.
Steven M. Parrish
-----------------------------------------------------------------------------------------
gpg fingerprint: 4B6C 8357 059E B7ED 8095 0FD6 1F4B EDA0 A9A6 13C0
http://tuxbrewr.fedorapeople.org/
irc.freenode.net: SMParrish @ #fedora-kde, #fedora-devel, #fedora-olpc
11:36 a.m.
Hi all,
We (OLPC folks, me) are still trying to find a spot to host the build
machine for this
so that we can do continuous or daily automated builds for testing.
I know it's jumping ahead a bit, but is this (for xo1 or 1.5) going to
be updatable with yum?
Leaving aside the utility of yum updates for XO in general ... for
testing these
builds it will be much more possible for testers to pull some updated
rpms
every day or week than pull 300MiB images and overwrite our device
memory
every day/week. Especially for the wonderful people in distant lands
with slow and
unreliable lines.
If this was already FAQ'd I do apologise.
Thanks,
adric
On Jul 25, 2009, at 11:24 AM, Steven M. Parrish wrote:
> Hi,
>
> I just built 2 images of F11-for-XO1 on OLPC infrastructure according
> to my own instructions.
> http://wiki.laptop.org/go/F11_for_XO-1
>
> The first one is based on the backport that I built and tested before
> (a few weeks ago), so it will probably work:
> http://dev.laptop.org/~dsd/f11-xo1/os1
>
> and the second one is updated with all of the recent changes that
> have
> been happening in XO-1.5 software development, bringing the 2 trees
> in
> sync at the present time
> http://dev.laptop.org/~dsd/f11-xo1/os2
>
> Neither have been tested since the internet connection here in Nepal
> is very slow - I will download them over the weekend.
> It would be great if anyone is interested in testing during that time
> though. I would suggest starting with os2 and falling back on os1 if
> it doesn't work.
>
> I'm still looking for people to take on the role of making these
> builds on a regular basis - for me, these builds are just a one-off
> for now.
>
> The usual cautions apply: this is development code, there will be
> bugs. Installation instructions: use copy-nand to install osX.img
> with
> osX.crc.
>
> Daniel
>
> _______________________________________________
> Fedora-olpc-list mailing list
> Fedora-olpc-list(a)redhat.com
> https://www.redhat.com/mailman/listinfo/fedora-olpc-list
Install went just fine.
Have an issue doing Activity updates in Sugar. Looks like the system
completes the update, however it then comes back and lists the same
Activity
as still needing to be updated.
I know that with the increased memory/cpu on the XO-1..5 running
Firefox is
trivial, however with the limited memory of the XO-1, Midori may be
a better
option.
When using Gnome having issues with screen brightness.
That's all for now but will keep testing.
Steven M. Parrish
-----------------------------------------------------------------------------------------
gpg fingerprint: 4B6C 8357 059E B7ED 8095 0FD6 1F4B EDA0 A9A6 13C0
http://tuxbrewr.fedorapeople.org/
irc.freenode.net: SMParrish @ #fedora-kde, #fedora-devel, #fedora-olpc
_______________________________________________
Fedora-olpc-list mailing list
Fedora-olpc-list(a)redhat.com
https://www.redhat.com/mailman/listinfo/fedora-olpc-list
Adric Net
adric(a)adric.net
11:42 a.m.
2009/7/25 Adric Net <adric(a)adric.net>:
We (OLPC folks, me) are still trying to find a spot to host the
build
machine for this
so that we can do continuous or daily automated builds for testing.
I know it's jumping ahead a bit, but is this (for xo1 or 1.5) going to be
updatable with yum?
You can use yum to update packages from Fedora, as has always been
true with OLPC releases.
Leaving aside the utility of yum updates for XO in general ... for
testing
these
builds it will be much more possible for testers to pull some updated rpms
every day or week than pull 300MiB images and overwrite our device memory
every day/week. Especially for the wonderful people in distant lands with
slow and
unreliable lines.
The images come with olpc-update and the initramfs is ready to boot
our special "versioned layout" filesystem (like 8.2 and previous).
However the code to generate the images as the versioned layout is
currently disabled because it exposed a bug in OFWs ext2 code. For
XO-1 this should be no problem. Perhaps one of the first tasks of our
new buildmasters could be to enable and test this. Then the only
missing step is to generate output accordingly so that people can run
olpc-update to receive updates.
In summary, this is not changing from the way that OLPC has previously
done things, but we're a couple of small steps away from having the
update system fully functional.
Daniel
8:35 a.m.
daniel wrote:
Hi,
I just built 2 images of F11-for-XO1 on OLPC infrastructure according
to my own instructions.
http://wiki.laptop.org/go/F11_for_XO-1
The first one is based on the backport that I built and tested before
(a few weeks ago), so it will probably work:
http://dev.laptop.org/~dsd/f11-xo1/os1
and the second one is updated with all of the recent changes that have
been happening in XO-1.5 software development, bringing the 2 trees in
sync at the present time
http://dev.laptop.org/~dsd/f11-xo1/os2
could someone who is running either, or both, of these images,
test the functionality of rtcwake? i've been given some logs of
powerd malfunctioning, and it seems that rtcwake successfully
suspends the laptop, but it never wakes up -- or, rather, it wakes
up for other reasons, but not due the timeout.
specifically, try:
time rtcwake -m mem -a -s 10
does the system wake up reliably? the output from the 'time'
command will probably be stretched a bit -- perhaps by 2 seconds
or a little less. but it should be fairly reproducible.
paul
=---------------------
paul fox, pgf(a)laptop.org
10:27 a.m.
--- On Wed, 7/29/09, Paul Fox <pgf(a)laptop.org> wrote:
From: Paul Fox <pgf(a)laptop.org>
Subject: Re: new F11-for-XO1 images available for testing
To: "fedora-olpc-list" <fedora-olpc-list(a)redhat.com>
Date: Wednesday, July 29, 2009, 9:35 AM
daniel wrote:
> Hi,
>
> I just built 2 images of F11-for-XO1 on OLPC
infrastructure according
> to my own instructions.
> http://wiki.laptop.org/go/F11_for_XO-1
>
> The first one is based on the backport that I built
and tested before
> (a few weeks ago), so it will probably work:
> http://dev.laptop.org/~dsd/f11-xo1/os1
>
> and the second one is updated with all of the recent
changes that have
> been happening in XO-1.5 software development,
bringing the 2 trees in
> sync at the present time
> http://dev.laptop.org/~dsd/f11-xo1/os2
could someone who is running either, or both, of these
images,
test the functionality of rtcwake? i've been given
some logs of
powerd malfunctioning, and it seems that rtcwake
successfully
suspends the laptop, but it never wakes up -- or, rather,
it wakes
up for other reasons, but not due the timeout.
specifically, try:
time rtcwake -m mem -a -s 10
does the system wake up reliably? the output from the
'time'
command will probably be stretched a bit -- perhaps by 2
seconds
or a little less. but it should be fairly
reproducible.
With the os2 installed, it NEVER wakes up on time without user input (and network)
paul
=---------------------
paul fox, pgf(a)laptop.org
_______________________________________________
Fedora-olpc-list mailing list
Fedora-olpc-list(a)redhat.com
https://www.redhat.com/mailman/listinfo/fedora-olpc-list
5:53 p.m.
On Wed, Jul 29, 2009 at 09:35:00AM -0400, Paul Fox wrote:
specifically, try:
time rtcwake -m mem -a -s 10
does the system wake up reliably?
No. It does wake on other activity once put into this sleep.
/sys/power/wakeup_events/* are all 1, and none of them are rtc.
/sys/devices/platform/rtc_cmos/power/wakeup is "enabled"
--
James Cameron
http://quozl.linux.org.au/
7:36 p.m.
james wrote:
On Wed, Jul 29, 2009 at 09:35:00AM -0400, Paul Fox wrote:
> specifically, try:
> time rtcwake -m mem -a -s 10
>
> does the system wake up reliably?
No. It does wake on other activity once put into this sleep.
thanks.
/sys/power/wakeup_events/* are all 1, and none of them are rtc.
like the lid, the rtc isn't a member of that club.
/sys/devices/platform/rtc_cmos/power/wakeup is "enabled"
okay. i suspect a kernel config error of some sort, because this
works in the SoaS-on-XO images.
paul
--
James Cameron
http://quozl.linux.org.au/
=---------------------
paul fox, pgf(a)laptop.org
5302
days inactive
5404
days old
12 comments
6 participants
participants (6)
-
Adric Net -
Daniel Drake -
James Cameron -
Paul Fox -
Steven M. Parrish -
Yioryos Asprobounitis