SSE/SSE2 support in os116
by Mikus Grinbergs
Happened to run an older version of mplayer on os116 on XO-1.5, and it
claimed "SSE supported but disabled" (also for SSE2). So I looked in
some Linux forums, and saw there: "CPUID will tell you whether the CPU
supports SSE/SSE2, but not the OS. The OS (linux in this case) can have
SSE and/or SSE2 disabled."
I looked in the config file residing in the boot directory in os116, but
saw nothing there about the enabling of SSE or SSE2 (not even of MMX).
My question -- was the older mplayer mistaken -- or is SSE/SSE2 actually
disabled in os116 ?
mikus
14 years
Re: New XO-1.5 10.2.0 build 116
by James Cameron
On Tue, Mar 30, 2010 at 12:24:39AM +0100, Tiago Marques wrote:
> That between XOs 1 & 1.5? I only have one 1.5 to test with.
Yes. If you only have one, then you can't really test that, but thanks
for offering.
> Or should I use a virtual machine to test os116?
No, I'm not sure how I can use results of VM testing.
--
James Cameron
http://quozl.linux.org.au/
14 years
Re: New XO-1.5 10.2.0 build 116
by James Cameron
On Mon, Mar 29, 2010 at 09:36:19PM +0100, Tiago Marques wrote:
> The Xv support recently introduced seems to be working well. The rest
> of the system seems to be doing fine like for the most recent builds.
> Anything else worth some extra testing for QA?
I'd like to know if activity sharing collaboration over wired ethernet
works.
--
James Cameron
http://quozl.linux.org.au/
14 years
Re: (fwd) Re: powerd on XO-1 (was Re: New release ... OS13 )
by Yioryos Asprobounitis
--- On Sun, 3/28/10, Paul Fox <pgf(a)laptop.org> wrote:
> From: Paul Fox <pgf(a)laptop.org>
> Subject: Re: (fwd) Re: powerd on XO-1 (was Re: New release ... OS13 )
> To: "Yioryos Asprobounitis" <mavrothal(a)yahoo.com>
> Cc: "OLPC Devel" <devel(a)lists.laptop.org>, "fedora-olpc-list" <fedora-olpc-list(a)redhat.com>
> Date: Sunday, March 28, 2010, 11:40 AM
> yioryos wrote:
> > So SLEEP basically drops connections and then the
> XO-1 fails
> > to DIM or BLANK. Setting SLEEP time _after_ DIM
> and BLANK has
>
> sounds like something's going wrong for you that isn't
> going wrong
> for me: dim and blank happen correctly after sleep
> for me.
>
> > the expected behavior. In all cases the XO
> fails to reconnect
> > to the preferred network after wakeup from
> SLEEP. I settled
>
> i haven't tested networking robustness on os13, so can't
> speak to
> this.
>
> please file tickets for the problems you're seeing, and
> attach
> dmesg output, as well as powerd.trace. (enable powerd
> tracing
> with "sudo powerd-config =trace-on".)
Well, my predicament with powerd and a proper ticket filling is that I can get no logs. So I'll describe the story instead ...:-)
Test settings SLEEP=15 DIM=30 BLANK=45 running on battery. os13 (clean). XO-1 CL1 Firmware q2e42d(not overclocked, no SDcard or anything attached to it)
Without trace-on the XO will sleep and will _not_ dim or blank. On slight touchpad touch after the timeouts (or spontaneous if you let it long enough) will wake to dim and then blank. Power button wakes it up fine but no trace log.
With trace-on, same behavior but on slight touch of the touchpad (or spontaneously) will wake to dim and freeze there. After hard reboot no trace log either :( and no I do not have a serial port adapter)
It's a clue though (I hope)
If while at sleep, pass dim or blank time points, you wake it up by typing or rubbing the touchpad constantly, will wake, dim and then recover to normal operation. This is where the attached powerd.trace is coming from.
It would appear that the kernel configuration is also relevant. With the os13 kernel I also got a freeze without the trace-on (1 in 5 tests). With the 2010322 kernel never (in 6 tests). Using one of my kernels patched for Aufs and with hfsplus, sisusbvga modules and in-kernel loop enabled, I can not get it to sleep unless both DIM and BLANK are before SLEEP time (I could provide config diffs and trace logs if you think it may help the issue at hand)
>
> paul
>
>
> > in DIM=180, BLANK=480, SLEEP=600. No huge power
> savings but
> > at least the build is usable.
> >
> >
> > --- On Sat, 3/27/10, Paul Fox <pgf(a)laptop.org>
> wrote:
> >
> > > From: Paul Fox <pgf(a)laptop.org>
> > > Subject: Re: (fwd) Re: powerd on XO-1 (was Re:
> New release ... OS13 )
> > > To: "Yioryos Asprobounitis" <mavrothal(a)yahoo.com>
> > > Cc: "OLPC Devel" <devel(a)lists.laptop.org>,
> "fedora-olpc-list"
> > <fedora-olpc-list(a)redhat.com>
> > > Date: Saturday, March 27, 2010, 1:26 PM
> > > yioryos wrote:
> > > > I guess the question is: is os13
> usable at this
> > > stage?
> > > > Should power management be be
> inactivated in the
> > > control panel?
> > > > Are there appropriate/recommended
> powerd.conf
> > > settings for the XO-1 at this
> > > > stage?
> > >
> > > maybe, i don't know, and i don't know.
> > >
> > > paul
> > > =---------------------
> > > paul fox, pgf(a)laptop.org
> > >
> >
> >
> >
>
> =---------------------
> paul fox, pgf(a)laptop.org
>
14 years
Re: New release of F11 for the XO-1 is available for testing - OS13
by Bernie Innocenti
On Mon, 2010-03-29 at 00:46 -0500, Mikus Grinbergs wrote:
> I've installed the 2010/03/22 XO-1 kernel on two os13 systems and on one
> 115-py system. Running those systems, I have seen no problems that I
> would think could be attributed to using this newest kernel. It is good
> enough for me -- but I customize my systems (including kernel parameter
> values and suchlike). Whether an unmodified system is good enough for
> your purposes is something you will have to decide for yourself.
Cool. Can you please test:
(1) camera and video playback in Record
(2) sound recording in Record
(this is expected to fail with any kernel, but we may be lucky)
(3) enable automatic power management in os115py and see if the camera
still works
(4) networking after a few cycles of suspend
> I've been installing new kernels for months. [ I actually rsync to
> /versions/pristine/xxx/boot/ ] This upgrade was more tricky than most
> -- kernel-firmware conflicts were found and I had to use --force
you could also install the new kernel-firmware package.
BTW, I've been wondering: does kernel-firmware contain anything that we
actually need? Probably not. It would be interesting to drop it and see
if anything breaks.
With some luck, we could greatly reduce the body of questionable blobs
that we ship with the OS images (the remaining offenders are the
libertas firmware and the EC code).
> > the alternate boot scheme (I wonder how many people actually use it and
> > if it's still worth keeping)
>
> Something (such as a form of olpc-update ?) needs to be available that
> is less drastic than using copy-nand (or equivalent). My beef with the
> alternate boot scheme is that the /versions tree takes up substantially
> more jffs2 space than what is actually running - whereas the XO-1 does
> not really have any jffs2 space to spare.
While olpc-update might never become usable for the general case, Daniel
said that it works well for small OS patches. For small changes, yum
would also work, although with a tiny window for failure.
What's the actual cost we're paying in terms of disk space and kludgery
in order to support olpc-update?
Flashing is drastic, but very fast and easy to perform. We could reduce
user annoyance by improving our journal backup-restore UI, which needs
to be done anyway for other data loss scenarios.
Currently, users are being told to save anything they want to keep to a
USB stick. Kids don't seem to be bothered, except for one girl who had
created a lot of really cool stuff in Scratch which we had to be backed
up manually. The upcoming sugarized Scratch will solve also this case.
--
// Bernie Innocenti - http://codewiz.org/
\X/ Sugar Labs - http://sugarlabs.org/
14 years
Re: New XO-1.5 10.2.0 build 116
by Chris Ball
Hi,
> First problem I have run into is that I see a problem with
> wireless networks after rebuilding. They showed up for about 30
> seconds and then disappeared.
>From http://wiki.laptop.org/go/XO_1.5_B2#Software_Limitations :
* If you have a B2 without hardware mods, you must disable suspend
using Control Panel->Power->Automatic power management, else your
wireless device will disconnect on suspend and not come back until
the next reboot.
- Chris.
--
Chris Ball <cjb(a)laptop.org>
One Laptop Per Child
14 years
ANNOUNCE: New F11 XO-1build 115 Paraguay
by Bernie Innocenti
This is a custom XO-1 OS image released by the Paraguay Educa technology
team for field testing in Caacupé:
http://people.sugarlabs.org/bernie/olpc/f11-xo1-py/os115.img
http://people.sugarlabs.org/bernie/olpc/f11-xo1-py/os115.crc
http://people.sugarlabs.org/bernie/olpc/f11-xo1-py/os115.img.fs.zip
The system is a derivative of Stephen Parrish's excellent F11-XO1
series, frozen a few weeks ago to concentrate on stability and field
testing. Our short-term goal is to meet a release criteria of "no
regressions against build 801". Once this is done, we'll re-sync with
the latest improvements from our upstreams, F11-XO1.5 and F11-XO1.
== Changes relative to the previous release (OS65 Paraguay) ==
* Removed all translations except English and Spanish to save space
* 3G broadband support (untested, probably buggy)
* Pick up all fixes from fedora-updates
* Add patent-encumbered multimedia codecs (gstreamer-plugins-bad)
== Bugs fixed ==
* Write activity doesn't let you cut, paste or delete selection
http://bugs.sugarlabs.org/ticket/1817
* Robot function in Speak does not work
http://dev.laptop.org/ticket/10059
* Graphics artifacts with some GMail backgrounds
http://dev.laptop.org/ticket/10076
* Black GTK buttons in Gnome and elsewhere
http://dev.laptop.org/ticket/7830
* Keyboard misconfigured if A/C is unplugged on first boot after update
* NetworkManager crashes on suspend/resume
(we have only a temporary work-around, tch is working on a solution)
* Disable "automatic power management" even on first boot
(this is a temporary work-around for wi-fi and XVideo bugs)
* Activities updates from ASLO should go through local mirror
http://trac.paraguayeduca.org/ticket/553
== Known bugs ==
Remaining bugs are summarized here:
http://wiki.paraguayeduca.org/index.php/Devel/Builds/Todo
In particular, these are the remaining *known* regressions wrt the
old stable build from OLPC (OS801 Paraguay):
* Record does not record sound
http://bugs.sugarlabs.org/ticket/1244
* NetworkManager crashes on resume from suspend
We have an temporary workaround. See thread with subject
"NetworkManager from fedora-updates-testing broken on
F11-XO1" for full details.
Many more bugs are likely to be filed over the next days, as our testing
team works through their test plan.
== How to help testing ==
Feedback from the entire community is of course welcome as well. Bugs
belonging to upstream components should be filed in the usual trackers:
* Sugar and activities: http://bugs.sugarlabs.org/
* Fedora 11: http://bugzilla.redhat.com/
* Drivers and OLPC customizations: http://dev.laptop.org/
* Paraguay-specific bugs: http://trac.paraguayeduca.org/
If you're unsure where a bug belongs to, use the Paragauy Educa bug
tracker. Please, always cc me so I can keep the status summary updated.
We're unlikely to dedicate much attention to bugs affecting Gnome and
obscure activities with no active maintainer, but it's good to stay
informed on what's broken anyway. For everything else, we'll do our
best, with the help of OLPC, Fedora, and Sugar Labs.
== How to join development ==
Build system source:
http://git.paraguayeduca.org/gitweb/users/bernie/olpc-os-builder.git
Yum Repository of our custom RPMs:
http://repo.paraguayeduca.org/f11-xo1-py/i386/os/
--
// Bernie Innocenti - http://codewiz.org/
\X/ Sugar Labs - http://sugarlabs.org/
14 years
(fwd) Re: powerd on XO-1 (was Re: New release ... OS13 )
by Paul Fox
when i reply to my own posts, my mailer screws up. resending
with proper headers...
(only new info: i've filed #10090)
paul
i wrote:
> Date: Sat, 27 Mar 2010 12:44:40 EDT
> cc: OLPC Devel <devel(a)lists.laptop.org>,
> fedora-olpc-list <fedora-olpc-list(a)redhat.com>
> From: Paul Fox <pgf(a)laptop.org>
> Subject: Re: powerd on XO-1 (was Re: New release ... OS13 )
>
> i wrote:
> > mathieu wrote:
> > > On Sat, Mar 27, 2010 at 16:42, Paul Fox <pgf(a)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(a)laptop.org
> part 2 text/plain 129
> _______________________________________________
> Devel mailing list
> Devel(a)lists.laptop.org
> http://lists.laptop.org/listinfo/devel
=---------------------
paul fox, pgf(a)laptop.org
14 years
What's going on with Sugar on a Stick?
by Sebastian Dziallas
Hi all,
as you may have noticed, there are a couple of changes coming to Sugar
on a Stick to keep the whole project sustainable. In the upcoming month,
from March 28 (I'll be off starting Sunday night) to May 7, my ability
to devote time to the project will cease. I have to prepare for my major
A-level exams; more importantly, I have to secure a significant amount
of funding in order to be able to attend college later this fall. (If
you're interested in helping, see
http://sdziallas.com/blog/sebastian/2010/03/sebastian-needs-100k.html
for more details - any advice would be appreciated.)
This does not affect the release date. Sugar on a Stick will be released
as a spin through Fedora's release engineering process on May 11. We are
bound to this date and will have a working release in time. The general
release schedule including all relevant policies is available here [1].
Nightly builds are also available [2] (and will contain a fixed IRC
activity within a couple of days, as soon as [3] has been pushed to stable).
Activity authors are also advised that the final freeze date for package
updates is April 27, so make sure to get fixes pushed well in advance to
give package maintainers and the update system time to process.
Peter Robinson has kindly agreed to act in case something is needed.
Please make sure to post to the appropriate lists, though, so that
everybody is in the loop. Finally, please file bugs at
bugs.sugarlabs.org as explained in [4] to save all of us time.
Thanks,
--Sebastian
[1] http://fedoraproject.org/wiki/Releases/13/Schedule
[2] http://alt.fedoraproject.org/pub/alt/nightly-composes/soas/
[3] https://admin.fedoraproject.org/updates/sugar-xoirc-6-4.fc13
[4] http://wiki.sugarlabs.org/go/Talk:Sugar_on_a_Stick/Getting_Involved
14 years
