August 28, 20251 yr Hi, I'm trying to build for the Rock 3C so that I can minimize what goes into the kernel and system. I'm new at this and tried mostly default values (current, bookworm), except that I did minimal image instead of standard. The build failed at applying a patch. I don't know what to do with that. Can anyone help me diagnose? Also, how would I get into more details about building the image and choosing what to add/remove? Thanks!
August 28, 20251 yr Author Thank you for the reply and suggestion. I tried trixie and got the same error with the same patch. I guess I can't tell it to skip VP9? Edited August 28, 20251 yr by CeeGO
August 28, 20251 yr Solution a fix was just merged for Rockchip, update your repo and try again, maybe you are lucky
August 28, 20251 yr Yes, I am fairly confident you were experiencing one of these two https://github.com/armbian/build/pull/8554 https://github.com/armbian/build/pull/8555
August 28, 20251 yr Happy to report that "./compile.sh build BOARD=rock-3c BRANCH=current BUILD_DESKTOP=no BUILD_MINIMAL=yes KERNEL_CONFIGURE=no RELEASE=bookworm SHARE_LOG=yes" builds fine for me now.
August 29, 20251 yr Author Looks good! Thank you. What's the best way to get start customizing the build?
August 29, 20251 yr 2 hours ago, CeeGO said: What's the best way to get start customizing the build? Easiest way is to use the customize-image.sh file in userpatches. Stuff there gets executed within chroot on the sdcard just before its closed and assembled. More advanced way is using extensions. Check extensions folder for examples.
August 30, 20251 yr Author On 8/28/2025 at 9:34 PM, Werner said: Easiest way is to use the customize-image.sh file in userpatches. Stuff there gets executed within chroot on the sdcard just before its closed and assembled. More advanced way is using extensions. Check extensions folder for examples. Thanks. I'll have to look into that. I expect that's for customizing the packages installed? Edited August 30, 20251 yr by CeeGO
August 30, 20251 yr Customizing image and customizing kernel are different tasks. For latter use the kernel-config command and then copy over the created config file from output to userpatches. The framework will look for custom kernel configuration files and uses them if they're detected. More details here: https://zuckerbude.org/armbian-using-kernel-config/
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.