-
Notifications
You must be signed in to change notification settings - Fork 70
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can not load fallback initramfs on nezha #2680
Comments
I think the address space allocated to ramdisk is not enough to store ramdisk. @felixonmars using the configs below boot into kernel, but failed to use initrd, we still try to figure out why.
Edited: Just these configs, doesn't set others to use default value. |
I am not sure why this occurs, as I already enlarged the ramfs size. Maybe hardcode address?
OK, I will try this. |
Results: Not boot, may no built-in sd driver?
only use this gives me a not found fdt.
If set fdt, this kernel with stuck on the starting kernel. It seems the rootfs not found.
extlinux.conf
|
Now It boot into kernel, but not boot into rootfs, Here is the boot.log Maybe need to set |
Any progress? I have confirmed the 6.5-rc4 kernel can boot. The kernel is just built with config |
I've applied changes below to u-boot(d1-wip), but I still cannot boot successfully via extlinux.
However EFI boot with GRUB is improving. Originally(without changes) the boot process will get stuck at I applied When Maybe there are bugs to fix in both u-boot and linux. PS. my hardware is MQ Pro. The decompressed kernel image is about 31MB. |
Apply
There is still a issue related the initramfs. The |
Now it's booting from fallback initramfs to rootfs with these modules in mkinitcpio.conf:
Mods to u-boot:
Kernel cmdline:
I haven't got a usable console yet. Besides I observe no HDMI output for MQ Pro. Attachments: Edit: forgot to mention that I'm still using EFI boot/GRUB. |
Thanks for the investigation. I have successfully booted my D1 with your mentioned modules added to the It seems only the It remains a mystery to me why aren't they loaded automatically given that the u-boot shipped DT nodes clearly mention relevant compatible names. This makes the changes to the |
I try to setup the latest
linux
package on my nezha board. As I setup the rootfs on x86, so I use fallback initramfs to boot the system. But the u-boot seems to fail to allocate data.Is there something I left?
The uboot I use is from here with mainline opensbi.
Boot log:
extlinux.conf
The text was updated successfully, but these errors were encountered: