Hi Phi, On 08/23/2013 01:52 AM, Phi Debian wrote: > Hi Christopher, > I was traveling yesterday, I will resume on this hopefully today.... > > This rootfs.imf is a short rename of standard (downloaded) > decompressed > /home/phi/armv8-dl/vexpress64-openembedded_lamp-armv8_20130719-403.img.gz > > Then > CU82$ file rootfs.img > rootfs.img: x86 boot sector; partition 1: ID=0xe, active, starthead 1, > startsector 63, 106432 sectors; partition 2: ID=0x83, starthead 0, > startsector 106496, 4087808 sectors, code offset 0x0 > > And I can indeed mount the partition #2 and change file in there if > needed later. > For instance adding some .ko that I would have compiled along with my > freshly build kernel.
Do you have virtio block device support properly configured? What kind of virtio-related messages do you see in the kernel log? Christopher > On Thu, Aug 22, 2013 at 5:09 PM, Christopher Covington > <c...@codeaurora.org> wrote: >> Hi Phi, >> >> On 08/22/2013 02:22 AM, Phi Debian wrote: >>> Hi Christopher, >>> >>> Progress!!! giving the full path for FDT_SRC give make(1) success >>> I obtained a linux-system-foundation.axf >>> >>> Note that I build linux-system-foundation.axf this way. >>> >>> make CROSS_COMPILE=aarch64-linux-gnu- BOOTARGS='"root=/dev/vda2 >>> consolelog=9 rw console=ttyAMA0"' >>> FDT_SRC=../linux/arch/arm64/boot/dts/foundation-v8.dts >>> IMAGE=linux-system-foundation.axf >>> >>> Now booting it gives >>> ./Foundation_v8pkg/models/Linux64_GCC-4.1/Foundation_v8 --image >>> ./kbuild/boot-wrapper-aarch64/linux-system-foundation.axf >>> --block-device ./rootfs.img --network=nat >>> >>> Linux version 3.11.0-rc6+ (phi@hpfrcu82) (gcc version 4.8.2 20130624 >>> (prerelease) (crosstool-NG linaro-1.13.1-4.8-2013.07-1 - Linaro GCC >>> 2013.07) ) #1 SMP Wed Aug 21 19:05:06 CEST 2013 >>> CPU: AArch64 Processor [410fd000] revision 0 >>> Machine: Foundation-v8A >>> PERCPU: Embedded 10 pages/cpu @ffffffc87ffaa000 s11392 r8192 d21376 u40960 >>> Built 1 zonelists in Zone order, mobility grouping on. Total pages: 1034240 >>> Kernel command line: root=/dev/vda2 consolelog=9 rw console=ttyAMA0 >>> PID hash table entries: 4096 (order: 3, 32768 bytes) >>> >>> . >>> . >>> . >>> TCP: cubic registered >>> NET: Registered protocol family 17 >>> VFS: Cannot open root device "vda2" or unknown-block(0,0): error -6 >>> Please append a correct "root=" boot option; here are the available >>> partitions: >>> Kernel panic - not syncing: VFS: Unable to mount root fs on >>> unknown-block(0,0) >>> CPU: 0 PID: 1 Comm: swapper/0 Not tainted 3.11.0-rc6+ #1 >>> Call trace: >>> [<ffffffc000087098>] dump_backtrace+0x0/0x12c >>> [<ffffffc0000871d8>] show_stack+0x14/0x1c >>> [<ffffffc0003618b0>] dump_stack+0x70/0x90 >>> [<ffffffc00035efc8>] panic+0xe8/0x208 >>> [<ffffffc00047bd04>] mount_block_root+0x1d8/0x278 >>> [<ffffffc00047bebc>] mount_root+0x118/0x134 >>> [<ffffffc00047c018>] prepare_namespace+0x140/0x188 >>> [<ffffffc00047b958>] kernel_init_freeable+0x1b4/0x1d4 >>> [<ffffffc00035d8b8>] kernel_init+0x18/0x148 >>> >>> So its not an illegal instruction anymore be really a wrong FS, >>> The rootfs.img I used in the runstring is a gunzip of >>> vexpress64-openembedded_lamp-armv8_20130719-403.img.gz >>> >>> Dunno why it can't open /dev/vda2, the --block-device ./rootfs.img seems ok >>> The message Please append a correct "root=" boot option seems strange >>> since the top console log gives >>> Kernel command line: root=/dev/vda2 consolelog=9 rw console=ttyAMA0 >>> >>> Well looks like we are getting closer to boot a newly build OS. >> >> When you run `file rootfs.img` does it start with something like "x86 boot >> sector; partition 1" or "Linux rev 0.0 ext2 filesystem data"? >> >> If it's the latter, the image doesn't have partitions and you'll need to use >> "root=/dev/vda" (no partition number specified). >> >> Regards, >> Christopher >> >> -- >> Employee of Qualcomm Innovation Center, Inc. >> Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, >> hosted by the Linux Foundation. -- Employee of Qualcomm Innovation Center, Inc. Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted by the Linux Foundation. _______________________________________________ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
