Quick run through of Activities on XO-1.5 (Part I)
by Mikus Grinbergs
Wanted to verify which of the "standard" Activities (those included
in recent builds, also on soas) would _launch__ on current build.
[The only one which failed to launch was Measure (ticket #9371).]
Note: For many of these Activities, I do not know enough about how
they are supposed to work to be able to "test" them. Thus the list
below did not "test" Activities - just checked if they would launch:
Hardware: XO-1.5 B2
Build: os32
Sugar: 0.84.5-1
> ---
> Analyze - 8 yes
> Arithmetic - 1 yes
> Browse - 108 yes - not polished
> Calculate - 30 yes
> CartoonBuilder - 5 yes
> Chat - 65 yes
> Clock - 5 yes
> Colors - 15 yes
> Develop - 39 yes - keep error
> Distance - 14 yes
> Etoys - 108 yes - slower than XO-1
> FlipSticks - 3 yes
> FreeCell - 1 yes
> GetIABooks - 3 yes - I don't have net
> ImageViewer - 10 yes
> Implode - 5 yes - slower than XO-1, keep error
> InfoSlicer - 5 yes
> IRC - 5 yes - I don't have net
> JigsawPuzzle - 7 yes
> JokeMachine - 10 yes
> Jukebox - 11 yes
> Labyrinth - 7 yes
> Log - 18 yes
> Maze - 6 yes
> Measure - 21 no -- failed to launch
> Memorize - 33 yes
> Moon - 10 yes
> Paint - 27 yes
> Physics - 2 yes
> Pippy - 34 yes - no module 'pippy'
> Poll - 22 yes
> Read - 68 yes
> ReadETexts - 17 yes - I don't have net
> Record - 64 yes - launched, but is not functional
> Scratch - 12 yes
> SliderPuzzle - 8 yes
> Speak - 11 yes
> StoryBuilder - 15 yes
> TamTamEdit - 51 yes
> TamTamJam - 52 yes
> TamTamMini - 51 yes
> TamTamSynthLab - 52 yes
> Terminal - 25 yes
> TurtleArt - 60 yes
> TuxPaint - 3 yes
> TypingTurtle - 16 yes - keep error
> ViewSlides - 10 yes
> Words - 4 yes
> Write - 63 yes
> ---
mikus
14 years, 7 months
os30 first impressions
by Mikus Grinbergs
Finally - the first new (non-F9) build that I've installed in over
nine months that can show "movies" for me !! [Though even on the
XO-1.5, YouTube remains "snapshotty" rather than "smooth".]
I'm still getting a feel for what this system will do. My "suite"
of multimedia applications works - and all of the 'memory-hogs' are
much much quicker than on the XO-1.
I noticed that this build does not even bother to define the msh0
interface. Also, my neighborhood view currently shows only me.
Noticed flakiness with the video. Others have already noted the
color bands during pretty boot. I also saw color areas while using
the (normally all black) text console (alt-ctl-F2). When using a
Frame icon's palette to 'Stop' a full-screen application, it looked
like a series of screen images (but smaller than the screen itself)
were being drawn as the previous session vanished. Some palette
opens/closes on some Frame icons cause a screen-wide blink.
All in all, a good system (with quirks).
mikus
14 years, 7 months
camera fail
by Yioryos Asprobounitis
I know this is not a question for this list but since most of the people have something to do with XO-1 are here, I will.
In an XO-1 self set I get:
camera pc@2
self test failed return code=-1
Indeed the camera light comes on but no image either in OFW or under linux. Reseted the EC and reinstalled firmware q2e41. No change.
Of course it could be just a hardware failure :(
But what intrigues me is that I noticed the failure just after I had booted from the DScard (Ubuntu) and was unpacking an initrd.gz (cpio -i). I got the usual permission denied in dev/device creation step and then went on.
Rebooting after that to f11/os7 from the NAND it failed at the loading the initrd.img step. This triggered the hardware test, where the camera problem was detected.
Everything else was OK,however booting kept failing.
Removing the SDcard allowed booting from the NAND!
After disassembling the XO to see for any obvious problems, reassembling, flashing the FW etc. it boots OK from the NAND and the SDcard but no camera.
Since I think that I remember having seen somewhere that the SDslot and the camera are somehow related, I'm hopping that the camera problem might be a software/firmware problem that could be fixed.
I would be grateful for any suggestions
If not, I guess I will not be testing camera function when is finally working in F11-XO1... (That's the connection with this list :-)
14 years, 7 months
os31 distribution directory files
by Mikus Grinbergs
http://dev.laptop.org/~cjb/f11-1.5/os31/ contains five large files.
I have trouble figuring out the WHY of providing all these files:
* os31.zd is input to 'fs-update' when using the XO OFW to install
the build to an SD card that will reside in the XO-1.5.
Clear enough.
* os31.img.gz is input to 'zcat' when using a Linux system to
install the build to an SD card that will reside in the XO-1.5.
Clear enough.
* os31.iso is input to 'livecd-iso-to-disk' when using a Fedora
system to install the build to a removable device.
The intent is clear, though I haven't tried with this file.
* os31.bootable.gz is input to 'zcat' when using a Linux system to
install the ("live") build to a removable device.
I think the intent is to save running the 'livecd-iso-to-disk'.
* os31.tree.tar.lzma is input to 'tar' when using a Linux system
to install the ("permanent"?)build to a removable device.
I hoped this method would let me keep the build on an USB stick.
But I did not understand why the content of this tarfile omitted
a 'vmlinuz' (in fact, the whole of '/boot' was omitted). Is
that a bug -- or can the XO-1.5 boot without needing 'vmlinuz' ?
mikus
14 years, 7 months
yum update crashes os7
by Yioryos Asprobounitis
Since I messed up my installation I re-downloaded os7 and after a yum update (with corrected repo files) updated 61 files including the olpc20091009 kernel and after restart it fail with a dracut problem.
The attached picture is from the XO screen (easier than describing it...:)
This is a problem I had seen using soas71xo too.
14 years, 7 months
Fw: yum update crashes os7
by Yioryos Asprobounitis
--- On Fri, 10/9/09, Yioryos Asprobounitis <mavrothal(a)yahoo.com> wrote:
> From: Yioryos Asprobounitis <mavrothal(a)yahoo.com>
> Subject: yum update crashes os7
> To: fedora-olpc-list(a)redhat.com
> Date: Friday, October 9, 2009, 5:55 PM
> Since I messed up my installation I
> re-downloaded os7 and after a yum update (with corrected
> repo files) updated 61 files including the olpc20091009
> kernel and after restart it fail with a dracut problem.
> The attached picture is from the XO screen (easier than
> describing it...:)
> This is a problem I had seen using soas71xo too.
>
On a fresh install updating first to dracut 002-9 and then the to kernel/headers 20091009...69c8c87 reproduces the problem.
Updating first the kernel and the dracut is OK !?!
>
>
14 years, 7 months
yum update crashes os7
by Mikus Grinbergs
> ... after a yum update ... and after restart it fail with a dracut problem.
I experienced the same thing. But the message (which your photo
captured) says to add 'selinux=0' to the kernel parameters (which
are supplied by the 'to boot-file' line in /boot/olpc.fth). I did
that - then booting worked the way it was supposed to.
mikus
14 years, 7 months
rpmbuild macro for libgcc.a location?
by Martin Langhoff
Working on an OLPC package (olpc-bios-crypto, which has a reasonable
chance of being upstreamable when it stabilizes)... we keep appending
-L lines to make it build in different releases / distros.
Is there an rpm macro that points to the location of libgcc.a? Or an
elegant way to get it? (While avoiding autoconf and the like...)
For example, for F11 I am adding: -L/usr/lib/gcc/i586-redhat-linux/4.4.1/
cheers,
martin
--
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
14 years, 7 months
Working on the XS F11 rebase
by Martin Langhoff
Working on...
Packages:
* idmgr - rebuilt
* usbmont
* pam_sotp -- help! doesn't build
* ds-backup
* ejabberd - rebuilt
** consider rebasing on 2.0.5, this will require remerging and
retesting @online@ patches
* fakeroot & fakechroot: F11 has current versions
* kernel-xs: we'll have to get XO-1 and XO-1.5 kernels and initrds...
* moodle-xs
* olpc-contents: (or equivalent for bitfrost libs)
* rssh - looks good on F11
* xs-activation
* xs-activity-server
* xs-config (lot of work to do!)
* xs-logos
* xs-pkgs: replace w groups (how? help!)
* xs-release (have an intermediate one?)
* xs-rsync
* xs-tools
* olpc-bios-crypto
* xs-otp
* xs-callhome
Plus:
* Get a usable installer build from revisor or pungi
* Test this thing!
You can track it on
http://wiki.laptop.org/index.php?title=User:Martinlanghoff/XS_F11_rebase_...
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
14 years, 7 months
XS - rebase on F-11, notes and RHF
by Martin Langhoff
So the F-9-based XS-0.6 is closed (at long last), and the next step is
to prep 0.7 based on F-11. Here is a rundown of the packaging /
installer work I think needs to be done:
=Rebuild packages, spec fixups=
Jerry Vonau has done a lot of the exploratory work, so mostly done I
think. Thanks! Still, might hit issues and cry for help...
=Switch from metapackage to 'groups'=
RFH: The repos I build have no 'groups' defined, and we need to
control livecdcreator/pungi and anaconda so that only the group (and
its deps) is included.
=Polish on the Anaconda / Installer=
- With the F11 buildsys tools maybe we can now replace fedora-logos properly.
- Anaconda on F11 seems to install from a bootable USB with less
crashes -- will want to streamline the process.
=Improve xs-config=
There are several ways in which xs-config can be a lot less intrusive,
for example using alternative init scripts (as we are doing with
'pgsql-xs' vs 'postgresql').
=FAQ=
Why F11? Because the XS needs to be stable, and doesn't need bleeding
edge, so targetting the "LTS" F11->RHEL6->CentOS path makes sense. The
XS team would like to spend more time working on "tools on top" and
less time tracking Fedora and regression-testing :-)
Why are these packages out of sync with Fedora (missing F-12, etc)?
The XS packages are still in flux and intrusive. And low-quality/risky
from a Fedora PoV. As things stabilize in the future it might make
sense to request inclusion.
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
14 years, 7 months