[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-id: <570F5DEA.1060908@samsung.com>
Date: Thu, 14 Apr 2016 11:07:54 +0200
From: Krzysztof Kozlowski <k.kozlowski@...sung.com>
To: Russell King - ARM Linux <linux@....linux.org.uk>,
Markus Reichl <m.reichl@...etechno.de>
Cc: Kukjin Kim <kgene@...nel.org>,
linux-arm-kernel <linux-arm-kernel@...ts.infradead.org>,
"linux-samsung-soc@...r.kernel.org"
<linux-samsung-soc@...r.kernel.org>, linux-kernel@...r.kernel.org,
linux-mmc@...r.kernel.org,
Javier Martinez Canillas <javier@....samsung.com>,
Bartlomiej Zolnierkiewicz <b.zolnierkie@...sung.com>,
Marek Szyprowski <m.szyprowski@...sung.com>
Subject: Re: [next] Failing Odroid XU3 boot due to missing MMC device
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
Powered by blists - more mailing lists