Mark Brown broonie@kernel.org writes:
[[PGP Signed Part:Undecided]] On Thu, Feb 22, 2024 at 11:24:59PM -0300, Thiago Jung Bauermann wrote:
Mark Brown broonie@kernel.org writes:
I believe based on prior discussions that you're running this using shrinkwrap - can you confirm exactly how please, including things like which firmware configuration you're using? I'm using current git with
shrinkwrap run \ --rtvar KERNEL=arch/arm64/boot/Image \ --rtvar ROOTFS=${ROOTFS} \ --rtvar CMDLINE="${CMDLINE}" \ --overlay=arch/v9.4.yaml ns-edk2.yaml
and a locally built yocto and everything seems perfectly happy.
Yes, this is how I'm running it:
CMDLINE="Image dtb=fdt.dtb console=ttyAMA0 earlycon=pl011,0x1c090000 root=/dev/vda2 ip=dhcp maxcpus=1"
shrinkwrap run \ --rtvar=KERNEL=Image-gcs-v8-v6.7-rc4-14743-ga551a7d7af93 \
I guess that's bitrotted?
Ah, sorry. When I renamed the Image I messed up the kernel version in the filename, but I did confirm via "uname -r" that I was running the correct version: 6.8.0-rc2-ga551a7d7af93.
My rootfs is Ubuntu 22.04.3. In case it's useful, my kernel config is here:
...
https://people.linaro.org/~thiago.bauermann/gcs/config-v6.8.0-rc2
Thanks, it seems to be something in your config that's making a difference - I can see issues with that. Hopefully that'll help me get to the bottom of this quickly. I spent a bunch of time fighting with Ubuntu images to get them running but once I did they didn't seem to make much difference.
In that case, it's interesting that I still run into the problem with the defconfig. One thing I failed to mention and perhaps is relevant considering your result, is that I didn't copy the modules into the disk image, so the FVP was running just with was built into the kernel.
That was actually the main reason for me to use a custom config: I didn't want to have to deal with kernel modules, so I created a config that didn't have any.