Unable to compile "noble" for Rockpi 4b

[CeeGO]

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!

[laibsch]

First suggestion: try trixie or noble instead of bookworm

[CeeGO]

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 Thursday at 09:02 PM by CeeGO

[laibsch]

let me have a closer look after I successfully unsuccessfully compile this

[laibsch]

a fix was just merged for Rockchip, update your repo and try again, maybe you are lucky

[laibsch]

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

[laibsch]

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.

[CeeGO]

Great! Thank you. I will try it.

[CeeGO]

Looks good! Thank you.

 

What's the best way to get start customizing the build?

[Werner]

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.

[CeeGO]

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 57 minutes ago by CeeGO

[Werner]

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/