<div dir="ltr"><div>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:<br></div><ul><li>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)</li><li>when the XO is sleeping</li></ul><p>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 <a href="http://dev.laptop.org/~quozl/q2f20ed.rom" target="_blank">http://dev.laptop.org/~quozl/q2f20ed.rom</a> which includes EC Firmware E35, dated 2010-08-23. Wonderful that James Cameron isolated the problem.</p><p>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.<br></p><p>Regardless, folks need to retrain (refrain) themselves on when to hit ESC on bootup: <a href="http://wiki.laptop.org/go/Ok#Unsecured">http://wiki.laptop.org/go/Ok#Unsecured</a><br></p><p>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:<br>
<br>
- you lose a fix for mouse activity at shutdown preventing reboot without keyboard,<br>
<br>
- you lose a fix for battery EEPROM corruption, which happens if you are holding the power button down and insert the battery,<br>
<br>
- you lose the AP (Auto Power) and CP (Constant Power) features for use as a server, and;<br>
<br>
- you lose RTC anti-rollback support, which you shouldn't be using anyway.</p><p>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 :-)<br></p></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Aug 4, 2015 at 9:28 AM, Adam Holt <span dir="ltr"><<a href="mailto:holt@laptop.org" target="_blank">holt@laptop.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div><div>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:<br></div><ul><li>Tapping the ESC key very rapidly during bootup causes the keyboard mismapping (and hence, failure to enter Open Firmware).<br></li><li>Holding down the ESC key during bootup (generally, but not always) avoids the problem (entering Open Firmware).</li><li>Typing no keys at all during initial bootup, appears (I hope) to be a workaround to boot the OS properly, with keyboard functioning properly.<br></li></ul></div></div>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?)<br></div><div class="gmail_extra"><br><div class="gmail_quote"><div><div class="h5">On Mon, Aug 3, 2015 at 7:03 PM, Adam Holt <span dir="ltr"><<a href="mailto:holt@laptop.org" target="_blank">holt@laptop.org</a>></span> wrote:<br></div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div><div><div><div class="h5"><div>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).<br><br></div><div>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:<br><br></div><div> <a href="http://wiki.laptop.org/go/Release_notes/13.2.5#XO-1" target="_blank">http://wiki.laptop.org/go/Release_notes/13.2.5#XO-1</a><br> <a href="http://wiki.laptop.org/go/Release_notes/13.2.5#XO-1_with_SD_card" target="_blank">http://wiki.laptop.org/go/Release_notes/13.2.5#XO-1_with_SD_card</a><br><br></div><div>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.<br><br>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.<br></div><div><br>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-<br><br></div></div></div><div><div><div class="h5">(Also, any recommendations as to which older builds are best, as an interim workaround?)<br clear="all"><br></div></div><span class="HOEnZb"><font color="#888888">-- <br><div><div dir="ltr">Unsung Heroes of OLPC, interviewed live @ <a href="http://unleashkids.org" target="_blank">http://unleashkids.org</a> !</div></div>
</font></span></div></div>
</div></div></div></blockquote></div></div>
</blockquote></div><br><br clear="all"><br>-- <br><div class="gmail_signature"><div dir="ltr">Unsung Heroes of OLPC, interviewed live @ <a href="http://unleashkids.org" target="_blank">http://unleashkids.org</a> !</div></div>
</div>