Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754757AbcDNIzJ (ORCPT ); Thu, 14 Apr 2016 04:55:09 -0400 Received: from wp126.webpack.hosteurope.de ([80.237.132.133]:35349 "EHLO wp126.webpack.hosteurope.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753408AbcDNIzH (ORCPT ); Thu, 14 Apr 2016 04:55:07 -0400 Subject: Re: [next] Failing Odroid XU3 boot due to missing MMC device To: Russell King - ARM Linux References: <570F5380.7010103@samsung.com> <570F5550.5010708@fivetechno.de> <20160414084530.GS19428@n2100.arm.linux.org.uk> Cc: Krzysztof Kozlowski , Kukjin Kim , linux-arm-kernel , "linux-samsung-soc@vger.kernel.org" , linux-kernel@vger.kernel.org, linux-mmc@vger.kernel.org, Javier Martinez Canillas , Bartlomiej Zolnierkiewicz , Marek Szyprowski From: Markus Reichl Organization: five technologies GmbH Message-ID: <570F5ADE.1010500@fivetechno.de> Date: Thu, 14 Apr 2016 10:54:54 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.7.0 MIME-Version: 1.0 In-Reply-To: <20160414084530.GS19428@n2100.arm.linux.org.uk> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-bounce-key: webpack.hosteurope.de;m.reichl@fivetechno.de;1460624106;84966052; Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 911 Lines: 28 Am 14.04.2016 um 10:45 schrieb Russell King - ARM Linux: > 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. lsblk --output PARTUUID >