Just to keep everyone posted. We managed to resolve the issue on the XO 1.0 thanks to an effective IRC troubleshooting session with Adam and James this morning. <br><br>Both issues were to do with security not being disabled (and the developer key being overwritten as expected when installing a new build). <br>
<br>The B5 build reacted to security still being enabled by not detecting the USB devices (otherwise it seemed to work fine), whilst the F11 would not boot at all. <br><br>This is probably expected behavior, and I presume only testers or developers ever have to do this, whilst the users (ie. kids or the scarce IT support you would find in rural communities :-) would have signed builds that would not require such a process. Please confirm if that is a valid use-case for the OLPCs.<br>
<br>thanks,<br><br>-- <br>Chamindra de Silva<br>Home:
<a href="http://chamindra-de-silva.blogspot.com">http://chamindra-de-silva.blogspot.com</a><br>Twitter:
<a href="http://twitter.com/ChamindraS">http://twitter.com/ChamindraS</a> (note the last S!)<br><br><br><div class="gmail_quote">On Fri, Mar 26, 2010 at 7:04 PM, Mikus Grinbergs <span dir="ltr"><<a href="mailto:mikus@bga.com">mikus@bga.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">You are using the phrase "updating the XO 1.0". I'm not sure whether by<br>
that word you mean "replace" { in which case you should tell us whether<br>
you are replacing the build version, the kernel (or other system<br>
"package") version, or an Activity ("application") version } -- or<br>
whether by "update" you mean "add more things than were included in the<br>
original distribution". You even mention "we need to ideally start<br>
again from scratch on all tests", which is "replacing" (e.g., by<br>
re-flashing) what you have by a clean version of what you have.<br>
<br>
Please, be specific whenever you say that some kind of "update" does not<br>
work. [What are you changing? What *content* are you using as input ?]<br>
<div class="im"><br>
<br>
> I can confirm that this release seems to have locked this machine. The USB<br>
> is not being detected.<br>
<br>
</div>I have a great deal of difficulty trying to visualize what is happening<br>
to you. I've been using "update the XO-1 from USB" for several years<br>
now, and have NEVER encountered problems. The only two explanations<br>
that come to mind are (1) the particular USB stick(s) that you are using<br>
is defective, or (2) what is actually on that USB stick is not what you<br>
expect to be on that stick (or perhaps you are using procedures/commands<br>
inappropriate to what is on that USB stick).<br>
<br>
So far, I've installed OS802B5.IMG on only one machine -- but that<br>
machine has had no problem "detecting" USB. [By the way, my setup uses<br>
ethernet rather than wireless.] I have a number of XO-1s running<br>
earlier 802B versions - none with USB problems. In a couple days I will<br>
install OS802B5 on several more XO-1 machines -- and will report if I<br>
encounter any problems (but I expect there will be no USB problems).<br>
<br>
I have experienced "locked this machine" very rarely in the past. A<br>
long while ago (but fixed since then) there was a time when beta builds<br>
would not load properly (and could thus be described as "locked up" --<br>
by that I mean "not functioning").<br>
<br>
<br>
If by "locked" you mean that once you installed os802b5 into a machine,<br>
you could not install anything else into that machine -- I've never<br>
experienced that.<br>
<br>
If you would like assistance, please describe "individual action step by<br>
individual action step" (starting from before you pushed the power-on<br>
button) what you did that leads you to say "The USB is not being detected."<br>
<br>
<br>
mikus<br>
<div class="im"><br>
<br>
p.s. Dhanushka Nuwan wrote:<br>
> Tried to update the activities using USB dongle<br>
<br>
</div>That's not how I myself update the activities. Nevertheless, "update<br>
the activities" is only one procedure -- it failing does not for<br>
instance mean that the *system* is not seeing the USB. A command that I<br>
have often found useful is ' ls -la /dev/disk/by-uuid ' -- that will<br>
tell you what storage devices (including USB) the system recognizes.<br>
<br>
I believe "update the activities" ought to work the same way whether on<br>
XO-1.5 or XO-1. If what you are trying works on the XO-1.5 but does not<br>
work on the XO-1, please tell us what the difference is. [For instance,<br>
suppose Journal View on the XO-1.5 shows an icon for the the USB<br>
filesystem, whereas Journal View on the XO-1 does not -- then the<br>
problem ought to be described as "OS802B5 Journal View does not show an<br>
icon for a plugged-in USB" instead of "802B5 seems to have locked this<br>
machine".]<br>
<br>
<br>
pps.<br>
In 2008, the method in <a href="http://wiki.laptop.org/go/Customization_stick" target="_blank">http://wiki.laptop.org/go/Customization_stick</a><br>
would allow me to prepare an USB stick which I used to _add_ Activities<br>
to the XOs of other users in the Austin XO User's Group. I have *not*<br>
tried this method with OS802B5 - but perhaps it would work here as well.<br>
[At worst you will screw up the XO, and have to re-flash it.]<br>
<br>
</blockquote></div><br><br clear="all"><br>