From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by yocto-www.yoctoproject.org (Postfix, from userid 118) id 67ADDE00D61; Mon, 21 Aug 2017 01:32:33 -0700 (PDT) X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on yocto-www.yoctoproject.org X-Spam-Level: X-Spam-Status: No, score=-6.9 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_HI autolearn=ham version=3.3.1 X-Spam-HAM-Report: * -5.0 RCVD_IN_DNSWL_HI RBL: Sender listed at http://www.dnswl.org/, high * trust * [134.134.136.24 listed in list.dnswl.org] * -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% * [score: 0.0000] Received: from mga09.intel.com (mga09.intel.com [134.134.136.24]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id 6D6D3E00BBF for ; Mon, 21 Aug 2017 01:32:32 -0700 (PDT) Received: from fmsmga002.fm.intel.com ([10.253.24.26]) by orsmga102.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 21 Aug 2017 01:32:31 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.41,408,1498546800"; d="scan'208";a="1208282373" Received: from linux.intel.com ([10.54.29.200]) by fmsmga002.fm.intel.com with ESMTP; 21 Aug 2017 01:32:28 -0700 Received: from linux.intel.com (vmed.fi.intel.com [10.237.72.38]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by linux.intel.com (Postfix) with ESMTPS id B87165805B3; Mon, 21 Aug 2017 01:32:25 -0700 (PDT) Date: Mon, 21 Aug 2017 11:08:23 +0300 From: Ed Bartosh To: Riko Ho Message-ID: <20170821080823.GA17975@linux.intel.com> References: <1502979391.28682.1.camel@linux.intel.com> <3e39f3ca-9228-769f-0b39-126fb124d280@gmail.com> <20170818085833.GA6976@linux.intel.com> MIME-Version: 1.0 In-Reply-To: Organization: Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo User-Agent: Mutt/1.5.21 (2010-09-15) Cc: "yocto@yoctoproject.org" Subject: Re: dd to nand flash chip? X-BeenThere: yocto@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: ed.bartosh@linux.intel.com List-Id: Discussion of all things Yocto Project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Aug 2017 08:32:33 -0000 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit Hi Riko, Sorry for this confusion. You can see used wks file On Fri, Aug 18, 2017 at 07:56:46PM +0800, Riko Ho wrote: > I'm confused, what is wks ? what layers do you want to know? Sorry for the confusion. You can read about wic and wks in the documentation: To understand which wks file was used to build your .wic image you can run this command: bitbake -e | grep ^WKS_FILE= > what layers do you want to know? all of them :) Please, show me the output of 'cat conf/bblayers.conf' > I was bitbaking core image minimal xfce. looks like you're using meta-xfce layer. > How can I see my bootloader config? You can mount your boot partition and see it there. Something like this: # kpartx -va ./tmp/deploy/images/qemux86-64/core-image-minimal-qemux86-64.wic add map loop2p1 (254:3): 0 46896 linear /dev/loop2 2048 add map loop2p2 (254:4): 0 49568 linear /dev/loop2 49152 # mount /dev/mapper/loop2p1 /mnt/ # cat /mnt/syslinux.cfg PROMPT 0 TIMEOUT 0 ALLOWOPTIONS 1 SERIAL 0 115200 DEFAULT boot LABEL boot KERNEL /vmlinuz APPEND label=boot root=/dev/mmcblk1p2 rootwait rootfstype=ext4 video=vesafb vga=0x318 console=tty0 console=ttyS0,115200n8 Note, that your image may have different bootloader. > Thanks and regards, > Riko > On Aug 18, 2017 5:22 PM, "Ed Bartosh" wrote: > > > On Fri, Aug 18, 2017 at 11:40:58AM +0800, Riko wrote: > > > Here's the boot messages : > > > > > > === > > > > > > VFS: PARTUUID= is invalid. > > > Expected PARTUUID=[/PARTNROFF=%d] > > > Disabling rootwait; root= is invalid. > > > VFS: Cannot open root device "PARTUUID=" or unknown-block(0,0): error -6 > > > > Looks like you have empty PARTUUID in the kernel command line. Which wks > > file do you use for this image? Which layers? Can you show your > > bootloader config? > > > > > Please append a correct "root=" boot option; here are the available > > > partitions: > > > 0100 4096 ram0 (driver?) > > > 0101 4096 ram1 (driver?) > > > 0102 4096 ram2 (driver?) > > > 0103 4096 ram3 (driver?) > > > 0104 4096 ram4 (driver?) > > > 0105 4096 ram5 (driver?) > > > 0106 4096 ram6 (driver?) > > > 0107 4096 ram7 (driver?) > > > 0108 4096 ram8 (driver?) > > > 0109 4096 ram9 (driver?) > > > 010a 4096 ram10 (driver?) > > > 010b 4096 ram11 (driver?) > > > 010c 4096 ram12 (driver?) > > > 010d 4096 ram13 (driver?) > > > 010e 4096 ram14 (driver?) > > > 010f 4096 ram15 (driver?) > > > b300 3735552 mmcblk1 driver: mmcblk > > > b301 16384 mmcblk1p1 2848be0f-01 > > > b302 756704 mmcblk1p2 2848be0f-02 > > > b310 4096 mmcblk1boot1 (driver?) > > > b308 4096 mmcblk1boot0 (driver?) > > > VFS: Unable to mount root fs on unknown-block(0,0) > > > User configuration error - no valid root filesystem found > > > Kernel panic - not syncing: Invalid configuration from end user > > > prevents conting > > > CPU: 0 PID: 1 Comm: swapper Not tainted 4.8.12-yocto-standard #3 > > > Hardware name: Generic AM33XX (Flattened Device Tree) > > > [] (unwind_backtrace) from [] (show_stack+0x20/0x24) > > > [] (show_stack) from [] (dump_stack+0x20/0x28) > > > [] (dump_stack) from [] (panic+0xc0/0x22c) > > > [] (panic) from [] (mount_block_root+0x19c/0x274) > > > [] (mount_block_root) from [] (mount_root+0xd0/0x124) > > > [] (mount_root) from [] (prepare_namespace+0x180/ > > 0x1c0) > > > [] (prepare_namespace) from [] > > > (kernel_init_freeable+0x220/) > > > [] (kernel_init_freeable) from [] > > > (kernel_init+0x18/0x11c) > > > [] (kernel_init) from [] (ret_from_fork+0x14/0x3c) > > > ---[ end Kernel panic - not syncing: Invalid configuration from end > > > user preveng > > > > > > ===== > > > > > > How to fix it ? thanks > > > > > > > > > On 17/08/17 22:16, Leonardo Sandoval wrote: > > > >On Thu, 2017-08-17 at 18:37 +0800, Riko Ho wrote: > > > >>Dear Yocto Team Members， > > > >> > > > >>I tried to dd *.wic to nand flash but always got kernel panic, it can > > > >>not find rootfs > > > >>when I dd the same file to sd card, it worked. > > > >> > > > >from the bootloader command prompt, you may need to change the root > > > >kernel parameter and point to the device where the filesystem resides. > > > > > > > > > > > >>I copy only *.wic file to usb drive n dd it. > > > >>Do I need the whole directory of images for dd? or I need hddimg? > > > >> > > > >>Regards, > > > >>Riko > > > >> > > > > > > > > > > -- > > > /***** > > > Sent By > > > Ubuntu 16.04 LTS > > > Kernel 4.4.0-92-generic > > > Regards, > > > Riko H > > > *****/ > > > > > > -- > > > _______________________________________________ > > > yocto mailing list > > > yocto@yoctoproject.org > > > https://lists.yoctoproject.org/listinfo/yocto > > > > -- > > -- > > Regards, > > Ed > > -- -- Regards, Ed