From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [next] Failing Odroid XU3 boot due to missing MMC device
Date: Thu, 14 Apr 2016 09:45:30 +0100 [thread overview]
Message-ID: <20160414084530.GS19428@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <570F5550.5010708@fivetechno.de>
On Thu, Apr 14, 2016 at 10:31:12AM +0200, Markus Reichl wrote:
> Hi Krzysztof,
>
> yes, observed this with linux-next from yesterday 13.
>
> I boot from eMMC.
> Device numbering of eMMC and SD are exchanged now.
>
> I solved the boot problem by changing the rootdev in U-Boot env
> from /dev/mmcblk0p2 to /dev/mmcblk1p2.
>
> Changed /etc/fdisk, too, to mount /dev/mmcblk1p1 to /boot.
You really should mount by partition uuid - supplying something like:
root=PARTUUID=f3ae567e-02
on the kernel command line. This makes the mounting of rootfs
independent of which device carries the filesystem.
If you're not using an initramfs, the kernel prints the partuuid
values if it doesn't find the rootfs. I don't know how to get the
partuuids without going through that process, sorry.
--
RMK's Patch system: http://www.arm.linux.org.uk/developer/patches/
FTTC broadband for 0.8mile line: currently at 9.6Mbps down 400kbps up
according to speedtest.net.
next prev parent reply other threads:[~2016-04-14 8:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-14 8:23 [next] Failing Odroid XU3 boot due to missing MMC device Krzysztof Kozlowski
2016-04-14 8:28 ` Jaehoon Chung
2016-04-14 9:05 ` Krzysztof Kozlowski
2016-04-14 8:31 ` Markus Reichl
2016-04-14 8:45 ` Russell King - ARM Linux [this message]
2016-04-14 8:54 ` Markus Reichl
2016-04-14 9:07 ` Krzysztof Kozlowski
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160414084530.GS19428@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=linux-arm-kernel@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).