RSS Bot

Description This fixes the readability of colorized output of compile.sh when running on a terminal with a light background. It uses the COLORFGBG environment variable similarly to how the ip(8) command does. Before: After: How Has This Been Tested? Compile command: ./compile.sh BOARD=nanopim1 RELEASE=bookworm KERNEL_CONFIGURE=no BUILD_MINIMAL=yes PREFER_DOCKER=no BRANCH=edge BUILD_ONLY=u-boot [X] Run in Konsole on a light background (COLORFGBG=0;15) [X] Run in Konsole on a light background (COLORFGBG unset) [X] Run in Konsole on a dark background (COLORFGBG=15;0) [X] Run in Konsole on a dark background (COLORFGBG unset) [X] Visually inspect the results 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 N/A [ ] I have made corresponding changes to the documentation N/A [X] My changes generate no new warnings [ ] Any dependent changes have been merged and published in downstream modules N/A View the full article

Description Fixed issue that prevented armbian-bsp-cli package for meson-s4t7 family to uninstall because of the added /etc/initramfs-tools/modules file. As this required custom code to be added in the postrm script of the package, I have added support for the same in armbian-bsp-cli package similar to how things worked for postinst script. 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] Tested that armbian-bsp-cli-vim4-legacy package uninstalls fine. 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 Fix regression caused by my previous PR #6248 that broke compilation for clearfog uboot. This PR refactors the patching logic to a separate function thereby making it easy to use outside uboot.sh. During the process I also noticed that uboot_prepatch_version variable being initialized as part of that logic was not really being used anywhere. Hence removed the same. 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 for meson-s4t7 [X] Test build for clearfog 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

Description Bumped uboot and overlays to match Fenix 1.6.4 release. I also noticed that since my last PR, my u-boot patch to enable setexpr command was not getting applied. Turns out we were not handling patching if build_custom_uboot extension was being used. Hence moved the relevant code so that its used in both cases. 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 and booted image for khadas-vim4 Checklist: [ ] 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

aml-s9xx-box uses the u-boot shipped with the TV Box instead of installing a new u-boot. Because of this, armbian-install will make the box unbootable if it is run to install to emmc. This change prevents running armbian-install on aml-s9xx-box boards Changes to be committed: modified: packages/bsp/common/usr/sbin/armbian-install 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. 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] Tested running armbian-config and armbian-install on TV Box and it exits cleanly [X] Tested on a non TV Box that armbian-install works as expected 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

rk35xx-legacy: 0000.patching_config.yaml with incremental: true for rk 5.10 vendor kernel patching: support 'incremental' Makefile auto-patching, for vendor kernels without incremental: true: we replace the DT Makefile based on *.dts at the DT directory after all patching/copying is done overlay target is added if overlays present with incremental: true: we parse the Makefile, parse the DTs being built, and only add .dts's we have added from 'dt' directory overlays target are not added; we assume smth else already added them rk35xx-legacy: 0000.patching_config.yaml with incremental: true for rk 5.10 vendor kernel allows users to put .dts files bare in userpatches/kernel/rk35xx-legacy/dt important: everyone is still invited to send the DTs to https://github.com/armbian/linux-rockchip directly where yes, they'll have to patch the Makefile there as normal View the full article

Description thead: update current&edge kernel, fix pinctrl config. How Has This Been Tested? [x] Successfully built. [x] System startup. 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 Minor edit in the description in reference to the 32GB ram model How Has This Been Tested? Just a comment that has been updated. 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.76. How Has This Been Tested? [x] 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

Description Added DMA support for H616/H618 devices. Added overlays for interfaces available on 26-pin header of orangepi zero2 and zero3. The 26 pin headers can provide upto 3 i2c interfaces, 2 pwm, 2 uarts and 1 spi with 2 chip selects. I have added overlays for the 3 i2c and 2 uart interfaces. I didn't saw the pwm suppport yet in the kernel and hence have skipped the same. For spi, the existing spidev1_0 and spidev1_1 seems to apply fine. As part of this PR, I am also stepping down as the maintainer. As a wip device needs a maintainer, I have moved the device to be csc instead. Any further development for this device should be handled by the community. 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] Tested patch applies and both kernel builds fine. [X] Tested all the overlays applies correctly on 6.7 kernel and their corresponding device nodes appear in /dev. I don't have any peripherals to attach and hence detail testing is not performed. 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

Description The command added to check whether the directory is git or not was having syntax error. Fixed the same. Also it seems adding safe-directory with local doesn't really work which actually makes sense. hence reverting to using global instead. Its still safer than before as we are not adding * and are adding the actual path of the directory Fixes following error in the logs --> (9) COMMAND: git --no-pager -C /home/flash/build-fork/cache/git-bare/kernel -C rev-parse --git-dir -->--> command failed with error code 128 after 0 seconds --> (9) WARNING: stacktrace for failed command [ exit code 128:git --no-pager -C /home/flash/build-fork/cache/git-bare/kernel -C rev-parse --git-dir regular_git() --> lib/functions/general/git.sh:44 git_ensure_safe_directory() --> lib/functions/general/git.sh:58 kernel_prepare_bare_repo_from_oras_gitball() --> lib/functions/compilation/kernel-git-oras.sh:232 do_with_hooks() --> lib/functions/general/extensions.sh:557 do_with_logging() --> lib/functions/logging/section-logging.sh:81 compile_kernel() --> lib/functions/compilation/kernel.sh:30 artifact_kernel_build_from_sources() --> lib/functions/artifacts/artifact-kernel.sh:230 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 ] 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] Ran compilation both inside and outside docker-shell. 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 Fix missing lightdm wallpaper. I noticed that the directory path in slick-greeter.conf is not correct. Our wallpapers are in armbian-lightdm directory. When checked in xfce image for vim4, /usr/share/backgrounds/lightdm was missing. Haven't tested the fix yet, but this seems to be the most obvious reason behind the missing lightdm wallpaper. 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 Unstable / testing packages sometimes contain hacks that are patching files. Fixing this in Debian Sid / Trixie Not sure why this happens, but we certainly don't need this check in rolling releases. [🐳|🌱] Checking MD5 sum of installed packages [ debsums ] [🐳|🔨] debsums: changed file /usr/sbin/start-stop-daemon (from dpkg package) [🐳|💥] Error 2 occurred in main shell [ at /armbian/lib/functions/logging/runners.sh:211 How Has This Been Tested? [x] Manual run 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 Some boards needs to be re-promoted, some retired. Welcome to add commits to this PR by the end of February. Please check https://docs.armbian.com/User-Guide_Board-Support-Rules/ prior to proposing. How Has This Been Tested? Board status change. View the full article

BananaPi CM4/M2S Update to u-boot v2024.01 Fixup meson-g12b-waveshare-cm4-io-base-b.dts Removed from 'fanctrl' node: #address-cells = <1>; #size-cells = <0>; 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

Description station-m3: move to rockchip-rk3588 family. Add UEFI_EDK2 support for station-m3. Remove the fan control binary file because automatic fan control has been added in this commit. How Has This Been Tested? [x] Almost all hardware functions(HDMI, WiFi, BT, GbE, USB...). [x] System startup. 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 Minor formatting fix. extensions should use tabs as indentation as @viraniac pointed. Definitely not mixed space/tabs. Also minor fix in examples to fully comply with spec. View the full article

Description Hi. mvebu has been moved to csc some time ago. Now every once in a while a patch breaks and we have to remove it / fix it. Russel King keeps a pretty up to date kernel tree for clearfog over at http://git.armlinux.org.uk/cgit/linux-arm.git/log/?h=clearfog So I tried to move our mvebu-edge to be based on his work. This allows us to include lots of mvebu patches without the need to maintain them. I would like to discuss the advantages and disadvantages with you! Also this is some movement to finally get the helios4 pwm patch mainlined over at the linux-pwm/gpio/kernel mailing list. Jira reference number AR-2015 How Has This Been Tested? Ran kernel build. View the full article

Description Fix uwe5622 load average. Patch is based on @pyavitz patch from his repository. Bumped Allwinner u-boot to 2024.01 from 2024.01-rc5. And increased kernel log buffer size. 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 and booted on Orange Pi 3 LTS 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

2023 was a great year for the Wayland driver for Wine. After several merge requests, many people are now already able to use the latest Wine release to enjoy some of their favorite Windows applications in a completely X11-free environment! View the full article

Description RTW88 driver has some problems (no working AP mode, wifi connection fails after 2-3 days, speed problems) on RTL8822CS SDIO modules. So: update rtl88x2cs commit sha to latest version add armbian_kernel_config hook to enable driver in kernel config (only for meson64 family) add jethub boards hook to blacklist rtw88 module in image (by default rtw88 loads first) Jira reference number AR-2033 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 family WiFi works [ ] Need to be tested on other family boards 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

Description GitHub Actions security feature. https://github.com/crazy-max/ghaction-github-labeler/issues/184 How Has This Been Tested? We use this way on armbian/os https://github.com/armbian/os/blob/main/.github/workflows/labeler.yml View the full article

Description Adding broadcom wifi modules to the rk35xx legacy kernel configuration. The edge configuration already has these. This are supported hardware that shipped as optional accessories with the Rock 5b (Official adapter list) 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] Compiled kernel with new options, deployed to rock-5b board, and validated wifi module (A1) connectivity. % ls /sys/class/net/wlan0/device/driver -l lrwxrwxrwx 1 root root 0 Jan 27 13:21 /sys/class/net/wlan0/device/driver -> ../../../../../../../bus/sdio/drivers/brcmfmac % ip l show wlan0 3: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP mode DORMANT group default qlen 1000 link/ether 08:fb:ea:xx:yy:zzbrd ff:ff:ff:ff:ff:ff 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 Reworked u-boot compilation for meson-s4t7 to make sure we are following same process for u-boot compilation as Khadas. Now we are not compiling it twice like we were doing it before as mentioned in #6112. Added post install script in uboot with option to force upgrade the same. The code is based on what is being used in armbian-config's bootloader update code. Also moved tinkerboard specific code out to tinkerboards's config 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] Tested both vim1s and vim4 boots [X] Tested upgrade with using deb files. I will also test it using beta repository after these changes are merged [X] Checked the postinst script of tinkerboard's u-boot to ensure that the code that I moved is present in postinst script. Checklist: [ ] 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 Basic support has been added, WIFI and Bluetooth are now working, the sound card can be recognized, and GPU cannot be used because the panel driver cannot be used. Currently, only simple fb can be used, and touch cannot work due to geni report some dma error, which requires some work Touch driver from https://github.com/qaz6750/linux/commit/bdfe4cfd872e8c8ff484e263dcf534e2f1844775 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] Boot and enter the Shell [x] Screen can display the desktop [x] WiFi&BT [x] USB RDNIS [x] Vol Up and Vol Dn Can be used, power button also work (pressing it will suspend,If it is a shell interface, it will shut down directly) 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