On Fri, Oct 31, 2014 at 1:48 PM, Brian Kambach <bkambach(a)i-a-i.com> wrote:
Thanks Peter. F21 does work much more easily, although I still had
to do the DTB appending thing.
Yes, unfortunately you still need to do that because the uboot is
ancient and doesn't support it. At the moment that's out of our
control but I think before long upstream uboot will have support for
it at which point we might be able to look at providing a uboot to
flash onto the device but only time will tell there
From: Peter Robinson [mailto:email@example.com]
Sent: Friday, October 31, 2014 7:02 AM
To: Brian Kambach
Subject: Re: [fedora-arm] F20 on Mirabox
On Thu, Oct 30, 2014 at 8:50 PM, Brian Kambach <bkambach(a)i-a-i.com> wrote:
> Does anyone have instructions for getting the stock F20 image to run
> on a Mirabox?
> I’m attempting to use the “Fedora-Minimal-armhfp-20-1-sda.raw.xz”
> image on an SD card. I initially tried booting the image as-is, but
> it simply hung at “Starting kernel …”. Following some old
> instructions in this mailing list for F19 from Jon Masters, I appended
> the “armada-370-mirabox.dtb” to the end of the uImage, which gets much further, but
> [ OK ] Started Show Plymouth Boot Screen.
> [ OK ] Reached target Paths.
> [ OK ] Reached target Basic System.
> [ 203.390737] dracut-initqueue: Warning: Could not boot.
> [ 203.432165] dracut-initqueue: Warning: /dev/sdb3 does not
> So, it obviously can’t find the real root filesystem, but I don’t know
> how to remedy this. Any ideas?
It's missing the usb driver from from the initrd. It may even have been missing the
usb driver entirely in the F-20 GA release as I discovered both issues around the same
time but I don't remember exactly when that was.
So to get it running on F-20 you'd likely need to pull in a newer kernel/dracut and
regenerate the initrd. I've never run F-20 on my Mirabox but it's running F-21
really well so TBH I'd grab the latest
F-21 Beta RC and go with that as it's very solid on the Mirabox.
This message and all attachments are PRIVATE, and contain information that is PROPRIETARY
to Intelligent Automation, Inc. You are not authorized to transmit or otherwise disclose
this message or any attachments to any third party whatsoever without the express written
consent of Intelligent Automation, Inc. If you received this message in error or you are
not willing to view this message or any attachments on a confidential basis, please
immediately delete this email and any attachments and notify Intelligent Automation, Inc.