-
Notifications
You must be signed in to change notification settings - Fork 417
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
raspberrypi4-64 kirkstone linux 6.1 image stuck on boot logos #1285
Comments
It might be unrelated to your issue, but today I've noticed that the default /boot partition is only 20MB: wic/sdimage-raspberrypi.wks:part /boot --source bootimg-partition --ondisk mmcblk0 --fstype=vfat --label boot --active --align 4096 --size 20 and the kernel image is bigger than that: with webOS OSE we're using own .wks file with 80MB /boot, but I wonder how it works for other people who might be using the default .wks file from this layer, is it extended so that it fits during the boot and then you don't need to ever write to /boot? |
@shr-project regardless, this should be fixed. Can you send a patch to raise it to 100M? |
Looks like it is increased automatically:
"--size 20M" is just minimum (our wks uses "--fixed-size 80M"): https://docs.yoctoproject.org/ref-manual/kickstart.html
|
I have gotten the 6.1 kernel to boot using a fresh yocto build. I can confirm 6.1.61 running well on raspberrypi4-64 board. Thanks! |
Description
Thanks to the backport of raspberrypi5 to kirkstone, we now have a 6.1 kernel available.
I tried to upgrade a raspberrypi4-64 image to use linux 6.1.
I am using u-boot. I can see the u-boot output up to Starting kernel ..., then the screen gets stuck on the pi logos and there is no kernel logs. Also, the green LED activity stops immediately.
I am guessing the kernel boots but stops very early in the process.
Any suggestions on how to diagnose this further?
The text was updated successfully, but these errors were encountered: