ANNOUNCEMENT: XO-AU USB Upgrade 3
Users of XO operating system builds from OLPC Australia can now upgrade to our latest release without losing their files and settings. If you have an OLPC Australia release made this year (10.1.3-au3, 10.1.3-au2, 10.1.3-au2-xo1 or 10.1.3-au1), you are eligible to upgrade. The process will check your installed build and only proceed if it meets that criteria. For details, see the announcement[0]. The Upgrade Stick is a derivation of our XO-AU USB technology[1]. Sridhar [0] http://dev.laptop.org.au/news/20 [1] http://dev.laptop.org.au/projects/xo-au-usb Sridhar Dhanapalan Engineering Manager One Laptop per Child Australia M: +61 425 239 701 E: srid...@laptop.org.au A: G.P.O. Box 731 Sydney, NSW 2001 W: www.laptop.org.au ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Fixing yum on F14-arm build os31
On Wed, Aug 3, 2011 at 10:44 PM, Martin Langhoff mar...@laptop.org wrote: On Thu, Jul 28, 2011 at 4:03 PM, Martin Langhoff mar...@laptop.org wrote: The Switch to Fedora-14 build. Download from: http://build.laptop.org/F14-arm/os31/ The default yum config - which we include - points to the official Fedora mirrors, and those don't really support unsupported architectures like ARM. Surprise! Actually there is a means of this being supported when F-14 gets replicated to the secondary mirrors. I'm working to get this to happen but there's a few holdups. Of course it's in my list of things to fix. In the meantime, here's what you can do - edit /etc/yum.repos.d/fedora-update.repo -- look at the first section, disable it (enabled=0) - edit /etc/yum.repos.d/fedora.repo -- look at the first section, disable gpg checks (gpgcheck=0), comment out the mirrorlist line, and add baseurl= http://arm.koji.fedoraproject.org/repos/dist-f14-build/latest/arm/ You're done! Note that it is a partial repo, and it only has the packages at the F14 release time versions. Additionally, some packages are missing or tagged wrong. If you want a package that is missing, ping Peter to see if it'll be available soon. Poke me on IRC/gtalk and its likely I can push it through, a few like csound are being fun but we're getting there. If you see a package or dependency bail out complaining about python(abi)=2.6, let Peter know. The repo is just showing the wrong package (and the right one is likely there). Poke me on IRC/gtalk. This one is a side effect of the mass rebuild script due to the bump to python. Hopefully we'll past this one soon. Peter ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Kernel git reorganisation
On Thu, Aug 4, 2011 at 3:08 AM, Paul Fox p...@laptop.org wrote: when you say delete the branch, does this imply no longer being able to look at the history leading to the X or Y tag? No, git log archive/olpc-2.6.30 will still show full history, and git checkout -b olpc-2.6.30 archive/olpc-2.6.30 will locally recreate the branch as before. The only real difference is that you can't commit to branches that have been archived in this manner, unless you recreate the tag pointing at a new tip. Daniel ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Kernel git reorganisation
daniel wrote: On Thu, Aug 4, 2011 at 3:08 AM, Paul Fox p...@laptop.org wrote: when you say delete the branch, does this imply no longer being able to look at the history leading to the X or Y tag? No, git log archive/olpc-2.6.30 will still show full history, and git checkout -b olpc-2.6.30 archive/olpc-2.6.30 will locally recreate the branch as before. The only real difference is that you can't commit to branches that have been archived in this manner, unless you recreate the tag pointing at a new tip. thanks. i figured/was hoping it was something like this. go for it. paul =- paul fox, p...@laptop.org ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
f14-dist-build: some packages mistagged?
I just ran a build and it seems to have picked up some older packages... perhaps an indication that the package is mistagged? -dracut-006-3.fc14.noarch -dracut-modules-olpc-0.5.3-1.fc14.1.armv5tel +dracut-006-2.fc14.noarch +dracut-modules-olpc-0.5.3-1.fc14.armv5tel -olpc-update-2.23-1.fc14.noarch +olpc-update-2.22-1.fc14.noarch cheers, m -- martin.langh...@gmail.com mar...@laptop.org -- Software Architect - OLPC - ask interesting questions - don't get distracted with shiny stuff - working code first - http://wiki.laptop.org/go/User:Martinlanghoff ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Kernel git reorganisation
Hi, On Thu, Aug 04 2011, Daniel Drake wrote: We've recently talked about reorganising our kernel git repo, and avoiding having multiple repos like we have ended up with now. I propose the following (and I volunteer to do it): This has now been done. I've pushed olpc-3.0:arm-3.0 to olpc-kernel:arm-3.0 now, so Martin can start using olpc-kernel:arm-3.0 as the branch to include in ARM builds. Thanks, - Chris. -- Chris Ball c...@laptop.org http://printf.net/ One Laptop Per Child ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: powerd-dbus network extension
hi daniel -- daniel wrote: Hi Paul, For 11.3.0 I'd like to implement a solution for the issue where powerd idle-suspends while wifi connections are being established, causing connection failures and other undesirable activity. The solution I'm thinking of isn't ideal in that it adds a mini-daemon alongside powerd. But hey, you just got rid of HAL, we have breathing space ;) and I can't think of a better way. Here is what I've thought up: Instead of being on-demand and short lived, powerd-dbus will be launched by powerd and will become a full-time daemon. In addition to the functionality that it already has, it will connect to the dbus system bus and monitor NetworkManager's StateChanged signals. The NM states are: DEVICE_STATE_UNKNOWN = 0 DEVICE_STATE_UNMANAGED = 1 DEVICE_STATE_UNAVAILABLE = 2 DEVICE_STATE_DISCONNECTED = 3 DEVICE_STATE_PREPARE = 4 DEVICE_STATE_CONFIG = 5 DEVICE_STATE_NEED_AUTH = 6 DEVICE_STATE_IP_CONFIG = 7 DEVICE_STATE_ACTIVATED = 8 DEVICE_STATE_FAILED = 9 Lets assign a variable: nm_suspend_ok = state = 3 state = 8 since that can't be true, i assume you meant: nm_suspend_ok = state = 3 || state = 8 (i.e. suspend is only OK if we aren't establishing a connection) It will also monitor the wpa_supplicant signals for the same device, watching for the Scanning signal. wpas_suspend_ok = !Scanning Finally: suspend_ok = wpas_suspend_ok nm_suspend_ok you're far more familiar with the details of how NM and wpa_supplicant operate, so i'm sure your proposed conditions are likely correct. When the suspend_ok flag changes, it would be communicated to powerd through the powerevents socket, as network_suspend_ok or network_suspend_not_ok. There would be a 2 second settle period after a not-OK to OK transition before sending the powerd event (and the event would be aborted if the situation changes within those 2 seconds). This captures the case where NM says the device is disconnected, and wpa_supplicant has finished a scan (suspend_ok == TRUE), but NM will initiate a connection immediately after (once it has processed the scan results). When powerd has been told network_suspend_not_ok, it would not suspend until told otherwise. (I'll probably ask you to implement this bit, I guess you could do it rather quickly?) sure. as john suggested in another message, this is yet another application-specific protocol being implemented in powerd, as a heuristic to keep the user happy. while i have no problem adding it (what's one more? :-), we should certainly be tracking the ongoing kernel work which might support all our suspend inhibitors in a more cohesive way. The above is the main functionality I want to implement. But, to kill 2 birds in 1 stone, having this full-time daemon around lets me solve another issue: rfkill. You probably recall that sugar-0.84 executed rfkill block olpc when the disable wifi checkbox was ticked. Unfortunately this was never it used to be rfkill block wifi, but perhaps that's changed. upstreamed (boo), so 11.2.0 doesn't have that functionality. In 11.2.0, the NM WirelessEnabled property is manipulated, and the interface is brought down, but we don't actually cut power. We do have the option of reimplementing it in Sugar, but (for now) I think powerd would be a nicer place to do this. (Ultimately, we want NM to do it). So, in addition to the above, powerd-dbus would monitor for NetworkManager's PropertiesChanged signal, and apply this simple logic. if WirelessEnabled == true: rfkill unblock olpc else: rfkill block olpc again, you're closer to the wireless bits than i am. i guess we know that NM won't be confused by having the card logically disappear when it brings the interface down? if so, then it sounds like a reasonable plan. (though it feels like a bit of a hack for it to be in powerd-dbus.) paul How does this sound to you? Thanks, Daniel =- paul fox, p...@laptop.org ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: powerd-dbus network extension
On Thu, Aug 4, 2011 at 9:20 PM, Paul Fox p...@laptop.org wrote: as john suggested in another message, this is yet another application-specific protocol being implemented in powerd, as a heuristic to keep the user happy. while i have no problem adding it (what's one more? :-), we should certainly be tracking the ongoing kernel work which might support all our suspend inhibitors in a more cohesive way. Agreed. And we're taking a 2-pronged approach to this, with the short-term fix as described in this thread, and our upstreaming work which is a stepping stone towards the long-term fix. I'll start work on the implementation, thanks for your comments! Daniel ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
11.3.0 development build 2 released
http://wiki.laptop.org/go/11.3.0 http://build.laptop.org/11.3.0/os2 Notable changes since build 1: - New XO-1.5 wireless firmware - XO-1 OpenFirmware update wasn't included in build 1 as planned, but is now included - linux-firmware removed - HAL removed, new kbdshim uses udev - pygtk glade module is back - Minor Fedora updates - Finance updated to v5 - Help updated to v13 - Jukebox updated to v22 - Log updated to v25 - Stopwatch updated to v11 - TurtleArt updated to v113 Tickets closed: #10780 Sugar Network view looses track of available networks but iwlist is fine #10864 Finance activity has old toolbar #10865 Help activity has old toolbar #10867 Jukebox activity has old toolbar #11053 import gtk.glade fails #11063 New XO-1.5 wifi firmware v9.70.20.p0 #11088 kbdshim-18 breaks boot ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: glade.so missing from /usr/lib/python2.7/site-packages/gtk-2,0/gtk
On Sat, Jul 16, 2011 at 06:05:19AM -0400, George Hunt wrote: I read the resolution of #11053 The resolution has changed. Glade will have been missing only from 11.2.0. -- James Cameron http://quozl.linux.org.au/ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
