<br><br><div class="gmail_quote">On Mon, Jan 21, 2013 at 4:19 PM, Peter Robinson <span dir="ltr"><<a href="mailto:pbrobinson@gmail.com" target="_blank">pbrobinson@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 class="HOEnZb"><div class="h5"><p dir="ltr"><br>
On 21 Jan 2013 18:47, "Jon" <<a href="mailto:jdisnard@gmail.com" target="_blank">jdisnard@gmail.com</a>> wrote:<br>
><br>
><br>
><br>
> On Mon, Jan 21, 2013 at 5:39 AM, Peter Robinson <<a href="mailto:pbrobinson@gmail.com" target="_blank">pbrobinson@gmail.com</a>> wrote:<br>
>><br>
>> Has anyone else seen issues booting on the Trimslice?<br>
>><br>
>> Basically it boots through but seems unable to fine the rootfs so just hangs.<br>
>><br>
>> <a href="http://www.fpaste.org/itUt/" target="_blank">http://www.fpaste.org/itUt/</a><br>
>><br>
>> Peter<br>
><br>
><br>
><br>
> Yes, the first thing to try is changing to boot.scr to have root=/dev/sda3 or root=/dev/mmcblkop3, or root=LABEL=rootfs<br>
></p>
</div></div><p dir="ltr">My point is this is suppose to just work. I know I can specify labels or partitions instead of uuid but for our supported platforms I shouldn't need to it needs to "just work". This is a blocker, oh and beagle is not better. 2/2 fail!</p>
</blockquote></div><div><br></div>What firmware level is the trimslice?<div>What fedora image was used (link plz)?</div><div><br></div><div>Will attempt to reproduce<br><br clear="all"><div><br></div>-- <br><br>-Jon
</div>