Hi All,
I am trying to boot with the root file system in a ram disk. I would
very much like it to be a Unified boot kernel with the ramdisk image
attached to the kernel. I though I was heading there. First here is the
images produced by Yocto:
-rw-r--r-- 2 johpeters johpeters 6528302 Nov 3 19:57
core-image-minimal-initramfs-yyy-20221103192741.cpio.gz
-rw-r--r-- 2 johpeters johpeters 949 Nov 3 19:57
core-image-minimal-initramfs-yyy-20221103192741.manifest
-rw-r--r-- 2 johpeters johpeters 276765 Nov 3 19:57
core-image-minimal-initramfs-yyy-20221103192741.testdata.json
lrwxrwxrwx 2 johpeters johpeters 59 Nov 3 19:57
core-image-minimal-initramfs-yyy.cpio.gz ->
core-image-minimal-initramfs-yyy-20221103192741.cpio.gz
lrwxrwxrwx 2 johpeters johpeters 60 Nov 3 19:57
core-image-minimal-initramfs-yyy.manifest ->
core-image-minimal-initramfs-yyy-20221103192741.manifest
lrwxrwxrwx 2 johpeters johpeters 65 Nov 3 19:57
core-image-minimal-initramfs-yyy.testdata.json ->
core-image-minimal-initramfs-yyy-20221103192741.testdata.json
-rw-rw-r-- 1 johpeters johpeters 0 Nov 3 22:00 filelist
lrwxrwxrwx 2 johpeters johpeters 71 Nov 3 19:59 Image ->
Image--5.15.68+git0+1128d7bcdc_0e51e57170-r0-yyy-20221103192741.bin
-rw-r--r-- 2 johpeters johpeters 37403136 Nov 3 19:59
Image--5.15.68+git0+1128d7bcdc_0e51e57170-r0-yyy-20221103192741.bin
-rw-r--r-- 2 johpeters johpeters 51493376 Nov 3 19:59
Image-initramfs--5.15.68+git0+1128d7bcdc_0e51e57170-r0-yyy-20221103192741.bin
lrwxrwxrwx 2 johpeters johpeters 81 Nov 3 19:59
Image-initramfs-yyy.bin ->
Image-initramfs--5.15.68+git0+1128d7bcdc_0e51e57170-r0-yyy-20221103192741.bin
lrwxrwxrwx 2 johpeters johpeters 71 Nov 3 19:59 Image-yyy.bin
-> Image--5.15.68+git0+1128d7bcdc_0e51e57170-r0-yyy-20221103192741.bin
-rwxr-xr-x 2 johpeters johpeters 78045 Nov 3 19:43 linuxaa64.efi.stub
-rw-r--r-- 2 johpeters johpeters 1175025425 Nov 3 19:59
modules--5.15.68+git0+1128d7bcdc_0e51e57170-r0-yyy-20221103192741.tgz
lrwxrwxrwx 2 johpeters johpeters 73 Nov 3 19:59 modules-yyy.tgz
-> modules--5.15.68+git0+1128d7bcdc_0e51e57170-r0-yyy-20221103192741.tgz
-rw-r--r-- 2 johpeters johpeters 4978 Nov 3 19:57 yyy-emulation.env
-rw-r--r-- 2 johpeters johpeters 19473626 Nov 3 19:57
yyy-emulation-yyy-20221103192741.rootfs.cpio.gz
-rw-r--r-- 2 johpeters johpeters 4842 Nov 3 19:57
yyy-emulation-yyy-20221103192741.rootfs.manifest
-rw-r--r-- 2 johpeters johpeters 19526312 Nov 3 19:57
yyy-emulation-yyy-20221103192741.rootfs.tar.gz
-rw-r--r-- 2 johpeters johpeters 179201024 Nov 3 20:00
yyy-emulation-yyy-20221103192741.rootfs.wic
-rw-r--r-- 2 johpeters johpeters 272783 Nov 3 19:57
yyy-emulation-yyy-20221103192741.testdata.json
lrwxrwxrwx 2 johpeters johpeters 55 Nov 3 19:57
yyy-emulation-yyy.cpio.gz -> yyy-emulation-yyy-20221103192741.rootfs.cpio.gz
-rw-r--r-- 2 johpeters johpeters 482 Nov 3 19:57
yyy-emulation-yyy-efidisk.wks
lrwxrwxrwx 2 johpeters johpeters 56 Nov 3 19:57
yyy-emulation-yyy.manifest ->
yyy-emulation-yyy-20221103192741.rootfs.manifest
lrwxrwxrwx 2 johpeters johpeters 54 Nov 3 19:57
yyy-emulation-yyy.tar.gz -> yyy-emulation-yyy-20221103192741.rootfs.tar.gz
lrwxrwxrwx 2 johpeters johpeters 54 Nov 3 19:57
yyy-emulation-yyy.testdata.json ->
yyy-emulation-yyy-20221103192741.testdata.json
lrwxrwxrwx 2 johpeters johpeters 51 Nov 3 20:00
yyy-emulation-yyy.wic -> yyy-emulation-yyy-20221103192741.rootfs.wic
-rwxr-xr-x 2 johpeters johpeters 102680 Nov 3 19:43
systemd-bootaa64.efi
I noticed the Image-initramfs--5* file is quite a bit larger than the
Image--5* file. I assumed since it is labeled with "initramfs" the
files for the root image are attached.
However, when I try to boot it, it fails to find the rootfs.img file.
So I added to the FAT32 partition and indeed it does boot but lsbk shows:
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop0 7:0 0 128M 0 loop /
sda 8:0 1 28.9G 0 disk
└─sda1 8:1 1 28.9G 0 part /media/sda1
And losetup:
NAME SIZELIMIT OFFSET AUTOCLEAR RO BACK-FILE DIO LOG-SEC
/dev/loop0 0 0 1 0 /media/sda1/rootfs.img 0 512
Which shows it is mounted loopback to the file and not using a ramdisk.
/proc/cmdline shows there were no kernel command line arguments passed
to the kernel.
I thought I was missing the correct kernel command line parameters but
googling has not found anything useful at this point.
Is my assumption the increased size of the "Image-initramfs" file over
the size of the "Image" file indicates the root ramdisk image is
attached correct?
I am at a loss. Any pointers will be much appreciated,
Johnnie
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#11838):
https://lists.yoctoproject.org/g/linux-yocto/message/11838
Mute This Topic: https://lists.yoctoproject.org/mt/94794770/21656
Group Owner: [email protected]
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-
