hi team,
I have a customer trying to use a ramdisk FS but is having issues getting everything up and running. This is something that the customer had not done previously so Im trying to ease them into the process by providing something from the 3 day workshop (from the TTO) and sets up a ramdisk in a controlled environment.
As for their own ramdisk FS, I (and the customer) are under the impression that using lsinitramfs would be the proper way to validate the ramdisk image but this does not appear to be the case. Is there another option/better option for validating? I keep seeing CPIO errors, even using the TTO's pre-made image.
Also, they previously attempted to use mkimage to create the FS.
$(QUIET)$(MKIMAGE) -A arm -T ramdisk -C gzip \ -n "my filesystem" \ -a 82000000 -e 82000000 \ -d fs.gz fs.img
They're wondering about the requirement of setting the load and exec addresses. To my understanding load and execute addresses would be set by the Uboot args and so they should not need to be set on the ramdisk build. They're also wondering on how much room do they need to keep away from Linux load which is at 81000000.
With their last attempt, this was the output on the console
[ 2.264617] RAMDISK: Couldn't find valid RAM disk image starting at 0. [ 2.285705] mmc1: queuing unknown CIS tuple 0x91 (3 bytes) [ 2.296173] List of all partitions: [ 2.299865] 1f00 128 mtdblock0 (driver?) [ 2.305145] 1f01 128 mtdblock1 (driver?) [ 2.310455] 1f02 128 mtdblock2 (driver?) [ 2.315734] 1f03 128 mtdblock3 (driver?) [ 2.321014] 1f04 1920 mtdblock4 (driver?) [ 2.326293] 1f05 128 mtdblock5 (driver?) [ 2.331573] 1f06 5120 mtdblock6 (driver?) [ 2.336853] 1f07 254464 mtdblock7 (driver?) [ 2.342102] No filesystem could mount root, tried: ext3 ext2 cramfs vfat msdos [ 2.349761] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(1,0) [ 2.358367] Backtrace: [ 2.360961] [] (dump_backtrace+0x0/0x10c) from [] (dump_stack+0x18/0x1c) [ 2.369781] r7:c0525e10 r6:00008000 r5:c0673bc8 r4:c0673bc8 [ 2.375701] [] (dump_stack+0x0/0x1c) from [] (panic+0x64/0x198) [ 2.383697] [] (panic+0x0/0x198) from [] (mount_block_root+0x1e8/0x228) [ 2.392425] r3:00000000 r2:c701df58 r1:c701df58 r0:c0525ec0 [ 2.398345] [] (mount_block_root+0x0/0x228) from [] (mount_root+0xb0/0xcc) [ 2.407348] [] (mount_root+0x0/0xcc) from [] (prepare_namespace+0x168/0x1c0) [ 2.416503] r4:c0670f20 [ 2.419158] [] (prepare_namespace+0x0/0x1c0) from [] (kernel_init+0xf0/0x124) [ 2.428436] r5:c0604548 r4:c0670ec0 [ 2.432189] [] (kernel_init+0x0/0x124) from [] (do_exit+0x0/0x69c) [ 2.264617] RAMDISK: Couldn't find valid RAM disk image starting at 0. [ 2.285705] mmc1: queuing unknown CIS tuple 0x91 (3 bytes) [ 2.296173] List of all partitions: [ 2.299865] 1f00 128 mtdblock0 (driver?) [ 2.305145] 1f01 128 mtdblock1 (driver?) [ 2.310455] 1f02 128 mtdblock2 (driver?) [ 2.315734] 1f03 128 mtdblock3 (driver?) [ 2.321014] 1f04 1920 mtdblock4 (driver?) [ 2.326293] 1f05 128 mtdblock5 (driver?) [ 2.331573] 1f06 5120 mtdblock6 (driver?) [ 2.336853] 1f07 254464 mtdblock7 (driver?) [ 2.342102] No filesystem could mount root, tried: ext3 ext2 cramfs vfat msdos [ 2.349761] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(1,0) [ 2.358367] Backtrace: [ 2.360961] [] (dump_backtrace+0x0/0x10c) from [] (dump_stack+0x18/0x1c) [ 2.369781] r7:c0525e10 r6:00008000 r5:c0673bc8 r4:c0673bc8 [ 2.375701] [] (dump_stack+0x0/0x1c) from [] (panic+0x64/0x198) [ 2.383697] [] (panic+0x0/0x198) from [] (mount_block_root+0x1e8/0x228) [ 2.392425] r3:00000000 r2:c701df58 r1:c701df58 r0:c0525ec0 [ 2.398345] [] (mount_block_root+0x0/0x228) from [] (mount_root+0xb0/0xcc) [ 2.407348] [] (mount_root+0x0/0xcc) from [] (prepare_namespace+0x168/0x1c0) [ 2.416503] r4:c0670f20 [ 2.419158] [] (prepare_namespace+0x0/0x1c0) from [] (kernel_init+0xf0/0x124) [ 2.428436] r5:c0604548 r4:c0670ec0 [ 2.432189] [] (kernel_init+0x0/0x124) from [] (do_exit+0x0/0x69c)
Thank you for any insight you can offer.