Re: New XO-1.5 10.2.0 build 111
On Sun, Mar 07, 2010 at 11:01:53PM -0500, Paul Fox wrote: actually, i think something like this did make it in. i haven't used it in a long time (since 8., but #6432 seems to imply that rpms in /home/olpc/.custom/rpms will get installed on the first reboot after an olpc-update. Hmm, yes. http://wiki.laptop.org/go/Yum#Making_persistent_changes documents this. /etc/rc.d/init.d/olpc-configure implements. for pkgdir in /home/olpc/.custom/rpms ... -- James Cameron http://quozl.linux.org.au/ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Etoys 4.0.2340
Hi folks, back in January I was asked to make a more space-efficient release of Etoys. I complied, the 4.0.2340 release uses its own compression scheme now instead of relying on the jffs2 compression as before. http://lists.sugarlabs.org/archive/sugar-devel/2010-January/022079.html I just want to make people aware this version has not appeared in a build since, 10.2/111 still uses the previous release. On a slightly related note, I intend to prepare another version with updated translations in time for the upcoming Sugar 0.88 release. - Bert - ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Etoys 4.0.2340
I installed etoys 4.0.2340 (plus Etoys-114.xo) in systems with os111, os11, and 802B2. In all instances, Etoys 4.0.2340 seemed to run fine. mikus ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: New XO-1.5 10.2.0 build 111
I see. No easy way to know what has been installed then, I guess. I'll stick to what Paul suggests. Would it be any use of doing it right for deployments? I could look into it a bit deeper if it would. Perhaps trying to diff the yum database somehow. Best regards On Mon, Mar 8, 2010 at 5:02 AM, James Cameron qu...@laptop.org wrote: On Mon, Mar 08, 2010 at 04:52:28AM +, Tiago Marques wrote: I don't know what olpc-update is doing in the backstage, is it restoring a pre-defined database or diffs? It is rsync'ing a filesystem tree from updates.laptop.org to your laptop, and then configuring next boot to use it. It uses the current operating system build as the initial filesystem before the rsync, so that only the changes are copied across the network. -- James Cameron http://quozl.linux.org.au/ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
q3a34 released
http://wiki.laptop.org/go/OLPC_Firmware_q3a34 - Lots of OFW fixes. (see wiki) - New EC bits that fix a keyboard lockup -- Richard A. Smith rich...@laptop.org One Laptop per Child ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: New XO-1.5 10.2.0 build 111
On Mon, Mar 08, 2010 at 06:24:39PM +, Tiago Marques wrote: No easy way to know what has been installed then, I guess. [...] Perhaps trying to diff the yum database somehow. You might use rpm to list the database in the previous version tree, then use rpm to list the database in the current version tree, sort the outputs, and then compare. For instance on a test system the package abyssinica-fonts was manually removed after olpc-update to os111, yet the previous build rpm database is still available: # rpm -q abyssinica-fonts package abyssinica-fonts is not installed # readlink /versions/running pristine/fe25e45429bcc3714552316f97e0acad # find /versions/run -name Packages /versions/run/fe25e45429bcc3714552316f97e0acad/var/lib/rpm/Packages /versions/run/0ab47a1d38c3ce22e58a488f6850ac41/var/lib/rpm/Packages # rpm --root=/versions/pristine/0ab47a1d38c3ce22e58a488f6850ac41 -q abyssinica-fonts abyssinica-fonts-1.0-4.fc11.noarch So it is possible to generate a package list diff: # rpm --root=/versions/run/0ab47a1d38c3ce22e58a488f6850ac41 -qa | sort /tmp/a # rpm -qa|sort /tmp/b # diff /tmp/a /tmp/b 11,13c11,13 NetworkManager-0.7.2.995-1.git20100202.fc11.i586 NetworkManager-glib-0.7.2.995-1.git20100202.fc11.i586 NetworkManager-gnome-0.7.2.995-1.git20100202.fc11.i586 --- NetworkManager-0.7.2.995-2.git20100225.fc11.i586 NetworkManager-glib-0.7.2.995-2.git20100225.fc11.i586 NetworkManager-gnome-0.7.2.995-2.git20100225.fc11.i586 26d25 abyssinica-fonts-1.0-4.fc11.noarch [...] Based on this you might learn what you have just lost by using olpc-update. -- James Cameron http://quozl.linux.org.au/ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: OLPC hardware: what if there was an SDR modem / chipset?
On Mar 7, 2010, at 10:24 PM, Tiago Marques wrote: Hi Wad, Been reading some lost e-mails, sorry to be bumping this up. On Tue, Jan 26, 2010 at 10:35 PM, John Watlington w...@laptop.org wrote: On Jan 27, 2010, at 12:17 AM, Luke Kenneth Casson Leighton wrote: hi scott, thanks for joining in, here. On Tue, Jan 26, 2010 at 3:01 PM, C. Scott Ananian csc...@laptop.org wrote: Good luck with your SDR dreams. I think the most you can expect from OLPC is that, *if* the 10 improbable things you described actually come to pass, OLPC will someday include a miniPCI slot so that they can plug in your magic daughtercard. miniPCI assumes there's a PCI bus. ARM SoCs don't have PCI (that i know of). the only SoC x86 chip i've heard about is the 1ghz IEC 100HV from RDC. but with ARM it'd have to be a mini PCI-e slot with the USB2 option - pins 36 and 34 - but that's been ruled out because john's removed all internal USB paths. the next gen x86 clone from RDC that they're planning will have full PCI-e. Actually, I got that miniPCI connector into XO-1.5. I won't go into You did? I can't find any reference in the XO 1.5 diagrams. Is it already being used for something? Read the next paragraph I wrote: But as with most networking cards, the miniPCI is just a form factor. Most WiFi/GSM cards on the market electrically use a USB connection. On XO-1.5, we use SDIO, but also provide a spare USB port to the miniPCI (why not ?)The form factor is half-length miniPCI, and the pinout is documented at: http://wiki.laptop.org/images/0/05/ XO_1.5_Pinouts_C2.pdf CN19 in that document is the PCIe pinout. http://wiki.laptop.org/go/Image:XO_1.5_C1_Annotated_Motherboard.png shows the miniPCIe connector, with a WLAN card attached. Cheers, wad ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: q3a34 released
Still has the problem (also seen in earlier q3a3_ versions) that when I power on with my USB hub plugged in, if I hold down the 'check' game button then after the chime sounds (I also get a light_brown/orange stripe across the top of the screen) the OFW boot-up sequence spontaneously restarts from the very beginning. To get the OFW boot-up sequence to offer to pause at the ok prompt (because I'm pressing the 'check' button), I'll boot my XO-1.5 B3 without the USB hub plugged in. mikus ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: surprisingly early suspend
Perhaps the suspend/sleep process should be disabled until the laptop is assigned a child's name and color preference on first boot. I find sleep to be more disorienting, as the screen is turned off (my laptop broke!) and it takes a press of the power button, not the keyboard, to wake the laptop up. What ever happened to making suspend invisible on the XO, and happen between keystrokes? I thought the new hardware was going to fix all the issues that prevented us from enabling that in the old hardware. (Suspend -- turning the CPU off -- should be separate from dimming the screen, and should also be separate from sleeping. If you can suspend and can dim, maybe you should sleep after an hour or something, but with the CPU and RAM off and the backlight off, how much does sleep really save?) John ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: q3a34 released
On Mon, Mar 08, 2010 at 05:15:45PM -0600, Mikus Grinbergs wrote: Still has the problem (also seen in earlier q3a3_ versions) that when I power on with my USB hub plugged in, if I hold down the 'check' game button then after the chime sounds (I also get a light_brown/orange stripe across the top of the screen) the OFW boot-up sequence spontaneously restarts from the very beginning. Does the battery LED go out? (It does for me, and also the power button does not respond to being held down). -- James Cameron http://quozl.linux.org.au/ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: q3a34 released
On Tue, Mar 09, 2010 at 10:55:13AM +1100, James Cameron wrote: Does the battery LED go out? (It does for me, and also the power button does not respond to being held down). This turned out to be a faulty USB powered hub that was feeding power back to the laptop. It is easy to check for; see if power is coming out of the other USB sockets on the laptop when the laptop is supposed to be off. -- James Cameron http://quozl.linux.org.au/ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: surprisingly early suspend
On Mar 8, 2010, at 6:52 PM, John Gilmore wrote: Perhaps the suspend/sleep process should be disabled until the laptop is assigned a child's name and color preference on first boot. I find sleep to be more disorienting, as the screen is turned off (my laptop broke!) and it takes a press of the power button, not the keyboard, to wake the laptop up. What ever happened to making suspend invisible on the XO, and happen between keystrokes? I thought the new hardware was going to fix all the issues that prevented us from enabling that in the old hardware. To a large extent it has. I don't know if anyone has an analysis of where we are with suspend times and where the seconds are going. The sync of the filesystem seems to be a big chunk of our current suspend time. Resume time is good --- when you type a key we wake up and update the screen in a reasonable amount of time (sub-1 second ?). I'm under the impression that our desire to stay with a stock operating system is one of the big remaining limitations, but could be wrong. Perhaps now that we actually think the hardware is relatively stable and functional we can spend some time there. (Suspend -- turning the CPU off -- should be separate from dimming the screen, and should also be separate from sleeping. If you can suspend and can dim, maybe you should sleep after an hour or something, but with the CPU and RAM off and the backlight off, how much does sleep really save?) Sleep saves because it turns the backlight and display completely off, and in suspend those are the dominant current hogs. I think we all agree with you about sleep versus suspend. The remaining issues being debated are: - what should the time before sleep occurs be ? - when should the backlight be dimmed relative to sleep ? (Apple seems to use 50% of the sleep time, which we are now trying). - should the time before suspend be even shorter than the current fifteen seconds ? Cheers, wad ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: q3a34 released
Please trac this, and try to provide a more verbose description. It sounds interesting... wad On Mar 8, 2010, at 6:15 PM, Mikus Grinbergs wrote: Still has the problem (also seen in earlier q3a3_ versions) that when I power on with my USB hub plugged in, if I hold down the 'check' game button then after the chime sounds (I also get a light_brown/orange stripe across the top of the screen) the OFW boot-up sequence spontaneously restarts from the very beginning. To get the OFW boot-up sequence to offer to pause at the ok prompt (because I'm pressing the 'check' button), I'll boot my XO-1.5 B3 without the USB hub plugged in. mikus ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: surprisingly early suspend
John Watlington wrote: I'm under the impression that our desire to stay with a stock operating system is one of the big remaining limitations, but could be wrong. My impression: Linux is capable of the desired behavior in general, via the cpuidle framework, which chooses to transition between sleep states based on the transition latencies, system activity, and upcoming timer events. Cpuidle separates policy from implementation by using pluggable backends in the form of cpuidle drivers that handle state transitions [1]. At present, the only cpuidle driver in the kernel is the ACPI driver (drivers/acpi/processor_idle.c). I do not know whether the XO's CPU deactivation, DCON, and timed wakeup system can be, or has been, mapped into an ACPI state. If ACPI is insufficient to represent the XO's behavior, then a new cpuidle driver will be required. I expect such a driver would be accepted into the upstream kernel. Writing it should not be hugely difficult, but I do not have enough experience to provide a good estimate of the amount of work required. --Ben [1] http://www.mjmwired.net/kernel/Documentation/cpuidle/driver.txt signature.asc Description: OpenPGP digital signature ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: surprisingly early suspend
The remaining issues being debated are: - what should the time before sleep occurs be ? - when should the backlight be dimmed relative to sleep ? (Apple seems to use 50% of the sleep time, which we are now trying). - should the time before suspend be even shorter than the current fifteen seconds ? For myself, whether it is ohm or powerd that is doing the suspending, I 'modify' the respective timing values to get my systems to behave the way I expect them to behave. When I started this thread, I had just flashed a new build - meaning I had not yet gotten around to changing the values built in to the build I agree that there ought to be one set of timing values for running on AC, and a separate set of timing values for running on battery. mikus ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
