Jump to content

Artifact cache supresses KERNEL_CONFIGURE


Recommended Posts

I'm having trouble trying to do a custom kernel configuration using this image on my hc4. It's just not opening menuconfig, I get the screen to select the board ( odroid hc4), then the LTS/Edge kernel screen, then this is the only output:

ย 

~/build$ ./compile.sh BOARD=odroidhc4 BRANCH=current BUILD_MINIMAL=no BUILD_DESKTOP=no KERNEL_ONLY=yes KERNEL_CONFIGURE=yes COMPRESS_OUTPUTIMAGE=sha,img
[๐ŸŒฟ] Applying cmdline param [ 'BUILD_MINIMAL': '(empty)' --> 'no' early ]
[๐ŸŒฟ] Applying cmdline param [ 'COMPRESS_OUTPUTIMAGE': '(empty)' --> 'sha,img' early ]
[๐ŸŒฟ] Applying cmdline param [ 'BUILD_DESKTOP': '(empty)' --> 'no' early ]
[๐ŸŒฟ] Applying cmdline param [ 'BRANCH': '(empty)' --> 'current' early ]
[๐ŸŒฟ] Applying cmdline param [ 'BOARD': '(empty)' --> 'odroidhc4' early ]
[๐ŸŒฟ] Applying cmdline param [ 'KERNEL_ONLY': '(empty)' --> 'yes' early ]
[๐ŸŒฟ] Applying cmdline param [ 'KERNEL_CONFIGURE': '(empty)' --> 'yes' early ]
[๐Ÿšธ] This script requires root privileges; Docker is unavailable [ trying to use sudo ]
[๐ŸŒฟ] Applying cmdline param [ 'PREFER_DOCKER': '(empty)' --> 'no' early ]
[๐ŸŒฟ] Applying cmdline param [ 'BUILD_MINIMAL': '(empty)' --> 'no' early ]
[๐ŸŒฟ] Applying cmdline param [ 'COMPRESS_OUTPUTIMAGE': '(empty)' --> 'sha,img' early ]
[๐ŸŒฟ] Applying cmdline param [ 'BUILD_DESKTOP': '(empty)' --> 'no' early ]
[๐ŸŒฟ] Applying cmdline param [ 'ARMBIAN_RELAUNCHED': '(empty)' --> 'yes' early ]
[๐ŸŒฟ] Applying cmdline param [ 'BRANCH': '(empty)' --> 'current' early ]
[๐ŸŒฟ] Applying cmdline param [ 'BOARD': '(empty)' --> 'odroidhc4' early ]
[๐ŸŒฟ] Applying cmdline param [ 'SET_OWNER_TO_UID': '(empty)' --> '1000' early ]
[๐ŸŒฟ] Applying cmdline param [ 'KERNEL_ONLY': '(empty)' --> 'yes' early ]
[๐ŸŒฟ] Applying cmdline param [ 'KERNEL_CONFIGURE': '(empty)' --> 'yes' early ]
[๐ŸŒฑ] Starting single build process [ odroidhc4 ]
[๐ŸŒฑ] Checking [ basic host setup ]
[๐ŸŒฑ] Build host OS release [ jammy ]
[๐ŸŒฑ] Build host architecture [ arm64 ]
[๐ŸŒฑ] Sourcing board configuration [ /home/steve/build/config/boards/odroidhc4.conf ]
[๐ŸŒฑ] Starting main configuration
[๐ŸŒฑ] Sourcing family configuration [ /home/steve/build/config/sources/families/meson-sm1.conf ]
[๐ŸŒฑ] Sourcing arch configuration [ arm64.conf ]
[๐ŸŒฑ] Extension manager [ processed 4 Extension Methods calls and 4 Extension Method implementations ]
[๐ŸŒฑ] Configuration prepared for BOARD build [ odroidhc4.conf ]
[โœจ] Repeat Build Options (early) [ ./compile.sh BOARD=odroidhc4 BRANCH=current BUILD_MINIMAL=no BUILD_DESKTOP=no KERNEL_ONLY=yes KERNEL_CONFIGURE=yes COMPRESS_OUTPUTIMAGE=sha,img ]
[๐ŸŒฑ] Checked directory OK for mount options [ /home/steve/build/.tmp ('main temporary dir') ]
[๐ŸŒฑ] Preparing [ host ]
[๐ŸŒฑ] Syncing clock [ host ]
[๐Ÿ”จ] ย  ย 4 Mar 18:52:16 ntpdate[41836]: adjust time server 38.229.56.9 offset -0.001440 sec
[๐ŸŒฑ] artifact [ uboot :: uboot() ]
[๐ŸŒฑ] Using cached [ GIT_INFO_UBOOT ]
[๐Ÿ’–] artifact [ present in local cache: uboot-odroidhc4-current 2023.01-S62e2-P1cd3-B680b ]
[๐ŸŒฑ] artifact [ kernel :: kernel() ]
[๐ŸŒฑ] Using cached [ GIT_INFO_KERNEL ]
[๐ŸŒฑ] Using kernel config file [ config/kernel/linux-meson64-current.config ]
[๐Ÿ’–] artifact [ present in local cache: kernel-meson64-current 6.1.15-S4261-De511-Pb8ce-C072bHfe66-Bb436 ]
[๐ŸŒฑ] artifact [ firmware :: firmware() ]
[๐ŸŒฑ] Using cached [ GIT_INFO_ARMBIAN_FIRMWARE ]
[๐Ÿ’–] artifact [ present in local cache: armbian-firmware 1-SA56ad-B6be6 ]
[๐ŸŒฑ] Building deb [ armbian-plymouth-theme ]
[๐ŸŒฑ] shellcheck found no problems in package scripts [ shellchecked 3 scripts in 'armbian-plymouth-theme' ]
[๐Ÿ”จ] ย  dpkg-deb: building package 'armbian-plymouth-theme' in '/home/steve/build/.tmp/work-5237001b-8933-4274-b02b-98b6ec67e71c/tmp.exL1KIf5bj/armbian-plymouth-theme_23.05.0-trunk_all.deb'.
[๐Ÿšธ] using legacy option [ KERNEL_ONLY=yes; stopping build mid-packages ]
[๐ŸŒฑ] Runtime [ 0 min ]
[โœจ] Repeat Build Options [ ./compile.sh BOARD=odroidhc4 BRANCH=current BUILD_MINIMAL=no BUILD_DESKTOP=no KERNEL_ONLY=yes KERNEL_CONFIGURE=yes COMPRESS_OUTPUTIMAGE=sha,img ]
[๐ŸŒฑ] Cleaning up [ please wait for cleanups to finish ]
[๐ŸŒฟ] ANSI log file built; inspect it by running: [ less -RS output/logs/log-build-5237001b-8933-4274-b02b-98b6ec67e71c.log.ans ]
[๐ŸŒฟ] Share log manually (or SHARE_LOG=yes): [ curl --data-binary @output/logs/log-build-5237001b-8933-4274-b02b-98b6ec67e71c.log.ans https://paste.next.armbian.com/log ]
steve@odroidhc4:~/build$
ย 

Link to comment
Share on other sites

FWIW, I tried a newer imageย ย Armbian 23.02.2 Jammy with Linux 6.1.11-meson64 and got a different error, which only seems to happen when the kernel configuration option is selected:

ย 

[๐ŸŒฑ] Syncing clock [ host ]
[๐Ÿ”จ] ย  ย 5 Mar 14:14:43 ntpdate[8332]: adjust time server 69.89.207.199 offset -0.002988 sec
[๐Ÿ”จ] ย  '/home/steve/build/config/templates/customize-image.sh.template' -> '/home/steve/build/userpatches/customize-image.sh'
[๐ŸŒฑ] artifact [ uboot :: uboot() ]
[๐ŸŒฑ] Producing new & caching [ GIT_INFO_UBOOT ]
[๐ŸŒฑ] Fetching SHA1 of tag v2023.01^{} [ https://github.com/u-boot/u-boot ]
[๐ŸŒฑ] SHA1 of tag v2023.01^{} [ '62e2ad1ceafbfdf2c44d3dc1b6efc81e768a96b9' ]
[๐ŸŒฑ] Getting ORAS manifest [ ORAS manifest from ghcr.io/armbian/cache-uboot/uboot-odroidhc4-current:2023.01-S62e2-P1cd3-B680b ]
[๐ŸŒฑ] Downloading required [ ORAS tooling ]
parse error: Invalid numeric literal at line 1, column 11
[๐Ÿ’ฅ] Error ย 4 occurred in SUBSHELL [ SUBSHELL at /home/steve/build/lib/functions/general/oci-oras.sh:141 ]
[๐Ÿ’ฅ] Error 4 occurred in main shell [ at /home/steve/build/lib/functions/general/oci-oras.sh:141
ย  ย  ย oras_get_artifact_manifest() --> lib/functions/general/oci-oras.sh:141
ย  ย is_artifact_available_in_remote_cache() --> lib/functions/artifacts/artifacts-obtain.sh:279
ย  ย artifact_uboot_is_available_in_remote_cache() --> lib/functions/artifacts/artifact-uboot.sh:107
ย  ย artifact_is_available_in_remote_cache() --> lib/functions/artifacts/artifacts-obtain.sh:24
ย  ย  ย  ย  ย  ย  ย  ย  do_with_logging() --> lib/functions/logging/section-logging.sh:72
ย  ย  ย  ย obtain_complete_artifact() --> lib/functions/artifacts/artifacts-obtain.sh:169
ย  ย  ย  ย build_artifact_for_image() --> lib/functions/artifacts/artifacts-obtain.sh:209
ย  ย  main_default_build_packages() --> lib/functions/main/build-packages.sh:49
ย  ย full_build_packages_rootfs_and_image() --> lib/functions/main/default-build.sh:4
ย  ย  ย  ย  ย  do_with_default_build() --> lib/functions/main/default-build.sh:17
ย  ย  ย  ย  ย cli_standard_build_run() --> lib/functions/cli/cli-build.sh:17
ย  ย  ย  ย  armbian_cli_run_command() --> lib/functions/cli/utils-cli.sh:126
ย  ย  ย  ย  ย  ย  ย  ย  ย cli_entrypoint() --> lib/functions/cli/entrypoint.sh:164
ย  ย  ย  ย  ย  ย  ย  ย  ย  ย  ย  ย  ย  ย main() --> compile.sh:52
ย ]
[๐Ÿ’ฅ] Cleaning up [ please wait for cleanups to finish ]
[๐ŸŒฟ] ANSI log file built; inspect it by running: [ less -RS output/logs/log-build-no-uuidgen-yet-20599-471010.log.ans ]
[๐ŸŒฟ] Share log manually (or SHARE_LOG=yes): [ curl --data-binary @output/logs/log-build-

ย 

ย 

Edited by frontrange
Link to comment
Share on other sites

FYI a workaround reply to the bug report:

"Confirm, when doing kernel configย during image buildย -- it can be worked-around by runningย ./compile.shย with commandย kernel-config, for now. I will try to come up with a way to make this work during image build, but inconsistencies arise, so fix is more complex than originally thought"

Link to comment
Share on other sites

Hello!

I'm trying to build Armbian for Nano Pi Neo with some extra kernel modules. But kernel options selection dialog is simply does not firing by compile.sh script. It ignores KERNEL_CONFIGURE=yes command line option as well as interactive choice. Just builds default config silently but wrote in logging "Repeat build options [...KERNEL_CONFIGURE=yes...]". I'm doing step by step procedure described at docs.armbian.com site. I have tried to build for different boards with same result. A few years ago I did it already same way with the older version and it worked fine. Now I trying to repeat the same from scratch but unsuccessfully. There are no error messages in logging. What can be wrong? How to call kernel configuration dialog?

Best regards, Dmitry

Link to comment
Share on other sites

  • Igor pinned this topic

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.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
ร—
ร—
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines