RSS Bot

Description This should make viewing the Action runs in the web UI more pleasant. Also small improvements: running a YAML formatter over all workflow files to fix formatting Sync labels with file Naming improvements How Has This Been Tested? [ ] To be seen in future workflow runs 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 [ ] My changes generate no new warnings View the full article

Description introduce common repo so we only add packages once publish via snapshots to increase reliability overwrite packages in case of conflicts add debug logging to file output/debs -> pool/main/ output/debs/$RELEASE -> pool/$RELEASE output/debs/extra/$RELEASE-utils -> pool/$RELEASE-utils output/debs/extra/$RELEASE-desktop -> pool/$RELEASE-desktop How Has This Been Tested? [x] Tested with local repository (completes significantly faster) [ ] Full test with stable and beta repository 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

Description Previously, only the type "Generic Linux filesystem" was used for the root filesystem. Use the correct type "Linux root ($ARCHITECTURE)" for the root filesystem. For other little improvements, please refer to the single commits: Add some comments to improve readbility Output the partitioning options to the debug log [Add check to use legacy BIOS boot partition with GPT only, not MBR(https://github.com/armbian/build/commit/c134638fb65f7863fba81fb74819a083b975f9ed) How Has This Been Tested? [x] Boot success on nanoPi R6C with build: ./compile.sh BOARD=nanopi-r6c BRANCH=edge BUILD_DESKTOP=no BUILD_MINIMAL=no EXPERT=yes KERNEL_CONFIGURE=no RELEASE=trixie FIXED_IMAGE_SIZE=3000 ROOTFS_TYPE=f2fs DEBUG=yes [x] fdisk shows the correct partition types 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 I'm sorry, I have created a monster 🧌 But this happens when you create a monster by embedding dependency versions inside shell script files 😅 This workflow is carefully crafted though and works surprisingly well imo :) Some of our scripts download tools from a repo. These can't be bumped by dependabot, so this workflow is a self-created dependabot to bump versions of those tools to stay up-to-date. This workflow only creates a PR if the version was actually updated. Tools currently supported: Shellcheck (in 2 different files) Shellfmt oci-oras Bat This will only run once a month since the tools we use are usually not updated frequently. Maybe every two weeks/twice a month would also be fine? Let me know. How Has This Been Tested? [x] Workflow run: https://github.com/ColorfulRhino/build/actions/runs/9857502042 [x] Created PR: https://github.com/ColorfulRhino/build/pull/8 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] Any dependent changes have been merged and published in downstream modules View the full article

Description Establish some consistency with extension logging: Add "Extension: ${EXTENSION}: " prefix to some extension logs Make the log messages more consistent throughout extensions. Some extensions use another format: display_alert "message" "${EXTENSION}" "info" These were not adapted to this new schema. Yes I do realize there is probably a better way to do this e.g. by introducing a new display_alert category, like "extension" instead of "info". How Has This Been Tested? [x] Build an image with this enabled, shows more consistent logging 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 Mount option commit=600 (=10 minutes) seems pretty high. Reduce it to 120 for ext4 (default for ext4 is commit=5) and 120 for btrfs (default for btrfs is commit=30) to reduce risk of losing data on power loss. Only verly low settings (maybe 1-10) will have impact on performance according to documentation. From ext4: commit=nrsec (*) This setting limits the maximum age of the running transaction to ‘nrsec’ seconds. The default value is 5 seconds. This means that if you lose your power, you will lose as much as the latest 5 seconds of metadata changes (your filesystem will not be damaged though, thanks to the journaling). This default value (or any low value) will hurt performance, but it’s good for data-safety. Setting it to 0 will have the same effect as leaving it at the default (5 seconds). Setting it to very large values will improve performance. Note that due to delayed allocation even older data can be lost on power failure since writeback of those data begins only after time set in /proc/sys/vm/dirty_expire_centisecs. From btrfs: commit= (since: 3.12, default: 30) Set the interval of periodic transaction commit when data are synchronized to permanent storage. Higher interval values lead to larger amount of unwritten data, which has obvious consequences when the system crashes. The upper bound is not forced, but a warning is printed if it’s more than 300 seconds (5 minutes). Use with care. Sources: https://www.kernel.org/doc/html/latest/admin-guide/ext4.html https://wiki.archlinux.org/title/Btrfs#Commit_interval https://btrfs.readthedocs.io/en/latest/Administration.html How Has This Been Tested? [x] Change is reflected in fstab 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

Bumps actions/upload-artifact from 4.3.3 to 4.3.4. Release notes Sourced from actions/upload-artifact's releases. v4.3.4 What's Changed Update @actions/artifact version, bump dependencies by @robherley in actions/upload-artifact#584 Full Changelog: https://github.com/actions/upload-artifact/compare/v4.3.3...v4.3.4 Commits 0b2256b Merge pull request #584 from actions/robherley/bump-pkgs 488dcef licensed cache 04c51f5 ncc 32a9e27 bump @actions/artifact and npm audit 552bf37 new version 79616d2 Merge pull request #565 from actions/eggyhead/use-artifact-v2.1.6 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 Remove & replace deprecated packages. How Has This Been Tested? [ ] Ci Checklist: [ ] My changes generate no new warnings [ ] Any dependent changes have been merged and published in downstream modules View the full article

mekotronics: u-boot: join rockchip-rk3588's default u-boot-radxa-rk35xx scheme mekotronics: u-boot: join rockchip-rk3588's default u-boot-radxa-rk35xx scheme rebased 2 patches moved null patches for dts & defconfigs to dt / defconfig dirs rename defconfigs since we're at it; use board-specific only defconfigs re-saved View the full article

mixtile-blade3: u-boot: join rockchip-rk3588's default u-boot-radxa-rk35xx scheme mixtile-blade3: u-boot: join rockchip-rk3588's default u-boot-radxa-rk35xx scheme rebased 3 patches moved null patches for dts & defconfigs to dt / defconfig dirs don't rename defconfigs: those are shared with Joshua Riek (ubuntu-rockchip) defconfigs re-saved View the full article

cli-patch: generalize to-git functionality with PUSH_TO_GITHUB and PUSH_TO_REPO & enable for u-boot as well as kernel cli-patch: generalize to-git functionality with PUSH_TO_GITHUB and PUSH_TO_REPO & enable for u-boot as well as kernel PUSH_TO_REPO=<url>: set the full git URL to push to PUSH_TO_GITHUB=<org>/<repo>: shorthand for pushing to GitHub; sets PUSH_TO_REPO note: be kind to GitHub, and use forks of torvalds/linux and u-boot/u-boot so GH has a decent base tree still, kernel pushes are huge, mostly due to the all-wifi-drivers commit that's always first and always slightly different note: when pushing to GitHub, keep in mind the pushed branch contains a GHA workflow, which will only run if you have GHA enabled on the repo examples (adapt to your username/forks): ./compile.sh BOARD=nanopct6 BRANCH=edge rewrite-kernel-patches PUSH_TO_GITHUB=rpardini/linux ./compile.sh BOARD=rock-5b BRANCH=legacy rewrite-uboot-patches PUSH_TO_GITHUB=rpardini/armbian-patched-u-boot View the full article

thinkpad-x13s: bump to jhovold's wip/sc8280xp-6.10-rc6; add fprintd back to Trixie; fixes thinkpad-x13s: bump to jhovold's wip/sc8280xp-6.10-rc6; add fprintd back to Trixie; fixes adapt according to most recent instructions from jhovold: https://github.com/jhovold/linux/wiki/X13s https://github.com/jhovold/linux/commit/993ae484d12ae6323647638000ed683c5222feb3 View the full article

Description Split off from https://github.com/armbian/build/pull/6902 as requested by @rpardini Add armhf support to Trixie Move the NETWORKING_STACK in main config to after family config to allow the family config to change it. How Has This Been Tested? [x] ./compile.sh BOARD=bananapir2 BRANCH=current BUILD_DESKTOP=no BUILD_MINIMAL=no EXPERT=yes KERNEL_CONFIGURE=no RELEASE=trixie [x] ./compile.sh BOARD=bananapir2 BRANCH=current BUILD_DESKTOP=no BUILD_MINIMAL=no EXPERT=yes KERNEL_CONFIGURE=no RELEASE=noble View the full article

Description Some beautification (new lines) Use only find without grep Board configs are also bash/shell files, so add them to the list. How Has This Been Tested? [x] Run lib/tools/shellfmt.sh 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 Add parallel compression for xz with the option XZ_OPT="--threads=0" gzip and bzip were already using parallel compressors. xz has this option built-in, so add the argument to make use of it. Source: https://lore.kernel.org/lkml/20200901151002.988547791@linuxfoundation.org/ Also change KBUILD user and host to make cat /proc/version show something like Linux version 6.9.8 (build@armbian) instead of Linux version 6.9.8 (armbian@next). build@armbian refers to the Armbian build framework (this repository) How Has This Been Tested? [x] ./compile.sh build BOARD=nanopi-r6c BRANCH=edge BUILD_DESKTOP=no BUILD_MINIMAL=no EXPERT=yes KERNEL_CONFIGURE=no RELEASE=trixie [ ] Benchmark could be done, but I don't know how I can force a full kernel rebuild without using any caching at all 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

Description The same configuration has been working fine for the similar NanoPi R6C for a while. Users have reported issues with the vendor U-Boot not able to boot. Ref: https://forum.armbian.com/topic/42105-report-bug-in-nanopi-r6s/ How Has This Been Tested? [x] ./compile.sh BOARD=nanopi-r6s BRANCH=edge BUILD_DESKTOP=no BUILD_MINIMAL=no EXPERT=yes KERNEL_CONFIGURE=no RELEASE=trixie uboot 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 [ ] My changes generate no new warnings [x] Any dependent changes have been merged and published in downstream modules View the full article

Description The mt7623 family only has one board (BananaPi R2) and has not been properly maintained in many years. Instead of fully removing the family, bump the kernel to 'current' 6.6 since the SoC and also the BananaPi R2 is mainlined and shouldn't cause too many troubles. No need for 'edge' kernel unless someone plans to step in as maintainer who bumps and tests it on every new kernel release. Also: Add armhf support to Trixie (was this disabled for a specific reason? If so, please let me know. It builds fine though) Move the NETWORKING_STACK in main config to after family config to allow the family config to change it. Please note: I do not own the hardware. Inspiration for changed were made from this 1.5 years old PR: https://github.com/armbian/build/pull/4873 By the way, when this is done, there will be no 4.x kernels anymore 🎉 (5.x I'm coming for you soon™ as well 😈) GitHub issue reference: https://github.com/armbian/build/issues/6821 Jira reference number AR-2392 How Has This Been Tested? [x] ./compile.sh BOARD=bananapir2 BRANCH=current BUILD_DESKTOP=no BUILD_MINIMAL=no EXPERT=yes KERNEL_CONFIGURE=no RELEASE=trixie [x] ./compile.sh BOARD=bananapir2 BRANCH=current BUILD_DESKTOP=no BUILD_MINIMAL=no EXPERT=yes KERNEL_CONFIGURE=no RELEASE=noble 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

multiple boards: bump u-boot from v2024.07-rcX to v2024.07 final u-boot v2024.07: rewrite patches against v2024.07 final rk322x-box: rewrite u-boot patches against v2024.07-rc5 rk3318-box: rewrite u-boot patches against v2024.07-rc5 jethubj200: rewrite u-boot patches against v2024.07 final multiple boards: bump u-boot from v2024.07-rcX to v2024.07 final after this, all patches were rewritten, but zero changes. success! View the full article

u-boot: embed armbian artifact version in CONFIG_LOCALVERSION u-boot: embed armbian artifact version in CONFIG_LOCALVERSION we're hacking at it anyway, so why not use it to uniquely identify the exact build View the full article

odroidm1: bump to u-boot v2024.07; replace defconfig patches with hook odroidm1: bump to u-boot v2024.07; replace defconfig patches with hook bump "armbian" env to reset env in SPI on first run View the full article

nanopi-r5s: u-boot: pci enum in preboot; disable armbian-led-state nanopi-r5s: u-boot: pci enum in preboot; disable armbian-led-state pci enum in preboot; required for working m.2 when booting some older kernels this board has an overlay (DEFAULT_OVERLAYS="nanopi-r5s-leds") to drive the LEDs, disable armbian-led-state service View the full article

Description also bump: rk3288 xt-q8l-v10 target rk322x-box target (was already v2024.07-rc5) rk3318-box target (was already v2024.07-rc5) rk322x-box and rk3318-box were already at v2024.07, since u-boot v2024.07 has been released some days ago, they have been moved from rc5 to release (see https://github.com/armbian/build/pull/6855) Asus Tinkerboard/S and xt-q8l-v10, which are both rk3288 targets, have been bumped from v2022.04 to v2024.07, trying to keep all the features working. I guess now the workaround cited here could be removed as well. GitHub issue reference: Jira reference number AR-2406 How Has This Been Tested? [x] Built image for both rk3288 targets successfully [x] Boot from emmc, sd and USB on xt-q8l-v10 [x] Boot from emmc and sd on Asus Tinkerboard S [x] UMS mode on Asus Tinkerboard S [x] Video console and USB keyboard working [x] Built uboot only for rk322x-box [x] Built uboot only for rk3318-box In particular, fresh images have been built, installed on sdcard, booted and then installed onto emmc with armbian-install script successfully for both Tinkerboard S and xt-q8l-v10 Side targets rk322x-box and rk3318-box have not been tested further: they have been througly tested with v2024.07-rc5 and I consider sufficient they don't break compilation with u-boot release version. 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 [x] My changes generate no new warnings View the full article

Fix: dtb dtbo install, wrong select media sensors Disable incorrectly designed patches. They need to be aligned with the kernel code. 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] Test build sunxi [ ] Test build sunxi64 View the full article

Description move original OrangepiZero patch to be applied on that board only add patch for powering WiFi on Inovato Quadra with correct pin How Has This Been Tested? [x] Build 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 Radxa E52C is a rk3582 based board with dual 2.5G ethernet. This pr depends on https://github.com/armbian/linux-rockchip/pull/203. Since its soc is rk3582 so it should the same uboot patch from rock-5c to enable good ip cores disabled by u-boot. 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] ./compile.sh BOARD=radxa-e52c BRANCH=vendor BUILD_MINIMAL=no DEB_COMPRESS=xz KERNEL_CONFIGURE=no RELEASE=noble KERNEL_GIT=shallow BUILD_DESKTOP=no [x] Board boots fine. 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 [ ] 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