From dsd at laptop.org Tue Sep 1 02:59:48 2009 From: dsd at laptop.org (Daniel Drake) Date: Tue, 1 Sep 2009 08:44:48 +0545 Subject: [Sugar-devel] F11 for XO1 - Fonts In-Reply-To: References: <199720.21214.qm@web65512.mail.ac4.yahoo.com> <818423da0908170317l13ec9cb8ia54003c8164b4ba4@mail.gmail.com> <82891173EED448FF82B23C8CA6F1F484@Art> <818423da0908170822s318304a2h20788f673aaed55d@mail.gmail.com> <46a038f90908180316l34d604dbh20121387060ee196@mail.gmail.com> <46a038f90908180338i5d4ec25fq6a22c30850c296d4@mail.gmail.com> <818423da0908180348i2aa9a8cfx1b5dd36ed278108f@mail.gmail.com> <818423da0908181019n585a3dc0q5a3bb6b21756ac0b@mail.gmail.com> Message-ID: <818423da0908311959o13b37712ua1d37b528e19e7cd@mail.gmail.com> 2009/9/1 Art Hunkins : > I've developed a way to handle fonts both on the XO-1 and on SoaS that fits > text nicely, on fixed pages, to all-sized screens. It seems to me like you have this working on 2 screen sizes, but it certainly won't apply to them all. You seem to make assumptions like that if 50 characters at a specific font size can fit on a screen that is 600 pixels wide, then 100 characters will fit on a screen that is 1200 pixels wide. And that's not how displays and font sizes work. The number of lines that can fit on a screen (at a certain font size) does not depend on the aspect ratio, it depends on the physical size of the screen. The correct way to do this is to render the fonts and measure the resultant number of pixels occupied by them, then dynamically adjust. You can discover the approximate size of a character of a font (in pixels) to seed the process. Pango provides you all you need to do this. Daniel From cjb at laptop.org Wed Sep 2 05:23:15 2009 From: cjb at laptop.org (Chris Ball) Date: Wed, 2 Sep 2009 01:23:15 -0400 (EDT) Subject: New F11 for XO-1.5 build 27 Message-ID: <20090902052315.06A45FAB12@dev.laptop.org> http://wiki.laptop.org/go/F11_for_1.5 http://dev.laptop.org/~cjb/f11-1.5/os27 Compressed image size: 375.71mb (-1.62mb since build 26) Description of changes in this build: * New kernel with DCON improvements from Paul Fox * Add / to automatic fsck list in fstab Package changes since build 26: -DeviceKit-power-009-1.fc11.i586 +DeviceKit-power-010-0.3.20090810git.fc11.i586 +atlas-sse-3.8.3-4.fc11.i586 -atlas-sse-3.8.3-7.fc11.i586 -bash-4.0-7.fc11.i586 +bash-4.0-8.fc11.i586 -checkpolicy-2.0.19-2.fc11.i586 -cups-libs-1.4-0.rc1.14.fc11.i586 +cups-libs-1.4-0.rc1.15.fc11.i586 -curl-7.19.4-9.fc11.i586 +curl-7.19.6-1.fc11.i586 +dash-0.5.5.1-2.fc11.i586 -dhclient-4.1.0p1-1.fc11.i586 +dhclient-4.1.0p1-4.fc11.i586 -diffutils-2.8.1-23.fc11.i586 -dracut-0.7-1.fc11.i586 +dracut-0.9-2.fc11.i586 -etoys-4.0.2212-1.fc11.noarch +etoys-4.0.2247-1.fc11.noarch -farsight2-0.0.12-1.fc11.i586 +farsight2-0.0.14-1.fc11.i586 -fontconfig-2.6.99.behdad.20090508-1.fc11.i586 +fontconfig-2.7.1-1.fc11.i586 -glib2-2.20.4-1.fc11.i586 +glib2-2.20.5-1.fc11.i586 -glibc-2.10.1-4.i686 +glibc-2.10.1-5.i686 -glibc-common-2.10.1-4.i586 +glibc-common-2.10.1-5.i586 -gnome-power-manager-2.26.4-1.fc11.i586 +gnome-power-manager-2.26.4-3.fc11.i586 -gnome-settings-daemon-2.26.1-8.fc11.i586 +gnome-settings-daemon-2.26.1-9.fc11.i586 -gnutls-2.6.6-1.fc11.i586 +gnutls-2.6.6-2.fc11.i586 -gstreamer-plugins-base-0.10.23-3.fc11.i586 +gstreamer-plugins-base-0.10.24-1.fc11.i586 -gstreamer-python-0.10.15-1.fc11.i586 +gstreamer-python-0.10.16-1.fc11.i586 -gtk2-2.16.5-1.fc11.i586 +gtk2-2.16.6-1.fc11.i586 -gupnp-igd-0.1.1-3.fc11.i586 +gupnp-igd-0.1.3-3.fc11.i586 +gvfs-1.2.3-12.fc11.i586 -gvfs-1.2.3-9.fc11.i586 +gvfs-fuse-1.2.3-12.fc11.i586 -gvfs-fuse-1.2.3-9.fc11.i586 -hal-0.5.12-28.20090226git.fc11.i586 +hal-0.5.12-29.20090226git.fc11.i586 -hal-libs-0.5.12-28.20090226git.fc11.i586 +hal-libs-0.5.12-29.20090226git.fc11.i586 -kernel-2.6.30_xo1.5-20090806.0016.1.olpc.1a4850b.i586 +kernel-2.6.30_xo1.5-20090827.1247.1.olpc.9e5aad8.i586 -kernel-firmware-2.6.30_xo1.5-20090806.0016.1.olpc.1a4850b.i586 +kernel-firmware-2.6.30_xo1.5-20090827.1247.1.olpc.9e5aad8.i586 -libcurl-7.19.4-9.fc11.i586 +libcurl-7.19.6-1.fc11.i586 -libmikmod-3.2.0-4.beta2.fc11.i586 +libmikmod-3.2.0-5.beta2.fc11.i586 -libnice-0.0.6-1.fc11.i586 +libnice-0.0.9-1.fc11.i586 -libpurple-2.5.8-2.fc11.i586 +libpurple-2.6.1-1.fc11.i586 -libselinux-utils-2.0.80-1.fc11.i586 -libsemanage-2.0.31-4.fc11.i586 -libvorbis-1.2.0-7.fc11.i586 +libvorbis-1.2.0-8.fc11.i586 -libxml2-2.7.3-2.fc11.i586 +libxml2-2.7.3-3.fc11.i586 -libxml2-python-2.7.3-2.fc11.i586 +libxml2-python-2.7.3-3.fc11.i586 +lyx-cmex10-fonts-1.6.4-1.fc11.noarch +lyx-cmmi10-fonts-1.6.4-1.fc11.noarch +lyx-cmr10-fonts-1.6.4-1.fc11.noarch +lyx-cmsy10-fonts-1.6.4-1.fc11.noarch +lyx-esint10-fonts-1.6.4-1.fc11.noarch +lyx-eufm10-fonts-1.6.4-1.fc11.noarch +lyx-fonts-common-1.6.4-1.fc11.noarch +lyx-fonts-compat-1.6.4-1.fc11.noarch +lyx-msam10-fonts-1.6.4-1.fc11.noarch +lyx-msbm10-fonts-1.6.4-1.fc11.noarch +lyx-wasy10-fonts-1.6.4-1.fc11.noarch -mathml-fonts-1.0-23.fc11.noarch -net-tools-1.60-92.fc11.i586 +net-tools-1.60-93.fc11.i586 -nscd-2.10.1-4.i586 +nscd-2.10.1-5.i586 -nss-3.12.3.99.3-2.11.3.fc11.i586 +nss-3.12.3.99.3-2.11.4.fc11.i586 -nss-softokn-freebl-3.12.3.99.3-2.11.3.fc11.i586 +nss-softokn-freebl-3.12.3.99.3-2.11.4.fc11.i586 -nss_ldap-264-2.fc11.i586 +nss_ldap-264-6.fc11.i586 -policycoreutils-2.0.62-12.12.fc11.i586 -pygtk2-2.14.1-1.fc11.i586 +pygtk2-2.14.1-2.fc11.i586 -readahead-1.4.9-1.fc11.i586 +readahead-1.5.0-1.fc11.i586 -sos-1.8-11.fc11.noarch +sos-1.8-14.fc11.noarch -telepathy-gabble-0.7.26-1.fc11.i586 +telepathy-gabble-0.7.26-2.fc11.i586 -telepathy-haze-0.3.0-1.fc11.i586 +telepathy-haze-0.3.1-1.fc11.i586 -totem-2.26.3-1.fc11.i586 +totem-2.26.3-3.fc11.i586 -totem-gstreamer-2.26.3-1.fc11.i586 +totem-gstreamer-2.26.3-3.fc11.i586 -totem-mozplugin-2.26.3-1.fc11.i586 +totem-mozplugin-2.26.3-3.fc11.i586 -tzdata-2009k-1.fc11.noarch +tzdata-2009k-2.fc11.noarch -ustr-1.0.4-8.fc11.i586 -xorg-x11-drv-evdev-2.2.4-1.fc11.i586 +xorg-x11-drv-evdev-2.2.5-1.fc11.i586 -xorg-x11-server-Xorg-1.6.2-3.fc11.i586 +xorg-x11-server-Xorg-1.6.3-4.fc11.i586 -xorg-x11-server-common-1.6.2-3.fc11.i586 +xorg-x11-server-common-1.6.3-4.fc11.i586 -xz-4.999.8-0.7.beta.fc11.i586 +xz-4.999.8-0.8.beta.20090817git.fc11.i586 -xz-libs-4.999.8-0.7.beta.fc11.i586 +xz-libs-4.999.8-0.8.beta.20090817git.fc11.i586 -xz-lzma-compat-4.999.8-0.7.beta.fc11.i586 +xz-lzma-compat-4.999.8-0.8.beta.20090817git.fc11.i586 From sebastian at when.com Wed Sep 2 18:37:40 2009 From: sebastian at when.com (Sebastian Dziallas) Date: Wed, 02 Sep 2009 20:37:40 +0200 Subject: Next Test Day: Sugar on a Stick [Tomorrow] Message-ID: <4A9EBB74.5060105@when.com> Greetings, sorry for the late notice and the cross-post. This test day will focus on Sugar Labs' Sugar on a Stick, a downstream project based on Fedora. Sugar on a Stick has launched it's first version codenamed "Strawberry" successfully in June and has recently announced the beta release of its next version. It contains basically a slightly modified version of the Sugar Desktop on a Fedora System, prepared to be deployed on USB keys. The test cases have been developed with the goal in mind to be of value for both projects, Sugar Labs and the Fedora Project. The latter one will especially profit from a better integration of the aforementioned desktop, as well as the testing of the LiveUSB technology. Additionally, new features like the rebootless live installer, which has been discussed before (and been included in Fedora lately) are also ready for testing. We invite you to jump in #fedora-test-day tomorrow, September 3, and to join the fun! More concrete information can be found in the wiki: https://fedoraproject.org/wiki/Test_Day:2009-09-03_SoaS Thanks, --Sebastian From cjb at laptop.org Wed Sep 2 22:41:13 2009 From: cjb at laptop.org (Chris Ball) Date: Wed, 2 Sep 2009 18:41:13 -0400 (EDT) Subject: New F11 for XO-1.5 build 28 Message-ID: <20090902224113.DE88FFAB12@dev.laptop.org> http://wiki.laptop.org/go/F11_for_1.5 http://dev.laptop.org/~cjb/f11-1.5/os28 Compressed image size: 375.66mb (-0.06mb since build 27) Description of changes in this build: * boot OFW's last: device, which resolves to the device that booted olpc.fth. Package changes since build 27: -fontconfig-2.7.1-1.fc11.i586 +fontconfig-2.7.2-1.fc11.i586 -libv4l-0.6.0-1.fc11.i586 +libv4l-0.6.1-1.fc11.i586 From mikus at bga.com Thu Sep 3 01:27:11 2009 From: mikus at bga.com (Mikus Grinbergs) Date: Wed, 02 Sep 2009 21:27:11 -0400 Subject: Next Test Day: Sugar on a Stick [Tomorrow] Message-ID: <4A9F1B6F.2060002@bga.com> Booted an XO-1 into soas-2-beta (from USB stick). Had the usual "SoaS3" problem making it ready for me (I use __Terminal__ for most of what I do): Initially, boot got as far as Home View - but the ring did not include Terminal. When I clicked on the upper right image to switch to Home List view (where I would have been able to click on Terminal's icon), Sugar vanished. Used the text console to modify 'favorite_activities' to put Terminal into the ring, and tried again. Once I was able to use Terminal, clicked in Home View on some Activities: Browse (launched); Speak (launched, no sound); Record (did not launch). Tried to change the timezone in 'My Settings' - Sugar vanished. To me, soas-2-beta on the XO-1 seems less stable than earlier SoaS3. Because I am currently not interested in checking out F12-on-XO1, I did not do any further testing with soas-2-beta. mikus From mavrothal at yahoo.com Mon Sep 7 22:30:28 2009 From: mavrothal at yahoo.com (Yioryos Asprobounitis) Date: Mon, 7 Sep 2009 15:30:28 -0700 (PDT) Subject: gcc for f11-xo/os6 Message-ID: <733352.66840.qm@web65509.mail.ac4.yahoo.com> I tried to install some modules in the f11-xo/os6 kernel in an XO-1. However, after I got the olpc-20090806 kernel-src, kernel-headers, kernel-devel etc I can not install gcc because glibc-headers and glibc-devel require glibc 2.10.1-4 while the installed is 2.10.1-5! Is that a yum problem or should I be activating some other repos? Should I just get the rpms and force install or will brake the system? thx From pbrobinson at gmail.com Mon Sep 7 22:32:24 2009 From: pbrobinson at gmail.com (Peter Robinson) Date: Mon, 7 Sep 2009 23:32:24 +0100 Subject: gcc for f11-xo/os6 In-Reply-To: <733352.66840.qm@web65509.mail.ac4.yahoo.com> References: <733352.66840.qm@web65509.mail.ac4.yahoo.com> Message-ID: <5256d0b0909071532s6527b7ddvb6958be166481295@mail.gmail.com> On Mon, Sep 7, 2009 at 11:30 PM, Yioryos Asprobounitis wrote: > I tried to install some modules in the f11-xo/os6 kernel in an XO-1. However, after I got the olpc-20090806 kernel-src, kernel-headers, kernel-devel etc I can not install gcc because glibc-headers and glibc-devel require glibc 2.10.1-4 while the installed is 2.10.1-5! > Is that a yum problem or should I be activating some other repos? > Should I just get the rpms and force install or will brake the system? You probably need to enable fedora-updates (might already be enabled) and fedora-updates-testing. Peter From mavrothal at yahoo.com Tue Sep 8 09:05:44 2009 From: mavrothal at yahoo.com (Yioryos Asprobounitis) Date: Tue, 8 Sep 2009 02:05:44 -0700 (PDT) Subject: gcc for f11-xo/os6 In-Reply-To: <5256d0b0909071532s6527b7ddvb6958be166481295@mail.gmail.com> Message-ID: <432297.82262.qm@web65516.mail.ac4.yahoo.com> --- On Mon, 9/7/09, Peter Robinson wrote: > From: Peter Robinson > Subject: Re: gcc for f11-xo/os6 > To: "Yioryos Asprobounitis" > Cc: fedora-olpc-list at redhat.com > Date: Monday, September 7, 2009, 6:32 PM > On Mon, Sep 7, 2009 at 11:30 PM, > Yioryos > Asprobounitis > wrote: > > I tried to install some modules in the f11-xo/os6 > kernel in an XO-1. However, after I got the olpc-20090806 > kernel-src, kernel-headers, kernel-devel etc I can not > install gcc because glibc-headers and glibc-devel require > glibc 2.10.1-4 while the installed is 2.10.1-5! > > Is that a yum problem or should I be activating some > other repos? > > Should I just get the rpms and force install or will > brake the system? > > You probably need to enable fedora-updates (might already > be enabled) > and fedora-updates-testing. > Thanks Apparently the build is using "update-testing" but the repo was not activated. That did it. > Peter > From mikus at bga.com Tue Sep 8 14:54:47 2009 From: mikus at bga.com (Mikus Grinbergs) Date: Tue, 08 Sep 2009 10:54:47 -0400 Subject: yum not accessing repository when running F12-on-XO1 Message-ID: <4AA67037.10804@bga.com> Running on XO-1 with build soas-2-beta (booted from USB stick). For several days now, 'yum' is timing out with the message: "Error: Cannot retrieve repository metadata (repmod.xml) for repository: fedora. Please verify its path and try again." Is the Fedora-12 repository having serious downtime problems, or is this something wrong with yum ? [I experience no problem with 'yum' accessing the Fedora-11 repository when running F11-on-XO1 builds.] mikus From pbrobinson at gmail.com Tue Sep 8 15:58:31 2009 From: pbrobinson at gmail.com (Peter Robinson) Date: Tue, 8 Sep 2009 16:58:31 +0100 Subject: yum not accessing repository when running F12-on-XO1 In-Reply-To: <4AA67037.10804@bga.com> References: <4AA67037.10804@bga.com> Message-ID: <5256d0b0909080858s1739a44ep43f1b6a71a95f8e2@mail.gmail.com> On Tue, Sep 8, 2009 at 3:54 PM, Mikus Grinbergs wrote: > Running on XO-1 with build soas-2-beta (booted from USB stick). > > For several days now, 'yum' is timing ?out with the message: "Error: Cannot > retrieve repository metadata (repmod.xml) for repository: fedora. Please > verify its path and try again." > > Is the Fedora-12 repository having serious downtime problems, or is this > something wrong with yum ? ?[I experience no problem with 'yum' accessing > the Fedora-11 repository when running F11-on-XO1 builds.] Generally there's no issues with the Fedora 12 repos at the moment. Is it trying to connect to the same mirror each time. It could be issues with a particular mirror. Regards, Peter From cjb at laptop.org Tue Sep 8 22:37:43 2009 From: cjb at laptop.org (Chris Ball) Date: Tue, 8 Sep 2009 18:37:43 -0400 (EDT) Subject: New F11 for XO-1.5 build 29 Message-ID: <20090908223743.84F91FAB13@dev.laptop.org> http://wiki.laptop.org/go/F11_for_1.5 http://dev.laptop.org/~cjb/f11-1.5/os29 Compressed image size: 379.72mb (+4.06mb since build 28) Description of changes in this build: * Switch to ext4 for the root filesystem. We don't know if our SD will handle an ext4 journal without damaging itself, but we suspect it might, and it's a good time to find out. Package changes since build 28: -alsa-lib-1.0.20-1.fc11.i586 +alsa-lib-1.0.21-1.fc11.i586 -alsa-utils-1.0.20-3.fc11.i586 +alsa-utils-1.0.21-1.fc11.i586 +csound-5.10.1-12.fc11.i586 -csound-5.10.1-9.fc11.i586 -etoys-4.0.2247-1.fc11.noarch +etoys-4.0.2258-1.fc11.noarch -gtk2-2.16.6-1.fc11.i586 +gtk2-2.16.6-2.fc11.i586 -kernel-2.6.30_xo1.5-20090827.1247.1.olpc.9e5aad8.i586 +kernel-2.6.30_xo1.5-20090908.1416.1.olpc.d1b0c02.i586 -kernel-firmware-2.6.30_xo1.5-20090827.1247.1.olpc.9e5aad8.i586 +kernel-firmware-2.6.30_xo1.5-20090908.1416.1.olpc.d1b0c02.i586 -libXext-1.0.99.1-2.fc11.i586 +libXext-1.0.99.1-3.fc11.i586 +libcap-ng-0.6.1-1.fc11.i586 -libpurple-2.6.1-1.fc11.i586 +libpurple-2.6.2-1.fc11.i586 -libsilc-1.1.8-5.fc11.i586 +libsilc-1.1.8-7.fc11.i586 -olpc-bootanim-2.5-1.i586 +olpc-bootanim-2.7-1.fc11.i586 -openldap-2.4.15-3.fc11.i586 +openldap-2.4.15-5.fc11.i586 -pciutils-3.1.3-1.fc11.i586 +pciutils-3.1.4-2.fc11.i586 -pciutils-libs-3.1.3-1.fc11.i586 +pciutils-libs-3.1.4-2.fc11.i586 -pulseaudio-libs-0.9.15-14.fc11.i586 +pulseaudio-libs-0.9.15-17.fc11.i586 -pulseaudio-libs-glib2-0.9.15-14.fc11.i586 +pulseaudio-libs-glib2-0.9.15-17.fc11.i586 -smartmontools-5.38-11.fc11.i586 +smartmontools-5.38-13.fc11.i586 -xapian-bindings-python-1.0.14-1.fc11.i586 +xapian-bindings-python-1.0.15-1.fc11.i586 -xapian-core-libs-1.0.14-2.fc11.i586 +xapian-core-libs-1.0.15-1.fc11.i586 +xorg-x11-server-utils-7.4-7.1.fc11.i586 -xorg-x11-server-utils-7.4-7.fc11.i586 -yum-3.2.23-3.fc11.noarch +yum-3.2.24-1.fc11.noarch From pbrobinson at gmail.com Wed Sep 9 12:27:32 2009 From: pbrobinson at gmail.com (Peter Robinson) Date: Wed, 9 Sep 2009 13:27:32 +0100 Subject: yum not accessing repository when running F12-on-XO1 In-Reply-To: <4AA78DAF.9000702@bga.com> References: <4AA78DAF.9000702@bga.com> Message-ID: <5256d0b0909090527p70aaeac1tb30c79eaf1efe2df@mail.gmail.com> On Wed, Sep 9, 2009 at 12:12 PM, Mikus Grinbergs wrote: > I'm going to assume my F12-on-XO1 yum problem was non-reproducible. > > I did a 'yum clean all', plus manually going into /var and removing things > whose names started with "yum". ?After that, I was able to use the customary > 'yum' commands with F12-on-XO1. I've not seen any issues. You probably shouldn't remove all yum directories within /var/. A 'yum clean all' is all I've ever needed to do. The only directory you might wish to clean up is /var/cache/yum. >> Is it trying to connect to the same mirror each time. >> It could be issues with a particular mirror. > > Your answer is what motivated me to try to start over with a "clean slate". > > The catch is - I had no information whatever about what mirror it was trying > to contact - no output from yum except for "could not retrieve". ?In my > experience, when there is a problem with a mirror, yum eventually outputs a > line identifying the mirror - nothing like that occurred here. ?[I suppose I > could have captured whatever packets it tried to send, and tried to figure > out what it was doing by looking at their content - but that's a *lot* of > effort.] I normally get the following: [root at neo ~]# yum update Loaded plugins: dellsysidplugin2, fastestmirror, presto, refresh-packagekit Determining fastest mirrors fedora/metalink | 28 kB 00:00 fedora-debuginfo/metalink | 21 kB 00:00 updates/metalink | 14 kB 00:00 updates-debuginfo/metalink | 8.1 kB 00:00 updates-testing/metalink | 7.9 kB 00:00 updates-testing-debuginfo/metalink | 6.6 kB 00:00 * fedora: mirror.sov.uk.goscomb.net * fedora-debuginfo: mirror.sov.uk.goscomb.net * rpmfusion-free: download1.rpmfusion.org * rpmfusion-free-updates: download1.rpmfusion.org * rpmfusion-free-updates-testing: download1.rpmfusion.org * updates: mirror.sov.uk.goscomb.net * updates-debuginfo: mirror.sov.uk.goscomb.net * updates-testing: mirror.sov.uk.goscomb.net * updates-testing-debuginfo: mirror.sov.uk.goscomb.net But that might be from the fastest mirror's plugin I use. 'yum install yum-plugin-fastestmirror' -> I highly recommend it. > [ I looked in /etc/yum.repos.d/ - but the entries there specify values such > as $releasever - so I don't even know which *list* of mirrors it was trying > to use (typing 'echo $releasever' showed me blanks). ?And looking at > https://mirrors.fedoraproject.org with a browser showed me human-readable > lists rather than what I imagined yum would be using. ] $releasever is the Fedora release and its a variable inside rpm/yum so you'll never get anything from the command line. The bit your interested in is: #baseurl=http://download.fedoraproject.org/pub/fedora/linux/releases/$releasever/Everything/$basearch/os/ mirrorlist=https://mirrors.fedoraproject.org/metalink?repo=fedora-$releasever&arch=$basearch The baseurl option (commented out in a default install) only references a single site ever (not recommended) the mirrorlist option tells yum to retrieve a list of mirrors from the URL. >> Generally there's no issues with the Fedora 12 repos at the moment. > > Again, I don't know if there is an issue at the Fedora end (i.e., "what is > there"), or in how my end is asking (this was with build soas-2-beta) - but > many many of the things I try to fetch with yum on F12-on-XO1 tell me "no > package xxx available - nothing to do". With F11-on-XO1, such packages > (vsftpd) *are* in the Fedora repos. I have no idea how the repos in SoaS-2 are configured but there is no problem with Fedora repo's at the moment. SoaS-2 should be just using default Fedora repos. Peter From todd at webpath.net Wed Sep 9 15:28:04 2009 From: todd at webpath.net (Todd Robinson) Date: Wed, 09 Sep 2009 11:28:04 -0400 Subject: Fedora 10 unable to boot after updating XO-1 to 8.2.0 In-Reply-To: <5256d0b0909080858s1739a44ep43f1b6a71a95f8e2@mail.gmail.com> References: <4AA67037.10804@bga.com> <5256d0b0909080858s1739a44ep43f1b6a71a95f8e2@mail.gmail.com> Message-ID: <4AA7C984.2060306@webpath.net> As some of you may know, we (On-Disk.com) do the Fedora 10 SD cards which are currently available for the XO-1, but which we will need to discontinue. Currently the Fedora 10 SD cards no longer work after updating to 8.2.0 (OpenFirmware CL1 Q2E41 Q2E). When inserting the SD card it acts as if it's not inserted, except that it also doesn't attempt to boot Sugar. I suspect the olpc.fth is used a bit differently with the newer firmware version. For informational purposes, the Fedora 10 SD cards work fine under older XO-1 firmware. The XOs also boot Xtra Ordinary fine after updating to 8.2.0 but do not work with older firmware versions. (see: http://on-disk.com/product_info.php/products_id/881 - should be an article tomorrow at OLPC News). I would love to be able to offer a Fedora 11 option, but from tracking this list there doesn't seem to be a version ready for public consumption (please correct me if I'm wrong). So this gives me three choices: 1. discontinue offering Fedora 10 on SD cards for the XO-1 and rely upon non-fedora XO options such as Xtra Ordinary and DebXO which run fine with the newer 8.2.0 os/firmware. 2. Continue to offer it, but warn that it must be used with older Firmware versions. (I would actually rather just discontinue it) 3. Find a fix to allow F10 to boot on the newer os/firmware. Any advice or work-arounds anyone may have would be very much appreciated. I'll append the Fedora 10 /boot/olpc.fth in case it's helpful. Thank you, Todd - - - - - - - - - - - - - - \ Boot script for USB boot hex rom-pa fffc7 + 4 $number drop h# 2e19 < [if] patch 2drop erase claim-params : high-ramdisk ( -- ) cv-load-ramdisk h# 22c +lp l@ 1+ memory-limit umin /ramdisk - ffff.f000 and ( new-ramdisk-adr ) ramdisk-adr over /ramdisk move ( new-ramdisk-adr ) to ramdisk-adr ; ' high-ramdisk to load-ramdisk [then] : set-bootpath-dev ( -- ) " /chosen" find-package if ( phandle ) " bootpath" rot get-package-property 0= if ( propval$ ) get-encoded-string ( bootpath$ ) [char] \ left-parse-string 2nip ( dn$ ) dn-buf place ( ) then then " /sd" dn-buf count sindex 0>= if " sd:" else " u:" then " BOOTPATHDEV" $set-macro ; set-bootpath-dev " root=UUID=4C67-D0F1 rootfstype=vfat rw liveimg overlay=UUID=4C67-D0F1 quiet rhgb persistenthome=mtd0 reset_overlay" to boot-file " ${BOOTPATHDEV}\syslinux\initrd0.img" expand$ to ramdisk " ${BOOTPATHDEV}\syslinux\vmlinuz0" expand$ to boot-device unfreeze boot From sebastian at when.com Wed Sep 9 19:29:51 2009 From: sebastian at when.com (Sebastian Dziallas) Date: Wed, 09 Sep 2009 21:29:51 +0200 Subject: Getting a SoaS Docs Effort off the Ground Message-ID: <4AA8022F.20507@when.com> From looking at the currently available documentation for Sugar on a Stick, I think it makes sense to collaborate on writing well written official instructions for it. So I've entered a Blueprint in Launchpad on it: https://blueprints.launchpad.net/soas/+spec/better-docs-for-soas I'd like to give the great Fedora Publican tool a try, as it has recently seen a new beta release. I have set up a new GIT repo in Gitorious, which lives here: http://git.sugarlabs.org/projects/soas-docs So if you're interested in writing the next generation of totally awesomeness-spreading SoaS docs, please speak up! :) ...you can even add yourself already to the Launchpad page and apply for commit access to the GIT repo, too. --Sebastian From kwade at redhat.com Thu Sep 10 01:18:32 2009 From: kwade at redhat.com (Karsten Wade) Date: Wed, 9 Sep 2009 18:18:32 -0700 Subject: Getting a SoaS Docs Effort off the Ground In-Reply-To: <4AA8022F.20507@when.com> References: <4AA8022F.20507@when.com> Message-ID: <20090910011832.GH4413@calliope.phig.org> On Wed, Sep 09, 2009 at 09:29:51PM +0200, Sebastian Dziallas wrote: > From looking at the currently available documentation for Sugar on a > Stick, I think it makes sense to collaborate on writing well written > official instructions for it. So I've entered a Blueprint in Launchpad > on it: https://blueprints.launchpad.net/soas/+spec/better-docs-for-soas > > I'd like to give the great Fedora Publican tool a try, as it has > recently seen a new beta release. I have set up a new GIT repo in > Gitorious, which lives here: http://git.sugarlabs.org/projects/soas-docs > > So if you're interested in writing the next generation of totally > awesomeness-spreading SoaS docs, please speak up! :) ...you can even add > yourself already to the Launchpad page and apply for commit access to > the GIT repo, too. Not to throw yet-another-tool out there, but have you looked at FLOSSManuals.net? There is an existing culture of using this tool for Sugar/OLPC docs, so you can make it easier for those folks to participate. Remixing content is possibly easier, too. Our experience in Fedora Docs is that you get 10x to 20x more participants if you use a wiki-like tool than DocBook XML (that hasn't had a viable wysiwyg editor.) - Karsten -- Karsten 'quaid' Wade, Community Gardener http://quaid.fedorapeople.org AD0E0C41 -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From quozl at laptop.org Thu Sep 10 03:16:31 2009 From: quozl at laptop.org (James Cameron) Date: Thu, 10 Sep 2009 13:16:31 +1000 Subject: Fedora 10 unable to boot after updating XO-1 to 8.2.0 In-Reply-To: <4AA7C984.2060306@webpath.net> References: <4AA67037.10804@bga.com> <5256d0b0909080858s1739a44ep43f1b6a71a95f8e2@mail.gmail.com> <4AA7C984.2060306@webpath.net> Message-ID: <20090910031631.GB26716@us.netrek.org> On Wed, Sep 09, 2009 at 11:28:04AM -0400, Todd Robinson wrote: > As some of you may know, we (On-Disk.com) do the Fedora 10 SD cards > which are currently available for the XO-1, but which we will need > to discontinue. > > Currently the Fedora 10 SD cards no longer work after updating to > 8.2.0 (OpenFirmware CL1 Q2E41 Q2E). When inserting the SD card it > acts as if it's not inserted ... you mean at this point that OpenFirmware doesn't read the /boot/olpc.fth on your SD card, right? You've tried changing it to emit test characters or something? > except that it also doesn't attempt to boot Sugar. ... you mean at this point that OpenFirmware also does not proceed to boot from the NAND flash, right? > I suspect the olpc.fth is used a bit differently with > the newer firmware version. I've reviewed your script. The first line does not contain the key text that DebXO uses: \ OLPC boot script The second last line uses unfreeze instead of dcon-unfreeze. There's some strange thing done to change the loading of the initrd, using constants that aren't defined, so I don't know what that code you have is trying to do. However, I've checked, and the code between the [if] and [then] does not trigger on Q2E41b. My guess is that you haven't tracked the changes in OpenFirmware correctly, or that the wrong first line text is used, or the unfreeze should be dcon-unfreeze. Lastly, check the line containing "root=UUID=4C67-D0F1", as it appears to have wrapped in your e-mail. -- James Cameron http://quozl.linux.org.au/ From cjb at laptop.org Fri Sep 11 00:27:17 2009 From: cjb at laptop.org (Chris Ball) Date: Thu, 10 Sep 2009 20:27:17 -0400 (EDT) Subject: New F11 for XO-1.5 build 30 Message-ID: <20090911002718.0B5EFFAB11@dev.laptop.org> http://wiki.laptop.org/go/F11_for_1.5 http://dev.laptop.org/~cjb/f11-1.5/os30 Compressed image size: 387.16mb (+7.44mb since build 29) Description of changes in this build: * Switch to a partitioned image: 1M partition map, 30M boot, 3.5G / Here's the commit that achieves this: http://dev.laptop.org/git/projects/fedora-xo/commit/?h=xo-1.5&id=e726a75dd9c89139ba959f846d7aaf5513c09f05 Package changes since build 29: -alsa-lib-1.0.21-1.fc11.i586 +alsa-lib-1.0.21-3.fc11.i586 -alsa-utils-1.0.21-1.fc11.i586 +alsa-utils-1.0.21-2.fc11.i586 -coreutils-7.2-3.fc11.i586 +coreutils-7.2-4.fc11.i586 -crda-1.1.0_2009.04.17-11.fc11.i586 +crda-1.1.0_2009.09.08-2.fc11.i586 +gnome-settings-daemon-2.26.1-10.fc11.i586 -gnome-settings-daemon-2.26.1-9.fc11.i586 -nfs-utils-1.2.0-4.fc11.i586 +nfs-utils-1.2.0-5.fc11.i586 From martin at martindengler.com Mon Sep 14 03:43:18 2009 From: martin at martindengler.com (Martin Dengler) Date: Mon, 14 Sep 2009 04:43:18 +0100 Subject: 30-keymap-olpc.fdi move from hal-info considered harmful? Message-ID: <20090914034318.GV22763@ops-13.xades.com> Sayamindu, rwh, and Team OLPC, Please reconsider the resolution of https://bugzilla.redhat.com/show_bug.cgi?id=514081 . Currently the resolution of this bug -- moving the file from the hal-info rpm to the olpc-utils rpm -- means olpc-utils must be installed for the 30-keymap-olpc.fdi file mapping the XO-1{,.5} keys to be installed. The problem with this is that olpc-utils brings in a raft of changes that are inappropriate for non-OLPC installs of Fedora. For example, the "olpc" user is assumed to exist, its homedir is written to, and olpc-dm is installed as the default display manager with the user "olpc" as the auto-login user. This breaks X startup unless the olpc user exists. Is there a better resolution that allows XO-1 keys to be recognised on a F12 timeframe without olpc-utils's other changes? Perhaps just putting the latest 30-keymap-olpc.fdi from http://dev.laptop.org/git/projects/olpc-utils/plain/etc/hal/fdi/information/30-keymap-olpc.fdi back into the hal-info package? Thanks, Martin -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From pgf at laptop.org Mon Sep 14 04:24:18 2009 From: pgf at laptop.org (Paul Fox) Date: Mon, 14 Sep 2009 00:24:18 -0400 Subject: 30-keymap-olpc.fdi move from hal-info considered harmful? In-Reply-To: <20090914034318.GV22763@ops-13.xades.com> (sfid-20090914_000613_005941_59D2B909) References: <20090914034318.GV22763@ops-13.xades.com> (sfid-20090914_000613_005941_59D2B909) Message-ID: <30202.1252902258@foxharp.boston.ma.us> martin wrote: > Sayamindu, rwh, and Team OLPC, > > Please reconsider the resolution of > https://bugzilla.redhat.com/show_bug.cgi?id=514081 . Currently the > resolution of this bug -- moving the file from the hal-info rpm to the > olpc-utils rpm -- means olpc-utils must be installed for the > 30-keymap-olpc.fdi file mapping the XO-1{,.5} keys to be installed. to be clear, the resolution wasn't to move the file -- there were two copies, one incorrect, and we requested that the out-of-date one be dropped. http://dev.laptop.org/ticket/9421 but perhaps this was the wrong thing to do, for the reasons you've given below. paul > > The problem with this is that olpc-utils brings in a raft of changes > that are inappropriate for non-OLPC installs of Fedora. For example, > the "olpc" user is assumed to exist, its homedir is written to, and > olpc-dm is installed as the default display manager with the user > "olpc" as the auto-login user. This breaks X startup unless the olpc > user exists. > > Is there a better resolution that allows XO-1 keys to be recognised > on a F12 timeframe without olpc-utils's other changes? > > Perhaps just putting the latest 30-keymap-olpc.fdi from > http://dev.laptop.org/git/projects/olpc-utils/plain/etc/hal/fdi/information/30-keymap-olpc.fdi > back into the hal-info package? > > Thanks, > Martin =--------------------- paul fox, pgf at laptop.org From martin at martindengler.com Mon Sep 14 10:24:11 2009 From: martin at martindengler.com (Martin Dengler) Date: Mon, 14 Sep 2009 11:24:11 +0100 Subject: 30-keymap-olpc.fdi move from hal-info considered harmful? In-Reply-To: <30202.1252902258@foxharp.boston.ma.us> References: <20090914034318.GV22763@ops-13.xades.com> <30202.1252902258@foxharp.boston.ma.us> Message-ID: <20090914102411.GW22763@ops-13.xades.com> On Mon, Sep 14, 2009 at 12:24:18AM -0400, Paul Fox wrote: > martin wrote: > > Sayamindu, rwh, and Team OLPC, > > > > Please reconsider the resolution of > > https://bugzilla.redhat.com/show_bug.cgi?id=514081 . Currently > > the resolution of this bug -- moving the file from the hal-info > > rpm to the olpc-utils rpm -- means olpc-utils must be installed > > for the 30-keymap-olpc.fdi file mapping the XO-1{,.5} keys to be > > installed. > > to be clear, the resolution wasn't to move the file Indeed...I should've said "removing the [one] file ... in favor of the [other]". > -- there were two copies, one incorrect To be clear, one wasn't incorrect to the point of uselessness - it was just not as complete / correct as we would like. It was still useful, which is why removing it is less than ideal. > but perhaps this was the wrong thing to do, for the reasons you've > given below. Yeah - the current situation seems like tidy-up that had an undesired consequence, as I assume olpc-utils' .fdi file was being used in preference to hal-info's one. Where is the .fdi file "supposed" to live - /etc/hal/... or /usr/share/hal/...? > paul Martin -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From sayamindu at gmail.com Mon Sep 14 13:44:44 2009 From: sayamindu at gmail.com (Sayamindu Dasgupta) Date: Mon, 14 Sep 2009 19:14:44 +0530 Subject: 30-keymap-olpc.fdi move from hal-info considered harmful? In-Reply-To: <20090914034318.GV22763@ops-13.xades.com> References: <20090914034318.GV22763@ops-13.xades.com> Message-ID: On Mon, Sep 14, 2009 at 9:13 AM, Martin Dengler wrote: > Sayamindu, rwh, and Team OLPC, > > Please reconsider the resolution of > https://bugzilla.redhat.com/show_bug.cgi?id=514081 . ?Currently the > resolution of this bug -- moving the file from the hal-info rpm to the > olpc-utils rpm -- means olpc-utils must be installed for the > 30-keymap-olpc.fdi file mapping the XO-1{,.5} keys to be installed. > > The problem with this is that olpc-utils brings in a raft of changes > that are inappropriate for non-OLPC installs of Fedora. ?For example, > the "olpc" user is assumed to exist, its homedir is written to, and > olpc-dm is installed as the default display manager with the user > "olpc" as the auto-login user. ?This breaks X startup unless the olpc > user exists. > > Is there a better resolution that allows XO-1 keys to be recognised > on a F12 timeframe without olpc-utils's other changes? > > Perhaps just putting the latest 30-keymap-olpc.fdi from > http://dev.laptop.org/git/projects/olpc-utils/plain/etc/hal/fdi/information/30-keymap-olpc.fdi > back into the hal-info package? > I guess now that the keys are working in both XO-1 and 1.5, we can submit two different files (or a single file if possible) to upstream HAL. Does that make sense ? Thanks, Sayamindu -- Sayamindu Dasgupta [http://sayamindu.randomink.org/ramblings] From martin at martindengler.com Mon Sep 14 13:49:13 2009 From: martin at martindengler.com (Martin Dengler) Date: Mon, 14 Sep 2009 14:49:13 +0100 Subject: 30-keymap-olpc.fdi move from hal-info considered harmful? In-Reply-To: References: <20090914034318.GV22763@ops-13.xades.com> Message-ID: <20090914134913.GZ22763@ops-13.xades.com> On Mon, Sep 14, 2009 at 07:14:44PM +0530, Sayamindu Dasgupta wrote: > I guess now that the keys are working in both XO-1 and 1.5, we can > submit two different files (or a single file if possible) to upstream > HAL. Does that make sense ? That'd work for me. > Thanks, > Sayamindu Martin -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From dsd at laptop.org Tue Sep 15 06:07:13 2009 From: dsd at laptop.org (Daniel Drake) Date: Tue, 15 Sep 2009 07:07:13 +0100 Subject: 30-keymap-olpc.fdi move from hal-info considered harmful? In-Reply-To: References: <20090914034318.GV22763@ops-13.xades.com> Message-ID: <818423da0909142307t1f8220ccrc25e78294fcada39@mail.gmail.com> 2009/9/14 Sayamindu Dasgupta : > I guess now that the keys are working in both XO-1 and 1.5, we can > submit two different files (or a single file if possible) to upstream > HAL. Does that make sense ? The single file as we have right now from olpc-utils is all you need. Daniel From mikus at bga.com Wed Sep 16 00:37:15 2009 From: mikus at bga.com (Mikus Grinbergs) Date: Tue, 15 Sep 2009 20:37:15 -0400 Subject: soas63xo impressions Message-ID: <4AB0333B.1040004@bga.com> Disclaimer: I am not asking for help; I'm sharing my experiences. Ran with soas63xo (booted from nand) on my XO-1. Many of the difficulties with previous SoaS builds were still present. My Settings -> Date&Time - as soon as (to move the selection off UTC to my timezone) I pressed (cursor was on vertical scrollbar) the left mouse button, sugar crashed. [Sugar also crashed when I clicked in the horizontal scrollbar in Browse.] Speak did not attempt to speak. [Note: The volume control in Frame came up as 'Muted' - I think that's the wrong initial default.] Record did not even launch. Browse came up with its display window size significantly exceeding the physical size of the XO screen. 'rpm -q kernel' shows *two* kernels applied to soas63xo. One nice thing is that Frame now shows one icon (instead of two) for setting up a local (under the tree) network. One less nice thing for me is the new toolbar design, as exemplified in Turtle_Art. It was nice to see the "Title" always in the toolbar - to remind "what am I on this screen for". Now that the user needs to hover (a particular spot) to see this reminder, Sugar seems less helpful. -------- *All* the builds-for-XO1 coming from sugarlabs.org are now f12-based. As far as I know, the OLPC plan is to start shipping XO-1.5 systems from the factory with f11-based software. I myself don't believe many XO users intend to immediately replace the (f11-based) software on their system with f12-based software (that they currently have to install themselves). From the point of view of users running an XO, the SugarLabs software is now on a "fork". mikus -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: Speak.log URL: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: Record.log URL: From gary at garycmartin.com Wed Sep 16 02:28:54 2009 From: gary at garycmartin.com (Gary C Martin) Date: Wed, 16 Sep 2009 03:28:54 +0100 Subject: soas63xo impressions In-Reply-To: <4AB0333B.1040004@bga.com> References: <4AB0333B.1040004@bga.com> Message-ID: Hi Mikus, On 16 Sep 2009, at 01:37, Mikus Grinbergs wrote: > One less nice thing for me is the new toolbar design, as exemplified > in Turtle_Art. It was nice to see the "Title" always in the toolbar > - to remind "what am I on this screen for". Now that the user needs > to hover (a particular spot) to see this reminder, Sugar seems less > helpful. There were many of tough calls to make re: the new toolbar design work. My early mockups tried to push in 'always show the title' direction above, for the reason you mention and for keeping the transition simpler: http://wiki.sugarlabs.org/go/Design_Team/Proposals/Toolbars ...but the 'always show the title' proposal was overridden by the community and for the sake of all the other new toolbar benefits (primary tools specifically 'Stop' need to always visible, kids got lost in old tab design, old tabs were rather small gui targets for young kids to click, tabs were text only, secondary toolbar lock open feature now allows visual access to many more tools at once), I needed to go with the flow and help with getting them into the release. I think they've turned out really great ? we (the ActivityTeam et al) just need to roll in the new design to as many Activities as we can, to keep UI consistency. FWIW, hiding the title text (plus sharing and keep) under the Activity toolbar icon does allow plenty of toolbar space so that even the most complicated current activities (Write) also have space to put commonly used functions in the primary toolbar. Putting the user coloured activity icon in as the first icon is also a nice design win regarding identifying the activity you're looking at (and whose it is). So, if most folks were still not often titling their activities, seeing the text "Write Activity" vs. seeing the Write Activity icon, in user colours, is actually providing slightly more information than in the common case before ;-b Thanks for the feedback. Regards, --Gary From mikus at bga.com Wed Sep 16 03:53:36 2009 From: mikus at bga.com (Mikus Grinbergs) Date: Tue, 15 Sep 2009 23:53:36 -0400 Subject: soas63xo impressions Message-ID: <4AB06140.7050506@bga.com> Regarding revised toolbar design: > Putting the user coloured activity icon > in as the first icon is also a nice design win regarding > identifying the activity you're looking at (and whose it is). I'm not your typical user - I usually have more than 100 Activities installed. You may remember what 100 icons mean - but I sure don't. [Whereas text is self-explanatory.] And if you've ever looked at Neighborhood View while connected to jabber.sugarlabs.org - it is hard to keep track of "whose" each icon is -- color is well suited for those with photographic memories. mikus From martin at martindengler.com Wed Sep 16 10:42:51 2009 From: martin at martindengler.com (Martin Dengler) Date: Wed, 16 Sep 2009 11:42:51 +0100 Subject: soas63xo impressions In-Reply-To: <4AB0333B.1040004@bga.com> References: <4AB0333B.1040004@bga.com> Message-ID: <20090916104251.GQ27645@ops-13.xades.com> On Tue, Sep 15, 2009 at 08:37:15PM -0400, Mikus Grinbergs wrote: > Disclaimer: I am not asking for help; I'm sharing my experiences. Thanks for reporting your experiences. You're good at finding builds that aren't even announced :). > Ran with soas63xo (booted from nand) on my XO-1. Many of the > difficulties with previous SoaS builds were still present. That last SoaS-on-XO build that was publicised was based on F11. This one (and recent ones) are based on Rawhide. So I expect there to be more bugs, rather than fewer, in the short term. > My Settings -> Date&Time - as soon as (to move the selection off UTC > to my timezone) I pressed (cursor was on vertical scrollbar) the > left mouse button, sugar crashed. [Sugar also crashed when I > clicked in the horizontal scrollbar in Browse.] I experienced this as well. No idea why. > 'rpm -q kernel' shows *two* kernels applied to soas63xo. This is expected and not a problem. > From the point of view of users running an XO, the SugarLabs > software is now on a "fork". It's on Fedora, and SugarLabs is upstream of OLPC. So it would be more usual to say "OLPC's distribution of GNU/Linux with Sugar is F11-based, and SoaS is F12-based". If you drew a graph to try to find "fork"s you might find it hard to usefully define that term: 0.82 0.84 0.86 Sugar -------O-------------O--------O-----------> Sugar HEAD \ \ \ ----> ----> ----> | | | F11 ---------oO-o--O-------------------|------> F11 HEAD | \ | | ------------------|------> OLPC HEAD | | F12 ----------|------------------------o-O----> F12 HEAD | | SoaS ----------o--------------------------o----> SoaS HEAD \ \ ---> Strawberry ---> Blueberry O = branch point o = merge point ("landing" a branch on another codeline) | = connection between branch and merge point > mikus Martin -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From dfarning at sugarlabs.org Mon Sep 21 18:48:19 2009 From: dfarning at sugarlabs.org (David Farning) Date: Mon, 21 Sep 2009 13:48:19 -0500 Subject: XO Special interest group at Sugar Labs Message-ID: For the past several months the OLPC/Sugar Labs ecosystem has been getting requests to provide releases of more recent versions of Sugar on the XO. The leading effort in this direction seems to be the F11-XO1 project. I would like to like to invite F11-XO1 to become part of the XO SIG. I have been trying to articulate the project goals and gather momentum across several groups. 1. OLPC as a downstream. 2. Sugar Labs as a focus point. 3. Various ecosystem leaders to do pilots with current versions of Sugar on XOs. 4. Various testers to provide user level testing. The goal of this groups is not to _fragment_ the existing efforts. The goal is bring the various efforts together to form a critical mass to help pull this propel forward. david From smparrish at gmail.com Mon Sep 21 20:40:27 2009 From: smparrish at gmail.com (Steven M. Parrish) Date: Mon, 21 Sep 2009 16:40:27 -0400 Subject: XO Special interest group at Sugar Labs In-Reply-To: References: Message-ID: <200909211640.28175.smparrish@gmail.com> > For the past several months the OLPC/Sugar Labs ecosystem has been > getting requests to provide releases of more recent versions of Sugar > on the XO. > > The leading effort in this direction seems to be the F11-XO1 project. > I would like to like to invite F11-XO1 to become part of the XO SIG. > I have been trying to articulate the project goals and gather momentum > across several groups. > 1. OLPC as a downstream. > 2. Sugar Labs as a focus point. > 3. Various ecosystem leaders to do pilots with current versions of Sugar on > XOs. 4. Various testers to provide user level testing. > > The goal of this groups is not to _fragment_ the existing efforts. > The goal is bring the various efforts together to form a critical mass > to help pull this propel forward. > > david > > _______________________________________________ > Fedora-olpc-list mailing list > Fedora-olpc-list at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-olpc-list > As the current maintainer of the "F11 for the XO-1" releases, I would be interested in hearing more about the XO SIG and how the work I am doing can benefit the SIG and how the SIG can benefit the work I am doing. Especially in regards to testing. The original goal of the project was to keep up with the work being done for the XO-1.5. It is important that the 2 releases stay in sync to present a consistent experience to the users. To that end I try and do frequent releases, and in fact one is due out this week. I am open to anything that will help both OLPC and Sugar in the hands of more users. Feel free to contact me off or on list. Steven ===================================================== Steven M. Parrish ------------------------------------------------------------------------------------------------- gpg fingerprint: 4B6C 8357 059E B7ED 8095 0FD6 1F4B EDA0 A9A6 13C0 http://tuxbrewr.fedorapeople.org/ irc.freenode.net: SMParrish @ #fedora-kde, #fedora-devel, #fedora-olpc, #sugar From pbrobinson at gmail.com Mon Sep 21 20:41:12 2009 From: pbrobinson at gmail.com (Peter Robinson) Date: Mon, 21 Sep 2009 21:41:12 +0100 Subject: XO Special interest group at Sugar Labs In-Reply-To: References: Message-ID: <5256d0b0909211341k339ab5cav2675a7bd71110ca9@mail.gmail.com> Hi David, On Mon, Sep 21, 2009 at 7:48 PM, David Farning wrote: > For the past several months the OLPC/Sugar Labs ecosystem has been > getting requests to provide releases of more recent versions of Sugar > on the XO. > > The leading effort in this direction seems to be the F11-XO1 project. > I would like to like to invite F11-XO1 to become part of the XO SIG. > I have been trying to articulate the project goals and gather momentum > across several groups. > 1. ?OLPC as a downstream. > 2. Sugar Labs as a focus point. > 3. Various ecosystem leaders to do pilots with current versions of Sugar on XOs. > 4. Various testers to provide user level testing. > > The goal of this groups is not to _fragment_ the existing efforts. > The goal is bring the various efforts together to form a critical mass > to help pull this propel forward. As far as I'm aware there is no F11-XO1 project, I'm aware of a couple of different projects to get the latest Sugar releases on the XO. - The SoaS on XO which is being run my Martin Dengler in conjunction with SoaS and SL (that's where its all hosted). - The OLPC project to get Fedora 11 on both the XO-1.5 and XO-1 which is being handled by Steven M. Parrish (and Daniel Drake / Chris Ball) Both projects are cross pollinated and use components of work done by both as well as myself and other Fedora upstream people. I don't believe there's much difference between them as where possible I believe most stuff is pushed upsteam. There is no current Fedora based project working on this directly due to the down stream projects. I have my own build that I use but that isn't generally published and is mostly to test core fedora for dependency bloat and breakages. I suggest you speak with the parties mentioned above for further information. Peter From dfarning at sugarlabs.org Mon Sep 21 23:36:50 2009 From: dfarning at sugarlabs.org (David Farning) Date: Mon, 21 Sep 2009 18:36:50 -0500 Subject: XO Special interest group at Sugar Labs In-Reply-To: <5256d0b0909211341k339ab5cav2675a7bd71110ca9@mail.gmail.com> References: <5256d0b0909211341k339ab5cav2675a7bd71110ca9@mail.gmail.com> Message-ID: On Mon, Sep 21, 2009 at 3:41 PM, Peter Robinson wrote: > Hi David, > > On Mon, Sep 21, 2009 at 7:48 PM, David Farning wrote: >> For the past several months the OLPC/Sugar Labs ecosystem has been >> getting requests to provide releases of more recent versions of Sugar >> on the XO. >> >> The leading effort in this direction seems to be the F11-XO1 project. >> I would like to like to invite F11-XO1 to become part of the XO SIG. >> I have been trying to articulate the project goals and gather momentum >> across several groups. >> 1. ?OLPC as a downstream. >> 2. Sugar Labs as a focus point. >> 3. Various ecosystem leaders to do pilots with current versions of Sugar on XOs. >> 4. Various testers to provide user level testing. >> >> The goal of this groups is not to _fragment_ the existing efforts. >> The goal is bring the various efforts together to form a critical mass >> to help pull this propel forward. > > As far as I'm aware there is no F11-XO1 project, I'm aware of a couple > of different projects to get the latest Sugar releases on the XO. > - The SoaS on XO which is being run my Martin Dengler in conjunction > with SoaS and SL (that's where its all hosted). > - The OLPC project to get Fedora 11 on both the XO-1.5 and XO-1 which > is being handled by Steven M. Parrish (and Daniel Drake / Chris Ball) This confusion is part of what I am hoping to clear up by create a single clearly defined project. I have heard back from many of the people working on the various projects. the work flow seems to be: 1. Sugar development team creates platform. 2. Fedora packagers package Sugar... and everything else required to make a disto. 3a. SoaS takes packages and turns them into a Soas image. 3b. Soas is getting pretty well test via test days and deployments such as the GPA. 4a. Steven take the Fedora packages adds the XO specific bit and turns them into xo builds. 4b. limited testing for xo builds. Because of time restrictions, the F11 on XO effort seems to be reactive. They take the output from cjb and the fedora packages and create builds. I believe that the XO SIG could help generate interest and attract more developers and testers to the project. > Both projects are cross pollinated and use components of work done by > both as well as myself and other Fedora upstream people. I don't > believe there's much difference between them as where possible I > believe most stuff is pushed upsteam. There is no current Fedora based > project working on this directly due to the down stream projects. > > I have my own build that I use but that isn't generally published and > is mostly to test core fedora for dependency bloat and breakages. Would it be useful if we started by combining your work and Stevens into an automatic build system. This could help identify breakages. Then we could create a release cycle of alpha and beta and final releases. By creating the daily builds and widely broadcasting the various releases, we can engage a larger community of testers. david From dsd at laptop.org Tue Sep 22 04:08:58 2009 From: dsd at laptop.org (Daniel Drake) Date: Tue, 22 Sep 2009 09:53:58 +0545 Subject: XO Special interest group at Sugar Labs In-Reply-To: References: <5256d0b0909211341k339ab5cav2675a7bd71110ca9@mail.gmail.com> Message-ID: <818423da0909212108i259bdd92v6a6ab3f2fe550f0e@mail.gmail.com> 2009/9/22 David Farning : > Because of time restrictions, the F11 on XO effort seems to be > reactive. ?They take the output from cjb and the fedora packages and > create builds. Is this a criticism? Are you proposing changing this? > ?I believe that the XO SIG could help generate interest > and attract more developers and testers to the project. That would be excellent. I'd encourage you to go ahead and create it so that these resources can start flowing. I don't think you need to say that F11-for-XO1 is "part of the XO SIG" -- the fact is that we all have the same goals, and Steven isn't going to reject help from anyone. This is the same way that the Fedora OLPC SIG was set up to help OLPC - it provides valuable assistance on various fronts but the actual "product" was still quite firmly under the OLPC roof. If you do want to formalise things and say "this is now a Sugar project," then that could be done at any point, but this should not be a barrier to getting people involved right now. > Would it be useful if we started by combining your work and Stevens > into an automatic build system. ?This could help identify breakages. > By creating the daily builds and widely broadcasting the various > releases, we can engage a larger community of testers. The build system would be trivial to automate, and I'd encourage you to do it as an exercise. Coordinated testing and a release cycle would of course be very beneficial to achieving the same quality of release as OLPC has done previously. It would be of value if you were to set that up. However, at this stage, I feel that both of those things would be severely hampered by the slow development pace. I would instead suggest that you focus on bringing in developers and technical resources at this point in time, leaving testing and release planning for a little later down the line. Thanks for your efforts! Daniel From phil at pricom.com.au Tue Sep 22 10:29:01 2009 From: phil at pricom.com.au (Philip Rhoades) Date: Tue, 22 Sep 2009 20:29:01 +1000 Subject: XO Special interest group at Sugar Labs In-Reply-To: <818423da0909212108i259bdd92v6a6ab3f2fe550f0e@mail.gmail.com> References: <5256d0b0909211341k339ab5cav2675a7bd71110ca9@mail.gmail.com> <818423da0909212108i259bdd92v6a6ab3f2fe550f0e@mail.gmail.com> Message-ID: <4AB8A6ED.2030104@pricom.com.au> People, I have been interested in the OLPC project for some time but only decided to try and install the Fedora Sugar desktop when I came across a mention of the TamTam application (for creating music). After a bit of messing around I got the Sugar desktop to start (on Fedora 11) but I don't get any sound and TamTam is supposed to be already installed but I don't see it . . suggestions? Also, I will probably update to a 64bit machine with a Fedora 12 beta - I presume Sugar would work in KVM virtual machine? Thanks, Phil. -- Philip Rhoades GPO Box 3411 Sydney NSW 2001 Australia E-mail: phil at pricom.com.au From phil at pricom.com.au Tue Sep 22 10:30:57 2009 From: phil at pricom.com.au (Philip Rhoades) Date: Tue, 22 Sep 2009 20:30:57 +1000 Subject: Fedora 11 + Sugar + TamTam In-Reply-To: <818423da0909212108i259bdd92v6a6ab3f2fe550f0e@mail.gmail.com> References: <5256d0b0909211341k339ab5cav2675a7bd71110ca9@mail.gmail.com> <818423da0909212108i259bdd92v6a6ab3f2fe550f0e@mail.gmail.com> Message-ID: <4AB8A761.7060208@pricom.com.au> People, Sorry - I should have changed the Subject on the previously sent mail . . I have been interested in the OLPC project for some time but only decided to try and install the Fedora Sugar desktop when I came across a mention of the TamTam application (for creating music). After a bit of messing around I got the Sugar desktop to start (on Fedora 11) but I don't get any sound and TamTam is supposed to be already installed but I don't see it . . suggestions? Also, I will probably update to a 64bit machine with a Fedora 12 beta - I presume Sugar would work in KVM virtual machine? Thanks, Phil. -- Philip Rhoades GPO Box 3411 Sydney NSW 2001 Australia E-mail: phil at pricom.com.au From martin at martindengler.com Tue Sep 22 10:31:43 2009 From: martin at martindengler.com (Martin Dengler) Date: Tue, 22 Sep 2009 11:31:43 +0100 Subject: TamTam on F11 (was: Re: XO Special interest group at Sugar Labs) In-Reply-To: <4AB8A6ED.2030104@pricom.com.au> References: <5256d0b0909211341k339ab5cav2675a7bd71110ca9@mail.gmail.com> <818423da0909212108i259bdd92v6a6ab3f2fe550f0e@mail.gmail.com> <4AB8A6ED.2030104@pricom.com.au> Message-ID: <20090922103142.GU14643@ops-13.xades.com> On Tue, Sep 22, 2009 at 08:29:01PM +1000, Philip Rhoades wrote: > After a bit of messing around I got the Sugar desktop to start (on > Fedora 11) but I don't get any sound and TamTam is supposed to be > already installed but I don't see it . . suggestions? Why do you think TamTam is supposed to be installed? Is it in /usr/share/sugar/Activities ? > Thanks, > > Phil. Martin -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From pbrobinson at gmail.com Tue Sep 22 10:48:25 2009 From: pbrobinson at gmail.com (Peter Robinson) Date: Tue, 22 Sep 2009 11:48:25 +0100 Subject: Fedora 11 + Sugar + TamTam In-Reply-To: <4AB8A761.7060208@pricom.com.au> References: <5256d0b0909211341k339ab5cav2675a7bd71110ca9@mail.gmail.com> <818423da0909212108i259bdd92v6a6ab3f2fe550f0e@mail.gmail.com> <4AB8A761.7060208@pricom.com.au> Message-ID: <5256d0b0909220348s606d75fbia649f4f0bbda828@mail.gmail.com> On Tue, Sep 22, 2009 at 11:30 AM, Philip Rhoades wrote: > People, > > Sorry - I should have changed the Subject on the previously sent mail . . > > I have been interested in the OLPC project for some time but only decided to > try and install the Fedora Sugar desktop when I came across a mention of the > TamTam application (for creating music). ?After a bit of messing around I > got the Sugar desktop to start (on Fedora 11) but I don't get any sound and > TamTam is supposed to be already installed but I don't see it . . > suggestions? > > Also, I will probably update to a 64bit machine with a Fedora 12 beta - I > presume Sugar would work in KVM virtual machine? Sugar works fine in Fedora on 32 or 64 bit on both Fedora 11 and Fedora 12. You can just do a 'yum groupinstall "Sugar Desktop Environment" ' Cheers, Peter From danceswithcars at gmail.com Tue Sep 22 11:23:08 2009 From: danceswithcars at gmail.com (DancesWithCars) Date: Tue, 22 Sep 2009 07:23:08 -0400 Subject: Fedora 11 + Sugar + TamTam In-Reply-To: <4AB8A761.7060208@pricom.com.au> References: <5256d0b0909211341k339ab5cav2675a7bd71110ca9@mail.gmail.com> <818423da0909212108i259bdd92v6a6ab3f2fe550f0e@mail.gmail.com> <4AB8A761.7060208@pricom.com.au> Message-ID: Sugar is more like an X desktop environment, so you would have to add another kernel/ iso to make it worth doing a virtual machine, kvm, qemu, virtualbox or whatever, Having multiple desktop environments is a bit of the issue, afaict. I'm running 64 bit Fedora Core 11 now, and have a vanilla sugar desktop from the yum repos (mentioned elsewhere on this thread) and a jhbuild later version, which I compile and run with jhbuild run (or similar, think there is a sugar- before it) when I want the latest that is not yet packaged for fedora. sound works, probably thru pulseaudio though most of the sound on olpc is done with csound, afaict. It would be nice to run 64 bit and run a little 32 bit image in virtual, but I've found the virtual environments not a good, resource intensive etc, so unless you are hacking the kernel and don't want to reboot so much, virtualization is a bit of overkill, imo. hope that clears a little bit up. but just what I know and more people on the list probably know lots more.. On Tue, Sep 22, 2009 at 6:30 AM, Philip Rhoades wrote: > People, > > Sorry - I should have changed the Subject on the previously sent mail . . > > I have been interested in the OLPC project for some time but only decided to > try and install the Fedora Sugar desktop when I came across a mention of the > TamTam application (for creating music). ?After a bit of messing around I > got the Sugar desktop to start (on Fedora 11) but I don't get any sound and > TamTam is supposed to be already installed but I don't see it . . > suggestions? > > Also, I will probably update to a 64bit machine with a Fedora 12 beta - I > presume Sugar would work in KVM virtual machine? > > Thanks, > > Phil. > -- > Philip Rhoades > > GPO Box 3411 > Sydney NSW ? ? ?2001 > Australia > E-mail: ?phil at pricom.com.au > > _______________________________________________ > Fedora-olpc-list mailing list > Fedora-olpc-list at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-olpc-list > -- DancesWithCars leave the wolves behind ;-) From bernie at codewiz.org Tue Sep 22 15:44:34 2009 From: bernie at codewiz.org (Bernie Innocenti) Date: Tue, 22 Sep 2009 11:44:34 -0400 Subject: XO Special interest group at Sugar Labs In-Reply-To: <4AB8A6ED.2030104@pricom.com.au> References: <5256d0b0909211341k339ab5cav2675a7bd71110ca9@mail.gmail.com> <818423da0909212108i259bdd92v6a6ab3f2fe550f0e@mail.gmail.com> <4AB8A6ED.2030104@pricom.com.au> Message-ID: <1253634274.1804.52.camel@giskard> El Tue, 22-09-2009 a las 20:29 +1000, Philip Rhoades escribi?: > I have been interested in the OLPC project for some time but only > decided to try and install the Fedora Sugar desktop when I came across a > mention of the TamTam application (for creating music). After a bit of > messing around I got the Sugar desktop to start (on Fedora 11) but I > don't get any sound and TamTam is supposed to be already installed but I > don't see it . . suggestions? > > Also, I will probably update to a 64bit machine with a Fedora 12 beta - > I presume Sugar would work in KVM virtual machine? By default, Qemu does not emulate any sound-card. Could this be part of the problem? -- // Bernie Innocenti - http://codewiz.org/ \X/ Sugar Labs - http://sugarlabs.org/ From mavrothal at yahoo.com Tue Sep 22 16:33:01 2009 From: mavrothal at yahoo.com (Yioryos Asprobounitis) Date: Tue, 22 Sep 2009 09:33:01 -0700 (PDT) Subject: XO Special interest group at Sugar Labs In-Reply-To: Message-ID: <899945.15576.qm@web65508.mail.ac4.yahoo.com> Now, that's an excellent idea! However, the crucial thing before any extensive building/testing starts is to address some major issues that would stop most people from using/testing F11/Sugar.84+. Namely the Xorg geode video driver, the camera and the battery monitor. These will primarily need developers. Having these components in place then a daily build bug fixing/reporting system would be more valuable since more people may be willing to give it a try, identifying the "minor" issues that may eventually allow a deployment-quality release. If this is going to be an OLPC, Fedora or SL project, I think is irrelevant. XO-1 is an EOL machine that runs an OS/UI developed by "some other" organization. Is literally orphan (besides these limited efforts) so any "adopter" should be welcome. Whoever sets it up should be good to go. With almost a million users is the biggest educational linux/sugar implementation and worths every attention. --- On Mon, 9/21/09, David Farning wrote: > From: David Farning > Subject: Re: XO Special interest group at Sugar Labs > To: fedora-olpc-list at redhat.com > Cc: "iaep" > Date: Monday, September 21, 2009, 7:36 PM > On Mon, Sep 21, 2009 at 3:41 PM, > Peter Robinson > wrote: > > Hi David, > > > > On Mon, Sep 21, 2009 at 7:48 PM, David Farning > wrote: > >> For the past several months the OLPC/Sugar Labs > ecosystem has been > >> getting requests to provide releases of more > recent versions of Sugar > >> on the XO. > >> > >> The leading effort in this direction seems to be > the F11-XO1 project. > >> I would like to like to invite F11-XO1 to become > part of the XO SIG. > >> I have been trying to articulate the project goals > and gather momentum > >> across several groups. > >> 1. ?OLPC as a downstream. > >> 2. Sugar Labs as a focus point. > >> 3. Various ecosystem leaders to do pilots with > current versions of Sugar on XOs. > >> 4. Various testers to provide user level testing. > >> > >> The goal of this groups is not to _fragment_ the > existing efforts. > >> The goal is bring the various efforts together to > form a critical mass > >> to help pull this propel forward. > > > > As far as I'm aware there is no F11-XO1 project, I'm > aware of a couple > > of different projects to get the latest Sugar releases > on the XO. > > - The SoaS on XO which is being run my Martin Dengler > in conjunction > > with SoaS and SL (that's where its all hosted). > > - The OLPC project to get Fedora 11 on both the XO-1.5 > and XO-1 which > > is being handled by Steven M. Parrish (and Daniel > Drake / Chris Ball) > > This confusion is part of what I am hoping to clear up by > create a > single clearly defined project. > > I have heard back from many of the people working on the > various > projects. the work flow seems to be: > 1. Sugar development team creates platform. > 2. Fedora packagers package Sugar... and everything else > required to > make a disto. > 3a. SoaS takes packages and turns them into a Soas image. > 3b. Soas is getting pretty well test via test days and > deployments > such as the GPA. > 4a. Steven take the Fedora packages adds the XO specific > bit and turns > them into xo builds. > 4b. limited testing for xo builds. > > Because of time restrictions, the F11 on XO effort seems to > be > reactive.? They take the output from cjb and the > fedora packages and > create builds.? I believe that the XO SIG could help > generate interest > and attract more developers and testers to the project. > > > Both projects are cross pollinated and use components > of work done by > > both as well as myself and other Fedora upstream > people. I don't > > believe there's much difference between them as where > possible I > > believe most stuff is pushed upsteam. There is no > current Fedora based > > project working on this directly due to the down > stream projects. > > > > I have my own build that I use but that isn't > generally published and > > is mostly to test core fedora for dependency bloat and > breakages. > > Would it be useful if we started by combining your work and > Stevens > into an automatic build system.? This could help > identify breakages. > Then we could create a release cycle of alpha and beta and > final > releases. > > By creating the daily builds and widely broadcasting the > various > releases, we can engage a larger community of testers. > > david > > _______________________________________________ > Fedora-olpc-list mailing list > Fedora-olpc-list at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-olpc-list > From phil at pricom.com.au Tue Sep 22 17:28:16 2009 From: phil at pricom.com.au (Philip Rhoades) Date: Wed, 23 Sep 2009 03:28:16 +1000 Subject: TamTam on F11 In-Reply-To: <20090922103142.GU14643@ops-13.xades.com> References: <5256d0b0909211341k339ab5cav2675a7bd71110ca9@mail.gmail.com> <818423da0909212108i259bdd92v6a6ab3f2fe550f0e@mail.gmail.com> <4AB8A6ED.2030104@pricom.com.au> <20090922103142.GU14643@ops-13.xades.com> Message-ID: <4AB90930.6030803@pricom.com.au> Martin, On 2009-09-22 20:31, Martin Dengler wrote: > On Tue, Sep 22, 2009 at 08:29:01PM +1000, Philip Rhoades wrote: >> After a bit of messing around I got the Sugar desktop to start (on >> Fedora 11) but I don't get any sound and TamTam is supposed to be >> already installed but I don't see it . . suggestions? > > Why do you think TamTam is supposed to be installed? Is it in > /usr/share/sugar/Activities ? I can't find the web page now but someone made a comment that there are many "TamTam"s and that they are part of the normal installation . . Thanks, Phil. -- Philip Rhoades GPO Box 3411 Sydney NSW 2001 Australia E-mail: phil at pricom.com.au From phil at pricom.com.au Tue Sep 22 17:32:34 2009 From: phil at pricom.com.au (Philip Rhoades) Date: Wed, 23 Sep 2009 03:32:34 +1000 Subject: Fedora 11 + Sugar + TamTam In-Reply-To: References: <5256d0b0909211341k339ab5cav2675a7bd71110ca9@mail.gmail.com> <818423da0909212108i259bdd92v6a6ab3f2fe550f0e@mail.gmail.com> <4AB8A761.7060208@pricom.com.au> Message-ID: <4AB90A32.6020402@pricom.com.au> Peter & DancesWithCars, Thanks for the info! Phil. On 2009-09-22 21:23, DancesWithCars wrote: > Sugar is more like an X desktop environment, > so you would have to add another kernel/ iso > to make it worth doing a virtual machine, kvm, > qemu, virtualbox or whatever, > > Having multiple desktop environments is > a bit of the issue, afaict. > > I'm running 64 bit Fedora Core 11 now, > and have a vanilla sugar desktop from the > yum repos (mentioned elsewhere on this thread) > and a jhbuild later version, which I compile > and run with jhbuild run (or similar, think there > is a sugar- before it) when I want the latest > that is not yet packaged for fedora. > > sound works, probably thru pulseaudio > though most of the sound on olpc > is done with csound, afaict. > > > It would be nice to run 64 bit > and run a little 32 bit image in virtual, > but I've found the virtual environments > not a good, resource intensive etc, > so unless you are hacking the kernel > and don't want to reboot so much, > virtualization is a bit of overkill, imo. > > hope that clears a little bit up. > but just what I know and more > people on the list probably know > lots more.. > > > On Tue, Sep 22, 2009 at 6:30 AM, Philip Rhoades wrote: >> People, >> >> Sorry - I should have changed the Subject on the previously sent mail . . >> >> I have been interested in the OLPC project for some time but only decided to >> try and install the Fedora Sugar desktop when I came across a mention of the >> TamTam application (for creating music). After a bit of messing around I >> got the Sugar desktop to start (on Fedora 11) but I don't get any sound and >> TamTam is supposed to be already installed but I don't see it . . >> suggestions? >> >> Also, I will probably update to a 64bit machine with a Fedora 12 beta - I >> presume Sugar would work in KVM virtual machine? >> >> Thanks, >> >> Phil. >> -- >> Philip Rhoades >> >> GPO Box 3411 >> Sydney NSW 2001 >> Australia >> E-mail: phil at pricom.com.au >> >> _______________________________________________ >> Fedora-olpc-list mailing list >> Fedora-olpc-list at redhat.com >> https://www.redhat.com/mailman/listinfo/fedora-olpc-list >> > > > -- Philip Rhoades GPO Box 3411 Sydney NSW 2001 Australia E-mail: phil at pricom.com.au From smparrish at gmail.com Tue Sep 22 23:39:54 2009 From: smparrish at gmail.com (Steven M. Parrish) Date: Tue, 22 Sep 2009 19:39:54 -0400 Subject: New F11 for the XO-1 Build 7 Message-ID: <200909221939.55114.smparrish@gmail.com> http://wiki.laptop.org/go/F11_for_XO-1 http://dev.laptop.org/~smparrish/XO-1/builds/OS7 This release includes and custom Fedora-olpc-release which enables the updates-testing repo by default. This repo is used in the creation of these builds so it makes sense to enable it by default. Also included is a new Fedora-olpc-kernel repo, this along with enabled repository protections will prevent the stock Fedora kernel being installed if the user does a "yum update". Delta RPMS have also been enabled, this will decrease the size of the downloads when doing an update. Here are the version differences between this release and the previous Enjoy, Steven -alsa-lib-1.0.20-1.fc11.i586 -alsa-utils-1.0.20-3.fc11.i586 +alsa-lib-1.0.21-3.fc11.i586 +alsa-utils-1.0.21-2.fc11.i586 -bash-4.0-7.fc11.i586 +bash-4.0-8.fc11.i586 -bind-libs-9.6.1-4.P1.fc11.i586 -bind-utils-9.6.1-4.P1.fc11.i586 +bind-libs-9.6.1-5.P1.fc11.i586 +bind-utils-9.6.1-5.P1.fc11.i586 -bridge-utils-1.2-7.fc11.i586 -checkpolicy-2.0.19-2.fc11.i586 -coreutils-7.2-3.fc11.i586 +coreutils-7.2-4.fc11.i586 -crda-1.1.0_2009.04.17-11.fc11.i586 +crda-1.1.0_2009.09.08-2.fc11.i586 -csound-5.10.1-9.fc11.i586 +csound-5.10.1-12.fc11.i586 +deltarpm-3.4-16.fc11.i586 -dhclient-4.1.0p1-2.fc11.i586 +dhclient-4.1.0p1-4.fc11.i586 -dracut-0.9-1.fc11.i586 +dracut-002-1.fc11.i586 -etoys-4.0.2229-1.fc11.noarch +etoys-4.0.2279-1.fc11.noarch -fedora-release-11-1.noarch -fedora-release-notes-11.0.0-2.fc11.noarch +fedora-olpc-release-11-3.noarch -firefox-3.5.2-2.fc11.i586 +firefox-3.5.3-1.fc11.i586 -fontconfig-2.7.1-1.fc11.i586 +fontconfig-2.7.2-1.fc11.i586 -glib2-2.20.4-1.fc11.i586 +glib2-2.20.5-1.fc11.i586 -gnome-settings-daemon-2.26.1-8.fc11.i586 +gnome-settings-daemon-2.26.1-10.fc11.i586 -gtk2-2.16.5-1.fc11.i586 +gtk2-2.16.6-2.fc11.i586 -hulahop-0.4.9-7.fc11.i586 +hulahop-0.4.9-8.fc11.i586 -kernel-2.6.30_xo1-20090806.0005.1.olpc.1a4850b.i586 -kernel-firmware-2.6.30_xo1-20090806.0005.1.olpc.1a4850b.i586 +kernel-2.6.30_xo1-20090919.0116.1.olpc.d2189d4.i586 +kernel-firmware-2.6.30_xo1-20090919.0116.1.olpc.d2189d4.i586 +libcap-ng-0.6.1-1.fc11.i586 -libmikmod-3.2.0-4.beta2.fc11.i586 +libmikmod-3.2.0-5.beta2.fc11.i586 -libpurple-2.6.1-1.fc11.i586 -libraw1394-2.0.1-2.fc11.i586 +libpurple-2.6.2-1.fc11.i586 +libraw1394-2.0.4-1.fc11.i586 -libselinux-utils-2.0.80-1.fc11.i586 -libsemanage-2.0.31-4.fc11.i586 -libsilc-1.1.8-5.fc11.i586 +libsilc-1.1.8-7.fc11.i586 -libudev0-141-4.fc11.i586 +libudev0-141-7.fc11.i586 -libv4l-0.6.0-1.fc11.i586 +libv4l-0.6.1-1.fc11.i586 -libvolume_id-141-4.fc11.i586 +libvolume_id-141-7.fc11.i586 -libXext-1.0.99.1-2.fc11.i586 +libXext-1.0.99.1-3.fc11.i586 -libxml2-2.7.3-3.fc11.i586 -libxml2-python-2.7.3-3.fc11.i586 +libxml2-2.7.4-2.fc11.i586 +libxml2-python-2.7.4-2.fc11.i586 -libxslt-1.1.24-4.fc11.i586 +libxslt-1.1.25-1.fc11.i586 -lzma-4.32.7-2.fc11.i586 -lzma-libs-4.32.7-2.fc11.i586 +lyx-cmex10-fonts-1.6.4-1.fc11.noarch +lyx-cmmi10-fonts-1.6.4-1.fc11.noarch +lyx-cmr10-fonts-1.6.4-1.fc11.noarch +lyx-cmsy10-fonts-1.6.4-1.fc11.noarch +lyx-esint10-fonts-1.6.4-1.fc11.noarch +lyx-eufm10-fonts-1.6.4-1.fc11.noarch +lyx-fonts-common-1.6.4-1.fc11.noarch +lyx-fonts-compat-1.6.4-1.fc11.noarch +lyx-msam10-fonts-1.6.4-1.fc11.noarch +lyx-msbm10-fonts-1.6.4-1.fc11.noarch +lyx-wasy10-fonts-1.6.4-1.fc11.noarch -mathml-fonts-1.0-23.fc11.noarch -nautilus-2.26.3-2.fc11.i586 -nautilus-extensions-2.26.3-2.fc11.i586 +nash-6.0.87-4.fc11.i586 +nautilus-2.26.3-3.fc11.i586 +nautilus-extensions-2.26.3-3.fc11.i586 -nfs-utils-1.2.0-4.fc11.i586 +nfs-utils-1.2.0-5.fc11.i586 -nss-3.12.3.99.3-2.11.4.fc11.i586 +nss-3.12.4-3.fc11.i586 -nss-softokn-freebl-3.12.3.99.3-2.11.4.fc11.i586 +nss-softokn-freebl-3.12.4-3.fc11.i586 -openldap-2.4.15-3.fc11.i586 +openldap-2.4.15-5.fc11.i586 -pciutils-3.1.3-1.fc11.i586 -pciutils-libs-3.1.3-1.fc11.i586 +pciutils-3.1.4-2.fc11.i586 +pciutils-libs-3.1.4-2.fc11.i586 +plymouth-scripts-0.7.0-0.2009.05.15.1.fc11.i586 -policycoreutils-2.0.62-12.12.fc11.i586 -pulseaudio-libs-0.9.15-14.fc11.i586 -pulseaudio-libs-glib2-0.9.15-14.fc11.i586 +pulseaudio-libs-0.9.15-17.fc11.i586 +pulseaudio-libs-glib2-0.9.15-17.fc11.i586 -smartmontools-5.38-11.fc11.i586 -sos-1.8-14.fc11.noarch +smartmontools-5.38-13.fc11.i586 +sos-1.8-16.fc11.noarch -taglib-1.5-4.fc11.i586 +taglib-1.5-9.fc11.i586 -telepathy-gabble-0.7.26-2.fc11.i586 +telepathy-gabble-0.7.26-3.fc11.i586 -totem-2.26.3-3.fc11.i586 -totem-gstreamer-2.26.3-3.fc11.i586 -totem-mozplugin-2.26.3-3.fc11.i586 +totem-2.26.3-5.fc11.i586 +totem-gstreamer-2.26.3-5.fc11.i586 +totem-mozplugin-2.26.3-5.fc11.i586 -tzdata-2009k-2.fc11.noarch -udev-141-4.fc11.i586 +tzdata-2009m-1.fc11.noarch +udev-141-7.fc11.i586 -ustr-1.0.4-8.fc11.i586 -util-linux-ng-2.14.2-9.fc11.i586 +util-linux-ng-2.14.2-11.fc11.i586 -xapian-bindings-python-1.0.14-1.fc11.i586 -xapian-core-libs-1.0.14-2.fc11.i586 +xapian-bindings-python-1.0.15-1.fc11.i586 +xapian-core-libs-1.0.15-1.fc11.i586 -xdg-utils-1.0.2-8.20081121cvs.fc11.noarch -xorg-x11-server-common-1.6.3-4.fc11.i586 -xorg-x11-server-utils-7.4-7.fc11.i586 -xorg-x11-server-Xorg-1.6.3-4.fc11.i586 +xorg-x11-server-common-1.6.4-0.1.fc11.i586 +xorg-x11-server-utils-7.4-7.1.fc11.i586 +xorg-x11-server-Xorg-1.6.4-0.1.fc11.i586 -xulrunner-1.9.1.2-1.fc11.i586 -xulrunner-python-1.9.1.2-1.fc11.i586 +xulrunner-1.9.1.3-1.fc11.i586 +xulrunner-python-1.9.1.3-1.fc11.i586 +xz-4.999.8-0.8.beta.20090817git.fc11.i586 +xz-lzma-compat-4.999.8-0.8.beta.20090817git.fc11.i586 -yum-3.2.23-3.fc11.noarch +yum-3.2.24-1.fc11.noarch +yum-plugin-protectbase-1.1.22-1.fc11.noarch +yum-presto-0.5.0-1.fc11.noarch ===================================================== Steven M. Parrish ------------------------------------------------------------------------------------------------- gpg fingerprint: 4B6C 8357 059E B7ED 8095 0FD6 1F4B EDA0 A9A6 13C0 http://tuxbrewr.fedorapeople.org/ irc.freenode.net: SMParrish @ #fedora-kde, #fedora-devel, #fedora-olpc, #sugar From jgotangco at gmail.com Wed Sep 23 02:13:39 2009 From: jgotangco at gmail.com (Jerome Gotangco) Date: Wed, 23 Sep 2009 10:13:39 +0800 Subject: [Testing] New F11 for the XO-1 Build 7 In-Reply-To: <200909221939.55114.smparrish@gmail.com> References: <200909221939.55114.smparrish@gmail.com> Message-ID: Thanks for this! I've tried it on an XO-1 and it updates fine. NM also works and connects to a wifi ap properly. I just noticed some things: 1. Panel has an email launcher but there is no associated email application for it. 2. Cheese doesn't recognize the webcam at all. 3. Buttons from dialog boxes get blackened out when hovered with the cursor (a refresh issue?) 4. The battery applet shows that laptop battery has no charge (0.0%) 5. No sound? Also the choice of Firefox as the default browser could be a potential issue because the performance of the browser is horrible caused by the very slow refresh rate of the display. Would something like Epiphany be more appropriate? Some of the issues presented above might have been to be known issues from the start and will be addressed in the future. My apologies if this is the case. Best, Jerome On Wed, Sep 23, 2009 at 7:39 AM, Steven M. Parrish wrote: > http://wiki.laptop.org/go/F11_for_XO-1 > http://dev.laptop.org/~smparrish/XO-1/builds/OS7 > > This release includes and custom Fedora-olpc-release which enables the > updates-testing repo by default. ?This repo is used in the creation of these > builds so it makes sense to enable it by default. ?Also included is a new > Fedora-olpc-kernel repo, this along with enabled repository protections will > prevent the stock Fedora kernel being installed if the user does a > "yum update". ?Delta RPMS have also been enabled, this will decrease the size > of the downloads when doing an update. -- Cheers, Jerome From mikus at bga.com Wed Sep 23 01:58:50 2009 From: mikus at bga.com (Mikus Grinbergs) Date: Tue, 22 Sep 2009 21:58:50 -0400 Subject: New F11 for the XO-1 Build 7 Message-ID: <4AB980DA.3010408@bga.com> > Also included is a new Fedora-olpc-kernel repo Running in Terminal. Unfortunately, that repo entry fails yum parsing (presumably because of the "*" character in the repo URL). Had to disable that whole entry in order to be able to run yum. mikus From reuben at laptop.org Wed Sep 23 12:40:53 2009 From: reuben at laptop.org (Reuben K. Caron) Date: Wed, 23 Sep 2009 08:40:53 -0400 Subject: New F11 for the XO-1 Build 7 In-Reply-To: <200909221939.55114.smparrish@gmail.com> References: <200909221939.55114.smparrish@gmail.com> Message-ID: <32E1DCFC-DE1A-489E-8919-8449F592F846@laptop.org> Steven, Great. I'll look forward to testing. Would it be possible and make sense to begin including DSD's the implement mesh support for F11: http://lists.laptop.org/pipermail/devel/2009-September/025645.html Regards, Reuben On Sep 22, 2009, at 7:39 PM, Steven M. Parrish wrote: > http://wiki.laptop.org/go/F11_for_XO-1 > http://dev.laptop.org/~smparrish/XO-1/builds/OS7 > > This release includes and custom Fedora-olpc-release which enables the > updates-testing repo by default. This repo is used in the creation > of these > builds so it makes sense to enable it by default. Also included is > a new > Fedora-olpc-kernel repo, this along with enabled repository > protections will > prevent the stock Fedora kernel being installed if the user does a > "yum update". Delta RPMS have also been enabled, this will decrease > the size > of the downloads when doing an update. > > Here are the version differences between this release and the previous > > Enjoy, > > Steven > > > -alsa-lib-1.0.20-1.fc11.i586 > -alsa-utils-1.0.20-3.fc11.i586 > +alsa-lib-1.0.21-3.fc11.i586 > +alsa-utils-1.0.21-2.fc11.i586 > > -bash-4.0-7.fc11.i586 > +bash-4.0-8.fc11.i586 > > -bind-libs-9.6.1-4.P1.fc11.i586 > -bind-utils-9.6.1-4.P1.fc11.i586 > +bind-libs-9.6.1-5.P1.fc11.i586 > +bind-utils-9.6.1-5.P1.fc11.i586 > > -bridge-utils-1.2-7.fc11.i586 > -checkpolicy-2.0.19-2.fc11.i586 > > -coreutils-7.2-3.fc11.i586 > +coreutils-7.2-4.fc11.i586 > > -crda-1.1.0_2009.04.17-11.fc11.i586 > +crda-1.1.0_2009.09.08-2.fc11.i586 > > -csound-5.10.1-9.fc11.i586 > +csound-5.10.1-12.fc11.i586 > > +deltarpm-3.4-16.fc11.i586 > > -dhclient-4.1.0p1-2.fc11.i586 > +dhclient-4.1.0p1-4.fc11.i586 > > -dracut-0.9-1.fc11.i586 > +dracut-002-1.fc11.i586 > > -etoys-4.0.2229-1.fc11.noarch > +etoys-4.0.2279-1.fc11.noarch > > -fedora-release-11-1.noarch > -fedora-release-notes-11.0.0-2.fc11.noarch > +fedora-olpc-release-11-3.noarch > > -firefox-3.5.2-2.fc11.i586 > +firefox-3.5.3-1.fc11.i586 > > -fontconfig-2.7.1-1.fc11.i586 > +fontconfig-2.7.2-1.fc11.i586 > > -glib2-2.20.4-1.fc11.i586 > +glib2-2.20.5-1.fc11.i586 > > -gnome-settings-daemon-2.26.1-8.fc11.i586 > +gnome-settings-daemon-2.26.1-10.fc11.i586 > > -gtk2-2.16.5-1.fc11.i586 > +gtk2-2.16.6-2.fc11.i586 > > -hulahop-0.4.9-7.fc11.i586 > +hulahop-0.4.9-8.fc11.i586 > > -kernel-2.6.30_xo1-20090806.0005.1.olpc.1a4850b.i586 > -kernel-firmware-2.6.30_xo1-20090806.0005.1.olpc.1a4850b.i586 > +kernel-2.6.30_xo1-20090919.0116.1.olpc.d2189d4.i586 > +kernel-firmware-2.6.30_xo1-20090919.0116.1.olpc.d2189d4.i586 > > +libcap-ng-0.6.1-1.fc11.i586 > > -libmikmod-3.2.0-4.beta2.fc11.i586 > +libmikmod-3.2.0-5.beta2.fc11.i586 > > -libpurple-2.6.1-1.fc11.i586 > -libraw1394-2.0.1-2.fc11.i586 > +libpurple-2.6.2-1.fc11.i586 > +libraw1394-2.0.4-1.fc11.i586 > > -libselinux-utils-2.0.80-1.fc11.i586 > -libsemanage-2.0.31-4.fc11.i586 > > -libsilc-1.1.8-5.fc11.i586 > +libsilc-1.1.8-7.fc11.i586 > > -libudev0-141-4.fc11.i586 > +libudev0-141-7.fc11.i586 > > -libv4l-0.6.0-1.fc11.i586 > +libv4l-0.6.1-1.fc11.i586 > > -libvolume_id-141-4.fc11.i586 > +libvolume_id-141-7.fc11.i586 > > -libXext-1.0.99.1-2.fc11.i586 > +libXext-1.0.99.1-3.fc11.i586 > > -libxml2-2.7.3-3.fc11.i586 > -libxml2-python-2.7.3-3.fc11.i586 > +libxml2-2.7.4-2.fc11.i586 > +libxml2-python-2.7.4-2.fc11.i586 > > -libxslt-1.1.24-4.fc11.i586 > +libxslt-1.1.25-1.fc11.i586 > > -lzma-4.32.7-2.fc11.i586 > -lzma-libs-4.32.7-2.fc11.i586 > > +lyx-cmex10-fonts-1.6.4-1.fc11.noarch > +lyx-cmmi10-fonts-1.6.4-1.fc11.noarch > +lyx-cmr10-fonts-1.6.4-1.fc11.noarch > +lyx-cmsy10-fonts-1.6.4-1.fc11.noarch > +lyx-esint10-fonts-1.6.4-1.fc11.noarch > +lyx-eufm10-fonts-1.6.4-1.fc11.noarch > +lyx-fonts-common-1.6.4-1.fc11.noarch > +lyx-fonts-compat-1.6.4-1.fc11.noarch > +lyx-msam10-fonts-1.6.4-1.fc11.noarch > +lyx-msbm10-fonts-1.6.4-1.fc11.noarch > +lyx-wasy10-fonts-1.6.4-1.fc11.noarch > > -mathml-fonts-1.0-23.fc11.noarch > > -nautilus-2.26.3-2.fc11.i586 > -nautilus-extensions-2.26.3-2.fc11.i586 > +nash-6.0.87-4.fc11.i586 > +nautilus-2.26.3-3.fc11.i586 > +nautilus-extensions-2.26.3-3.fc11.i586 > > -nfs-utils-1.2.0-4.fc11.i586 > +nfs-utils-1.2.0-5.fc11.i586 > > -nss-3.12.3.99.3-2.11.4.fc11.i586 > +nss-3.12.4-3.fc11.i586 > > -nss-softokn-freebl-3.12.3.99.3-2.11.4.fc11.i586 > +nss-softokn-freebl-3.12.4-3.fc11.i586 > > -openldap-2.4.15-3.fc11.i586 > +openldap-2.4.15-5.fc11.i586 > > -pciutils-3.1.3-1.fc11.i586 > -pciutils-libs-3.1.3-1.fc11.i586 > +pciutils-3.1.4-2.fc11.i586 > +pciutils-libs-3.1.4-2.fc11.i586 > > +plymouth-scripts-0.7.0-0.2009.05.15.1.fc11.i586 > > -policycoreutils-2.0.62-12.12.fc11.i586 > > -pulseaudio-libs-0.9.15-14.fc11.i586 > -pulseaudio-libs-glib2-0.9.15-14.fc11.i586 > > +pulseaudio-libs-0.9.15-17.fc11.i586 > +pulseaudio-libs-glib2-0.9.15-17.fc11.i586 > > -smartmontools-5.38-11.fc11.i586 > -sos-1.8-14.fc11.noarch > +smartmontools-5.38-13.fc11.i586 > +sos-1.8-16.fc11.noarch > > -taglib-1.5-4.fc11.i586 > +taglib-1.5-9.fc11.i586 > > -telepathy-gabble-0.7.26-2.fc11.i586 > +telepathy-gabble-0.7.26-3.fc11.i586 > > -totem-2.26.3-3.fc11.i586 > -totem-gstreamer-2.26.3-3.fc11.i586 > -totem-mozplugin-2.26.3-3.fc11.i586 > +totem-2.26.3-5.fc11.i586 > +totem-gstreamer-2.26.3-5.fc11.i586 > +totem-mozplugin-2.26.3-5.fc11.i586 > > -tzdata-2009k-2.fc11.noarch > -udev-141-4.fc11.i586 > +tzdata-2009m-1.fc11.noarch > +udev-141-7.fc11.i586 > > -ustr-1.0.4-8.fc11.i586 > -util-linux-ng-2.14.2-9.fc11.i586 > +util-linux-ng-2.14.2-11.fc11.i586 > > -xapian-bindings-python-1.0.14-1.fc11.i586 > -xapian-core-libs-1.0.14-2.fc11.i586 > +xapian-bindings-python-1.0.15-1.fc11.i586 > +xapian-core-libs-1.0.15-1.fc11.i586 > > -xdg-utils-1.0.2-8.20081121cvs.fc11.noarch > > -xorg-x11-server-common-1.6.3-4.fc11.i586 > -xorg-x11-server-utils-7.4-7.fc11.i586 > -xorg-x11-server-Xorg-1.6.3-4.fc11.i586 > +xorg-x11-server-common-1.6.4-0.1.fc11.i586 > +xorg-x11-server-utils-7.4-7.1.fc11.i586 > +xorg-x11-server-Xorg-1.6.4-0.1.fc11.i586 > > -xulrunner-1.9.1.2-1.fc11.i586 > -xulrunner-python-1.9.1.2-1.fc11.i586 > +xulrunner-1.9.1.3-1.fc11.i586 > +xulrunner-python-1.9.1.3-1.fc11.i586 > > +xz-4.999.8-0.8.beta.20090817git.fc11.i586 > +xz-lzma-compat-4.999.8-0.8.beta.20090817git.fc11.i586 > > -yum-3.2.23-3.fc11.noarch > +yum-3.2.24-1.fc11.noarch > > +yum-plugin-protectbase-1.1.22-1.fc11.noarch > +yum-presto-0.5.0-1.fc11.noarch > > > ===================================================== > Steven M. Parrish > ------------------------------------------------------------------------------------------------- > gpg fingerprint: 4B6C 8357 059E B7ED 8095 0FD6 1F4B EDA0 A9A6 13C0 > http://tuxbrewr.fedorapeople.org/ > irc.freenode.net: SMParrish @ #fedora-kde, #fedora-devel, #fedora- > olpc, #sugar > > _______________________________________________ > Fedora-olpc-list mailing list > Fedora-olpc-list at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-olpc-list From smparrish at gmail.com Wed Sep 23 16:06:18 2009 From: smparrish at gmail.com (Steven M. Parrish) Date: Wed, 23 Sep 2009 12:06:18 -0400 Subject: New F11 for the XO-1 Build 7 In-Reply-To: <4AB980DA.3010408@bga.com> References: <4AB980DA.3010408@bga.com> Message-ID: <200909231206.19283.smparrish@gmail.com> > > Also included is a new Fedora-olpc-kernel repo > > Running in Terminal. Unfortunately, that repo entry fails yum > parsing (presumably because of the "*" character in the repo URL). > > Had to disable that whole entry in order to be able to run yum. > > mikus > > _______________________________________________ > Fedora-olpc-list mailing list > Fedora-olpc-list at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-olpc-list > Strange this works just fine for me. Is anyone else able to reproduce this? Steven ===================================================== Steven M. Parrish ------------------------------------------------------------------------------------------------- gpg fingerprint: 4B6C 8357 059E B7ED 8095 0FD6 1F4B EDA0 A9A6 13C0 http://tuxbrewr.fedorapeople.org/ irc.freenode.net: SMParrish @ #fedora-kde, #fedora-devel, #fedora-olpc, #sugar From mavrothal at yahoo.com Wed Sep 23 18:41:41 2009 From: mavrothal at yahoo.com (Yioryos Asprobounitis) Date: Wed, 23 Sep 2009 11:41:41 -0700 (PDT) Subject: New F11 for the XO-1 Build 7 In-Reply-To: <4AB980DA.3010408@bga.com> Message-ID: <492384.67719.qm@web65509.mail.ac4.yahoo.com> --- On Tue, 9/22/09, Mikus Grinbergs wrote: > From: Mikus Grinbergs > Subject: Re: New F11 for the XO-1 Build 7 > To: "Fedora OLPC List" > Date: Tuesday, September 22, 2009, 9:58 PM > > Also included is a new > Fedora-olpc-kernel repo > > Running in Terminal.? Unfortunately, that repo entry > fails yum parsing (presumably because of the "*" character > in the repo URL). > > Had to disable that whole entry in order to be able to run > yum. > > mikus > > Strange this works just fine for me. Is anyone else able to reproduce > this? Actually yes. here is what I get [root at localhost olpc]# yum update Loaded plugins: presto, protectbase Options Error: Error parsing 'http://dev.laptop.org/~dilinger/olpc-2.6.30-xo1 --includepkgs=kernel*': URL must be http, ftp, file or https not "" Removing the '*' from the URL in /etc/yum.repos.d/fedora-olpc-kernel.repo results in the same message From mavrothal at yahoo.com Wed Sep 23 19:18:33 2009 From: mavrothal at yahoo.com (Yioryos Asprobounitis) Date: Wed, 23 Sep 2009 12:18:33 -0700 (PDT) Subject: New F11 for the XO-1 Build 7 Message-ID: <868966.34210.qm@web65516.mail.ac4.yahoo.com> --- On Wed, 9/23/09, Yioryos Asprobounitis wrote: > From: Yioryos Asprobounitis > Subject: Re: New F11 for the XO-1 Build 7 > To: "Fedora OLPC List" , "Mikus Grinbergs" , "Steven M. Parrish" > Date: Wednesday, September 23, 2009, 2:41 PM > > > --- On Tue, 9/22/09, Mikus Grinbergs > wrote: > > > From: Mikus Grinbergs > > Subject: Re: New F11 for the XO-1? Build 7 > > To: "Fedora OLPC List" > > Date: Tuesday, September 22, 2009, 9:58 PM > > > Also included is a new > > Fedora-olpc-kernel repo > > > > Running in Terminal.? Unfortunately, that repo entry > > fails yum parsing (presumably because of the "*" > character > > in the repo URL). > > > > Had to disable that whole entry in order to be able to > run > > yum. > > > > mikus > > > > > Strange this works just fine for me.? Is anyone > else able to reproduce > this? > > Actually yes. > here is what I get > > [root at localhost olpc]# yum update > Loaded plugins: presto, protectbase > Options Error: Error parsing 'http://dev.laptop.org/~dilinger/olpc-2.6.30-xo1 > --includepkgs=kernel*': URL must be http, ftp, file or https > not "" > > Removing the '*' from the URL in > /etc/yum.repos.d/fedora-olpc-kernel.repo results in the same > message > > PS: renaming /etc/yum.repos.d/fedora-olpc-kernel.repo allows yum to work. However now offers to update the Kernel and kernel firmware so I assume the --excludepkgs=kernel* option does not work jn the fedora .repo files From danceswithcars at gmail.com Thu Sep 24 10:45:17 2009 From: danceswithcars at gmail.com (DancesWithCars) Date: Thu, 24 Sep 2009 06:45:17 -0400 Subject: XO Special interest group at Sugar Labs In-Reply-To: <899945.15576.qm@web65508.mail.ac4.yahoo.com> References: <899945.15576.qm@web65508.mail.ac4.yahoo.com> Message-ID: I'm not sure about the hardware issues mentioned below, as new to some of these lists, but if there is an installed base of XO-1 computers with special hardware like the touchpad with 2 extra areas that were never implemented, why not develop applications for those, even if the XO-1.5 and XO-2 plans don't include them? What are you going to tell the kids with XO-1s when the XO-1.5 come out? What is the consolation prize? Knowing more about it, and being further up the learning curve? Also, the battery issues will get worse, as the hardware gets older, so testing and determining when need new battery, as a computer without power isn't much fun. Repairing hardware gets more crucial as machines get older. Being more inventive with what you have instead of this is the shiny new machine, so going deeper into the system, maybe programming instead of just using. Or more time with the learning content. Even as a ebook reader, getting new content, creating new content, maybe more translating content? I still think flossmanuals.net needs indexing and other layout stuff, under the hood, or however parallel, LyX makes some assumptions, and does some of that but not the wiki and social stuff up top, so [La]TeX classes and styles might be a good contribution, finding objavi and booki source code, etc... The requirements for testing a new build is some extra XO-n hardware for testing, and a high speed connection, if giving new .isos builds out to the world, or access to some place that would, plus the time and knowledge to make the changes, find bugs, report them, etc. And if 'It's An Eduction Project" are we teaching self reliance and how to do builds, make your own constructionist style or whatever teaching paradigm fits the locals? Or forcing dependence upon others? My $.02 USD - costs of ownership/ && giving back. On Tue, Sep 22, 2009 at 12:33 PM, Yioryos Asprobounitis wrote: > Now, that's an excellent idea! > However, the crucial thing before any extensive building/testing starts is to address some major issues that would stop most people from using/testing F11/Sugar.84+. Namely the Xorg geode video driver, the camera and the battery monitor. These will primarily need developers. > Having these components in place then a daily build bug fixing/reporting system would be more valuable since more people may be willing to give it a try, identifying the "minor" issues that may eventually allow a deployment-quality release. > If this is going to be an OLPC, Fedora or SL project, I think is irrelevant. XO-1 is an EOL machine that runs an OS/UI developed by "some other" organization. Is literally orphan (besides these limited efforts) so any "adopter" should be welcome. Whoever sets it up should be good to go. With almost a million users is the biggest educational linux/sugar implementation and worths every attention. > > --- On Mon, 9/21/09, David Farning wrote: > >> From: David Farning >> Subject: Re: XO Special interest group at Sugar Labs >> To: fedora-olpc-list at redhat.com >> Cc: "iaep" >> Date: Monday, September 21, 2009, 7:36 PM >> On Mon, Sep 21, 2009 at 3:41 PM, >> Peter Robinson >> wrote: >> > Hi David, >> > >> > On Mon, Sep 21, 2009 at 7:48 PM, David Farning >> wrote: >> >> For the past several months the OLPC/Sugar Labs >> ecosystem has been >> >> getting requests to provide releases of more >> recent versions of Sugar >> >> on the XO. >> >> >> >> The leading effort in this direction seems to be >> the F11-XO1 project. >> >> I would like to like to invite F11-XO1 to become >> part of the XO SIG. >> >> I have been trying to articulate the project goals >> and gather momentum >> >> across several groups. >> >> 1. ?OLPC as a downstream. >> >> 2. Sugar Labs as a focus point. >> >> 3. Various ecosystem leaders to do pilots with >> current versions of Sugar on XOs. >> >> 4. Various testers to provide user level testing. >> >> >> >> The goal of this groups is not to _fragment_ the >> existing efforts. >> >> The goal is bring the various efforts together to >> form a critical mass >> >> to help pull this propel forward. >> > >> > As far as I'm aware there is no F11-XO1 project, I'm >> aware of a couple >> > of different projects to get the latest Sugar releases >> on the XO. >> > - The SoaS on XO which is being run my Martin Dengler >> in conjunction >> > with SoaS and SL (that's where its all hosted). >> > - The OLPC project to get Fedora 11 on both the XO-1.5 >> and XO-1 which >> > is being handled by Steven M. Parrish (and Daniel >> Drake / Chris Ball) >> >> This confusion is part of what I am hoping to clear up by >> create a >> single clearly defined project. >> >> I have heard back from many of the people working on the >> various >> projects. the work flow seems to be: >> 1. Sugar development team creates platform. >> 2. Fedora packagers package Sugar... and everything else >> required to >> make a disto. >> 3a. SoaS takes packages and turns them into a Soas image. >> 3b. Soas is getting pretty well test via test days and >> deployments >> such as the GPA. >> 4a. Steven take the Fedora packages adds the XO specific >> bit and turns >> them into xo builds. >> 4b. limited testing for xo builds. >> >> Because of time restrictions, the F11 on XO effort seems to >> be >> reactive.? They take the output from cjb and the >> fedora packages and >> create builds.? I believe that the XO SIG could help >> generate interest >> and attract more developers and testers to the project. >> >> > Both projects are cross pollinated and use components >> of work done by >> > both as well as myself and other Fedora upstream >> people. I don't >> > believe there's much difference between them as where >> possible I >> > believe most stuff is pushed upsteam. There is no >> current Fedora based >> > project working on this directly due to the down >> stream projects. >> > >> > I have my own build that I use but that isn't >> generally published and >> > is mostly to test core fedora for dependency bloat and >> breakages. >> >> Would it be useful if we started by combining your work and >> Stevens >> into an automatic build system.? This could help >> identify breakages. >> Then we could create a release cycle of alpha and beta and >> final >> releases. >> >> By creating the daily builds and widely broadcasting the >> various >> releases, we can engage a larger community of testers. >> >> david >> >> _______________________________________________ >> Fedora-olpc-list mailing list >> Fedora-olpc-list at redhat.com >> https://www.redhat.com/mailman/listinfo/fedora-olpc-list >> > > > > > _______________________________________________ > Fedora-olpc-list mailing list > Fedora-olpc-list at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-olpc-list > -- DancesWithCars leave the wolves behind ;-) From mavrothal at yahoo.com Thu Sep 24 13:22:50 2009 From: mavrothal at yahoo.com (Yioryos Asprobounitis) Date: Thu, 24 Sep 2009 06:22:50 -0700 (PDT) Subject: XO Special interest group at Sugar Labs In-Reply-To: Message-ID: <666336.72153.qm@web65513.mail.ac4.yahoo.com> --- On Thu, 9/24/09, DancesWithCars wrote: > From: DancesWithCars > Subject: Re: XO Special interest group at Sugar Labs > To: "Yioryos Asprobounitis" > Cc: fedora-olpc-list at redhat.com, "David Farning" , "iaep" > Date: Thursday, September 24, 2009, 6:45 AM > I'm not sure about the hardware > issues > mentioned below, as new to some of these lists, > but if there is an installed base of XO-1 computers > with special hardware like the touchpad > with 2 extra areas that were never implemented, > why not develop applications for those, > even if the XO-1.5 and XO-2 plans don't > include them? > > What are you going to tell the kids > with XO-1s when the XO-1.5 come out? > What is the consolation prize? > Knowing more about it, and > being further up the learning curve? > > Also, the battery issues will get worse, > as the hardware gets older, so testing > and determining when need new battery, > as a computer without power isn't much > fun. > > Repairing hardware gets more crucial > as machines get older. > > Being more inventive with what you have > instead of this is the shiny new machine, > so going deeper into the system, > maybe programming instead of just > using.? Or more time with the learning > content. > > Even as a ebook reader, getting new > content, creating new content, > maybe more translating content? > > I still think flossmanuals.net > needs indexing and other layout stuff, > under the hood, or however parallel, > LyX makes some assumptions, > and does some of that but not > the wiki and social stuff up top, > so [La]TeX classes and styles might be > a good contribution, finding > objavi and booki source code, > etc... > These are all very valid points. However, is not clear to me if you imply that they should be prioritized over the updating of the os/sugar or not. I hope not since some of these may even benefit from an updated OS (touchpad, battery, other hardware related patches) as opposed to an unsupported one (Fedora 9). On the other hand being a voluntary process is hard to tell to people "you do this instead of that". You can certainly try to convince them, and I think you do a good job on that :-) > The requirements for testing a new build > is some extra XO-n hardware for testing, > and a high speed connection, if giving > new .isos builds out to the world, > or access to some place that would, > plus the time and knowledge to > make the changes, find bugs, > report them, etc. Again I'm not sure what this means. That is trivial? That a "beta" quality OS should be delivered to the students/deployments and let them debug it? Other? > > And if 'It's An Eduction Project" > are we teaching self reliance > and how to do builds, make your > own constructionist style or > whatever teaching paradigm fits > the locals?? Or forcing dependence > upon others? Again trying to read between the lines... I'm sure that "locals" have their hands full trying to make the best of the available hardware/software, adapt it to their needs and build their own apps when needed. I would also guess that if the current Fedora 9-based OS is a blocker to paramount needs they may try to update it themselves. However, providing a better option as the F11/Sugar0.84+ is, in no way is in contrast with the "educational project". For one is _not_ a "computer education" project. So "upgrade your OS", is by no means a priority. Is welcome, but in no way required. Expecting a 9-12 years old on the other hand to come up with the solutions is conceivable but nothing to depend on, either. Finally the fact that if you give someone a fishing pole will eat fish all his/her life, does not preclude that you can not give them a fishing boat to get bigger fish, nor it implies they should built one. They may as well build a boat by themselves but the goal here is to get as much and as good fish as possible given the needs. Finally self reliance is an important factor. However like everything else in teaching it must be build gradually, in the right order and by experience. Assigning tasks that will be never completed guaranties that you will build self depreciation rather than self reliance. And as you said "is an educational project". If I read your comments wrong, my apologies. > > My $.02 USD - costs of ownership/ > && giving back. > > On Tue, Sep 22, 2009 at 12:33 PM, Yioryos Asprobounitis > > wrote: > > Now, that's an excellent idea! > > However, the crucial thing before any extensive > building/testing starts is to address some major issues that > would stop most people from using/testing F11/Sugar.84+. > Namely the Xorg geode video driver, the camera and the > battery monitor. These will primarily need developers. > > Having these components in place then a daily build > bug fixing/reporting system would be more valuable since > more people may be willing to give it a try, identifying the > "minor" issues that may eventually allow a > deployment-quality release. > > If this is going to be an OLPC, Fedora or SL project, > I think is irrelevant. XO-1 is an EOL machine that runs an > OS/UI developed by "some other" organization. Is literally > orphan (besides these limited efforts) so any "adopter" > should be welcome. Whoever sets it up should be good to go. > With almost a million users is the biggest educational > linux/sugar implementation and worths every attention. > > > > --- On Mon, 9/21/09, David Farning > wrote: > > > >> From: David Farning > >> Subject: Re: XO Special interest group at Sugar > Labs > >> To: fedora-olpc-list at redhat.com > >> Cc: "iaep" > >> Date: Monday, September 21, 2009, 7:36 PM > >> On Mon, Sep 21, 2009 at 3:41 PM, > >> Peter Robinson > >> wrote: > >> > Hi David, > >> > > >> > On Mon, Sep 21, 2009 at 7:48 PM, David > Farning > >> wrote: > >> >> For the past several months the > OLPC/Sugar Labs > >> ecosystem has been > >> >> getting requests to provide releases of > more > >> recent versions of Sugar > >> >> on the XO. > >> >> > >> >> The leading effort in this direction > seems to be > >> the F11-XO1 project. > >> >> I would like to like to invite F11-XO1 to > become > >> part of the XO SIG. > >> >> I have been trying to articulate the > project goals > >> and gather momentum > >> >> across several groups. > >> >> 1. ?OLPC as a downstream. > >> >> 2. Sugar Labs as a focus point. > >> >> 3. Various ecosystem leaders to do pilots > with > >> current versions of Sugar on XOs. > >> >> 4. Various testers to provide user level > testing. > >> >> > >> >> The goal of this groups is not to > _fragment_ the > >> existing efforts. > >> >> The goal is bring the various efforts > together to > >> form a critical mass > >> >> to help pull this propel forward. > >> > > >> > As far as I'm aware there is no F11-XO1 > project, I'm > >> aware of a couple > >> > of different projects to get the latest Sugar > releases > >> on the XO. > >> > - The SoaS on XO which is being run my Martin > Dengler > >> in conjunction > >> > with SoaS and SL (that's where its all > hosted). > >> > - The OLPC project to get Fedora 11 on both > the XO-1.5 > >> and XO-1 which > >> > is being handled by Steven M. Parrish (and > Daniel > >> Drake / Chris Ball) > >> > >> This confusion is part of what I am hoping to > clear up by > >> create a > >> single clearly defined project. > >> > >> I have heard back from many of the people working > on the > >> various > >> projects. the work flow seems to be: > >> 1. Sugar development team creates platform. > >> 2. Fedora packagers package Sugar... and > everything else > >> required to > >> make a disto. > >> 3a. SoaS takes packages and turns them into a Soas > image. > >> 3b. Soas is getting pretty well test via test days > and > >> deployments > >> such as the GPA. > >> 4a. Steven take the Fedora packages adds the XO > specific > >> bit and turns > >> them into xo builds. > >> 4b. limited testing for xo builds. > >> > >> Because of time restrictions, the F11 on XO effort > seems to > >> be > >> reactive.? They take the output from cjb and the > >> fedora packages and > >> create builds.? I believe that the XO SIG could > help > >> generate interest > >> and attract more developers and testers to the > project. > >> > >> > Both projects are cross pollinated and use > components > >> of work done by > >> > both as well as myself and other Fedora > upstream > >> people. I don't > >> > believe there's much difference between them > as where > >> possible I > >> > believe most stuff is pushed upsteam. There > is no > >> current Fedora based > >> > project working on this directly due to the > down > >> stream projects. > >> > > >> > I have my own build that I use but that > isn't > >> generally published and > >> > is mostly to test core fedora for dependency > bloat and > >> breakages. > >> > >> Would it be useful if we started by combining your > work and > >> Stevens > >> into an automatic build system.? This could help > >> identify breakages. > >> Then we could create a release cycle of alpha and > beta and > >> final > >> releases. > >> > >> By creating the daily builds and widely > broadcasting the > >> various > >> releases, we can engage a larger community of > testers. > >> > >> david > >> > >> _______________________________________________ > >> Fedora-olpc-list mailing list > >> Fedora-olpc-list at redhat.com > >> https://www.redhat.com/mailman/listinfo/fedora-olpc-list > >> > > > > > > > > > > _______________________________________________ > > Fedora-olpc-list mailing list > > Fedora-olpc-list at redhat.com > > https://www.redhat.com/mailman/listinfo/fedora-olpc-list > > > > > > -- > DancesWithCars > leave the wolves behind ;-) > From smparrish at gmail.com Thu Sep 24 15:26:38 2009 From: smparrish at gmail.com (Steven M. Parrish) Date: Thu, 24 Sep 2009 11:26:38 -0400 Subject: New F11 for the XO-1 Build 7 In-Reply-To: <4AB980DA.3010408@bga.com> References: <4AB980DA.3010408@bga.com> Message-ID: <200909241126.38698.smparrish@gmail.com> > > Also included is a new Fedora-olpc-kernel repo > > Running in Terminal. Unfortunately, that repo entry fails yum > parsing (presumably because of the "*" character in the repo URL). > > Had to disable that whole entry in order to be able to run yum. > > mikus > > _______________________________________________ > Fedora-olpc-list mailing list > Fedora-olpc-list at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-olpc-list > There is a type in the repo file and I have fixed it locally and will be in the next release. Until you can fix this issue by modifying the fedora-olpc- kernel.repo file as follows. baseurl=http://dev.laptop.org/~dilinger/olpc-2.6.30-xo1/ --includepkgs=kernel* These need to be on seperate lines to get it to parse correctly. Sorry bout that. Steven ===================================================== Steven M. Parrish ------------------------------------------------------------------------------------------------- gpg fingerprint: 4B6C 8357 059E B7ED 8095 0FD6 1F4B EDA0 A9A6 13C0 http://tuxbrewr.fedorapeople.org/ irc.freenode.net: SMParrish @ #fedora-kde, #fedora-devel, #fedora-olpc, #sugar From phil at pricom.com.au Thu Sep 24 23:55:50 2009 From: phil at pricom.com.au (Philip Rhoades) Date: Fri, 25 Sep 2009 09:55:50 +1000 Subject: TamTam on F11 (was: XO Special interest group at Sugar Labs) In-Reply-To: <1253634274.1804.52.camel@giskard> References: <5256d0b0909211341k339ab5cav2675a7bd71110ca9@mail.gmail.com> <818423da0909212108i259bdd92v6a6ab3f2fe550f0e@mail.gmail.com> <4AB8A6ED.2030104@pricom.com.au> <1253634274.1804.52.camel@giskard> Message-ID: <4ABC0706.6060102@pricom.com.au> Bernie, On 2009-09-23 01:44, Bernie Innocenti wrote: > El Tue, 22-09-2009 a las 20:29 +1000, Philip Rhoades escribi?: >> I have been interested in the OLPC project for some time but only >> decided to try and install the Fedora Sugar desktop when I came across a >> mention of the TamTam application (for creating music). After a bit of >> messing around I got the Sugar desktop to start (on Fedora 11) but I >> don't get any sound and TamTam is supposed to be already installed but I >> don't see it . . suggestions? >> >> Also, I will probably update to a 64bit machine with a Fedora 12 beta - >> I presume Sugar would work in KVM virtual machine? > > By default, Qemu does not emulate any sound-card. Could this be part of > the problem? Currently I am trying to get it working on a non-virtual, Fedora 11 i686 . . Thanks, Phil. -- Philip Rhoades GPO Box 3411 Sydney NSW 2001 Australia E-mail: phil at pricom.com.au From martin at martindengler.com Sat Sep 26 03:24:17 2009 From: martin at martindengler.com (Martin Dengler) Date: Sat, 26 Sep 2009 03:24:17 +0000 Subject: New SoaS build soas68 Message-ID: <200909260324.n8Q3OHjQ011969@buildslave-fedora-11-32bit.sugarlabs.org> New Sugar-on-a-Stick build soas68 is available. Size changes: ------------ total SoaS ext3 size / change in size: 1442.41M / -248K (change) total SoaS-for-XO-1 NAND size / change in size: 608.73M / 132K (change) Package changes: --------------- --- soas67.tree.packages.txt 2009-09-26 01:43:40.000000000 +0000 +++ soas68.tree.packages.txt 2009-09-25 23:58:30.000000000 +0000 DeviceKit-power-011-0.1.20090914git.fc12.i686 -GConf2-2.27.0-1.fc12.i686 -GConf2-gtk-2.27.0-1.fc12.i686 +GConf2-2.28.0-1.fc12.i686 +GConf2-gtk-2.28.0-1.fc12.i686 MAKEDEV-3.24-4.i686 ModemManager-0.2-3.20090826.fc12.i686 -NetworkManager-0.7.996-2.git20090921.fc12.i686 -NetworkManager-glib-0.7.996-2.git20090921.fc12.i686 +NetworkManager-0.7.996-3.git20090921.fc12.i686 +NetworkManager-glib-0.7.996-3.git20090921.fc12.i686 ORBit2-2.14.17-3.fc12.i686 SDL_ttf-2.0.9-6.fc12.i686 -abrt-0.0.9-1.fc12.i686 -abrt-addon-ccpp-0.0.9-1.fc12.i686 -abrt-addon-kerneloops-0.0.9-1.fc12.i686 -abrt-addon-python-0.0.9-1.fc12.i686 -abrt-cli-0.0.9-1.fc12.i686 -abrt-desktop-0.0.9-1.fc12.i686 -abrt-devel-0.0.9-1.fc12.i686 -abrt-gui-0.0.9-1.fc12.i686 -abrt-libs-0.0.9-1.fc12.i686 -abrt-plugin-bugzilla-0.0.9-1.fc12.i686 -abrt-plugin-filetransfer-0.0.9-1.fc12.i686 -abrt-plugin-kerneloopsreporter-0.0.9-1.fc12.i686 -abrt-plugin-logger-0.0.9-1.fc12.i686 -abrt-plugin-mailx-0.0.9-1.fc12.i686 -abrt-plugin-runapp-0.0.9-1.fc12.i686 -abrt-plugin-sosreport-0.0.9-1.fc12.i686 -abrt-plugin-sqlite3-0.0.9-1.fc12.i686 -abrt-plugin-ticketuploader-0.0.9-1.fc12.i686 +abrt-0.0.9-2.fc12.i686 +abrt-addon-ccpp-0.0.9-2.fc12.i686 +abrt-addon-kerneloops-0.0.9-2.fc12.i686 +abrt-addon-python-0.0.9-2.fc12.i686 +abrt-cli-0.0.9-2.fc12.i686 +abrt-desktop-0.0.9-2.fc12.i686 +abrt-devel-0.0.9-2.fc12.i686 +abrt-gui-0.0.9-2.fc12.i686 +abrt-libs-0.0.9-2.fc12.i686 +abrt-plugin-bugzilla-0.0.9-2.fc12.i686 +abrt-plugin-filetransfer-0.0.9-2.fc12.i686 +abrt-plugin-kerneloopsreporter-0.0.9-2.fc12.i686 +abrt-plugin-logger-0.0.9-2.fc12.i686 +abrt-plugin-mailx-0.0.9-2.fc12.i686 +abrt-plugin-runapp-0.0.9-2.fc12.i686 +abrt-plugin-sosreport-0.0.9-2.fc12.i686 +abrt-plugin-sqlite3-0.0.9-2.fc12.i686 +abrt-plugin-ticketuploader-0.0.9-2.fc12.i686 acl-2.2.47-5.fc12.i686 at-3.1.10-37.fc12.i686 -at-spi-1.27.92-1.fc12.i686 -atk-1.27.90-1.fc12.i686 +at-spi-1.28.0-1.fc12.i686 +atk-1.28.0-1.fc12.i686 atlas-sse-3.8.3-9.fc12.i686 bash-4.0.33-1.fc12.i686 -bc-1.06-36.fc12.i686 +bc-1.06.95-1.fc12.i686 bind-libs-9.6.1-11.P1.fc12.i686 constantine-backgrounds-11.90.2-2.fc12.noarch -control-center-2.27.91-6.fc12.i686 -control-center-filesystem-2.27.91-6.fc12.i686 +control-center-2.28.0-9.fc12.i686 +control-center-filesystem-2.28.0-9.fc12.i686 coreutils-7.6-5.fc12.i686 csound-python-5.10.1-12.fc12.i686 -cups-1.4.1-4.fc12.i686 -cups-libs-1.4.1-4.fc12.i686 +cups-1.4.1-5.fc12.i686 +cups-libs-1.4.1-5.fc12.i686 curl-7.19.6-8.fc12.i686 -cyrus-sasl-2.1.23-2.fc12.i686 -cyrus-sasl-lib-2.1.23-2.fc12.i686 -cyrus-sasl-plain-2.1.23-2.fc12.i686 +cyrus-sasl-2.1.23-4.fc12.i686 +cyrus-sasl-lib-2.1.23-4.fc12.i686 +cyrus-sasl-plain-2.1.23-4.fc12.i686 dash-0.5.5.1-3.fc12.i686 desktop-file-utils-0.15-8.fc12.i686 -device-mapper-1.02.37-3.fc12.i686 -device-mapper-event-1.02.37-3.fc12.i686 -device-mapper-event-libs-1.02.37-3.fc12.i686 -device-mapper-libs-1.02.37-3.fc12.i686 +device-mapper-1.02.37-4.fc12.i686 +device-mapper-event-1.02.37-4.fc12.i686 +device-mapper-event-libs-1.02.37-4.fc12.i686 +device-mapper-libs-1.02.37-4.fc12.i686 device-mapper-multipath-0.4.9-5.fc12.i686 device-mapper-multipath-libs-0.4.9-5.fc12.i686 -dhclient-4.1.0p1-10.fc12.i686 +dhclient-4.1.0p1-11.fc12.i686 dirmngr-1.0.3-3.fc12.i686 dosfstools-3.0.1-6.fc12.i686 -dracut-002-4.git23aa2048.fc12.noarch -dracut-kernel-002-4.git23aa2048.fc12.noarch +dracut-002-8.git845dd502.fc12.noarch dump-0.4-0.3.b42.fc12.i686 expat-2.0.1-7.i686 -fedora-gnome-theme-12.2-1.fc12.noarch +fedora-gnome-theme-12.3-1.fc12.noarch fedora-icon-theme-1.0.0-6.fc12.noarch gdbm-1.8.0-33.fc12.i686 -gdm-2.27.90-2.fc12.i686 +gdm-2.28.0-1.fc12.i686 generic-logos-11.0.1-2.fc12.noarch giflib-4.1.6-3.fc12.i686 -glib2-2.22.0-1.fc12.i686 +glib2-2.22.0-3.fc12.i686 glibc-2.10.90-23.i686 gnome-keyring-pam-2.28.0-1.fc12.i686 -gnome-menus-2.28.0-1.fc12.i686 +gnome-menus-2.28.0-2.fc12.i686 gnome-packagekit-2.28.0-1.fc12.i686 -gnome-panel-libs-2.27.92-1.fc12.i686 +gnome-panel-libs-2.28.0-1.fc12.i686 gnome-power-manager-2.28.0-1.fc12.i686 -gnome-python2-2.18.0-1.fc12.i686 -gnome-python2-bonobo-2.18.0-1.fc12.i686 -gnome-python2-canvas-2.18.0-1.fc12.i686 +gnome-python2-2.28.0-1.fc12.i686 +gnome-python2-bonobo-2.28.0-1.fc12.i686 +gnome-python2-canvas-2.28.0-1.fc12.i686 gnome-python2-desktop-2.28.0-1.fc12.i686 gnome-python2-evince-2.28.0-1.fc12.i686 -gnome-python2-gconf-2.18.0-1.fc12.i686 -gnome-python2-gnome-2.18.0-1.fc12.i686 -gnome-python2-gnomevfs-2.18.0-1.fc12.i686 +gnome-python2-gconf-2.28.0-1.fc12.i686 +gnome-python2-gnome-2.28.0-1.fc12.i686 +gnome-python2-gnomevfs-2.28.0-1.fc12.i686 gnome-python2-libwnck-2.28.0-1.fc12.i686 gnome-python2-rsvg-2.28.0-1.fc12.i686 -gnome-session-2.27.92-1.fc12.i686 +gnome-session-2.28.0-1.fc12.i686 gnome-settings-daemon-2.28.0-2.fc12.i686 -gnome-themes-2.27.92-1.fc12.noarch +gnome-themes-2.28.0-1.fc12.noarch gnome-vfs2-2.24.1-9.fc12.i686 gnupg2-2.0.13-1.fc12.i686 -gnutls-2.8.3-1.fc12.i686 +gnutls-2.8.4-1.fc12.i686 +gobject-introspection-0.6.5-1.fc12.i686 google-droid-fonts-common-20090906-4.fc12.noarch gtkmm24-2.17.11-1.fc12.i686 -gtksourceview2-2.7.5-1.fc12.i686 +gtksourceview2-2.8.0-1.fc12.i686 gvfs-1.4.0-1.fc12.i686 kbd-1.15-9.fc12.i686 -kernel-2.6.31-33.fc12.i686 -kernel-firmware-2.6.31-33.fc12.noarch +kernel-2.6.31-40.fc12.i686 +kernel-firmware-2.6.31-40.fc12.noarch keyutils-libs-1.2-6.fc12.i686 libXdamage-1.1.1-9.fc12.i686 -libXdmcp-1.0.2-11.fc12.i686 +libXdmcp-1.0.3-1.fc12.i686 libXext-1.0.99.4-3.fc12.i686 libXinerama-1.0.99.1-1.fc12.i686 -libXmu-1.0.4-5.fc12.i686 +libXmu-1.0.5-1.fc12.i686 libXrandr-1.3.0-3.fc12.i686 libblkid-2.16-10.fc12.i686 -libbonobo-2.24.1-4.fc12.i686 -libbonoboui-2.24.1-3.fc12.i686 +libbonobo-2.24.2-1.fc12.i686 +libbonoboui-2.24.2-1.fc12.i686 libcanberra-0.18-1.fc12.i686 libdmx-1.0.99.1-1.fc12.i686 -libdrm-2.4.12-0.10.fc12.i686 +libdrm-2.4.14-1.fc12.i686 libdv-1.0.0-8.fc12.i686 libgail-gnome-1.20.1-4.fc12.i686 -libgcc-4.4.1-15.i686 +libgcc-4.4.1-16.i686 libgcrypt-1.4.4-8.fc12.i686 -libgfortran-4.4.1-15.i686 +libgfortran-4.4.1-16.i686 libglade2-2.6.4-3.fc12.i686 -libgnome-2.27.5-1.fc12.i686 +libgnome-2.28.0-1.fc12.i686 libgnomecanvas-2.26.0-2.fc12.i686 -libgnomekbd-2.27.91-1.fc12.i686 +libgnomekbd-2.28.0-1.fc12.i686 libgnomeui-2.24.1-3.fc12.i686 libgssglue-0.1-8.fc12.i686 -libgudev1-145-7.fc12.i686 -libgweather-2.27.92-1.fc12.i686 +libgudev1-145-8.fc12.i686 +libgweather-2.28.0-1.fc12.i686 libical-0.43-5.fc12.i686 liboil-0.3.16-4.fc12.i686 -libpcap-1.0.0-2.20090716git6de2de.fc12.i686 -libpciaccess-0.10.6-7.fc12.i686 +libpcap-1.0.0-3.20090922gite154e2.fc12.i686 +libpciaccess-0.10.9-1.fc12.i686 libpng-1.2.39-1.fc12.i686 libssh2-1.2-2.fc12.i686 -libstdc++-4.4.1-15.i686 +libstdc++-4.4.1-16.i686 libtasn1-2.3-1.fc12.i686 libtool-ltdl-2.2.6-13.fc12.i686 -libudev-145-7.fc12.i686 +libudev-145-8.fc12.i686 libusb-0.1.12-22.fc12.i686 libxklavier-4.0-4.fc12.i686 -libxml2-2.7.4-2.fc12.i686 -libxml2-python-2.7.4-2.fc12.i686 -libxslt-1.1.25-2.fc12.i686 +libxml2-2.7.5-1.fc12.i686 +libxml2-python-2.7.5-1.fc12.i686 +libxslt-1.1.26-1.fc12.i686 link-grammar-4.3.5-5.fc12.i686 lua-5.1.4-4.fc12.i686 -lvm2-2.02.52-3.fc12.i686 -lvm2-libs-2.02.52-3.fc12.i686 +lvm2-2.02.52-4.fc12.i686 +lvm2-libs-2.02.52-4.fc12.i686 lx-20030328-5.fc12.i686 net-tools-1.60-95.fc12.i686 -newt-0.52.10-4.fc12.i686 -newt-python-0.52.10-4.fc12.i686 -nfs-utils-1.2.0-11.fc12.i686 +newt-0.52.11-1.fc12.i686 +newt-python-0.52.11-1.fc12.i686 +nfs-utils-1.2.0-12.fc12.i686 nfs-utils-lib-1.1.4-8.fc12.i686 nodoka-metacity-theme-0.3.90-4.fc12.noarch -notification-daemon-0.4.0-8.fc12.i686 -notification-daemon-engine-nodoka-0.1.0-11.fc12.i686 +notification-daemon-0.4.1-0.20090923.2.fc12.i686 +notification-daemon-engine-slider-0.1.0-1.fc12.i686 nscd-2.10.90-23.i686 nss-3.12.4-9.fc12.i686 -nss-softokn-3.12.4-9.fc12.i686 -nss-softokn-freebl-3.12.4-9.fc12.i686 +nss-softokn-3.12.4-10.fc12.i686 +nss-softokn-freebl-3.12.4-10.fc12.i686 nss-util-3.12.4-8.fc12.i686 openjpeg-libs-1.3-6.fc12.i686 -openldap-2.4.18-1.fc12.i686 -openssh-5.2p1-26.fc12.i686 -openssh-askpass-5.2p1-26.fc12.i686 -openssh-clients-5.2p1-26.fc12.i686 -openssh-server-5.2p1-26.fc12.i686 +openldap-2.4.18-3.fc12.i686 +openssh-5.2p1-28.fc12.i686 +openssh-askpass-5.2p1-28.fc12.i686 +openssh-clients-5.2p1-28.fc12.i686 +openssh-server-5.2p1-28.fc12.i686 openssl-1.0.0-0.7.beta3.fc12.i686 pcre-7.8-3.fc12.i686 -perf-2.6.31-33.fc12.noarch +perf-2.6.31-40.fc12.noarch perl-5.10.0-82.fc12.i686 pygame-1.8.1-7.fc12.i686 -pygobject2-2.18.0-2.fc12.i686 +pygobject2-2.20.0-1.fc12.i686 pygpgme-0.1-16.20090824bzr68.fc12.i686 pygtk2-libglade-2.16.0-1.fc12.i686 -pygtksourceview-2.7.0-1.fc12.i686 +pygtksourceview-2.8.0-1.fc12.i686 pyorbit-2.24.0-4.fc12.i686 python-simplejson-2.0.9-3.fc12.i686 -python-slip-0.2.4-1.fc12.noarch -python-slip-dbus-0.2.4-1.fc12.noarch -python-slip-gtk-0.2.4-1.fc12.noarch +python-slip-0.2.5-1.fc12.noarch +python-slip-dbus-0.2.5-1.fc12.noarch +python-slip-gtk-0.2.5-1.fc12.noarch python-telepathy-0.15.11-1.fc12.noarch pyxf86config-0.3.37-7.fc12.i686 -ql2100-firmware-1.19.38-3.fc12.noarch -ql2200-firmware-2.02.08-3.fc12.noarch -ql23xx-firmware-3.03.27-3.fc12.noarch -ql2400-firmware-4.04.09-1.fc12.noarch ql2500-firmware-4.04.09-1.fc12.noarch readline-6.0-3.fc12.i686 -redhat-menus-10.0.1-4.fc12.noarch +redhat-menus-12.0.1-1.fc12.noarch rmt-0.4-0.3.b42.fc12.i686 shadow-utils-4.1.4.2-1.fc12.i686 -shared-mime-info-0.60-4.fc12.i686 +shared-mime-info-0.60-5.fc12.i686 slang-2.2.1-1.fc12.i686 sugar-0.85.8-2.fc12.i686 -sugar-artwork-0.85.4-2.fc12.i686 +sugar-artwork-0.86.0-1.fc12.i686 sugar-base-0.85.6-1.fc12.i686 tcp_wrappers-libs-7.6-56.fc12.i686 -tcpdump-4.0.0-2.20090818git832d2c.fc12.i686 +tcpdump-4.0.0-3.20090921gitdf3cb4.fc12.i686 telepathy-filesystem-0.0.2-1.fc12.noarch telepathy-gabble-0.8.3-1.fc12.i686 -telepathy-glib-0.7.37-1.fc12.i686 +telepathy-glib-0.8.0-1.fc12.i686 telepathy-salut-0.3.10-1.fc12.i686 tree-1.5.2.2-4.fc12.i686 -tzdata-2009m-1.fc12.noarch -udev-145-7.fc12.i686 +tzdata-2009m-2.fc12.noarch +udev-145-8.fc12.i686 unique-1.1.2-1.fc12.i686 xorg-x11-drv-elographics-1.2.3-4.fc12.i686 -xorg-x11-drv-evdev-2.2.99-7.20090909.fc12.i686 +xorg-x11-drv-evdev-2.2.99-8.20090923.fc12.i686 xorg-x11-drv-fbdev-0.4.1-1.fc12.i686 xorg-x11-drv-i740-1.3.2-1.fc12.i686 -xorg-x11-drv-intel-2.8.0-15.20090909.fc12.i686 +xorg-x11-drv-intel-2.8.0-16.20090909.fc12.i686 xorg-x11-drv-keyboard-1.3.99.1-1.fc12.i686 ypbind-1.20.4-19.fc12.i686 -yum-3.2.24-5.fc12.noarch +yum-3.2.24-6.fc12.noarch yum-metadata-parser-1.1.2-14.fc12.i686 How to get it: ------------- Download from http://people.sugarlabs.org/~mtd/soas Caveats/Known Issues: Please reply or comment on the Fedora/Redhat bug report if you see any of these. - XO-1 camera not recognised in Record / Cheese https://bugzilla.redhat.com/show_bug.cgi?id=498900 - XO-1 SD boots sometimes fail (mount: unknown filesystem type: 'jffs2') https://bugzilla.redhat.com/show_bug.cgi?id=500196 Before reporting bugs, it'd be nice if one could search the fedora bugzilla; start with this bug: https://bugzilla.redhat.com/show_bug.cgi?id=461806 Quickstart: ---------- either: copy-nand u:\soas??xo.img or: (2g or larger removable) cat soas??xo.4gremovable.tar.lzma | lzma -dc - | tar xf - -O > /dev/sdX or: (4g or larger removable) cat soas??xo.2gremovable.tar.lzma | lzma -dc - | tar xf - -O > /dev/sdX Installation instructions: ------------------------- http://people.sugarlabs.org/~mtd/soas/README.txt Files: ----- soas68.iso - iso9990 file system (for use with livecd-iso-to-disk) soas68.tree.tar.lzma - for hacking soas68xo.img - for ... soas68xo.crc - ... copy-nand'ing soas68xo.plc - ... NANDblast'ing soas68.4gremovable.img.tar.lzma - for simply writing to 4 gig removable devices: cat soas68.4gremovable.tar.lzma | lzma -dc - | tar xf - -O > /dev/sdX soas68.2gremovable.img.tar.lzma - for simply writing to 2 gig removable devices: cat soas68.2gremovable.tar.lzma | lzma -dc - | tar xf - -O > /dev/sdX Build date: Sat Sep 26 02:57:04 UTC 2009 From martin at martindengler.com Sat Sep 26 03:52:58 2009 From: martin at martindengler.com (Martin Dengler) Date: Sat, 26 Sep 2009 04:52:58 +0100 Subject: New SoaS build soas68 In-Reply-To: <200909260324.n8Q3OHjQ011969@buildslave-fedora-11-32bit.sugarlabs.org> References: <200909260324.n8Q3OHjQ011969@buildslave-fedora-11-32bit.sugarlabs.org> Message-ID: <20090926035258.GN14643@ops-13.xades.com> On Sat, Sep 26, 2009 at 03:24:17AM +0000, Martin Dengler wrote: > > New Sugar-on-a-Stick build soas68 is available. > [...] This is the SoaS-on-XO-1 build announcement - sorry for the ambiguity in the subject/wording and any resultant confusion. The git trunk announcer's language is in flux and I didn't pay close attention to it before sending. I will fix the ambiguity after discussing with Sebastian. Martin -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From mikus at bga.com Sat Sep 26 06:01:47 2009 From: mikus at bga.com (Mikus Grinbergs) Date: Sat, 26 Sep 2009 02:01:47 -0400 Subject: New SoaS build soas68 Message-ID: <4ABDAE4B.2080006@bga.com> Did copy-nand of soas68xo.img to my XO-1. Tried to boot. No X. The initial boot gets as far as a screen with a "plaza pavement" background and a login window in the center saying "Automatically logging in ...". Nothing more happens (I waited an hour, just in case it was installing Activities, or something). [I can select "Language" and "Keyboard" - but that doesn't help.] X is stuck. [Nothing that looks wrong in /var/log.] > This is the SoaS-on-XO-1 build announcement I can get into a text console (alt-ctl-F2) -- but for me. trying to run from soas68xo.img on an XO-1 is a failure. mikus From danceswithcars at gmail.com Sat Sep 26 07:53:58 2009 From: danceswithcars at gmail.com (DancesWithCars) Date: Sat, 26 Sep 2009 03:53:58 -0400 Subject: XO Special interest group at Sugar Labs In-Reply-To: <666336.72153.qm@web65513.mail.ac4.yahoo.com> References: <666336.72153.qm@web65513.mail.ac4.yahoo.com> Message-ID: more inline and reviewing, highlighting/ commenting on the original posting/ thread below that... On Thu, Sep 24, 2009 at 9:22 AM, Yioryos Asprobounitis wrote: > > > --- On Thu, 9/24/09, DancesWithCars wrote: > >> From: DancesWithCars >> Subject: Re: XO Special interest group at Sugar Labs >> To: "Yioryos Asprobounitis" >> Cc: fedora-olpc-list at redhat.com, "David Farning" , "iaep" >> Date: Thursday, September 24, 2009, 6:45 AM >> I'm not sure about the hardware >> issues >> mentioned below, as new to some of these lists, >> but if there is an installed base of XO-1 computers >> with special hardware like the touchpad >> with 2 extra areas that were never implemented, >> why not develop applications for those, >> even if the XO-1.5 and XO-2 plans don't >> include them? >> >> What are you going to tell the kids >> with XO-1s when the XO-1.5 come out? >> What is the consolation prize? >> Knowing more about it, and >> being further up the learning curve? >> Note: Nothing mentioned on new hardware and have/ vs. have nots on that?... >> Also, the battery issues will get worse, >> as the hardware gets older, so testing >> and determining when need new battery, >> as a computer without power isn't much >> fun. >> Batteries, as my first laptop has problems years later with the battery (flashing red), and replacements not currently/ easily available, and a 5 yo Nikon CoolPix 4300 camera that the 2 Gig Compact Flash memory card is not available much anymore, as it's too small size to be considered, (Salesman: 4 Gig+ is better, must be able to use that, Me: No, not really. Salesman: Faster speed better? Me: No, not supported, so why pay for that? Salesman/Manager: Not comparable, so not a 1-to-1 swap replacement for cost/ raincheck) and stores want to force me to get a new camera instead of the supplies I went in for, i.e. snotty sales/ register people making others wait in line [i.e. look how difficult he is being making all the others in line wait, when small local brand memory stuff is only available at the counter...], and all... But I rant on MicroCenter in the Washington DC area... But it is an industry thing even here in supposedly 1st world where everyone is supposedly rich and should be donors only, not receipients (OLPC USA???) (but by comparison to $50 USD/ year per capita annual income, though consider cost of living here...) >> Repairing hardware gets more crucial >> as machines get older. >> Try finding i386 PC-100 memory, or getting delivery on an XO touchpad without it being so late as to be useless, being shorted on the order from XOExplosion.com and non responsive to a certified letter and phone doesn't work, and email rarely... >> Being more inventive with what you have >> instead of this is the shiny new machine, >> so going deeper into the system, >> maybe programming instead of just >> using.? Or more time with the learning >> content. >> >> Even as a ebook reader, getting new >> content, creating new content, >> maybe more translating content? >> >> I still think flossmanuals.net >> needs indexing and other layout stuff, >> under the hood, or however parallel, >> LyX makes some assumptions, >> and does some of that but not >> the wiki and social stuff up top, >> so [La]TeX classes and styles might be >> a good contribution, finding >> objavi and booki source code, >> etc... >> > > These are all very valid points. However, is not clear to me if you imply that they should be prioritized over the updating of the os/sugar or not. Getting something on a list of features/ requirements is probably the first step, then prioritizing, when we can a;; see what the whole list looks like, available resources (time, skill, man/woman/kid power, etc), ... > I hope not since some of these may even benefit from an updated OS (touchpad, battery, other hardware related patches) as opposed to an unsupported one (Fedora 9). Fedora seems to be on a 6 month development cycle. The OLPC/ SugarLabs split plus OLPC SW dev team cutbacks seems to have effected the published timeline(s) greatly... So maybe determining the timeline would be a good first step. Suggesting an F-Odd release cycle? Backporting anything critical, security wise, and keeping repos online for the full year+ XO/Sugar cycle, if not longer? Usenet/ UUNet store and forward seems like an interesting technology to push updates into remote areas. Can an XO/Sugar machine actually share files? Activity / kernel/ rpm / repo saved on local machine / SD/ USB and easily update the others when meshing/ if approved by local neighbor(s) vs w/o whole mesh entire reflash image?? i.e. incrementals instead of full refresh? Sugar has a large installed base on XO/ Fedora, and seems like it's not a Special Interest (i.e. subgroup) but the largest part so far, and relegating it to junior status, is demeaning. Development (most people here are probably developers? no?) is important, but serving the customer base instead of orphaning them is also important... > On the other hand being a voluntary process is hard to tell to people "you do this instead of that". You can certainly try to convince them, and I think you do a good job on that :-) > I can voice my opinion, but others are free to disagree... Usually what we call a democracy, but I'm not sure if you prefer a meritocracy (those who do the work get to determine how others live)?? >> The requirements for testing a new build >> is some extra XO-n hardware for testing, >> and a high speed connection, if giving >> new .isos builds out to the world, >> or access to some place that would, >> plus the time and knowledge to >> make the changes, find bugs, >> report them, etc. > > Again I'm not sure what this means. That is trivial? That a "beta" quality OS should be delivered to the students/deployments and let them debug it? Other? > Less impossible (topic was trivial), if supported. I didn't say a beta quality, but you (original poster) seem to want us to just be testers, so if you have to have an RT account, join a Gang (interpreted differently here when 6 surround me at MetroRail and want my stuff, i.e bike/ computer, etc), get flooded with list emails just to report a bug/ process issue (i.e. put a form on the Sugar interface and have it store and forward when connected? bottom up instead of top down, creating feedback all the way down from kids/ users) then the users of the software get to report stuff, and it reported multiply, then filter it out/ condense symptoms/ merge into better reports, and prioritize by User counts?... Filters can sort out if the poster is a minor, redact certain stuff, etc. i.e. 30 kids reported a problem with Z. Must be worth looking into. Local school admins not figuring it out, maybe they need some support on that? >> >> And if 'It's An Eduction Project" >> are we teaching self reliance >> and how to do builds, make your >> own constructionist style or >> whatever teaching paradigm fits >> the locals?? Or forcing dependence >> upon others? > > Again trying to read between the lines... Not always good to do when I'm pissed about ClassActs and writing in response to that... ;-/ Or writing in the middle of the night with little sleep, but this thread is getting messy... > I'm sure that "locals" have their hands full trying to make the best of the available hardware/software, adapt it to their needs and build their own apps when needed. So you don't think 'locals' are capable human beings?? That's the attitude I've gotten from OLPC... Not as much from a Red Hat visit. With their//our own customs and traditions that seem to work for things We/they already encounter, until a little XO is introduced/ [or forced, in some cases, as some teachers/ admins might not want it...] Some organizations can't modify a kernel locally? Create operating systems/ applications? Translate English based dominance to local languages? A Finland grad student started Linux, not the US. And not M$. But FSF and GNU and many others added to it... Even in the USA, MIT arrogance is pissing me off. We 'locals' can host a book sprint, and be treated like shit, not heard, not worthy of a visit from NN, WB, etc as Congress / funding is the Only priority, but not good enough to write/ be published (in ClassActs), must less vote on things that effect us (SLOB)? > I would also guess that if the current Fedora 9-based OS is a blocker to paramount needs they may try to update it themselves. See the talk on the wiki.laptop.org F11forXO1 about some git commands and the 'we are not going to do it, but it's easy' type of tone, and then see if you can do it from what was provided... > However, providing a better option as the F11/Sugar0.84+ is, in no way is in contrast with the "educational project". > For one is _not_ a "computer education" project. Isn't anything done on a computer, a computer education project? ;-/ But most people don't look under the hood of their cars (those that own cars...) > So "upgrade your OS", is by no means a priority. Install or develop? Remix the kernel modules? > Is welcome, but in no way required. > Expecting a 9-12 years old on the other hand to come up with the solutions is conceivable but nothing to depend on, either. You might be surprised what 9-12 yos can do, but there are also high schools, colleges, administrators, teachers and community members and over the lifecycle of the project, kids starting out on XO's might want to graduate to hacking kernels, and going upstream, so to speak, with support instead of fighting the attitude that they are not good enough to do that... > Finally the fact that if you give someone a fishing pole will eat fish all his/her life, does not preclude that you can not give them a fishing boat to get bigger fish, nor it implies they should built one. Giving someone *the first* fishing pole (G1G1 Donor) does not mean that that once introduced to fishing, they cannot try making a fishing pole locally once seen... Or better yet, adapt the pole to the type of waters locally. Fishing off a dock / pier is one thing, in a stream, another, and in the ocean, requires something else entirely... Not to mentioned bait... [humorous analogy to herding cats somewhere in here] > They may as well build a boat by themselves but the goal here is to get as much and as good fish as possible given the needs. Since we are talking fishing, is that for sport or to survive? Here in the USA, many people are recreational fisherman/women/kids. And some poor/ homeless in the city, that is the only way they get food/ fresh fish, but the rivers are polluted, though better after the 1970's, but I'd guess here in Washington,DC somewhat still polluted and mercury (+whatever) poisoned. > Finally self reliance is an important factor. Respect is important too. > However like everything else in teaching it must be build gradually, in the right order and by experience. Assigning tasks that will be never completed guaranties that you will build self depreciation rather than self reliance. > And as you said "is an educational project". > > If I read your comments wrong, my apologies. > Well, you actually read them :-) and stated what you heard, so I'm responding, even if late, and still pissed about ClassActs/ FlossManuals.net Index/ LyX/ LaTeX stuff. Tux.org people were _involved_ in the ClassActs, but not even listed on the poster, t-shirt, invited to meet NN, WB, etc... And if Sugar is to be truely cross platform, then it might want people who are involved in other distros (Ubuntu, YellowDog, etc )/ hardware (Apple Mac, Sun?, etc) plus the whole user community instead of just developers (see criteria for SL membership)... And most old hardware don't boot from USB (64 bit laptop w battery issue mentioned above), and really old stuff doesn't boot from CDR (Beige G3, and P1 class machines, i.e. stuff people give away/ trash locally...), much less support virtualization (even 1st Gen 64 bit Averatec and this 64 bit desktop doesn't have the real cpu chip support)... >> >> My $.02 USD - costs of ownership/ >> && giving back. >> >> On Tue, Sep 22, 2009 at 12:33 PM, Yioryos Asprobounitis >> >> wrote: >> > Now, that's an excellent idea! >> > However, the crucial thing before any extensive >> building/testing starts is to address some major issues that >> would stop most people from using/testing F11/Sugar.84+. >> Namely the Xorg geode video driver, the camera and the battery monitor. >> These will primarily need developers. >> > Having these components in place then a daily build >> bug fixing/reporting system would be more valuable since >> more people may be willing to give it a try, identifying the >> "minor" issues that may eventually allow a >> deployment-quality release. >> > If this is going to be an OLPC, Fedora or SL project, >> I think is irrelevant. XO-1 is an EOL machine that runs an >> OS/UI developed by "some other" organization. Is literally >> orphan (besides these limited efforts) so any "adopter" >> should be welcome. Whoever sets it up should be good to go. >> With almost a million users is the biggest educational >> linux/sugar implementation and worths every attention. >> > >> > --- On Mon, 9/21/09, David Farning >> wrote: >> > >> >> From: David Farning >> >> Subject: Re: XO Special interest group at Sugar >> Labs >> >> To: fedora-olpc-list at redhat.com >> >> Cc: "iaep" >> >> Date: Monday, September 21, 2009, 7:36 PM >> >> On Mon, Sep 21, 2009 at 3:41 PM, >> >> Peter Robinson >> >> wrote: >> >> > Hi David, >> >> > >> >> > On Mon, Sep 21, 2009 at 7:48 PM, David >> Farning >> >> wrote: >> >> >> For the past several months the >> OLPC/Sugar Labs >> >> ecosystem has been >> >> >> getting requests to provide releases of >> more >> >> recent versions of Sugar >> >> >> on the XO. >> >> >> >> >> >> The leading effort in this direction >> seems to be >> >> the F11-XO1 project. >> >> >> I would like to like to invite F11-XO1 to >> become >> >> part of the XO SIG. >> >> >> I have been trying to articulate the >> project goals >> >> and gather momentum >> >> >> across several groups. >> >> >> 1. ?OLPC as a downstream. as posted by SL >> >> >> 2. Sugar Labs as a focus point. as posted by SL >> >> >> 3. Various ecosystem leaders to do pilots >> with >> >> current versions of Sugar on XOs. near as I can tell OLPC doesn't do Pilots, they expect results only, at least in the contributor program. >> >> >> 4. Various testers to provide user level >> testing. User level testing on the kernel??? Or Sugar? Or Activities? Or the whole Gestalt? >> >> >> >> >> >> The goal of this groups is not to >> _fragment_ the >> >> existing efforts. >> >> >> The goal is bring the various efforts >> together to >> >> form a critical mass >> >> >> to help pull this propel forward. >> >> > >> >> > As far as I'm aware there is no F11-XO1 >> project, I'm >> >> aware of a couple >> >> > of different projects to get the latest Sugar >> releases >> >> on the XO. >> >> > - The SoaS on XO which is being run my Martin >> Dengler >> >> in conjunction >> >> > with SoaS and SL (that's where its all >> hosted). >> >> > - The OLPC project to get Fedora 11 on both >> the XO-1.5 >> >> and XO-1 which >> >> > is being handled by Steven M. Parrish (and >> Daniel >> >> Drake / Chris Ball) >> >> >> >> This confusion is part of what I am hoping to >> clear up by >> >> create a >> >> single clearly defined project. >> >> >> >> I have heard back from many of the people working >> on the >> >> various >> >> projects. the work flow seems to be: >> >> 1. Sugar development team creates platform. >> >> 2. Fedora packagers package Sugar... and >> everything else >> >> required to >> >> make a disto. >> >> 3a. SoaS takes packages and turns them into a Soas >> image. >> >> 3b. Soas is getting pretty well test via test days >> and >> >> deployments >> >> such as the GPA. >> >> 4a. Steven take the Fedora packages adds the XO >> specific >> >> bit and turns >> >> them into xo builds. >> >> 4b. limited testing for xo builds. >> >> >> >> Because of time restrictions, the F11 on XO effort >> seems to >> >> be >> >> reactive.? They take the output from cjb and the >> >> fedora packages and >> >> create builds.? I believe that the XO SIG could >> help >> >> generate interest >> >> and attract more developers and testers to the >> project. >> >> >> >> > Both projects are cross pollinated and use >> components >> >> of work done by >> >> > both as well as myself and other Fedora >> upstream >> >> people. I don't >> >> > believe there's much difference between them >> as where >> >> possible I >> >> > believe most stuff is pushed upsteam. There >> is no >> >> current Fedora based >> >> > project working on this directly due to the >> down >> >> stream projects. >> >> > >> >> > I have my own build that I use but that >> isn't >> >> generally published and >> >> > is mostly to test core fedora for dependency >> bloat and >> >> breakages. >> >> >> >> Would it be useful if we started by combining your >> work and >> >> Stevens >> >> into an automatic build system.? This could help >> >> identify breakages. >> >> Then we could create a release cycle of alpha and >> beta and >> >> final >> >> releases. >> >> >> >> By creating the daily builds and widely >> broadcasting the >> >> various >> >> releases, we can engage a larger community of >> testers. >> >> >> >> david >> >> >> >> _______________________________________________ >> >> Fedora-olpc-list mailing list >> >> Fedora-olpc-list at redhat.com >> >> https://www.redhat.com/mailman/listinfo/fedora-olpc-list >> >> >> > >> > >> > >> > >> > _______________________________________________ >> > Fedora-olpc-list mailing list >> > Fedora-olpc-list at redhat.com >> > https://www.redhat.com/mailman/listinfo/fedora-olpc-list >> > >> >> >> >> -- >> DancesWithCars >> leave the wolves behind ;-) >> > > > > -- DancesWithCars leave the wolves behind ;-) From mavrothal at yahoo.com Sat Sep 26 10:24:19 2009 From: mavrothal at yahoo.com (Yioryos Asprobounitis) Date: Sat, 26 Sep 2009 03:24:19 -0700 (PDT) Subject: New SoaS build soas68 In-Reply-To: <20090926035258.GN14643@ops-13.xades.com> Message-ID: <662541.57260.qm@web65502.mail.ac4.yahoo.com> I tried soas68.2gremovable.img.tar.lzma on a 2GB USB stick. It did not work. /boot folder does not have an olpc.fth file so did not go anywhere. I added the following olpc.fth file in /boot ============ \ olpc.fth " root=/dev/sda1 rootfstype=ext2 console=ttyS0,115200 console=tty0 fbcon=font:SUN12x22" to boot-file " disk:\boot\vmlinuz" to boot-device " disk:\boot\initrd.img" to ramdisk setup-smbios unfreeze dcon-unfreeze visible boot =========== and got in the boot console: dracut: Mounted root filesystem /dev/sda1 dracut Warning: Machine in enforcing mode and cannot execute load_policy dracut Warning: To disable selinux, add selinux=0 to the kernel command line dracut Warning: Not confirming (All of them twice) at which point the boot stoped Changing the rootfstype to ext4 gave the same result while changing to ext3 said ?wrong filesystem?. By the way the /boot permissions are 555. So I had to change them to add the olpc.fth file and the relevant simlinks so boot will work. --- On Fri, 9/25/09, Martin Dengler wrote: > From: Martin Dengler > Subject: Re: New SoaS build soas68 > To: sugar-devel at lists.sugarlabs.org, fedora-olpc-list at redhat.com > Date: Friday, September 25, 2009, 11:52 PM > On Sat, Sep 26, 2009 at 03:24:17AM > +0000, Martin Dengler wrote: > > > > New Sugar-on-a-Stick build soas68 is available. > > [...] > > This is the SoaS-on-XO-1 build announcement - sorry for the > ambiguity > in the subject/wording and any resultant confusion.? > The git trunk > announcer's language is in flux and I didn't pay close > attention to it > before sending. > > I will fix the ambiguity after discussing with Sebastian. > > Martin > > -----Inline Attachment Follows----- > > _______________________________________________ > Fedora-olpc-list mailing list > Fedora-olpc-list at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-olpc-list From mavrothal at yahoo.com Sat Sep 26 11:01:32 2009 From: mavrothal at yahoo.com (Yioryos Asprobounitis) Date: Sat, 26 Sep 2009 04:01:32 -0700 (PDT) Subject: XO Special interest group at Sugar Labs In-Reply-To: Message-ID: <169656.79153.qm@web65502.mail.ac4.yahoo.com> This is getting _very_ complicated/confusing with references to unclear to me issues. would be better if in a different post you code your reasons for _not_ forming a SIG. eg what is the harm per se, not as oppose to something else. Then in another post what, OLPC, SL, others should be doing about the XO-1/Sugar installed base. I thing that these will get your messages much better across. So for now I'll just "answer" some misunderstanding-derived questions. No, I do not prefer meritocracy. (how did you come up with this?) No, I think that "locals" are very capable but have other priorities.(I even said so originally) Best --- On Sat, 9/26/09, DancesWithCars wrote: > From: DancesWithCars > Subject: Re: XO Special interest group at Sugar Labs > To: "Yioryos Asprobounitis" > Cc: fedora-olpc-list at redhat.com, "David Farning" , "iaep" > Date: Saturday, September 26, 2009, 3:53 AM > more inline > > and reviewing, highlighting/ commenting on the original > posting/ thread below that... > > > On Thu, Sep 24, 2009 at 9:22 AM, Yioryos Asprobounitis > > wrote: > > > > > > --- On Thu, 9/24/09, DancesWithCars > wrote: > > > >> From: DancesWithCars > >> Subject: Re: XO Special interest group at Sugar > Labs > >> To: "Yioryos Asprobounitis" > >> Cc: fedora-olpc-list at redhat.com, > "David Farning" , > "iaep" > >> Date: Thursday, September 24, 2009, 6:45 AM > >> I'm not sure about the hardware > >> issues > >> mentioned below, as new to some of these lists, > >> but if there is an installed base of XO-1 > computers > >> with special hardware like the touchpad > >> with 2 extra areas that were never implemented, > >> why not develop applications for those, > >> even if the XO-1.5 and XO-2 plans don't > >> include them? > >> > >> What are you going to tell the kids > >> with XO-1s when the XO-1.5 come out? > >> What is the consolation prize? > >> Knowing more about it, and > >> being further up the learning curve? > >> > > Note: Nothing mentioned on new hardware > and have/ vs. have nots on that?... > > >> Also, the battery issues will get worse, > >> as the hardware gets older, so testing > >> and determining when need new battery, > >> as a computer without power isn't much > >> fun. > >> > > Batteries, as my first laptop has problems > years later with the battery (flashing red), > and replacements not currently/ easily available, > and a 5 yo Nikon CoolPix 4300 camera that the > 2 Gig Compact Flash memory card is not available > much anymore,? as it's too small size to be > considered, > (Salesman: 4 Gig+ is better, must be able to use that, > Me: No, not really. > Salesman: Faster speed better? > Me: No, not supported, so why pay for that? > Salesman/Manager: Not comparable, > so not a 1-to-1? swap replacement for cost/ > raincheck) > and stores want to force me > to get a new camera instead of the supplies > I went in for, i.e. snotty sales/ register people > making others wait in line [i.e. look how difficult > he is being making all the others in line wait, > when small local brand memory stuff is only > available at the counter...], and all... > > But I rant on MicroCenter in the Washington DC > area...? But it is an industry thing even here > in supposedly 1st world where everyone > is supposedly rich and should be donors > only, not receipients (OLPC USA???) > (but by comparison to? $50 USD/ year > per capita annual income, > though consider cost of living here...) > > >> Repairing hardware gets more crucial > >> as machines get older. > >> > > Try finding i386 PC-100 memory, > or getting delivery on an XO touchpad > without it being so late as to be useless, > being shorted on the order > from XOExplosion.com and non responsive > to a certified letter and phone doesn't work, > and email rarely... > > >> Being more inventive with what you have > >> instead of this is the shiny new machine, > >> so going deeper into the system, > >> maybe programming instead of just > >> using.? Or more time with the learning > >> content. > >> > >> Even as a ebook reader, getting new > >> content, creating new content, > >> maybe more translating content? > >> > >> I still think flossmanuals.net > >> needs indexing and other layout stuff, > >> under the hood, or however parallel, > >> LyX makes some assumptions, > >> and does some of that but not > >> the wiki and social stuff up top, > >> so [La]TeX classes and styles might be > >> a good contribution, finding > >> objavi and booki source code, > >> etc... > >> > > > > These are all very valid points. However, is not clear > to me if you imply that they should be prioritized over the > updating of the os/sugar or not. > > Getting something on a list of features/ requirements > is probably the first step, then prioritizing, when we can > a;; see what the whole list looks like, available > resources (time, skill, man/woman/kid power, etc), ... > > > > I hope not since some of these may even benefit from > an updated OS (touchpad, battery, other hardware related > patches) as opposed to an unsupported one (Fedora 9). > > Fedora seems to be on a 6 month development > cycle.? The OLPC/ SugarLabs split plus OLPC > SW dev team cutbacks seems to have effected > the published timeline(s) greatly... > > So maybe determining the timeline would be a > good first step.???Suggesting an F-Odd > release > cycle?? Backporting anything critical, security > wise, and keeping repos online for the full > year+ XO/Sugar cycle, if not longer? > > Usenet/ UUNet store and forward seems like an > interesting technology to push updates > into remote areas. > > Can an XO/Sugar machine actually share files? > Activity / kernel/ rpm / repo saved on local machine / > SD/ USB and easily update the others when meshing/ > if approved by local neighbor(s) > vs w/o whole mesh entire reflash image?? > i.e. incrementals instead of full refresh? > > Sugar has a large installed base on XO/ > Fedora, and seems like it's not a Special Interest > (i.e. subgroup) but the largest part so far, > and relegating it to junior status, is demeaning. > > Development (most people here are probably > developers? no?) is important, but serving > the customer base instead of orphaning > them is also important... > > > On the other hand being a voluntary process is hard to > tell to people "you do this instead of that". You can > certainly try to convince them, and I think you do a good > job on that :-) > > > I can voice my opinion, but others are free to disagree... > > Usually what we call a democracy, but I'm not sure > if you prefer a meritocracy (those who do the work > get to determine how others live)?? > > >> The requirements for testing a new build > >> is some extra XO-n hardware for testing, > >> and a high speed connection, if giving > >> new .isos builds out to the world, > >> or access to some place that would, > >> plus the time and knowledge to > >> make the changes, find bugs, > >> report them, etc. > > > > Again I'm not sure what this means. That is trivial? > That a "beta" quality OS should be delivered to the > students/deployments and let them debug it? Other? > > > Less impossible (topic was trivial), if supported. > I didn't say a beta quality, but you (original poster) > seem to want us to just be testers, so > if you have to have an RT account, > join a Gang (interpreted differently here when > 6 surround me at MetroRail and want my stuff, > i.e bike/ computer, etc), get flooded > with list emails just to report a bug/ process issue > (i.e. put a form on the Sugar interface and have it > store and forward when connected? > bottom up instead of top down, > creating feedback all the way down from kids/ users) > then the users of the software get to report > stuff, and it reported multiply, then filter it out/ > condense symptoms/ merge into better reports, > and prioritize by User counts?... > > Filters can sort out if the poster is a minor, > redact certain stuff, etc.? i.e. 30 kids reported > a problem with Z.? Must be worth looking into. > Local school admins not figuring it out, maybe > they need some support on that? > > > >> > >> And if 'It's An Eduction Project" > >> are we teaching self reliance > >> and how to do builds, make your > >> own constructionist style or > >> whatever teaching paradigm fits > >> the locals?? Or forcing dependence > >> upon others? > > > > Again trying to read between the lines... > > Not always good to do when I'm pissed > about ClassActs and writing in response > to that... ;-/ > > Or writing in the middle of the night > with little sleep, but this thread is getting > messy... > > > > I'm sure that "locals" have their hands full trying to > make the best of the available hardware/software, adapt it > to their needs and build their own apps when needed. > > So you don't think 'locals' are capable human beings?? > > That's the attitude I've gotten from OLPC... > Not as much from a Red Hat visit. > > With their//our own customs and traditions > that seem to work for things We/they already encounter, > until a little XO is introduced/ [or forced, in some > cases, > as some teachers/ admins? might not want it...] > > Some organizations can't modify a kernel locally? > Create operating systems/ applications? > Translate English based dominance > to local languages? > > A Finland grad student started Linux, > not the US.? And not M$.? But FSF and GNU > and many others added to it... > > > Even in the USA, MIT arrogance is pissing me off. > We 'locals' can host a book sprint, and be treated > like shit, not heard, not worthy of a visit from NN, > WB, etc as Congress / funding is the Only priority, > but not good enough to write/ be published (in ClassActs), > must less vote on things that effect us > (SLOB)? > > > I would also guess that if the current Fedora 9-based > OS is a blocker to paramount needs they may try to update it > themselves. > > See the talk on the wiki.laptop.org F11forXO1 about some > git commands and the 'we are not going to do it, > but it's easy' type of tone, and then see if you > can do it from what was provided... > > > However, providing a better option as the > F11/Sugar0.84+ is, in no way is in contrast with the > "educational project". > > > For one is _not_ a "computer education" project. > > Isn't anything done on a computer, > a computer education project? ;-/ > > But most people don't look under > the hood of their cars (those that own cars...) > > > So "upgrade your OS", is by no means a priority. > > Install or develop? > Remix the kernel modules? > > > Is welcome, but in no way required. > > > Expecting a 9-12 years old on the other hand to come > up with the solutions is conceivable but nothing to depend > on, either. > > You might be surprised what 9-12 yos can do, > but there are also high schools, colleges, > administrators, teachers and community members > and over the lifecycle of the project, > kids starting out on XO's > might want to graduate to hacking kernels, > and going upstream, so to speak, > with support instead of fighting > the attitude that they are not good enough > to do that... > > > Finally the fact that if you give someone a fishing > pole will eat fish all his/her life, does not preclude that > you can not give them a fishing boat to get bigger fish, nor > it implies they should built one. > > Giving someone *the first* fishing pole (G1G1 Donor) > does not mean that that once introduced to fishing, > they cannot try making a fishing pole locally once seen... > > Or better yet, adapt the pole to the type of waters > locally.? Fishing off a dock / pier is one thing, in a > stream, > another, and in the ocean, requires something else > entirely... > > Not to mentioned bait... > [humorous analogy to herding cats somewhere in here] > > > They may as well build a boat by themselves but the > goal here is to get as much and as good fish as possible > given the needs. > > Since we are talking fishing, is that for sport or to > survive? > > Here in the USA, many people are recreational > fisherman/women/kids. > > And some poor/ homeless in the city, > that is the only way they get food/ > fresh fish, but the rivers are polluted, though better > after the 1970's, but I'd guess here in Washington,DC > somewhat still polluted and mercury (+whatever) poisoned. > > > Finally self reliance is an important factor. > > Respect is important too. > > > However like everything else in teaching it must be > build > gradually, in the right order and by experience. Assigning > tasks that > will be never completed guaranties that you will build > self > depreciation rather than self reliance. > > > And as you said "is an educational project". > > > > If I read your comments wrong, my apologies. > > > Well, you actually read them :-) > and stated what you heard, > so I'm responding, even if late, > and still pissed about ClassActs/ > FlossManuals.net Index/ LyX/ LaTeX stuff. > > Tux.org people were _involved_ in the > ClassActs, but not even listed on the > poster, t-shirt, invited to meet NN, > WB, etc... > > And if Sugar is to be truely cross platform, > then it might want people who are involved > in other distros (Ubuntu, YellowDog, etc )/ > hardware (Apple Mac, Sun?, etc) > plus the whole user community instead of > just developers (see criteria for SL membership)... > > And most old hardware don't boot from USB > (64 bit laptop w battery issue mentioned above), > and really old stuff doesn't boot from CDR (Beige G3, > and P1 class machines, i.e. stuff people give away/ > trash locally...), much less support virtualization > (even 1st Gen 64 bit Averatec and this 64 bit desktop > doesn't have the real cpu chip support)... > > > >> > >> My $.02 USD - costs of ownership/ > >> && giving back. > >> > >> On Tue, Sep 22, 2009 at 12:33 PM, Yioryos > Asprobounitis > >> > >> wrote: > >> > Now, that's an excellent idea! > >> > However, the crucial thing before any > extensive > >> building/testing starts is to address some major > issues that > >> would stop most people from using/testing > F11/Sugar.84+. > >> Namely the > Xorg geode video driver, > the camera > and the battery monitor. > > >> These will primarily need developers. > >> > Having these components in place then a daily > build > >> bug fixing/reporting system would be more valuable > since > >> more people may be willing to give it a try, > identifying the > >> "minor" issues that may eventually allow a > >> deployment-quality release. > >> > If this is going to be an OLPC, Fedora or SL > project, > >> I think is irrelevant. XO-1 is an EOL machine that > runs an > >> OS/UI developed by "some other" organization. Is > literally > >> orphan (besides these limited efforts) so any > "adopter" > >> should be welcome. Whoever sets it up should be > good to go. > >> With almost a million users is the biggest > educational > >> linux/sugar implementation and worths every > attention. > >> > > >> > --- On Mon, 9/21/09, David Farning > >> wrote: > >> > > >> >> From: David Farning > >> >> Subject: Re: XO Special interest group at > Sugar > >> Labs > >> >> To: fedora-olpc-list at redhat.com > >> >> Cc: "iaep" > >> >> Date: Monday, September 21, 2009, 7:36 > PM > >> >> On Mon, Sep 21, 2009 at 3:41 PM, > >> >> Peter Robinson > >> >> wrote: > >> >> > Hi David, > >> >> > > >> >> > On Mon, Sep 21, 2009 at 7:48 PM, > David > >> Farning > >> >> wrote: > >> >> >> For the past several months the > >> OLPC/Sugar Labs > >> >> ecosystem has been > >> >> >> getting requests to provide > releases of > >> more > >> >> recent versions of Sugar > >> >> >> on the XO. > >> >> >> > >> >> >> The leading effort in this > direction > >> seems to be > >> >> the F11-XO1 project. > >> >> >> I would like to like to invite > F11-XO1 to > >> become > >> >> part of the XO SIG. > >> >> >> I have been trying to articulate > the > >> project goals > >> >> and gather momentum > >> >> >> across several groups. > >> >> >> 1. ?OLPC as a downstream. > > as posted by SL > > >> >> >> 2. Sugar Labs as a focus point. > > as posted by SL > > >> >> >> 3. Various ecosystem leaders to > do pilots > >> with > >> >> current versions of Sugar on XOs. > > near as I can tell OLPC doesn't do Pilots, > they expect results only, at least in the > contributor program. > > >> >> >> 4. Various testers to provide > user level > >> testing. > > User level testing on the kernel??? > Or Sugar? > Or Activities? > Or the whole Gestalt? > > >> >> >> > >> >> >> The goal of this groups is not > to > >> _fragment_ the > >> >> existing efforts. > >> >> >> The goal is bring the various > efforts > >> together to > >> >> form a critical mass > >> >> >> to help pull this propel > forward. > >> >> > > >> >> > As far as I'm aware there is no > F11-XO1 > >> project, I'm > >> >> aware of a couple > >> >> > of different projects to get the > latest Sugar > >> releases > >> >> on the XO. > >> >> > - The SoaS on XO which is being run > my Martin > >> Dengler > >> >> in conjunction > >> >> > with SoaS and SL (that's where its > all > >> hosted). > >> >> > - The OLPC project to get Fedora 11 > on both > >> the XO-1.5 > >> >> and XO-1 which > >> >> > is being handled by Steven M. > Parrish (and > >> Daniel > >> >> Drake / Chris Ball) > >> >> > >> >> This confusion is part of what I am > hoping to > >> clear up by > >> >> create a > >> >> single clearly defined project. > >> >> > >> >> I have heard back from many of the people > working > >> on the > >> >> various > >> >> projects. the work flow seems to be: > >> >> 1. Sugar development team creates > platform. > >> >> 2. Fedora packagers package Sugar... and > >> everything else > >> >> required to > >> >> make a disto. > >> >> 3a. SoaS takes packages and turns them > into a Soas > >> image. > >> >> 3b. Soas is getting pretty well test via > test days > >> and > >> >> deployments > >> >> such as the GPA. > >> >> 4a. Steven take the Fedora packages adds > the XO > >> specific > >> >> bit and turns > >> >> them into xo builds. > >> >> 4b. limited testing for xo builds. > >> >> > >> >> Because of time restrictions, the F11 on > XO effort > >> seems to > >> >> be > >> >> reactive.? They take the output from cjb > and the > >> >> fedora packages and > >> >> create builds.? I believe that the XO > SIG could > >> help > >> >> generate interest > >> >> and attract more developers and testers > to the > >> project. > >> >> > >> >> > Both projects are cross pollinated > and use > >> components > >> >> of work done by > >> >> > both as well as myself and other > Fedora > >> upstream > >> >> people. I don't > >> >> > believe there's much difference > between them > >> as where > >> >> possible I > >> >> > believe most stuff is pushed > upsteam. There > >> is no > >> >> current Fedora based > >> >> > project working on this directly due > to the > >> down > >> >> stream projects. > >> >> > > >> >> > I have my own build that I use but > that > >> isn't > >> >> generally published and > >> >> > is mostly to test core fedora for > dependency > >> bloat and > >> >> breakages. > >> >> > >> >> Would it be useful if we started by > combining your > >> work and > >> >> Stevens > >> >> into an automatic build system.? This > could help > >> >> identify breakages. > >> >> Then we could create a release cycle of > alpha and > >> beta and > >> >> final > >> >> releases. > >> >> > >> >> By creating the daily builds and widely > >> broadcasting the > >> >> various > >> >> releases, we can engage a larger > community of > >> testers. > >> >> > >> >> david > >> >> > >> >> > _______________________________________________ > >> >> Fedora-olpc-list mailing list > >> >> Fedora-olpc-list at redhat.com > >> >> https://www.redhat.com/mailman/listinfo/fedora-olpc-list > >> >> > >> > > >> > > >> > > >> > > >> > > _______________________________________________ > >> > Fedora-olpc-list mailing list > >> > Fedora-olpc-list at redhat.com > >> > https://www.redhat.com/mailman/listinfo/fedora-olpc-list > >> > > >> > >> > >> > >> -- > >> DancesWithCars > >> leave the wolves behind ;-) > >> > > > > > > > > > > > > -- > DancesWithCars > leave the wolves behind ;-) > From mavrothal at yahoo.com Sat Sep 26 17:35:24 2009 From: mavrothal at yahoo.com (Yioryos Asprobounitis) Date: Sat, 26 Sep 2009 10:35:24 -0700 (PDT) Subject: New SoaS build soas68 In-Reply-To: <20090926035258.GN14643@ops-13.xades.com> Message-ID: <904218.92236.qm@web65505.mail.ac4.yahoo.com> Also, using soas68xo.img and 'sudo ./livecd-iso-to-disk.sh --format --xo --xo-no-home soas68xo.iso /dev/sda1' in a Fedora 11 machine results in a stick that will go through the fedora progress bars all the way and freeze there, with no console access. It would appear that "on a stick" is not very easy on the XO-1 at this point. --- On Fri, 9/25/09, Martin Dengler wrote: > From: Martin Dengler > Subject: Re: New SoaS build soas68 > To: sugar-devel at lists.sugarlabs.org, fedora-olpc-list at redhat.com > Date: Friday, September 25, 2009, 11:52 PM > On Sat, Sep 26, 2009 at 03:24:17AM > +0000, Martin Dengler wrote: > > > > New Sugar-on-a-Stick build soas68 is available. > > [...] > > This is the SoaS-on-XO-1 build announcement - sorry for the > ambiguity > in the subject/wording and any resultant confusion.? > The git trunk > announcer's language is in flux and I didn't pay close > attention to it > before sending. > > I will fix the ambiguity after discussing with Sebastian. > > Martin > > -----Inline Attachment Follows----- > > _______________________________________________ > Fedora-olpc-list mailing list > Fedora-olpc-list at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-olpc-list From jvonau at shaw.ca Sat Sep 26 18:11:16 2009 From: jvonau at shaw.ca (Jerry Vonau) Date: Sat, 26 Sep 2009 13:11:16 -0500 Subject: New SoaS build soas68 In-Reply-To: <4ABDAE4B.2080006@bga.com> References: <4ABDAE4B.2080006@bga.com> Message-ID: <1253988676.2210.103.camel@f9.vonau.ca> On Sat, 2009-09-26 at 02:01 -0400, Mikus Grinbergs wrote: > Did copy-nand of soas68xo.img to my XO-1. Tried to boot. No X. > > The initial boot gets as far as a screen with a "plaza pavement" > background and a login window in the center saying "Automatically > logging in ...". Nothing more happens (I waited an hour, just in > case it was installing Activities, or something). [I can select > "Language" and "Keyboard" - but that doesn't help.] > > X is stuck. [Nothing that looks wrong in /var/log.] > > > This is the SoaS-on-XO-1 build announcement > > I can get into a text console (alt-ctl-F2) -- but for me. trying to > run from soas68xo.img on an XO-1 is a failure. > > mikus > Same issues booting from an usbkey.. Jerry From mikus at bga.com Sat Sep 26 17:54:31 2009 From: mikus at bga.com (Mikus Grinbergs) Date: Sat, 26 Sep 2009 13:54:31 -0400 Subject: New SoaS build soas68 Message-ID: <4ABE5557.6070807@bga.com> Did livecd-iso-to-disk with soas68xo.iso to USB stick, then tried to boot my XO-1. Got no further than booting with soas68xo.img. No X. [Creating the USB stick (I don't have Fedora) seemed to take much longer than what I remember from doing it with previous builds.] > Also, using soas68xo.img and 'sudo ./livecd-iso-to-disk.sh --format > --xo --xo-no-home soas68xo.iso /dev/sda1' in a Fedora 11 machine > results in a stick that will go through the fedora progress bars > all the way and freeze there, with no console access. If one then presses , one is shown a text console with: /sbin/dmsquash-live-root: 166: grep: not found dracut Warning: Machine in enforcing mode and cannot execute load-policy. dracut Warning: To disable selinux, add selinux=0 to the kernel command line. dracut Warning: Not continuing So I added selinux-0 to the kernel command line, and tried booting. This time the fedora progress bars eventually go to town. Pressing shows the end of the boot-process bring-up, and eventually a screen with a "plaza pavement" background and a login window in the center saying "Automatically logging in ...". Nothing more happens (I waited half an hour, just in case it was installing Activities, or something). [This time the bottom edge of the screen (in addition to allowing "Language" and "Keyboard" selection and some icons) includes an icon that shows the messages-during-boot - but nothing on the bottom edge helps start the user's X session.] X is stuck. [Nothing that looks wrong in /var/log.] > This is the SoaS-on-XO-1 build announcement I can get into a text console (alt-ctl-F2) -- but for me, trying to run from soas68xo.iso on an XO-1 is a failure. mikus From mavrothal at yahoo.com Sat Sep 26 19:12:10 2009 From: mavrothal at yahoo.com (Yioryos Asprobounitis) Date: Sat, 26 Sep 2009 12:12:10 -0700 (PDT) Subject: New SoaS build soas68 In-Reply-To: <4ABE5557.6070807@bga.com> Message-ID: <769757.22682.qm@web65510.mail.ac4.yahoo.com> --- On Sat, 9/26/09, Mikus Grinbergs wrote: > From: Mikus Grinbergs > Subject: Re: New SoaS build soas68 > To: fedora-olpc-list at redhat.com > Date: Saturday, September 26, 2009, 1:54 PM > Did livecd-iso-to-disk with > soas68xo.iso to USB stick, Oups..., Hopefully you did not got misguided by my typo. It should read "soas68.iso" not "soas68xo.iso" But you are right both versions (I tried the 68xo too) end up at the same point. then tried to boot my XO-1.? > Got no further than booting with soas68xo.img.? No X. > > [Creating the USB stick (I don't have Fedora) seemed to > take much longer than what I remember from doing it with > previous builds.] > > > Also, using soas68xo.img and 'sudo > ./livecd-iso-to-disk.sh --format > > --xo --xo-no-home soas68xo.iso /dev/sda1' in a Fedora > 11 machine > > results in a stick that will go through the fedora > progress bars > > all the way and freeze there, with no console access. > > If one then presses , one is shown a text > console with: > ? /sbin/dmsquash-live-root: 166: grep: not found > ? dracut Warning: Machine in enforcing mode and cannot > execute > ? ? load-policy. > ? dracut Warning: To disable selinux, add selinux=0 to > the kernel > ? ? command line. > ? dracut Warning: Not continuing That's what I got with the with the "removable" versions > > > So I added selinux-0 to the kernel command line, and tried > booting. > This time the fedora progress bars eventually go to > town.? Pressing shows the end of the > boot-process bring-up, and eventually a screen with a "plaza > pavement" background and a login window in the center saying > "Automatically logging in ...".? Nothing more happens > (I waited half an hour, just in case it was installing > Activities, or something).? [This time the bottom edge > of the screen (in addition to allowing "Language" and > "Keyboard" selection and some icons) includes an icon that > shows the messages-during-boot - but nothing on the bottom > edge helps start the user's X session.] > > X is stuck.? [Nothing that looks wrong in /var/log.] > > > This is the SoaS-on-XO-1 build announcement > > I can get into a text console (alt-ctl-F2) -- but for me, > trying to > run from soas68xo.iso on an XO-1 is a failure. > > mikus > > _______________________________________________ > Fedora-olpc-list mailing list > Fedora-olpc-list at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-olpc-list > From dfarning at sugarlabs.org Mon Sep 28 21:06:03 2009 From: dfarning at sugarlabs.org (David Farning) Date: Mon, 28 Sep 2009 16:06:03 -0500 Subject: XO Special interest group at Sugar Labs In-Reply-To: <200909211640.28175.smparrish@gmail.com> References: <200909211640.28175.smparrish@gmail.com> Message-ID: > As the current maintainer of the "F11 for the XO-1" releases, ?I would be > interested in hearing more about the XO SIG and how the work I am doing can > benefit the SIG and how the SIG can benefit the work I am doing. ?Especially in > regards to testing. > > The original goal of the project was to keep up with the work being done for > the XO-1.5. ?It is important that the 2 releases stay in sync to present a > consistent experience to the users. ?To that end I try and do frequent > releases, and in fact one is due out this week. > > I am open to anything that will help both OLPC and Sugar in the hands of more > users. > > Feel free to contact me off or on list. > > Steven Thanks Steven, It has taken me a while to pull this together. Based on feedback from you and others, it looks like the best way a Sugar Labs SIG/Project can help the ecosystem is to work with you to create frequent 'upstream' releases for the XO and then gather high quality feedback by engaging testers. Would you be willing to lead me through the process of creating builds so that I can document your procedures in order to make it easier for other to become involved? So far we have buy in from the olpc contributors program in the form of developer machines. david From martin at martindengler.com Tue Sep 29 04:40:57 2009 From: martin at martindengler.com (Martin Dengler) Date: Tue, 29 Sep 2009 05:40:57 +0100 Subject: New SoaS build soas68 In-Reply-To: <1253988676.2210.103.camel@f9.vonau.ca> References: <4ABDAE4B.2080006@bga.com> <1253988676.2210.103.camel@f9.vonau.ca> Message-ID: <20090929044057.GT32229@ops-13.xades.com> On Sat, Sep 26, 2009 at 01:11:16PM -0500, Jerry Vonau wrote: > On Sat, 2009-09-26 at 02:01 -0400, Mikus Grinbergs wrote: > > Did copy-nand of soas68xo.img to my XO-1. Tried to boot. No X. > > > > The initial boot gets as far as a screen with a "plaza pavement" > > background and a login window in the center saying "Automatically > > logging in ...". Nothing more happens (I waited an hour, just in > > case it was installing Activities, or something). [I can select > > "Language" and "Keyboard" - but that doesn't help.] > > > > X is stuck. [Nothing that looks wrong in /var/log.] > > > > > This is the SoaS-on-XO-1 build announcement > > > > I can get into a text console (alt-ctl-F2) -- but for me. trying to > > run from soas68xo.img on an XO-1 is a failure. > > > > mikus > > > Same issues booting from an usbkey.. Thanks for the report. gpm autologin was broken in rawhide; it's now fixed. If you do something like: yum -y install gpm --nogpgcheck ...it should fix it. I'm making a new build now as I've tweaked how SUGAR_SCALING gets set. > Jerry Martin -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From martin at martindengler.com Tue Sep 29 04:44:47 2009 From: martin at martindengler.com (Martin Dengler) Date: Tue, 29 Sep 2009 05:44:47 +0100 Subject: X crash with Browse / gtk scrollbars + Rawhide? Message-ID: <20090929044447.GU32229@ops-13.xades.com> Is it just me, or does scrolling in Browse in rawhide (e.g., soas68xo.img and earlier/later) cause X to crash? It's not just Browse but it's not all scrollbars. The backtrace I get in /var/log/Xorg.0.log is: Backtrace: 0: /usr/bin/Xorg (xorg_backtrace+0x3c) [0x80e562c] 1: /usr/bin/Xorg (0x8048000+0x5eae6) [0x80a6ae6] 2: (vdso) (__kernel_rt_sigreturn+0x0) [0xb7fbb40c] 3: /usr/lib/libpixman-1.so.0 (0xb7f09000+0x46738) [0xb7f4f738] 4: /usr/lib/libpixman-1.so.0 (0xb7f09000+0x468db) [0xb7f4f8db] 5: /usr/lib/libpixman-1.so.0 (0xb7f09000+0x15324) [0xb7f1e324] 6: /usr/lib/libpixman-1.so.0 (pixman_blt+0x79) [0xb7f435a9] 7: /usr/lib/xorg/modules/libfb.so (fbCopyNtoN+0x1aa) [0xb77a8cca] 8: /usr/bin/Xorg (miCopyRegion+0x19a) [0x819656a] 9: /usr/bin/Xorg (miDoCopy+0x44d) [0x8196b0d] 10: /usr/lib/xorg/modules/libfb.so (fbCopyArea+0x79) [0xb77a82b9] 11: /usr/lib/xorg/modules/libexa.so (0xb7783000+0xec70) [0xb7791c70] 12: /usr/lib/xorg/modules/libexa.so (0xb7783000+0x931e) [0xb778c31e] 13: /usr/bin/Xorg (miCopyRegion+0x19a) [0x819656a] 14: /usr/bin/Xorg (miDoCopy+0x44d) [0x8196b0d] 15: /usr/lib/xorg/modules/libexa.so (0xb7783000+0x77cb) [0xb778a7cb] 16: /usr/bin/Xorg (0x8048000+0xd5714) [0x811d714] 17: /usr/bin/Xorg (0x8048000+0x249fd) [0x806c9fd] 18: /usr/bin/Xorg (0x8048000+0x26167) [0x806e167] 19: /usr/bin/Xorg (0x8048000+0x1a855) [0x8062855] 20: /lib/libc.so.6 (__libc_start_main+0xe6) [0xb7ac7b36] 21: /usr/bin/Xorg (0x8048000+0x1a441) [0x8062441] Segmentation fault at address 0x30f638 Fatal server error: Caught signal 11 (Segmentation fault). Server aborting Martin Full Xorg.0.log: X.Org X Server 1.6.99.902 (1.7.0 RC 2) Release Date: 2009-9-22 X Protocol Version 11, Revision 0 Build Operating System: 2.6.18-164.el5 Current Operating System: Linux localhost.localdomain 2.6.30_xo1-20090808.1740.1.olpc.a817f86 #1 PREEMPT Sat Aug 8 17:48:32 BST 2009 i586 Kernel command line: ro root=mtd0 rootfstype=jffs2 console=ttyS0,115200 console=tty0 fbcon=font:SUN12x22 Build Date: 22 September 2009 02:06:09AM Build ID: xorg-x11-server 1.6.99.902-1.fc12 Current version of pixman: 0.16.0 Before reporting problems, check http://bodhi.fedoraproject.org/ to make sure that you have the latest version. Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: "/var/log/Xorg.0.log", Time: Tue Sep 29 00:28:40 2009 (II) Loader magic: 0x821b740 (II) Module ABI versions: X.Org ANSI C Emulation: 0.4 X.Org Video Driver: 6.0 X.Org XInput driver : 7.0 X.Org Server Extension : 2.0 (--) using VT number 7 (--) PCI:*(0:0:1:1) 1022:2081:100b:0030 Advanced Micro Devices [AMD] Geode LX Video rev 0, Mem @ 0xfd000000/16777216, 0xfe000000/16384, 0xfe004000/16384, 0xfe008000/16384, 0xfe00c000/16384, BIOS @ 0x????????/131072 (--) PCI: (0:0:12:2) 11ab:4102:11ab:4100 Marvell Technology Group Ltd. rev 16, Mem @ 0xfe028000/16384, BIOS @ 0x????????/65536 (==) Using default built-in configuration (30 lines) (==) --- Start of built-in configuration --- Section "Device" Identifier "Builtin Default geode Device 0" Driver "geode" EndSection Section "Screen" Identifier "Builtin Default geode Screen 0" Device "Builtin Default geode Device 0" EndSection Section "Device" Identifier "Builtin Default vesa Device 0" Driver "vesa" EndSection Section "Screen" Identifier "Builtin Default vesa Screen 0" Device "Builtin Default vesa Device 0" EndSection Section "Device" Identifier "Builtin Default fbdev Device 0" Driver "fbdev" EndSection Section "Screen" Identifier "Builtin Default fbdev Screen 0" Device "Builtin Default fbdev Device 0" EndSection Section "ServerLayout" Identifier "Builtin Default Layout" Screen "Builtin Default geode Screen 0" Screen "Builtin Default vesa Screen 0" Screen "Builtin Default fbdev Screen 0" EndSection (==) --- End of built-in configuration --- (==) ServerLayout "Builtin Default Layout" (**) |-->Screen "Builtin Default geode Screen 0" (0) (**) | |-->Monitor "" (**) | |-->Device "Builtin Default geode Device 0" (==) No monitor specified for screen "Builtin Default geode Screen 0". Using a default monitor configuration. (**) |-->Screen "Builtin Default vesa Screen 0" (1) (**) | |-->Monitor "" (**) | |-->Device "Builtin Default vesa Device 0" (==) No monitor specified for screen "Builtin Default vesa Screen 0". Using a default monitor configuration. (**) |-->Screen "Builtin Default fbdev Screen 0" (2) (**) | |-->Monitor "" (**) | |-->Device "Builtin Default fbdev Device 0" (==) No monitor specified for screen "Builtin Default fbdev Screen 0". Using a default monitor configuration. (==) Automatically adding devices (==) Automatically enabling devices (==) FontPath set to: catalogue:/etc/X11/fontpath.d, built-ins (==) ModulePath set to "/usr/lib/xorg/modules" (II) Cannot locate a core pointer device. (II) Cannot locate a core keyboard device. (II) The server relies on HAL to provide the list of input devices. If no devices become available, reconfigure HAL or disable AllowEmptyInput. (II) LoadModule: "extmod" (II) Loading /usr/lib/xorg/modules/extensions/libextmod.so (II) Module extmod: vendor="X.Org Foundation" compiled for 1.6.99.902, module version = 1.0.0 Module class: X.Org Server Extension ABI class: X.Org Server Extension, version 2.0 (II) Loading extension SELinux (II) Loading extension MIT-SCREEN-SAVER (II) Loading extension XFree86-VidModeExtension (II) Loading extension XFree86-DGA (II) Loading extension DPMS (II) Loading extension XVideo (II) Loading extension XVideo-MotionCompensation (II) Loading extension X-Resource (II) LoadModule: "dbe" (II) Loading /usr/lib/xorg/modules/extensions/libdbe.so (II) Module dbe: vendor="X.Org Foundation" compiled for 1.6.99.902, module version = 1.0.0 Module class: X.Org Server Extension ABI class: X.Org Server Extension, version 2.0 (II) Loading extension DOUBLE-BUFFER (II) LoadModule: "glx" (II) Loading /usr/lib/xorg/modules/extensions/libglx.so (II) Module glx: vendor="X.Org Foundation" compiled for 1.6.99.902, module version = 1.0.0 ABI class: X.Org Server Extension, version 2.0 (==) AIGLX enabled (II) Loading extension GLX (II) LoadModule: "record" (II) Loading /usr/lib/xorg/modules/extensions/librecord.so (II) Module record: vendor="X.Org Foundation" compiled for 1.6.99.902, module version = 1.13.0 Module class: X.Org Server Extension ABI class: X.Org Server Extension, version 2.0 (II) Loading extension RECORD (II) LoadModule: "dri" (II) Loading /usr/lib/xorg/modules/extensions/libdri.so (II) Module dri: vendor="X.Org Foundation" compiled for 1.6.99.902, module version = 1.0.0 ABI class: X.Org Server Extension, version 2.0 (II) Loading extension XFree86-DRI (II) LoadModule: "dri2" (II) Loading /usr/lib/xorg/modules/extensions/libdri2.so (II) Module dri2: vendor="X.Org Foundation" compiled for 1.6.99.902, module version = 1.1.0 ABI class: X.Org Server Extension, version 2.0 (II) Loading extension DRI2 (II) LoadModule: "geode" (II) Loading /usr/lib/xorg/modules/drivers/geode_drv.so (II) Module geode: vendor="X.Org Foundation" compiled for 1.6.99.900, module version = 2.11.4 Module class: X.Org Video Driver ABI class: X.Org Video Driver, version 6.0 (II) LoadModule: "vesa" (II) Loading /usr/lib/xorg/modules/drivers/vesa_drv.so (II) Module vesa: vendor="X.Org Foundation" compiled for 1.6.99.1, module version = 2.2.1 Module class: X.Org Video Driver ABI class: X.Org Video Driver, version 6.0 (II) LoadModule: "fbdev" (II) Loading /usr/lib/xorg/modules/drivers/fbdev_drv.so (II) Module fbdev: vendor="X.Org Foundation" compiled for 1.6.99.1, module version = 0.4.1 ABI class: X.Org Video Driver, version 6.0 (II) GEODE: Driver for AMD Geode Chipsets: Geode LX, Geode GX (II) VESA: driver for VESA chipsets: vesa (II) FBDEV: driver for framebuffer: fbdev (II) Primary Device is: PCI 00 at 00:01:1 AmdPciProbe: Probing for supported devices! (WW) Falling back to old probe method for vesa (WW) Falling back to old probe method for fbdev (II) Loading sub module "fbdevhw" (II) LoadModule: "fbdevhw" (II) Loading /usr/lib/xorg/modules/linux/libfbdevhw.so (II) Module fbdevhw: vendor="X.Org Foundation" compiled for 1.6.99.902, module version = 0.0.2 ABI class: X.Org Video Driver, version 6.0 (WW) VGA arbiter: cannot open kernel arbiter, no multi-card support (WW) System lacks support for changing MTRRs (II) GEODE(0): Creating default Display subsection in Screen section "Builtin Default geode Screen 0" for depth/fbbpp 16/16 (==) GEODE(0): Depth 16, (==) framebuffer bpp 16 (==) GEODE(0): RGB weight 565 (==) GEODE(0): Default visual is TrueColor (==) GEODE(0): Using gamma correction (1.0, 1.0, 1.0) (==) GEODE(0): DCON detected. (II) GEODE(0): LX output options: (II) GEODE(0): CRT: NO (II) GEODE(0): PANEL: YES (II) GEODE(0): DCON: YES (II) GEODE(0): VGA: NO (II) GEODE(0): 1000000 bytes of video memory is less then optimal (II) GEODE(0): when compression is on. Disabling compression. (II) GEODE(0): Output default has no monitor section (II) GEODE(0): I2C bus "CS5536 DDC" initialized. (II) GEODE(0): Printing probed modes for output default (II) GEODE(0): Modeline "1200x900"x50.6 57.27 1200 1208 1216 1240 900 905 908 912 -hsync -vsync (46.2 kHz) (II) GEODE(0): Output default connected (II) GEODE(0): Using exact sizes for initial modes (II) GEODE(0): Output default using initial mode 1200x900 +0+0 (II) GEODE(0): Using default gamma of (1.0, 1.0, 1.0) unless otherwise stated. (--) GEODE(0): Virtual size is 1940x1200 (pitch 0) (**) GEODE(0): Driver mode "1200x900": 57.3 MHz (scaled from 0.0 MHz), 46.2 kHz, 50.6 Hz (II) GEODE(0): Modeline "1200x900"x50.6 57.27 1200 1208 1216 1240 900 905 908 912 -hsync -vsync (46.2 kHz) (**) GEODE(0): Display dimensions: (152, 114) mm (**) GEODE(0): DPI set to (324, 267) (II) Loading sub module "fb" (II) LoadModule: "fb" (II) Loading /usr/lib/xorg/modules/libfb.so (II) Module fb: vendor="X.Org Foundation" compiled for 1.6.99.902, module version = 1.0.0 ABI class: X.Org ANSI C Emulation, version 0.4 (II) Loading sub module "exa" (II) LoadModule: "exa" (II) Loading /usr/lib/xorg/modules/libexa.so (II) Module exa: vendor="X.Org Foundation" compiled for 1.6.99.902, module version = 2.5.0 ABI class: X.Org Video Driver, version 6.0 (II) UnloadModule: "vesa" (II) Unloading /usr/lib/xorg/modules/drivers/vesa_drv.so (II) UnloadModule: "fbdev" (II) Unloading /usr/lib/xorg/modules/drivers/fbdev_drv.so (II) UnloadModule: "fbdevhw" (II) Unloading /usr/lib/xorg/modules/linux/libfbdevhw.so (II) GEODE(0): Geode LX video memory e00000 bytes at 0xb6773000 (II) GEODE(0): LX video memory: (II) GEODE(0): Display: 0x72db20 bytes (II) GEODE(0): Cursor: 0x3000 bytes (II) GEODE(0): EXA: 0x58f4e0 bytes (II) GEODE(0): FREE: 0x0 bytes (II) EXA(0): Offscreen pixmap area of 5829856 bytes (II) EXA(0): Driver registered support for the following operations: (II) Solid (II) Copy (II) Composite (RENDER acceleration) (==) GEODE(0): Backing store disabled (==) GEODE(0): DPMS enabled (II) GEODE(0): RandR 1.2 enabled, ignore the following RandR disabled message. (--) RandR disabled (II) Initializing built-in extension Generic Event Extension (II) Initializing built-in extension SHAPE (II) Initializing built-in extension MIT-SHM (II) Initializing built-in extension XInputExtension (II) Initializing built-in extension XTEST (II) Initializing built-in extension BIG-REQUESTS (II) Initializing built-in extension SYNC (II) Initializing built-in extension XKEYBOARD (II) Initializing built-in extension XC-MISC (II) Initializing built-in extension XINERAMA (II) Initializing built-in extension XFIXES (II) Initializing built-in extension RENDER (II) Initializing built-in extension RANDR (II) Initializing built-in extension COMPOSITE (II) Initializing built-in extension DAMAGE SELinux: Disabled on system, not enabling in X server record: RECORD extension enabled at configure time. record: This extension is known to be broken, disabling extension now.. record: http://bugs.freedesktop.org/show_bug.cgi?id=20500 (II) AIGLX: Screen 0 is not DRI2 capable (II) AIGLX: Screen 0 is not DRI capable (II) AIGLX: Loaded and initialized /usr/lib/dri/swrast_dri.so (II) GLX: Initialized DRISWRAST GL provider for screen 0 (II) GEODE(0): Setting screen physical size to 317 x 238 (II) config/hal: Adding input device AT Translated Set 2 keyboard (II) LoadModule: "evdev" (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so (II) Module evdev: vendor="X.Org Foundation" compiled for 1.6.99.902, module version = 2.2.99 Module class: X.Org XInput Driver ABI class: X.Org XInput driver, version 7.0 (**) AT Translated Set 2 keyboard: always reports core events (**) AT Translated Set 2 keyboard: Device: "/dev/input/event4" (II) AT Translated Set 2 keyboard: Found keys (II) AT Translated Set 2 keyboard: Configuring as keyboard (II) XINPUT: Adding extended input device "AT Translated Set 2 keyboard" (type: KEYBOARD) (**) Option "xkb_rules" "evdev" (**) Option "xkb_model" "pc105+inet" (**) Option "xkb_layout" "us" (**) Option "xkb_options" "terminate:ctrl_alt_bksp" (II) config/hal: Adding input device OLPC HGPK ALPS HGPK (**) OLPC HGPK ALPS HGPK: always reports core events (**) OLPC HGPK ALPS HGPK: Device: "/dev/input/event5" (II) OLPC HGPK ALPS HGPK: Found 3 mouse buttons (II) OLPC HGPK ALPS HGPK: found relative axes (II) OLPC HGPK ALPS HGPK: Found x and y relative axes (II) OLPC HGPK ALPS HGPK: Configuring as mouse (**) OLPC HGPK ALPS HGPK: YAxisMapping: buttons 4 and 5 (**) OLPC HGPK ALPS HGPK: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200 (II) XINPUT: Adding extended input device "OLPC HGPK ALPS HGPK" (type: MOUSE) (**) OLPC HGPK ALPS HGPK: (accel) keeping acceleration scheme 1 (**) OLPC HGPK ALPS HGPK: (accel) acceleration profile 0 (II) OLPC HGPK ALPS HGPK: initialized for relative axes. (II) config/hal: Adding input device OLPC PM (**) OLPC PM: always reports core events (**) OLPC PM: Device: "/dev/input/event0" (II) OLPC PM: Found keys (II) OLPC PM: Configuring as keyboard (II) XINPUT: Adding extended input device "OLPC PM" (type: KEYBOARD) (**) Option "xkb_rules" "evdev" (**) Option "xkb_model" "evdev" (**) Option "xkb_layout" "us" (II) GEODE(0): Printing probed modes for output default (II) GEODE(0): Modeline "1200x900"x50.6 57.27 1200 1208 1216 1240 900 905 908 912 -hsync -vsync (46.2 kHz) (II) AT Translated Set 2 keyboard: Device reopened after 1 attempts. (II) OLPC HGPK ALPS HGPK: Device reopened after 1 attempts. (II) OLPC PM: Device reopened after 1 attempts. Backtrace: 0: /usr/bin/Xorg (xorg_backtrace+0x3c) [0x80e562c] 1: /usr/bin/Xorg (0x8048000+0x5eae6) [0x80a6ae6] 2: (vdso) (__kernel_rt_sigreturn+0x0) [0xb7fbb40c] 3: /usr/lib/libpixman-1.so.0 (0xb7f09000+0x46738) [0xb7f4f738] 4: /usr/lib/libpixman-1.so.0 (0xb7f09000+0x468db) [0xb7f4f8db] 5: /usr/lib/libpixman-1.so.0 (0xb7f09000+0x15324) [0xb7f1e324] 6: /usr/lib/libpixman-1.so.0 (pixman_blt+0x79) [0xb7f435a9] 7: /usr/lib/xorg/modules/libfb.so (fbCopyNtoN+0x1aa) [0xb77a8cca] 8: /usr/bin/Xorg (miCopyRegion+0x19a) [0x819656a] 9: /usr/bin/Xorg (miDoCopy+0x44d) [0x8196b0d] 10: /usr/lib/xorg/modules/libfb.so (fbCopyArea+0x79) [0xb77a82b9] 11: /usr/lib/xorg/modules/libexa.so (0xb7783000+0xec70) [0xb7791c70] 12: /usr/lib/xorg/modules/libexa.so (0xb7783000+0x931e) [0xb778c31e] 13: /usr/bin/Xorg (miCopyRegion+0x19a) [0x819656a] 14: /usr/bin/Xorg (miDoCopy+0x44d) [0x8196b0d] 15: /usr/lib/xorg/modules/libexa.so (0xb7783000+0x77cb) [0xb778a7cb] 16: /usr/bin/Xorg (0x8048000+0xd5714) [0x811d714] 17: /usr/bin/Xorg (0x8048000+0x249fd) [0x806c9fd] 18: /usr/bin/Xorg (0x8048000+0x26167) [0x806e167] 19: /usr/bin/Xorg (0x8048000+0x1a855) [0x8062855] 20: /lib/libc.so.6 (__libc_start_main+0xe6) [0xb7ac7b36] 21: /usr/bin/Xorg (0x8048000+0x1a441) [0x8062441] Segmentation fault at address 0x30f638 Fatal server error: Caught signal 11 (Segmentation fault). Server aborting Please consult the The X.Org Foundation support at http://bodhi.fedoraproject.org/ for help. Please also check the log file at "/var/log/Xorg.0.log" for additional information. (II) AT Translated Set 2 keyboard: Close (II) UnloadModule: "evdev" (II) OLPC HGPK ALPS HGPK: Close (II) UnloadModule: "evdev" (II) OLPC PM: Close (II) UnloadModule: "evdev" -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From echerlin at gmail.com Tue Sep 29 05:38:19 2009 From: echerlin at gmail.com (Edward Cherlin) Date: Mon, 28 Sep 2009 22:38:19 -0700 Subject: New SoaS build soas68 In-Reply-To: <20090929044057.GT32229@ops-13.xades.com> References: <4ABDAE4B.2080006@bga.com> <1253988676.2210.103.camel@f9.vonau.ca> <20090929044057.GT32229@ops-13.xades.com> Message-ID: Same with soas68.iso in Virtualbox. On Mon, Sep 28, 2009 at 9:40 PM, Martin Dengler wrote: > On Sat, Sep 26, 2009 at 01:11:16PM -0500, Jerry Vonau wrote: >> On Sat, 2009-09-26 at 02:01 -0400, Mikus Grinbergs wrote: >> > Did copy-nand of soas68xo.img to my XO-1. ?Tried to boot. ?No X. >> > >> > The initial boot gets as far as a screen with a "plaza pavement" >> > background and a login window in the center saying "Automatically >> > logging in ...". ?Nothing more happens (I waited an hour, just in >> > case it was installing Activities, or something). ?[I can select >> > "Language" and "Keyboard" - but that doesn't help.] >> > >> > X is stuck. ?[Nothing that looks wrong in /var/log.] >> > >> > > This is the SoaS-on-XO-1 build announcement >> > >> > I can get into a text console (alt-ctl-F2) -- but for me. trying to >> > run from soas68xo.img on an XO-1 is a failure. >> > >> > mikus >> > >> Same issues booting from an usbkey.. > > Thanks for the report. > > gpm autologin was broken in rawhide; it's now fixed. ?If you do > something like: > > ?yum -y install gpm --nogpgcheck > > ...it should fix it. > > I'm making a new build now as I've tweaked how SUGAR_SCALING gets set. > >> Jerry > > Martin > > > _______________________________________________ > Fedora-olpc-list mailing list > Fedora-olpc-list at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-olpc-list > -- Edward Mokurai (??/???????????????/????????????? ?) Cherlin Silent Thunder is my name, and Children are my nation. The Cosmos is my dwelling place, the Truth my destination. http://earthtreasury.org/ From martin at martindengler.com Tue Sep 29 11:10:06 2009 From: martin at martindengler.com (Martin Dengler) Date: Tue, 29 Sep 2009 12:10:06 +0100 Subject: New SoaS build soas68 In-Reply-To: References: <4ABDAE4B.2080006@bga.com> <1253988676.2210.103.camel@f9.vonau.ca> <20090929044057.GT32229@ops-13.xades.com> Message-ID: <20090929111006.GZ32229@ops-13.xades.com> On Mon, Sep 28, 2009 at 10:38:19PM -0700, Edward Cherlin wrote: > > On Mon, Sep 28, 2009 at 9:40 PM, Martin Dengler > wrote: > > On Sat, Sep 26, 2009 at 01:11:16PM -0500, Jerry Vonau wrote: > >> On Sat, 2009-09-26 at 02:01 -0400, Mikus Grinbergs wrote: > >> > Did copy-nand of soas68xo.img to my XO-1. ?Tried to boot. ?No X. > >> > > >> > The initial boot gets as far as a screen with a "plaza pavement" > >> > background > >> > > >> Same issues booting from an usbkey.. > Same with soas68.iso in Virtualbox. > > Thanks for the report. > > > > gpm autologin was broken in rawhide; it's now fixed. ?If you do > > something like: > > > > ?yum -y install gpm --nogpgcheck Sorry that's "gdm": yum -y install gdm --nogpgcheck > > Martin -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From martin at martindengler.com Tue Sep 29 11:41:41 2009 From: martin at martindengler.com (Martin Dengler) Date: Tue, 29 Sep 2009 12:41:41 +0100 Subject: New SoaS [XO-1] build soas70 Message-ID: <20090929114141.GB32229@ops-13.xades.com> New Sugar-on-a-Stick [XO-1] build soas70 is done. This has a fix for gdm / X startup, though it has not been tested. I imagine there is still a Browse (and more) X crash bug that I emailed about earlier. Size changes: ------------ total SoaS ext3 size / change in size: 1442.70M / -104K (change) total SoaS-for-XO-1 NAND size / change in size: 608.47M / 0K (change) Package changes: --------------- --- soas69.tree.packages.txt 2009-09-28 17:01:57.000000000 +0000 +++ soas70.tree.packages.txt 2009-09-29 05:36:03.000000000 +0000 at-3.1.10-37.fc12.i686 -at-spi-1.28.0-1.fc12.i686 +at-spi-1.28.0-2.fc12.i686 atk-1.28.0-1.fc12.i686 -atlas-sse-3.8.3-9.fc12.i686 +atlas-3.8.3-10.fc12.i686 atmel-firmware-1.3-6.noarch cups-libs-1.4.1-5.fc12.i686 -curl-7.19.6-9.fc12.i686 +curl-7.19.6-10.fc12.i686 cyrus-sasl-2.1.23-4.fc12.i686 fontconfig-2.7.3-1.fc12.i686 -fontpackages-filesystem-1.24-1.fc12.noarch +fontpackages-filesystem-1.26-1.fc12.noarch fprintd-0.1-15.git04fd09cfa.fc12.i686 htmlview-4.0.0-6.fc12.noarch -hulahop-0.5.2-1.fc12.i686 +hulahop-0.6.0-2.fc12.i686 hunspell-1.2.8-12.fc12.i686 libcroco-0.6.2-3.fc12.i686 -libcurl-7.19.6-9.fc12.i686 +libcurl-7.19.6-10.fc12.i686 libdaemon-0.13-3.fc12.i686 nspr-4.8-2.fc12.i686 -nss-3.12.4-10.fc12.i686 +nss-3.12.4-12.fc12.i686 nss-softokn-3.12.4-10.fc12.i686 sudo-1.7.1-7.fc12.i686 -sugar-0.85.8-2.fc12.i686 +sugar-0.86.0-1.fc12.i686 sugar-artwork-0.86.0-1.fc12.i686 sugar-base-0.86.0-1.fc12.i686 -sugar-datastore-0.85.4-3.fc12.i686 -sugar-presence-service-0.85.3-1.fc12.noarch -sugar-toolkit-0.85.8-1.fc12.i686 +sugar-datastore-0.86.0-1.fc12.i686 +sugar-presence-service-0.86.0-1.fc12.noarch +sugar-toolkit-0.86.0-1.fc12.i686 symlinks-1.2-34.fc12.i686 How to get it: ------------- Download from http://people.sugarlabs.org/~mtd/soas Caveats/Known Issues: Please reply or comment on the Fedora/Redhat bug report if you see any of these. - XO-1 camera not recognised in Record / Cheese https://bugzilla.redhat.com/show_bug.cgi?id=498900 - XO-1 SD boots sometimes fail (mount: unknown filesystem type: 'jffs2') https://bugzilla.redhat.com/show_bug.cgi?id=500196 Before reporting bugs, it'd be nice if one could search the fedora bugzilla; start with this bug: https://bugzilla.redhat.com/show_bug.cgi?id=461806 Quickstart: ---------- either: copy-nand u:\soas??xo.img or: (2g or larger removable) cat soas??xo.4gremovable.tar.lzma | lzma -dc - | tar xf - -O > /dev/sdX or: (4g or larger removable) cat soas??xo.2gremovable.tar.lzma | lzma -dc - | tar xf - -O > /dev/sdX Installation instructions: ------------------------- http://people.sugarlabs.org/~mtd/soas/README.txt Files: ----- soas70.iso - iso9990 file system (for use with livecd-iso-to-disk) soas70.tree.tar.lzma - for hacking soas70xo.img - for ... soas70xo.crc - ... copy-nand'ing soas70xo.plc - ... NANDblast'ing soas70.4gremovable.img.tar.lzma - for simply writing to 4 gig removable devices: cat soas70.4gremovable.tar.lzma | lzma -dc - | tar xf - -O > /dev/sdX soas70.2gremovable.img.tar.lzma - for simply writing to 2 gig removable devices: cat soas70.2gremovable.tar.lzma | lzma -dc - | tar xf - -O > /dev/sdX Build date: Tue Sep 29 06:55:47 UTC 2009 ----- End forwarded message ----- -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From mikus at bga.com Tue Sep 29 12:01:41 2009 From: mikus at bga.com (Mikus Grinbergs) Date: Tue, 29 Sep 2009 08:01:41 -0400 Subject: New SoaS build soas68 Message-ID: <4AC1F725.4060300@bga.com> > gpm autologin was broken in rawhide; it's now fixed. If you do > something like: > yum -y install gpm --nogpgcheck > ..it should fix it. Using yum to (re)install gdm did get beyond the earlier stall -- though I had to first press to "awaken" the login window, and follow that by clicking on "soas user" to actually launch the login. This shows the vulnerability of the login process to a "single point of failure". When 'gdm autologin' broke, the user was *not* being offered any opportunity to bring up the gui any other way (once the gdm had stalled, even startx from a text console did not work). mikus From martin at martindengler.com Tue Sep 29 14:13:51 2009 From: martin at martindengler.com (Martin Dengler) Date: Tue, 29 Sep 2009 15:13:51 +0100 Subject: New SoaS build soas68 In-Reply-To: <4AC1F725.4060300@bga.com> References: <4AC1F725.4060300@bga.com> Message-ID: <20090929141351.GE32229@ops-13.xades.com> On Tue, Sep 29, 2009 at 08:01:41AM -0400, Mikus Grinbergs wrote: >> gpm autologin was broken in rawhide; it's now fixed. If you do >> something like: >> yum -y install gpm --nogpgcheck >> ..it should fix it. > > Using yum to (re)install gdm did get beyond the earlier stall -- though I > had to first press to "awaken" the login window, and follow that by > clicking on "soas user" to actually launch the login. > > This shows the vulnerability of the login process to a "single point > of failure". When 'gdm autologin' broke, the user was *not* being > offered any opportunity to bring up the gui any other way Indeed. One alternative is to write our own session manager, like OLPC has. I'm not signing up for that. > (once the gdm had stalled, even startx from a text console did not > work). I did actually have startx work fine for me (as liveuser). It didn't work for you? > mikus Martin -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From mikus at bga.com Tue Sep 29 14:14:34 2009 From: mikus at bga.com (Mikus Grinbergs) Date: Tue, 29 Sep 2009 10:14:34 -0400 Subject: soas70xo impressions Message-ID: <4AC2164A.8050502@bga.com> Disclaimer: I am not asking for help; I'm sharing my experiences. Ran with soas70xo (booted from nand) on my XO-1. Many of the difficulties with previous SoaS builds were still present, with some new ones added. The "X crash" scrolling problem is a BLOCKER - for instance, because of this problem I cannot change the Jabber server specification. Speak did not produce any sound. [It did not even attempt to wiggle its mouth until I in Frame "unmuted" the volume.] Record did not launch. Browse came up with its display window size significantly exceeding the physical size of the XO screen. 'rpm -q kernel' attests to sloppy composing of the build. With now more exposure to it, I still do not like the new toolbar design. The XO has a *small* display screen. Now many Activity capabilities (such as 'Edit' in Terminal) can only be invoked from a secondary toolbar that drops down from the primary toolbar. The two toolbars together take up a significant amount of XO screen real estate. And each time the secondary toolbar needs to be shown or hidden, it takes one *extra* click (after me having to move the cursor off the part of the screen that I was doing my work on). I notice that now Sugar 0.86 has been "upstreamed" into Rawhide. I suspect that some Activities still need changing to fit 0.86. mikus From mikus at bga.com Tue Sep 29 14:32:07 2009 From: mikus at bga.com (Mikus Grinbergs) Date: Tue, 29 Sep 2009 10:32:07 -0400 Subject: New SoaS build soas68 Message-ID: <4AC21A67.2020707@bga.com> >> (once the gdm had stalled, even startx from a text console did not >> work). > > I did actually have startx work fine for me (as liveuser). It didn't > work for you? It did not. Entered 'startx -- :1' at a text console. The system did not bring up a GUI session for this startx command. After waiting a while, I did a ctrl-C and looked at /var/log/Xorg.1.log -- saw nothing that was not normal -- it had come up with all the usual messages, then had closed when I killed the startx -- but there was no clue for how come the screen (should have been on ctrl-alt-F8) was not shown. mikus p.s. Would no longer be able to reproduce - have moved on to soas70 From gary at garycmartin.com Tue Sep 29 17:01:52 2009 From: gary at garycmartin.com (Gary C Martin) Date: Tue, 29 Sep 2009 18:01:52 +0100 Subject: soas70xo impressions In-Reply-To: <4AC2164A.8050502@bga.com> References: <4AC2164A.8050502@bga.com> Message-ID: <0BFC5BB5-DC6D-46CE-8DA6-8689FBB21529@garycmartin.com> Hi Mikus, On 29 Sep 2009, at 15:14, Mikus Grinbergs wrote: > With now more exposure to it, I still do not like the new toolbar > design. The XO has a *small* display screen. Now many Activity > capabilities (such as 'Edit' in Terminal) can only be invoked from a > secondary toolbar that drops down from the primary toolbar. The two > toolbars together take up a significant amount of XO screen real > estate. And each time the secondary toolbar needs to be shown or > hidden, it takes one *extra* click (after me having to move the > cursor off the part of the screen that I was doing my work on). Just a quick hint that you do not need to click if you don't want to. The secondary toolbars hover expose (or right click if you want them instantly), in this mode they work just like any palette menu, taking up no canvas space, forcing no canvas redraw. I would argue your 'significant amount of XO screen real estate' is a rather large exaggeration ;-) Here's a quick screen shot comparison for the worst case when you have a secondary toolbar locked open to the canvas. On a 1200x900 display, two layers of toolbars is only an extra ~30 pixels, and you have the choice of not locking open the secondary toolbar (especially for edit, just use the keyboard shortcuts), gaining you an extra ~40 vertical pixels of canvas space. -------------- next part -------------- A non-text attachment was scrubbed... Name: calculater_old_vs_new.png Type: image/png Size: 71272 bytes Desc: not available URL: -------------- next part -------------- Regards, --Gary From walter.bender at gmail.com Tue Sep 29 17:10:45 2009 From: walter.bender at gmail.com (Walter Bender) Date: Tue, 29 Sep 2009 13:10:45 -0400 Subject: soas70xo impressions In-Reply-To: <0BFC5BB5-DC6D-46CE-8DA6-8689FBB21529@garycmartin.com> References: <4AC2164A.8050502@bga.com> <0BFC5BB5-DC6D-46CE-8DA6-8689FBB21529@garycmartin.com> Message-ID: On Tue, Sep 29, 2009 at 1:01 PM, Gary C Martin wrote: > Hi Mikus, > > On 29 Sep 2009, at 15:14, Mikus Grinbergs wrote: > >> With now more exposure to it, I still do not like the new toolbar >> design. ?The XO has a *small* display screen. ?Now many Activity >> capabilities (such as 'Edit' in Terminal) can only be invoked from a >> secondary toolbar that drops down from the primary toolbar. ?The two >> toolbars together take up a significant amount of XO screen real >> estate. ?And each time the secondary toolbar needs to be shown or >> hidden, it takes one *extra* click (after me having to move the >> cursor off the part of the screen that I was doing my work on). > > Just a quick hint that you do not need to click if you don't want to. The > secondary toolbars hover expose (or right click if you want them instantly), > in this mode they work just like any palette menu, taking up no canvas > space, forcing no canvas redraw. > > I would argue your 'significant amount of XO screen real estate' is a rather > large exaggeration ;-) > > Here's a quick screen shot comparison for the worst case when you have a > secondary toolbar locked open to the canvas. On a 1200x900 display, two > layers of toolbars is only an extra ~30 pixels, and you have the choice of > not locking open the secondary toolbar (especially for edit, just use the > keyboard shortcuts), gaining you an extra ~40 vertical pixels of canvas > space. > Not to mention that many (most) toolbar items have keyboard shortcuts. Edit certainly does :) -walter > > Regards, > --Gary > _______________________________________________ > Devel mailing list > Devel at lists.laptop.org > http://lists.laptop.org/listinfo/devel > > -- Walter Bender Sugar Labs http://www.sugarlabs.org From mavrothal at yahoo.com Tue Sep 29 18:33:00 2009 From: mavrothal at yahoo.com (Yioryos Asprobounitis) Date: Tue, 29 Sep 2009 11:33:00 -0700 (PDT) Subject: New SoaS [XO-1] build soas70 In-Reply-To: <20090929114141.GB32229@ops-13.xades.com> Message-ID: <384124.22432.qm@web65510.mail.ac4.yahoo.com> It is apparent that the script that generates the "removable" builds is not making the olpc.fth file. Would you please let us know which change should we look for in the build announcement before we waste your bandwidth and our time? BTW various olpc.fth files failed with kernel panic and inability to find the boot device. --- On Tue, 9/29/09, Martin Dengler wrote: > From: Martin Dengler > Subject: New SoaS [XO-1] build soas70 > To: fedora-olpc-list at redhat.com > Date: Tuesday, September 29, 2009, 7:41 AM > > New Sugar-on-a-Stick [XO-1] build soas70 is done. > > This has a fix for gdm / X startup, though it has not been > tested. > > I imagine there is still a Browse (and more) X crash bug > that I > emailed about earlier. > > > Size changes: > ------------ > > total SoaS ext3 size / change in size: 1442.70M / -104K > (change) > total SoaS-for-XO-1 NAND size / change in size: 608.47M / > 0K (change) > > > Package changes: > --------------- > --- soas69.tree.packages.txt??? 2009-09-28 > 17:01:57.000000000 +0000 > +++ soas70.tree.packages.txt??? 2009-09-29 > 05:36:03.000000000 +0000 > at-3.1.10-37.fc12.i686 > -at-spi-1.28.0-1.fc12.i686 > +at-spi-1.28.0-2.fc12.i686 > atk-1.28.0-1.fc12.i686 > -atlas-sse-3.8.3-9.fc12.i686 > +atlas-3.8.3-10.fc12.i686 > atmel-firmware-1.3-6.noarch > cups-libs-1.4.1-5.fc12.i686 > -curl-7.19.6-9.fc12.i686 > +curl-7.19.6-10.fc12.i686 > cyrus-sasl-2.1.23-4.fc12.i686 > fontconfig-2.7.3-1.fc12.i686 > -fontpackages-filesystem-1.24-1.fc12.noarch > +fontpackages-filesystem-1.26-1.fc12.noarch > fprintd-0.1-15.git04fd09cfa.fc12.i686 > htmlview-4.0.0-6.fc12.noarch > -hulahop-0.5.2-1.fc12.i686 > +hulahop-0.6.0-2.fc12.i686 > hunspell-1.2.8-12.fc12.i686 > libcroco-0.6.2-3.fc12.i686 > -libcurl-7.19.6-9.fc12.i686 > +libcurl-7.19.6-10.fc12.i686 > libdaemon-0.13-3.fc12.i686 > nspr-4.8-2.fc12.i686 > -nss-3.12.4-10.fc12.i686 > +nss-3.12.4-12.fc12.i686 > nss-softokn-3.12.4-10.fc12.i686 > sudo-1.7.1-7.fc12.i686 > -sugar-0.85.8-2.fc12.i686 > +sugar-0.86.0-1.fc12.i686 > sugar-artwork-0.86.0-1.fc12.i686 > sugar-base-0.86.0-1.fc12.i686 > -sugar-datastore-0.85.4-3.fc12.i686 > -sugar-presence-service-0.85.3-1.fc12.noarch > -sugar-toolkit-0.85.8-1.fc12.i686 > +sugar-datastore-0.86.0-1.fc12.i686 > +sugar-presence-service-0.86.0-1.fc12.noarch > +sugar-toolkit-0.86.0-1.fc12.i686 > symlinks-1.2-34.fc12.i686 > > > How to get it: > ------------- > Download from http://people.sugarlabs.org/~mtd/soas > > > Caveats/Known Issues: > > Please reply or comment on the Fedora/Redhat bug report if > you see any > of these. > > - XO-1 camera not recognised in Record / Cheese > ? https://bugzilla.redhat.com/show_bug.cgi?id=498900 > > - XO-1 SD boots sometimes fail (mount: unknown filesystem > type: > ? 'jffs2') > ? https://bugzilla.redhat.com/show_bug.cgi?id=500196 > > Before reporting bugs, it'd be nice if one could search the > fedora > bugzilla; start with this bug: > https://bugzilla.redhat.com/show_bug.cgi?id=461806 > > > Quickstart: > ---------- > either: > ? copy-nand u:\soas??xo.img > or: (2g or larger removable) > ? cat soas??xo.4gremovable.tar.lzma | lzma -dc - | tar > xf - -O > /dev/sdX > or: (4g or larger removable) > ? cat soas??xo.2gremovable.tar.lzma | lzma -dc - | tar > xf - -O > /dev/sdX > > > Installation instructions: > ------------------------- > > http://people.sugarlabs.org/~mtd/soas/README.txt > > > Files: > ----- > > soas70.iso - iso9990 file system (for use with > livecd-iso-to-disk) > soas70.tree.tar.lzma - for hacking > > soas70xo.img - for ... > soas70xo.crc - ... copy-nand'ing > soas70xo.plc - ... NANDblast'ing > > soas70.4gremovable.img.tar.lzma - for simply writing to 4 > gig removable devices: > cat soas70.4gremovable.tar.lzma | lzma -dc - | tar xf - -O > > /dev/sdX > > soas70.2gremovable.img.tar.lzma - for simply writing to 2 > gig removable devices: > cat soas70.2gremovable.tar.lzma | lzma -dc - | tar xf - -O > > /dev/sdX > > Build date: Tue Sep 29 06:55:47 UTC 2009 > > > ----- End forwarded message ----- > > -----Inline Attachment Follows----- > > _______________________________________________ > Fedora-olpc-list mailing list > Fedora-olpc-list at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-olpc-list From martin at martindengler.com Tue Sep 29 18:49:44 2009 From: martin at martindengler.com (Martin Dengler) Date: Tue, 29 Sep 2009 19:49:44 +0100 Subject: New SoaS [XO-1] build soas70 In-Reply-To: <384124.22432.qm@web65510.mail.ac4.yahoo.com> References: <20090929114141.GB32229@ops-13.xades.com> <384124.22432.qm@web65510.mail.ac4.yahoo.com> Message-ID: <20090929184944.GK32229@ops-13.xades.com> On Tue, Sep 29, 2009 at 11:33:00AM -0700, Yioryos Asprobounitis wrote: > It is apparent that the script that generates the "removable" builds > is not making the olpc.fth file. > [...] > BTW various olpc.fth files failed with kernel panic and inability to find the boot device. Not making a /boot/olpc.fth or making a useless one? I'll fix it up. It's pretty odd, though, since the removable builds are made from exactly the same directory tree as the .img files. > Would you please let us know which change should we look for in the > build announcement before we waste your bandwidth and our time? Certainly. It's quite frustrating to waste all that time. I should figure out why we're not getting .xdelta files, as well. Should save some download time. Martin -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From martin at martindengler.com Tue Sep 29 18:59:52 2009 From: martin at martindengler.com (Martin Dengler) Date: Tue, 29 Sep 2009 19:59:52 +0100 Subject: soas70xo impressions In-Reply-To: <4AC2164A.8050502@bga.com> References: <4AC2164A.8050502@bga.com> Message-ID: <20090929185951.GL32229@ops-13.xades.com> On Tue, Sep 29, 2009 at 10:14:34AM -0400, Mikus Grinbergs wrote: > The "X crash" scrolling problem is a BLOCKER I know, you heard it here first. Care to bugzilla it? > 'rpm -q kernel' attests to sloppy composing of the build. Sloppy is hardly the moniker for the general practice of having two kernels installed (one backup/running and one to-be-booted into, for example). The way the kickstart file installs the OLPC one is indeed terrible, and I'm not proud of it. > I notice that now Sugar 0.86 has been "upstreamed" into Rawhide. > I suspect that some Activities still need changing to fit 0.86. Oh yeah. It's going to get worse before it gets better, I think. > mikus Martin -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From pbrobinson at gmail.com Tue Sep 29 19:17:50 2009 From: pbrobinson at gmail.com (Peter Robinson) Date: Tue, 29 Sep 2009 20:17:50 +0100 Subject: soas70xo impressions In-Reply-To: <20090929185951.GL32229@ops-13.xades.com> References: <4AC2164A.8050502@bga.com> <20090929185951.GL32229@ops-13.xades.com> Message-ID: <5256d0b0909291217na20670cxb0080b1a97ac3a54@mail.gmail.com> >> The "X crash" scrolling problem is a BLOCKER > > I know, you heard it here first. ?Care to bugzilla it? > >> 'rpm -q kernel' attests to sloppy composing of the build. > > Sloppy is hardly the moniker for the general practice of having two > kernels installed (one backup/running and one to-be-booted into, for > example). ?The way the kickstart file installs the OLPC one is indeed > terrible, and I'm not proud of it. > >> I notice that now Sugar 0.86 has been "upstreamed" into Rawhide. >> I suspect that some Activities still need changing to fit 0.86. > > Oh yeah. ?It's going to get worse before it gets better, I think. Record would be one of those. Peter From mikus at bga.com Tue Sep 29 18:32:58 2009 From: mikus at bga.com (Mikus Grinbergs) Date: Tue, 29 Sep 2009 14:32:58 -0400 Subject: soas70xo impressions Message-ID: <4AC252DA.7070909@bga.com> Regarding _using_ the 'new' toolbar: > I would argue your 'significant amount of XO screen real estate' is a > rather large exaggeration ;-) My XO-1 screen is 4.5 inches vertically. On soas70xo, two toolbars together visually "black out" .75 inches vertically. That's 1/6 of my entire screen. [What I'm remembering is the *total* visual impression of those two totally black toolbars; what you are measuring is the *incremental* area of that second toolbar vs. the less obtrusive former tabs.] > Just a quick hint that you do not need to click if you don't want to I did not mind the click, since I was already clicking on the old toolbar. [To me, more time gets wasted when hovering than when clicking.] What I see as a duplication of effort (unless I leave the second toolbar in place, which I perceive as taking away limited XO screen real estate) is that I have to first [click|hover] to bringup the second toolbar - only then can I [click|whatever] on the service I want. With the old design, I *would* leave the appropriate tab selected, yet not feel as though by doing so I was obstructing part of my "doing-the-actual-work" area. mikus p.s. I suspect that on an XO-1 with Sugar 0.86 I will end up switching to full screen whenever possible, thereby visually _eliminating_ the distraction of seeing those thick toolbars. From martin at martindengler.com Tue Sep 29 20:06:32 2009 From: martin at martindengler.com (Martin Dengler) Date: Tue, 29 Sep 2009 21:06:32 +0100 Subject: New SoaS [XO-1] build soas70 In-Reply-To: <20090929184944.GK32229@ops-13.xades.com> References: <20090929114141.GB32229@ops-13.xades.com> <384124.22432.qm@web65510.mail.ac4.yahoo.com> <20090929184944.GK32229@ops-13.xades.com> Message-ID: <20090929200631.GO32229@ops-13.xades.com> On Tue, Sep 29, 2009 at 07:49:44PM +0100, Martin Dengler wrote: > On Tue, Sep 29, 2009 at 11:33:00AM -0700, Yioryos Asprobounitis wrote: > > It is apparent that the script that generates the "removable" builds > > is not making the olpc.fth file. > > [...] > > BTW various olpc.fth files failed with kernel panic and inability to find the boot device. > > Not making a /boot/olpc.fth or making a useless one? I'll fix it up. > It's pretty odd, though, since the removable builds are made from > exactly the same directory tree as the .img files. Though it's not hard, I managed to fool myself here: the removable images are not XO builds (though they were at one point). They are for "normal" SoaS usage. It's only a little odd for me to put an olpc.fth on the "non-XO" installs, and only a small increment in the already ridiculous disk space usage to make both XO and non-XO .removable images. Can you offer any guidance as to what you'd use? > Martin Martin -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From mavrothal at yahoo.com Tue Sep 29 20:48:32 2009 From: mavrothal at yahoo.com (Yioryos Asprobounitis) Date: Tue, 29 Sep 2009 13:48:32 -0700 (PDT) Subject: New SoaS [XO-1] build soas70 In-Reply-To: <20090929184944.GK32229@ops-13.xades.com> Message-ID: <366422.88573.qm@web65516.mail.ac4.yahoo.com> --- On Tue, 9/29/09, Martin Dengler wrote: > From: Martin Dengler > Subject: Re: New SoaS [XO-1] build soas70 > To: "Yioryos Asprobounitis" > Cc: fedora-olpc-list at redhat.com > Date: Tuesday, September 29, 2009, 2:49 PM > On Tue, Sep 29, 2009 at 11:33:00AM > -0700, Yioryos Asprobounitis wrote: > > It is apparent that the script that generates the > "removable" builds > > is not making the olpc.fth file. > > [...] > > BTW various olpc.fth files failed with kernel panic > and inability to find the boot device. > > Not making a /boot/olpc.fth or making a useless one? No olpc.fth file at all. Also no vmlinuz and olpcrd.img simlinks in /boot. Finally the /boot folder permissions (555) look strange. The same permissions are for also for /bin. I'll > fix it up. > It's pretty odd, though, since the removable builds are > made from > exactly the same directory tree as the .img files. > > > Would you please let us know which change should we > look for in the > > build announcement before we waste your bandwidth and > our time? > > Certainly.? It's quite frustrating to waste all that > time.? I should > figure out why we're not getting .xdelta files, as > well.? Should save > some download time. > > Martin > From mavrothal at yahoo.com Tue Sep 29 20:56:07 2009 From: mavrothal at yahoo.com (Yioryos Asprobounitis) Date: Tue, 29 Sep 2009 13:56:07 -0700 (PDT) Subject: New SoaS [XO-1] build soas70 In-Reply-To: <20090929200631.GO32229@ops-13.xades.com> Message-ID: <489508.38019.qm@web65507.mail.ac4.yahoo.com> --- On Tue, 9/29/09, Martin Dengler wrote: > From: Martin Dengler > Subject: Re: New SoaS [XO-1] build soas70 > To: "Yioryos Asprobounitis" > Cc: fedora-olpc-list at redhat.com > Date: Tuesday, September 29, 2009, 4:06 PM > On Tue, Sep 29, 2009 at 07:49:44PM > +0100, Martin Dengler wrote: > > On Tue, Sep 29, 2009 at 11:33:00AM -0700, Yioryos > Asprobounitis wrote: > > > It is apparent that the script that generates the > "removable" builds > > > is not making the olpc.fth file. > > > [...] > > > BTW various olpc.fth files failed with kernel > panic and inability to find the boot device. > > > > Not making a /boot/olpc.fth or making a useless one? > I'll fix it up. > > It's pretty odd, though, since the removable builds > are made from > > exactly the same directory tree as the .img files. > > Though it's not hard, I managed to fool myself here: the > removable > images are not XO builds (though they were at one > point).? They are > for "normal" SoaS usage. > > It's only a little odd for me to put an olpc.fth on the > "non-XO" > installs, and only a small increment in the already > ridiculous disk > space usage to make both XO and non-XO .removable images. > > Can you offer any guidance as to what you'd use? Well, I do not think that non-XO removable images are needed for soasXXxo builds. XO removable builds are very handy since they allow kids to "play" with the XO and dads/moms with testing :-) > > > Martin > > Martin > > > > From martin at martindengler.com Tue Sep 29 23:05:13 2009 From: martin at martindengler.com (Martin Dengler) Date: Wed, 30 Sep 2009 00:05:13 +0100 Subject: New SoaS [XO-1] build soas70 In-Reply-To: <20090929200631.GO32229@ops-13.xades.com> References: <20090929114141.GB32229@ops-13.xades.com> <384124.22432.qm@web65510.mail.ac4.yahoo.com> <20090929184944.GK32229@ops-13.xades.com> <20090929200631.GO32229@ops-13.xades.com> Message-ID: <20090929230511.GC11568@ops-13.xades.com> On Tue, Sep 29, 2009 at 09:06:31PM +0100, Martin Dengler wrote: > On Tue, Sep 29, 2009 at 07:49:44PM +0100, Martin Dengler wrote: > > On Tue, Sep 29, 2009 at 11:33:00AM -0700, Yioryos Asprobounitis wrote: > > > It is apparent that the script that generates the "removable" builds > > > is not making the olpc.fth file. > > > [...] > > > BTW various olpc.fth files failed with kernel panic and inability to find the boot device. > > It's only a little odd for me to put an olpc.fth on the "non-XO" > installs, and only a small increment in the already ridiculous disk > space usage to make both XO and non-XO .removable images. This is done, and soas71xo* is being synced to people.sugarlabs.org now. Martin -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From mavrothal at yahoo.com Wed Sep 30 07:01:01 2009 From: mavrothal at yahoo.com (Yioryos Asprobounitis) Date: Wed, 30 Sep 2009 00:01:01 -0700 (PDT) Subject: New SoaS [XO-1] build soas70 In-Reply-To: <20090929230511.GC11568@ops-13.xades.com> Message-ID: <279277.70818.qm@web65506.mail.ac4.yahoo.com> --- On Tue, 9/29/09, Martin Dengler wrote: > From: Martin Dengler > Subject: Re: New SoaS [XO-1] build soas70 > To: "Yioryos Asprobounitis" > Cc: fedora-olpc-list at redhat.com > Date: Tuesday, September 29, 2009, 7:05 PM > On Tue, Sep 29, 2009 at 09:06:31PM > +0100, Martin Dengler wrote: > > On Tue, Sep 29, 2009 at 07:49:44PM +0100, Martin > Dengler wrote: > > > On Tue, Sep 29, 2009 at 11:33:00AM -0700, Yioryos > Asprobounitis wrote: > > > > It is apparent that the script that > generates the "removable" builds > > > > is not making the olpc.fth file. > > > > [...] > > > > BTW various olpc.fth files failed with > kernel panic and inability to find the boot device. > > > > It's only a little odd for me to put an olpc.fth on > the "non-XO" > > installs, and only a small increment in the already > ridiculous disk > > space usage to make both XO and non-XO .removable > images. > > This is done, and soas71xo* is being synced to > people.sugarlabs.org > now. soas71xo.2gremovable: olpcrd.img symlink is missing from the /boot folder resulting in kernel panic Addition of the symlink allows booting to proceed but dracut complains about sysninx not being "0" and quits while booting continues to SCSI read-through and stops there with no USB read/write activity (left it ~10 min) I guess the init script is still coming from wild-type SoaS? More latter when I'll have the chance (unless soas72xo appears :-) From martin at martindengler.com Wed Sep 30 08:31:18 2009 From: martin at martindengler.com (Martin Dengler) Date: Wed, 30 Sep 2009 09:31:18 +0100 Subject: New SoaS [XO-1] build soas70 In-Reply-To: <279277.70818.qm@web65506.mail.ac4.yahoo.com> References: <20090929230511.GC11568@ops-13.xades.com> <279277.70818.qm@web65506.mail.ac4.yahoo.com> Message-ID: <20090930083118.GD11568@ops-13.xades.com> On Wed, Sep 30, 2009 at 12:01:01AM -0700, Yioryos Asprobounitis wrote: > soas71xo.2gremovable: olpcrd.img symlink is missing from the /boot > folder This is by design. The initrd olpc.fth asks for is /boot/initrd.img. olpcrd.img has not been used for a long time, and initrd.img is not necessary to boot the included kernel on the XO-1. > [...] resulting in kernel panic There should be no kernel panic due to a missing initrd.img. Are you really trying to boot from the removable image? Its olpc.fth looks fine to me. Perhaps you could try to manually boot from the removable device: 1) Power on the XO-1 with the SD card in it 2) Press Esc to get to the OFW prompt 3) Check the SD card looks ok with "dir sd:\boot" 4) Boot from the SD card with these OFW commands: " ro root=LABEL=OLPCRoot rootwait" to boot-file " sd:\boot\vmlinuz" to boot-device setup-smbios boot What happens then? Do you see the green and blue "sugarlabs" logo when the kernel messages appear? If you see a kernel panic about "can't find root device", try with this boot-file: " ro root=/dev/mmcblk0p1 rootwait" to boot-file [all the other commands the same] > I guess the init script is still coming from wild-type SoaS? olpc.fth should be suitable for both removable images, but I've not tested the "root=OLPCRoot" kernel command line behaviour as much as I'd like. > More latter when I'll have the chance (unless soas72xo appears :-) Thanks for your time and the testing results. Martin -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From mavrothal at yahoo.com Wed Sep 30 08:56:45 2009 From: mavrothal at yahoo.com (Yioryos Asprobounitis) Date: Wed, 30 Sep 2009 01:56:45 -0700 (PDT) Subject: New SoaS [XO-1] build soas70 In-Reply-To: <20090930083118.GD11568@ops-13.xades.com> Message-ID: <996473.76199.qm@web65506.mail.ac4.yahoo.com> --- On Wed, 9/30/09, Martin Dengler wrote: > From: Martin Dengler > Subject: Re: New SoaS [XO-1] build soas70 > To: "Yioryos Asprobounitis" > Cc: fedora-olpc-list at redhat.com > Date: Wednesday, September 30, 2009, 4:31 AM > On Wed, Sep 30, 2009 at 12:01:01AM > -0700, Yioryos Asprobounitis wrote: > > soas71xo.2gremovable: olpcrd.img symlink is missing > from the /boot > > folder > > This is by design.? The initrd olpc.fth asks for is > /boot/initrd.img. olpcrd.img has not been used for a long > time, and > initrd.img is not necessary to boot the included kernel on > the XO-1. However, the olpc.fth points to \boot\initrd.img Looks like a SoaS olpc.fth generated by liveCD-to-usb and tries to generate an overlay I think. > > > [...] resulting in kernel panic > > There should be no kernel panic due to a missing > initrd.img.? Are you > really trying to boot from the removable image?? Its > olpc.fth looks > fine to me. I downloaded soas71xo.2gremovable.img.tar.lzma and then cat soas71xo.2gremovable.tar.lzma | lzma -dc - | tar xf - -O > /dev/sda to a _USB_ stick (not SD card) > > Perhaps you could try to manually boot from the removable > device: > > 1) Power on the XO-1 with the SD card in it > 2) Press Esc to get to the OFW prompt > 3) Check the SD card looks ok with "dir sd:\boot" > 4) Boot from the SD card with these OFW commands: > > " ro root=LABEL=OLPCRoot rootwait" to boot-file > " sd:\boot\vmlinuz" to boot-device > setup-smbios > boot > > > What happens then?? Do you see the green and blue > "sugarlabs" logo > when the kernel messages appear? > > If you see a kernel panic about "can't find root device", > try with > this boot-file: > > " ro root=/dev/mmcblk0p1 rootwait" to boot-file > [all the other commands the same] > This will have to wait for latter. so the console=... etc parameters are not needed in the boot-file string? > > > I? guess the init script is still coming from > wild-type SoaS? > > olpc.fth should be suitable for both removable images, but > I've not > tested the "root=OLPCRoot" kernel command line behaviour as > much as > I'd like. > > > More latter when I'll have the chance (unless soas72xo > appears :-) > > Thanks for your time and the testing results. > > Martin > From martin at martindengler.com Wed Sep 30 09:49:17 2009 From: martin at martindengler.com (Martin Dengler) Date: Wed, 30 Sep 2009 10:49:17 +0100 Subject: New SoaS [XO-1] build soas70 In-Reply-To: <996473.76199.qm@web65506.mail.ac4.yahoo.com> References: <20090930083118.GD11568@ops-13.xades.com> <996473.76199.qm@web65506.mail.ac4.yahoo.com> Message-ID: <20090930094917.GF11568@ops-13.xades.com> On Wed, Sep 30, 2009 at 01:56:45AM -0700, Yioryos Asprobounitis wrote: > > > --- On Wed, 9/30/09, Martin Dengler wrote: > > > From: Martin Dengler > > Subject: Re: New SoaS [XO-1] build soas70 > > To: "Yioryos Asprobounitis" > > Cc: fedora-olpc-list at redhat.com > > Date: Wednesday, September 30, 2009, 4:31 AM > > On Wed, Sep 30, 2009 at 12:01:01AM > > -0700, Yioryos Asprobounitis wrote: > > > soas71xo.2gremovable: olpcrd.img symlink is missing > > from the /boot > > > folder > > > > This is by design.? The initrd olpc.fth asks for is > > /boot/initrd.img. olpcrd.img has not been used for a long > > time, and > > initrd.img is not necessary to boot the included kernel on > > the XO-1. > > However, the olpc.fth points to \boot\initrd.img Well, it points to something a bit different than that, but that's not really germane. The lack of the initrd.img file in the specified location will cause OFW to print an error message, and then carry on giving control to the linux kernel. So unless the kernel needs the initrd (in the case, it doesn't), you don't have to worry about it. > Looks like a SoaS olpc.fth generated by liveCD-to-usb and tries to > generate an overlay I think. There's no livecd-to-usb script involved. There is no overlay involved either. > > > [...] resulting in kernel panic > > > > There should be no kernel panic due to a missing > > initrd.img.? Are you > > really trying to boot from the removable image?? Its > > olpc.fth looks > > fine to me. > > I downloaded soas71xo.2gremovable.img.tar.lzma and then > cat soas71xo.2gremovable.tar.lzma | lzma -dc - | tar xf - -O > > /dev/sda to a _USB_ stick (not SD card) Ok. So the instructions should be: 1) Power on the XO-1 with the USB stick in it 2) Press Esc to get to the OFW prompt 3) Check the USB stick looks ok with "dir u:\boot" 4) Boot from the USB stick with these OFW commands: " ro root=LABEL=OLPCRoot rootwait" to boot-file " u:\boot\vmlinuz" to boot-device setup-smbios boot Then it'd be good to observe what happens. Do you see the green and blue "sugarlabs" logo when the kernel messages appear? > so the console=... etc parameters are not needed in the boot-file > string? They're good to have in normal operation but are not required to get to a basic runlevel 3 or 5. Martin -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From pbrobinson at gmail.com Wed Sep 30 10:50:43 2009 From: pbrobinson at gmail.com (Peter Robinson) Date: Wed, 30 Sep 2009 11:50:43 +0100 Subject: cvs branched for Fedora 12 Message-ID: <5256d0b0909300350r67c00283l1ad4f43df6d5eb92@mail.gmail.com> Hi All, Just a reminder to those people that maintain packages in upstream Fedora that as of now the packages have been branched for F-12. That means if you need to build a package for Fedora-12 it will need to be built in the F-12 branch. If you do this also please ensure you commit the build to the devel (the one that will become F-13) as well to ensure that both places have the latest build. Also as of today we are in Freeze in preparation for the Fedora 12 Beta and in preparation for final. As a result any bug fix packages built for F-12 will need a rel-eng ticket so they can be tagged into the release. If you need any assistance or have any queries about any of the above by all means poke me on or off list and I'll be glad to help out. Cheers, Peter From mavrothal at yahoo.com Wed Sep 30 19:06:11 2009 From: mavrothal at yahoo.com (Yioryos Asprobounitis) Date: Wed, 30 Sep 2009 12:06:11 -0700 (PDT) Subject: New SoaS [XO-1] build soas70 In-Reply-To: <20090930094917.GF11568@ops-13.xades.com> Message-ID: <96385.42464.qm@web65513.mail.ac4.yahoo.com> --- On Wed, 9/30/09, Martin Dengler wrote: > From: Martin Dengler > Subject: Re: New SoaS [XO-1] build soas70 > To: "Yioryos Asprobounitis" > Cc: fedora-olpc-list at redhat.com > Date: Wednesday, September 30, 2009, 5:49 AM > On Wed, Sep 30, 2009 at 01:56:45AM > -0700, Yioryos Asprobounitis wrote: > > > > > > --- On Wed, 9/30/09, Martin Dengler > wrote: > > > > > From: Martin Dengler > > > Subject: Re: New SoaS [XO-1] build soas70 > > > To: "Yioryos Asprobounitis" > > > Cc: fedora-olpc-list at redhat.com > > > Date: Wednesday, September 30, 2009, 4:31 AM > > > On Wed, Sep 30, 2009 at 12:01:01AM > > > -0700, Yioryos Asprobounitis wrote: > > > > soas71xo.2gremovable: olpcrd.img symlink is > missing > > > from the /boot > > > > folder > > > > > > This is by design.? The initrd olpc.fth asks for > is > > > /boot/initrd.img. olpcrd.img has not been used > for a long > > > time, and > > > initrd.img is not necessary to boot the included > kernel on > > > the XO-1. > > > > However, the olpc.fth points to \boot\initrd.img > > Well, it points to something a bit different than that, but > that's not > really germane. > > The lack of the initrd.img file in the specified location > will cause > OFW to print an error message, and then carry on giving > control to the > linux kernel.? So unless the kernel needs the initrd > (in the case, it > doesn't), you don't have to worry about it. I repeated the process form scratch. The included olpc.fth in the vergin stick _does_ point to initrd.img and the OFW complains that can not open the boot devise and stops there. (more below) > > > Looks like a SoaS olpc.fth generated by liveCD-to-usb > and tries to > > generate an overlay I think. > > There's no livecd-to-usb script involved.? There is no > overlay > involved either. > > > > > [...] resulting in kernel panic > > > > > > There should be no kernel panic due to a missing > > > initrd.img.? Are you > > > really trying to boot from the removable image?? > Its > > > olpc.fth looks > > > fine to me. > > > > I downloaded soas71xo.2gremovable.img.tar.lzma and > then > > cat soas71xo.2gremovable.tar.lzma | lzma -dc - | tar > xf - -O > > > /dev/sda to a _USB_ stick (not SD card) > > Ok.? So the instructions should be: > > 1) Power on the XO-1 with the USB stick in it > 2) Press Esc to get to the OFW prompt > 3) Check the USB stick looks ok with "dir u:\boot" > 4) Boot from the USB stick with these OFW commands: > > " ro root=LABEL=OLPCRoot rootwait" to boot-file > " u:\boot\vmlinuz" to boot-device > setup-smbios > boot > > Then it'd be good to observe what happens. Do you see the > green and > blue "sugarlabs" logo when the kernel messages appear? I made a new olpc.fth file with just these 4 lines after a "\ boot script" line on the top. It does go through the kernel loading with the SL logo on the top and then freezes at: Waiting for root devise LABEL=OLPCRoot... Changing to " ro root=/dev/dsa1 rootwait" to boot-file in case their is label conflict with the NAND which has F11-XO1/os7, results in a freeze at: Waiting for root devise /dev/dsa1 Just to verify that the the stick shows up as "OLPCRoot" on any Linux OS including Sugar and it is /dev/sda1 when booting the XO from the NAND or an SD card. It is ext2 formatted and I did erase the stick just before 'cating' the soas71xo file into it. So certainly will not boot with just the kernel in this setting. > > > so the console=... etc parameters are not needed in > the boot-file > > string? > > They're good to have in normal operation but are not > required to get > to a basic runlevel 3 or 5. > > Martin > From martin at martindengler.com Wed Sep 30 19:59:08 2009 From: martin at martindengler.com (Martin Dengler) Date: Wed, 30 Sep 2009 20:59:08 +0100 Subject: New SoaS [XO-1] build soas70 In-Reply-To: <96385.42464.qm@web65513.mail.ac4.yahoo.com> References: <20090930094917.GF11568@ops-13.xades.com> <96385.42464.qm@web65513.mail.ac4.yahoo.com> Message-ID: <20090930195908.GN11568@ops-13.xades.com> Yioryos, On Wed, Sep 30, 2009 at 12:06:11PM -0700, Yioryos Asprobounitis wrote: > > The lack of the initrd.img file in the specified location will > > cause OFW to print an error message, and then carry on giving > > control to the linux kernel.? So unless the kernel needs the > > initrd (in the case, it doesn't), you don't have to worry about > > it. > > I repeated the process form scratch. Thanks. > The included olpc.fth in the vergin stick _does_ point to initrd.img > and the OFW complains that can not open the boot devise and stops > there. (more below) Careful, some people are going to take your words literally :). It clearly doesn't stop there (you had me worried) from what you said below. > > Then it'd be good to observe what happens. Do you see the green > > and blue "sugarlabs" logo when the kernel messages appear? > > I made a new olpc.fth file with just these 4 lines after a "\ boot script" line on the top. > It does go through the kernel loading with the SL logo on the top and then freezes at: Waiting for root devise LABEL=OLPCRoot... Ok, thanks this is useful - I wonder what's wrong with the label-based root device detection. > Changing to > " ro root=/dev/dsa1 rootwait" to boot-file > in case their is label conflict with the NAND which has F11-XO1/os7, > results in a freeze at: Waiting for root devise /dev/dsa1 It's not /dev/dsa1 but /dev/sda1 . Or is that just a double typo in your email? > Just to verify that the the stick shows up as "OLPCRoot" on any > Linux OS including Sugar and it is /dev/sda1 when booting the XO > from the NAND or an SD card. I wonder if the USB device is detected as something else...if you boot from the NAND and plug in the USB device with the soas71xo filesystem on it, what device node (e.g., /dev/sda1) does its partition show up as? We really should be using the same root-device-specification as livecd-iso-to-disk uses, which would be pretty unambiguous. I'll look into that. > It is ext2 formatted and I did erase the stick just before 'cating' > the soas71xo file into it. Ok, though you don't need to erase the stick first - "cat'ing" the file includes a partition table and filesystem superblocks, so whatever bits are left on the device aren't going to be known as files or anything afterwards. > So certainly will not boot with just the kernel in this setting. Yeah - though precisely one should say that the kernel _is_ booting, it's just not finding the root device. Martin -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From mavrothal at yahoo.com Wed Sep 30 20:23:18 2009 From: mavrothal at yahoo.com (Yioryos Asprobounitis) Date: Wed, 30 Sep 2009 13:23:18 -0700 (PDT) Subject: New SoaS [XO-1] build soas70 In-Reply-To: <20090930195908.GN11568@ops-13.xades.com> Message-ID: <230973.13434.qm@web65513.mail.ac4.yahoo.com> --- On Wed, 9/30/09, Martin Dengler wrote: > From: Martin Dengler > Subject: Re: New SoaS [XO-1] build soas70 > To: "Yioryos Asprobounitis" > Cc: fedora-olpc-list at redhat.com > Date: Wednesday, September 30, 2009, 3:59 PM > Yioryos, > > On Wed, Sep 30, 2009 at 12:06:11PM -0700, Yioryos > Asprobounitis wrote: > > > The included olpc.fth in the vergin stick _does_ point > to initrd.img > > and the OFW complains that can not open the boot > devise and stops > > there. (more below) > > Careful, some people are going to take your words literally > :).? It > clearly doesn't stop there (you had me worried) from what > you said > below. With the original olpc.fth it _does_ stop there. Never get to console. > > > > Then it'd be good to observe what happens. Do you > see the green > > > and blue "sugarlabs" logo when the kernel > messages appear? > > > > I made a new olpc.fth file with just these 4 lines > after a "\ boot script" line on the top. > > It does go through the kernel loading with the SL logo > on the top and then freezes at: Waiting for root devise > LABEL=OLPCRoot... > > Ok, thanks this is useful - I wonder what's wrong with the > label-based > root device detection. > > > Changing to > > " ro root=/dev/dsa1 rootwait" to boot-file > > in case their is label conflict with the NAND which > has F11-XO1/os7, > > results in a freeze at: Waiting for root devise > /dev/dsa1 > > It's not /dev/dsa1 but /dev/sda1 .? Or is that just a > double typo in > your email? one typo one copy/paste :-) > > > Just to verify that the the stick shows up as > "OLPCRoot" on any > > Linux OS including Sugar and it is /dev/sda1 when > booting the XO > > from the NAND or an SD card. > > I wonder if the USB device is detected as something > else...if you boot > from the NAND and plug in the USB device with the soas71xo > filesystem > on it, what device node (e.g., /dev/sda1) does its > partition show up > as? as mentioned above, as: OLPCRoot > > We really should be using the same > root-device-specification as > livecd-iso-to-disk uses, which would be pretty > unambiguous.? I'll > look into that. > > > It is ext2 formatted and I did erase the stick just > before 'cating' > > the soas71xo file into it. > > Ok, though you don't need to erase the stick first - > "cat'ing" the > file includes a partition table and filesystem superblocks, > so > whatever bits are left on the device aren't going to be > known as files > or anything afterwards. Yeh, but just in case. USB sticks can be very "funny" at times. > > > So certainly will not boot with just the kernel in > this setting. > > Yeah - though precisely one should say that the kernel _is_ > booting, > it's just not finding the root device. > > Martin > From martin at martindengler.com Wed Sep 30 20:55:16 2009 From: martin at martindengler.com (Martin Dengler) Date: Wed, 30 Sep 2009 21:55:16 +0100 Subject: New SoaS [XO-1] build soas70 In-Reply-To: <230973.13434.qm@web65513.mail.ac4.yahoo.com> References: <20090930195908.GN11568@ops-13.xades.com> <230973.13434.qm@web65513.mail.ac4.yahoo.com> Message-ID: <20090930205515.GO11568@ops-13.xades.com> On Wed, Sep 30, 2009 at 01:23:18PM -0700, Yioryos Asprobounitis wrote: > --- On Wed, 9/30/09, Martin Dengler wrote: > > On Wed, Sep 30, 2009 at 12:06:11PM -0700, Yioryos Asprobounitis > > wrote: > > > > The included olpc.fth in the vergin stick _does_ point to > > initrd.img > and the OFW complains that can not open the boot > > devise and stops > there. (more below) > > > > Careful, some people are going to take your words literally :).? > > It clearly doesn't stop there (you had me worried) from what you > > said below. > > With the original olpc.fth it _does_ stop there. Never get to > console. Hmm, odd. I finally just tested a USB stick with that olpc.fth and it booted the kernelfine (failed where you areseeing the failure, but...). Can you remove the "boot" line from the "virgin" olpc.fth and let me know what printenv boot-device printenv boot-file printenv ramdisk ...show? > > > So certainly will not boot with just the kernel in this setting. > > > > Yeah - though precisely one should say that the kernel _is_ > > booting, it's just not finding the root device. Ok, I realised the problem. USB storage is modular in the kernel, SD (SCSI) is not. So the initrd is required for USB-stick root devices and not for SD-based root devices. The reason I had to remove the initrd was due to a problem with dracut and NAND-root-devices, so perhaps I can find a better workaround (like build USB storage into the kernel, or not setting the OFW ramdisk variable when NAND provides the root device) or just teach dracut about root=mtd0 root devices. In the meantime, sorry for not remembering this earlier. I should have a fix soon. Martin -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: