From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.chez-thomas.org (mail.mlbassoc.com [65.100.170.105]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id 1B567E0140A for ; Thu, 13 Dec 2012 03:33:29 -0800 (PST) Received: by mail.chez-thomas.org (Postfix, from userid 1998) id 7F062F81246; Thu, 13 Dec 2012 04:33:28 -0700 (MST) X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on hermes.chez-thomas.org X-Spam-Level: X-Spam-Status: No, score=-2.0 required=4.0 tests=ALL_TRUSTED,BAYES_00, DKIM_ADSP_CUSTOM_MED, FREEMAIL_FROM, NML_ADSP_CUSTOM_MED, T_TO_NO_BRKTS_FREEMAIL autolearn=no version=3.3.2 Received: from [192.168.1.114] (zeus [192.168.1.114]) by mail.chez-thomas.org (Postfix) with ESMTP id B195AF81246; Thu, 13 Dec 2012 04:33:27 -0700 (MST) Message-ID: <50C9BD1D.6010206@gmail.com> Date: Thu, 13 Dec 2012 04:33:49 -0700 From: Gary Thomas User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/17.0 Thunderbird/17.0 MIME-Version: 1.0 To: meta-freescale@yoctoproject.org References: <6846987.PbH0MvyKo8@rudolf> <1871063.4foROqM6CQ@rudolf> <5488991.8kIXbUn0ec@rudolf> In-Reply-To: <5488991.8kIXbUn0ec@rudolf> Subject: Re: Booting imx6q Saber SD X-BeenThere: meta-freescale@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Usage and development list for the meta-fsl-* layers List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Dec 2012 11:33:29 -0000 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit On 2012-12-13 04:28, Thomas Senyk wrote: > On Thu, December 13, 2012 12:13:58 Thomas Senyk wrote: >> On Thu, December 13, 2012 09:07:05 Fabio Estevam wrote: >>> On Thu, Dec 13, 2012 at 9:03 AM, Thomas Senyk >>> >>> wrote: >>>> Hi, >>>> >>>> Yesterday I got a Saber SD (as a second board to my SaberLite). >>>> I've used the imx6qsabresd machine config to create a sdcard. >>>> >>>> uboot and kernel look like they are working, but the rootfs is not >>>> mountable during boot. >>>> >>>> Here is the corresponding kernel output: >>>> >>>> Waiting 2sec before mounting root device... >>>> VFS: Cannot open root device "mmcblk1p2" or unknown-block(179,26) >>>> Please append a correct "root=" boot option; here are the available >>> >>> Do you also have a SD card connected to SD2 slot? If so, can you >>> please remove it and keep only the SD card at slot SD3? >> >> Nop nothing in SD2 > > The opposite (haven the "same" sdcard in both slots) doesn't help either ;) > > VFS: Cannot open root device "mmcblk1p2" or unknown-block(179,26) > Please append a correct "root=" boot option; here are the available > partitions: > b300 7757824 mmcblk0 driver: mmcblk > b310 2048 mmcblk0boot1 (driver?) > b308 2048 mmcblk0boot0 (driver?) > b318 3880960 mmcblk1 driver: mmcblk > b319 8192 mmcblk1p1 00000000-0000-0000-0000-000000000000 > b31a 262144 mmcblk1p2 00000000-0000-0000-0000-000000000000 > b320 7822336 mmcblk2 driver: mmcblk > b321 8192 mmcblk2p1 00000000-0000-0000-0000-000000000000 > b322 262144 mmcblk2p2 00000000-0000-0000-0000-000000000000 > Kernel panic - not syncing: VFS: Unable to mount root fs on unknown- > block(179,26) Could you post the boot log? There should be messages about what MMC devices and partitions are discovered by the kernel which could help. > > I tried to boot from SD2 only. > When switching the DIPs 1 and 2 he loads uboot from SD2, but I can't get > 'fatload mmc' working when booting from SD2