Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754461AbcDNJID (ORCPT ); Thu, 14 Apr 2016 05:08:03 -0400 Received: from mailout1.w1.samsung.com ([210.118.77.11]:10668 "EHLO mailout1.w1.samsung.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753571AbcDNJH6 (ORCPT ); Thu, 14 Apr 2016 05:07:58 -0400 X-AuditID: cbfec7f4-f796c6d000001486-43-570f5deb03d5 Subject: Re: [next] Failing Odroid XU3 boot due to missing MMC device To: Russell King - ARM Linux , Markus Reichl References: <570F5380.7010103@samsung.com> <570F5550.5010708@fivetechno.de> <20160414084530.GS19428@n2100.arm.linux.org.uk> Cc: 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: Krzysztof Kozlowski Message-id: <570F5DEA.1060908@samsung.com> Date: Thu, 14 Apr 2016 11:07:54 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.6.0 MIME-version: 1.0 In-reply-to: <20160414084530.GS19428@n2100.arm.linux.org.uk> Content-type: text/plain; charset=windows-1252 Content-transfer-encoding: 7bit X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrMLMWRmVeSWpSXmKPExsVy+t/xq7qvY/nDDfqnaFtsnLGe1eLN2zVM Fq9fGFr0P37NbLHp8TVWi8u75rBZHPnfz2gx4/w+Jovbl3ktXh75wWix9shddgduj5bmHjaP W3fqPTat6mTz2Lyk3mNL/112j74tqxg9Pm+SC2CP4rJJSc3JLEst0rdL4MrY9raZpeA2e8Wl 3/9ZGhg72LoYOTkkBEwkfny/wwxhi0lcuLceLC4ksJRRoq+Ls4uRC8h+xiixoPsTC0hCWMBV YvLdTawgtohAvMTpe7tZIRpqJY49uMEC0sAs8I9JYumUeWCT2ASMJTYvXwJm8wpoSdy9sAqo gYODRUBV4sICC5CwqECExJO5JxkhSgQlfky+B7aLU8BG4tv2dmaQcmYBPYn7F7VAwswC8hKb 17xlnsAoMAtJxyyEqllIqhYwMq9iFE0tTS4oTkrPNdQrTswtLs1L10vOz93ECImKLzsYFx+z OsQowMGoxMN7YQ1vuBBrYllxZe4hRgkOZiUR3rsx/OFCvCmJlVWpRfnxRaU5qcWHGKU5WJTE eefueh8iJJCeWJKanZpakFoEk2Xi4JRqYOxsebr31xbtY1ObV37cv/WVd6pUwUOfa3OTPj6y rPax4JuyM+3OyfUG3e6blC0it9sfOOxkVPPvzVzmg1GP9nHFOHfXah9WYQli211Y8GvJcQ6m TuVpK6YsuVrsvFq5UG7+scCjIjsKEw3e/Z82VSUq97a09D/b6O2fbCsfiautunF8D6/lbW4l luKMREMt5qLiRAAAREqfhgIAAA== Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 954 Lines: 31 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