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 <your image> | 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" <ed.bart...@linux.intel.com> wrote: > > > On Fri, Aug 18, 2017 at 11:40:58AM +0800, Riko wrote: > > > Here's the boot messages : > > > > > > === > > > > > > VFS: PARTUUID= is invalid. > > > Expected PARTUUID=<valid-uuid-id>[/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) > > > [<c010f260>] (unwind_backtrace) from [<c010c11c>] (show_stack+0x20/0x24) > > > [<c010c11c>] (show_stack) from [<c0493068>] (dump_stack+0x20/0x28) > > > [<c0493068>] (dump_stack) from [<c01f20f4>] (panic+0xc0/0x22c) > > > [<c01f20f4>] (panic) from [<c0f013ac>] (mount_block_root+0x19c/0x274) > > > [<c0f013ac>] (mount_block_root) from [<c0f0163c>] (mount_root+0xd0/0x124) > > > [<c0f0163c>] (mount_root) from [<c0f01810>] (prepare_namespace+0x180/ > > 0x1c0) > > > [<c0f01810>] (prepare_namespace) from [<c0f00f3c>] > > > (kernel_init_freeable+0x220/) > > > [<c0f00f3c>] (kernel_init_freeable) from [<c0964fb8>] > > > (kernel_init+0x18/0x11c) > > > [<c0964fb8>] (kernel_init) from [<c01078b8>] (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 -- _______________________________________________ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
