RSS Bot

My precious! How Has This Been Tested? Daily Driving 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] 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 [X] Blood Donated [X] Tears produced [X] Contract with the devil signed View the full article

Description enable CONFIG_RTW89_8852BE=m to take advantage of https://github.com/armbian/linux-rockchip/pull/192 GitHub issue reference: https://github.com/armbian/linux-rockchip/pull/192 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] built kernel&image for opi5plus - 8852BE chipset and bluetooth are recognized and working OOB 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 Fix boot from btrfs fs in uboot 2024.07 (backport patch from uboot.next https://github.com/u-boot/u-boot/commit/ee1941e4fec601a8444f49c7dad04ad700d501a6) 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 image and boot from (zstd-compressed) btrfs sole rootfs/bootfs partition Checklist: [x] I have performed a self-review of my own code View the full article

Description Reverse commit 75317a0 since this is a special case. Eliminate the real reason for the inability to boot the kernel. Linux kernel hangs in early boot on 32-bit ARM platform, when ftrace 4-byte "mcount" function call location for "_raw_spin_unlock_irqrestore" function straddles icache lines. The problem is present for (cross-compiler) GCC 10, 11, 12. It does not happen when the kernel is compiled with GCC 9, even when condition (1) is satisfied. Detailed description: https://forum.armbian.com/topic/41339-linux-image-legacy-sunxi2451-kernel-6192-is-broken-stuck-at-starting-kernel/?do=findComment&comment=196528 How Has This Been Tested? [x] Test build for sunxi [x] Test work on board BPI-m3 View the full article

Description This patch has been mainlined in the kernel for both v6.6.37 and somewhere in v6.9.y branch too.. There are several reports that it broke rk3328 pinctrl and, as the worst side effect, eMMC controller does not work anymore on rk3318/rk3328 (reports on the forums: this, this and this) I identified the single line that is causing the issue; reverting the single change fixes the bad pinctrl behaviour in my case. How Has This Been Tested? [x] built and tested kernel 6.6.37 on live system [x] built and tested kernel 6.9.9 on live system 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

Bump u-boot to v2024.07 View the full article

Description Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change. GitHub issue reference: #6940 Jira reference number AR-2419 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 A create /root/.not_logged_in_yet as noted in #6940 notice the errors disappear 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] I have commented my code, particularly in hard-to-understand areas [x] My changes generate no new warnings View the full article

Description sunxi-6.9: Add megous patches and switch EDGE to tag:v6.9.9 How Has This Been Tested? [x] Test build for armhf [x] Test work on BPI-m3 View the full article

Description Follow-up to #6927 Bind mount /dev into the container Remove previous attempt via MKNOD capability which actually didn't affect the issue GitHub issue reference: #6568 Jira reference number AR-2132 Documentation summary for feature / change The issue has been found in other projects as well, and they end up bind mounting /dev into the container: https://github.com/moby/moby/issues/27886 https://github.com/moby/moby/issues/16160 The issues have a lot of discussion on the various aspects of the problem and solutions. The most accepted one is binding /dev into the container. The MKNOD capability doesn't solve the issue, as it turns out. Testing in #6927 was faulty, as the device is available by the next launch, and the most reliable way to remove it that I've found is to reboot the machine. How Has This Been Tested? Fresh system boot, run ./compile.sh build BOARD=odroidm1 BRANCH=current BUILD_DESKTOP=no BUILD_MINIMAL=no KERNEL_CONFIGURE=no KERNEL_GIT=shallow RELEASE=bookworm PREFER_DOCKER=yes 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] 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

mainline-kernel: bump to 6.10-rc7 mainline-kernel: bump to 6.10-rc7 just rockchip-rk3588 for now rockchip-rk3588 / edge: rebase onto 6.10-rc7 win: notice how one can actually spot relevant changes now case in point, 1022-arm64-dts-rockchip-support-poweroff-on-rock-5a.patch -- will drop it in separate commit rockchip-rk3588 / edge: drop patch that landed in 6.10-rc7 1022-arm64-dts-rockchip-support-poweroff-on-rock-5a.patch landed https://github.com/torvalds/linux/commit/d05f7aff7ac23884ed9103a876325047ff9049aa View the full article

thinkpad-x13s: bump to jhovold's wip/sc8280xp-6.10-rc7 thinkpad-x13s: bump to jhovold's wip/sc8280xp-6.10-rc7 View the full article

Description Each family should build the same kernel. 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 kernel BOARD=armsom-sige5 BRANCH=vendor DEB_COMPRESS=xz KERNEL_CONFIGURE=no KERNEL_GIT=shallow 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

Description Update JetHub D2 support Jira reference number AR-2028 View the full article

Description Added arguments --cap-add MKNOD to docker run command to allow losetup -f to create the loop device node. Fixes #6568 GitHub issue reference: https://github.com/armbian/build/issues/6568 Jira reference number AR-2132 How Has This Been Tested? Running ./compile.sh build BOARD=odroidm1 BRANCH=current BUILD_DESKTOP=no BUILD_MINIMAL=no KERNEL_CONFIGURE=no KERNEL_GIT=shallow RELEASE=bookworm 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 [x] Any dependent changes have been merged and published in downstream modules View the full article

Description Copy missing common.mk for build Comment undefined RTW_WARN_LMT Fix wrong dir name in Makefile Remove sed CONFIG_PLATFORM_SPACEMIT for bpif3 because source code has alraedy enabled it, and fix sed CONFIG_PLATFORM_ARM_ROCKCHIP for armsom-sige5 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 kernel BOARD=armsom-sige5 BRANCH=vendor DEB_COMPRESS=xz KERNEL_CONFIGURE=no KERNEL_GIT=shallow [x] wifi works on armsom sige5 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

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