Re: Signed candidate-765 and gg-765-2 builds available for testing.
Michael Stone wrote: I have decided to publish 8.2-765 as a signed Candidate http://download.laptop.org/xo-1/os/candidate/765/ (raw os) I reverted my signed (no-developer key) XO-1 back to build 650 (ship.1, 7.1.0) and did a ``olpc-update --usb`` to update to candidate-765. I had the expected issues of no sudo and having to update olpc-update itself, and it worked! This wasn't a perfect test because I didn't revert firmware as well, I was on latest q2e18 firmware throughout. I improved and simplified the early sections of http://wiki.laptop.org/go/olpc-update for the USB upgrade path. I noticed one slightly confusing thing. The line of text in a virtual terminal and in `cat /etc/issue` is: OLPC build 765 (stream 8.2; variant devel_jffs2) ^^^? ^? I guess this candidate stream isn't a real stream, it's just a special treatment of certain builds. But why is the variant called devel ? According to http://wiki.laptop.org/go/OS_images#Image_variants , devel Contains tools useful for developers of the OLPC operating system, including: yum, rpm, vim-minimal, openssh-server, xterm, which, file, tree, wget, xorg-x11-twm, gdb packages My OS only has some of those. I think these days there isn't a Normal image any more, just devel_? Will this variant devel_ go away when 8.2.0 moves to http://download.laptop.org/xo-1/os/official/ ? I see a newer http://download.laptop.org/xo-1/os/candidate/766/ ; Friends_in_testing still suggests candidate-765. http://download.laptop.org/xo-1/custom/g1g1/gg-765-2/ (G1G1 composite) I see a newer gg-766-3. But nobody has explained when or how you'd upgrade to a gg- build (is it for a clean-install with activities?), so I think it goes unmentioned on the wiki. Regards, -- =S Page user:skierpage ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Signed candidate-765 and gg-765-2 builds available for testing.
So you are going to put those on a USB flash drive and run sudo olpc-update -usb from build 711 (release 8.1.2)? Yes! - the update process complete successfully. - at reboot the firmware got updated - at the start of the sugar session been asked to check for update activities (I had to say no because I'm not connected to network) - at first glance the system seems ok (username color scheme preserved) - my locale (it) get preserved - I open control panel (the widget layout is weird ): - Information of my XO widget says: Build 765 Sugar 8.2.1 Firmware Q2E18 - Browse starts - Journal get preserved more on it later... ._) please let me know if you need some specific test ! ciao e grazie Carlo Falciola - Messaggio originale - Da: S Page [EMAIL PROTECTED] A: Carlo Falciola [EMAIL PROTECTED] Inviato: Martedì 30 settembre 2008, 11:28:15 Oggetto: Re: Signed candidate-765 and gg-765-2 builds available for testing. Carlo Falciola wrote: I just need to re-download and I'll let you know asap (did you already update the link in the wiki-home box, did you?) Yes, I updated the wiki. sudo olpc-update candidate-765 from 8.2-763 worked fine for me. I'm getting os765.usb .toc from http://download.laptop.org/xo-1/os/candidate/765/jffs2/ . So you are going to put those on a USB flash drive and run sudo olpc-update -usb from build 711 (release 8.1.2)? Please let me know if you have any suggestions or problems with the steps in http://wiki.laptop.org/go/Olpc-update Thanks, -- =S Page (just someone trying to improve the wiki) Scopri il blog di Yahoo! Mail: Trucchi, novità e la tua opinione. http://www.ymailblogit.com/blog ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [sugar] Signed candidate-765 and gg-765-2 builds available for testing.
Important: has anyone successfully upgraded/installed to the signed candidate-765? 1. I retried `sudo olpc-update candidate-765` from 8.2-763 on a secure (developer.sig moved away) XO. This time it worked fine. 2. I followed http://wiki.laptop.org/go/Clean-install_procedure to go back to build 650 (for that Christmas 2007 ship.1 feel :-) ) on a secure XO. su -l olpc-update candidate-765 succeeded, after errors in irsync_pristine and irsync dirty but apparently no out-of-memory problems. This wasn't a perfect test because I didn't revert firmware as well, I was on latest q2e18 firmware throughout. After reboot Software update's Checking for updates hung in Loading groups... , just as Walter Bender reported to testing list. I think this is bug 8681, fixed in build 766. shell.log had two WARNING root: Activity directory lacks a MANIFEST file. then exception from actinfo.py, line 138, in get_activity_group_urls with open( USER_GROUPS_FILE, 'w') that No such file or directory: '/home/olpc/Activities/.groups' 3. Carlo Falciola updated from 711 (8.1.2) to candidate-765 using olpc-update -usb, see separate e-mail. I changed the wiki Sunday night and I think all the links and banners mentioning candidate-765 work. Nobody replied to my question about the gg-765-2 image below. Michael Stone wrote: I have also published gg-765-2, a signed G1G1 candidate composite image, created by Scott. gg-765-2 is similar to what we hope to put into manufacturing next week. ... http://download.laptop.org/xo-1/custom/g1g1/gg-765-2/ (G1G1 composite) Where should this be mentioned? Should someone doing http://wiki.laptop.org/go/Clean-install_procedure copy this image? -- =S Page user:skierpage ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [sugar] Signed candidate-765 and gg-765-2 builds available for testing.
On Tue, Sep 30, 2008 at 8:23 AM, S Page [EMAIL PROTECTED] wrote: After reboot Software update's Checking for updates hung in Loading groups... , just as Walter Bender reported to testing list. I think this is bug 8681, fixed in build 766. shell.log had two WARNING root: Activity directory lacks a MANIFEST file. then exception from actinfo.py, line 138, in get_activity_group_urls with open( USER_GROUPS_FILE, 'w') that No such file or directory: '/home/olpc/Activities/.groups' Yes, this is fixed in 766 (although testing confirmation welcome). I have also published gg-765-2, a signed G1G1 candidate composite image, created by Scott. gg-765-2 is similar to what we hope to put into manufacturing next week. ... http://download.laptop.org/xo-1/custom/g1g1/gg-765-2/ (G1G1 composite) Where should this be mentioned? Should someone doing http://wiki.laptop.org/go/Clean-install_procedure copy this image? We have not yet released 765. In fact, we just made 766. So let's not jump the gun. We'll update all the pages when we actually release 766. (Basically, we'll meet on Friday, and if we haven't found any blocking bugs in 766 by that time, we'll declare that to be 8.2 and partying will ensure. If we find severe bugs, we'll fix them, make a new build, and reset the testing clock.) --scott -- ( http://cscott.net/ ) ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Signed candidate-765 and gg-765-2 builds available for testing.
I did not worked for me: I've a G1G1 without developer key, already updated to 711. I just tried to olpc-update via USB picking up the 765 from the link available from wiki. After a long run, the olpc-update command terminated with a message like: update aborted: need a development key... I've to admit I'm a bit confused by abundance of docs/versions :-) ciao carlo Scopri il blog di Yahoo! Mail: Trucchi, novità e la sua opinione. http://www.ymailblogit.com/blog ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Signed candidate-765 and gg-765-2 builds available for testing.
Carlo Falciola wrote: I did not worked for me: I've a G1G1 without developer key, already updated to 711. I just tried to olpc-update via USB picking up the 765 from the link available from wiki. You didn't tell us the exact command you typed, but the link on the wiki has been 8.2-765, which isn't signed, hence the error message you got. Please retry with sudo olpc-update candidate-765 and let everyone know. Thanks indeed, you may be the first without a developer key to try it! -- =S Page user:skierpage ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [sugar] Signed candidate-765 and gg-765-2 builds available for testing.
Important: has anyone successfully upgraded/installed to the signed candidate-765? If so, someone can edit http://wiki.laptop.org/go/Friends_in_testing/current_image_stream changing it from 8.2 to candidate and links and banners should work. C. Scott Ananian wrote: On Sat, Sep 27, 2008 at 3:47 AM, S Page [EMAIL PROTECTED] wrote: So I think you could or should change http://wiki.laptop.org/go/Template:Latest_Releases/rc to candidate-765, and update Friend_in_testing to replace 1. Get a developer key for your XO laptop. with Anyone with a mass production XO can upgrade to this candidate release (you don't need a developer key). This sounds good to me. I don't think you need to wait for Michael to make this change, could you go ahead and update the wiki? I made http://wiki.laptop.org/go/Template:candidate-jffs2-link , pointing to http://pilgrim.laptop.org/~pilgrim/xo-1/streams/candidate/build765/devel_jffs2/ There might be other templates and fragments needed. BUT! after I disabled my developer key and ran sudo olpc-update candidate-765 , my XO won't boot: Trying nand:\boot\runos.zip OS found - No signature for our key Boot failed :-( I've been asking on irc:#olpc if anyone has upgraded/installed candidate-765 on a secure or developer-key XO, with no response. So I haven't permanently changed http://wiki.laptop.org/go/Friends_in_testing/current_image_stream from 8.2 to candidate , but I believe the wiki is set up for the change. Michael Stone wrote: I have also published gg-765-2, a signed G1G1 candidate composite image, created by Scott. gg-765-2 is similar to what we hope to put into manufacturing next week. ... http://download.laptop.org/xo-1/custom/g1g1/gg-765-2/ (G1G1 composite) Where should this be mentioned? Should someone doing http://wiki.laptop.org/go/Clean-install_procedure copy this image? -- =S Page user:skierpage ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Testing] [sugar] Signed candidate-765 and gg-765-2 builds available for testing.
OK, I can't really test the candidate-765 here. My B4 starts to secure boot (hold the X gamepad down), shows an SD card, then flashes what looks like a USB key in red a few times, then a wireless symbol, before telling me activation lease not found - no se encontrò elpermiso de activiòn - permis d'activation introuvable. Shutting down faster than I can type the text into this email :-) This is very probably as expected, as I'm a developer and have never activated an XO lease in any way, shape, or form. Is there a way I can get a lease so I can test this side of things (just curious)? I guess I'd need a local school server set-up. Booting in insecure mode was no problem, seemed to work just like what I had running before in 765 with the .toc and .usb images from pilgrim. --Gary On 28 Sep 2008, at 23:59, Gary C Martin wrote: Off list, I'm just sudo olpc-update candidate-765 on my B4 now. I'll reboot with security** temporally off and let you know how it goes. **I don't have a dev key, funnily enough, I was shipped a B4 with the Firmware set to disable security and have always just rolled with that set-up, so no dev key to hide. On 28 Sep 2008, at 23:45, S Page wrote: Important: has anyone successfully upgraded/installed to the signed candidate-765? If so, someone can edit http://wiki.laptop.org/go/Friends_in_testing/current_image_stream changing it from 8.2 to candidate and links and banners should work. C. Scott Ananian wrote: On Sat, Sep 27, 2008 at 3:47 AM, S Page [EMAIL PROTECTED] wrote: So I think you could or should change http://wiki.laptop.org/go/Template:Latest_Releases/rc to candidate-765, and update Friend_in_testing to replace 1. Get a developer key for your XO laptop. with Anyone with a mass production XO can upgrade to this candidate release (you don't need a developer key). This sounds good to me. I don't think you need to wait for Michael to make this change, could you go ahead and update the wiki? I made http://wiki.laptop.org/go/Template:candidate-jffs2-link , pointing to http://pilgrim.laptop.org/~pilgrim/xo-1/streams/candidate/build765/devel_jffs2/ There might be other templates and fragments needed. BUT! after I disabled my developer key and ran sudo olpc-update candidate-765 , my XO won't boot: Trying nand:\boot\runos.zip OS found - No signature for our key Boot failed :-( I've been asking on irc:#olpc if anyone has upgraded/installed candidate-765 on a secure or developer-key XO, with no response. So I haven't permanently changed http://wiki.laptop.org/go/Friends_in_testing/current_image_stream from 8.2 to candidate , but I believe the wiki is set up for the change. Michael Stone wrote: I have also published gg-765-2, a signed G1G1 candidate composite image, created by Scott. gg-765-2 is similar to what we hope to put into manufacturing next week. ... http://download.laptop.org/xo-1/custom/g1g1/gg-765-2/ (G1G1 composite) Where should this be mentioned? Should someone doing http://wiki.laptop.org/go/Clean-install_procedure copy this image? -- =S Page user:skierpage ___ Testing mailing list [EMAIL PROTECTED] http://lists.laptop.org/listinfo/testing ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [sugar] Signed candidate-765 and gg-765-2 builds available for testing.
On Sun, Sep 28, 2008 at 6:45 PM, S Page [EMAIL PROTECTED] wrote: BUT! after I disabled my developer key and ran sudo olpc-update candidate-765 , my XO won't boot: Trying nand:\boot\runos.zip OS found - No signature for our key Boot failed :-( Hmm, two bugs potentially here: olpc-update shouldn't let you upgrade to an unsigned build (if that's what candidate-765 is giving you) without an active developer key (unless you use the --force option, at least). I'll check this out on Monday. I've been asking on irc:#olpc if anyone has upgraded/installed candidate-765 on a secure or developer-key XO, with no response. I've installed it on a secured XO with a dev key (that's my usual machine); I'll have to try turning security off. --scott -- ( http://cscott.net/ ) ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [sugar] Signed candidate-765 and gg-765-2 builds available for testing.
On Mon, Sep 29, 2008 at 12:04 AM, C. Scott Ananian [EMAIL PROTECTED] wrote: I've installed it on a secured XO with a dev key (that's my usual machine); I'll have to try turning security off. I mean, turning the *dev key* off. --scott -- ( http://cscott.net/ ) ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Signed candidate-765 and gg-765-2 builds available for testing.
Michael Stone wrote: I have decided to publish 8.2-765 as a signed Candidate So IIUC you should be promoting candidate-765? I re-enabled security on my XO running 8.2-763 by renaming /security/developer.sig to developer.sig.MOVED Then sudo olpc-update 8.2-765 led to WARNING: You seem to be attempting to download an unsigned development build, but you don't have a developer key. This will probably fail. /usr/sbin/olpc-update prints this warning if there's a - in the build name and the build name doesn't start with candidate. I killed and retried and sudo olpc-update candidate-765 is updating without complaint on my un-security-disabled XO. So I think you could or should change http://wiki.laptop.org/go/Template:Latest_Releases/rc to candidate-765, and update Friend_in_testing to replace 1. Get a developer key for your XO laptop. with Anyone with a mass production XO can upgrade to this candidate release (you don't need a developer key). I have also published gg-765-2, a signed G1G1 candidate composite image, created by Scott. gg-765-2 is similar to what we hope to put into manufacturing next week. This doesn't work using olpc-update, right? sudo olpc-update gg-765-2 gave @ERROR: unknown module 'build-gg-765-2': bad build identifier: gg-765-2. -- =S Page ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Memory pressure (Re: Signed candidate-765 and gg-765-2 builds available for testing.)
Since everyone major concern is memory pressure especially with Browse, I did some comparison tests with Update.1. The results are somewhat surprising: os711 + g1g1 activity pack Startup: free 127 mb Min Browse: free 91 mb Max Browse: free 61 mb gg-765-2 Startup: free 129 mb Min Browse: free 91 mb Max Browse: free 63 mb Notes: * I have not repeated the tests yet (I intend to do so), so there is the possibility of measurement errors. From my experience so far I'd say +/- 5 mb. * Free memory is measured with free, after having dropped the caches with echo 3 /proc/sys/vm/drop_caches * Min Browse is free memory just after having started browse, no navigation. * Max Browse is the maximum amount of memory I could get Browse to use while navigating randomly inside wikipedia (starting from Moon). Browse memory usage normally grows up quickly when you load the first few pages and then it stabilizes and does not grow anymore. * I tested on clean copy-nand installations of both images, without any reboot. Marco ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [sugar] Memory pressure (Re: Signed candidate-765 and gg-765-2 builds available for testing.)
Don't forget cpu pressure, I've had freezes which need a forcefull shutdown because of it. One example is installing Scratch from the wiki. When it reaches the point of unzipping, it makes the system slow. If you happen to have some activity also doing something intensive (like a Browse instance rendering a complicated webpage) the UI freezes. Sometimes waiting works, other times it doesn't. Eduardo 2008/9/27 Marco Pesenti Gritti [EMAIL PROTECTED]: Since everyone major concern is memory pressure especially with Browse, I did some comparison tests with Update.1. The results are somewhat surprising: os711 + g1g1 activity pack Startup: free 127 mb Min Browse: free 91 mb Max Browse: free 61 mb gg-765-2 Startup: free 129 mb Min Browse: free 91 mb Max Browse: free 63 mb Notes: * I have not repeated the tests yet (I intend to do so), so there is the possibility of measurement errors. From my experience so far I'd say +/- 5 mb. * Free memory is measured with free, after having dropped the caches with echo 3 /proc/sys/vm/drop_caches * Min Browse is free memory just after having started browse, no navigation. * Max Browse is the maximum amount of memory I could get Browse to use while navigating randomly inside wikipedia (starting from Moon). Browse memory usage normally grows up quickly when you load the first few pages and then it stabilizes and does not grow anymore. * I tested on clean copy-nand installations of both images, without any reboot. Marco ___ Sugar mailing list [EMAIL PROTECTED] http://lists.laptop.org/listinfo/sugar ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Signed candidate-765 and gg-765-2 builds available for testing.
After checking with Joe this evening and having previously discussed the necessary security signoffs with Mitch, Richard, Scott, Andres, and Deepak, I have decided to publish 8.2-765 as a signed Candidate in the interests of spurring easier and more widespread testing over the weekend. I have also published gg-765-2, a signed G1G1 candidate composite image, created by Scott. gg-765-2 is similar to what we hope to put into manufacturing next week. http://download.laptop.org/xo-1/os/candidate/765/ (raw os) http://download.laptop.org/xo-1/custom/g1g1/gg-765-2/ (G1G1 composite) olpc-update candidate-765 (olpc-update) http://wiki.laptop.org/go/Friends_in_testing (the usual) http://wiki.laptop.org/go/Customization_stick (make your own) http://wiki.laptop.org/go/Image_builder (next steps) http://wiki.laptop.org/go/Software_update (activity groups) Enjoy, Michael P.S. - You should expect an 8.2-766 with minor changes either over the weekend or on Monday; however, it will be substantially the same as 765, so please get started on 765 now. ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
