Initial F14 developers-only release for XO and XO-1.5
by Daniel Drake
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 that publishing the work
so far is the first step in getting things fixed.
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 doesn't work right on either laptop,
desktop switching lands you at a blank screen.
For now, please don't file bugs unless you include patches. And, to
take 1 bite at a time out of this huge task, lets ignore all but the
biggest sugar issues for now because there is plenty of OS work to be
done first. (or alternatively lets take sugar issues directly to SL
trac)
And the links:
2.6.35 kernel is in git://dev.laptop.org/olpc-2.6 branch olpc-2.6.35
OS build is done from 'f14' branch of olpc-os-builder
First released images are at http://build.laptop.org/F14/os1/
Trac is at http://dev.laptop.org/milestone/F14 (basically my immediate
TODO), please don't file tickets unless you include patches in these
early days
Note: I haven't tested those exact images (since Chris @ OLPC built
them), so boot-testing them can be the first task for someone. I have
been working from the same codebases making local images successfully,
so they will probably work (to the extent that things are working).
At this point this is all something put together by me in my spare
time. It's not known if or when OLPC would start working on an
official release from these efforts. But I figure that if we get
things properly stabilized and all the work is done cleanly, we'll
find one way or another to get this in the hands of deployments.
Daniel
13 years, 5 months
Re: OLPC wireless startup at boot time
by Mikus Grinbergs
> The question is why does it take so long for the connection to be established?
>
> A 10-12 second reconnect time is to be expected:
> 1. A 1 second delay for the device to be probed and initialized on resume
> 2. NetworkManager has a 7 second delay hardcoded
> 3. A 1-2 second delay for scanning to complete
> 4. A 1-2 second delay for authentication, association, key exchange
> (if applicable) and DHCP.
It has looked to me as though icons already in Neighborhood View can
disappear as the XO reinitializes a complete scan of its radio spectrum.
I still think that in the plurality of wireless startup cases the pupil
will expect to make a connection on the SAME frequency that the XO was
using the last time his XO system's wireless was in use.
[I hope that an XO which is in "I've had my wireless connected for a
whole hour" mode can nevertheless detect whenever a __new__ AP shows up
(whose radio signal was not previously noticed). If that is possible,
then the SAME capability should be applicable even at startup time.]
I'm thinking that at startup, Network Manager ought to be *inhibited*
while the XO listens on the same frequency as was last used. If the XO
hears a strong enough signal, it ought to go into its "I've had my
wireless connected for a whole hour" mode -- and depend upon "radio
signal discovery" the same way that it does when not starting up..
Only if the XO at startup does NOT hear a strong signal on the last-used
frequency should the XO depend upon scanning and Network Manager to
determine "what are the radio signals that I am receiving now".
Whenever steps 2-3 above can be avoided, wireless startup will be
noticeably quicker.
[For those cases where the pupil has moved to a different schoolroom
while his XO was powered down - once the XO is powered up let the pupil
perform whatever manual "tuning" procedure he would have used if he had
moved to that different schoolroom while carrying his XO powered up.]
mikus
13 years, 6 months
Script to install missing langs?
by Martin Langhoff
Hi folks,
we're now including a very limited set of langs in our OS images. This
can make life rather awkward for small deployments (read: no tech
team) using languages not included in our build...
Is there a script to install missing locales for already-installed rpms?
Cross-posting to fedora-olpc -- maybe there's a Fedora tool to install
pruned locales?
cheers,
m
--
martin.langhoff(a)gmail.com
martin(a)laptop.org -- School Server Architect
- ask interesting questions
- don't get distracted with shiny stuff - working code first
- http://wiki.laptop.org/go/User:Martinlanghoff
13 years, 6 months
