OS13 is now available for testing.
It is available for download at http://people.sugarlabs.org/~smparrish
Installation instructions are here http://wiki.laptop.org/go/F11_for_XO-1#Installation_instructions
I want to thank everyone who has taken the time to test these releases. We are getting close to an Final and Official release, and without your help would not have made it to this point.
Steven
steven m. parrish wrote:
OS13 is now available for testing.
excellent stuff!
i'm sorry i didn't get a chance to try os12, but i just installed os13.
suspend/resume, and powerd, seem to be working mostly fine, as far as i've tested. (which wasn't all that far.)
there are a few things i noticed that are a bit of a concern, and arise directly from me having been concentrating entirely on XO-1.5, and not considering the effects of some changes on XO-1.
- the sleep/dim/blank timers are tuned for XO-1.5. in os13 sleep happens in 15 seconds, dim happens 45s later, and blank happens 3 minutes after that. this behavior is quite different than anything we've shipped on XO-1 before -- previously we dimmed, then slept. (and never blanked, though we would have liked to.) the only effects of this change i've seen so far is that the wakeup-on-keystroke delay is more noticeable than XO-1.5 (obviously), and on the network view, the access points seem to all disappear more often than they used to. i haven't looked at why that last thing happens. it's certainly annoying. since i think the wlan card stays powered, i don't really understand it.
- the "config_MESH_DURING_SUSPEND" setting is set to "no", which means the wireless won't stay on when the laptop is sleeping. i think ohmd runs some code to decide whether it should leave mesh active or not -- there are "todo" comments to that effect in powerd, but i've never looked at it further. i don't know if the "relay mesh for others while sleeping" feature is used in the field -- i suspect not.
- powerd now integrates most of olpc-pwr-log, which will let us gather battery and charging data from the field much more readily. i don't know that we necessarily want to run this on XO-1 all the time -- it's definitely not free in terms of cpu (even if it only runs every minute or so), or disk. the logs it keeps (which start out in /var/log, and are moved to /home/olpc/olpc-pwr-log) may take more space than XO-1 users would like to give up. (currently capped at 10M)
- in the next releases of powerd, there are even more changes surrounding wake-on-wlan that may have an effect on XO-1. i'll try and be more proactive about keeping XO-1 working, but it will have to be lower priority than XO-1.5, at least for a while.
in any case, all of this points at having separate default configurations for powerd on XO-1 and XO-1.5. i guess this should be handled by the rpm install -- but i'm not sure how. (help appreciated.)
thanks again for all your great work!
paul =--------------------- paul fox, pgf@laptop.org
On Sat, Mar 27, 2010 at 16:42, Paul Fox pgf@laptop.org wrote:
steven m. parrish wrote: > OS13 is now available for testing.
I just tried it and am encountering a very annoying issue: if I don't do anything, the screen dims, and everything just freezes this way. Screen remains dim, keyboard and mouse don't respond.
Is this a known issue? Any idea how I could help debugging it?
---------- Mathieu Bridon
mathieu wrote:
On Sat, Mar 27, 2010 at 16:42, Paul Fox pgf@laptop.org wrote:
steven m. parrish wrote: ��> OS13 is now available for testing.
I just tried it and am encountering a very annoying issue: if I don't do anything, the screen dims, and everything just freezes this way. Screen remains dim, keyboard and mouse don't respond.
Is this a known issue? Any idea how I could help debugging it?
can you recover at all? if so, a copy of the output of dmesg would probably be helpful. probably most helpful if it were attached to a trac ticket. i don't know how f11-on-xo1 tickets are being filed, though.
oh. wait. i just went and fetch my os13 machine, and sure enough -- it's completely locked up. :-/ it wasn't, earlier.
i'll look into it, but a dmesg from you would be useful in any case, if you can get it.
i know there's been some churn in the XO-1 wireless area, to get suspend/resume working. should i still be seeing this in the logs?
.... [ 166.626628] usb 1-1: reset high speed USB device using ehci_hcd and address 3 [ 166.788820] libertas: Not issuing HOST_SLEEP_CFG on XO-1 [ 166.794406] PM: Finishing wakeup. [ 166.797732] Restarting tasks ... done. [ 171.336902] libertas: command 0x000b timed out [ 171.341449] libertas: requeueing command 0x000b due to timeout (#1) [ 174.346795] libertas: command 0x000b timed out [ 174.351343] libertas: requeueing command 0x000b due to timeout (#2) [ 177.356689] libertas: command 0x000b timed out [ 177.361236] libertas: requeueing command 0x000b due to timeout (#3) [ 180.366585] libertas: command 0x000b timed out [ 180.371131] libertas: Excessive timeouts submitting command 0x000b [ 180.376495] Resetting OLPC wireless via EC... [ 180.386912] usb 1-1: USB disconnect, address 3 [ 180.391514] libertas: PREP_CMD: command 0x000b failed: -110 [ 180.473533] libertas: SCAN_CMD failed [ 182.757118] usb 1-1: new high speed USB device using ehci_hcd and address 4 [ 182.920801] usb 1-1: configuration #1 chosen from 1 choice [ 182.937592] usb 1-1: firmware: requesting usb8388.bin [ 183.743575] usb8xxx: Firmware ready event received [ 183.750328] libertas: 00:17:c4:0d:27:d0, fw 5.110.22p23, cap 0x000003a3 [ 183.768505] libertas: eth0: Marvell WLAN 802.11 adapter [ 183.775009] libertas: Not issuing HOST_SLEEP_CFG on XO-1 [ 183.780996] libertas: PREP_CMD: command 0x0074 failed: 2 [ 183.786319] usb8xxx: Firmware does not seem to support PS mode [ 188.358189] ADDRCONF(NETDEV_UP): eth0: link is not ready [ 198.903425] msh0: no IPv6 routers present [ 205.829492] olpc-pm: SCI 0x4 received [ 205.836519] olpc-pm: SCI 0x0 received [ 211.508645] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [ 222.186771] eth0: no IPv6 routers present
paul =--------------------- paul fox, pgf@laptop.org
i wrote:
mathieu wrote:
On Sat, Mar 27, 2010 at 16:42, Paul Fox pgf@laptop.org wrote:
steven m. parrish wrote: ��> OS13 is now available for testing.
I just tried it and am encountering a very annoying issue: if I don't do anything, the screen dims, and everything just freezes this way. Screen remains dim, keyboard and mouse don't respond.
Is this a known issue? Any idea how I could help debugging it?
can you recover at all? if so, a copy of the output of dmesg would probably be helpful. probably most helpful if it were attached to a trac ticket. i don't know how f11-on-xo1 tickets are being filed, though.
oh. wait. i just went and fetch my os13 machine, and sure enough -- it's completely locked up. :-/ it wasn't, earlier.
i don't know that it's the same lockup, but i've just filed #10090, with full dmesg log. (captured via serial)
paul =--------------------- paul fox, pgf@laptop.org
On 27 March 2010 09:42, Paul Fox pgf@laptop.org wrote:
in any case, all of this points at having separate default configurations for powerd on XO-1 and XO-1.5. i guess this should be handled by the rpm install -- but i'm not sure how. (help appreciated.)
It can't be done cleanly in RPM install, since the RPM is installed on a computer that makes the build, not on an XO.
More realistic options would be runtime detection, or overriding the powerd config from the xo1-specific module in the build system. And there are probably others.
Daniel
daniel wrote:
On 27 March 2010 09:42, Paul Fox pgf@laptop.org wrote:
in any case, all of this points at having separate default configurations for powerd on XO-1 and XO-1.5. i guess this should be handled by the rpm install -- but i'm not sure how. (help appreciated.)
It can't be done cleanly in RPM install, since the RPM is installed on a computer that makes the build, not on an XO.
good point. thanks.
paul
More realistic options would be runtime detection, or overriding the powerd config from the xo1-specific module in the build system. And there are probably others.
Daniel
=--------------------- paul fox, pgf@laptop.org
Disclaimer: I am not asking for help: I am sharing my experiences.
I've gotten gun-shy regarding suspend. Accordingly, when I flashed os13 and first booted it (not having experienced any problems bringing it up) I immediately went into My Settings and turned off the checkmark for power management. I then customized the os13 build (which involved a couple of reboots), including modifying /etc/powerd/powerd.conf values. [My values dim before blanking, blank before sleeping, and inhibit power-down while connected to AC.]
I then noticed that os13 came with olpc-powerd-13. I used yum update to install olpc-powerd-15 (keeping my own powerd.conf values). Again, no problems with system behavior (nor with reboot).
Having read the various posts regarding suspend on os13, I put the checkmark for power management back into My Settings. I let my system (with powerd-15) go into "hard sleep" (screen dark, power led pulsing). A touch on the native keyboard brought the XO-1 back to life.
My conclusion: I have no problems using suspend on os13. What I have run so far on os13 leads me to consider this release as completely usable.
mikus
Em 27-03-2010 22:23, Mikus Grinbergs escreveu:
Disclaimer: I am not asking for help: I am sharing my experiences.
I've gotten gun-shy regarding suspend. Accordingly, when I flashed os13 and first booted it (not having experienced any problems bringing it up) I immediately went into My Settings and turned off the checkmark for power management. I then customized the os13 build (which involved a couple of reboots), including modifying /etc/powerd/powerd.conf values. [My values dim before blanking, blank before sleeping, and inhibit power-down while connected to AC.]
I then noticed that os13 came with olpc-powerd-13. I used yum update to install olpc-powerd-15 (keeping my own powerd.conf values). Again, no problems with system behavior (nor with reboot).
Having read the various posts regarding suspend on os13, I put the checkmark for power management back into My Settings. I let my system (with powerd-15) go into "hard sleep" (screen dark, power led pulsing). A touch on the native keyboard brought the XO-1 back to life.
My conclusion: I have no problems using suspend on os13. What I have run so far on os13 leads me to consider this release as completely usable.
My weirdness with networking was, perhaps, due to this issue.
Where did you get olpc-powerd-15 from?
Thanks, Rui
Too many builds and only one XO-1 :-) Is there any priority? Is testing os115-py immediately applicable to os13 and vice versa?
--- On Sat, 3/27/10, Steven M. Parrish smparrish@gmail.com wrote:
From: Steven M. Parrish smparrish@gmail.com Subject: New release of F11 for the XO-1 is available for testing - OS13 To: "fedora-olpc-list" fedora-olpc-list@redhat.com, "OLPC Devel" devel@lists.laptop.org, "Sugar Development" sugar-devel@lists.sugarlabs.org, devel-announce@lists.laptop.org, testing@lists.laptop.org Date: Saturday, March 27, 2010, 8:53 AM OS13 is now available for testing.
It is available for download at http://people.sugarlabs.org/~smparrish
Installation instructions are here http://wiki.laptop.org/go/F11_for_XO-1#Installation_instructions
I want to thank everyone who has taken the time to test these releases. We are getting close to an Final and Official release, and without your help would not have made it to this point.
Steven
===================================================== Steven M. Parrish
gpg fingerprint: 4B6C 8357 059E B7ED 8095 0FD6 1F4B EDA0 A9A6 13C0 http://tuxbrewr.fedorapeople.org/ irc.freenode.net: Nickname: SMParrish Channels: #fedora-kde, #fedora-olpc, #fedora-edu, #sugar, #packagekit _______________________________________________ olpc mailing list olpc@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/olpc
On Sat, 2010-03-27 at 10:12 -0700, Yioryos Asprobounitis wrote:
Too many builds and only one XO-1 :-) Is there any priority?
We'll deploy this to ~4000 kids really-soon-now. Bugs reported within 1-2 weeks have a chance of being fixed in time.
Is testing os115-py immediately applicable to os13 and vice versa?
They should already be very similar, and we're going to merge as much as possible.
Both F11-XO1/os13 and os115-py are using the same custom kernel. However, kernel headers are not included, so trying to yum install compiling packages (gcc/make) you get the fedora 2.6.30 kernel headers instead. Maybe an appropriate repo should be included, if not the olpc one, or at least some way to get point to kernel headers, sources etc
--- On Sat, 3/27/10, Steven M. Parrish smparrish@gmail.com wrote:
From: Steven M. Parrish smparrish@gmail.com Subject: New release of F11 for the XO-1 is available for testing - OS13 To: "fedora-olpc-list" fedora-olpc-list@redhat.com, "OLPC Devel" devel@lists.laptop.org, "Sugar Development" sugar-devel@lists.sugarlabs.org, devel-announce@lists.laptop.org, testing@lists.laptop.org Date: Saturday, March 27, 2010, 8:53 AM OS13 is now available for testing.
It is available for download at http://people.sugarlabs.org/~smparrish
Installation instructions are here http://wiki.laptop.org/go/F11_for_XO-1#Installation_instructions
I want to thank everyone who has taken the time to test these releases. We are getting close to an Final and Official release, and without your help would not have made it to this point.
Steven
===================================================== Steven M. Parrish
gpg fingerprint: 4B6C 8357 059E B7ED 8095 0FD6 1F4B EDA0 A9A6 13C0 http://tuxbrewr.fedorapeople.org/ irc.freenode.net: Nickname: SMParrish Channels: #fedora-kde, #fedora-olpc, #fedora-edu, #sugar, #packagekit _______________________________________________ olpc mailing list olpc@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/olpc
Steven - your builds (as released) continue to leave out the entries for http://xs-dev.laptop.org/~dsd/repos/f11/ and ../f11-xo1/ from /etc/yum.repos.d/ That has the effect of "freezing" the XO-1 services levels of your builds -- when potential newly-committed XO-1 rpms cannot be applied on-the-fly. Was that your intent ?
Also, os13 came with a NetworkManager dated 2009/12/23. Was the newer F12 NetworkManager dated 2010/02/25 (and available in updates-testing) left deliberately out of os13 ?
mikus
On Sat, 2010-03-27 at 17:01 -0500, Mikus Grinbergs wrote:
Steven - your builds (as released) continue to leave out the entries for http://xs-dev.laptop.org/~dsd/repos/f11/ and ../f11-xo1/ from /etc/yum.repos.d/ That has the effect of "freezing" the XO-1 services levels of your builds -- when potential newly-committed XO-1 rpms cannot be applied on-the-fly. Was that your intent ?
These repositories are created by aggregating public_rpms directories of multiple developers. These packages are often fresh from rpmbuild and totally untested on the XO-1.
I discussed this with cjb, and he recommended that stable build pin-point packages manually from a stable repository instead.
Also, os13 came with a NetworkManager dated 2009/12/23. Was the newer F12 NetworkManager dated 2010/02/25 (and available in updates-testing) left deliberately out of os13 ?
The 20100225 version crashes on resume from suspend:
http://lists.laptop.org/pipermail/devel/2010-February/thread.html#27505
Martin Abente of Paraguay Educa has been working on a fix.
Thanks for explaining about os13 not using the Feb 2010 NetworkManager.
Another question, if I may -- os13 comes with a 2010/03/13 XO-1 kernel (commit bfcaa33). Is it ok to install the newer 2010/03/22 XO-1 kernel (commit 3f93d90) in my os13 system ?
mikus
On Sun, 2010-03-28 at 15:51 -0500, Mikus Grinbergs wrote:
Another question, if I may -- os13 comes with a 2010/03/13 XO-1 kernel (commit bfcaa33). Is it ok to install the newer 2010/03/22 XO-1 kernel (commit 3f93d90) in my os13 system ?
Please try and let me know. I froze on that version because some XO-1 specific bugs had appeared in the following revisions. Those may have gone by now.
To install a kernel on the XO-1, you need to do some trickery:
rpm -i kernel-* rsync -a /boot/ /versions/running/boot/
This is due to the odd filesystem layout used to implement the alternate boot scheme (I wonder how many people actually use it and if it's still worth keeping).
Em 27-03-2010 12:53, Steven M. Parrish escreveu:
OS13 is now available for testing.
It is available for download at http://people.sugarlabs.org/~smparrish
Installation instructions are here http://wiki.laptop.org/go/F11_for_XO-1#Installation_instructions
I want to thank everyone who has taken the time to test these releases. We are getting close to an Final and Official release, and without your help would not have made it to this point.
Nice to see LXDE battery now being able to read OLPC battery :)
Sadly, CPU bound actions seems to affect wifi even worse than before.
Example: it's very hard for me to "yum install anything" since wifi just dies, then after a long while comes back, slowly...
I'm being more carefull noting down what I did to get an lxde desktop environment as it may be useful for others.
Rui
Em 10-04-2010 11:48, Rui Miguel Silva Seabra escreveu:
Em 27-03-2010 12:53, Steven M. Parrish escreveu:
OS13 is now available for testing.
It is available for download at http://people.sugarlabs.org/~smparrish
Installation instructions are here http://wiki.laptop.org/go/F11_for_XO-1#Installation_instructions
I want to thank everyone who has taken the time to test these releases. We are getting close to an Final and Official release, and without your help would not have made it to this point.
Sadly, CPU bound actions seems to affect wifi even worse than before.
Example: it's very hard for me to "yum install anything" since wifi just dies, then after a long while comes back, slowly...
Sorry, it seems to be periodical and not cpu bound, as it happened while it was idle. Unsure if it's a regular period or not.
Rui
rui miguel silva seabra wrote:
Em 27-03-2010 12:53, Steven M. Parrish escreveu:
OS13 is now available for testing.
It is available for download at http://people.sugarlabs.org/~smparrish
Installation instructions are here http://wiki.laptop.org/go/F11_for_XO-1#Installation_instructions
I want to thank everyone who has taken the time to test these releases. We are getting close to an Final and Official release, and without your help would not have made it to this point.
Nice to see LXDE battery now being able to read OLPC battery :)
Sadly, CPU bound actions seems to affect wifi even worse than before.
Example: it's very hard for me to "yum install anything" since wifi just dies, then after a long while comes back, slowly...
are you sure the laptop isn't simply suspending? i've not heard of cpu activity causing wifi outages before.
paul =--------------------- paul fox, pgf@laptop.org
Em 12-04-2010 15:15, Paul Fox escreveu:
rui miguel silva seabra wrote:
Em 27-03-2010 12:53, Steven M. Parrish escreveu:
OS13 is now available for testing.
It is available for download at http://people.sugarlabs.org/~smparrish
Installation instructions are here http://wiki.laptop.org/go/F11_for_XO-1#Installation_instructions
I want to thank everyone who has taken the time to test these releases. We are getting close to an Final and Official release, and without your help would not have made it to this point.
Nice to see LXDE battery now being able to read OLPC battery :)
Sadly, CPU bound actions seems to affect wifi even worse than before.
Example: it's very hard for me to "yum install anything" since wifi just dies, then after a long while comes back, slowly...
are you sure the laptop isn't simply suspending? i've not heard of cpu activity causing wifi outages before.
In a later email, same day, about 6h later, I understood it as a problem with the sleep mode, which happened after 15 s of idle.
I postponed sleep to way after blank and now it's usable.
Rui
rui miguel silva seabra wrote:
Em 12-04-2010 15:15, Paul Fox escreveu:
rui miguel silva seabra wrote:
Em 27-03-2010 12:53, Steven M. Parrish escreveu:
OS13 is now available for testing.
It is available for download at http://people.sugarlabs.org/~smparrish
Installation instructions are here http://wiki.laptop.org/go/F11_for_XO-1#Installation_instructions
I want to thank everyone who has taken the time to test these releases.
We
are getting close to an Final and Official release, and without your
help
would not have made it to this point.
Nice to see LXDE battery now being able to read OLPC battery :)
Sadly, CPU bound actions seems to affect wifi even worse than before.
Example: it's very hard for me to "yum install anything" since wifi just dies, then after a long while comes back, slowly...
are you sure the laptop isn't simply suspending? i've not heard of cpu activity causing wifi outages before.
In a later email, same day, about 6h later, I understood it as a problem with the sleep mode, which happened after 15 s of idle.
I postponed sleep to way after blank and now it's usable.
good. the latest version of powerd contains code to monitor network usage, and to make a guess as to whether it's okay to suspend. on XO-1.5 it seems to make yum work without extra effort. i've not been able to test this on XO-1, so if someone could do that, i'd appreciate it. (a yum update of olpc-powerd may work, or, fetch olpc-powerd-18 from http://dev.laptop.org/~pgf/rpms.) the feature depends on the presence of iptables, so if that's not there it won't work.
paul =--------------------- paul fox, pgf@laptop.org
--- On Thu, 4/15/10, Paul Fox pgf@laptop.org wrote:
From: Paul Fox pgf@laptop.org Subject: Re: New release of F11 for the XO-1 is available for testing - OS13
good. the latest version of powerd contains code to monitor network usage, and to make a guess as to whether it's okay to suspend. on XO-1.5 it seems to make yum work without extra effort. i've not been able to test this on XO-1, so if someone could do that, i'd appreciate it. (a yum update of olpc-powerd may work, or, fetch olpc-powerd-18 from http://dev.laptop.org/~pgf/rpms.) the feature depends on the presence of iptables, so if that's not there it won't work.
A bit off topic but I tried kbdshim12/powerd18 on os140py. No luck. Behaves similar to os13 (see http://lists.fedoraproject.org/pipermail/olpc/2010-March/002301.html )
paul
paul fox, pgf@laptop.org _______________________________________________ olpc mailing list olpc@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/olpc
yioryos wrote:
--- On Thu, 4/15/10, Paul Fox pgf@laptop.org wrote:
From: Paul Fox pgf@laptop.org Subject: Re: New release of F11 for the XO-1 is available for testing - OS13
good. the latest version of powerd contains code to monitor network usage, and to make a guess as to whether it's okay to suspend. on XO-1.5 it seems to make yum work without extra effort. i've not been able to test this on XO-1, so if someone could do that, i'd appreciate it. (a yum update of olpc-powerd may work, or, fetch olpc-powerd-18 from http://dev.laptop.org/~pgf/rpms.) the feature depends on the presence of iptables, so if that's not there it won't work.
A bit off topic but I tried kbdshim12/powerd18 on os140py. No luck. Behaves similar to os13 (see http://lists.fedoraproject.org/pipermail/olpc/2010-March/002301.html )
i see. i thought the suspend/resume issues had been fixed in the most recent XO-1 kernels. perhaps that's not the case.
paul =--------------------- paul fox, pgf@laptop.org
--- On Thu, 4/15/10, Paul Fox pgf@laptop.org wrote:
From: Paul Fox pgf@laptop.org Subject: Re: New release of F11 for the XO-1 is available for testing - OS13 To: "Yioryos Asprobounitis" mavrothal@yahoo.com Cc: olpc@lists.fedoraproject.org Date: Thursday, April 15, 2010, 11:57 AM yioryos wrote:
--- On Thu, 4/15/10, Paul Fox pgf@laptop.org
wrote:
From: Paul Fox pgf@laptop.org Subject: Re: New release of F11 for the XO-1 is
available for testing - OS13
good. the latest version of powerd
contains code to
monitor network usage, and to make a guess as to whether
it's okay
to suspend. on XO-1.5 it seems to make yum
work without
extra effort. i've not been able to test this on
XO-1, so
if someone could do that, i'd appreciate it. (a yum
update of
olpc-powerd may work, or, fetch olpc-powerd-18 from http://dev.laptop.org/~pgf/rpms.) the feature depends on the presence of iptables,
so if
that's not there it won't work.
A bit off topic but I tried kbdshim12/powerd18 on
os140py.
No luck. Behaves similar to os13 (see http://lists.fedoraproject.org/pipermail/olpc/2010-March/002301.html
)
i see. i thought the suspend/resume issues had been fixed in the most recent XO-1 kernels. perhaps that's not the case.
os140py is using a custom kernel with many more additional goodies and some debugging/controls off, so...
paul
paul fox, pgf@laptop.org