<div dir="ltr">David Leeming,<div><br></div><div style>I went ahead, using the 64GB SD, and loaded my current development branch of XSCE on top of the OS 13.1.0 which I loaded via fs-update devalias on xo-1.5 successfully (almost).</div>
<div style><br></div><div style>The almost is probably related to a download error of the ejabberd rpm (it's md5sum did not match upstream). Reloaded, and reinstalled, ejabberd rpm and it functioned as expected.</div>
<div style><br></div><div style>I did not go back and re-install the 0.3 release, because it would be a sidetrack. But I figured you could use the data point. (and that if it failed, I could always look into it further).</div>
<div style><br></div><div style>I do notice that the class 10 SD card seems a little snappier than the storage on the motherboard. James Cameron's comments about all the qualification they did for the SD card on the motherboard seem pertinent. As you proceed, you should probably get a mix of SD cards, and keep track of any failures.</div>
<div style><br></div><div style> I've had difficulty just identifying and serializing my SD cards because any additional stickers rub off, and/or cause the SD card to become stuck in the XO. Jerry noticed that the write protect switch can get toggled. </div>
<div style><br></div><div style>George</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Jun 19, 2013 at 5:25 AM, George Hunt <span dir="ltr"><<a href="mailto:georgejhunt@gmail.com" target="_blank">georgejhunt@gmail.com</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">Thanks James. I always learn a lot from your communications.</div><div class="HOEnZb"><div class="h5"><div class="gmail_extra">
<br><br><div class="gmail_quote">On Tue, Jun 18, 2013 at 7:34 PM, James Cameron <span dir="ltr"><<a href="mailto:quozl@laptop.org" target="_blank">quozl@laptop.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">G'day George,<br>
<div><br>
On Tue, Jun 18, 2013 at 12:27:08PM -0400, George Hunt wrote:<br>
> I followed the suggestions at <a href="http://wiki.laptop.org/go/Release_notes/10.1.0#" target="_blank">http://wiki.laptop.org/go/Release_notes/10.1.0#</a><br>
> External_SD -- substituting 31035o1.zd for the earlier OS64.<br>
><br>
> devalias fsdisk /sd/disk@1:0<br>
> fs-update u:\os64.zd<br>
<br>
</div>I've changed the instructions to read<br>
<br>
devalias fsdisk ext:0<br>
<br>
because it is easier to type, and does the same thing.<br>
<div><br>
> after the reboot, the "df" command indicated rootfs had a size of<br>
> 60GB. I was able to write and read from the command line as olpc and<br>
> as root. So I believe that indicates that 64GB drives do work on the<br>
> XO-1.5. <br>
<br>
</div>Yes, I agree it works on your XO-1.5. It is now more likely that it<br>
will work on other XO-1.5.<br>
<br>
(Now scale it up to a statistically significant sample of 100 units of<br>
XO-1.5 and 100 units of 64 GB SD card? That's the advantage we had<br>
when choosing what device to purchase for production, although we were<br>
using 4 GB microSD cards.)<br>
<div><br>
On Tue, Jun 18, 2013 at 02:58:50PM -0400, George Hunt wrote:<br>
> This is probably a question for James C. I'm concerned that I may<br>
> have invalidated the verification, or at least created misleading<br>
> information.<br>
><br>
> My confession: I couldn't pass up the chance to evolve our<br>
> "prep-storage.sh" script that is part of XSCE before I lost the<br>
> exfat formatting. So I tweaked on our script until it recognized and<br>
> dealt correctly with exfat format. So when I did the "fs-update<br>
> <os.zd>", the 64GB SD card was already formatted ext4.<br>
><br>
> Do you think that a separate formatting step is necessary, or<br>
> irrelevant, to the success of fs-update?<br>
<br>
</div>Irrelevant. fs-update using any of the OLPC OS .zd files will:<br>
<br>
- destroy the partition table and create a new one,<br>
<br>
- destroy any filesystem and create a new one.<br>
<br>
It does this by treating the disk as a series of blocks, and writing<br>
to them an image of a disk that was constructed by the release<br>
engineer.<br>
<br>
In your case, there may be remnant structure of your ext4 filesystem<br>
that may be discovered by forensic analysis of the unwritten blocks on<br>
the card. But this will have no discernable impact on operation.<br>
<div><div><br>
--<br>
James Cameron<br>
<a href="http://quozl.linux.org.au/" target="_blank">http://quozl.linux.org.au/</a><br>
</div></div></blockquote></div><br></div>
</div></div></blockquote></div><br></div>