Hello everyone
I am getting an error when setting initramfs load address in config.txt.
The code:-> initramfs initramfs.img load_addr_in_hex
What works :- initramfs initramfs.img followkernel
What are the errors :-
1) Setting memory address after 1gb or sometimes in some addresses gives "rootfs image is not initramfs (junk in compressed archive); looks like an initrd" when kernel tries to unpack initramfs
2) Some address like 200mb, 300mb or even 400mb zone works but after booting xorg stops working and log says it cant find /dev/card*** device. At this stage the CMA changed from 448mb (set in config.txt by dtoverlay=vc4-kms-v3d,cma-448) to 64mb and I think this might be the coz as maybe the initrd address is messing with CMA region which is stopping the vc4 or v3d driver. This problem persists when using u-boot bootloader. Also seen in Manjaro generic arm64 efi image as this image uses tow-boot and grub (image boots but cant access xorg). Generic image uses vanilla kernel.
I tried using uboot to boot raspberrypi kernel (not vanilla kernel) but still the xorg error persists.
Am I putting the address wrong ?
Is there any fix to this problem when using u-boot or using custom initramfs address instead of followkernel ??
I am getting an error when setting initramfs load address in config.txt.
The code:-> initramfs initramfs.img load_addr_in_hex
What works :- initramfs initramfs.img followkernel
What are the errors :-
1) Setting memory address after 1gb or sometimes in some addresses gives "rootfs image is not initramfs (junk in compressed archive); looks like an initrd" when kernel tries to unpack initramfs
2) Some address like 200mb, 300mb or even 400mb zone works but after booting xorg stops working and log says it cant find /dev/card*** device. At this stage the CMA changed from 448mb (set in config.txt by dtoverlay=vc4-kms-v3d,cma-448) to 64mb and I think this might be the coz as maybe the initrd address is messing with CMA region which is stopping the vc4 or v3d driver. This problem persists when using u-boot bootloader. Also seen in Manjaro generic arm64 efi image as this image uses tow-boot and grub (image boots but cant access xorg). Generic image uses vanilla kernel.
I tried using uboot to boot raspberrypi kernel (not vanilla kernel) but still the xorg error persists.
Am I putting the address wrong ?
Is there any fix to this problem when using u-boot or using custom initramfs address instead of followkernel ??
Statistics: Posted by asutosh5941 — Sun Jun 09, 2024 8:17 pm — Replies 1 — Views 57