package review needed for olpc-kbdshim
by Paul Fox
i'd like to get olpc-kbdshim upstreamed so that more people can try it, etc.
https://bugzilla.redhat.com/show_bug.cgi?id=495902
if anyone can do me the honor of taking a look, and gently
telling me all that i've done wrong, or not at all, i'd
appreciate it.
(i'll be submitting olpc-powerd for review as well, but since
i've surely made the same mistakes in both, and olpc-kbdshim is
independent of olpc-powerd, i'm doing it first...)
thanks!
paul
=---------------------
paul fox, pgf(a)laptop.org
14 years, 11 months
Please update your Sugar packages for SoaS!
by Sebastian Dziallas
Hi all,
as we're quite quickly approaching the next release of SoaS, which is
scheduled for June 24, it would be great if you could update the Sugar
packages you maintain in Fedora to their latest versions.
The whole roadmap is listed on our wiki, where you can also find the
current version number of your package(s):
http://wiki.sugarlabs.org/go/Sugar_on_a_Stick/Roadmap#Packaging
In case you're unable to do the update, you can drop Steven (listed as
CC) an e-mail, who has kindly agreed to help, if needed.
Thanks a lot,
--Sebastian
14 years, 11 months
Daily builds are no longer livecd images
by Chris Ball
Hi,
Starting with today's 20090525 build, the images are no longer livecd
images, so changes will persist across reboots.
http://dev.laptop.org/~cjb/rawhide-xo/20090525/
(The sporadic "creating devices" mount hang will still be present for
jffs2; there's no need to report that again.)
Thanks to Sebastian for the script to make installed images!
- Chris.
--
Chris Ball <cjb(a)laptop.org>
14 years, 11 months
Re: Daily builds are no longer livecd images
by Mikus Grinbergs
>> On the USB stick, in the file '/boot/olpc.fth' (generated
>> by 'livecd-iso-to-disk'), the line that sets up the boot
>> parameters specifies: 'reset_overlay'.
>>
>> What does 'reset_overlay' as a parameter do ? Should it be
>> there ?
>
> That would re-create the "/LiveOS/overlay-LIVE-AA00-0383" file, thus
> wiping out the changes made prior to the reboot. I'd remove that from
> the olpc.fth file.
Thank you, thank you.
Finally, I'm able to see that changes will "persist" after the
reboot of an XO, which was booted off an USB stick.
It was a long struggle to get this working - but with the help of
the participants on the fedora-olpc-list it ended successfully.
Thanks: Chris, Mathieu, Jerry, everyone.
mikus
14 years, 11 months
Re: Daily builds are no longer livecd images
by Mikus Grinbergs
> When you use livecd-iso-to-disk to burn a liveUSB, you get a read-only
> system on the USB stick.
>
> However, if you use the "--overlay-size-mb <size>" to the
> livecd-iso-to-disk script, it will create a unionfs persistent storage
> of <size> Mega Bytes _on the same USB stick_.
Thank you.
I added the "--overlay-size-mb <size>" to the script invocation, so
it now is: 'livecd-iso-to-disk.sh --format --overlay-size-mb 600
--xo --xo-no-home /media/disk/20090519.iso /dev/sdf1'. That caused
additional file '/LiveOS/overlay-LIVE-AA00-0383' to be allocated on
the USB stick when its content was being built.
[But note that when I run 'livecd-iso-to-disk' on my Ubuntu 9.04
(Jaunty) system (with latest kernel released by Ubuntu), I'm still
getting the error: "running kernel cannot mount the squashfs from
the ISO file to extract it. The compressed squashfs will be copied
to the USB stick."]
When I booted the XO using that USB stick; made system changes;
shutdown; powered off; rebooted with the USB stick -- the changes
I had made had "evaporated".
----
What can I do to make my changes "persistent" when booting an XO
from an USB stick ? [It is not realistic for me to acquire a Fedora
desktop system to run 'livecd-iso-to-disk'.]
Thanks, mikus
p.s. On the USB stick, in the file '/boot/olpc.fth' (generated
by 'livecd-iso-to-disk'), the line that sets up the boot
parameters specifies: 'reset_overlay'.
What does 'reset_overlay' as a parameter do ? Should it be
there ?
14 years, 11 months
Re: rawhide-xo 20090528
by Mikus Grinbergs
>>> When you press the Fn key + End (right
>>> arrow) in Pippy/Terminal/etc., do you also get an equals sign
>>> character inserted in the text before <End> gets activated?
>
> Are you saying it happened before the Frame key started working?
Yes. If I remember correctly, this has happened with every
rawhide-xo build ever released. [It also happens with Soas2.]
mikus
14 years, 11 months
Re: rawhide-xo 20090528
by Mikus Grinbergs
> When you press the Fn key + End (right
> arrow) in Pippy/Terminal/etc., do you also get an equals sign
> character inserted in the text before <End> gets activated?
Just tried it with rawhide-xo 20090528.iso (installed on nand):
Pressing the Fn key generates an '=' character at the text cursor.
[I normally use an external USB keyboard with my XO, to avoid this
unwanted Fn key behavior.]
mikus
14 years, 11 months
rawhide-xo 20090528
by Mikus Grinbergs
Using 'copy-nand', flashed ~cjb/rawhide-xo 20090528.img to XO nand.
My experience with rawhide-xo 20090528 matches that with 20090525.
One significant fix that first showed up in 20090525 is that the
OLPC keyboard (e.g., the Frame key) is now being recognized.
One problem that showed up in 20090525 is that Sugar does not pick
up on the 'Desktop' font size specification set within Gnome. The
result is that labels (e.g., in My Settings) are now really tiny.
A bigger problem, which I first noticed with 20090525, is that
Neighborhood View is empty (except for the 'me' icon in the middle).
[In contrast, my rawhide-xo 20090519 system's Neighborhood View
shows both existing wireless access points and existing wired XOs.]
mikus
14 years, 11 months
Re: rawhide-xo 20090528
by Mikus Grinbergs
> In Soas we are forcing a sane dpi for the XO by using a .Xresources
> file. When I last looked into this, I think it pointed to the graphics
> driver.
Ran 'livecd-iso-to-disk' with Soas2-200905241902.iso to create a
bootable USB stick. Then booted my XO from that stick.
The labels in 'My Settings' using Soas2-20090524 are equally tiny as
those same labels using rawhide-xo 20090528. So is the default text
in 'Terminal' (in Sugar).
mikus
14 years, 11 months
Re: Daily builds are no longer livecd images
by Mikus Grinbergs
> > What does "no longer livecd images" mean ?
>
> On previous builds, changes to the root filesystem disappeared at
> reboot because the filesystem was refreshed from the same image
> every boot. This no longer happens, so if you (for example):
>
> # touch /foo
> # touch /etc/bar
> # reboot
>
> The files will still be there after reboot.
I *still* do not understand why that should be so.
The only machines available for me to experiment with are XO-1s.
The above-described scenario does NOT work for me.
--------
I did the zcat 20090525.bootable.gz > /dev/sdf1 (USB stick).
That USB stick failed to boot on the XO. The messages from OFW were
"Error: Unknown file system Can't open disk label package"
Then I did the livecd-iso-to-disk.sh 20090525.iso > /dev/sdf1 (USB
stick). That USB stick booted fine on the XO. Made some changes to
the root filesystem, and rebooted. After the XO had completed
rebooting (in the process, it reloaded its root filesystem from the
USB stick), the changes I had previously made were NOT there.
--------
I can understand how changes made to the "recording medium" will be
there after a reboot. [For instance, if I boot from nand, then make
changes to the filesystem in memory (and the system writes those
changed memory pages back out to nand), then when I reboot (from
nand) the changes will still be there.]
But in the case of booting from an USB stick, I believe the system
does *not* write the contents of changed memory pages back out to
the USB stick. When I reboot from that USB stick (particularly if
I've powered-down the system in the meantime), why would the changes
still be there ??
Thanks, mikus
14 years, 11 months
