On 26 February 2018 at 06:34, Giordon Stark <kra...@gmail.com> wrote: > Hi all, I'm using a zynqmp 102 chip: > > I used the wic file created to flash an SD card using dd. I also copied > system.dtb and created a BOOT.bin to copy into the first (boot) partition. > However, the SD card seems readable, and shows the right partitions.. but I > still cannot get the kernel to load the FS from it? > > Any ideas? > > [ 6.983061] Waiting for root device /dev/mmcblk0p2... > [ 7.244076] mmc0: new high speed SDXC card at address 59b4 > [ 7.249846] mmcblk0: mmc0:59b4 SD 58.9 GiB (ro)
Its mounted read only. Check the card, and the preceding log (there might be information regarding why it was mounted read only). > [ 7.255864] mmcblk0: p1 p2 > [ 7.341815] VFS: Cannot open root device "mmcblk0p2" or > unknown-block(179,2): error -30 Error read only. If you want to mount it read only make sure to pass the "ro" flag in your boot args. Regards, Nathan > [ 7.349751] Please append a correct "root=" boot option; here are the > available partitions: > [ 7.358115] 0100 65536 ram0 [ 7.361627] (driver?) > [ 7.363996] 0101 65536 ram1 [ 7.367529] (driver?) > [ 7.369880] 0102 65536 ram2 [ 7.373446] (driver?) > [ 7.375782] 0103 65536 ram3 [ 7.379334] (driver?) > [ 7.381697] 0104 65536 ram4 [ 7.385236] (driver?) > [ 7.387587] 0105 65536 ram5 [ 7.391139] (driver?) > [ 7.393503] 0106 65536 ram6 [ 7.397041] (driver?) > [ 7.399392] 0107 65536 ram7 [ 7.402956] (driver?) > [ 7.405295] 0108 65536 ram8 [ 7.408846] (driver?) > [ 7.411196] 0109 65536 ram9 [ 7.414762] (driver?) > [ 7.417100] 010a 65536 ram10 [ 7.420738] (driver?) > [ 7.423100] 010b 65536 ram11 [ 7.426727] (driver?) > [ 7.429078] 010c 65536 ram12 [ 7.432727] (driver?) > [ 7.435067] 010d 65536 ram13 [ 7.438706] (driver?) > [ 7.441056] 010e 65536 ram14 [ 7.444706] (driver?) > [ 7.447046] 010f 65536 ram15 [ 7.450684] (driver?) > [ 7.453051] b300 61766656 mmcblk0 [ 7.456848] driver: mmcblk > [ 7.459632] b301 31159 mmcblk0p1 22568d5b-01[ 7.464767] > [ 7.466227] b302 161078 mmcblk0p2 22568d5b-02[ 7.471344] > [ 7.472837] Kernel panic - not syncing: VFS: Unable to mount root fs on > unknown-block(179,2) > [ 7.481257] CPU: 3 PID: 1 Comm: swapper/0 Not tainted > 4.9.0-xilinx-v2017.1 #1 > [ 7.488364] Hardware name: xlnx,zynqmp (DT) > [ 7.492528] Call trace: > [ 7.494965] [<ffffff8008088440>] dump_backtrace+0x0/0x198 > [ 7.500345] [<ffffff80080885ec>] show_stack+0x14/0x20 > [ 7.505379] [<ffffff80083e7f70>] dump_stack+0x90/0xb0 > [ 7.510414] [<ffffff800813461c>] panic+0x110/0x258 > [ 7.515188] [<ffffff8008c210f4>] mount_block_root+0x198/0x270 > [ 7.520916] [<ffffff8008c21408>] mount_root+0x11c/0x134 > [ 7.526123] [<ffffff8008c21590>] prepare_namespace+0x170/0x1b8 > [ 7.531939] [<ffffff8008c20d20>] kernel_init_freeable+0x1c0/0x1e0 > [ 7.538016] [<ffffff800892d690>] kernel_init+0x10/0x100 > [ 7.543223] [<ffffff8008082e80>] ret_from_fork+0x10/0x50 > [ 7.548516] SMP: stopping secondary CPUs > [ 7.585970] Kernel Offset: disabled > [ 7.589380] Memory Limit: none > [ 7.592425] ---[ end Kernel panic - not syncing: VFS: Unable to mount > root fs on unknown-block(179,2) > > -- > Giordon Stark > > -- > _______________________________________________ > meta-xilinx mailing list > meta-xilinx@yoctoproject.org > https://lists.yoctoproject.org/listinfo/meta-xilinx > -- _______________________________________________ meta-xilinx mailing list meta-xilinx@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-xilinx
