RSS Bot

Description Add megous patches Sunxi edge switch kernel to v6.10.5 How Has This Been Tested? [x] Test build on ubuntu 22.04 env the Bookworm img [x] Test work on BPI-m64 & install on eMMC ____ ____ _ __ __ __ _ _ | __ )| _ \(_) | \/ |/ /_ | || | | _ \| |_) | | | |\/| | '_ \| || |_ | |_) | __/| | | | | | (_) |__ _| |____/|_| |_| |_| |_|\___/ |_| Welcome to Armbian_community 24.8.0-trunk Bookworm with bleeding edge Linux 6.10.5-edge-sunxi64 No end-user support: built from trunk System load: 7% Up time: 0 min Memory usage: 7% of 1.94G IP: 192.168.100.101 CPU temp: 25°C Usage of /: 17% of 7.0G View the full article

Description The forked helper workflow ran regardless whether ARMBIAN_SELF_DISPATCH_TOKEN was set or not, generating errors if the secret could not be found. In addition, simplify and beautify the workflow. How Has This Been Tested? [ ] To be tested in future automatic workflow runs, if no errors are generated Checklist: [x] My code follows the style guidelines of this project [x] I have performed a self-review of my own code [x] I have commented my code, particularly in hard-to-understand areas View the full article

After rigorous debugging, a new unit testing framework was added to the backend compiler for NVK. This is a walkthrough of the steps taken to achieve this. View the full article

Description Found lost patch for JetHub D2 devicetree file. Jira reference number AR-2028 View the full article

Description Currently, if losetup -f has to create a new device node and is run in a docker container, the device will be created on host butt will not be available to the already running container. This PR mitigates that by running losetup -f in a container in case there are no loop devices (/dev/loop0 is checked). The container exits after executing losetup and the main build container is run after. The MKNOD capability does not affect the issue, so it was removed. For additional context, previous attempts at fixing: #6576 #6642 #6927 #6936 GitHub issue reference: #6568 Jira reference number AR-2132 How Has This Been Tested? Fresh boot on a system that doesn't have loop devices created by default Run a dockerized build ./compile.sh build PREFER_DOCKER=yes Checklist: [x] My code follows the style guidelines of this project [x] I have performed a self-review of my own code [x] I have commented my code, particularly in hard-to-understand areas [x] My changes generate no new warnings View the full article

Description rework to apply cleanly on 6.10.5 and 6.6.46 - root cause GitHub issue reference: #7087 Jira reference number AR-2467 special thanks: @EvilOlaf How Has This Been Tested? [x] Patch applies cleanly to meson64 edge 6.10.5 - compiling ok [x] Patch applies cleanly to meson64 current 6.6.46 - compiling ok Checklist: [x] My code follows the style guidelines of this project [x] I have performed a self-review of my own code [x] My changes generate no new warnings View the full article

Description rework to apply cleanly on 6.10.5 and 6.6.46 - root cause GitHub issue reference: #7087 Jira reference number AR-2467 special thanks: @EvilOlaf How Has This Been Tested? [x] Patch applies cleanly to rockchip64 edge 6.10.5 - compiling ok [x] Patch applies cleanly to rockchip64 current 6.6.46 - compiling ok Checklist: [x] My code follows the style guidelines of this project [x] I have performed a self-review of my own code [x] My changes generate no new warnings View the full article

Description The kernel supports compilation with LLVM in addition to GCC, including cross-compilation to arm and riscv. This PR adds an option to use KERNEL_COMPILER=clang to compile kernel with clang. Documentation summary for feature / change I haven't added documentation but probably should? How Has This Been Tested? [x] Built armbian with clang for one target of each architecture (x86, arm, riscv) [x] Verified that gcc build still works Checklist: Please delete options that are not relevant. [x] My code follows the style guidelines of this project [x] I have performed a self-review of my own code [ ] My changes generate no new warnings View the full article

The armbian way appears to be to use the u-boot.bin.sd.bin in place of the u-boot.bin. Usually this isn't a huge problem, but on this unit it isn't playing nicely. There is also no SDCARD slot on this unit, so let's just use the intended binary. View the full article

Description Fix u-boot patchset for JetHub D2 Jira reference number [AR-2028] How Has This Been Tested? Please describe the tests that you ran to verify your changes. Please also note any relevant details for your test configuration. [X] JetHub D2 Boot ok Checklist: [X] My code follows the style guidelines of this project [X] I have performed a self-review of my own code [X] My changes generate no new warnings View the full article

Description FW maintenance Are we ready to note that Noble host provides experimental support? Perhaps we can get some help in ironing problems? Checklist: [x] My code follows the style guidelines of this project View the full article

Description Important: This PR is based on and depends on https://github.com/armbian/build/pull/7015 and can only be merged after that PR (NEEDS TO BE REBASED FIRST AFTER RK3588 6.11 HAS BEEN MERGED!) This PR should be merged at the same time as vendor kernel PR https://github.com/armbian/linux-rockchip/pull/220 Full mainline support for the CM3588 NAS has been added to kernel 6.11 🎉 Make use of this device tree going forward. In addition, support for mainline U-Boot is also in the pipeline and is available in Kwiboo's repo in v2024.10. Use this as well. How Has This Been Tested? [x] edge: Successful boot without any obvious errors in dmesg with build command ./compile.sh BOARD=cm3588-nas BRANCH=edge BUILD_DESKTOP=no BUILD_MINIMAL=no EXPERT=yes KERNEL_CONFIGURE=no RELEASE=trixie [x] vendor: Successful boot without any obvious errors in dmesg with build command ./compile.sh BOARD=cm3588-nas BRANCH=vendor BUILD_DESKTOP=no BUILD_MINIMAL=no EXPERT=yes KERNEL_CONFIGURE=no RELEASE=trixie Checklist: [x] My code follows the style guidelines of this project [x] I have performed a self-review of my own code [x] I have commented my code, particularly in hard-to-understand areas [x] My changes generate no new warnings [ ] Any dependent changes have been merged and published in downstream modules View the full article

Description set CONFIG_SECURITY_DMESG_RESTRICT=y to BRANCH=edge & BRANCH=current Advised for KASLR-enabled kernels complements nicely #7078 (but not depending on each other) - no side effect for non-KASLR-enabled kernel/boards How Has This Been Tested? [X] Built/ran nanopi-r5c current/edge (with patched u-boot from #7078) Checklist: [X] My code follows the style guidelines of this project [X] I have performed a self-review of my own code [X] My changes generate no new warnings View the full article

Description set CONFIG_SECURITY_DMESG_RESTRICT=y to BRANCH=edge & BRANCH=current Advised for KASLR-enabled kernels complements nicely #7078 (but not depending on each other) - no side effect for non-KASLR-enabled kernel/boards How Has This Been Tested? [X] Built/ran orangepi5-plus edge (with patched u-boot from #7078) Checklist: [X] My code follows the style guidelines of this project [X] I have performed a self-review of my own code [X] My changes generate no new warnings View the full article

Description KASRL-supported u-boot 2024.07 for everyone: move /chosen/kaslr-seed DTC node support patchset to general 2024.07 BOOTPATCHDIR attach nanopi-r5c and oprangepi5-plus BOOTPACHDIR to patches/uboot/v2024.07 general dir Hopefully, other boards using same uboot-version can benefit from the added support note for Maintainers - to enable KASLR seed, you need: - CONFIG_RANDOMIZE_BASE=y configured in your kernel .config - CONFIG_CMD_KASLRSEED=y and CONFIG_DM_RNG=y configure in your u-boot .config - exposed crypto and rng nodes in you board's device-tree - kasrlseed command before kernel boot in your boot.cmd - CONFIG_SECURITY_DMESG_RESTRICT=y in kernel .config is also advisable (integrated by #7079 and #7080 for orangepi5-plus/nanopi-r5c) note for Maintainers 2 - please place your patched u-boot defconfig and device-trees (when needed) in patch/u-boot/v2024.07/defconfig and patch/u-boot/v2024.07/dt How Has This Been Tested? [X] Built and ran BRANCH=edge RELEASE=trixie BOARDS=(nanopi-r5c orangepi5-plus) [x] Built and ran BRANCH=current RELEASE=trixie BOARD=nanopi-r5c Checklist: [x] My code follows the style guidelines of this project [x] I have performed a self-review of my own code [x] My changes generate no new warnings View the full article

Description Building for mangopi mq crashes with the following error: Image 'itb' is missing external blobs and is non-functional: opensbi /binman/itb/fit/images/opensbi/opensbi (fw_dynamic.bin): See the documentation for your board. The OpenSBI git repo is at https://github.com/riscv/opensbi.git You may need to build fw_dynamic.bin first and re-build u-boot with OPENSBI=/path/to/fw_dynamic.bin Some images are invalid make: *** [Makefile:1124: .binman_stamp] Error 103 --> (179) ERROR: Error 2 occurred in main shell [ at /armbian/lib/functions/logging/runners.sh:211 run_host_command_logged_raw() --> lib/functions/logging/runners.sh:211 run_host_command_logged_long_running() --> lib/functions/logging/runners.sh:188 do_with_ccache_statistics() --> lib/functions/compilation/ccache.sh:39 compile_uboot_target() --> lib/functions/compilation/uboot.sh:230 loop_over_uboot_targets_and_do() --> lib/functions/compilation/uboot.sh:287 compile_uboot() --> lib/functions/compilation/uboot.sh:391 do_with_logging() --> lib/functions/logging/section-logging.sh:81 artifact_uboot_build_from_sources() --> lib/functions/artifacts/artifact-uboot.sh:175 artifact_build_from_sources() --> lib/functions/artifacts/artifacts-obtain.sh:34 obtain_complete_artifact() --> lib/functions/artifacts/artifacts-obtain.sh:280 build_artifact_for_image() --> lib/functions/artifacts/artifacts-obtain.sh:392 main_default_build_packages() --> lib/functions/main/build-packages.sh:108 full_build_packages_rootfs_and_image() --> lib/functions/main/default-build.sh:31 do_with_default_build() --> lib/functions/main/default-build.sh:42 cli_standard_build_run() --> lib/functions/cli/cli-build.sh:25 armbian_cli_run_command() --> lib/functions/cli/utils-cli.sh:136 cli_entrypoint() --> lib/functions/cli/entrypoint.sh:176 main() --> compile.sh:50 See, e.g., https://forum.armbian.com/topic/21465-armbian-image-and-build-support-for-risc-v/?do=findComment&comment=190008 The fix is to build OpenSBI and use it to build uboot as suggested in error message, as discussed in https://forum.rvspace.org/t/building-u-boot-from-mainline-repo/3398 for example. This PR adds OpenSBI building stage. How Has This Been Tested? [x] Built for BOARD=mangopi-m28k Checklist: [x] My code follows the style guidelines of this project [x] I have performed a self-review of my own code [x] My changes generate no new warnings View the full article

Description JetHome: Move blacklist for rtw88 kernel module to the board configs Jira reference number AR-2466 How Has This Been Tested? Build without warning [X] JetHub D1+ [X] JetHub H1 Checklist: [X] My code follows the style guidelines of this project [X] I have performed a self-review of my own code [X ] My changes generate no new warnings View the full article

Description As tittle said. How Has This Been Tested? Need to be tested. Checklist: [x] My changes generate no new warnings [x] Any dependent changes have been merged and published in downstream modules View the full article

Description Fix logic. How Has This Been Tested? [x] Build current and edge kernel with rock3c Checklist: [x] My changes generate no new warnings [x] Any dependent changes have been merged and published in downstream modules View the full article

Description How Has This Been Tested? Not yet. Checklist: [ ] My changes generate no new warnings [ ] Any dependent changes have been merged and published in downstream modules View the full article

Bumps actions/upload-artifact from 4.3.5 to 4.3.6. Release notes Sourced from actions/upload-artifact's releases. v4.3.6 What's Changed Revert to @actions/artifact 2.1.8 by @robherley in actions/upload-artifact#594 Full Changelog: https://github.com/actions/upload-artifact/compare/v4...v4.3.6 Commits 834a144 Merge pull request #594 from actions/robherley/4.3.6 134dcf3 v4.3.6 73a0b9c revert back to @actions/artifact 2.1.8 See full diff in compare view Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase. Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: @dependabot rebase will rebase this PR @dependabot recreate will recreate this PR, overwriting any edits that have been made to it @dependabot merge will merge this PR after your CI passes on it @dependabot squash and merge will squash and merge this PR after your CI passes on it @dependabot cancel merge will cancel a previously requested merge and block automerging @dependabot reopen will reopen this PR if it is closed @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) View the full article

Bumps pyyaml from 6.0.1 to 6.0.2. Release notes Sourced from pyyaml's releases. 6.0.2 What's Changed Support for Cython 3.x and Python 3.13. Full Changelog: https://github.com/yaml/pyyaml/compare/6.0.1...6.0.2 6.0.2rc1 Support for extension build with Cython 3.x Support for Python 3.13 Added PyPI wheels for musllinux on aarch64 Changelog Sourced from pyyaml's changelog. 6.0.2 (2024-08-06) yaml/pyyaml#808 -- Support for Cython 3.x and Python 3.13 Commits 41309b0 Release 6.0.2 (#819) dd9f0e1 6.0.2rc1 (#809) f5527a2 disable CI trigger on PR edits b4d80a7 Python 3.12 + musllinux_1_1_x86_64 wheel support See full diff in compare view Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase. Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: @dependabot rebase will rebase this PR @dependabot recreate will recreate this PR, overwriting any edits that have been made to it @dependabot merge will merge this PR after your CI passes on it @dependabot squash and merge will squash and merge this PR after your CI passes on it @dependabot cancel merge will cancel a previously requested merge and block automerging @dependabot reopen will reopen this PR if it is closed @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) View the full article

Description Maint. How Has This Been Tested? [ ] Compile at CI Checklist: [ ] My changes generate no new warnings [ ] Any dependent changes have been merged and published in downstream modules View the full article

Description Maint. How Has This Been Tested? [x] Compile test Checklist: [x] My changes generate no new warnings [x] Any dependent changes have been merged and published in downstream modules View the full article

Description Moved patch from uboot 35xx to uboot 3588 In order to patch. At before, the patch has not been patched. How Has This Been Tested? [x] ./compile.sh build ARTIFACT_IGNORE_CACHE=yes BOARD=firefly-itx-3588j BRANCH=vendor BUILD_DESKTOP=yes BUILD_MINIMAL=no DESKTOP_ENVIRONMENT=gnome DESKTOP_ENVIRONMENT_CONFIG_NAME=config_base KERNEL_CONFIGURE=no RELEASE=bookworm [x] observed successful patch to uboot w/o error [x] u-boot said Starting Kernel ... Checklist: [x] My code follows the style guidelines of this project [x] I have performed a self-review of my own code [x] I have commented my code, particularly in hard-to-understand areas [x] My changes generate no new warnings [x] Any dependent changes have been merged and published in downstream modules View the full article