SBC News

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

Description Adding in kernel module for controller support for the rk3588 currently disabled in the kernel How Has This Been Tested? Untested 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 [ ] My changes generate no new warnings [ ] Any dependent changes have been merged and published in downstream modules View the full article

Linux Mint Vanessa 21.0 was already added. Now added the first point relese 21.1 named Vera. 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. Linux Mint Vanessa 21.0 was already added. Now added the first point relese 21.1 named Vera. Jira reference number [AR-9999] How Has This Been Tested? Already tested by myself on the local installation. No problems at all. Maybe because Linux Mint is based on Ubuntu Jammy. View the full article

Adding myself as a maintainer for the Orange Pi PC+ View the full article

adding new apps to build to allow for use of telegram/pidgin/discord and others View the full article

Adding in support for new desktop being added . i3 lxde lxqt and others to be added as made 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. Adding support for the fine3399 board. Documentation summary for feature / change Please delete this section if entry to main documentation is not needed. If documentation entry is predicted, please provide key elements for further implementation into main documentation and set label to "Needs Documentation". You are welcome to open a PR to documentation or you can leave following information for technical writer: Adding support for the fine3399 board How Has This Been Tested? Please…

Description Future Ubuntu development release, CSC. How Has This Been Tested? Builds, but we need to enable repository. Checklist: [x] My changes generate no new warnings View the full article

Description 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] I compiled a own build from my repository [x] Booting the system and the system booting up without any error in dmesg Checklist: Please delete options that are not relevant. [x] My code follows the style guidelines of this project [x] I have performed a self-review of my own code [x] My changes generate no new warnings View the full article

Description 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] I compiled a own build from my repository [x] Booting the system and the system booting up without any error in dmesg Checklist: Please delete options that are not relevant. [x] My code follows the style guidelines of this project [x] I have performed a self-review of my own code [x] My changes generate no new warnings View the full article

Description Few more fixes to config. Changes in patches affect RK3308 audio @brentr 3328 @paolosabatino ... I hope i didn't break something. How Has This Been Tested? [x] Build test 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 As stated in the tittle. View the full article

Description In several situations we need to have systemd-resolved installed and configured or we loose DNS. This happens in case of HA and most likely OMV too. As per documentation: systemd-resolved will work out of the box with a network manager using /etc/resolv.conf. No particular configuration is required since systemd-resolved will be detected by following the /etc/resolv.conf symlink. This is going to be the case with systemd-networkd, NetworkManager, and iwd. move DNS server set from Ubuntu specifics change switch to if and check for DISTRIBUTION instead of RELEASE detach bullseye so we can keep it operational without systemd-resolved change bullseye to EOS Ins…

Description Maintanace. Jira reference number AR-1444 How Has This Been Tested? [x] Run View the full article

Description removing network manager dependency. Left over from moving networking into extensions. address errors when wireless networking is still not detected Jira reference number AR-2390 Documentation summary for feature / change How Has This Been Tested? [x] Several images on board without wifi only [x] Tested making wrong wifi password 3x, exits with "Unable to connect to AP" [x] Connecting with correct credentials [x] Choosing to not connect to wireless [x] Tested on NM and systemd networkd 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 Adds i2c3, pwm1, pwdm2, spi0 and uart1 nodes to rk3568-odroid-m1.dts. Adds patch to remove spi-dev warning Adds patch with support for overlay compilation Adds DTS overlays for spi, uart0, uart1, pwm1, pwm2, pwm9, i2c0 and i2c1 How Has This Been Tested? This was tested with a 4GB M1 board. The [x] SPI0: tested with a SPI OLED display [x] uart0, uart1: loopback test [x] pwm1, pwm2, pwm9: with scope [x] i2c0, i2c1: with scope 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 …

Description General: disable kernel boot splash > 6.1 We don't use it anymore and its time to go rest. Adjust 881xau, 8811cu, 88xbu @adeepn you have a patch for 6.1 ready? For jethome-ru/rtl88x2cs Jira reference number AR-1432 How Has This Been Tested? [x] Build test Checklist: [x] My code follows the style guidelines of this project [ ] 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 I have changed label for pull request that is more telling what it means. This action depends on label change, so we need to adjust it. How Has This Been Tested? None. Parameter name change 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 Jira reference number AR-1449 How Has This Been Tested? [ ] Tested in working branch 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 address wrong target we can expose two targets max Jira reference number AR-1386 How Has This Been Tested? This is fixing after the test 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 Adjusting XFCE skel to add WindowScalingFactor and few additional monitor cominations. Jira reference number AR-1324 How Has This Been Tested? [x] Tested on x86 xfce desktop 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 remove Budgie and KDE desktops as they are not in a best condition remove Sid add minimal images where useful Jira reference number AR-1368 View the full article

Description View the full article

Description Maintanace Jira reference number AR-1351 View the full article

Description Maintenance job. We provide options to build several desktop combinations, but we don't have a mechanism for verifying if those targets still work. I developed a simple action script that cycles all variants that are either supported or community supported. Community supported will only check for deboostrap success. This commit is a result of reading build logs of that Action script. Kde-Neon is in EOS zone as it doesn't build anywhere (atm). AR-2358 How Has This Been Tested? [x] Targets were tested for (x86 qemu which will be further tested on VM once CI extents to this functionality) image compiling. Checklist: [x] My code follows the style guidelines …

Description Lets keep consistent board naming. @jeanrhum Checklist: [x] My code follows the style guidelines of this project [x] My changes generate no new warnings View the full article

Description Based on https://github.com/armbian/build/issues/4690 Jira reference number [AR-9999] How Has This Been Tested? [x] Using the command [ ] ??? [ ] Profit 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 This obviously needs adjustment for armbian-next. View the full article

Description Maint. How Has This Been Tested? [x] Build test Checklist: [x] My changes generate no new warnings View the full article

Description Maint. How Has This Been Tested? [ ] CI build Checklist: [ ] My changes generate no new warnings [ ] Any dependent changes have been merged and published in downstream modules View the full article

Description After merging #4958 many patches are breaking the build. We need to adjust them. Jira reference number AR-1780 How Has This Been Tested? [x] Boot test Nanopi Neo 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 Bugfix Jira reference number AR-1348 How Has This Been Tested? [x] Build test 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 As per title How Has This Been Tested? [ ] hasn't 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 [ ] My changes generate no new warnings [ ] Any dependent changes have been merged and published in downstream modules View the full article

Lets us put down the hammer. Cleaned 6.1, 6.3 and added 6.2 patch set. Simplified function: rtw88_driver This PR was created in order to ease the pain here https://github.com/armbian/build/pull/5276 and add support for the current edge branch 6.2. 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 Fix logic. How Has This Been Tested? [x] Build current and edge kernel with rock3c 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 If we don't need to build u-boot, we can special BOOTCONFIG=none. But this will also prevent to copy bootscript. How Has This Been Tested? [X] Build 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 How Has This Been Tested? [x] Manual build Checklist: [x] My changes generate no new warnings View the full article

This also moves the console from UART2 to UART0, because the upgraded loader blob from Radxa only supports console on UART0. Discussion at: https://forum.armbian.com/topic/11228-rock-pi-s-rk3308-cpu-is-it-supported-by-anything/page/3 Description I don't have access to Jira. The bug being addressed would be that the images generated will only boot from the SDcard. They will not boot from the built-in EMMC. The issue is known to Radxa. 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. Configuration: Rock PI-S board with 4GB built-in SDNAND chip option Connected to bui…

Description Allow to use Docker credentials for oras-cli push artifacts when CI=true is set, but not in GitHub action. TODO: fix GITHUB_OUTPUT use if CI=true is set. Jira reference number AR-2357 How Has This Been Tested? [X] correct push to external container registry with CI=true 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 legacy - 5.15.124 -> 5.15.125 current - 6.1.43 -> 6.1.45 edge - 6.4.8 -> 6.4.10 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 n…

Description This PR ports over recent changes for the Orange Pi Zero 2 board brought by AGM1968 for 6.2.y kernel, back to 6.1.y kernel (current LTS). Changes being ported (minor modifications required to the patching metadata, overall code & structure intact): https://github.com/armbian/build/pull/5247 (CPU scaling) https://github.com/armbian/build/pull/5270 (on-board LED states changes) How Has This Been Tested? CPU scaling tests [x] Test A: Build & boot-up the board, making sure it still works [x] Test B: Run ThomasKaiser/sbc-bench See: https://github.com/mdziekon/armbian-build/pull/2 LED changes tests [x] Test A: Build & boot-up the board, making…

Description Bump Allwinner kernels Legacy - 5.15.x -> 6.1.x Current - 6.1.x -> 6.6.x Edge - 6.6.x -> 6.7-rc6 Removed old leftover kernel patch directories. 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. [ ] Edge kernel builds with EXTRAWIFI=no. Some driver harness drivers including xradio, rtl8189es, rtl8189fs, rtl8812au, rtl8192eu and possibly others needs some fixes as compilation fails for the same. 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, p…

Description Maint. How Has This Been Tested? [ ] Running legacy kernel on Nanopi Neo https://paste.armbian.com/juzupiburi Checklist: [ ] My changes generate no new warnings [ ] Any dependent changes have been merged and published in downstream modules View the full article

Description Bumping U-boot to 2024.01-rc5 for Allwinner boards. There were some defconfig patches that were failing, I have migrated them to board config file using post_uboot_config_target hook function. This has resulted into removal of several patches. There are still some defconfig patches left, I will move them as and when needed. Apart from that, updated crust support patches for Allwinner H3 as few of them had patch application failure. As U-boot now has AXP313 support, I have removed the patch for the same and have migrated Bigtreetech to use the upstream driver. How Has This Been Tested? Please describe the tests that you ran to verify your changes. Please also …

Description Current U-Boot compile on SUNXI 32-bit boards comes up with a couple of CONFIG_ redefined warnings. Root cause is allwinner-boot-splash.patch. If CONFIG_VIDEO or CONFIG_DM_VIDEO is defined, then this patch is defining a couple of dependent configs - regardless if those are defined already. Solution Wrap those defines with an appropriate if !defined pattern. How Has This Been Tested? [x] Test 1: Compile for a SUNXI 32-bit board - e.g.: /compile.sh u-boot BOARD=bananapipro BRANCH=current RELEASE=focal BUILD_MINIMAL=yes BUILD_DESKTOP=no KERNEL_CONFIGURE=no COMPRESS_OUTPUTIMAGE=sha,gpg,7z SYNC_CLOCK=no CREATE_PATCHES=no [x] Test 2: Compile for a SUNXI 64-b…

Description Bumped Allwinner edge kernel to 6.7-rc7 Added HDMI support for H616/H618 boards. The hdmi driver patch is based on changes from Orange Pi's 6.1 repo but is heavily modified to get applied on top of drm patches of megous tree. Removed 4.9 Orange Pi Zero 2 vendor kernel and legacy u-boot utilities Added WIP Orange Pi Zero3 board. 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. [ ] Testing current and edge kernel on Orange Pi Zero3 using XFCE desktop image [ ] Need someone to test on Orange Pi Zero2 Checklist: [ ] My code follows the style guidelines …

Description Bumped legacy, current and edge kernel. Legacy - 5.15.127 -> 5.15.130 Current - 6.1.47 -> 6.1.51 Edge - 6.5 -> 6.5.1 Fixed compilation of xradio and as its working fine, disabled cw1200 driver that I added for edge last week. Refreshed kernel configs. Also uwe5622 patches needed for orange pi 3 lts were not being applied as least kernel version was set to 6.0. Moved it back to 5.15. Not sure if it works though will test next week once I receive my orangepi 3 lts. Also for edge kernel, enabled rtw88 based drivers and disabled their corresponding legacy counterparts. How Has This Been Tested? Please describe the tests that you ran to verify your cha…

Description Bumped current kernel to 6.1.33. Also disabled some Rockchip patches thats gets applied on the sunxi kernel. How Has This Been Tested? [X] Compiled an image and booted it on Nanopiduo2 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 kernel versions as follows sunxi & sunxi64: legacy - 5.15.121 -> 5.15.123 edge - 6.4.5 -> 6.4.7 sunxi64 only: current - 6.1.40 -> 6.1.42 The sunxi current kernel is kept back as 6.1.42 is currently not booting on 32-bit allwinner boards. 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 updated sunxi images on NanoPi Duo2 (sun8i H3) [X] Booted updated sunxi64 images on Orange Pi Prime (sun50i H5) Checklist: [ ] My code follows the style guidelines of this project [ ] I have performed a self-review of my own code [ ] I …

Description Legacy - 5.15.134 -> 5.15.135 Current - 6.1.56 -> 6.1.57 Edge - 6.5.6 -> 6.5.7 Config refreshed using rewrite-kernel-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] All patches apply fine, builds fine, and seems to work fine as well. 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 depe…

Description Legacy - 5.15.135 -> 5.15.137 Current - 6.1.57 -> 6.1.60 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] Both 32-bit and 64-bit Kernel builds [X] Booted on Orange Pi Zero, 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 downstrea…

Description Legacy - 5.15.32 -> 5.15.33 Current - 6.1.54 -> 6.1.55 Edge - 6.5.4 -> 6.5.5 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 NanoPi Duo2 (sun8i H3) [X] Booted on Orange Pi Prime (sun50i H5) 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 publish…

Description Bumped Allwinner kernels. legacy - 5.15.137 -> 5.15.139 current - 6.1.62 -> 6.1.63 edge - 6.6.1 -> 6.6.2 Updated ov5640 camera patches to fix patch application failure. Also rebased the config files. 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] Both 32-bit and 64-bit kernel builds fine. [X] Tested 32-bit kernel on NanoPi Duo2(H3). All 3 kernels seems to work fine. [X] Tested ov5640 camera with current and edge kernels. Autofocus didn't worked for me, but its possible that I might have damaged my camera by placing something on it. Hav…

Description Legacy - 5.15.123 -> 5.15.124 Current - 6.1.42 -> 6.1.43 Edge - 6.4.7 -> 6.4.8 Toggled CONFIG_RCU_TRACE in linux-sunxi-current.config to fix booting on 32-bit 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] 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 Maint. How Has This Been Tested? [ ] CI Checklist: [ ] My changes generate no new warnings View the full article

Description Bump U-boot to 2023.01. Backported dts patch from 2023.07-rc4 to fix compilation of bigtreetech-cb1 board. Jira reference number AR-1753 How Has This Been Tested? [X] Built images for all of the Maintained and community supported allwinner boards [X] Booted on Nanopiduo2 and checked that crust continues to work 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 [X] My changes generate no new warnings [ ] Any dependent changes have been merged and published …

Description Bump u-boot version to v2022.10 and refreshed the u-boot-sunxi patches wherever needed. I had to remove the add-zeropi.patch as the support already seemed to be there in upstream u-boot. I was not able to check all the supported functionality of zeropi though as I don't have the board myself How Has This Been Tested? [X] Checked that all patches gets applied successfully [X] Tested by booting on nanopiduo2 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…

Description Bumped the Allwinner kernel and U-boot U-boot - 2023.07-rc6 -> 2023.07 Legacy - 5.15.119 -> 5.15.120 Current - 6.1.37 -> 6.1.38 Edge - 6.4.1 -> 6.4.2 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 NanoPi Duo2 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 cha…

Description Bumped kernel versions Current: 6.1.38 -> 6.1.39 Edge: 6.4.2 -> 6.4.4 Modified thermal-sun8i-Be-loud-when-probe-fails.patch to fix patch application failure Disabled drm-sun4i-Fix-wrong-location-of-clk_prepare_enable.patch to fix patch failure and as its not needed after the upstream change Rest of the disabled patches for 6.4.4 are upstreamed U-boot: 2023.07 -> 2023.07.02. This is very trivial bump. It only removes the -rc6 extra version from the Makefile which was not removed when 2023.07 was released. 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 r…

Description Bumps edge kernel to v6.4. Megous patches are synced from orange-pi-6.4-20230619-0323 tag. Following heuristic was used to disable some of the Megous patches patch was already disabled for previous kernel patch also had a revert patch patch had rockchip, rk3xxx or pinephone-pro in name Following armbian patches were modified a bit to fix patch application failures drv-iio-adc-axp20x_adc-arm64-dts-axp803-hwmon-enable-thermal.patch drv-pmic-add-axp313a.patch drv-rgb-add-ws2812.patch drv-rtc-sun6i-support-RTCs-without-external-LOSCs.patch drv-touchscreen-tsc2007-polling.patch Following armbian patches were modified to fix compilation issues Add-dump_reg-…

Description When crust is enabled on H3 and H5 boards, when booting, the following error is displayed during u-boot spl stage. ns16550_serial serial@1c28000: pinctrl_select_state_full: uclass_get_device_by_phandle_id: err=-19 The error is quite benign and doesn't impact functionality in any way. Still for user experience sake, this PR fixes 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 Nanopiduo2 and verified that error is no longer produced Checklist: [ ] My code follows the style guidelines of this project [X] I have performed a se…

Description Minor kernel bumps Legacy - 5.15.143 -> 5.15.144 Current - 6.1.68 -> 6.1.69 Edge - 6.6.7 -> 6.6.8 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 booting 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 warnings [ ] Any dependent changes have been merged and published in down…

Description Converted configuration for uwe5622 support to extension making it easier to add wifi and bluetooth support to boards with uwe5622 wireless module. Added the uwe5622 extension to Orange Pi Zero2. This should add bluetooth support to the same. Moved Orange Pi 3 LTS specific code out of the family config file Also for H6 based devices, switched to lightdm-gtk-greeter as slick-greeter shows weird artifacts Also added myself as maintainer for Orange Pi 3 and Orange Pi 3 LTS. 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 wifi, bluetooth and …

Description Does following cleanup for series.* files from patch/kernel/archive/sunxi-*/ Disabled Revert-net-Remove-net-ipx.h-and-uapi-linux-ipx.h-header-files.patch as its also applied from patch/misc For 6.2+, series.armbian file also had list of patches from patches.fixes directory. As we have series.fixes file for that, removed the same from series. armbian Some patches were disabled in series.conf file, but were not disabled in the corresponding series.* files. Synced the same so that concatenating series.megous, series.fixes and series.armbian file produces matching series.conf file. These are just cosmetic fixes/cleanup, doesn't change anything on code level or …

Description Bumped u-boot and kernel version for Allwinner. Toggled CONFIG_MEDIA_SUPPORT from y to m in linux-sunxi-current.config similar to edge kernel to resolve the boot issue on 32-bit boards. U-boot 2023.07-rc4 -> 2023.07-rc6 (2023.07 is delayed by a week. Will bump it again once thats released) Kernel Legacy 5.15.113 -> 5.15.119 Kernel Current 6.1.34 -> 6.1.37 Kernel Edge 6.4.0 -> 6.4.1 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 NanoPi Duo2 Checklist: [ ] My code follows the style guidelines of this project [ ] I have perf…

Description Bump crust to v0.6. Doesn't change anything for us other than version shown on serial console and dmesg log as the commits that went in from what we were using only includes 2 defconfig changes and some changes in readme file. 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 crust builds and works as expected on Nanopiduo2 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 correspond…

This will enable the latest Armbian images to boot on aml-s905x3 boxes after the move from uImage to Image. The blob is built on mainline u-boot's tag v2023.10. Changes to be committed: modified: packages/bsp/aml-s9xx-box/boot/build-u-boot/readme.txt new file: packages/bsp/aml-s9xx-box/boot/build-u-boot/u-boot-s905x3.patch new file: packages/bsp/aml-s9xx-box/boot/u-boot-s905x3 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. More information can be found here: #4938 How Has This Been Tested? Please describe the tests that you…

aml-s9xx-box: bsp-cli hashing fixes aml-s9xx-box: inline bsp-cli preinst function so it's hashed together with the hook; half fixes #6817 this is technically cheating, but works add TODO's ref the manual include'ing of files that are not hashed in the bsp-cli aml-s9xx-box: move files included in bsp-cli from packages/bsp/aml-s9xx-box to config/optional/boards/aml-s9xx-box/_packages/bsp-cli; fixes #6817 with this: those files are automatically hashed by the bsp-cli hashing mechanism no need to copy them manually any more View the full article

aml-s9xx-box: Move board specific bsp file handling to the board config file from from the family config file Changes to be committed: modified: config/boards/aml-s9xx-box.tvb modified: config/sources/families/meson-gxl.conf [x] Built and verified files in aml-s9xx-box build View the full article

Changes to be committed: modified: config/boards/aml-s9xx-box.tvb modified: packages/bsp/aml-s9xx-box/boot/extlinux/extlinux.conf.template The aml-s9xx-box builds use the native TV Box u-boot. I've had as a todo item to figure out how to not build and include an unused u-boot. In a recent PR for a different board the opposite was being done (adding a u-boot where a board didn't previously ship one), thus I then had the info to remove it here. This also changes the generated extlinux.conf to include a fdt line by adding the boot_fdt_file to the board config file. This reduces the effort needed to manually modify the extlinux.conf. How Has This Been Tested? [x] Bui…

Previously, the u-boot binary files used to chainload u-boot for the amlogic tv boxes were the ones produced by balbes150 in his old tv box builds. There was no source code for them. This commit is the first to convert from those old binary files to newly built ones along with a u-boot patch file and instructions on how to build/rebuild them. Eventually this needs to be incorporated into the build framework to automate it. But for now one step at a time. Changes to be committed: new file: packages/bsp/aml-s9xx-box/boot/build-u-boot/readme.txt new file: packages/bsp/aml-s9xx-box/boot/build-u-boot/u-boot-s905x-s912.patch deleted: packages/bsp/aml-s9xx-box/boot/u-…

This fixes an incompatibility introduced with new Armbian framework's change from uImage to Image Changes to be committed: modified: packages/bsp/aml-s9xx-box/boot/build-u-boot/readme.txt new file: packages/bsp/aml-s9xx-box/boot/build-u-boot/u-boot-s905x2-s922.patch modified: packages/bsp/aml-s9xx-box/boot/u-boot-s905x2-s922 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. 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. …

Description Improve naming confusion by changing build framework defaults. 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 Input method such as fcitx5 requires applications running under gtk or qt. We have another choice libreoffice-qt5, but I think preinstalled libreoffice-gtk3 should be okay. 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 Follow up on #3943, this hack appears to fix Zero's eMMC boot issue when paired with Kingston eMMC module. How Has This Been Tested? This hack has been tested with upstream U-Boot 2022.04 and was confirmed working. View the full article

Description Currently there is an error when generating desktop rootfs: FileNotFoundError: [Errno 2] No such file or directory: '/var/lib/apt/lists' If index is not generated, package search is super slow. Jira reference number AR-1684 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 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-1301 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 by end users in nightly builds [x] Tested myself in local 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 change…

Description This fixes a wrong error message from nand-sata-install when filesystem tools are missing. Prior to this change, the script doesn't notice that the tools are missing and tries to actually check the target FS size. Since that size is a blank string (because the target FS was never created), it gives a wrong error message saying that the FS is too small. Jira reference number AR-1398 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. [ ] Tested on a nightly build with Orange PI 3 LTS Checklist: [ ] My code follows the style guidelines of this project …

Description This PR contains update to make creation of armbian i3-wm images possible for the following distributions listed by their code names. jammy focal bookworm bullseye Jira reference number AR-1708 How Has This Been Tested? So far I have made sure that the images can be built and that they are bootable and functional. Testing was done on real hardware, bare metal. [X] Test A - able to create the image in the first place without errors present [X] Test B - check if bootable and can be used like a regular i3-wm setup Checklist: Not sure what to mark exactly, so leaving most of these blank for now [] My code follows the style guidelines of this project [X] I…

Description Fixed PR from wrong DB Jira reference number AR-1712 View the full article

Description Add cpu-frequency to orangepizero2, allwinner h616 6.x.y kernels Follow up Jira reference number AR-1683 How Has This Been Tested? Armbian 23.05.0-trunk Bullseye ttyS0 orangepizero2 login: alistair Password: ___ ____ _ _____ ____ / _ \| _ \(_) |__ /___ _ __ ___|___ \ | | | | |_) | | / // _ \ '__/ _ \ __) | | |_| | __/| | / /| __/ | | (_) / __/ \___/|_| |_| /____\___|_| \___/_____| Welcome to Armbian 23.05.0-trunk Bullseye with bleeding edge Linux 6.2.16-sunxi64 No end-user support: built from trunk System load: 13% Up time: 0 min Memory usage: 8% of 984M IP: 10.0.0.12 CPU temp: 42°…

Description Add cpu-frequency to orangepizero2, allwinner h616. From sunxi 5.16 the drivers and dtsi, dts files have the necessary support. Add: sun50i-h616-cpu-opp.dtsi Additions: sun50i-h616-orangepi-zero2.dts +#include "sun50i-h616-cpu-opp.dtsi" +&cpu0 { + cpu-supply = <&reg_dcdca>; +}; How Has This Been Tested? Test A: BUILD compiled and booted Test B: BOARD @orangepizero2:~$ uname -a Linux orangepizero2 5.19.6-sunxi64 #trunk SMP Mon Sep 5 23:16:49 UTC 2022 aarch64 GNU/Linux @orangepizero2:~$ find /sys -name cpufreq /sys/devices/system/cpu/cpu3/cpufreq /sys/devices/system/cpu/cpu1/cpufreq /sys/devices/system/cpu/cpufreq /sys/devices/system/c…

Add uart_A to the meson-sm1-bananapi-m2-pro DTS. 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 ROCK Pi E 1000M port is not working due to following error: rk_gmac-dwmac ff540000.ethernet end0: __stmmac_open: Cannot attach to PHY (error: -19) Documentation summary for feature / change this patch fixes above error and make 1000M port usable. How Has This Been Tested? [x] connect 1000M port and see dmesg [x] connect 1000M port and see ip 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 [x] My changes generate no new warnings [ ] Any dependent changes have been merged and published in downstream modules View th…

Description There are several small problems / corner cases that needs to be addressed. Any help is appriciated. 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 new warnings [ ] Any dependent changes have been merged and published in downstream modules View the full ar…

Description An attempt to set default Wallpaper on KDE Neon Jira reference number AR-2002 How Has This Been Tested? [ ] Build image Desktop show in selection, but does not apply. 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 In commit 0aa61abe7 (armbian-audio-config: Massively speed up script) this script was changed to not call amixer for each control, but just once for each card, feeding commands for many controls in one invocation with the --stdin option. In that commit, two errors were introduced: Controls that were intended to be muted were turned on instead. This affects the "CD", "Mic" and "Internal Speaker" controls. This occured because there is a helper shell function whose arguments were renumbered, but the last argument kept the old numbering, keeping it always at the default value of "on", even when it should have been "mute". Controls with a space in their na…

Description This script calls amixer to set various mixer volumes, by simply trying a bunch of mixer names for each sound card in the system. In practice, this meant the amixer command was called 158 times for each sound card. The overhead of all these forks and probably also amixer startup added together to produce a noticable slowdown in startup. For example on an Orange Pi PC, the script took about 6 seconds per soundcard. This was on a system with a few extra USB soundcards (6 alsa cards in total): $ time bash ./armbian-audio-config.original real 0m35.662s user 0m20.145s sys 0m15.145s This commit modifies the script to spawn amixer only once per alsa …

Description armbian-bsp-cli: fix 10-wifi-disable-powermanagement.rules corrected "iw" path made rule better targeted at wifi devices switched from %k (kernel) to $name variable to better integrate with user-provided rules How Has This Been Tested? [x] Tested new rule with actual wifi devices --> udeavdm test /sys/class/net/wlan0 output: Queued commands: RUN{program} : /usr/sbin/iw dev wlan0 set power_save off Checklist: [x] My code follows the style guidelines of this project [x] I have commented my code, particularly in hard-to-understand areas [x] My changes generate no new warnings View the full article

armbian-desktop: remove "Conflicts: gdm3"; some sddm support rootfs-desktop: disable sddm as well as lightdm and gdm3 in desktop_postinstall() lightdm, gdm3 already had this armbian-firstlogin: shellfmt, no changes armbian-firstlogin: better dm detection + add simple no-op sddm support armbian-desktop: remove "Conflicts: gdm3" if you installed gdm3 (even if you don't use it), you lose Armbian wallpapers View the full article

Description Many network cards (wired and wireless) now require specific firmware to work, these are usually included in linux-firmware. The idea of this commit is to include some common firmware in armbian-firmware to solve driver loading problems. After that we can remove the same firmware files on armbian-firmware. Note: Didn't copy the brcm part from linux-firmware because I don't have the relevant hardware to test. 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] rtl8153 (NanoPi R1S H5) [x] mt7921 (Radxa ROCK3A) Checklist: [x] My code follows the style…

Modify both weak password warning messages to be consistent Formatted as follows: "Warning: Weak password, !". Jira reference number AR-1385 Tested on a board (Orange Pi Zero Plus) Create root password: ****** Repeat root password: ****** Warning: Weak password, it does not contain enough DIFFERENT characters! Create user (testuser) password: ****** Repeat user (testuser) password: ****** Warning: Weak password, it does not contain enough DIFFERENT characters! 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 cor…

Call the 'passwd' command with the right arguments depending on whether the user entered a password or not. View the full article

Description I noticed that I was not seeing many locales that were supposed to be shown during first login like en_IN for English India. I was only getting the following 3 options when choosing to get locales based on my location At your location, more locales are possible: 1) bhb_IN.UTF-8 2) tcy_IN.UTF-8 3) Skip generating locales Please enter your choice: This is because we were looking for .UTF-8 suffix in the locale names. But not all UTF-8 locales have that suffix. All UTF-8 locales do end with UTF-8 at the end. So now we are using the same. With the fix, I am now getting much better result. Here is the list after the fix for comparison At your location, more lo…

Fix all shellcheck issues, as well as some formatting/indentation. Tested by building and booting a Radxa Zero image with this included. View the full article

Description #5007 Support unmbers in username. But don't make sure that the first charactor of username isn't number. So let's fix it. How Has This Been Tested? [ ] Manual grep 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

Make the two Y/n questions that firstlogin asks behave consistently with each other, and more in line with user expectation: Reject anything that is not Y, y, N, n or . Previously the "Connect via wireless? [Y/n]" question would interpret Y, y and as "yes", and everything else as "no", whereas the "Set user language based on your location? [Y/n]" question would loop until the user selected Y, y, N or n. Make pressing enter equivalent to the default "Y", since that is the capitalized option. Echo back what the user typed. View the full article

Commit c90986492252a85db3357362594e5c40b80fbf95 removed a prompt asking the user if they want to change display settings, but didn't remove the checks that later used the answer. Since it's been like this for 2 years now apparently without issue, remove the checks and the shellcheck workaround. View the full article

ifconfig is no longer included in a default install of Armbian Bookworm, causing armbian-firstrun-config to silently fail when ifconfig -a is used to get the list of network adapters. Replaced with nmcli device. 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 pro…

Description Context systemd's cloud-init.target and armbian-firstrun.service will be started concurrently (both are wanted by multi-user.target). Both will try to create SSH host keys by default: armbian-firstrun will always delete SSH host keys and then generate new ones cloud-init.target (by default) will always delete SSH host keys and then generate new ones. Problem When one must run armbian-firstrun and cloud-init, there is no deterministic ordering between the 2 files execution and therefore no one can guarantee which will be last to setup OpenSSH host keys. In my current scenario, host keys are explicitly setup in cloud-init and I would expect armbian-firstrun…

Description armbian-installer have troubles if we are installing OS to SSD with previously defined partitions. Adding a recommended option to start with a clean drive - wiping everything - is one way. In this case, our installer starts in predicted way. Also it gives user no option to choose wrong (too small) partition, if there are more of them pre-made. Jira reference number AR-2393 https://forum.armbian.com/topic/41699-how-to-debugfix-armbian-config-for-kernel-update/#comment-195551 How Has This Been Tested? [x] Made several installs to nvme with several or no partitions Checklist: [x] My changes generate no new warnings [x] Any dependent changes have been merged …