<br><br><div class="gmail_quote">On Mon, Nov 7, 2011 at 10:43 AM, Kevin Gordon <span dir="ltr"><<a href="mailto:kgordon420@gmail.com">kgordon420@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<br><br><div class="gmail_quote"><div class="im">On Mon, Nov 7, 2011 at 9:59 AM, Martin Langhoff <span dir="ltr"><<a href="mailto:martin@laptop.org" target="_blank">martin@laptop.org</a>></span> wrote:<br></div><div class="im">
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>On Mon, Nov 7, 2011 at 9:41 AM, Peter Robinson <<a href="mailto:pbrobinson@gmail.com" target="_blank">pbrobinson@gmail.com</a>> wrote:<br>
> Yes, its coming to F17 as a feature, as I said previously, that<br>
> doesn't mean that Fallback mode is going away in F17.<br>
<br>
</div>There's nothing in that discussion thread about keeping a knob to<br>
enable fallback mode. The title of the thread says it all.<br>
<br>
I was just going to send Ajax your build, I see you're one step ahead<br>
of me :-) -- one thing is missing -- instructions on how to install<br>
it, for someone who's gotten rusty (like Ajax who hasn't updated his<br>
XOs in a while). And the XO-1 install process is different with UBIFS.<br></blockquote></div><div><br>I was fortunate enough to have DSD install an F17 build on an XO 1.5 when in SF. <br><br>So, I'm up for anything you want me to test. I downloaded the xo 1.5 files from <a href="http://build.laptop.org" target="_blank">build.laptop.org</a><br>
</div><div><br>On a new XO 1.5, i just used the same proc as previously for developer build installs:<br><br>boot to OFW, enter 'disable-security' to verify no wp tag so the install doesn't scrub mu ability to boot back into ofw :-)<br>
copy os1.zd4 onto a usb stick<br>insert usb stick into XO 1.5<br>fs-update u:\os1.zd4.<br><br>The 'f'ile updated only 1 chunk' message is back, which means one enters 'reboot', but otherwise things were actually copied correctly.<br>
The firmware updated to Q3B22.<br>It booted with a transient black screen, brings up the little arrow, then goes to sugar arrow and boots into the sugar home screen, but has a little black square on the screen in the bottom left corner.<br>
Switched desktop to gnome. Pretty b/g image, no desktop icons:-)<br>Wireless connected in gnome<br>Switched back to sugar (using menu)<br>Switched bac to sugar, little black square is gone.<br>Wireless network persists on Sugar side :-)<br>
Shutdown from sugar doesnt immediately shutdown. Goes to text mode, seems to go into a loop, then after about 2 minutes finishes the shutdown.<br>Subsequent startup in sugar now does the unexpeceted full black screen transition, and the little black square in the bottom left corner re-appears.<br>
Switch to gnome - being a fool, i cant find the shutdown icon, or an entry on a menu. So, I go to terminal, enter shutdown, it broadcasts a 1 minute delay, message, then shuts down. <br>Reboot brings up prettyboot, then does the black screen transition again, and even on the gnome side, the little black square in the bottom left appears.<br>
That's about all the time I have this morning to play.<br>I'll try the XO-1 once I get home<br><br>Cheers<br><br>KG<br><br>' <br><br><br></div></div></blockquote><div>Further to the above, installed on a second XO 1.5 same results. I knew I could find the shutdown, it's under the user name in the top right corner. Still a fool, but a little less of one.<br>
<br>Also, the screen goes to black after the first dot of the pretty boot comes up - (the o> first dot, not the initial ox first dot.) Not at the end of a pretty boot as previously stated.<br><br>Also 'restart' from sugar also seems to hang up for a minute in text-console land before completely executing.<br>
<br>KG<br> </div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"><div class="gmail_quote"><div><br> <br><br>I dont have an XO-1 with me, but I presume if it's ubifs, the files will also be the same (i.e. os1.onu and os1.uim), adn one will use the update-nand ofw command, instead of the jffs2 copy-nand command. But, I'm presuming that. Will let you know tonight.<span class="HOEnZb"><font color="#888888"><br>
<br>KG<br></font></span></div><div class="im"><blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204, 204, 204);padding-left:1ex">
<div><br>
> What is the state of merging out VIA driver back into mainline? That<br>
> would certainly help from the XO 1.5 PoV.<br>
<br>
</div>That's for Jon to answer...<br>
<div><br>
<br>
<br>
m<br>
--<br>
<a href="mailto:martin@laptop.org" target="_blank">martin@laptop.org</a> -- Software Architect - OLPC<br>
- ask interesting questions<br>
- don't get distracted with shiny stuff - working code first<br>
- <a href="http://wiki.laptop.org/go/User:Martinlanghoff" target="_blank">http://wiki.laptop.org/go/User:Martinlanghoff</a><br>
</div><div><div>_______________________________________________<br>
Devel mailing list<br>
<a href="mailto:Devel@lists.laptop.org" target="_blank">Devel@lists.laptop.org</a><br>
<a href="http://lists.laptop.org/listinfo/devel" target="_blank">http://lists.laptop.org/listinfo/devel</a><br>
</div></div></blockquote></div></div><br>
</blockquote></div><br>