SBC News

artifacts (all): implement DONT_BUILD_ARTIFACTS=any (so we don't need to list them all for CI image builds) View the full article

Description Remove PGP signing from the script as its done in GHA. Also remove generating .current control file as its obsolete in this design. Also remove rootfs-cache alias as we are anyway making action script from scratch. Nobody else uses this. View the full article

Description Affected: Orangepi 3 LTS and Zero 2 Jira reference number AR-1396 How Has This Been Tested? [x] Opizero2 red led light up at once 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

Linux 6.1 (current) / 6.4 (edge) Add "current" to: config/boards/bananapim2pro.csc Add uart_A uart_AO_B and uart_B to: meson-sm1-bananapi.dtsi Add related pins to: meson-g12-common.dtsi Add the ability to enable via overlays 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

Linux 6.1 (current) / 6.4 (edge) Add "current" to: config/boards/bananapim2pro.csc Add uart_AO_B and uart_B to: meson-sm1-bananapi.dtsi Add related pins to: meson-g12-common.dtsi Add wif/bt support to: meson-sm1-bananapi-m5.dts (BT = uart_A) Add the ability to enable via overlays NOTE: The overlay to enable the wifi on the BPI-M5 will be added at a later date. 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…

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 Small functional fixes, otherwise cosmetic change: How Has This Been Tested? [x] On dev machince and several working ones. 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

Description Any mounted directory should not be copied but also mounted on the new boot device when booting. Jira reference number AR-2043 Closing https://github.com/armbian/build/issues/6242 How Has This Been Tested? Need testing ! [ ] Fresh install to eMMC media [ ] Install to eMMC with configured zfs device 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 Bug reporting form needs to be extended with a question: How to reproduce? View the full article

Description Currently we were bumping nightly build version at the end which caused problems. Now version is bumped at start, then we clean possible left overs and start with the train. How Has This Been Tested? [ ] Several manual runs 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 Divide kernel config ownership more precise. Jira reference number AR-1435 View the full article

Description Fix #6857 and add 10 seconds network timeout to initramfs ssh daemon waiting for cryptroot-unlock password GitHub issue reference: #6857 Jira reference number [AR-2401] How Has This Been Tested? [x] Succesfully running CRYPTROOT_ENABLE="y" nanopi-r5c [x] Succesfully running CRYPTROOT_ENABLE="y" orangepi5-plus 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 GitHub provides issue forms for opening an issue. Lets implement it and improve UX. Jira reference number AR-1470 How Has This Been Tested? Demo: https://github.com/igorpecovnik/linux-orangepi/issues/new/choose 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 add information to the places where people might looking for it try to resolve confusions remove unnecessary infos Jira reference number AR-1284 How Has This Been Tested? Text changes only. 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 losetup -f always return 1st free loop device and in parallel build it often happens that same is found which results in: failed to set up loop device: Device or resource busy If we seek random way, chances of allocating the same device are significantly smaller. Jira reference number AR-1582 How Has This Been Tested? [x] Few manual 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 [x] My changes generate no new warnings [x] Any dependent changes have been merged and published in downstream modules View the full…

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. [ ] Test A [ ] Test B 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 ne…

BPI-CM4: In accordance with the BSP DTS, set LED gpio to GPIO_ACTIVE_LOW. Added default-on trigger to led-green Board now powers off, added reboot node 'meson64-reboot'. CONFIG_POWER_RESET_MESON64 Isolated RESET ODROID driver and renamed to MESON64 as it can be used in more than ODROIDS. MESON UART Series improves support for UART attached Bluetooth modules on Amlogic Meson G12A and newer SoCs. These SoCs also support the "divide XTAL by 2" bit which (greatly) reduces jitter when generating baud rates such as 1500000 (which is used by the Bluetooth part of the RTL8822CS SDIO WiFi and UART Bluetooth combo chip). Jira reference number [AR-9999] How Has This Been Tested?…

Backport DTS/DTSI changes from linux-6.4.y to 6.1.y Add meson64-reboot driver to all boards Add board: ODROID N2L Add uart_A uart_AO_B uart_B uart_C where appropriate U-Boot v2023.07.02: ODROID N2/N2L/N2Plus/C4 Meson64-reboot driver: (source: tobetter) While the current meson64-reboot driver is cleaner and doesn't depend on modding other kernel sources, its functionality leaves much to be desired. One example can be found in the ODROID C4. Using the current driver, the board will not properly power off, leaving the POWER LED still on. The new driver powers off the unit completely. Fan control: (ODROID N2L/N2PLus) Added service and script for controlling the trip point. …

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 FIXE…

Description Script was chowning all files in the home folder each time desktop package was updated. Jira reference number AR-1403 How Has This Been Tested? [ ] 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 Those are just small left over fixes for AR-1444 How Has This Been Tested? [ ] Manual repo generation Checklist: [ ] My changes generate no new warnings View the full article

Description Integrating deboostrap hack directly into build framework instead of having it as extension. better compatibility with host system support for Debian variants too doesn't break on making docker images future proof and auto-obsolete when host systems deboostrap version passes 1.0.128 Jira reference number AR-2004 How Has This Been Tested? [x] Generating Docker images [x] Generating Ubuntu noble 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…

Description How Has This Been Tested? Setting a version to pinning file and reinstalling / upgrading packages. Checklist: [ ] 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

include (clean/real) apt lists and xapian cache in built images (not in rootfs cache) include (clean/real) apt lists in built images; update xapian index during image build, not rootfs; don't leave junk in the rootfs cache revert #5139 Revert "Apt lists is needed for synpatic index generation" - This reverts commit 63e9bd3baad4f6faa8e6e6f6c82e46716b89acf7 - this actually only left junk in rootfs cache for the future to find Now when building images, at the end: Notice how "53" lists where copied (from host-side cache) into the image, and then updated & cleaned, resulting in "32" lists at the end. This is a clean, junk-free, and updated apt lists. On top of…

This ensures that the armbian-audio-config script actually works in minimal builds too. This fixes #5012 (AR-1644) How Has This Been Tested? ./compile.sh BOARD=orangepipc BRANCH=current RELEASE=jammy BUILD_MINIMAL=yes BUILD_DESKTOP=no KERNEL_CONFIGURE=prebuilt booting it Installing mpg321 Trying to play some audio file on the minijack output: mpg321 -a hw:0 sample-15s.mp3, which produces audible sound Using alsamixer to see that the "Line out" control of card 0 is indeed successfully unmuted and set to 45% (0dB), presumably by armbian-audio-config Checklist: [ ] My code follows the style guidelines of this project N/A [ ] I have performed a self-review of my own code…

BPI-M2S is a small form factor SBC based on the Amlogic A311D chipset (or s922x, not supported yet): Amlogic A311D (Quad A73 + Dual A53) CPU 4GB LPDDR4 RAM 16GB eMMC Mali G52-MP4 GPU HDMI 2.1 output 2 Gigabit ports 40 pins GPIO 1x USB-A 2.0 1 USB-C (5V power) Not working/tested: 2nd ethernet port MIPI DSI/CSI Description I created a dts from existing A311D board (vim3 and radxa zero2). I use the radxa zero2 u-boot that allows to launch armbian linux kernel for this board. The dts is basic for now, since I'm not an expert with device trees. Jira reference number [AR-9999] How Has This Been Tested? Please describe the tests that you ran to verify your changes. Pleas…

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-2050 How Has This Been Tested? Boots current and edge kernel from SDcard images Built-in WiFi works in both cases However, board will not allow clocking >1.0Ghz Built-in WiFi antenna is very weak Please describe the tests that you ran to verify your changes. Please also note any relevant details for your test configuration. [ x ] Generate current image [ x ] Generate edge image Checklist: [x] My code follows the style guidelines of this project [x] I hav…

Description New Linux family declaration featuring both flagship devices X13s and Microsoft devkit. No needed hacks implemented at this stage, untested, no hardware, but someone might take it from here:) @xlazom00 How Has This Been Tested? [x] Kernel builds, image structure looks o.k. 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

initrd: cache: add /etc/modprobe.d to cache key (eg for MODULES_BLACKLIST) initrd: cache: add /etc/modprobe.d to cache key (eg for MODULES_BLACKLIST) View the full article

initrd: if debugging, don't filter update-initramfs output (errors might be lurking in there) initrd: if debugging, don't filter update-initramfs output (errors might be lurking in there) View the full article

initrd: when cache hit, don't preserve perms during deploy, otherwise FAT32 /boot gags AR-1715 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 Support partner. How Has This Been Tested? [x] Was reported as working good. Checklist: [x] Any dependent changes have been merged and published in downstream modules View the full article

Description We are using debsums to check packages integrity. This packages is present in all distributions, we only need it for checking. After the installation, package was removed. Lets move this from packages lists. Jira reference number AR-1455 How Has This Been Tested? [x] Assembly of one rootfs 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 install xfce4-power-manager by default on xfce desktop remove x11 config which is obsolete and prevent dkms functinality remove per board power manager install Jira reference number AR-1186 How Has This Been Tested? [x] Tested manually in VM [ ] Tested on bare metal 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 Since systemd journal can have its persistent files in /var/log/journal and may be softlinked to /var/log/journal, it needs to be safely recreated during the installation process. 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] installed fix on up-to-date neo2 apt update && apt upgrade on nanopi neo2, copied updated nand-sata-install and exclude.txt, run nand-sata-install to install image to nand, restarted from NAND verified that /var/log.hdd/journal is a folder for persistent journald logging verified that /var/log/journal is symlink to…

Description Fixing https://github.com/armbian/build/commit/26fb31cfbfae41557f75ad8669e03e28bbc0aa0a#commitcomment-111843350 How Has This Been Tested? Tested thoroughly with custom builds. 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 Fake vcgencmd allows requesting information from a non-Raspberry Pi board in the same way that can be done via an executable on there. Since this command is now available, the Armbian board can also be monitored, rebooted etc via eht FOSS Android app RasPi Check. See also: https://f-droid.org/en/packages/de.eidottermihi.raspicheck/ https://github.com/eidottermihi/rpicheck/issues/161 https://forum.armbian.com/topic/17069-android-app-to-monitor-and-restart-boards/#comment-119650 https://github.com/clach04/fake_vcgencmd Jira reference number [AR-9999] How Has This Been Tested? Yes, made a build and it worked, also via the Android app. Checklist: [x] My cod…

Description The media board family was long abandoned and most boards that formerly were using this board family already switched to rockchip64 or rk3588. @rpardini recently mentioned being in favor of getting rid of this kernel: https://github.com/armbian/build/pull/6717#discussion_r1632321571 Integrate the last remaining boards into rockchip64 and remove the media board family, including its kernel. GitHub issue reference: https://github.com/armbian/build/issues/6821 Jira reference number AR-2392 How Has This Been Tested? [x] ./compile.sh uboot BOARD=quartz64a BRANCH=edge BUILD_DESKTOP=no BUILD_MINIMAL=no EXPERT=yes KERNEL_CONFIGURE=no RELEASE=trixie [x] ./compile.s…

interactive: show all possible KERNEL_TARGET's in branch selection UI; handle current/edge/legacy, others are "experimental" interactive: show all possible KERNEL_TARGET's in branch selection UI; handle current/edge/legacy, others are "experimental" remove midstream special handling View the full article

Description Move executing check from the script. It breaks if script runs for beta and stable at the same machine. Which will be the case. Checklist: [x] My changes generate no new warnings View the full article

Description Resolving 3d and multimedia extensions confusions. Replacement for: https://github.com/armbian/build/blob/main/extensions/mesa-oibaf.sh https://github.com/armbian/build/blob/main/extensions/rk-multimedia-amazingfate.sh https://github.com/armbian/build/blob/main/extensions/rk-panthor.sh and custom one: https://github.com/armbian/os/blob/main/userpatches/extensions/amazingfated-rk3588.sh How Has This Been Tested? [ ] Made all test images with enabled extension Checklist: [ ] My changes generate no new warnings [ ] Any dependent changes have been merged and published in downstream modules View the full article

Description Yes, we have documented the maintainers in armbian/documentation. But it seem like that some of them don't maintain anymore. Use a separated repos make us forget to update it. So let's document here. What's more, defining this make us easier to update .github/CODEOWNERS The way to find out the BOARD_MAINTAINER has documented in the commit messages. The script to do this #!/bin/bash SRC="$(realpath "${BASH_SOURCE%/*}/../")" readarray -t members < <(curl -L -H "Accept: application/vnd.github+json" -H "Authorization: Bearer ${TOKEN}" "https://api.github.com/orgs/armbian/members?per_page=100" | jq -r .[].login) doc="$(curl -L https://github.com/armbi…

Description Digging and reworking this https://github.com/armbian/build/pull/6100 while (de)attaching to new LTS kernel. Jira reference number AR-2005 How Has This Been Tested? 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 The full log make debug easier. How Has This Been Tested? 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 Bluetooth on PBP is currently broken and this might fix it. No hw to test but: https://github.com/armbian/build/pull/4608#issuecomment-1364484639 View the full article

Description Add support for onboard eeprom in JetHub D1+ devices. Jira reference number AR-1907 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] current/edge build [ ] Test B 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 articl…

Description Prepare for support JetHub D1p device. All working now. uboot 2022.07 (only jethome devices) update uboot jethome patches (add support for amlogic unifykey in eMMC, rewrite is needed) some updates for kernel patchset (update in jethub device tree) all changes only for jethub devices. Work will be progress. Jira reference number AR-1232 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 D1p [] Test B Checklist: [ ] My code follows the style guidelines of this project [ ] I have performed a self-review of my own code [ ] I have commented m…

Description JetHome: fix u-boot patches for rescue button. Applies only to JetHub devices Jira reference number AR-2081 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] Fixed JetHub D1/D1+ [ ] Test B Checklist: [X] 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 modu…

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 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 Rework JetHub BSP files: enable CPUFREQUTILS by default (force CPUMIN/CPUMAX settings) update init service to match new gpio numeration in kernel 6.2+ add new /dev/serial/rs485/ aliases for RS485 ports in JetHub D1/D1+ no changes in other boards/base files Jira reference number AR-1553 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 D1+ boots ok 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…

Description JetHome: u-boot: add bugfix for broken efi code in commit a9bf024b2933bba0e23038892970a18b72dfaeb4 No impact on other boards. Jira reference number AR-1296 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 D1 boots ok [X] no impact on other boards View the full article

Description JetHome: u-boot: add bugfix for broken efi code in commit a9bf024b2933bba0e23038892970a18b72dfaeb4 No impact on other boards. Update for https://github.com/armbian/build/pull/4112: add JetHub H1 u-boot patch Jira reference number AR-1296 View the full article

Description Update for AR-1553: Update symlink names for RS485 Adapters on JetHub D1/D1+. Simple change. Jira reference number AR-1553 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 [ ] Test B 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 mo…

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

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

Description JetHome: Update u-boot: move to 2023.10 remove old eMMC HACK add upstream RFT emmc patches Only JetHub devices should be affected by the change. Jira reference number AR-1879 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 H1 boot ok [X] JetHub D1+ boot ok 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 warn…

@adeepn @rpardini As discussed here: https://github.com/armbian/build/pull/5315 In order to update to the latest rtl8822cs BT firmware for the G12/SM1 family of boards and still provide the downstream firmware for the AXG/GXL family, I created an apt hook to ensure the proper firmware stays in place. I unfortunately can’t test this beyond creating an IMG as I don’t own the unit and the firmware isn’t currently committed. In order to test, someone would need to boot an IMG built from this commit, add the latest firmware to the booted unit and install a package to see if the apt hook works. Firmware commit: https://github.com/pyavitz/armbian-firmware/commit/a7bf7c7cc8a8…

Description JetHub BSP: update preinstalled python packages to install via apt Jira reference number AR-1545 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 on jammy, bullseye, sid,lunar [ ] Test B 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 downs…

Description This PR add some tweaks to get the current (and IMO best possible yet) configuration of the WDK. point to latest development branch which appears to be quite stable add package mtools to support mounting the EFI partition, enable mount add tweak to ensure qrtr-ns.service also runs, like protected-domain-mapper add board file with calibration data that work well with the QCNFA765 Wireless Network Adapter 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 the image with ./compile.sh build BOARD=wdk2023 BUILD_DESKTOP=yes BUILD_MINIMAL=no DESKTOP…

jsoninfo: add inventory-artifacts cli, which stops after artifacts-reduced and adds kernels.ndjson and uboots.njdson via jq jsoninfo: add inventory-artifacts cli, which stops after artifacts-reduced and adds kernels.ndjson and uboots.njdson via jq if one runs ./compile.sh inventory-artifacts we shall get: output/info/kernels.ndjson: one line for each kernel build output/info/uboots.ndjson: one line for each u-boot build this is meant as base for other tooling that acts "for each kernel" or "for each u-boot" such as patch/config rewrites, etc View the full article

Description Update K3 edge Linux kernel to v6.5 and U-Boot to v2023.10-rc3. Plus a couple minor cleanup patches to k3.conf How Has This Been Tested? [x] Build and boot on SK-AM64B [x] Build and boot on SK-AM62B 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 The causes the first-stage bootloader to be generated before the normal U-Boot allowing the later build to use the firmware fetched during the first-stage build. How Has This Been Tested? [x] Boot SK-AM62B 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 was going to be used if building the bootloader from external source did not work. As this did work we never needed this blob, remove it. How Has This Been Tested? [x] SK-AM62B still builds and boots without this file 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 The latest ATF has several fixes and improvements for the K3 platform. The current default ATFBRANCH is rather old (and should be updated, but I don't have all the other platforms needed to test right now). For now update to the latest stable tag for K3 platforms. How Has This Been Tested? [ ] Build and boot SK-AM64B [ ] Build and boot SK-AM62B [ ] Build and boot SK-TDA4VM 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 [x] 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

kde-neon: use Neon's "user" repo for Jammy & return it to csc status kde-neon: use Neon's "user" repo for Jammy & return it to csc status for noble: keep on Neon's "testing" repo which now has a "noble" dist (instead of Jammy) - but keep it eos as it really doesn't build yet. See https://blog.neon.kde.org/2024/05/09/kde-neon-rebasing-on-ubuntu-noble/ - might take a while still View the full article

Description Keep empty line in armbianEnv.txt How Has This Been Tested? [ ] Test A 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 Ubuntu variants were somehow forgotten when adding systemd-resolved in https://github.com/armbian/build/pull/6142 Jira reference number AR-1657 How Has This Been Tested? [x] Generating Ubuntu Jammy image 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 On images with changed vendor, when update comes from Armbian repository, VENDOR is overwritten. This change keeps the VENDOR variable from image. 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 [x] My changes generate no new warnings [x] Any dependent changes have been merged and published in downstream modules View the full article

kernel / drivers-harness: use the kernel git SHA1 ($KERNEL_GIT_SHA1) instead of $KERNEL_MAJOR_MINOR for drivers cache key kernel / drivers-harness: use the kernel git SHA1 ($KERNEL_GIT_SHA1) instead of $KERNEL_MAJOR_MINOR for drivers cache key this should avoid (late) patching errors that might happen during a point release bump like 6.4.5 -> 6.4.6 cos we'd be using the wrong cached drivers patch using the SHA1 will instead (possibly) trigger the "real patching failure", during drivers-harness when building a new driver patch cache also try to cleanup old caches in the old format so we've not many leftovers -- each patch is ~150mb View the full article

Description A change to ledtrig_netdev driver causes the boot to fail on Orangepi-r1plus-lts and possibly other boards. The board boots and LED netdev trigger works if service is modified to occur later in the boot sequence by using After=timers.target in armbian-led-state.service. Jira reference number AR-1875 Issue discussion rockchip64: bump rockchip64-edge kernel to 6.5#5657 How Has This Been Tested? Tested on current and 6.5y Rockchip64 and other (H5). The following configurations were tested for boot, reboot and shutdown then boot and that LED's light when network is connected and LED's flicker on network activity: [x] Orangepi R1 Plus LTS with Kernel 6.5y with…

Description Small semi automated changes to the config. How Has This Been Tested? [x] Build affected kernels 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 What comes out of automation - no other changes. How Has This Been Tested? Haven't been tested, CI will do this job. Checklist: [ ] My changes generate no new warnings [ ] Any dependent changes have been merged and published in downstream modules View the full article

kernel drivers: replace all "branch:xxx" references with sha1; hash the whole of patch/misc stacktraces: introduce get_stacktrace_element_by_index() to get a specific stracktrace element git: fetch_from_repo(): introduce FETCH_FROM_REPO_CALLBACK_IF_REF_MUTABLE function defined in FETCH_FROM_REPO_CALLBACK_IF_REF_MUTABLE is called if reference is mutable which is anything that's not commit: or tag: and really there's no guarantee that tag: is immutable, but lets assume drivers-harness: hash the whole of patch/misc; throw error if driver does fetch_from_repo with mutable ref this should make drivers hash consistent, at the expense of being moar tiresome any change…

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 We package kernel debs with package name like linux-image-legacy-rk35xx. In general people treat legacy-rk35xx as the flavor. Debian's live-build will use it to generate grub config: https://salsa.debian.org/live-team/live-build/-/blob/master/scripts/build/binary_grub_cfg#L117. And ubiquity which is ubuntu's desktop installer also looks for it. So it's better to change our kernel filename to standard like vmlinuz-*${flavor}. 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] Build success for rk35xx legacy kernel [x] …

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. [ ] Test A [ ] Test B 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 ne…

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. [ ] Test A [ ] Test B 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 ne…

See #4854 View the full article

Description Fix/rewrite-kernel-config two kernel configs (mvebu64-current and sun50iw9-btt-legacy) to adapt them to the latest wireless driver updates in drivers_network.sh. Without doing a rewrite-kernel-config refresh, their kernel builds might potentially fail due to misconfigured wireless driver modules. Checklist: [x] My changes generate no new warnings View the full article

kernel-debs: headers: hack/fix for 6.5-rc1's "tools/counter: Makefile: Remove lingering 'include' directories on make clean" kernel-debs: headers: hack/fix for 6.5-rc1's "tools/counter: Makefile: Remove lingering 'include' directories on make clean" introduced at https://github.com/torvalds/linux/commit/228354ed692faa08f40f2630658c0771f77da457 simply creating the dir solves it reported to author, let's hope for an -rc2 fix. better logging when DEBUG=yes (don't pass "-s"(ilent) to make clean) View the full article

kernel-dtb: copy also the dtb binary for the board to output kernel-dtb: copy also the dtb binary for the board to output View the full article

kernel-headers: don't try to build objtool if not amd64 target (for real this time) I severely messed up last night, copied instead of moving, into an if block. Delete so it's a move now. View the full article

Description Bumped Allwinner kernels Legacy: 5.15.120 -> 5.15.121 Current: 6.1.39 -> 6.1.40 Edge: 6.4.4 -> 6.4.5 5.15.121 needed same patch fixes as done for 6.1.39 in PR #5494 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] Booted legacy, current and edge images on Orange Pi Prime (sun50i H5) [X] Booted legacy, current and edge images on NanoPi Duo2 (sun8i H3) 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…

Description Add support for RPi5 in our bcm2711 kernel. This is mostly but not entirely based on changes from Raspberry Pi kernel PR 5618. After enabling those options, I noticed that even though hdmi was working, kernel was not able to find the sdcard and usb was also not working. So I had to use diffconfig to compare our configs with the vendor config and enable some more options. Raising the PR so that others can also play with it as well. Meanwhile I will work on getting Trixie Desktop Image running with mesa 23.3-rc5 from experimental repo. As part of that I will split RPi 5 into separate board config until recent version of mesa is made available in current debian …

Description Bump mainline from 6.8-rc7 to 6.8 stable This currently affects only rk3588-edge Bump UEFI-edge from 6.7 to 6.8 [DOES NOT COMPILE YET!!!] Kernel configs updated via ./compile.sh rewrite-kernel-config Kernel patches updated via ./compile.sh rewrite-kernel-patches The uefi-edge kernel does not compile without errors yet, because of drivers/net/wireless/rtl8192eu and the likes. Some patches need to be added or adapted for 6.8 in patch/misc, but I honestly don't know where to get these patches from. I could not find folders like /drivers/net/wireless/rtl8192eu/os_dep/ in the mainline kernel. Help is appreciated! ❤️ Build log for BOARD=uefi-arm64 BRANCH=ed…

kernel: call make with INSTALL_MOD_STRIP=1 so modules are stripped kernel: call make with INSTALL_MOD_STRIP=1 so modules are stripped also, don't add target 'install' twice View the full article

kernel: drivers: wireless-rtl8723du-6.3.patch: don't patch the same thing twice Can't really tell how this happened. Am I missing something, @paolosabatino? This removes second identical patch in the same file... View the full article

kernel: fix for 6.3+ linux-headers pkg due to upstream dir change extra: run kernel make through pipetty for moar colors Small detour: in v6.3-rc1, in commit https://github.com/torvalds/linux/commit/799fb82aa132fa3a3886b7872997a5a84e820062, the tools/vm dir was renamed to tools/mm. Unfortunately tools/Makefile still expects it to exist, and make clean in the tools dir fails. Drop in a fake Makefile there to work around this. Should fix #4991 View the full article

Description Bump the 6.10 kernel from 6.10-rc4 to 6.10-rc5. Includes kernel config rewrite for RK3588. How Has This Been Tested? [x] Build success: ./compile.sh BOARD=nanopi-r6c BRANCH=edge RELEASE=trixie EXPERT=yes KERNEL_CONFIGURE=no BUILD_MINIMAL=no BUILD_DESKTOP=no EXTRAWIFI=no kernel 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 [x] Any dependent changes have been merged and published in downstream modules View the full article

kernel: postinst: use --nofsroot option to findmnt when finding /boot's filesystem type otherwise we might get /dev/mmcblk2p1[/boot] when /boot is bind-mounted --nofsroot: don't print [/dir] for bind or btrfs mounts View the full article

Description Fixed thermal monitoring in 6.1 kernel caused by missing GPU trips. Also configured sw4 switch as power button for suspend/resume support for Orange Pi Prime. Jira reference number AR-1804 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] Booted on Orange Pi Prime and checked that armbianmonitor -M reports back the temperature [X] Booted all three kernels on Orange PI Prime and ensured that button is working fine for rebooting or resuming the board Checklist: [ ] My code follows the style guidelines of this project [ ] I have performed a self-rev…

Description I have changed the way the patches are generated a bit. Instead of using orange-pi branch from megous tree for 6.6 kernel, I have used the following 6.6 kernel branches from megous tree a83t-suspend, af8133j, anx, audio, axp, cam, err, fixes, mbus, modem, opi3, pb, pinetab, pp, ppkb, samuel, speed, tbs-a711, ths These branches were carefully chosen to include only allwinner related patches and remove importing of most of the rockchip related patches into the allwinner kernel. This has led to decrease in the total applied patch count by 84. We now apply 407 patches instead of 491 patches as applied in 6.5 kernel, while all functionality will remain the same. …

Description We had autofocus patches for ov5640 camera in allwinner current and edge kernel that were disabled due to patch application failure. This PR fixes the patch application failure and re-enables 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] Checked that patches applies on 6.4 kernel [X] Checked that patches applies on 6.4 kernel [X] Tested that autofocus works with 6.1 kernel on NanoPi Duo2 The following procedure was used to test autofocus with 6.1 kernel Compiled and enabled device tree overlay for ov5640 camera taken from the forum p…

Description legacy - 5.15.126 -> 5.15.127 current - 6.1.45 -> 6.1.46 edge - 6.4.10 -> 6.4.11 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] Booted legacy, current and edge images on Orange Pi Prime (sun50i H5) [X] Booted legacy, current and edge images on NanoPi Duo2 (sun8i H3) 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 …

Description Enabled CONFIG_RCU_TRACE as a workaround to fix booting 6.1.64 kernel on 32-bit allwinner boards. Edge kernel is not having this issue and hence workaround was not added for 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] Booted on Orange Pi Zero (sun8i H3) 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 warn…

Description A lot of people has been asking on the forums for host mode not working on the otg port in 6.1+ kernel. It seems to be caused by patches.megous/usb-musb-sunxi-Avoid-enabling-host-side-code-on-SoCs-where-it-s.patch. The patch claims to solve sleep issue (rtcwake not working) on pinephone. As we don't support pinephone, I don't see any issue disabling 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] Tested host mode works on otg port on Orange Pi Zero (H3) and NanoPi Duo2 (H3) [X] Tested rtcwake continues to work on NanoPi Duo2 (H3), Orange…

Description Removed rtl8822cs bluetooth patches from sunxi patch directory to make use of patches from driver harness. Also in the process I noticed that rtl8822cs bluetooth patches were upstreamed in 5.18 and were unnecessarily applied on newer kernels. Added condition to prevent the same in driver-network.sh 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 legacy, current and edge allwinner images and tested them on nanopiduo2 Checklist: [X] My code follows the style guidelines of this project [X] I have performed a self-review of my own c…