RSS Bot

Description When trying to build an image with FIXED_IMAGE_SIZE=3000 ROOTFS_TYPE=f2fs with WSL2 as build host, I stumbled on an error pretty late in the build process when trying to mount the rootfs: [💲|🌿] Creating rootfs [ f2fs on /dev/loop2p2 ] [💲|🔨] [💲|🔨] F2FS-tools: mkfs.f2fs Ver: 1.14.0 (2020-08-24) [💲|🔨] [💲|🔨] Info: Disable heap-based policy [💲|🔨] Info: Debug level = 0 [💲|🔨] Info: Label = armbi_root [💲|🔨] Info: Trim is enabled [💲|🔨] Info: Segments per section = 1 [💲|🔨] Info: Sections per zone = 1 [💲|🔨] Info: sector size = 512 [💲|🔨] Info: total sectors = 5586911 (2727 MB) [💲|🔨] Info: zone aligned segment0 blkaddr: 512 [💲|🔨] Info: format version with [💲|🔨] "Linux version 6.1.21.2-microsoft-standard-WSL2+ (flash@DESKTOP-2VA4T55) (gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0, GNU ld (GNU Binutils for Ubuntu) 2.38) #1 SMP Wed Jan 31 20:29:07 CET 2024" [💲|🔨] Info: [/dev/loop2p2] Discarding device [💲|🔨] Info: This device doesn't support BLKSECDISCARD [💲|🔨] Info: Discarded 2727 MB [💲|🔨] Info: Overprovision ratio = 3.860% [💲|🔨] Info: Overprovision segments = 108 (GC reserved = 59) [💲|🔨] Info: format successful [💲|🌿] Mounting rootfs [ /dev/loop2p2 (UUID=02dfb13e-172d-44b1-b71c-25164f29cc0b) ] [💲|🔨] mount: /home/user/build-fork/.tmp/mount-bfedd4e1-02f1-4bac-99c1-88d420d40809: unknown filesystem type 'f2fs'. [💲|💥] Error 32 occurred in main shell [ at /home/flash/build-fork/lib/functions/logging/runners.sh:211 run_host_command_logged_raw() --> lib/functions/logging/runners.sh:211 run_host_command_logged() --> lib/functions/logging/runners.sh:193 prepare_partitions() --> lib/functions/image/partitioning.sh:275 do_with_logging() --> lib/functions/logging/section-logging.sh:81 build_rootfs_and_image() --> lib/functions/main/rootfs-image.sh:86 full_build_packages_rootfs_and_image() --> lib/functions/main/default-build.sh:36 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 ] [💲|💥] Cleaning up [ please wait for cleanups to finish ] I found out that this is because the WSL2 kernel does not have support for the F2FS filesystem. f2fs-tools could be installed normally though. To make the build script exit at the beginning instead of at a late stage and to tell the user a more exact reason why it failed, I added a check if the chosen ROOTFS_TYPE is supported by the host the build script is running on. The check checks /proc/filesystems which should be present in all Linux distros. But just in case /proc/filesystems is not present, the build won't fail and instead print a warning that the build might fail just like if it can't install python2. How Has This Been Tested? Build host: Linux version 6.1.21.2-microsoft-standard-WSL2+ (no F2FS support, but BTRFS and EXT4 support) Command: ./compile.sh build BOARD=nanopi-r5c BRANCH=edge BUILD_DESKTOP=no BUILD_MINIMAL=no KERNEL_CONFIGURE=no RELEASE=bookworm FIXED_IMAGE_SIZE=3000 ROOTFS_TYPE=f2fs [x] Ran build with FIXED_IMAGE_SIZE=3000 ROOTFS_TYPE=f2fs --> build exits at an early stage with [💲|💥] error! [ Filesystem type unsupported by build host: f2fs ] [x] Ran build with ROOTFS_TYPE=btrfs --> build success [x] Ran build without ROOTFS_TYPE option --> build success Might need some testing with other more exotic build hosts like Docker. 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 [ ] I have made corresponding changes to the documentation [x] My changes generate no new warnings View the full article

rk35xx/rockchip-rk3588: vendor: switch to armbian/linux-rockchip#rk-6.1-rkr1 rk35xx/rockchip-rk3588: vendor: switch to armbian/linux-rockchip#rk-6.1-rkr1 since https://github.com/armbian/linux-rockchip/pull/155 khadas-edge2: remove vendor branch, we've no kedge2 DT/patches for it yet View the full article

Description make common section similar to CLI remove deprecated remove 3rd party repository from 3d section remove / replace Codium with Code Jira reference number AR-2101 How Has This Been Tested? [ ] Manual builds Checklist: [ ] My code follows the style guidelines of this project [ ] I have performed a self-review of my own code [ ] I have commented my code, particularly in hard-to-understand areas [ ] I have made corresponding changes to the documentation [ ] My changes generate no new warnings [ ] Any dependent changes have been merged and published in downstream modules View the full article

Description Enable rk3528 soc support to make rk3528 boards bootable. Enable lima gpu driver for mali 400/450 gpu on rk3528 and disable arm mali400/450 driver. Devicetree related change is already in https://github.com/amazingfate/linux-rockchip/commit/419410ff56c8e80b37e100c265d57f23cc0db835 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=hinlink-ht2 BRANCH=vendor DEB_COMPRESS=xz KERNEL_CONFIGURE=no [x] Lima gpu driver works on hinlink-ht2 Checklist: [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 [ ] I have made corresponding changes to the documentation [x] My changes generate no new warnings [ ] Any dependent changes have been merged and published in downstream modules View the full article

Description Mainline kernel linux-6.7.y has broken dsi panel since 6.7.6, so we use back v6.7.5 avoid it. Other sm8250 device xiaomi 10 doesn't support panel in kernel so it should be fine. Use typec pd patch from lujianhua and now the typec port can auto switch to host mode when usb deivices are plugged in. 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=xiaomi-elish BRANCH=sm8250 DEB_COMPRESS=xz KERNEL_GIT=shallow DEB_COMPRESS=xz [x] Xiaomi pad5 pro works fine. Checklist: [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 [ ] I have made corresponding changes to the documentation [x] My changes generate no new warnings [ ] Any dependent changes have been merged and published in downstream modules View the full article

Description Add the patching config file for rk35xx-vendor to easily patch in dts files by putting them in the dt folder. How Has This Been Tested? [x] Put new dts files in patch/kernel/rk3588-vendor/dt and successfully ran ./compile.sh build BOARD=nanopc-cm3588-nas BRANCH=vendor BUILD_DESKTOP=no BUILD_MINIMAL=no KERNEL_CONFIGURE=no RELEASE=bookworm. New patches were applied. 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 [ ] I have made corresponding changes to the documentation [x] My changes generate no new warnings [x] Any dependent changes have been merged and published in downstream modules View the full article

Description Initial commit of most recent KDE desktop v6.x Jira reference number AR-2100 How Has This Been Tested? [x] Generated x86 and arm64 image (Odroid N2) Checklist: [ ] My code follows the style guidelines of this project [ ] I have performed a self-review of my own code [ ] I have commented my code, particularly in hard-to-understand areas [ ] My changes generate no new warnings [ ] Any dependent changes have been merged and published in downstream modules View the full article

Description Currently "Repeat Build Options" shows at the end of screen log only if process was successfully finished. This change adds "Repeat Build Options" text on the screen at the end of visible log. View the full article

u-boot: rewrite/rebase u-boot patches for a few boards; bump odroidm1 and orangepi3b u-boot: rewrite/rebase u-boot patches for a few boards; drop long-forgotten old version patches; no actual changes I guess this is most of the u-boot's I've touched over the years; notable exception is the orangepi3b (patches live in Kwiboo's tree) this is in preparation for bumping versions, hopefully soon radxa-zero, radxa-zero2, khadas-vim3, khadas-vim3l: drop patches for old u-boot versions no longer used odroidm1: bump u-boot to v2024.04-rc3 odroidm1: copy patches from v2023.10 odroidm1: rebase u-boot patches against v2024.04-rc3 odroidm1: drop v2023.10 u-boot patches orangepi3b: bump u-boot to Kwiboo's rk3xxx-2024.04 Add exact commit in a comment if it ever breaks Kwiboo's tree contains the OPi3B commits, not yet in upstream; I tried to rebase onto upstream v2024.04-rc3, but failed with "unmet direct dependencies detected for SPL_OF_LIBFDT" & SPL_LIBGENERIC_SUPPORT View the full article

cli: introduce rewrite-uboot-patches cli command, works similar to the kernel one cli: introduce rewrite-uboot-patches cli command, works similar to the kernel one it prepares git, applies patches to git, and re-writes them back from git same as kernel, it does git archeology for mbox-less patches, etc uboot-patches-to-git alias is also added, but my guess is rewrite is more useful refactor a common config function for both kernel and uboot example invocation: ./compile.sh BOARD=xxxx BRANCH=edge rewrite-uboot-patches View the full article

Description ::set-output has been deprecated in 2022: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/ Thus replacing it with >> $GITHUB_OUTPUT as described in the guide above. Also, took me a while to figure out how to create and use the ARMBIAN_SELF_DISPATCH_TOKEN mentioned in the readme. So I updated the readme accordingly so others don't have to spend time figuring it out on their own in the future. (This helped me a lot: https://github.com/peter-evans/repository-dispatch?tab=readme-ov-file#token) How Has This Been Tested? [x] Ran the workflow on my forked repo without issues. Checklist: [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] I have made corresponding changes to the documentation [x] My changes generate no new warnings [ ] Any dependent changes have been merged and published in downstream modules View the full article

rtw88_8821cu takes priority over the github driver, so this shouldn't effect other units or usb dongles people use. My reasoning is; The rtw88 driver for reasons yet unknown seems to trigger usb fails more often than the github driver. If a fail occurs it will introduce dmesg spam and upon reboot leave the onboard wireless module undetectable. Checklist: [ ] My code follows the style guidelines of this project [ ] I have performed a self-review of my own code [ ] I have commented my code, particularly in hard-to-understand areas [ ] I have made corresponding changes to the documentation [X] My changes generate no new warnings [ ] Any dependent changes have been merged and published in downstream modules View the full article

U-Boot: Update DRAM parameters and enable USB. Backport sunxi reorganize mctl_mem_matches_* functions Backport restore modified memory Add delay to steady dram detection Alphabetize dts Linux: Add spi1_cs1_pin to h616 dtsi Add node to m4-zero dts Alphabetize dts [ ] My code follows the style guidelines of this project [ ] I have performed a self-review of my own code [ ] I have commented my code, particularly in hard-to-understand areas [ ] I have made corresponding changes to the documentation [X] My changes generate no new warnings [ ] Any dependent changes have been merged and published in downstream modules View the full article

Description Added PPA source for Noble, added Bluetooth service, required fixed Bluetooth MAC to use Bluetooth function, added automatic generation of random MAC function (to be tested), fixed some udev file content issues Jira reference number [AR-9999] 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] Bluetooth [x] Auto gen random bt Mac 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] I have made corresponding changes to the documentation [x] My changes generate no new warnings [x] Any dependent changes have been merged and published in downstream modules View the full article

Description This commit adds Khadas MCU support to edge kernel. It can be used for fan control and some device configurations. Fan state can be set from /sys/class/thermal/cooling_device3. Jira reference number AR-2085 How Has This Been Tested? [x] Tested fan control. Checklist: [ ] My code follows the style guidelines of this project [ ] I have performed a self-review of my own code [ ] I have commented my code, particularly in hard-to-understand areas [ ] I have made corresponding changes to the documentation [ ] My changes generate no new warnings [ ] Any dependent changes have been merged and published in downstream modules View the full article

Description Expand legacy hooks to vendor. How Has This Been Tested? [x] Build previously broken u-boot 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 Added PPA source for Noble, added Bluetooth service, required fixed Bluetooth MAC to use Bluetooth function, added automatic generation of random MAC function (to be tested), fixed some udev file content issues Jira reference number [AR-9999] 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] Bluetooth [ ] Auto gen random bt Mac 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] I have made corresponding changes to the documentation [x] My changes generate no new warnings [x] Any dependent changes have been merged and published in downstream modules View the full article

lib: drop old boot_logo code; keep png/gif as they're used for plymouth lib: drop old boot_logo code; keep png/gif as they're used for plymouth origins of what's being dropped: https://github.com/armbian/build/pull/2065 View the full article

cli: introduce inventory-boards cli command, for hopefully painless & useful one-board-per-line CSV output cli: introduce inventory-boards cli command, for hopefully painless & useful one-board-per-line CSV output inventory-boards-csv.py: moar Python atrocities done to data; idea here is to output one line per board, with <> for fields that, well, vary (mainly across BRANCH'es) inventory-boards sets TARGETS_FILE to something that doesn't exist, so the default-targets.yaml is used (so same list for everyone, save for userpatched-boards) View the full article

cli: introduce kernel-dtb cli command, to build only DTB, and output full preprocessed dts source cli: introduce kernel-dtb cli command, to build only DTB, and output full preprocessed dts source example: ./compile.sh BOARD=xxxxx BRANCH=edge kernel-dtb outputs preprocessed DTS source for board in question to output/ also outputs same preprocessed DTS source, ran through dtc with input and output DTS formats for "normalized" comparisions View the full article

This PR enables kernel modules for various USB Gadget applications for rockchip 32 bit platforms (rk322x, rk3288) for both current 6.6 and edge 6.7 kernels. Also provides a bunch of patches to address issues with rk322x, whose peripheral mode does not really well with dwc2 driver yet. A couple of patches are self-produced after trial-and-error sessions, another pair are imported from rockchip 5.10 kernel and substitutes an older patch with a bit more refined code (see the "debounce" patch). edit: the patches addressing the rk322x issues probably are worth also for rk3318 and rk3328, since the controller is the very same with similar issues. During my tests, I quickly checked an rk3318 device and found it has the same behaviour (disconnection, system freeze, ...). I will do further tests and, in case, import the same patches for rockchip64 too. Jira reference number AR-2096 How Has This Been Tested? [x] Installed on live rk322x system, tested mass storage :heavy_check_mark:, ethernet :heavy_check_mark:, uac1/2 :negative_squared_cross_mark: [x] Installed on live rk3288 system in OTG mode, tested mass storage :heavy_check_mark:, uac1/2 :heavy_check_mark: For sake of curiosity, iperf3 run on rk322x in ethernet gadget mode: 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] I have made corresponding changes to the documentation [x] My changes generate no new warnings [x] Any dependent changes have been merged and published in downstream modules View the full article

Description Update odroidxu4-current kernel to 6.1.80. How Has This Been Tested? Reboot of my Odroid HC1. 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 [ ] I have made corresponding changes to the documentation [x] My changes generate no new warnings [ ] Any dependent changes have been merged and published in downstream modules View the full article

Late last week, the long-awaited kernel driver supporting 10th-generation Arm Mali GPUs was merged into drm-misc. The existing Gallium driver support has also been extended, effectively enabling GPUs on Rockchip's RK3588 platforms. View the full article

Description I wrote the wrong path and it has now been fixed Jira reference number [AR-9999] 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] Gamepad 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] I have made corresponding changes to the documentation [x] My changes generate no new warnings [x] Any dependent changes have been merged and published in downstream modules View the full article

Update maintainers and board status synced status from the database rename to .csc where we don't have anyone If you want to become a board maintainer, adjust data here. Ref: Board Maintainers Procedures and Guidelines View the full article