Re: My xo-1 isn't multicolor
Here is the list of sku numbers manufactured. http://wiki.laptop.org/go/Manufacturing_data SKU stands for Stock Keeping Unit https://en.wikipedia.org/wiki/Stock_keeping_unit It is a common term used when identifying inventory and unique manufacturing batches. cjl On Tue, Mar 28, 2017 at 6:49 PM, Jhon Diazwrote: > The x on the faceplate is orange and so is the o is this normal? its says > sku1 > > ___ > 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: My xo-1 isn't multicolor
On Tue, Mar 28, 2017 at 6:49 PM, Jhon Diazwrote: > The x on the faceplate is orange and so is the o is this normal? its says > sku1 It is not abnormal. I think that this is the collection of possible x and o plastic colors. http://wiki.laptop.org/images/5/59/Xo_colors.pdf You just happened to get an x and an o of the same color. Find a friend and swap colors! http://wiki.laptop.org/go/Swapping_XO_Man_Colors cjl ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
My xo-1 isn't multicolor
The x on the faceplate is orange and so is the o is this normal? its says sku1 ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [XSCE] 2007 -> 2017 browser experience on XO-1, XO-1.5, XO-1.75 and XO-4
On Tue, Dec 27, 2016 at 11:28 AM, Adam Holt <h...@laptop.org> wrote: > On Tue, Dec 27, 2016 at 11:18 AM, Tony Anderson <tony_ander...@usa.net> > wrote: > >> measure the parameters of the video stream produced by the XO-1 after >> conversion to ogg. Any XO should be able to sustain that level. >> >> One current browser practice is to stream media where the browser is >> capable. This is not suitable for an XO. The media should be downloaded and >> played locally. One of the customizations is to patch the Browse activity >> to automatically download mp3 (unless a short Talk English clip), mp4, pdf, >> epub, and txt files. >> In the case of the book formats, a user is not going to be able to read >> it while online. This patch is simple and effective. >> > > Great suggestions, thanks Tony. I'll add these to > http://wiki.laptop.org/go/Browser_improvements along with your general > recommendation to avoid HD video (and broadband glitz in general...) > Many thanks to Tony Anderson for the following code that provides a way for kids (who need to read/review materials after walking away school servers) to store such large downloaded media & ebooks on their XO's, by default: from: Tony Anderson <tony_ander...@usa.net> date: Wed, Dec 28, 2016 at 10:48 AM One of the features of the Sugar Browse activity is the use of webkit. This provides an easy way to incorporate the browser in Sugar python activities such as markdown. The control of downloads in Browse is in browser.py where I modified this procedure: def __mime_type_policy_cb(self, webview, frame, request, mimetype, policy_decision): """Handle downloads and PDF files.""" print 'mimetype is', mimetype print 'uri is', request.get_uri() if mimetype == 'application/pdf': #uri = request.get_uri() #print 'uri', uri #self.emit('open-pdf', request.get_uri()) #policy_decision.ignore() policy_decision.download() return True elif mimetype in ['audio/mpeg','video/webm','au dio/x-m4a','video/mp4','audio/mp4']: print 'audio', request.get_uri() if 'ShortAudio' in request.get_uri(): #cmd = '/home/olpc/Documents/gsttest/playmp3 '+request.get_uri() cmd = "gst-launch-0.10 playbin2 uri="+request.get_uri() print 'cmd', cmd call(cmd,shell=True) policy_decision.ignore() return True policy_decision.download() return True elif mimetype == 'text/plain': if 'rachel' in request.get_uri(): policy_decision.download() return True elif mimetype == 'application/epub+zip': print 'download epub', request.get_uri() policy_decision.download() return True elif not self.can_show_mime_type(mimetype): policy_decision.download() return True return False Note: the test for 'ShortAudio' refers to TalkEnglish which puts its short mp3s in this folder. These can be streamed. The following code in downloadmanager.py launches Jukebox for the downloaded file with these mime_types (appears after test for Sugar activity). if sniffed_mime_type in ['audio/mpeg','video/webm','au dio/x-m4a','video/mp4','audio/mp4']: cmd = 'sugar-launch -o ' + str(self.dl_jobject) + 'Jukebox.activity' call(cmd, shell=True) These changes were made in Browse-147 but should be the same for the current version (157.3). > On 12/27/2016 03:52 PM, Adam Holt wrote: > > Thanks Terry Gillett for accentuating this central point that I'd failed > to highlight -- now added to http://wiki.laptop.org/go/Brow > ser_improvements : > > "*Perhaps Most Important: can we communicate concisely/explicitly best > browser & video "what works" guidelines, so that hard-working free content > aggregators/publishers (many of whom volunteers) understand their tight > packaging requirements across old Androids, old XO's, etc? Hence greatly > enhancing the XO's practical purposes during its remaining years~"* > > On Sat, Dec 24, 2016 at 10:47 AM, Adam Holt <h...@laptop.org> wrote: > >> Thanks Tony for your voluminous and very thoughtful experiences below! >> >> I'm pretty swamped with holiday prep over the coming 48 hours, but is >> there a good time I can call you in the coming 7-10 days? >> >> I don't want to miss (or misrepresent) anybody's hard-fought "fieldback" >> / usability testing lessons, recommendations & opinions @ >> http://wiki.laptop.org/go/Browser_improvements >> >
Re: Removing Adobe Flash on XO-1, XO-1.75 and XO-4 laptops (CVE-2015-7645)
An update from Adobe; https://blogs.adobe.com/flashplayer/2016/08/beta-news-flash-player-npapi-for-linux.html#sthash.zmBvj3cS.R31QTmNV.dpbs thanks to http://www.theregister.co.uk/2016/09/06/adobe_reverses_decision_to_kill_npapi_flash_plugin_for_linux/ This will likely work on XO-1.5. On XO-1, XO-1.75 and XO-4 the situation below is unchanged. On Mon, Oct 19, 2015 at 01:36:32PM +1100, James Cameron wrote: > G'day, > > To keep learners safe, please remove the Adobe Flash plugin on XO-1, > XO-1.75 or XO-4 laptops: > > sudo rm /usr/lib/mozilla/plugins/libflashplayer.so > > Adobe Security Bulletin APSA15-05 [1] is for a critical remote control > vulnerability (CVE-2015-7645). An attacker can take control of the > laptop. > > For XO-4 and XO-1.75, there will be no fix. Adobe do not provide a > player for Linux 32-bit ARM platform [2]. > > For XO-1, there will be no fix. Adobe do not provide a player > compatible with the AMD Geode processor on the XO-1, which doesn't > have SSE (XMM) registers [3]. > > For XO-1.5, a fix may be available from Adobe. Use the steps > on our Wiki [4]. > > -- > > References: > > 1. > https://helpx.adobe.com/security/products/flash-player/apsa15-05.html > > 2. > https://get.adobe.com/flashplayer/otherversions/ > > 3. > http://lists.laptop.org/pipermail/devel/2012-October/036209.html > > 4. > http://wiki.laptop.org/go/Adobe_Flash#Installation_on_XO-1.5 > > -- > James Cameron > http://quozl.linux.org.au/ -- James Cameron http://quozl.netrek.org/ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: replacement RTC batteries for XO-1 and XO-1.5; which are recommended?
Larger deployments should talk to OLPC for large quantities of this spare part. Smaller deployments won't be able to afford the MOQ. -- There is only one recommended battery model number; ML1220, also written as ML-1220: https://octopart.com/search?q=ml1220 (first two pages of search results) Plenty available from multiple vendors, with reasonably low MOQ, just make sure you get the right packaging, or be prepared to replace the holder as well. On an XO-1, to trade-off part cost for labour, get the cheaper battery with PCB tabs, solder wires to the tabs, cover in heat shrink, remove the holder from the main board, solder the wires to the board, and anchor them with an adhesive so that they don't pull off the traces. Alternatively, it might be possible to solder to the battery holder contacts. Use an adhesive to hold the battery down so that it doesn't bounce around; because by bouncing around it will break the wires eventually. -- To trade-off longevity of repair for labour, add a series shottky diode and a larger format battery (e.g. ANSI 5029LC) that won't be recharged by the main board because of the diode. It will need regular replacement. On Tue, Mar 29, 2016 at 03:55:47PM -0400, Adam Holt wrote: > Does anyone have recommended RTC battery model number(s) handy for XO-1 and > XO-1.5? In context with these very useful RTC (Real-Time-Clock on > motherboard) > rescue/maintenance tips here: > > [1]http://wiki.laptop.org/go/Fix_Clock/Background > > Evidently some schools prefer a clean start, replacing all their RTC batteries > now that XO-1 laptops especially are approaching a decade of life. Depending > what RTC prices and Minimum Order Quantities are forthcoming in 2016+ of > course > -- both for smaller & larger operations -- perhaps Nathan has an idea? > > (Less urgent, but recommended RTC battery model numbers for XO-1.75 and XO-4 > would be wonderful too, if handy?) > > Aside: [2]http://wiki.laptop.org/go/Reuse_checklist is an excellent more > comprehensive list of refurbishing tactics for those interested! > > References: > > [1] http://wiki.laptop.org/go/Fix_Clock/Background > [2] http://wiki.laptop.org/go/Reuse_checklist > ___ > Devel mailing list > Devel@lists.laptop.org > http://lists.laptop.org/listinfo/devel -- James Cameron http://quozl.netrek.org/ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Power] replacement RTC batteries for XO-1 and XO-1.5; which are recommended?
On Tue, Mar 29, 2016 at 5:08 PM, Adam Holt <h...@laptop.org> wrote: > On Tue, Mar 29, 2016 at 4:54 PM, Paul Fox <p...@laptop.org> wrote: > >> it's an ML1220. >> >> http://wiki.laptop.org/go/Fix_Clock#Check_the_battery_and_holder > > > Thanks!! > > I'll try to see if Nathan Riddle has expertise obtaining many hundred -- > for XO-1 especially at this point -- but later the pony-tailed versions > might in future need to procured for XO-1.5+ > > (We'll take note to *avoid* the "CR1220" as mentioned on the page above!) > -- Unsung Heroes of OLPC, interviewed live @ http://unleashkids.org ! ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
replacement RTC batteries for XO-1 and XO-1.5; which are recommended?
Does anyone have recommended RTC battery model number(s) handy for XO-1 and XO-1.5? In context with these very useful RTC (Real-Time-Clock on motherboard) rescue/maintenance tips here: http://wiki.laptop.org/go/Fix_Clock/Background Evidently some schools prefer a clean start, replacing all their RTC batteries now that XO-1 laptops especially are approaching a decade of life. Depending what RTC prices and Minimum Order Quantities are forthcoming in 2016+ of course -- both for smaller & larger operations -- perhaps Nathan has an idea? (Less urgent, but recommended RTC battery model numbers for XO-1.75 and XO-4 would be wonderful too, if handy?) *Aside: http://wiki.laptop.org/go/Reuse_checklist <http://wiki.laptop.org/go/Reuse_checklist> is an excellent more comprehensive list of refurbishing tactics for those interested!* ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [support-gang] A XO-1 BUA ("keyboard") replaced with a XO-1.75 BUA
Hey, This sounds great. I have a couple of XO-1s that could well do with this upgrade. Is it possible for the general public to buy the XO-1.75 BUA? Or even a XO-4 BUA if it's compatible. Cheers, Andrew On Tue, 2016-01-12 at 21:07 -0500, Adam Holt wrote: > Thanks Nathan! Am circulating to devel@laptop so we get more > thoughts- > On Jan 12, 2016 8:32 PM, <nathanr...@charter.net> wrote: > > > > A XO-1 BUA (Base Upper Assembly -- "keyboard" [ http://flickr.com/ > curiouslee/5932732888 http://flickr.com/curiouslee/5932732736 ] ) > replaced with a XO-1.75 BUA and no mechanical or software issues were > observed, (13.2.6 SD). No modification needed. > > If someone can confirm that XO-4 BUA is same as for XO-1.75 BUA, > then the BUA from any XO model can be used on the XO-1. > > > > Previously posted here by others that lower half of any XO model > could be used on the XO-1. > > > > I had been unable to obtain any answer as to the ongoing BUA > compatibility question, so made the test with the first XO-1.75 that > I got my hands on. :) > > > > Nathan Riddle > [There are hundreds of XO's out there than that are being refurb'd, > in Boston/Michigan/Nicaragua/Haiti especially, but we're only just > getting started: Nancie Severs & Paul Fox helped tremendously in > November!!] > ___ > Devel mailing list > Devel@lists.laptop.org > http://lists.laptop.org/listinfo/devel -- Andrew Ruthven, Wellington, New Zealand MIITP, CITPNZ At work: andrew.ruth...@catalyst.net.nz At home: and...@etc.gen.nz Card : http://qr.catalyst.net.nz/907675e1 Cloud : NZs only real cloud - https://catalyst.net.nz/cloud GPG fpr: C603 FC4E 600F 1CEC D1C8 D97C 4B53 D931 E4D3 E863 LCA2016: LCA By the Bay, Geelong, AU - lca2016.linux.org ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Server-devel] [support-gang] "Modern" Browser XO-1
On Mon, Jan 11, 2016 at 10:33 AM, Sora Edwards-Thro <s...@unleashkids.org> wrote: > Hi all, > > What's the most "modern" browser someone could install on an XO-1? (either > Sugar or Gnome side). What options do we have for upgrading to support > specific apps? > > This is a generic question that I figure others would be interested. I > have a specific problem I want to deal with in the future, but not enough > information to ask a good question about it yet. > This affects so many so I'm expanding the conversation to others who know more: what modern/snappy browsers do different folk out there find are most viable for XO-1 (primarily, but all other XO laptops too) going forward? For offline content / offline deployments especially, where security risks are theoretically a lot lower -- but yet these schools increasingly need to render "modern" HTML5/Javascript content, and will use Gnome or Sugar depending which browser's best -- and hopefully Sugarizer soon too! Currently on the SD cards for XO-1 we're preparing for many countries (and Los Angeles' big SCaLE show in 10 days) we include these 3 browsers so people have options: OLPC Release 13.2.6's Browse activity (far better than older browsers ;) Epiphany on Gnome (wonderfully fast!) Firefox 26.0 on Gnome (I wish something more up-to-date was available for Fedora 18, but apparently not?) Going forward what subtleties should we be paying attention to between browsers to do better? Separately, why does Firefox 43.x still seem like a hog after so many years, after major improvement recently isolating tabs from one another as Chrome pioneered? (And where is Nick Doiron hiding in Asia, to solve all our front-end problems when we need him ;-) Thanks all for digging deeper into this annoying-yet-central question -- hemlines rise and fall in the fashion industry of which browsers are coolest/fastest one year to the next -- but at the same time we need to come full circle making strong recommendations to deployments that constantly keep asking us =} -- Unsung Heroes of OLPC, interviewed live @ http://unleashkids.org ! ___ Server-devel mailing list Server-devel@lists.laptop.org http://lists.laptop.org/listinfo/server-devel
GentooXO; Re: Ubuntu 15.04/15.10 for xo-1
Am Samstag, 29. August 2015, 09:09:28 schrieb James Cameron: If you guys want i could port ubuntu 15.04 or 15.10 to xo-1 like i did with 14.04 Did anybody use it? I didn't. It was too hard! I don’t know about Ubuntu, but I’m still using GentooXO on an xo-1 as my working system when I’m moving. Best wishes, Arne -- Unpolitisch sein heißt politisch sein, ohne es zu merken. - Arne (http://draketo.de) signature.asc Description: This is a digitally signed message part. ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Ubuntu 15.04/15.10 for xo-1
If you guys want i could port ubuntu 15.04 or 15.10 to xo-1 like i did with 14.04 :P ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Ubuntu 15.04/15.10 for xo-1
On Fri, Aug 28, 2015 at 11:19:24AM -0700, Jhon Diaz wrote: If you guys want i could port ubuntu 15.04 or 15.10 to xo-1 like i did with 14.04 :P Did anybody use it? I didn't. It was too hard! HOWTO.save was very very long. Can you use programming to make it shorter? Also, please update our Wiki pages; or your work is lost and isolated from community. These two pages may be important: http://wiki.laptop.org/go/Ubuntu (how to use Ubuntu on XO laptops) http://wiki.sugarlabs.org/go/Ubuntu (how to add Sugar to 14.04) -- James Cameron http://quozl.linux.org.au/ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: intermittent keyboard mismapping: 13.2.5 on XO-1 SKU39
Summary: while both 13.2.5 OS's for XO-1 SKU39 (and possibly similar SKU's) have a couple keyboard/mouse issues, arising from q2f20's EC firmware it seems -- the workaround to both issues appears very simple -- simply do not to touch the keyboard during these 2 critical moments: - during the first few seconds after powering on (hit/hold ESC key _after_ the XO kid appears in the center of your screen, if seeking the ok prompt on an unlocked XO) - when the XO is sleeping Yes there's now also a bulletproof workaround to the 1st issue (keyboard mismapping if ESC is tapped too early during bootup) if you downgrade firmware from q2f20 to http://dev.laptop.org/~quozl/q2f20ed.rom which includes EC Firmware E35, dated 2010-08-23. Wonderful that James Cameron isolated the problem. But this fix might not be worth the trouble, as keyboard+mouse variously go haywire after sleep/wake -- up particularly if you touch the keyboard while XO's sleeping -- regardless which of these 2 firmwares. Regardless, folks need to retrain (refrain) themselves on when to hit ESC on bootup: http://wiki.laptop.org/go/Ok#Unsecured Conclusion: I'm not educated enough to know whether q2f20 or q2f20ed is best for one deployment or another. Sticking with 13.2.5's stock firmware q2f20 (including EC Firmware 1.2.1) might well be easiest for many, certainly for now, sure the above 2 workarounds to require training, but both appear 100% effective so far. Or if you do choose to downgrade to q2f20ed, note the 4 small accompanying regressions/risks below, and judge for yourself: - you lose a fix for mouse activity at shutdown preventing reboot without keyboard, - you lose a fix for battery EEPROM corruption, which happens if you are holding the power button down and insert the battery, - you lose the AP (Auto Power) and CP (Constant Power) features for use as a server, and; - you lose RTC anti-rollback support, which you shouldn't be using anyway. Most important, let's all be very helpful James Cameron carefully explained the above tradeoff- whether XO-1 live forever or not as we shall see :-) On Tue, Aug 4, 2015 at 9:28 AM, Adam Holt h...@laptop.org wrote: Just an update that I've narrowed in on the/a pattern which triggers the problem, with the help of James Cameron, and some workarounds: - Tapping the ESC key very rapidly during bootup causes the keyboard mismapping (and hence, failure to enter Open Firmware). - Holding down the ESC key during bootup (generally, but not always) avoids the problem (entering Open Firmware). - Typing no keys at all during initial bootup, appears (I hope) to be a workaround to boot the OS properly, with keyboard functioning properly. Better yet, earlier firmware (e.g. q2e41 in this case) does not appear to show the problem at all, so newer firmware may be available in future to solve this annoying-but-less-serious-that-I-imagined problem. For all using SKU39 XO-1s (or perhaps other/similar XO laptops having the modern touchpad?) On Mon, Aug 3, 2015 at 7:03 PM, Adam Holt h...@laptop.org wrote: I haven't figured out the pattern yet, but perhaps 50% of the time these XO-1s boot with an unusable keyboard (it's a US Intl keyboard, but the keys end up mapped to all the wrong places, showing the wrong letters/numbers, such that not even the ESC key works to get to the Ok prompt). This pattern arises with vanilla 13.2.5 (without SD cards) as well as 13.2.5 with SD cards. In other words both of these: http://wiki.laptop.org/go/Release_notes/13.2.5#XO-1 http://wiki.laptop.org/go/Release_notes/13.2.5#XO-1_with_SD_card Running the bye command at the Ok prompt seems to trigger the problem almost every time (possibly every time?). But that is not the only thing that triggers the problem. Sometimes the XO just boots with unusable keyboard, repeatedly. Then when I try to hit ESC on boot 20 times in a row, I cannot reproduce the problem at other times. Problem occurs on all SKU39 XO-1s I've tried so far. I've not yet tried other SKU's. My testing has only just begun, to see if this same problem occurs with (both) 13.2.4 OS's and earlier. Any tips for debugging / identifying the source of this quite serious gremlin? What should I and my small team of debugging volunteers look out for and try? And I'll do more work on this when I get back home late tonight, but all thoughts appreciated- (Also, any recommendations as to which older builds are best, as an interim workaround?) -- Unsung Heroes of OLPC, interviewed live @ http://unleashkids.org ! -- Unsung Heroes of OLPC, interviewed live @ http://unleashkids.org ! ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [support-gang] intermittent keyboard mismapping: 13.2.5 on XO-1 SKU39
G'day Caryl, If you're asking with respect to the discussion thread, go ahead with the latest 13.2.5, because the problem Adam is talking about won't affect you or the women and children, it is very minor. Otherwise, 13.2.5 is still the best for XO-1 because it can start every activity at once if necessary, and has all the latest updates. http://wiki.laptop.org/go/Release_notes/13.2.5/Installation/XO-1 On Tue, Aug 04, 2015 at 10:07:23AM -0600, Caryl Bigenho wrote: Hi… So… the XO-1s at the project we have at a school at a women's shelter in central Los Angeles will be updated in the next couple of weeks, getting ready for September school start. What would be the safest build for them to use? I won't be there to help, but it is in good hands with one of our SoCal volunteers. I just want to make it easy for everything to go smoothly. Thanks, Carul ━━━ Date: Tue, 4 Aug 2015 09:28:23 -0400 From: h...@laptop.org To: support-g...@lists.laptop.org; de...@laptop.org Subject: Re: [support-gang] intermittent keyboard mismapping: 13.2.5 on XO-1 SKU39 Just an update that I've narrowed in on the/a pattern which triggers the problem, with the help of James Cameron, and some workarounds: • Tapping the ESC key very rapidly during bootup causes the keyboard mismapping (and hence, failure to enter Open Firmware). • Holding down the ESC key during bootup (generally, but not always) avoids the problem (entering Open Firmware). • Typing no keys at all during initial bootup, appears (I hope) to be a workaround to boot the OS properly, with keyboard functioning properly. Better yet, earlier firmware (e.g. q2e41 in this case) does not appear to show the problem at all, so newer firmware may be available in future to solve this annoying-but-less-serious-that-I-imagined problem. For all using SKU39 XO-1s (or perhaps other/similar XO laptops having the modern touchpad?) On Mon, Aug 3, 2015 at 7:03 PM, Adam Holt [1]h...@laptop.org wrote: I haven't figured out the pattern yet, but perhaps 50% of the time these XO-1s boot with an unusable keyboard (it's a US Intl keyboard, but the keys end up mapped to all the wrong places, showing the wrong letters/ numbers, such that not even the ESC key works to get to the Ok prompt). This pattern arises with vanilla 13.2.5 (without SD cards) as well as 13.2.5 with SD cards. In other words both of these: [2]http://wiki.laptop.org/go/Release_notes/13.2.5#XO-1 [3]http://wiki.laptop.org/go/Release_notes/13.2.5#XO-1_with_SD_card Running the bye command at the Ok prompt seems to trigger the problem almost every time (possibly every time?). But that is not the only thing that triggers the problem. Sometimes the XO just boots with unusable keyboard, repeatedly. Then when I try to hit ESC on boot 20 times in a row, I cannot reproduce the problem at other times. Problem occurs on all SKU39 XO-1s I've tried so far. I've not yet tried other SKU's. My testing has only just begun, to see if this same problem occurs with (both) 13.2.4 OS's and earlier. Any tips for debugging / identifying the source of this quite serious gremlin? What should I and my small team of debugging volunteers look out for and try? And I'll do more work on this when I get back home late tonight, but all thoughts appreciated- (Also, any recommendations as to which older builds are best, as an interim workaround?) -- Unsung Heroes of OLPC, interviewed live @ [4]http://unleashkids.org ! ___ support-gang mailing list support-g...@lists.laptop.org http://lists.laptop.org/listinfo/support-gang References: [1] mailto:h...@laptop.org [2] http://wiki.laptop.org/go/Release_notes/13.2.5#XO-1 [3] http://wiki.laptop.org/go/Release_notes/13.2.5#XO-1_with_SD_card [4] http://unleashkids.org/ ___ support-gang mailing list support-g...@lists.laptop.org http://lists.laptop.org/listinfo/support-gang -- James Cameron http://quozl.linux.org.au/ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [support-gang] intermittent keyboard mismapping: 13.2.5 on XO-1 SKU39
G'day Caryl, If you're asking with respect to the discussion thread, go ahead with the latest 13.2.5, because the problem Adam is talking about won't affect you or the women and children, it is very minor. Otherwise, 13.2.5 is still the best for XO-1 because it can start every activity at once if necessary, and has all the latest updates. http://wiki.laptop.org/go/Release_notes/13.2.5/Installation/XO-1 On Tue, Aug 04, 2015 at 10:07:23AM -0600, Caryl Bigenho wrote: Hi… So… the XO-1s at the project we have at a school at a women's shelter in central Los Angeles will be updated in the next couple of weeks, getting ready for September school start. What would be the safest build for them to use? I won't be there to help, but it is in good hands with one of our SoCal volunteers. I just want to make it easy for everything to go smoothly. Thanks, Carul ━━━ Date: Tue, 4 Aug 2015 09:28:23 -0400 From: h...@laptop.org To: support-g...@lists.laptop.org; de...@laptop.org Subject: Re: [support-gang] intermittent keyboard mismapping: 13.2.5 on XO-1 SKU39 Just an update that I've narrowed in on the/a pattern which triggers the problem, with the help of James Cameron, and some workarounds: • Tapping the ESC key very rapidly during bootup causes the keyboard mismapping (and hence, failure to enter Open Firmware). • Holding down the ESC key during bootup (generally, but not always) avoids the problem (entering Open Firmware). • Typing no keys at all during initial bootup, appears (I hope) to be a workaround to boot the OS properly, with keyboard functioning properly. Better yet, earlier firmware (e.g. q2e41 in this case) does not appear to show the problem at all, so newer firmware may be available in future to solve this annoying-but-less-serious-that-I-imagined problem. For all using SKU39 XO-1s (or perhaps other/similar XO laptops having the modern touchpad?) On Mon, Aug 3, 2015 at 7:03 PM, Adam Holt [1]h...@laptop.org wrote: I haven't figured out the pattern yet, but perhaps 50% of the time these XO-1s boot with an unusable keyboard (it's a US Intl keyboard, but the keys end up mapped to all the wrong places, showing the wrong letters/ numbers, such that not even the ESC key works to get to the Ok prompt). This pattern arises with vanilla 13.2.5 (without SD cards) as well as 13.2.5 with SD cards. In other words both of these: [2]http://wiki.laptop.org/go/Release_notes/13.2.5#XO-1 [3]http://wiki.laptop.org/go/Release_notes/13.2.5#XO-1_with_SD_card Running the bye command at the Ok prompt seems to trigger the problem almost every time (possibly every time?). But that is not the only thing that triggers the problem. Sometimes the XO just boots with unusable keyboard, repeatedly. Then when I try to hit ESC on boot 20 times in a row, I cannot reproduce the problem at other times. Problem occurs on all SKU39 XO-1s I've tried so far. I've not yet tried other SKU's. My testing has only just begun, to see if this same problem occurs with (both) 13.2.4 OS's and earlier. Any tips for debugging / identifying the source of this quite serious gremlin? What should I and my small team of debugging volunteers look out for and try? And I'll do more work on this when I get back home late tonight, but all thoughts appreciated- (Also, any recommendations as to which older builds are best, as an interim workaround?) -- Unsung Heroes of OLPC, interviewed live @ [4]http://unleashkids.org ! ___ support-gang mailing list support-g...@lists.laptop.org http://lists.laptop.org/listinfo/support-gang References: [1] mailto:h...@laptop.org [2] http://wiki.laptop.org/go/Release_notes/13.2.5#XO-1 [3] http://wiki.laptop.org/go/Release_notes/13.2.5#XO-1_with_SD_card [4] http://unleashkids.org/ ___ support-gang mailing list support-g...@lists.laptop.org http://lists.laptop.org/listinfo/support-gang -- James Cameron http://quozl.linux.org.au/ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: intermittent keyboard mismapping: 13.2.5 on XO-1 SKU39
Just an update that I've narrowed in on the/a pattern which triggers the problem, with the help of James Cameron, and some workarounds: - Tapping the ESC key very rapidly during bootup causes the keyboard mismapping (and hence, failure to enter Open Firmware). - Holding down the ESC key during bootup (generally, but not always) avoids the problem (entering Open Firmware). - Typing no keys at all during initial bootup, appears (I hope) to be a workaround to boot the OS properly, with keyboard functioning properly. Better yet, earlier firmware (e.g. q2e41 in this case) does not appear to show the problem at all, so newer firmware may be available in future to solve this annoying-but-less-serious-that-I-imagined problem. For all using SKU39 XO-1s (or perhaps other/similar XO laptops having the modern touchpad?) On Mon, Aug 3, 2015 at 7:03 PM, Adam Holt h...@laptop.org wrote: I haven't figured out the pattern yet, but perhaps 50% of the time these XO-1s boot with an unusable keyboard (it's a US Intl keyboard, but the keys end up mapped to all the wrong places, showing the wrong letters/numbers, such that not even the ESC key works to get to the Ok prompt). This pattern arises with vanilla 13.2.5 (without SD cards) as well as 13.2.5 with SD cards. In other words both of these: http://wiki.laptop.org/go/Release_notes/13.2.5#XO-1 http://wiki.laptop.org/go/Release_notes/13.2.5#XO-1_with_SD_card Running the bye command at the Ok prompt seems to trigger the problem almost every time (possibly every time?). But that is not the only thing that triggers the problem. Sometimes the XO just boots with unusable keyboard, repeatedly. Then when I try to hit ESC on boot 20 times in a row, I cannot reproduce the problem at other times. Problem occurs on all SKU39 XO-1s I've tried so far. I've not yet tried other SKU's. My testing has only just begun, to see if this same problem occurs with (both) 13.2.4 OS's and earlier. Any tips for debugging / identifying the source of this quite serious gremlin? What should I and my small team of debugging volunteers look out for and try? And I'll do more work on this when I get back home late tonight, but all thoughts appreciated- (Also, any recommendations as to which older builds are best, as an interim workaround?) -- Unsung Heroes of OLPC, interviewed live @ http://unleashkids.org ! ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
intermittent keyboard mismapping: 13.2.5 on XO-1 SKU39
I haven't figured out the pattern yet, but perhaps 50% of the time these XO-1s boot with an unusable keyboard (it's a US Intl keyboard, but the keys end up mapped to all the wrong places, showing the wrong letters/numbers, such that not even the ESC key works to get to the Ok prompt). This pattern arises with vanilla 13.2.5 (without SD cards) as well as 13.2.5 with SD cards. In other words both of these: http://wiki.laptop.org/go/Release_notes/13.2.5#XO-1 http://wiki.laptop.org/go/Release_notes/13.2.5#XO-1_with_SD_card Running the bye command at the Ok prompt seems to trigger the problem almost every time (possibly every time?). But that is not the only thing that triggers the problem. Sometimes the XO just boots with unusable keyboard, repeatedly. Then when I try to hit ESC on boot 20 times in a row, I cannot reproduce the problem at other times. Problem occurs on all SKU39 XO-1s I've tried so far. I've not yet tried other SKU's. My testing has only just begun, to see if this same problem occurs with (both) 13.2.4 OS's and earlier. Any tips for debugging / identifying the source of this quite serious gremlin? What should I and my small team of debugging volunteers look out for and try? And I'll do more work on this when I get back home late tonight, but all thoughts appreciated- (Also, any recommendations as to which older builds are best, as an interim workaround?) ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [IAEP] Announcing OLPC OS 13.2.4 for XO-1
Great news .. indeed. I am trying out the new 13.2.4 release in my XO-1 now. When I try to use the sugar-install-bundle to install/add new activities (e.g. recall-4.xo) it stall at the end with the message: caution: excluded filename not matched: mimetype I need to use Ctrl-C as keyboard interrupt to continue. In a simple script that contain a number of sugar-install-build I have to do many Ctrl-C to enable it to run. In previous 13.2.1 I need no manual intervention. Advice? --- T.K. Kang -Original Message- From: James Cameron [mailto:qu...@laptop.org] Sent: Monday, May 11, 2015 01:35 PM To: devel@lists.laptop.org, sugar-de...@lists.sugarlabs.org, support-g...@lists.laptop.org, i...@lists.sugarlabs.org, unleashk...@googlegroups.com Subject: [IAEP] Announcing OLPC OS 13.2.4 for XO-1 G'day, We're pleased to announce the release of OLPC OS 13.2.4 for XO-1. It is Sugar 0.104 on Fedora 18, with a fix to using Browse with Google Search. To install on XO-1: http://wiki.laptop.org/go/Release_notes/13.2.4/Installation/XO-1 To install on SD card on XO-1: http://wiki.laptop.org/go/Release_notes/13.2.4/Installation/XO-1/SD Details of new features, known issues, and how to download, install or upgrade can be found in the release notes: http://wiki.laptop.org/go/Release_notes/13.2.4 Many thanks to all contributors, testers, upstreams, and those who have provided feedback of any kind. 32016o0 -- James Cameron http://quozl.linux.org.au/ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [UKids] Re: [IAEP] Announcing OLPC OS 13.2.4 for XO-1
I've set Reply-to sugar-devel@. On Tue, May 12, 2015 at 12:19:56AM +, tkk...@nurturingasia.com wrote: When I try to use the sugar-install-bundle to install/add new activities (e.g. recall-4.xo) it stall at the end with the message: caution: excluded filename not matched: mimetype The message is normal, but is not the cause of the hang. I've reproduced this. The hang lasts for a few minutes. The hang is caused by code in Sugar that is continually trying to set an inotify watch on /usr/local/share/sugar/activities You can work around the problem by creating this directory: sudo mkdir /usr/local/share/sugar/activities You would not have this problem if you had used olpc-os-builder, which is the method recommended and tested by OLPC. @Sam, any ideas? -- James Cameron http://quozl.linux.org.au/ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Sugar-devel] Announcing OLPC OS 13.2.4 for XO-1
Nice!!! -walter On Mon, May 11, 2015 at 1:35 AM, James Cameron qu...@laptop.org wrote: G'day, We're pleased to announce the release of OLPC OS 13.2.4 for XO-1. It is Sugar 0.104 on Fedora 18, with a fix to using Browse with Google Search. To install on XO-1: http://wiki.laptop.org/go/Release_notes/13.2.4/Installation/XO-1 To install on SD card on XO-1: http://wiki.laptop.org/go/Release_notes/13.2.4/Installation/XO-1/SD Details of new features, known issues, and how to download, install or upgrade can be found in the release notes: http://wiki.laptop.org/go/Release_notes/13.2.4 Many thanks to all contributors, testers, upstreams, and those who have provided feedback of any kind. 32016o0 -- James Cameron http://quozl.linux.org.au/ ___ Sugar-devel mailing list sugar-de...@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel -- Walter Bender Sugar Labs http://www.sugarlabs.org ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Announcing OLPC OS 13.2.4 for XO-1
G'day, We're pleased to announce the release of OLPC OS 13.2.4 for XO-1. It is Sugar 0.104 on Fedora 18, with a fix to using Browse with Google Search. To install on XO-1: http://wiki.laptop.org/go/Release_notes/13.2.4/Installation/XO-1 To install on SD card on XO-1: http://wiki.laptop.org/go/Release_notes/13.2.4/Installation/XO-1/SD Details of new features, known issues, and how to download, install or upgrade can be found in the release notes: http://wiki.laptop.org/go/Release_notes/13.2.4 Many thanks to all contributors, testers, upstreams, and those who have provided feedback of any kind. 32016o0 -- James Cameron http://quozl.linux.org.au/ signature.asc Description: Digital signature ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Windows xo-1
Microsoft Windows XP was released for the XO-1 and XO-1.5 laptops. Both were special projects done for a limited number of users, and were never maintained beyond the initial release. Neither version is or was generally available. - Ed On Apr 25, 2015, at 9:41 PM, Jhon Diaz linuxs...@gmail.com wrote: Is windows on xo-1 real i saw it in a video if so how or where can i get a copy ___ 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
Windows xo-1
Is windows on xo-1 real i saw it in a video if so how or where can i get a copy ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: XO-1 vs Sugar 0.104 performance, and swap to NAND Flash
On Mon, Apr 13, 2015 at 05:56:22AM +, Yioryos Asprobounitis wrote: James wrote: To check, make sure the laptop is unlocked, and add this to the second line of the boot/olpc.fth file: dev /sd patch 2drop cb! sdhci-card-power-off dend Does this keep the SD slot powered only when is occupied or regardless? Regardless, but only if the slot is powered up for access. Does the OS takes over the SD slot power management after boot? Yes. The firmware driver is not used by the kernel. If not, can OFW detect the presence of an external SDcard early, and keep it powered only then or detect its absence latter in the boot sequence and revert? Not answered. -- James Cameron http://quozl.linux.org.au/ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [support-gang] XO-1 vs Sugar 0.104 performance, and swap to NAND Flash
To check, make sure the laptop is unlocked, and add this to the second line of the boot/olpc.fth file: dev /sd patch 2drop cb! sdhci-card-power-off dend Does this keep the SD slot powered only when is occupied or regardless? Does the OS takes over the SD slot power management after boot? If not, can OFW detect the presence of an external SDcard early, and keep it powered only then or detect its absence latter in the boot sequence and revert? ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: XO-1 vs Sugar 0.104 performance, and swap to NAND Flash
Very nice job James. Thanks to give us these details. Numbers give sometimes more than tons of words ! Lionel. 2015-04-08 18:00 GMT+02:00 devel-requ...@lists.laptop.org: Date: Wed, 8 Apr 2015 13:47:27 +1000 From: James Cameron qu...@laptop.org To: support-g...@lists.laptop.org, devel@lists.laptop.org, sugar-de...@lists.sugarlabs.org Subject: Re: XO-1 vs Sugar 0.104 performance, and swap to NAND Flash Message-ID: 20150408034727.gi9...@us.netrek.org Content-Type: text/plain; charset=us-ascii Browse is one of the most heavily used activities when internet or local content is available. Tests were run over many hours on several XO-1 laptops. The XO-1 is an old design which is slow enough to give useful statistics. The results show a continued improvement to startup time over the recent versions of Sugar, and a very small advantage to using swap memory. -- The first test was to reboot, wait for Sugar to start, then automatically start the Browse activity, and time how long it took to start. Then the results of hundreds of tests were averaged. Browse-140 on 12.1.0 with Sugar 0.94 took 25 seconds. Browse-149.4 on 13.2.1 with Sugar 0.98 took 23 seconds. Browse-157 on 13.2.4 with Sugar 0.104 and no swap took 21 seconds. Browse-157 on 13.2.4 with Sugar 0.104 and NAND swap took 20 seconds. This shows continued improvement to Browse startup time, in the scenario where the libraries have to be loaded into memory. (Reference: test #8, and #9) -- Another test started and stopped the Browse activity 25 times without rebooting. Then the results were averaged. Browse-140 on 12.1.0 with Sugar 0.94 took 14 seconds. Browse-149.4 on 13.2.1 with Sugar 0.98 took 15 seconds. Browse-157 on 13.2.4 with Sugar 0.104 and NAND swap took 13 seconds. This shows some improvement to Browse startup time, in the scenario where the needed libraries are already loaded into memory. (Reference: test #6) -- The same test also started and stopped most of the other activities 25 times without rebooting. Then the results were averaged. For Sugar 0.96 the average startup time was 15 seconds the first time, and 11 seconds each subsequent time. For Sugar 0.98 the average startup time was 17 seconds the first time, and 13 seconds each subsequent time. For Sugar 0.104 the average startup time was 14 seconds the first time, and 11 seconds each subsequent time. Detailed results by activity below. The key for these tables is: cold = startup time for first start after sugar restart. warm = average of startup time for subsequence starts. std = population standard deviation for warm starts. ratio = a ratio comparing warm start to cold start times. tests = number of warm start tests recorded. For Sugar 0.96 the results by activity were: bundle_idcoldwarmstd ratio tests com.garycmartin.Moon 10.595 10.643 0.531 1.005 24 com.jotaro.ImplodeActivity 6.691 6.486 0.045 0.969 24 org.laptop.AbiWordActivity 19.474 14.459 0.804 0.743 24 org.laptop.AcousticMeasure 11.984 7.761 0.045 0.648 24 org.laptop.Calculate 9.809 9.560 0.065 0.975 24 org.laptop.HelpActivity 19.487 11.342 0.688 0.582 24 org.laptop.MeasureActivity 12.478 10.246 0.085 0.821 24 org.laptop.Memorize 16.229 13.243 0.539 0.816 24 org.laptop.Oficina 10.421 9.490 0.431 0.911 24 org.laptop.Pippy 6.421 6.150 0.050 0.958 24 org.laptop.RecordActivity 12.563 11.179 0.346 0.890 24 org.laptop.TamTamMini 16.676 14.414 0.338 0.864 24 org.laptop.WebActivity 23.335 14.260 0.241 0.611 24 tv.alterna.Clock 8.782 8.631 0.067 0.983 24 vu.lux.olpc.Maze 11.699 8.731 0.269 0.746 24 vu.lux.olpc.Speak 15.187 11.460 0.261 0.755 24 For Sugar 0.98 the results by activity were: bundle_idcoldwarmstd ratio tests com.garycmartin.Moon 12.946 11.039 0.372 0.853 24 com.jotaro.ImplodeActivity 11.494 11.352 0.499 0.988 24 org.laptop.AbiWordActivity 26.611 21.501 1.041 0.808 24 org.laptop.AcousticMeasure 14.865 12.949 0.351 0.871 24 org.laptop.Calculate 12.063 10.220 0.207 0.847 24 org.laptop.HelpActivity 18.378 11.101 0.311 0.604 24 org.laptop.MeasureActivity 19.566 13.791 0.308 0.705 24 org.laptop.Memorize 20.977 14.462 0.791 0.689 24 org.laptop.Oficina 14.216 13.948 0.246 0.981 24 org.laptop.Pippy 11.793 10.983 0.141 0.931 24 org.laptop.RecordActivity 18.459 13.165 0.514 0.713 24 org.laptop.sugar.Jukebox 16.346 11.466 0.292 0.701
Re: XO-1 vs Sugar 0.104 performance, and swap to NAND Flash
On Wed, Apr 08, 2015 at 07:35:34PM -0400, Kevin Gordon Gmail wrote: Perhaps silly Q... Any benefit just putting swap and static content on the SD? No question is silly. ;-) I'm guessing you are asking about performance, or response times. If so, the short answer is no. Details below. If you are looking for benefits other than performance, the main benefit is total size. NAND flash is only 1 GB. By adding an 128 GB SD card, the total content stored on the XO-1 can increase dramatically. -- Details #1 It has to do with when data moves, and how much concurrency occurs. A counter question is ... when is it that the XO-1 will both read from NAND flash _and_ from SD card at the same time? Probably never. Data that moves from NAND flash to memory happens during Sugar startup, and the first time an activity is started. It can also happen if a different activity is started. Once an activity is started, usually no further demand occurs. Memory data that moves to swap does so because it isn't being used. In my tests of Sugar 0.104 on Fedora 18, about 12 MB of data moves to swap, and no more. This happens during Sugar startup, and the first activity startup, then it doesn't happen any more until the next reboot. This data generally does not return from swap. So with swap on SD card, it only benefits during Sugar startup and first activity startup, and before content is accessed. Content data, such as videos, web pages, audio, images, and so on, is accessed after the Browse activity has started. So with content on SD card, there should be no significant difference. While the system is capable of much more concurrency (see below), Sugar and the activities just don't make that demand. You could test it by timing how long before content is visible. -- Details #2 Proof the NAND flash and SD card do not block each other. The camera, SD card reader slot, and NAND flash all hang off the CAFE ASIC which presents through a PCI bus to the CPU. Does filling the data channel to one device block the other device in any way? Read test from NAND flash yields about 8 MB/s. When the SD card is doing a read test, a simultaneous read test from NAND flash yields about 5.8 MB/s. The decrease is due to contention for CPU and bus. At the same time, the SD card read test result is mostly unchanged, falling from 6.9 MB/s to 6.6 MB/s. Read from filesystem cache of NAND flash yields about 45 MB/s. When the SD card is doing a read test, a read from filesystem cache of NAND flash yields about 32 MB/s. The decrease is due to contention for CPU and bus. At the same time, the SD card read test result is mostly unchanged, falling from 6.9 MB/s to 6.7 MB/s. This means the bus path to the SD card is mostly idle, and the kernel is waiting for the SD card to respond. So the CAFE ASIC and PCI bus are easily able to handle an aggregate of about 12.4 MB/s, and perhaps much more. -- James Cameron http://quozl.linux.org.au/ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: XO-1 vs Sugar 0.104 performance, and swap to NAND Flash
Perhaps silly Q... Any benefit just putting swap and static content on the SD? Kg Sent from my currently functioning gadget Original Message From: James Cameron Sent: Wednesday, April 8, 2015 19:31 To: devel@lists.laptop.org; sugar-de...@lists.sugarlabs.org; support-g...@lists.laptop.org Subject: Re: XO-1 vs Sugar 0.104 performance, and swap to NAND Flash What benefit is an SD card on an XO-1? My tests of about 400 starts show some benefit of using an SD card, on activity startup time. The benefits are: - boot time was decreased by several seconds; because of reduced demand for memory, - first activity start after boot was decreased by several seconds; because of reduced demand for memory, - when there is no contention for memory, mean cold activity startup time is decreased by between 1 and 2 seconds; because of both different data rates and no decompression, and; - writing journal entries is slightly faster. There was no benefit on activity startup time where caches were warm; everything needed by the activity was already in memory, so there was no extra wait. The SD card was a SanDisk Ultra 8GB, class 10, 30 MB/s. Sequential read speed on a modern desktop is 18.5 MB/s. But on the XO-1 the speed is 6.3 MB/s. There may be little advantage to using a faster card. For Sugar 0.104 comparing results by activity, between NAND flash and SD card: bundle_id cold warm std ratio tests com.garycmartin.Moon 11.928 10.294 0.492 0.863 24 com.garycmartin.Moon 11.809 10.585 0.516 0.896 24 sd com.jotaro.ImplodeActivity 9.084 9.017 0.498 0.993 24 com.jotaro.ImplodeActivity 9.560 8.904 0.501 0.931 24 sd org.laptop.AbiWordActivity 20.868 16.862 0.376 0.808 24 org.laptop.AbiWordActivity 19.326 16.441 0.277 0.851 24 sd org.laptop.AcousticMeasure 12.330 10.513 0.137 0.853 24 org.laptop.AcousticMeasure 11.854 10.552 0.254 0.890 24 sd org.laptop.Calculate 11.591 9.920 0.120 0.856 24 org.laptop.Calculate 12.152 9.975 0.205 0.821 24 sd org.laptop.HelpActivity 14.654 8.981 0.329 0.613 24 org.laptop.HelpActivity 13.025 9.027 0.345 0.693 24 sd org.laptop.MeasureActivity 16.381 11.364 0.135 0.694 24 org.laptop.MeasureActivity 15.000 11.634 0.344 0.776 24 sd org.laptop.Memorize 17.961 14.550 0.183 0.810 24 org.laptop.Memorize 16.442 14.724 0.240 0.896 24 sd org.laptop.Oficina 12.231 12.029 0.351 0.983 24 org.laptop.Oficina 13.250 12.270 0.585 0.926 24 sd org.laptop.Pippy 8.752 8.202 0.128 0.937 24 org.laptop.Pippy 9.897 8.404 0.467 0.849 24 sd org.laptop.RecordActivity 16.956 12.652 0.145 0.746 24 org.laptop.RecordActivity 15.341 12.501 0.255 0.815 24 sd org.laptop.sugar.Jukebox 9.666 8.986 0.108 0.930 24 org.laptop.sugar.Jukebox 9.821 9.287 0.472 0.946 24 sd org.laptop.sugar.ReadActivity 11.296 10.477 0.165 0.928 24 org.laptop.sugar.ReadActivity 11.080 10.618 0.463 0.958 24 sd org.laptop.TamTamMini 18.628 14.734 0.576 0.791 24 org.laptop.TamTamMini 19.838 14.615 0.288 0.737 24 sd org.laptop.WebActivity 19.425 12.527 0.217 0.645 24 org.laptop.WebActivity 17.935 12.937 0.274 0.721 24 sd tv.alterna.Clock 10.061 7.124 0.123 0.708 24 tv.alterna.Clock 21.226 7.522 0.316 0.354 24 sd ? vu.lux.olpc.Maze 8.366 8.265 0.120 0.988 24 vu.lux.olpc.Maze 8.998 8.646 0.370 0.961 24 sd vu.lux.olpc.Speak 24.555 12.075 0.208 0.492 24 ? vu.lux.olpc.Speak 16.526 11.946 0.358 0.723 24 sd The cold results for Clock and Speak are unexpected, but this may be related to gst-plugin-scan. (Reference: test #6, vs #10) -- James Cameron http://quozl.linux.org.au/ ___ 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: XO-1 vs Sugar 0.104 performance, and swap to NAND Flash
What benefit is an SD card on an XO-1? My tests of about 400 starts show some benefit of using an SD card, on activity startup time. The benefits are: - boot time was decreased by several seconds; because of reduced demand for memory, - first activity start after boot was decreased by several seconds; because of reduced demand for memory, - when there is no contention for memory, mean cold activity startup time is decreased by between 1 and 2 seconds; because of both different data rates and no decompression, and; - writing journal entries is slightly faster. There was no benefit on activity startup time where caches were warm; everything needed by the activity was already in memory, so there was no extra wait. The SD card was a SanDisk Ultra 8GB, class 10, 30 MB/s. Sequential read speed on a modern desktop is 18.5 MB/s. But on the XO-1 the speed is 6.3 MB/s. There may be little advantage to using a faster card. For Sugar 0.104 comparing results by activity, between NAND flash and SD card: bundle_idcoldwarmstd ratio tests com.garycmartin.Moon 11.928 10.294 0.492 0.863 24 com.garycmartin.Moon 11.809 10.585 0.516 0.896 24 sd com.jotaro.ImplodeActivity 9.084 9.017 0.498 0.993 24 com.jotaro.ImplodeActivity 9.560 8.904 0.501 0.931 24 sd org.laptop.AbiWordActivity 20.868 16.862 0.376 0.808 24 org.laptop.AbiWordActivity 19.326 16.441 0.277 0.851 24 sd org.laptop.AcousticMeasure 12.330 10.513 0.137 0.853 24 org.laptop.AcousticMeasure 11.854 10.552 0.254 0.890 24 sd org.laptop.Calculate 11.591 9.920 0.120 0.856 24 org.laptop.Calculate 12.152 9.975 0.205 0.821 24 sd org.laptop.HelpActivity 14.654 8.981 0.329 0.613 24 org.laptop.HelpActivity 13.025 9.027 0.345 0.693 24 sd org.laptop.MeasureActivity 16.381 11.364 0.135 0.694 24 org.laptop.MeasureActivity 15.000 11.634 0.344 0.776 24 sd org.laptop.Memorize 17.961 14.550 0.183 0.810 24 org.laptop.Memorize 16.442 14.724 0.240 0.896 24 sd org.laptop.Oficina 12.231 12.029 0.351 0.983 24 org.laptop.Oficina 13.250 12.270 0.585 0.926 24 sd org.laptop.Pippy 8.752 8.202 0.128 0.937 24 org.laptop.Pippy 9.897 8.404 0.467 0.849 24 sd org.laptop.RecordActivity 16.956 12.652 0.145 0.746 24 org.laptop.RecordActivity 15.341 12.501 0.255 0.815 24 sd org.laptop.sugar.Jukebox 9.666 8.986 0.108 0.930 24 org.laptop.sugar.Jukebox 9.821 9.287 0.472 0.946 24 sd org.laptop.sugar.ReadActivity 11.296 10.477 0.165 0.928 24 org.laptop.sugar.ReadActivity 11.080 10.618 0.463 0.958 24 sd org.laptop.TamTamMini 18.628 14.734 0.576 0.791 24 org.laptop.TamTamMini 19.838 14.615 0.288 0.737 24 sd org.laptop.WebActivity 19.425 12.527 0.217 0.645 24 org.laptop.WebActivity 17.935 12.937 0.274 0.721 24 sd tv.alterna.Clock 10.061 7.124 0.123 0.708 24 tv.alterna.Clock 21.226 7.522 0.316 0.354 24 sd ? vu.lux.olpc.Maze 8.366 8.265 0.120 0.988 24 vu.lux.olpc.Maze 8.998 8.646 0.370 0.961 24 sd vu.lux.olpc.Speak 24.555 12.075 0.208 0.492 24 ? vu.lux.olpc.Speak 16.526 11.946 0.358 0.723 24 sd The cold results for Clock and Speak are unexpected, but this may be related to gst-plugin-scan. (Reference: test #6, vs #10) -- James Cameron http://quozl.linux.org.au/ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Sugar-devel] XO-1 vs Sugar 0.104 performance, and swap to NAND Flash
On 07/04/15 22:47, James Cameron wrote: The testing scripts can be made available if anybody else would like to replicate the results. I'd be curious to look at your scripts and try to replicate some results with our builds. git clone git://dev.laptop.org/users/quozl/test-startup-time.git Look at the file HOWTO. Somewhat unfinished work. Do ask any questions you may have. Thanks a lot for your detailed tests! No worries. Interesting details! I'd be interested to see if porting Browse to the newer webkit 2 and what effect the perf improvements there would offer ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Sugar-devel] XO-1 vs Sugar 0.104 performance, and swap to NAND Flash
On 07/04/15 22:47, James Cameron wrote: The testing scripts can be made available if anybody else would like to replicate the results. I'd be curious to look at your scripts and try to replicate some results with our builds. Thanks a lot for your detailed tests! Sebastian ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Sugar-devel] XO-1 vs Sugar 0.104 performance, and swap to NAND Flash
On Tue, Apr 07, 2015 at 11:32:00PM -0500, Sebastian Silva wrote: On 07/04/15 22:47, James Cameron wrote: The testing scripts can be made available if anybody else would like to replicate the results. I'd be curious to look at your scripts and try to replicate some results with our builds. git clone git://dev.laptop.org/users/quozl/test-startup-time.git Look at the file HOWTO. Somewhat unfinished work. Do ask any questions you may have. Thanks a lot for your detailed tests! No worries. -- James Cameron http://quozl.linux.org.au/ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
RE: [support-gang] XO-1 vs Sugar 0.104 performance, and swap to NAND Flash
Thanks for wrapping your arms around this. And congratulations to those who made the curve head in the right direction. -Original Message- From: support-gang [mailto:support-gang-boun...@lists.laptop.org] On Behalf Of James Cameron Sent: Tuesday, April 07, 2015 11:47 PM To: support-g...@lists.laptop.org; devel@lists.laptop.org; sugar-de...@lists.sugarlabs.org Subject: Re: [support-gang] XO-1 vs Sugar 0.104 performance, and swap to NAND Flash Browse is one of the most heavily used activities when internet or local content is available. Tests were run over many hours on several XO-1 laptops. The XO-1 is an old design which is slow enough to give useful statistics. The results show a continued improvement to startup time over the recent versions of Sugar, and a very small advantage to using swap memory. -- The first test was to reboot, wait for Sugar to start, then automatically start the Browse activity, and time how long it took to start. Then the results of hundreds of tests were averaged. Browse-140 on 12.1.0 with Sugar 0.94 took 25 seconds. Browse-149.4 on 13.2.1 with Sugar 0.98 took 23 seconds. Browse-157 on 13.2.4 with Sugar 0.104 and no swap took 21 seconds. Browse-157 on 13.2.4 with Sugar 0.104 and NAND swap took 20 seconds. This shows continued improvement to Browse startup time, in the scenario where the libraries have to be loaded into memory. (Reference: test #8, and #9) -- Another test started and stopped the Browse activity 25 times without rebooting. Then the results were averaged. Browse-140 on 12.1.0 with Sugar 0.94 took 14 seconds. Browse-149.4 on 13.2.1 with Sugar 0.98 took 15 seconds. Browse-157 on 13.2.4 with Sugar 0.104 and NAND swap took 13 seconds. This shows some improvement to Browse startup time, in the scenario where the needed libraries are already loaded into memory. (Reference: test #6) -- The same test also started and stopped most of the other activities 25 times without rebooting. Then the results were averaged. For Sugar 0.96 the average startup time was 15 seconds the first time, and 11 seconds each subsequent time. For Sugar 0.98 the average startup time was 17 seconds the first time, and 13 seconds each subsequent time. For Sugar 0.104 the average startup time was 14 seconds the first time, and 11 seconds each subsequent time. Detailed results by activity below. The key for these tables is: cold = startup time for first start after sugar restart. warm = average of startup time for subsequence starts. std = population standard deviation for warm starts. ratio = a ratio comparing warm start to cold start times. tests = number of warm start tests recorded. For Sugar 0.96 the results by activity were: bundle_idcoldwarmstd ratio tests com.garycmartin.Moon 10.595 10.643 0.531 1.005 24 com.jotaro.ImplodeActivity 6.691 6.486 0.045 0.969 24 org.laptop.AbiWordActivity 19.474 14.459 0.804 0.743 24 org.laptop.AcousticMeasure 11.984 7.761 0.045 0.648 24 org.laptop.Calculate 9.809 9.560 0.065 0.975 24 org.laptop.HelpActivity 19.487 11.342 0.688 0.582 24 org.laptop.MeasureActivity 12.478 10.246 0.085 0.821 24 org.laptop.Memorize 16.229 13.243 0.539 0.816 24 org.laptop.Oficina 10.421 9.490 0.431 0.911 24 org.laptop.Pippy 6.421 6.150 0.050 0.958 24 org.laptop.RecordActivity 12.563 11.179 0.346 0.890 24 org.laptop.TamTamMini 16.676 14.414 0.338 0.864 24 org.laptop.WebActivity 23.335 14.260 0.241 0.611 24 tv.alterna.Clock 8.782 8.631 0.067 0.983 24 vu.lux.olpc.Maze 11.699 8.731 0.269 0.746 24 vu.lux.olpc.Speak 15.187 11.460 0.261 0.755 24 For Sugar 0.98 the results by activity were: bundle_idcoldwarmstd ratio tests com.garycmartin.Moon 12.946 11.039 0.372 0.853 24 com.jotaro.ImplodeActivity 11.494 11.352 0.499 0.988 24 org.laptop.AbiWordActivity 26.611 21.501 1.041 0.808 24 org.laptop.AcousticMeasure 14.865 12.949 0.351 0.871 24 org.laptop.Calculate 12.063 10.220 0.207 0.847 24 org.laptop.HelpActivity 18.378 11.101 0.311 0.604 24 org.laptop.MeasureActivity 19.566 13.791 0.308 0.705 24 org.laptop.Memorize 20.977 14.462 0.791 0.689 24 org.laptop.Oficina 14.216 13.948 0.246 0.981 24 org.laptop.Pippy 11.793 10.983 0.141 0.931 24 org.laptop.RecordActivity 18.459 13.165 0.514 0.713 24 org.laptop.sugar.Jukebox 16.346 11.466 0.292 0.701 24 org.laptop.sugar.ReadActivity 16.407 13.253 0.597 0.808 24 org.laptop.TamTamMini 20.218 16.475 0.638
Re: [Sugar-devel] XO-1 vs Sugar 0.104 performance, and swap to NAND Flash
SHC8420412 = 332S On Thu, Apr 2, 2015 at 12:54 AM, James Cameron qu...@laptop.org wrote: With Sugar 0.98 in 13.2.1, the XO-1 was so short of memory that adding swap gave an obvious benefit. Thanks to those who have verified this for us. With Sugar 0.104 in 13.2.4, things seem much better on the XO-1, thanks to all the work done by Sugar Labs developers. But I'm not finished testing [1]. Meanwhile, there's an opportunity to add swap to jffs2 filesystem. The XO-1 NAND Flash is rated for 100,000 writes per cell. The jffs2 filesystem we use spreads the writes across all the cells. There's a risk that swapping to the NAND Flash will shorten the life of an XO-1. It may become slower at reading and writing journal entries. But they might already be so slow that this isn't a problem any more. What I need is some data from XO-1 that have been used a lot: how long does it take to reflash? To test, surround a copy-nand command with timing markers, like this: ok t-sec( copy-nand u:\32014o0.img )t-sec The result will be on the line above the ok prompt when it is done, e.g. 403S, which is 403 seconds. Send me the serial number, file name, and time in seconds. Notes: 1. free memory with no activities running is up around the 40 MB mark. Browse running leaves 16 MB free. Activity startup time is much reduced, and reduced still further when the pulsing icon animation is switched from 10 times a second to twice a second. The animation is stealing resources! On the other hand, the spinning cursor during startup or in Browse consumes no significant resources. http://dev.laptop.org/~quozl/z/1YdW4T.txt shows the change. -- James Cameron http://quozl.linux.org.au/ ___ Sugar-devel mailing list sugar-de...@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel -- Gonzalo Odiard SugarLabs - Software for children learning ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Sugar-devel] XO-1 vs Sugar 0.104 performance, and swap to NAND Flash
Activity startup time is much reduced, and reduced still further when the pulsing icon animation is switched from 10 times a second to twice a second. The animation is stealing resources! On the other hand, the spinning cursor during startup or in Browse consumes no significant resources. http://dev.laptop.org/~quozl/z/1YdW4T.txt shows the change. Hmm, good catch, I will try with different numbers. Gonzalo -- James Cameron http://quozl.linux.org.au/ ___ Sugar-devel mailing list sugar-de...@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel -- Gonzalo Odiard SugarLabs - Software for children learning ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
XO-1 vs Sugar 0.104 performance, and swap to NAND Flash
With Sugar 0.98 in 13.2.1, the XO-1 was so short of memory that adding swap gave an obvious benefit. Thanks to those who have verified this for us. With Sugar 0.104 in 13.2.4, things seem much better on the XO-1, thanks to all the work done by Sugar Labs developers. But I'm not finished testing [1]. Meanwhile, there's an opportunity to add swap to jffs2 filesystem. The XO-1 NAND Flash is rated for 100,000 writes per cell. The jffs2 filesystem we use spreads the writes across all the cells. There's a risk that swapping to the NAND Flash will shorten the life of an XO-1. It may become slower at reading and writing journal entries. But they might already be so slow that this isn't a problem any more. What I need is some data from XO-1 that have been used a lot: how long does it take to reflash? To test, surround a copy-nand command with timing markers, like this: ok t-sec( copy-nand u:\32014o0.img )t-sec The result will be on the line above the ok prompt when it is done, e.g. 403S, which is 403 seconds. Send me the serial number, file name, and time in seconds. Notes: 1. free memory with no activities running is up around the 40 MB mark. Browse running leaves 16 MB free. Activity startup time is much reduced, and reduced still further when the pulsing icon animation is switched from 10 times a second to twice a second. The animation is stealing resources! On the other hand, the spinning cursor during startup or in Browse consumes no significant resources. http://dev.laptop.org/~quozl/z/1YdW4T.txt shows the change. -- James Cameron http://quozl.linux.org.au/ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Windows XP on XO-1, XO-1.5
Windows XP on the XO-1 loads and works just about the same as on any other machine. Microsoft did the implementation, primarily by replacing Open Firmware with Insyde BIOS, a standard proprietary x86 PC BIOS. There’s nothing you’d learn from it that you wouldn’t learn from studying XP booting on any other PC. Windows XP on XO-1.5 was made available in a dual-boot configuration, supporting Sugar and XP. That work was done by OLPC, mainly by Mitch Bradley and me, and the system booted from Open Firmware. The Open Firmware work consisted of adding support for required PC BIOS interfaces, and much of the rest of the technical work involved supporting Microsoft’s modifications to allow XP to be booted from removable media (a card in the external SD slot). Microsoft did not support booting XP from removable media, and at the time the XO-1.5 was the only machine that could do so - as far as I know, that’s still the case. But there is nothing to learn there other than how Mitch and I implemented Microsoft’s cryptic and often unhelpful suggestions to get it to work. In particular, XP on the XO-1.5 is locked to a specific SD card signature so no other make and/or model of SD card would boot. Reasonable effort went into that fairly useless exercise. And as Paul says, in each case these machines were made available for initial trials by a specific customer and were never generally available or widely produced. - Ed On Jan 27, 2015, at 2:08 PM, Paul Fox p...@laptop.org wrote: please post messages with descriptive subject lines. lucia wrote: Hi: I subscribe to Mike's question. Don't hate me people, but I am also interested in finding a copy of Windows XP for XO-1 to try and learn about how it works and loads on the XO. Thanks, windows for the XO-1 was never publicly available, and was never deployed beyond initial trials by the customer who wanted it. Furthermore, (sorry for the pro's here): I understand that Sugar GUI sits on top of Linux OS, but if somebody wants to develop something in a Windows 8.1 environment (I'm not a converted to Microsoft or any other OS), does he/she have to go back to the command line? i don't really understand the question, but if you want to know how to do sugar development on non-OLPC platforms, you should ask on the sugar mailing list: http://lists.sugarlabs.org/listinfo/sugar-devel paul =- paul fox, p...@laptop.org ___ 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
xo-1
are all xo-1 multi colored on the back ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: xo-1
Some of the beta units (B1s) are not multicolored. -walter On Sat, Nov 8, 2014 at 1:38 PM, Jhon Diaz linuxs...@gmail.com wrote: are all xo-1 multi colored on the back ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel -- Walter Bender Sugar Labs http://www.sugarlabs.org ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
ubuntu xo-1
as i speak ubuntu trusty for xo-1 is being bulti debootstrap alsa how do i tar it and where do i upload the tarball ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: ubuntu xo-1
On 11/8/14, Jhon Diaz linuxs...@gmail.com wrote: as i speak ubuntu trusty for xo-1 is being bulti debootstrap alsa how do i tar it and where do i upload the tarball bump ooops it failed cannot run mount with mount maybe 13.10 13.04 12.04 or higher ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
end of a XO-1
I hope this isn't completely off topic for this list. My idea is that posting this report here might be useful to someone in the future searching for related information. Back in 2008 I bricked my XO-1 B2 (128MB) machine by upgrading to a firmware that was incompatible with it. The original firmware didn't have the commands needed to boot SqueakNOS and I wanted to play with that system. I downloaded the needed software (spiflash.dic) and firmware (q2c27.rom) to fix the problem and opened up the machine. The serial connector CN24 was missing, but I made a five wire cable from an old floppy cable and my brother-in-law, Fred, carefully soldered the wires to the missing connector's solder pads on the board. The plan was to use the IDC connector at the other end of the cable to connect to a Xilinx ML401 FPGA development board configured as a serial adaptor. I was using the FPGA board for another project and only got around to trying to fix the XO-1 last week. The XO-1 was also missing the Recovery Mode Jumper Block (CN31) so my father taped a small piece of metal shorting all four solder blobs. I checked that the FPGA was generating 65MHz for the EC chip and using a serial terminal application on the PC I could see that characters typed on the PC keyboard were reaching CN24 on the laptop. Plugging in the laptop's power brick (with no batteries) made the message 213423:SCI:40 appear in the terminal application (the first number wasn't exactly that and changed a little each time - it was some kind of time stamp). Unplugging caused a similar message. Eventually I noticed that pin 1 of CN24 is supposed to be 3.3V from the laptop to the serial board and not from the serial board like I had thought. I reconfigured the FPGA to stop sending 3.3V on that pin and now the message would only appear when plugging in the laptop and random noise when unplugging. Pressing the power button generated about five more messages and then a crlfM heartbeat message every two seconds or so. Running ./forth spiflash.dic didn't yield the desired results because the program thought that 0x0d was the SPI FLASH ID, which was invalid. Trying more times would get 0x0a, 0x4d and back to 0x0d as IDs, all invalid. I suspected that the KB3700 was operating in normal mode instead of ISP (programming) mode. So I removed the metal short from the solder blobs at CN31 and verified that two of the diagonal pins were ground (I got about 1 ohm) and the two opposite diagonals were KB3700 pins (about 100 ohms to ground). I expect these would be TP_ISP_MODE (pin 54) and TP_CLK_TEST (pin 48). Without the short the behavior was exactly the same as before. We tried to use two screwdrivers instead as short circuits but couldn't get anything that looked like an ISP mode. At one point the laptop failed to turn on and the EC chip no longer sent any messages to the PC. The 12V from the power brick was still good and the 65MHz from the FPGA board was the same as before. It is very likely that the EC died, though it could also be some part of the internal power supply. We unsoldered the cable and closed up the machine. It can still be a nice static display in some museum. I can think of two possibilities for the failure to program the ISP flash. The first is that the EC chip was not in ISP mode. Given how hard we had to poke the solder blobs with the multimeter probe to see which ones were supposed to be ground it is likely that there was a layer of something on top of the blobs (even though they still look shiny) that was causing bad contacts. The alternative is that the EC wasn't receiving commands from the PC because of the 65MHz ripple on the RX line. It looked pretty bad on the oscilloscope (nearly 1V peak to peak) but serial ports are sometimes surprisingly robust. -- Jecel ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: end of a XO-1
Thanks, very interesting. Quite true that SPI FLASH reprogramming of XO-1 B2 is a challenge. We would normally replace the SPI FLASH chip with a freshly programmed one. The SCI text you saw was the EC serial port explaining what it was sending the host over the SCI channel. I agree it sounds like the EC is now dead, perhaps ESD, or the output stage of the relevant pin has failed. -- James Cameron http://quozl.linux.org.au/ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [support-gang] Firefox won't install on XO-1/Gnome; other options?
Sent from my currently functioning gadget Original Message From: James Cameron Sent: Friday, September 12, 2014 00:37 To: Kevin Gordon Gmail Cc: support-g...@lists.laptop.org; OLPC Devel Subject: Re: [support-gang] Firefox won't install on XO-1/Gnome; other options? On Thu, Sep 11, 2014 at 11:59:17PM -0400, Kevin Gordon Gmail wrote: On an xo-1, using the official 12.1 from download.laptop.org as a base, I am able to successfully yum install firefox with the 2 new dependencies (fedora-bookmarks, xulrunner) and 7 updates - mostly nss* modules). FF works fine with the Google and Gmail sites. That version of Firefox (13.0-1.fc17) is very old, and has security vulnerabilities. Do not let anybody use it. https://www.mozilla.org/security/known-vulnerabilities/firefox.html The version that installed using 'yum install' is 22.0-1.fc17. Perhaps the update repo contains a newer version? Also, speaking selfishly, I don't think our specific deployments can keep up with that almost weekly update cycle from mozilla. Besides chewing bandwidth, the new updates sometimes break stuff:-). I think one needs to evaluate the probability of someone actually being susceptible on the attack vector when using fedora 17/crippled flash in concert with ff. Everyone needs to do their own plan, risks, costs, needs. For example, if one needs to run google search on 12.1, there will be some compromise made somewhere. For example, neither firefox nor opera use the journal. -- James Cameron http://quozl.linux.org.au/ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [support-gang] Firefox won't install on XO-1/Gnome; other options?
Firefox has a lot of dependencies, it has to bring the whole xulrunner thing back, so the out of space may be disk, not memory Sent from my currently functioning gadget Original Message From: Sebastian Silva Sent: Thursday, September 11, 2014 20:47 To: Community Support Volunteers -- who help respond to help AT laptop.org Reply To: Community Support Volunteers -- who help respond to help AT laptop.org Cc: Community Support Volunteers -- who help respond to help AT laptop.org Subject: Re: [support-gang] Firefox won't install on XO-1/Gnome; other options? Hi, This is because by default /tmp is only 50mb on XO1. Yum is a real memory hog. What I do as a temporal fix is: mount -o remount,size=200m /tmp I second James's discouragement of using private lists to give public support. Regards, Sebastian El jue, 11 de sep 2014 a las 7:36 PM, Adam Holt h...@laptop.org escribió: Great rpmdropbox.laptop.org is back live, consequently yum install firefox proceeded much further. Then, after filling up over 50MB it quit complaining about insufficient space. df -u showed 958MB on /. Browsers (incl Gnome's) continue to crash the moment Sean tries gmail.com and similar sites. George, What should Sean remove from the XO-1 and how, to create space, allowing completion of this Firefox test if you believe this is still valuable? On Thu, Sep 11, 2014 at 6:04 PM, James Cameron qu...@laptop.org wrote: On Thu, Sep 11, 2014 at 02:03:27PM -0400, Adam Holt wrote: Sean Collins our new volunteer heading to Haiti in 10 days is trying to get a working browser for the many XO-1s in Haiti now unable to use Google. Given others have reported further change that made Google work again, it would be worth testing again before heading to Haiti. He'd like to try Firefox on HaitiOS 0.7.1 (a much-patched derivative of OLPC OS 12.1.0) now ubiquitious around Haiti, but gets No more mirrors to try error messages like: [Errno 12] Timeout on [1]http://rpmdropbox.laptop.org/f17/repodata/ repomd.xml: (28, '') Trying another mirror. Error: failure: repodata/repomd.xml from olpc-f17: [Errno 256] No more mirrors to try. Any other options or workarounds until [2]rpmdropbox.laptop.org is fixed? Now that they are available again, you might make a copy of the repositories of interest, both rpmdropbox.laptop.org and mock.laptop.org, so that you can have a plan next time there is a brief outage. This is something we anticipate any deployment would do in order to avoid an ongoing dependency on our servers. You might also temporarily remove the failed repository from /etc/yum.repos.d Please ensure Sean is subscribed to devel@ where technical discussions are best undertaken. It pisses me off to hide useful solutions on a private list, and I'm very uninclined to waste my time on private lists going forward. -- James Cameron http://quozl.linux.org.au/ ___ support-gang mailing list support-g...@lists.laptop.org http://lists.laptop.org/listinfo/support-gang -- Unsung Heroes of OLPC, interviewed live @ http://unleashkids.org ! ___ support-gang mailing list support-g...@lists.laptop.org http://lists.laptop.org/listinfo/support-gang ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [support-gang] Firefox won't install on XO-1/Gnome; other options?
On an xo-1, using the official 12.1 from download.laptop.org as a base, I am able to successfully yum install firefox with the 2 new dependencies (fedora-bookmarks, xulrunner) and 7 updates - mostly nss* modules). FF works fine with the Google and Gmail sites. Sent from my currently functioning gadget Original Message From: James Cameron Sent: Thursday, September 11, 2014 21:12 To: Community Support Volunteers -- who help respond to help AT laptop.org Reply To: Community Support Volunteers -- who help respond to help AT laptop.org Subject: Re: [support-gang] Firefox won't install on XO-1/Gnome; other options? On Thu, Sep 11, 2014 at 08:36:25PM -0400, Adam Holt wrote: Great [1]rpmdropbox.laptop.org is back live, consequently yum install firefox proceeded much further. Then, after filling up over 50MB it quit complaining about insufficient space. df -u showed 958MB on /. Browsers (incl Gnome's) continue to crash the moment Sean tries [2]gmail.com and similar sites. Easier to make a new XO-1 build using olpc-os-builder that already has firefox in it, than to deal with all the things that have to be done to bolt it on later. -- James Cameron http://quozl.linux.org.au/ ___ support-gang mailing list support-g...@lists.laptop.org http://lists.laptop.org/listinfo/support-gang ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [support-gang] Firefox won't install on XO-1/Gnome; other options?
On Thu, Sep 11, 2014 at 11:59:17PM -0400, Kevin Gordon Gmail wrote: On an xo-1, using the official 12.1 from download.laptop.org as a base, I am able to successfully yum install firefox with the 2 new dependencies (fedora-bookmarks, xulrunner) and 7 updates - mostly nss* modules). FF works fine with the Google and Gmail sites. That version of Firefox (13.0-1.fc17) is very old, and has security vulnerabilities. Do not let anybody use it. https://www.mozilla.org/security/known-vulnerabilities/firefox.html -- James Cameron http://quozl.linux.org.au/ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: WebKit uses SSE XMM and breaks on XO-1
Hi James, On Sat, Aug 23, 2014 at 7:05 AM, James Cameron qu...@laptop.org wrote: With recent changes to Google Search JavaScript, searching terminates Browse with a SIGSEGV, in WTF::dtoa. http://bugs.sugarlabs.org/ticket/4785 This is only seen on an XO-1, in 13.2.1, 13.2.0, all the way back to 12.1.0. It is not seen on more recent XO laptops. On Fedora 20, with Sugar 0.102, and Browse-156, on kernel 3.10, does similar, but the failure is SIGILL. Using gdb we find the failing instructions are references to XMM registers: 0xabeda509: mov0x4(%eax),%ebx 0xabeda50c: cmp-0x8(%ebx),%ecx 0xabeda50f: jae0xabedbcde = 0xabeda515: movsd (%ebx,%ecx,8),%xmm0= 0xabeda51a: ucomisd %xmm0,%xmm0 0xabeda51e: jp 0xabedbcde 0xabeda524: movd %xmm0,%eax The XO-1 with AMD Geode processor does not have these registers, so the SIGILL is valid. So it would seem one way to fix this may be to rebuild WebKit without this instruction stream. But first, I want to make sure I can rebuild WebKit. I've tried on a Fedora 20 system to do this: yumdownloader --source webkitgtk3 rpmrebuild --rebuild webkitgtk3-1.10.2-3.fc18.src.rpm But it fails with this: libtool: link: gcc -o /root/rpmbuild/BUILD/webkitgtk-1.10.2/tmp-introspectHnbXap/.libs/WebKit-3.0 -O2 -g1 -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m32 -march=i686 -mtune=atom -fasynchronous-unwind-tables -DLIBSOUP_I_HAVE_READ_BUG_594377_AND_KNOW_SOUP_PASSWORD_MANAGER_MIGHT_GO_AWAY -O2 -Wl,-z -Wl,relro /root/rpmbuild/BUILD/webkitgtk-1.10.2/tmp-introspectHnbXap/WebKit-3.0.o -Wl,--export-dynamic -pthread -Wl,--export-dynamic -L. /root/rpmbuild/BUILD/webkitgtk-1.10.2/.libs/libwebkitgtk-3.0.so /root/rpmbuild/BUILD/webkitgtk-1.10.2/.libs/libjavascriptcoregtk-3.0.so -lgmodule-2.0 -lrt -lgtk-3 -lgdk-3 -latk-1.0 -lpangocairo-1.0 -lgdk_pixbuf-2.0 -lcairo-gobject -lpango-1.0 -lcairo -lsoup-2.4 -lgio-2.0 -lgobject-2.0 -lglib-2.0 -pthread /lib/libGL.so.1: undefined reference to `_glapi_tls_Dispatch' /lib/libEGL.so.1: undefined reference to `wl_display_dispatch_queue_pending' collect2: error: ld returned 1 exit status linking of temporary binary failed: Command '['./doltlibtool', '--mode=link', '--tag=CC', 'gcc', '-o', '/root/rpmbuild/BUILD/webkitgtk-1.10.2/tmp-introspectHnbXap/WebKit-3.0', '-export-dynamic', '-O2', '-g1', '-pipe', '-Wall', '-Wp,-D_FORTIFY_SOURCE=2', '-fexceptions', '-fstack-protector', '--param=ssp-buffer-size=4', '-m32', '-march=i686', '-mtune=atom', '-fasynchronous-unwind-tables', '-DLIBSOUP_I_HAVE_READ_BUG_594377_AND_KNOW_SOUP_PASSWORD_MANAGER_MIGHT_GO_AWAY', '-O2', '-Wl,-z,relro', '/root/rpmbuild/BUILD/webkitgtk-1.10.2/tmp-introspectHnbXap/WebKit-3.0.o', '-L.', '-lwebkitgtk-3.0', '-ljavascriptcoregtk-3.0', '-Wl,--export-dynamic', '-pthread', '-lgmodule-2.0', '-lrt', '-lgtk-3', '-lgdk-3', '-latk-1.0', '-lpangocairo-1.0', '-lgdk_pixbuf-2.0', '-lcairo-gobject', '-lpango-1.0', '-lcairo', '-lsoup-2.4', '-lgio-2.0', '-lgobject-2.0', '-lglib-2.0']' returned non-zero exit status 1 make[1]: *** [WebKit-3.0.gir] Error 1 make[1]: Leaving directory `/root/rpmbuild/BUILD/webkitgtk-1.10.2' make: *** [all] Error 2 error: Bad exit status from /var/tmp/rpm-tmp.vGFtGZ (%build) I wonder if that's due to a newer mesa, I can have a look, or review/push any package updates needed to Fedora to fix this. Let me know how I can help fix this. Peter ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: WebKit uses SSE XMM and breaks on XO-1
On Mon, Aug 25, 2014 at 12:22:20PM +0100, Peter Robinson wrote: Hi James, On Sat, Aug 23, 2014 at 7:05 AM, James Cameron qu...@laptop.org wrote: With recent changes to Google Search JavaScript, searching terminates Browse with a SIGSEGV, in WTF::dtoa. http://bugs.sugarlabs.org/ticket/4785 This is only seen on an XO-1, in 13.2.1, 13.2.0, all the way back to 12.1.0. It is not seen on more recent XO laptops. On Fedora 20, with Sugar 0.102, and Browse-156, on kernel 3.10, does similar, but the failure is SIGILL. Using gdb we find the failing instructions are references to XMM registers: 0xabeda509: mov0x4(%eax),%ebx 0xabeda50c: cmp-0x8(%ebx),%ecx 0xabeda50f: jae0xabedbcde = 0xabeda515: movsd (%ebx,%ecx,8),%xmm0= 0xabeda51a: ucomisd %xmm0,%xmm0 0xabeda51e: jp 0xabedbcde 0xabeda524: movd %xmm0,%eax The XO-1 with AMD Geode processor does not have these registers, so the SIGILL is valid. So it would seem one way to fix this may be to rebuild WebKit without this instruction stream. But first, I want to make sure I can rebuild WebKit. I've tried on a Fedora 20 system to do this: yumdownloader --source webkitgtk3 rpmrebuild --rebuild webkitgtk3-1.10.2-3.fc18.src.rpm But it fails with this: libtool: link: gcc -o /root/rpmbuild/BUILD/webkitgtk-1.10.2/tmp-introspectHnbXap/.libs/WebKit-3.0 -O2 -g1 -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m32 -march=i686 -mtune=atom -fasynchronous-unwind-tables -DLIBSOUP_I_HAVE_READ_BUG_594377_AND_KNOW_SOUP_PASSWORD_MANAGER_MIGHT_GO_AWAY -O2 -Wl,-z -Wl,relro /root/rpmbuild/BUILD/webkitgtk-1.10.2/tmp-introspectHnbXap/WebKit-3.0.o -Wl,--export-dynamic -pthread -Wl,--export-dynamic -L. /root/rpmbuild/BUILD/webkitgtk-1.10.2/.libs/libwebkitgtk-3.0.so /root/rpmbuild/BUILD/webkitgtk-1.10.2/.libs/libjavascriptcoregtk-3.0.so -lgmodule-2.0 -lrt -lgtk-3 -lgdk-3 -latk-1.0 -lpangocairo-1.0 -lgdk_pixbuf-2.0 -lcairo-gobject -lpango-1.0 -lcairo -lsoup-2.4 -lgio-2.0 -lgobject-2.0 -lglib-2.0 -pthread /lib/libGL.so.1: undefined reference to `_glapi_tls_Dispatch' /lib/libEGL.so.1: undefined reference to `wl_display_dispatch_queue_pending' collect2: error: ld returned 1 exit status linking of temporary binary failed: Command '['./doltlibtool', '--mode=link', '--tag=CC', 'gcc', '-o', '/root/rpmbuild/BUILD/webkitgtk-1.10.2/tmp-introspectHnbXap/WebKit-3.0', '-export-dynamic', '-O2', '-g1', '-pipe', '-Wall', '-Wp,-D_FORTIFY_SOURCE=2', '-fexceptions', '-fstack-protector', '--param=ssp-buffer-size=4', '-m32', '-march=i686', '-mtune=atom', '-fasynchronous-unwind-tables', '-DLIBSOUP_I_HAVE_READ_BUG_594377_AND_KNOW_SOUP_PASSWORD_MANAGER_MIGHT_GO_AWAY', '-O2', '-Wl,-z,relro', '/root/rpmbuild/BUILD/webkitgtk-1.10.2/tmp-introspectHnbXap/WebKit-3.0.o', '-L.', '-lwebkitgtk-3.0', '-ljavascriptcoregtk-3.0', '-Wl,--export-dynamic', '-pthread', '-lgmodule-2.0', '-lrt', '-lgtk-3', '-lgdk-3', '-latk-1.0', '-lpangocairo-1.0', '-lgdk_pixbuf-2.0', '-lcairo-gobject', '-lpango-1.0', '-lcairo', '-lsoup-2.4', '-lgio-2.0', '-lgobject-2.0', '-lglib-2.0']' returned non-zero exit status 1 make[1]: *** [WebKit-3.0.gir] Error 1 make[1]: Leaving directory `/root/rpmbuild/BUILD/webkitgtk-1.10.2' make: *** [all] Error 2 error: Bad exit status from /var/tmp/rpm-tmp.vGFtGZ (%build) I wonder if that's due to a newer mesa, I can have a look, or review/push any package updates needed to Fedora to fix this. Let me know how I can help fix this. Thanks. I guess you're saying dependent packages are not tested for rebuildabillity when a package is released for update. Would using mock have avoided this? mesa package versions present in the builder are mesa-libEGL-10.1.5-1.20140607.fc20.i686 mesa-libEGL-devel-10.1.5-1.20140607.fc20.i686 mesa-libgbm-10.1.5-1.20140607.fc20.i686 mesa-libGL-10.1.5-1.20140607.fc20.i686 mesa-libglapi-10.1.5-1.20140607.fc20.i686 mesa-libGL-devel-10.1.5-1.20140607.fc20.i686 full list at http://dev.laptop.org/~quozl/z/1XM1IG.txt -- James Cameron http://quozl.linux.org.au/ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: 13.2.1 for XO-1 using external SD card slot
On Fri, Jun 20, 2014 at 09:39:32AM +1000, James Cameron wrote: You need an XO-1, an SD card of 4GB or more, a USB drive of 1GB, and a download of 585 MB. http://wiki.laptop.org/go/11233 has the instructions. The zip file there has been refreshed following the 13.2.1 release, and now contains the signed release. 750bdd1fccc7f1fcf884b1a85de47f64 32014o0.zip (old) e6dd46458d51e1ca2b543b47a4e421c2 32014o0.zip (new) -- James Cameron http://quozl.linux.org.au/ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: 13.2.1 for XO-1 using external SD card slot
On Fri, Jun 20, 2014 at 09:39:32AM +1000, James Cameron wrote: Therefore using an SD card instead of NAND flash should increase I/O performance, decrease processor time, and increase available memory. I've measured the increase in available memory. With the laptop freshly booted at the activity view and the journal icon coloured, a program is run that consumes memory in order to determine how much is available; - moving the root filesystem from NAND to SDIO is a 7% gain, from 146 MB to 156 MB, - leaving the root filesystem on NAND and adding 64 MB swap on SDIO is a 31% gain, from 146 MB to 191 MB, - moving the root filesystem from NAND to SDIO and adding 64 MB swap on SDIO is a 41% gain, from 146 MB to 206 MB. A visualisation of the results: https://plot.ly/~quozl/7/xo-1-256-mb-usable-memory-1321-nand-vs-sdio-as-root/ The test program: http://dev.laptop.org/~quozl/z/1WyA0M.txt (oom.c) Measurement was the anon-rss in the kernel OOM message, e.g. [ 761.307460] Killed process 937 (oom) total-vm:197692kB, anon-rss:183048kB, file-rss:4kB -- James Cameron http://quozl.linux.org.au/ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
13.2.1 for XO-1 using external SD card slot
Announcing an unsigned early build of 13.2.1 for XO-1 using external SD card slot. The XO-1 has 1GB of NAND flash with jffs2 filesystem. After many years of service the NAND flash will have slowed down [1]. The XO-1 has a 433 MHz Geode processor. The processor is used to compress and decompress data stored on NAND flash. The XO-1 has 256 MB of RAM. 11 MB is consumed by jffs2 filesystem log structure. During read and write, extra memory is used temporarily for compress and decompress. The XO-1 has an external SD card slot. Some don't work well, but most do. SD cards have increased in performance, increased in capacity, and decreased in cost. Therefore using an SD card instead of NAND flash should increase I/O performance, decrease processor time, and increase available memory. Would you like to try it? You need an XO-1, an SD card of 4GB or more, a USB drive of 1GB, and a download of 585 MB. http://wiki.laptop.org/go/11233 has the instructions. This build is 13.2.0 plus new firmware, plus new kernel with wireless fixes, plus driver for new camera, and packaged for use with an SD card, not internal NAND flash. The NAND flash is not touched. Do not remove the card while the laptop is running. The laptop will hang if the card is removed. The data on the card may be damaged. In testing so far, this build boots a little bit faster than 13.2.0. Measurement methods suggested: 1. subsequent boot time to journal ready, (boot first time, enter name, select colour, wait for journal icon to colour, shutdown, press power button and begin timing, wait for the journal icon to colour and end timing). 2. initial startup time for Browse activity, (boot once, open Browse, quit Browse, reboot, wait for journal icon to colour, switch to journal, start Browse journal entry and begin timing, wait for rendering and end timing, quit Browse), 3. subsequent startup time for Browse activity, (prepare as above, then start Browse journal entry and begin timing, wait for rendering and end timing, quit Browse) A further performance gain is to add a swap file to the SD card, which in my tests using Sugar can free up to another 30 MB. -- Footnote: 1. no analysis is available for how much slow down has happened, but a timing of scan-nand and copy-nand firmware commands should be an effective measure: ok t( scan-nand )t press the escape key while the scan is in progress, then read off the result in milliseconds, ok t( copy-nand u:\32013o0.img )t note this destroys all data on the laptop. -- James Cameron http://quozl.linux.org.au/ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [support-gang] SD Sugar boot for XO-1
On Wed, May 14, 2014 at 6:56 PM, James Cameron qu...@laptop.org wrote: On Wed, May 14, 2014 at 11:57:31AM +, tkk...@nurturingasia.com wrote: Is there a complete step by setp quick instruction that I can create a SD card that will boot Sugar for XO-1 machines? I am happy SD card deployment running on XO 1.75 and felt maybe I could do the same for the older machines. No, there is no such guide. It is possible to do, but nobody has written a guide. I did ask for help on this on 9th December on support-gang@, but no material help emerged. I include the posting below signature. The expertise required include Fedora operating system early boot and the dracut initramfs builder. devel@ mailing list contains this expertise, support-gang@ has far fewer. Indeed, I don't know anything about dracut. But it occurs to me that the mktinycore tool James, Yiryous, and Jerry worked on might offer another model for getting the XO1 image running on an SD card. Jerry's bind mounting onto the mother board, and then chrooting into it might also work for the external SD card. With so many XO1's out there, it might really be helpful, and strategic, to be able to have more that 1 GB storage. I guess we might not know for a while how many XO1's are unreliable, when running off of an SD card, until we try it. The external SD slot is not as reliable on the XO-1 as it is on later models, so you might find some XO-1 that won't work with it. A quick demonstration of external SD slot booting can be made by copying the boot folder from a Tiny Core Linux USB drive to an SD card. -- James Cameron http://quozl.linux.org.au/ Date: Mon, 9 Dec 2013 16:20:30 +1100 From: James Cameron qu...@laptop.org To: support-g...@lists.laptop.org Subject: Wanted: XO-1 boot from external SD Hyoomin on IRC #olpc asked about installing OLPC OS on external SD card on an XO-1. This would allow easer re-use of still working XO-1 laptops for people willing to put up with their low performance and old age cranky habits. I could be wrong, but as far as I know this doesn't work, but could be made to work with some engineering effort. If I am wrong, please say how you did it, so it can be documented on the Wiki. Technical stuff: the key to the problem seems to be the initramfs which has a file olpc-boot-cmdline.sh that doesn't have an entry for the XO-1 external SD slot. http://dev.laptop.org/git/users/dsd/dracut-modules-olpc/tree/30olpc-boot/olpc-boot-cmdline.sh ___ support-gang mailing list support-g...@lists.laptop.org http://lists.laptop.org/listinfo/support-gang ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [support-gang] SD Sugar boot for XO-1
On Thu, May 15, 2014 at 07:32:49AM -0400, George Hunt wrote: Indeed, I don't know anything about dracut. It doesn't look that hard. It's mostly just shell script. Then something like mkinitramfs is used. But it occurs to me that the mktinycore tool James, Yiryous, and Jerry worked on might offer another model for getting the XO1 image running on an SD card. Yes, as a method for making a card filesystem. There's also the Linux which is usually in the NAND FLASH of the XO-1. With a bit of work, an Open Firmware script could also write the filesystem from USB. It's just that it isn't there ready to go like it is with XO-1.5 and later. -- James Cameron http://quozl.linux.org.au/ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
SD on XO-1
georgejh...@gmail.com said: With so many XO1's out there, it might really be helpful, and strategic, to be able to have more that 1 GB storage. I guess we might not know for a while how many XO1's are unreliable, when running off of an SD card, until we try it. I have an XO-1 that was setup to reboot every 4 hours. and mount an SD card. It didn't get a lot of use, but it did test the reboot process and make sure the WiFi worked. The only problems I ever saw was that it would occasionally hang during boot because Linux couldn't talk to the SD card. It was printing out a timeout message every second or two. There was a short pause between messages. I assumed it was a quirk in the firmware setup. I'll try to collect some data if somebody wants to chase this. -- These are my opinions. I hate spam. ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: SD on XO-1
That sounds like it. I saw the same on a laptop set up as a motion camera with SD card for the image storage. I seem to recall the problem is electrical, and so the impact varies across the population of XO-1. There isn't a quirk in the firmware setup. A quirk might be placed in the Linux driver to reset the card. On Thu, May 15, 2014 at 01:19:28PM -0700, Hal Murray wrote: georgejh...@gmail.com said: With so many XO1's out there, it might really be helpful, and strategic, to be able to have more that 1 GB storage. I guess we might not know for a while how many XO1's are unreliable, when running off of an SD card, until we try it. I have an XO-1 that was setup to reboot every 4 hours. and mount an SD card. It didn't get a lot of use, but it did test the reboot process and make sure the WiFi worked. The only problems I ever saw was that it would occasionally hang during boot because Linux couldn't talk to the SD card. It was printing out a timeout message every second or two. There was a short pause between messages. I assumed it was a quirk in the firmware setup. I'll try to collect some data if somebody wants to chase this. -- These are my opinions. I hate spam. -- James Cameron http://quozl.linux.org.au/ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: SD Sugar boot for XO-1
On Wed, May 14, 2014 at 11:57:31AM +, tkk...@nurturingasia.com wrote: Is there a complete step by setp quick instruction that I can create a SD card that will boot Sugar for XO-1 machines? I am happy SD card deployment running on XO 1.75 and felt maybe I could do the same for the older machines. No, there is no such guide. It is possible to do, but nobody has written a guide. I did ask for help on this on 9th December on support-gang@, but no material help emerged. I include the posting below signature. The expertise required include Fedora operating system early boot and the dracut initramfs builder. devel@ mailing list contains this expertise, support-gang@ has far fewer. The external SD slot is not as reliable on the XO-1 as it is on later models, so you might find some XO-1 that won't work with it. A quick demonstration of external SD slot booting can be made by copying the boot folder from a Tiny Core Linux USB drive to an SD card. -- James Cameron http://quozl.linux.org.au/ Date: Mon, 9 Dec 2013 16:20:30 +1100 From: James Cameron qu...@laptop.org To: support-g...@lists.laptop.org Subject: Wanted: XO-1 boot from external SD Hyoomin on IRC #olpc asked about installing OLPC OS on external SD card on an XO-1. This would allow easer re-use of still working XO-1 laptops for people willing to put up with their low performance and old age cranky habits. I could be wrong, but as far as I know this doesn't work, but could be made to work with some engineering effort. If I am wrong, please say how you did it, so it can be documented on the Wiki. Technical stuff: the key to the problem seems to be the initramfs which has a file olpc-boot-cmdline.sh that doesn't have an entry for the XO-1 external SD slot. http://dev.laptop.org/git/users/dsd/dracut-modules-olpc/tree/30olpc-boot/olpc-boot-cmdline.sh ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: SD Sugar boot for XO-1
Why exclude devel@? Re-added. On Wed, May 14, 2014 at 10:30:53PM -0400, Nathan C. Riddle wrote: TK, I have tried to follow the thread on Boot Menu on XO. Have you gone beyond the boot int:x and boot ext:x to use internal or external SD ? Open Firmware will boot from any media present; it tries USB first, then external SD card slot, then whatever the internal storage is. If this is still the simple case, I am missing why this is not possible on an unlocked XO-1 . It is possible, but it does not work, because it was never completed during development. The installation on the SD is same (?): devalias fsdisk ext:0 fs-update u:\nameoftheimage.zd No, the installation on SD card would have to be entirely different, because an XO-1 lacks fsdisk and fs-update. Is boot ext:x not available in XO-1 firmware ? (x is \boot\olpc.fth) Manual boot from SD card is available on XO-1 firmware, but it is not needed, because Open Firmware will boot from any media present. I have recently installed on XO-1.5 , 13.2.0 on SD (class 10) with Firefox and Flash (per Jame's fine posts here). (The erase step on SD appears to be almost twice as fast on this faster card versus internal card.) Reasonable Flash performance. These faster cards (8 GB) are under $10 at the local WalMart. :) There is no erase step per se. You're seeing the write step, and the card may have been pre-erased. Next time you do this it will be slower. Yes, modern cards can be quite fast. Look for one with a specified write speed designed for video recording, and it might increase the performance of the whole system. -- James Cameron http://quozl.linux.org.au/ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [support-gang] [XSCE] Using a wifi dongle on an XO-1(.5) -- another dongle
XSCE usually finds the correct device names based on role (gateway/non-gateway ).Sent from my BlackBerry® PlayBook™www.blackberry.comFrom: "Nathan C. Riddle" nathanr...@charter.netTo: "Community Support Volunteers -- who help respond to help AT laptop.org" support-g...@lists.laptop.orgCC: "xsce-devel" xsce-de...@googlegroups.com, "OLPC Devel" devel@lists.laptop.org, "Community Support Volunteers -- who help respond to help AT laptop.org" support-g...@lists.laptop.orgSent: 1 May, 2014 3:56 PMSubject: Re: [support-gang] [XSCE] Using a wifi dongle on an XO-1(.5) -- another dongleFound another Ralink device that works: RT5370. Used exactly same instructions given by Anna (same .bin files). There seems to be a lot of low cost dongles based on this device. This was a "BG/N" from ebay for $5. This was a USB dongle replacement for failed wireless on early XO-1.5 (static discharge damage ?). Removed (unplugged) failed internal wireless. Linux drivers RT2800usb in kernels 3.0.0-12 (?) or later. This XO-1.5 had 13.2.0 installed, but should apply to 12.1.0 . Worked with second XO-1.5 (which had 11.3.0 installed) running Chat Activity.Also works on XO-1 (internal wireless intact) with 13.2.0 .Initially, I was distracted with info from google search about changing device id in udev.rules - proved unnecessary. The dongle is assigned to wlan0 . Now, is there a device based on Ralink chips to replace the internal Libertas wireless module ? :)Finally, will this XO-1.5 now function as an XSCE server (i.e, will wlan0 get properly reassigned to eth0).Using udev reassignment (persistent-net.rules) method used on 11.3.0's (2.?.? kernel) does not seem available on 13.2.0 .Nathan RiddleOn Sun, Feb 9, 2014 at 9:31 PM, Anna wrote: I've got another dongle - this one has the Ralink chipset. Just like the Atheros dongle, to get it to work on the XO-1 was just amatter of finding and downloading the firmware for it, then putting thefirmware into /lib/firmware.I'm on yet another XO-1 with a dead internal wifi chip, all that shows upnatively is loopback.Here's the lsusb output for the dongle:Bus 001 Device 004: ID 148f:3070 Ralink Technology, Corp. RT2870/RT3070Wireless AdapterGoogle quickly pointed me here:http://wireless.kernel.org/en/users/Drivers/rt2800usbI cloned the firmware repo:git clone git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.gitPoked around in the linux-firmware dir and found rt2870.bin andrt3070.bin. Cp'd those two files to /lib/firmware on the XO-1, insertedthe dongle, then checked out Network Neighborhood. Yep, saw AP circles.Powered up the other XO-1 with "broken" wifi I was playing with last night,the one with the Atheros dongle. Yep, the buddy icons show up in NetworkNeighborhood (since both devices are on the same LAN). Tested the chatactivity just to be completely sure Sugar collaboration over the LAN workswith dongles___ support-gang mailing list support-g...@lists.laptop.org http://lists.laptop.org/listinfo/support-gang ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Using a wifi dongle on an XO-1(.5) -- another dongle
On Sat, May 03, 2014 at 12:19:43AM -0400, Nathan C. Riddle wrote: I see an example at http://oxfordtec.com/us/wireless-adapters/usb-interface-minicard-wireless/sparklan-wper-172gn-802-11bgn-1t1r-usb-interface-mini-pci-express-half-size-module-ralink-rt5390u-minicard-soc-solution.htm That link didn't work, but it was only a missing www prefix and l suffix: http://www.oxfordtec.com/us/wireless-adapters/usb-interface-minicard-wireless/sparklan-wper-172gn-802-11bgn-1t1r-usb-interface-mini-pci-express-half-size-module-ralink-rt5390u-minicard-soc-solution.html The datasheet link on that page is broken. An engineer working on integrating this module would need the datasheet, so that they can check the pinout. So, if USB pin location is not too different (near, on same side), might be possible (?). Yes. Might get lucky that there is a standard location of the USB pins. Yes. There's a great song by Daft Punk along those lines. Get Lucky. By possible, I mean pin-cut modified card used as workable replacement for (unavailable) Libertas in XO-1.5 . libertas is not the right term to use. It is the name of the kernel driver for the 8686 and the 8388. It is also the name of the Open Firmware driver for the 8388, 8686 and 8787. It might not require card changes, it might instead require main board changes. Certainly an exciting and challenging task that might not scale well. I note that the Ralink (and Atheros) drivers are in 12.1.0 and 13.2.0 (not in 11.3.1) and the rt2800usb.bin (for /lib/firmware/) can be obtained at http://wireless.kernel.org/en/users/Drivers/ (click on rt2800usb to download) and supported models are given in the Status link. ncr I also note two other devices with SDIO interface listed on the libertas driver Wiki page: http://wireless.kernel.org/en/users/Drivers/libertas -- James Cameron http://quozl.linux.org.au/ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Using a wifi dongle on an XO-1(.5) -- another dongle
On Thu, May 01, 2014 at 03:56:32PM -0400, Nathan C. Riddle wrote: Found another Ralink device that works: RT5370. [...] Now, is there a device based on Ralink chips to replace the internal Libertas wireless module ? :) No, certainly not. libertas kernel driver is used for the Marvell 88W8388 and 88W8686 based wireless modules. The XO-1 module, based on the 88W8388 chip, is not removable, and no other module is compatible. The XO-1.5, XO-1.75, and XO-4 modules, the 88W8686, are removable, but the only source of replacements is OLPC spare parts, and minimum order quantities make this impractical for you. And, if I'm reading the schematics right, there's also two voltage variants, so the modules for XO-1.5 (3.3V) can't be swapped with the modules for XO-1.75 and XO-4 (1.8V). The XO-1.5, XO-1.75, and XO-4 main board wireless socket is a Mini-PCIe connector, but the electrical interface is custom, and carries SDIO, wireless indicator LED, and wakeup signals, so any new module must be custom made for the hardware. You might break open a USB wireless adapter, attach to the USB connecting points at a socket, and glue it into the laptop in the space vacated by the original module. -- James Cameron http://quozl.linux.org.au/ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Using a wifi dongle on an XO-1(.5) -- another dongle
On May 1, 2014, at 6:32 PM, James Cameron wrote: On Thu, May 01, 2014 at 03:56:32PM -0400, Nathan C. Riddle wrote: Found another Ralink device that works: RT5370. [...] Now, is there a device based on Ralink chips to replace the internal Libertas wireless module ? :) No, certainly not. ... And, if I'm reading the schematics right, there's also two voltage variants, so the modules for XO-1.5 (3.3V) can't be swapped with the modules for XO-1.75 and XO-4 (1.8V). Only cards built before we added the ESD protection (very early in production) are limited to operation at +3.3V. Most of the cards used in XO-1.5 operate at either +3.3V or +1.8V, and are identical to the 88W8686 modules were used for XO-1.75 and XO-4. The XO-1.5, XO-1.75, and XO-4 main board wireless socket is a Mini-PCIe connector, but the electrical interface is custom, and carries SDIO, wireless indicator LED, and wakeup signals, so any new module must be custom made for the hardware. The miniPCIe form factor is frequently used for USB-based wireless cards as well, and XO laptops do provide USB signals at the appropriate pins although the shipped wireless card doesn't use it. Power, ground, and some auxiliary signals use standard pins. But we did reuse the actual PCIe signal pins to provide the SD interface so you might need to cut some wires to avoid conflict. The pinout is available at: http://wiki.laptop.org/images/d/d9/XO_4_Pinouts.pdf Cheers, wad ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Using a wifi dongle on an XO-1(.5) -- another dongle
On Thu, May 01, 2014 at 07:37:10PM -0400, John Watlington wrote: On May 1, 2014, at 6:32 PM, James Cameron wrote: On Thu, May 01, 2014 at 03:56:32PM -0400, Nathan C. Riddle wrote: Found another Ralink device that works: RT5370. [...] Now, is there a device based on Ralink chips to replace the internal Libertas wireless module ? :) No, certainly not. ... And, if I'm reading the schematics right, there's also two voltage variants, so the modules for XO-1.5 (3.3V) can't be swapped with the modules for XO-1.75 and XO-4 (1.8V). Only cards built before we added the ESD protection (very early in production) are limited to operation at +3.3V. Most of the cards used in XO-1.5 operate at either +3.3V or +1.8V, and are identical to the 88W8686 modules were used for XO-1.75 and XO-4. Thanks. The XO-1.5, XO-1.75, and XO-4 main board wireless socket is a Mini-PCIe connector, but the electrical interface is custom, and carries SDIO, wireless indicator LED, and wakeup signals, so any new module must be custom made for the hardware. The miniPCIe form factor is frequently used for USB-based wireless cards as well, and XO laptops do provide USB signals at the appropriate pins although the shipped wireless card doesn't use it. I couldn't prove they were connected, on the XO-1.5 schematic (Rev M), as the signal name didn't appear elsewhere. They are tied to the USB hub on XO-1.75 and XO-4. Power, ground, and some auxiliary signals use standard pins. But we did reuse the actual PCIe signal pins to provide the SD interface so you might need to cut some wires to avoid conflict. The pinout is available at: http://wiki.laptop.org/images/d/d9/XO_4_Pinouts.pdf Thanks. Are you aware of any replacement USB cards that have been made to work? -- James Cameron http://quozl.linux.org.au/ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Using a wifi dongle on an XO-1(.5) -- another dongle
On May 1, 2014, at 9:26 PM, James Cameron wrote: The miniPCIe form factor is frequently used for USB-based wireless cards as well, and XO laptops do provide USB signals at the appropriate pins although the shipped wireless card doesn't use it. I couldn't prove they were connected, on the XO-1.5 schematic (Rev M), as the signal name didn't appear elsewhere. On XO-1.5 it is connected to the VX855 USB port 5 (page 15). They are tied to the USB hub on XO-1.75 and XO-4. ... Are you aware of any replacement USB cards that have been made to work? Nope. wad ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Using a wifi dongle on an XO-1(.5) -- another dongle
On Thu, May 01, 2014 at 09:39:36PM -0400, John Watlington wrote: On May 1, 2014, at 9:26 PM, James Cameron wrote: I couldn't prove they were connected, on the XO-1.5 schematic (Rev M), as the signal name didn't appear elsewhere. On XO-1.5 it is connected to the VX855 USB port 5 (page 15). Thanks. My PDF reader didn't Find it, turns out to be WspaceL_USBP5 on page 15, and WL_USBP5 on page 24. -- James Cameron http://quozl.linux.org.au/ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Server-devel] [support-gang] 32(+) XO-1's on Mesh Potato 2 as AP on XSCE
As far as I know the implementation of ejabberd on xsce was a straight port from xs 0.7, so I wouldn't have expected a bug to have been introduced, but it is speculation either way. All we know is that what Nathan observes was not previously reported as a bug. Still, it is an annoyance. So the question is, what is the event that causes sugar to remove an icon from the NN and how does it arise. If it is a poll of ejabberd then we should investigate, regardless of whether it is a new bug or an old one. Date: Thu, 17 Apr 2014 15:09:16 +1000 From: qu...@laptop.org To: support-g...@lists.laptop.org Subject: Re: [support-gang] 32(+) XO-1's on Mesh Potato 2 as AP on XSCE On Thu, Apr 17, 2014 at 12:54:30AM -0400, Nathan C. Riddle wrote: Hopefully, later XSCE (ejabberd) version has corrected issue of falsely persistent icons in neighborhood. Not AP model related (same on TP Link). We don't know that this is an ejabberd problem yet, it could be a problem with Sugar. It would require deeper investigation. Any comments by XSCE development team ? You can write to them at xsce-de...@googlegroups.com There's also server-devel@lists.laptop.org -- James Cameron http://quozl.linux.org.au/ ___ support-gang mailing list support-g...@lists.laptop.org http://lists.laptop.org/listinfo/support-gang ___ Server-devel mailing list Server-devel@lists.laptop.org http://lists.laptop.org/listinfo/server-devel
Re: [Server-devel] 32(+) XO-1's on Mesh Potato 2 as AP on XSCE
As this is a question about Sugar, perhaps the Sugar developers should be involved. +CC sugar-devel@ Problem description: 32 XO-1 laptops are booted and registered to a school server, and all 32 icons are visible in neighbourhood, but the icons persist after any XO leaves. Sugar-0.96 (yes, really), on OLPC OS 12.1.0. Sorry, I don't know how the XO is being asked to leave; forced power off, shutdown request using power button, or shutdown using Sugar menu. This would be something to investigate. My experience is that a shutdown request using power button is similar in effect to typing shutdown -h now via sshd, and this leaves the SSH client stranded without the connection clearing down. Perhaps all that is required is time for the ejabberd connection to time out? Perhaps this is fixed in a later release of Sugar, and an upgrade or field change can be recommended? On Thu, Apr 17, 2014 at 06:58:40AM +, Tim Moody wrote: As far as I know the implementation of ejabberd on xsce was a straight port from xs 0.7, so I wouldn't have expected a bug to have been introduced, but it is speculation either way. All we know is that what Nathan observes was not previously reported as a bug. Still, it is an annoyance. So the question is, what is the event that causes sugar to remove an icon from the NN and how does it arise. If it is a poll of ejabberd then we should investigate, regardless of whether it is a new bug or an old one. Date: Thu, 17 Apr 2014 15:09:16 +1000 From: qu...@laptop.org To: support-g...@lists.laptop.org Subject: Re: [support-gang] 32(+) XO-1's on Mesh Potato 2 as AP on XSCE On Thu, Apr 17, 2014 at 12:54:30AM -0400, Nathan C. Riddle wrote: Hopefully, later XSCE (ejabberd) version has corrected issue of falsely persistent icons in neighborhood. Not AP model related (same on TP Link). We don't know that this is an ejabberd problem yet, it could be a problem with Sugar. It would require deeper investigation. Any comments by XSCE development team ? You can write to them at xsce-de...@googlegroups.com There's also server-devel@lists.laptop.org -- James Cameron http://quozl.linux.org.au/ ___ support-gang mailing list support-g...@lists.laptop.org http://lists.laptop.org/listinfo/support-gang ___ Server-devel mailing list Server-devel@lists.laptop.org http://lists.laptop.org/listinfo/server-devel -- James Cameron http://quozl.linux.org.au/ ___ Server-devel mailing list Server-devel@lists.laptop.org http://lists.laptop.org/listinfo/server-devel
Re: [Server-devel] [Sugar-devel] 32(+) XO-1's on Mesh Potato 2 as AP on XSCE
Perhaps the following links might be useful :: https://bugs.freedesktop.org/show_bug.cgi?id=51501 http://www.mail-archive.com/telepathy@lists.freedesktop.org/msg05699.html Also, I wrote a patch for Avahi, which allows to customize the TTL time, after which the disconnected buddy actually gets removed from Avahi's list :: http://people.sugarlabs.org/ajay/root/freedesktop_bug_51501/common-patch-for-f14-and-f17/customize-avahi-default-ttl-values.patch Thanks and Regards, Ajay On Thu, Apr 17, 2014 at 12:46 PM, James Cameron qu...@laptop.org wrote: As this is a question about Sugar, perhaps the Sugar developers should be involved. +CC sugar-devel@ Problem description: 32 XO-1 laptops are booted and registered to a school server, and all 32 icons are visible in neighbourhood, but the icons persist after any XO leaves. Sugar-0.96 (yes, really), on OLPC OS 12.1.0. Sorry, I don't know how the XO is being asked to leave; forced power off, shutdown request using power button, or shutdown using Sugar menu. This would be something to investigate. My experience is that a shutdown request using power button is similar in effect to typing shutdown -h now via sshd, and this leaves the SSH client stranded without the connection clearing down. Perhaps all that is required is time for the ejabberd connection to time out? Perhaps this is fixed in a later release of Sugar, and an upgrade or field change can be recommended? On Thu, Apr 17, 2014 at 06:58:40AM +, Tim Moody wrote: As far as I know the implementation of ejabberd on xsce was a straight port from xs 0.7, so I wouldn't have expected a bug to have been introduced, but it is speculation either way. All we know is that what Nathan observes was not previously reported as a bug. Still, it is an annoyance. So the question is, what is the event that causes sugar to remove an icon from the NN and how does it arise. If it is a poll of ejabberd then we should investigate, regardless of whether it is a new bug or an old one. Date: Thu, 17 Apr 2014 15:09:16 +1000 From: qu...@laptop.org To: support-g...@lists.laptop.org Subject: Re: [support-gang] 32(+) XO-1's on Mesh Potato 2 as AP on XSCE On Thu, Apr 17, 2014 at 12:54:30AM -0400, Nathan C. Riddle wrote: Hopefully, later XSCE (ejabberd) version has corrected issue of falsely persistent icons in neighborhood. Not AP model related (same on TP Link). We don't know that this is an ejabberd problem yet, it could be a problem with Sugar. It would require deeper investigation. Any comments by XSCE development team ? You can write to them at xsce-de...@googlegroups.com There's also server-devel@lists.laptop.org -- James Cameron http://quozl.linux.org.au/ ___ support-gang mailing list support-g...@lists.laptop.org http://lists.laptop.org/listinfo/support-gang ___ Server-devel mailing list Server-devel@lists.laptop.org http://lists.laptop.org/listinfo/server-devel -- James Cameron http://quozl.linux.org.au/ ___ Sugar-devel mailing list sugar-de...@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel -- Regards, Ajay ___ Server-devel mailing list Server-devel@lists.laptop.org http://lists.laptop.org/listinfo/server-devel
Re: [Server-devel] [XSCE] Fwd: [support-gang] Number of XO-1 per AP on XSCE - one data point
This number resonates with me. Kevin Gordon, in Toronto, was interested in XSCE primarily because it would offer ejabberd, without which the factorial N conversations taken two at a time would fill the air waves at N=13. I'm responding this way because of your statement that the clients were non-XOs. My guess is that no AP will be able to handle more than 13 without ejabberd (and the registration process between the XO and the server which enables it). On Mon, Apr 7, 2014 at 12:14 PM, Adam Holt h...@laptop.org wrote: FYI! From: Nathan C. Riddle nathanr...@charter.net Date: Mon, Apr 7, 2014 at 12:05 PM Subject: [support-gang] Number of XO-1 per AP on XSCE - one data point To: Gang support-g...@laptop.org The maximum usable number of XO-1's (12.1.0) appears to be 14 using as AP TP-Link MR3020 on XSCE 0.4 RC1 on XO-1.5 with about 10 non-XO's showing in neighborhood. Number 15 is unreliable at connecting. With 14, simple connections to MOODLE appear reliable. XSCE 0.4 was used since it was the only one available last September as school started. Testing DKMS libertas.ko file provided by quozl.org ( http://dev.laptop.org/~quozl/12757/dkms with chmod 744 to file) to establish baseline for Mesh Potato-2 Basic AP replacement of MR3020. Presence of XO-1 with no modification appears to have no effect on connections by modified XO-1's (as contrasted to XO-1's with old .ko file). Hoping MP-2 will push this past 25. Supplying this one data point since I had previously ask this question here. Nathan Riddle -- Unsung Heroes of OLPC, interviewed live @ http://unleashkids.org ! ___ Server-devel mailing list Server-devel@lists.laptop.org http://lists.laptop.org/listinfo/server-devel
Re: [Server-devel] [XSCE] Fwd: [support-gang] Number of XO-1 per AP on XSCE - one data point
It would be interesting to see the same test with XSCE, ejabberd, and three APs on separate channels. This would reduce the processing burden on the AP CPUs, and reduce the air time requirement. On Mon, Apr 07, 2014 at 06:55:55PM -0400, George Hunt wrote: This number resonates with me. Kevin Gordon, in Toronto, was interested in XSCE primarily because it would offer ejabberd, without which the factorial N conversations taken two at a time would fill the air waves at N=13. I'm responding this way because of your statement that the clients were non-XOs. My guess is that no AP will be able to handle more than 13 without ejabberd (and the registration process between the XO and the server which enables it). On Mon, Apr 7, 2014 at 12:14 PM, Adam Holt h...@laptop.org wrote: FYI! From: Nathan C. Riddle nathanr...@charter.net Date: Mon, Apr 7, 2014 at 12:05 PM Subject: [support-gang] Number of XO-1 per AP on XSCE - one data point To: Gang support-g...@laptop.org The maximum usable number of XO-1's (12.1.0) appears to be 14 using as AP TP-Link MR3020 on XSCE 0.4 RC1 on XO-1.5 with about 10 non-XO's showing in neighborhood. Number 15 is unreliable at connecting. With 14, simple connections to MOODLE appear reliable. XSCE 0.4 was used since it was the only one available last September as school started. Testing DKMS libertas.ko file provided by quozl.org (http://dev.laptop.org/ ~quozl/12757/dkms with chmod 744 to file) to establish baseline for Mesh Potato-2 Basic AP replacement of MR3020. Presence of XO-1 with no modification appears to have no effect on connections by modified XO-1's (as contrasted to XO-1's with old .ko file). Hoping MP-2 will push this past 25. Supplying this one data point since I had previously ask this question here. Nathan Riddle -- Unsung Heroes of OLPC, interviewed live @ http://unleashkids.org ! -- James Cameron http://quozl.linux.org.au/ ___ Server-devel mailing list Server-devel@lists.laptop.org http://lists.laptop.org/listinfo/server-devel
Re: XO-1 wireless tests
On Sat, Feb 15, 2014 at 05:57:56PM +0100, Jon Nettleton wrote: Tim wrote: So I think the answer is yes to 1) and yes to 2), especially if you are unlucky enough to have your target AP and the active mesh on the same channel. Does the mesh get disabled or moved when you connect to an AP on a different channel? I studied this last week with monitor mode, tcpdump and wireshark. When the wireless adapter has been commanded to associate with an access point on a specific channel, mesh beacons and mesh probe responses are seen from that adapter on that channel. This can be verified by scanning. So in my opinion, you are always going to have your target AP and the active mesh on the same channel. The variability of Tim's results are probably determined by the environment the test is being done in. Take the test back to Haiti where it failed. -- James Cameron http://quozl.linux.org.au/ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
XO-1 wireless tests
I've spent quite a bit of time testing the recent fix to the libertas driver to determine 1) does it resolve the issue of access points being missed in scans 2) if so, does that help the problem we had in Haiti, where XO-1s could not see and not connect to access points On the first point, I ran the scripts provided in the call for testing and returned the files produced. I am told the results indicate that access points are significantly less likely to be missed in a scan and I believe that to be true. Confirming the second point was more tricky in that I found it difficult to reproduce the failure we saw in Haiti. I used three APs that I had in Haiti (2 x TPL 4300 and a VT MP02), but in the house everything worked fine, in spite of the fact that it is a very noisy environment, as many as 14 APs can be visible in the NN. I didn't see any difference between Kevin Gordon's custom OS based on 11.3 and the 12.1 we had in Haiti (I did not try 13.2 on more than one XO-1). I didn't see any difference that I could pin on the make and model (all had the same firmware - VT SECN 2.0 RC3d). But channel makes a big difference, though not in the way I had assumed. I initially set the AP to 9 to avoid the mesh and other APs and there were no connectivity issues. Of course my AP was right next to the XOs, so had the strongest signal. I tried 1 and 11 and still connectivity was 100%, even though there are a number of other APs visible that are on those channels. But the XOs change the active mesh according to their own inscrutable (by me) logic. When the mesh was active on channel 1 and the AP was set to 1 the likelihood of a successful connection went down to 50% and below. I applied James Cameron's fix. All XOs successfully connected to the AP even though both the AP and the active mesh were on channel 1. For more certainty I reverted the fix and connectivity went down again, applied it and connectivity went back to 100%. I should say that I did not try the workaround of turning off the mesh on all the XOs. So I think the answer is yes to 1) and yes to 2), especially if you are unlucky enough to have your target AP and the active mesh on the same channel. The tinycore script I used to apply the fix is at http://xsce.activitycentral.com/downloads/TC-libertas-patch.zip (I only tested it with 12.1, but it has logic and files for both 12.1 and 13.2) unzip it to a usb, insert the usb into the XO-1 and boot (no four button or other button combination) It contains the modified libertas.ko files, the originals of which are at http://dev.laptop.org/~quozl/12757/dkms/ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [XSCE] XO-1 wireless tests
*snip* So I think the answer is yes to 1) and yes to 2), especially if you are unlucky enough to have your target AP and the active mesh on the same channel. Does the mesh get disabled or moved when you connect to an AP on a different channel? The XO's only have a single radio so can only communicate efficiently on a single channel at a time. If we are trying to keep the mesh active on one channel and connect to an AP on another that is certainly going to cause problems. -Jon ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [XSCE] XO-1 wireless tests
I have no idea what the XO does, only observations. I speculate that when an XO connects to an AP, it stops connecting to the mesh. My observation is that when the AP is on a different channel than the mesh the XO is much more likely to find it and connect to it, especially with an unpatched libertas driver. Tim -Original Message- From: Jon Nettleton Sent: Saturday, February 15, 2014 11:57 AM To: xsce-devel Cc: server-de...@lists.laptop.org ; server-de...@lists.laptop.org ; Unleash Kids! ; Community Support Volunteers -- who help respond to help AT laptop.org Subject: Re: [XSCE] XO-1 wireless tests *snip* So I think the answer is yes to 1) and yes to 2), especially if you are unlucky enough to have your target AP and the active mesh on the same channel. Does the mesh get disabled or moved when you connect to an AP on a different channel? The XO's only have a single radio so can only communicate efficiently on a single channel at a time. If we are trying to keep the mesh active on one channel and connect to an AP on another that is certainly going to cause problems. -Jon ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Server-devel] [XSCE] XO-1 wireless tests
*snip* So I think the answer is yes to 1) and yes to 2), especially if you are unlucky enough to have your target AP and the active mesh on the same channel. Does the mesh get disabled or moved when you connect to an AP on a different channel? The XO's only have a single radio so can only communicate efficiently on a single channel at a time. If we are trying to keep the mesh active on one channel and connect to an AP on another that is certainly going to cause problems. -Jon ___ Server-devel mailing list Server-devel@lists.laptop.org http://lists.laptop.org/listinfo/server-devel
Re: XO-1 wireless scan test Tim-2
Tim followed up privately with some more results, testing with the new wireless driver gave this: Linux: 699 scans, 694 pass, 5 fail, 1% failure to see SSID. Open Firmware: 1019 scans, 1019 pass, 0 fail, 0% failure to see SSID. Which was a drop from 59% failure to 1% failure, and is consistent with the earlier Open Firmware test at 4% failure. So the effect of the new wireless driver was to decrease the scan failure significantly, as monitored by one XO-1 in a group of 12 XO-1s. This result mirrors the results that Terry and I have achieved, so it looks like it is solved. New kernels are available with the new wireless driver, for all XO laptops, but only for the Fedora 18 builds of OLPC OS. Deployment builds with an automatic updater, such as the Dextrose updater, may upgrade their kernel some time in the next week. http://wiki.laptop.org/go/12757 describes how to upgrade. -- James Cameron http://quozl.linux.org.au/ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: XO-1 wireless scan test Tim-1
iwlist on 11.3 does not return Extra:Last Beacon. I tried yum upgrade, but there was no later package. So I upgraded the monitor xo only to 12.1 and am re-running. Tim -Original Message- From: James Cameron Sent: Monday, February 10, 2014 6:53 PM To: Tim Moody Cc: devel@lists.laptop.org ; server-de...@lists.laptop.org ; xsce-de...@googlegroups.com ; support-g...@lists.laptop.org ; unleashk...@googlegroups.com Subject: Re: XO-1 wireless scan test Tim-1 Thanks. The Open Firmware test results look valid and I shall process them. The Linux test results don't seem to be working. Each line contains timestamp only, and no last beacon time. I wonder if the script won't work properly on 11.3. I haven't tested it there. Can you check that script for me, especially whether the iwlist command is working and if it includes a last beacon time in the output. If 11.3 hasn't got what it takes, try again with 12.1.0 or 13.2.0, thanks. -- James Cameron http://quozl.linux.org.au/ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [support-gang] CFT: XO-1 wireless scan results loss
how should we test? Tim -Original Message- From: James Cameron Sent: Tuesday, February 11, 2014 12:32 AM To: devel@lists.laptop.org ; server-de...@lists.laptop.org ; xsce-de...@googlegroups.com ; support-g...@lists.laptop.org ; unleashk...@googlegroups.com Subject: Re: [support-gang] CFT: XO-1 wireless scan results loss The problem: as XO-1s are turned on in a class, the chances of scanning an access point fall. Only affects XO-1s. The cause: the XO-1s also respond to scan, and if these probes arrive first, the access point is not seen. The bug is in the kernel, and has been there from the beginning. A fix has been pushed, and is in testing by Terry and I. http://dev.laptop.org/ticket/12757 has the technical details. It will need wider testing. There are other reasons why an access point might not be scanned; the probes may have happened too close together, the antennas may be broken, or there may be too much noise from other devices. So it is important to get an idea of the change that this fix will make. -- James Cameron http://quozl.linux.org.au/ ___ support-gang mailing list support-g...@lists.laptop.org http://lists.laptop.org/listinfo/support-gang ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: XO-1 wireless scan test Tim-2
Very good data, thanks. Your test results are: Open Firmware: 1334 scans, 1328 pass, 6 fail, 4% failure to see SSID. Linux: 346 scans, 142 pass, 204 fail, 59% failure to see SSID. This result confirms the problem is happening; the wireless card works fine, but Linux does not. Next, please do not change the test configuration at all, but upgrade the monitor to 13.2.0, and I will send you a kernel module file that will fix the problem, and you can then retest. Will send in separate private mail. You may also upgrade the rest of the XO-1s to 13.2.0 for this next test, and apply the kernel module there as well. On Tue, Feb 11, 2014 at 01:41:02PM -0500, Tim Moody wrote: TPLink WDR4300 SSID: WDR4300 Channel: 9 MAC: 10:FE:ED:9B:66:2F Firmware: SECN v 2 RC3d router's dhcp server is on router's mesh is off 2.4Hz only and set to G only no internet access 11 XO-1s with 12th a logger XO OS: Kevin Gordon custom based on 11.3, fc14 with Q2F19 ROM Monitor XO OS 12.1 Powered off previous AP, powered on WDR4300, and tried switching all XO-1s without powering off and on individually: 1 - 4 new AP visible in NN and connected with no problem 5 - took more time to appear 6 -7 new AP visible and connected with no problem 8 - 11 never became visible 8 - discarded network history without effect 8 - powered off and on and new AP visible and easily connected 9 - powered off and on and new AP visible and easily connected 10 -11 done together with success All XO-1s powered off and powered on sequentially All connected to the AP OFW test run Linux test run 1392139305 220 1392139310 5250 1392139315 10250 1392139350 220 1392139355 5210 1392139360 10210 1392139375 170 1392139380 5050 1392139385 10060 1392139420 2147489028 1392139425 2147493998 1392139450 220 1392139455 230 1392139460 5220 1392139465 10210 1392139505 220 1392139510 230 1392139515 5220 1392139520 10200 1392139565 220 1392139570 5220 1392139575 10220 1392139590 230 1392139595 230 1392139600 220 1392139605 210 1392139610 5200 1392139615 10220 1392139635 220 1392139640 5330 1392139645 10300 1392139650 220 1392139655 5220 1392139660 10210 1392139675 220 1392139680 220 1392139685 5230 1392139690 10210 1392139700 230 1392139705 5320 1392139710 10180 1392139725 220 1392139735 10150 1392139760 230 1392139765 5210 1392139770 10200 1392139775 220 1392139780 5220 1392139785 10230 1392139840 220 1392139845 5220 1392139850 10200 1392139865 230 1392139870 5230 1392139875 10250 1392139920 230 1392139925 5200 1392139930 10190 1392139960 220 1392139965 220 1392139970 5220 1392139975 230 1392139980 5240 1392139985 10210 1392140010 220 1392140015 5230 1392140020 10210 1392140090 230 1392140095 5230 1392140100 220 1392140105 5210 1392140110 10290 1392140115 220 1392140120 230 1392140125 5230 1392140130 10210 1392140150 220 1392140155 5230 1392140160 10230 1392140180 220 1392140185 5230 1392140190 220 1392140195 230 1392140200 220 1392140205 220 1392140210 5220 1392140215 10220 1392140230 220 1392140235 5240 1392140240 10230 1392140330 220 1392140335 5230 1392140340 220 1392140345 210 1392140350 5220 1392140355 10210 1392140365 230 1392140370 5220 1392140375 10330 1392140475 220 1392140480 5230 1392140485 10250 1392140495 230 1392140500 5210 1392140505 10300 1392140515 190 1392140520 5070 1392140525 10060 1392140530 230 1392140535 5230 1392140540 10230 1392140560 220 1392140565 5110 1392140570 230 1392140575 5210 1392140580 220 1392140585 5220 1392140590 10210 1392140645 220 1392140650 5220 1392140655 10210 1392140690 230 1392140695 5150 1392140700 10160 1392140715 220 1392140720 5220 1392140725 10230 1392140760 220 1392140765 230 1392140770 220 1392140775 5240 1392140780 10250 1392140785 220 1392140790 5200 1392140795 10190 1392140815 230 1392140820 220 1392140825 220 1392140830 5210 1392140835 10190 1392140840 220 1392140845 230 1392140850 5290 1392140855 10280 1392140865 220 1392140870 5210 1392140875 10190 1392140890 230 1392140895 5230 1392140900 10230 1392140915 220 1392140920 5230 1392140925 230 1392140930 5230 1392140935 220 1392140940 230 1392140945 220 1392140950 5220 1392140955 10300 1392140980 220 1392140985 220 1392140995 10240 1392141050 220 1392141055 5220 1392141060 10220 1392141080 210 1392141085 5210 1392141090 10200 1392141140 220 1392141145 5240 1392141150 10220 1392141180 230 1392141185 5230 1392141190 210 1392141195 5210 1392141200 10200 1392141215 220 1392141220 220 1392141225 5250 1392141230 10240 1392141235 220 1392141240 5220 1392141245 10220 1392141265 230 1392141270 5220 1392141275 10200 1392141310 220 1392141315 5210 1392141320 230 1392141325 5210 1392141330 10210 1392141340 220 1392141345 5330 1392141350 10300 1392141365 230 1392141370 5240 1392141375 10220 1392141385 210 1392141390 5220 1392141395 10220 1392141455
Re: CFT: XO-1 wireless scan results loss
The testing can be widened to include a fixed kernel. See http://wiki.laptop.org/go/12757 for details. -- James Cameron http://quozl.linux.org.au/ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Server-devel] XO-1 wireless scan test Tim-1
iwlist on 11.3 does not return Extra:Last Beacon. I tried yum upgrade, but there was no later package. So I upgraded the monitor xo only to 12.1 and am re-running. Tim -Original Message- From: James Cameron Sent: Monday, February 10, 2014 6:53 PM To: Tim Moody Cc: de...@lists.laptop.org ; server-devel@lists.laptop.org ; xsce-de...@googlegroups.com ; support-g...@lists.laptop.org ; unleashk...@googlegroups.com Subject: Re: XO-1 wireless scan test Tim-1 Thanks. The Open Firmware test results look valid and I shall process them. The Linux test results don't seem to be working. Each line contains timestamp only, and no last beacon time. I wonder if the script won't work properly on 11.3. I haven't tested it there. Can you check that script for me, especially whether the iwlist command is working and if it includes a last beacon time in the output. If 11.3 hasn't got what it takes, try again with 12.1.0 or 13.2.0, thanks. -- James Cameron http://quozl.linux.org.au/ ___ Server-devel mailing list Server-devel@lists.laptop.org http://lists.laptop.org/listinfo/server-devel
Re: [Server-devel] XO-1 wireless scan test Tim-2
Very good data, thanks. Your test results are: Open Firmware: 1334 scans, 1328 pass, 6 fail, 4% failure to see SSID. Linux: 346 scans, 142 pass, 204 fail, 59% failure to see SSID. This result confirms the problem is happening; the wireless card works fine, but Linux does not. Next, please do not change the test configuration at all, but upgrade the monitor to 13.2.0, and I will send you a kernel module file that will fix the problem, and you can then retest. Will send in separate private mail. You may also upgrade the rest of the XO-1s to 13.2.0 for this next test, and apply the kernel module there as well. On Tue, Feb 11, 2014 at 01:41:02PM -0500, Tim Moody wrote: TPLink WDR4300 SSID: WDR4300 Channel: 9 MAC: 10:FE:ED:9B:66:2F Firmware: SECN v 2 RC3d router's dhcp server is on router's mesh is off 2.4Hz only and set to G only no internet access 11 XO-1s with 12th a logger XO OS: Kevin Gordon custom based on 11.3, fc14 with Q2F19 ROM Monitor XO OS 12.1 Powered off previous AP, powered on WDR4300, and tried switching all XO-1s without powering off and on individually: 1 - 4 new AP visible in NN and connected with no problem 5 - took more time to appear 6 -7 new AP visible and connected with no problem 8 - 11 never became visible 8 - discarded network history without effect 8 - powered off and on and new AP visible and easily connected 9 - powered off and on and new AP visible and easily connected 10 -11 done together with success All XO-1s powered off and powered on sequentially All connected to the AP OFW test run Linux test run 1392139305 220 1392139310 5250 1392139315 10250 1392139350 220 1392139355 5210 1392139360 10210 1392139375 170 1392139380 5050 1392139385 10060 1392139420 2147489028 1392139425 2147493998 1392139450 220 1392139455 230 1392139460 5220 1392139465 10210 1392139505 220 1392139510 230 1392139515 5220 1392139520 10200 1392139565 220 1392139570 5220 1392139575 10220 1392139590 230 1392139595 230 1392139600 220 1392139605 210 1392139610 5200 1392139615 10220 1392139635 220 1392139640 5330 1392139645 10300 1392139650 220 1392139655 5220 1392139660 10210 1392139675 220 1392139680 220 1392139685 5230 1392139690 10210 1392139700 230 1392139705 5320 1392139710 10180 1392139725 220 1392139735 10150 1392139760 230 1392139765 5210 1392139770 10200 1392139775 220 1392139780 5220 1392139785 10230 1392139840 220 1392139845 5220 1392139850 10200 1392139865 230 1392139870 5230 1392139875 10250 1392139920 230 1392139925 5200 1392139930 10190 1392139960 220 1392139965 220 1392139970 5220 1392139975 230 1392139980 5240 1392139985 10210 1392140010 220 1392140015 5230 1392140020 10210 1392140090 230 1392140095 5230 1392140100 220 1392140105 5210 1392140110 10290 1392140115 220 1392140120 230 1392140125 5230 1392140130 10210 1392140150 220 1392140155 5230 1392140160 10230 1392140180 220 1392140185 5230 1392140190 220 1392140195 230 1392140200 220 1392140205 220 1392140210 5220 1392140215 10220 1392140230 220 1392140235 5240 1392140240 10230 1392140330 220 1392140335 5230 1392140340 220 1392140345 210 1392140350 5220 1392140355 10210 1392140365 230 1392140370 5220 1392140375 10330 1392140475 220 1392140480 5230 1392140485 10250 1392140495 230 1392140500 5210 1392140505 10300 1392140515 190 1392140520 5070 1392140525 10060 1392140530 230 1392140535 5230 1392140540 10230 1392140560 220 1392140565 5110 1392140570 230 1392140575 5210 1392140580 220 1392140585 5220 1392140590 10210 1392140645 220 1392140650 5220 1392140655 10210 1392140690 230 1392140695 5150 1392140700 10160 1392140715 220 1392140720 5220 1392140725 10230 1392140760 220 1392140765 230 1392140770 220 1392140775 5240 1392140780 10250 1392140785 220 1392140790 5200 1392140795 10190 1392140815 230 1392140820 220 1392140825 220 1392140830 5210 1392140835 10190 1392140840 220 1392140845 230 1392140850 5290 1392140855 10280 1392140865 220 1392140870 5210 1392140875 10190 1392140890 230 1392140895 5230 1392140900 10230 1392140915 220 1392140920 5230 1392140925 230 1392140930 5230 1392140935 220 1392140940 230 1392140945 220 1392140950 5220 1392140955 10300 1392140980 220 1392140985 220 1392140995 10240 1392141050 220 1392141055 5220 1392141060 10220 1392141080 210 1392141085 5210 1392141090 10200 1392141140 220 1392141145 5240 1392141150 10220 1392141180 230 1392141185 5230 1392141190 210 1392141195 5210 1392141200 10200 1392141215 220 1392141220 220 1392141225 5250 1392141230 10240 1392141235 220 1392141240 5220 1392141245 10220 1392141265 230 1392141270 5220 1392141275 10200 1392141310 220 1392141315 5210 1392141320 230 1392141325 5210 1392141330 10210 1392141340 220 1392141345 5330 1392141350 10300 1392141365 230 1392141370 5240 1392141375 10220 1392141385 210 1392141390 5220 1392141395 10220 1392141455
Re: [support-gang] CFT: XO-1 wireless scan results loss
A couple of questions on the test environment. Do you care what channel the ap is on? Do you care if anything is serving dhcp? Do you care if the xo can reach the internet? Tim -Original Message- From: James Cameron Sent: Sunday, February 09, 2014 11:47 PM To: devel@lists.laptop.org ; server-de...@lists.laptop.org ; xsce-de...@googlegroups.com ; support-g...@lists.laptop.org ; unleashk...@googlegroups.com Subject: Re: [support-gang] CFT: XO-1 wireless scan results loss On Mon, Feb 10, 2014 at 01:41:51PM +1100, James Cameron wrote: Ingredients: 1. several XO-1, with mesh not disabled, with Q2F19, At least two XO-1 are required. Recipe: 1. record the SSID of the access point, and customise the shell script accordingly, 2. record the MAC address of the access point, Typo. Second phrase is to be swapped; the MAC address goes into the shell script. -- James Cameron http://quozl.linux.org.au/ ___ support-gang mailing list support-g...@lists.laptop.org http://lists.laptop.org/listinfo/support-gang ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Server-devel] [support-gang] CFT: XO-1 wireless scan results loss
On Mon, Feb 10, 2014 at 10:52:10AM -0500, Tim Moody wrote: Do you care what channel the ap is on? Yes, and I will be able to deduce it from the logs. Our tests so far have been with channel 1. If you detect any channel dependency, that will be interesting data. Do you care if anything is serving dhcp? No, but it may be useful to record the state of this in case it has relevance. Our tests so far have been with DHCP. Additional wireless traffic does occur with DHCP, but as these are data broadcast packets they should not be relevant to the problem at hand except as a generic air time consumer. Do you care if the xo can reach the internet? No, as above, s/DHCP/routable. -- James Cameron http://quozl.linux.org.au/ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [XSCE] XO-1 wireless scan test Tim-1
Might try your Haiti 12.1 and see if you get similar Kg Sent from my currently functioning gadget Original Message From: Tim Moody Sent: Monday, February 10, 2014 18:25 To: James Cameron Reply To: xsce-de...@googlegroups.com Cc: devel@lists.laptop.org; server-de...@lists.laptop.org; xsce-de...@googlegroups.com; support-g...@lists.laptop.org; unleashk...@googlegroups.com Subject: [XSCE] XO-1 wireless scan test Tim-1 VT MP02 SSID: TIM-UTIL-AP Channel: 9 MAC: A8:40:41:13:49:A8 Firmware: SECN v 2 RC3d router's dhcp server is on router's mesh is off no internet access 11 XO-1s with 12th a logger XO OS: Kevn Gordon custom based on 11.3, fc14 with Q2F19 ROM Each XO was powered on and connected to AP, which was visible in NN in each case, and then powered off. The 11 XOs were powered on in sequence and after all had connected to AP the 12th booted the scan logging software. After 1 hour the test was stopped and the linux test run. I don't think there were any misses. Additionally, after the test, the AP was changed to channel 1 and rebooted. All XOs connected to mesh-1. After the AP rebooted it was visible in all NN and all were manually connected to it successfully, though connection time as a little longer, or order of 10 seconds. I'll run another test on this channel tomorrow. ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: XO-1 wireless scan test Tim-1
Thanks. The Open Firmware test results look valid and I shall process them. The Linux test results don't seem to be working. Each line contains timestamp only, and no last beacon time. I wonder if the script won't work properly on 11.3. I haven't tested it there. Can you check that script for me, especially whether the iwlist command is working and if it includes a last beacon time in the output. If 11.3 hasn't got what it takes, try again with 12.1.0 or 13.2.0, thanks. -- James Cameron http://quozl.linux.org.au/ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: XO-1 wireless scan test Tim-1
I've verified your Open Firmware test log. Number of scans: 1201 Number of scans that included the SSID: 1172 Proportion of scans that did not include the SSID: 2.4% Please run the Linux half of the test again once you have fixed the cause of the missing last beacon time. -- James Cameron http://quozl.linux.org.au/ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: CFT: XO-1 wireless scan results loss
The problem: as XO-1s are turned on in a class, the chances of scanning an access point fall. Only affects XO-1s. The cause: the XO-1s also respond to scan, and if these probes arrive first, the access point is not seen. The bug is in the kernel, and has been there from the beginning. A fix has been pushed, and is in testing by Terry and I. http://dev.laptop.org/ticket/12757 has the technical details. It will need wider testing. There are other reasons why an access point might not be scanned; the probes may have happened too close together, the antennas may be broken, or there may be too much noise from other devices. So it is important to get an idea of the change that this fix will make. -- James Cameron http://quozl.linux.org.au/ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [UKids] XO-1 classrooms don't reliably connect to many/most Wifi AP's
On Mon, Feb 10, 2014 at 11:31:39AM +1100, James Cameron wrote: On Sun, Feb 09, 2014 at 07:18:49PM -0500, Kevin Gordon Gmail wrote: Tp link set as 3g router mode, with usb Sierra wireless usb modem, set to channel 11, 80211g only, wpa2 pal security. Running stock f/w. Terry found that channel 1 was the most afflicted. I suspect, but I haven't checked, that the idle mesh only uses channel 1, but it also use whatever channel the laptop is associated with. Tim's results from Open Firmware show that the idle mesh switches to whatever channel is being used for association with an access point. So while we would normally see an operating mesh on 1, 6 and 11, it can be seen on other channels as well. The underlying fault was somewhat channel specific ... because the scans are done in sets; (1,2,3,4), (5,6,7,8), (9,10,11,12). If a mesh was heard on channel 1 then the scan results for channels 2, 3 and 4 will have been lost. If a mesh was heard on channel 9, then the scan results for channels 10, 11 and 12 will have been lost. -- James Cameron http://quozl.linux.org.au/ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [UKids] XO-1 classrooms don't reliably connect to many/most Wifi AP's
On Tue, Feb 11, 2014 at 7:08 AM, James Cameron qu...@laptop.org wrote: On Mon, Feb 10, 2014 at 11:31:39AM +1100, James Cameron wrote: On Sun, Feb 09, 2014 at 07:18:49PM -0500, Kevin Gordon Gmail wrote: Tp link set as 3g router mode, with usb Sierra wireless usb modem, set to channel 11, 80211g only, wpa2 pal security. Running stock f/w. Terry found that channel 1 was the most afflicted. I suspect, but I haven't checked, that the idle mesh only uses channel 1, but it also use whatever channel the laptop is associated with. Tim's results from Open Firmware show that the idle mesh switches to whatever channel is being used for association with an access point. This has to be the case because there is only one radio, so both 802.11s and 802.11b/g have to be configured for the same channel. So while we would normally see an operating mesh on 1, 6 and 11, it can be seen on other channels as well. The underlying fault was somewhat channel specific ... because the scans are done in sets; (1,2,3,4), (5,6,7,8), (9,10,11,12). If a mesh was heard on channel 1 then the scan results for channels 2, 3 and 4 will have been lost. If a mesh was heard on channel 9, then the scan results for channels 10, 11 and 12 will have been lost. I think really what we need to do is have a better workflow for detecting connectivity, not much different from how we are handling ad-hoc on the later model XO's I think on initial boot, or waking from suspend and the previous wifi state was not connected, we need to disable the mesh interface and scan for infrastructure AP's. Then if this fails we can either scan for ad-hoc or bring up the mesh interface and look for a mesh network to connect to. I think besides driver bugs we have a general problem of trying to do too much at the same time with a single radio. any takers on this workflow for network discovery? -Jon ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: XO-1 classrooms don't reliably connect to many/most Wifi AP's
On Tue, Feb 11, 2014 at 07:24:33AM +0100, Jon Nettleton wrote: On Tue, Feb 11, 2014 at 7:08 AM, James Cameron qu...@laptop.org wrote: On Mon, Feb 10, 2014 at 11:31:39AM +1100, James Cameron wrote: On Sun, Feb 09, 2014 at 07:18:49PM -0500, Kevin Gordon Gmail wrote: Tp link set as 3g router mode, with usb Sierra wireless usb modem, set to channel 11, 80211g only, wpa2 pal security. Running stock f/w. Terry found that channel 1 was the most afflicted. I suspect, but I haven't checked, that the idle mesh only uses channel 1, but it also use whatever channel the laptop is associated with. Tim's results from Open Firmware show that the idle mesh switches to whatever channel is being used for association with an access point. This has to be the case because there is only one radio, so both 802.11s and 802.11b/g have to be configured for the same channel. And being off-channel would be too costly. So while we would normally see an operating mesh on 1, 6 and 11, it can be seen on other channels as well. The underlying fault was somewhat channel specific ... because the scans are done in sets; (1,2,3,4), (5,6,7,8), (9,10,11,12). If a mesh was heard on channel 1 then the scan results for channels 2, 3 and 4 will have been lost. If a mesh was heard on channel 9, then the scan results for channels 10, 11 and 12 will have been lost. I think really what we need to do is have a better workflow for detecting connectivity, not much different from how we are handling ad-hoc on the later model XO's I think on initial boot, or waking from suspend and the previous wifi state was not connected, we need to disable the mesh interface and scan for infrastructure AP's. Then if this fails we can either scan for ad-hoc or bring up the mesh interface and look for a mesh network to connect to. I think besides driver bugs we have a general problem of trying to do too much at the same time with a single radio. any takers on this workflow for network discovery? Sounds interesting, but can't commit myself. But it may be something that Sugar Labs might be interested in. It does look like it would be possible to scan for APs, ad-hoc, and mesh at the same time, without having to bring up the mesh interface first. All within about 440ms. Those mesh probe responses are useful after all. ;-) -- James Cameron http://quozl.linux.org.au/ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Server-devel] [support-gang] CFT: XO-1 wireless scan results loss
A couple of questions on the test environment. Do you care what channel the ap is on? Do you care if anything is serving dhcp? Do you care if the xo can reach the internet? Tim -Original Message- From: James Cameron Sent: Sunday, February 09, 2014 11:47 PM To: de...@lists.laptop.org ; server-devel@lists.laptop.org ; xsce-de...@googlegroups.com ; support-g...@lists.laptop.org ; unleashk...@googlegroups.com Subject: Re: [support-gang] CFT: XO-1 wireless scan results loss On Mon, Feb 10, 2014 at 01:41:51PM +1100, James Cameron wrote: Ingredients: 1. several XO-1, with mesh not disabled, with Q2F19, At least two XO-1 are required. Recipe: 1. record the SSID of the access point, and customise the shell script accordingly, 2. record the MAC address of the access point, Typo. Second phrase is to be swapped; the MAC address goes into the shell script. -- James Cameron http://quozl.linux.org.au/ ___ support-gang mailing list support-g...@lists.laptop.org http://lists.laptop.org/listinfo/support-gang ___ Server-devel mailing list Server-devel@lists.laptop.org http://lists.laptop.org/listinfo/server-devel
Re: [Server-devel] [XSCE] XO-1 wireless scan test Tim-1
Might try your Haiti 12.1 and see if you get similar Kg Sent from my currently functioning gadget Original Message From: Tim Moody Sent: Monday, February 10, 2014 18:25 To: James Cameron Reply To: xsce-de...@googlegroups.com Cc: de...@lists.laptop.org; server-devel@lists.laptop.org; xsce-de...@googlegroups.com; support-g...@lists.laptop.org; unleashk...@googlegroups.com Subject: [XSCE] XO-1 wireless scan test Tim-1 VT MP02 SSID: TIM-UTIL-AP Channel: 9 MAC: A8:40:41:13:49:A8 Firmware: SECN v 2 RC3d router's dhcp server is on router's mesh is off no internet access 11 XO-1s with 12th a logger XO OS: Kevn Gordon custom based on 11.3, fc14 with Q2F19 ROM Each XO was powered on and connected to AP, which was visible in NN in each case, and then powered off. The 11 XOs were powered on in sequence and after all had connected to AP the 12th booted the scan logging software. After 1 hour the test was stopped and the linux test run. I don't think there were any misses. Additionally, after the test, the AP was changed to channel 1 and rebooted. All XOs connected to mesh-1. After the AP rebooted it was visible in all NN and all were manually connected to it successfully, though connection time as a little longer, or order of 10 seconds. I'll run another test on this channel tomorrow. ___ Server-devel mailing list Server-devel@lists.laptop.org http://lists.laptop.org/listinfo/server-devel
Re: [Server-devel] CFT: XO-1 wireless scan results loss
The problem: as XO-1s are turned on in a class, the chances of scanning an access point fall. Only affects XO-1s. The cause: the XO-1s also respond to scan, and if these probes arrive first, the access point is not seen. The bug is in the kernel, and has been there from the beginning. A fix has been pushed, and is in testing by Terry and I. http://dev.laptop.org/ticket/12757 has the technical details. It will need wider testing. There are other reasons why an access point might not be scanned; the probes may have happened too close together, the antennas may be broken, or there may be too much noise from other devices. So it is important to get an idea of the change that this fix will make. -- James Cameron http://quozl.linux.org.au/ ___ Server-devel mailing list Server-devel@lists.laptop.org http://lists.laptop.org/listinfo/server-devel
Re: [Server-devel] [UKids] XO-1 classrooms don't reliably connect to many/most Wifi AP's
On Mon, Feb 10, 2014 at 11:31:39AM +1100, James Cameron wrote: On Sun, Feb 09, 2014 at 07:18:49PM -0500, Kevin Gordon Gmail wrote: Tp link set as 3g router mode, with usb Sierra wireless usb modem, set to channel 11, 80211g only, wpa2 pal security. Running stock f/w. Terry found that channel 1 was the most afflicted. I suspect, but I haven't checked, that the idle mesh only uses channel 1, but it also use whatever channel the laptop is associated with. Tim's results from Open Firmware show that the idle mesh switches to whatever channel is being used for association with an access point. So while we would normally see an operating mesh on 1, 6 and 11, it can be seen on other channels as well. The underlying fault was somewhat channel specific ... because the scans are done in sets; (1,2,3,4), (5,6,7,8), (9,10,11,12). If a mesh was heard on channel 1 then the scan results for channels 2, 3 and 4 will have been lost. If a mesh was heard on channel 9, then the scan results for channels 10, 11 and 12 will have been lost. -- James Cameron http://quozl.linux.org.au/ ___ Server-devel mailing list Server-devel@lists.laptop.org http://lists.laptop.org/listinfo/server-devel
Re: [Server-devel] [UKids] XO-1 classrooms don't reliably connect to many/most Wifi AP's
On Tue, Feb 11, 2014 at 7:08 AM, James Cameron qu...@laptop.org wrote: On Mon, Feb 10, 2014 at 11:31:39AM +1100, James Cameron wrote: On Sun, Feb 09, 2014 at 07:18:49PM -0500, Kevin Gordon Gmail wrote: Tp link set as 3g router mode, with usb Sierra wireless usb modem, set to channel 11, 80211g only, wpa2 pal security. Running stock f/w. Terry found that channel 1 was the most afflicted. I suspect, but I haven't checked, that the idle mesh only uses channel 1, but it also use whatever channel the laptop is associated with. Tim's results from Open Firmware show that the idle mesh switches to whatever channel is being used for association with an access point. This has to be the case because there is only one radio, so both 802.11s and 802.11b/g have to be configured for the same channel. So while we would normally see an operating mesh on 1, 6 and 11, it can be seen on other channels as well. The underlying fault was somewhat channel specific ... because the scans are done in sets; (1,2,3,4), (5,6,7,8), (9,10,11,12). If a mesh was heard on channel 1 then the scan results for channels 2, 3 and 4 will have been lost. If a mesh was heard on channel 9, then the scan results for channels 10, 11 and 12 will have been lost. I think really what we need to do is have a better workflow for detecting connectivity, not much different from how we are handling ad-hoc on the later model XO's I think on initial boot, or waking from suspend and the previous wifi state was not connected, we need to disable the mesh interface and scan for infrastructure AP's. Then if this fails we can either scan for ad-hoc or bring up the mesh interface and look for a mesh network to connect to. I think besides driver bugs we have a general problem of trying to do too much at the same time with a single radio. any takers on this workflow for network discovery? -Jon ___ Server-devel mailing list Server-devel@lists.laptop.org http://lists.laptop.org/listinfo/server-devel
Re: [Server-devel] XO-1 classrooms don't reliably connect to many/most Wifi AP's
On Tue, Feb 11, 2014 at 07:24:33AM +0100, Jon Nettleton wrote: On Tue, Feb 11, 2014 at 7:08 AM, James Cameron qu...@laptop.org wrote: On Mon, Feb 10, 2014 at 11:31:39AM +1100, James Cameron wrote: On Sun, Feb 09, 2014 at 07:18:49PM -0500, Kevin Gordon Gmail wrote: Tp link set as 3g router mode, with usb Sierra wireless usb modem, set to channel 11, 80211g only, wpa2 pal security. Running stock f/w. Terry found that channel 1 was the most afflicted. I suspect, but I haven't checked, that the idle mesh only uses channel 1, but it also use whatever channel the laptop is associated with. Tim's results from Open Firmware show that the idle mesh switches to whatever channel is being used for association with an access point. This has to be the case because there is only one radio, so both 802.11s and 802.11b/g have to be configured for the same channel. And being off-channel would be too costly. So while we would normally see an operating mesh on 1, 6 and 11, it can be seen on other channels as well. The underlying fault was somewhat channel specific ... because the scans are done in sets; (1,2,3,4), (5,6,7,8), (9,10,11,12). If a mesh was heard on channel 1 then the scan results for channels 2, 3 and 4 will have been lost. If a mesh was heard on channel 9, then the scan results for channels 10, 11 and 12 will have been lost. I think really what we need to do is have a better workflow for detecting connectivity, not much different from how we are handling ad-hoc on the later model XO's I think on initial boot, or waking from suspend and the previous wifi state was not connected, we need to disable the mesh interface and scan for infrastructure AP's. Then if this fails we can either scan for ad-hoc or bring up the mesh interface and look for a mesh network to connect to. I think besides driver bugs we have a general problem of trying to do too much at the same time with a single radio. any takers on this workflow for network discovery? Sounds interesting, but can't commit myself. But it may be something that Sugar Labs might be interested in. It does look like it would be possible to scan for APs, ad-hoc, and mesh at the same time, without having to bring up the mesh interface first. All within about 440ms. Those mesh probe responses are useful after all. ;-) -- James Cameron http://quozl.linux.org.au/ ___ Server-devel mailing list Server-devel@lists.laptop.org http://lists.laptop.org/listinfo/server-devel
Re: [XSCE] Re: Large groups of XO-1 do not work with access points
On Sat, Feb 08, 2014 at 10:20:29AM -0500, Tim Moody wrote: Does it matter if the xo has previously connected to the ap and stored connection info? No, it doesn't matter. There's a lot of misunderstanding. I feel people aren't taking the time to understand. Restating the problem; with a stored connection, on reboot Sugar will often not connect to it, because the network is not shown in network neighbourhood, in turn because the scan results did not include the network, in turn because the scan results were lost or corrupted, in turn because of a flaw in the kernel or wireless firmware, in turn triggered by the presence of mesh nodes. Could we avoid the scan by pre-populating the connection info? No, Sugar will not initiate a connection to a wireless network name unless the name is seen in the scan results. (I think you did this in tinycore. This would also eliminate the variable of relying on NN to show us the AP.) No, Tiny Core Linux is affected by the same problem to a lesser degree, but as the user base for Tiny Core Linux is small to non-existent, I don't care to worry about it. Since we are regularly reflashing, could we turn off mesh and prepopulate a connection to a standard SSID; in Haiti we used 'lekol'? Turn off mesh; yes. Prepopulate; no. But I do not recommend turning off mesh. Mesh is actually very useful to the learners. If this strategy increases the likelihood of connection would it be possible to get fancier and have our boot script check for a connection to the known ap and if not found turn mesh back on? Yes, this might help, but I think you should wait until we move from trying to understand the problem and into selecting fixes and workarounds. It is taking a long time because we are doing it together, Terry and I, and there is other work at OLPC that is also important. I don't want you all to go off implementing quick workarounds that you have to pull out. ;-) Especially if that prevents you from using and testing a final solution. -- James Cameron http://quozl.linux.org.au/ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [UKids] XO-1 classrooms don't reliably connect to many/most Wifi AP's
On Sat, Feb 08, 2014 at 09:20:05PM +1000, T Gillett wrote: I guess the key point is that we have to make changes to the XO-1 rather than the routers :-] I don't know that yet, sorry. While the evidence so far does not incriminate the routers, there are some routers that have worked fine, and the reason they work fine is not obvious ... so I can't dismiss the possibility that a router might be modified. -- James Cameron http://quozl.linux.org.au/ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel