[Testing] New F11 for the XO-1 Build 6
Rafael Enrique Ortiz Guerrero
dirakx at gmail.com
Wed Aug 26 16:24:13 EDT 2009
Thanks for your reply Mitch.
Even thought, i pressed the '√' gamepad button at boot
the system does not pass from loading ramdisk,
can any body build a new F11 on XO .img with the solution propossed
by Mitch ?
wmb: The solution for this is to add "dcon-unfreeze unfreeze" to
/boot/olpc.fth, somewhere before the "boot" line, thus turning off
"pretty boot". Alternatively, if you want to keep pretty boot,
releasing the screen only after all of the text messages have
finished, you can add "echo 0 >/sys/devices/platform/dcon/freeze" to a
or what can i do to workaround this issue ?.
On Wed, Aug 26, 2009 at 3:06 PM, Mitch Bradley<wmb at laptop.org> wrote:
> It's probably the same thing as the first item in
> We made "pretty boot" the default in later versions of Open Firmware,
> but many alternative operating systems don't know how to "unfreeze" the
> Rafael Enrique Ortiz Guerrero wrote:
>> i was trying these instructions
>> (http://wiki.laptop.org/go/F11_for_XO-1) on an XO-1 for the new
>> but the booting gets stuck on loading the ramdisk image
>> is there something else i should be doing ?.
>> Rafael Ortiz
>> On Wed, Aug 26, 2009 at 2:23 PM, Yioryos
>> Asprobounitis<mavrothal at yahoo.com> wrote:
>>> Thank you.
>>> Now olpc-powerd works as advertised. Kudos. However the problem with the overlap with the GNOME PM remains.
>>> I guess the X-server and Gnome power management updates also did not affect the battery monitor and screen rotation issues rotation. Next one may be :)
>>> Did the automatic software update ok, found etoys-103, updated it but kept finding it as updatable. This was also the case with os5. Also etoys (and scratch) fail to get the fill color after the first use and to not have a Journal entry.
>>> Other activities with problems
>>> Pippy-34 fails to find and import modules (I have filled a ticked since os3). Could be a distro-specific problem though.
>>> Record does _not_ record sound. Actually the mic light is not even coming up (this was also the case in os5). Use of mic does not solve the problem. The "silent" recording is not saved at the bottom strip.
>>> Measure also fails to see the mic (internal or external) and record anything on first launch. Is there anyway to test if mic is working? On the second launch Measure fails to load altogether. This was also the case in os5. If you erase the existing Journal entry launches OK (but fails to see the mic again)
>>> Might be an issue with Journal/paths? (datastore log is full of dbus warnings) Pippy also generates a working tmp copy of the application file in ~/.sugar/default/org.laptop/tmp/ and from there can not find the modules that do exist.
>>> Of course could be independent problems.
>>> Should I be filling tickets with (if not present)? I mean is F11-XO1 going to be the way to Sugar0.84?
>>> Fedora-olpc-list mailing list
>>> Fedora-olpc-list at redhat.com
>> Testing mailing list
>> Testing at lists.laptop.org
> Devel mailing list
> Devel at lists.laptop.org
More information about the Devel