From: Krzysztof Kozlowski <k.kozlowski@samsung.com>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>,
Markus Reichl <m.reichl@fivetechno.de>
Cc: Kukjin Kim <kgene@kernel.org>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
"linux-samsung-soc@vger.kernel.org"
<linux-samsung-soc@vger.kernel.org>,
linux-kernel@vger.kernel.org, linux-mmc@vger.kernel.org,
Javier Martinez Canillas <javier@osg.samsung.com>,
Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>,
Marek Szyprowski <m.szyprowski@samsung.com>
Subject: Re: [next] Failing Odroid XU3 boot due to missing MMC device
Date: Thu, 14 Apr 2016 11:07:54 +0200 [thread overview]
Message-ID: <570F5DEA.1060908@samsung.com> (raw)
In-Reply-To: <20160414084530.GS19428@n2100.arm.linux.org.uk>
On 04/14/2016 10:45 AM, Russell King - ARM Linux wrote:
> 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.
Markus, Russell,
Thanks, I'll switch to UUID.
Best regards,
Krzysztof
WARNING: multiple messages have this Message-ID (diff)
From: k.kozlowski@samsung.com (Krzysztof Kozlowski)
To: linux-arm-kernel@lists.infradead.org
Subject: [next] Failing Odroid XU3 boot due to missing MMC device
Date: Thu, 14 Apr 2016 11:07:54 +0200 [thread overview]
Message-ID: <570F5DEA.1060908@samsung.com> (raw)
In-Reply-To: <20160414084530.GS19428@n2100.arm.linux.org.uk>
On 04/14/2016 10:45 AM, Russell King - ARM Linux wrote:
> 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.
Markus, Russell,
Thanks, I'll switch to UUID.
Best regards,
Krzysztof
next prev parent reply other threads:[~2016-04-14 9:07 UTC|newest]
Thread overview: 14+ 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:23 ` Krzysztof Kozlowski
2016-04-14 8:28 ` Jaehoon Chung
2016-04-14 8:28 ` Jaehoon Chung
2016-04-14 9:05 ` Krzysztof Kozlowski
2016-04-14 9:05 ` Krzysztof Kozlowski
2016-04-14 8:31 ` Markus Reichl
2016-04-14 8:31 ` Markus Reichl
2016-04-14 8:45 ` Russell King - ARM Linux
2016-04-14 8:45 ` Russell King - ARM Linux
2016-04-14 8:54 ` Markus Reichl
2016-04-14 8:54 ` Markus Reichl
2016-04-14 9:07 ` Krzysztof Kozlowski [this message]
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=570F5DEA.1060908@samsung.com \
--to=k.kozlowski@samsung.com \
--cc=b.zolnierkie@samsung.com \
--cc=javier@osg.samsung.com \
--cc=kgene@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=m.reichl@fivetechno.de \
--cc=m.szyprowski@samsung.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.