frontrange Posted March 4, 2023 Posted March 4, 2023 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$ Β 0 Quote
SteeMan Posted March 5, 2023 Posted March 5, 2023 I'm pretty sure this is a bug and I have logged it as such: https://github.com/armbian/build/issues/4905 1 Quote
frontrange Posted March 5, 2023 Author Posted March 5, 2023 (edited) 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 March 5, 2023 by frontrange 0 Quote
SteeMan Posted March 5, 2023 Posted March 5, 2023 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" 0 Quote
DmitryVS Posted March 7, 2023 Posted March 7, 2023 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 0 Quote
Recommended Posts
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.