<span class="gmail_quote"></span>Ok, guys, I've been testing continuously since my last mail.<br>Using the latest existing olpc-auto.zip file, I made it to install 499 and 502 but when I tried 525, 527, 528 it failed again.
<br><br>Could not activate this XO.
<br>Serial Number: SHF7140010D<br><br>I have 256 MB of RAM but maybe my laptop isn't B2 but B1. It had Q2C11 firmware and 2 days ago I upgraded to Q2C18 and first I tried installing XO 528. That's my story. I've read again and again the wiki, I told you I even translated a good part of it in Romanian, is not that. The algorithm presented there doesn't work for me... :(
<br><br>It must be something I can do.<br><span class="sg">Tibi</span><div><span class="e" id="q_113f318665e447dd_2"><br><br><div><span class="gmail_quote">On 7/23/07, <b class="gmail_sendername">Bert Freudenberg</b> <
<a href="mailto:bert@freudenbergs.de" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">bert@freudenbergs.de</a>> wrote:
</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">The auto update boot script supports both nand1234.img and<br>os123456.img naming schemes, both fit into
8.3 FAT.<br><br>Maybe we should use one for dev builds and the other for stable builds.<br><br>> Renaming the installation file does not change the version<br>> number that<br>> is actually stored in the NAND FLASH as a result of the
<br>> installation.<br><br>I thought that was obvious - sorry for not mentioning it, and thanks<br>for spelling it out.<br><br>- Bert -<br><br>On Jul 23, 2007, at 5:57 , Mitch Bradley wrote:<br><br>> Kim Quirk wrote:
<br>>> Thanks Mitch! I didn't know that.<br>>><br>>> Do you think that is the best way to do the downgrade? I already<br>>> changed the Autoreinstallation page to the notes I above. The<br>>> possible problem at the end of the downgrade didn't sound good;
<br>>> and we are going to start using stable release numbers >1000, so<br>>> if you do change it back, please keep that in mind.<br>> I think the rename method is good. It is simple, effective, and safe.
<br>><br>> As Dan points out, you have to both rename the file to e.g.<br>> nand6000.img and change the corresponding number in olpc.fth .<br>><br>> Be sure to respect the 8.3 limitation on the filename - nand60000
<br>> will fail on a FAT filesystem.<br>><br>><br>>><br>>> Thanks,<br>>> Kim<br>>><br>>> On 7/22/07, *Mitch Bradley* <<a href="mailto:wmb@laptop.org" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
wmb@laptop.org</a><br>>> <mailto:
<a href="mailto:wmb@laptop.org" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">wmb@laptop.org</a>>> wrote:<br>>><br>>> Kim Quirk wrote:<br>>> > I don't recommend that your rename your nand to a higher build
<br>>> number
<br>>> > than it actually is just to avoid a downgrade. You may never<br>>> be able<br>>> > to catch up (or catch back down to the proper version).<br>>> ><br>>><br>>> Renaming the installation file does not change the version
<br>>> number that<br>>> is actually stored in the NAND FLASH as a result of the<br>>> installation.<br>>><br>>><br>><br><br><br><br><br>_______________________________________________
<br>Devel mailing list<br><a href="mailto:Devel@lists.laptop.org" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">Devel@lists.laptop.org</a><br><a href="http://lists.laptop.org/listinfo/devel" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
http://lists.laptop.org/listinfo/devel</a><br></blockquote></div><br>
</span></div>