SBC News

Description packages.debian.org has been down a lot lately, so builds could not finish since the build system wants to find out the package name and version for base-files. Use Packages.gz from the mirrors as an alternative method to search for this information. How Has This Been Tested? [x] Building works as normal even if packages.debian.org is down 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

When running in Docker, do not install basic utilities on the host. Do not install them in the container either, as they're already part of the image we're building for Docker runs. Description I also moved the whole if block in compile.sh down to a place where $1 is guaranteed to have attained its final value (e.g. if compile.sh dockerpurge was called). How Has This Been Tested? Please describe the tests that you ran to verify your changes. Please also note any relevant details for your test configuration. [x] ran compile.sh docker and verified it installs nothing on the host Checklist: [x] My code follows the style guidelines of this project [x] I have performed a…

Description Fix boot from btrfs fs in uboot 2024.01/2024.04 How Has This Been Tested? [x] Compile image and boot from (zstd-compressed) btrfs sole rootfs/bootfs partition Checklist: [x] My code follows the style guidelines of this project [x] I have performed a self-review of my own code View the full article

Description Currently there is no HDMI output on edge 6.5 kernel on rk3228/rk3328. Forum discussion https://forum.armbian.com/topic/26978-csc-armbian-for-rk3318rk3328-tv-box-boards/?do=findComment&comment=171661 This PR will restore 'less than or equal' match of clocks that was lost in patch transition from 6.3 to 6.4: https://github.com/armbian/build/blob/6d981baba68699b0c6ada476704556e11dd661bc/patch/kernel/archive/rockchip64-6.3/rk356x-vop2-support.patch#L333 https://github.com/armbian/build/blob/6d981baba68699b0c6ada476704556e11dd661bc/patch/kernel/archive/rockchip64-6.4/rk356x-vop2-support.patch#L333 How Has This Been Tested? [x] rk3328-box + FullHD HDMI displ…

Description Fix regression caused by my previous PR #6248 that broke compilation for clearfog uboot. This PR refactors the patching logic to a separate function thereby making it easy to use outside uboot.sh. During the process I also noticed that uboot_prepatch_version variable being initialized as part of that logic was not really being used anywhere. Hence removed the same. How Has This Been Tested? Please describe the tests that you ran to verify your changes. Please also note any relevant details for your test configuration. [X] Test build for meson-s4t7 [X] Test build for clearfog Checklist: [ ] My code follows the style guidelines of this project [ ] I have p…

Description Auto resize rootfs don't work if build image with: ROOTFS_TYPE=btrfs ROOTFS_TYPE=xfs 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 image, flash, check rootfs resized Checklist: Please delete options that are not relevant. [x] My code follows the style guidelines of this project [x] I have performed a self-review of my own code [x] I have commented my code, particularly in hard-to-understand areas [x] My changes generate no new warnings [x] Any dependent changes have been merged and published in downstream modules View the full article

Description When compiling using vagrant as build environment, the first option following vagrant is skipped. ./compile.sh vagrant foo bar In this example foo is skipped. This PR fix that bug. 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] An image was successfully built using vagrant as builder. 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 …

No descriptionView the full article

Fixes the build of DEB packages after changing files in the shared GIT. Switching the LEGACY kernel from RK BSP 4.4 to RK BSP 5.10. View the full article

build work for kernel 6.0 View the full article

No descriptionView the full article

Description On my samsung TV, Rock 5b disconnects the CEC communication after TV restart. This patch fixes that. 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 ] Rock 5b using Samsung TV Checklist: [ x] My code follows the style guidelines of this project [ x] I have performed a self-review of my own code [ ] I have commented my code, particularly in hard-to-understand areas [x ] I have made corresponding changes to the documentation [x ] My changes generate no new warnings [x ] Any dependent changes have been merged and pub…

Description This PR includes a patch that fixes: HDMI sound. X11 cursor flickering (https://github.com/radxa/kernel/pull/50) Missing resolutions (https://github.com/orangepi-xunlong/linux-orangepi/commit/6947bce36393fc034389ab1eef6f18a5ea64f17d) HDMI-CEC feature (https://github.com/radxa/kernel/commit/d35989ed644b9d67de09849779e5147f4332df55) How Has This Been Tested? [x] I compiled kernel and tested sound, flickering. [x] Confirmed adding missing resolutions -> https://forum.armbian.com/topic/25600-wip-current-issues/#comment-156823 [x] HDMI-CEC is confirmed by @catalinii. Orange Pi has CEC but i'm not able to test it. Checklist: [x] My code follows the style gu…

Description fix GPIO patch disable pci updates due to many changes. probably we don't need this anymore @Heisath Jira reference number AR-1577 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 [x] I have made corresponding changes to the documentation [ ] My changes generate no new warnings [x] Any dependent changes have been merged and published in downstream modules View the full article

fix create efi parted for arm View the full article

Description As reported here, the cryptroot functionality was broken on boards that were using flash-kernel. Also because the dropbear config directory and filename is changed in newer dropbear versions, the ssh unlock functionality was broken on bullseye+. This PR fixes the same Jira reference number AR-1799 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 creating image for RPI4B with cryptroot and ssh unlock enabled. Unlocked cryptroot using ssh key Checklist: [X] My code follows the style guidelines of this project [X] I have performed a self-…

Description Fix Raspberry Pi 5 DSI functionality. Context: A display connected to the DSI connector of Raspberry Pi 5 does not work. Dmesg reveals the following information: [ 13.283052] mipi-dsi 1f00118000.dsi.0: deferred probe pending: mipi-dsi: supplier 2.reg_bridge not ready [ 13.283060] platform 1.panel_disp: deferred probe pending: platform: wait for supplier /axi/pcie@120000/rp1/i2c@88000/reg_display@45 The problem could be traced back to a missing I2C Driver. See: https://forum.armbian.com/topic/50963-dsi-display-does-not-work-on-raspberry-pi-5/ Documentation summary for feature / change Add module to kernel configuration: CONFIG_I2C_DESIGNWARE_CORE How …

Description ddbr was failing on a recent jammy build. The issue is that lsblk output has changed sometime since this script was written. The logic to parse out the $runfrom drive was returning duplicate info, so instead of 'mmcblk0' the value was 'mmcblk0 mmcblk0' Having this duplicate value was causing an error further down the script. Fix is to add ' | sort | uniq' this was already being done on the other lsblk outputs, just not this one. I've run into this before, and I guess at that time, I forgot to submit a PR for the fix, or it was for a different script that had the same issue. Changes to be committed: modified: packages/bsp/common/usr/sbin/ddbr Jira refere…

Description Setting the display mode in armbianEnv.txt no longer worked, probably because it used an old, sunxi-specific interface. See the commit message (also shown below) for details about this. I'm marking this as draft, because: I'm not sure if we should reuse the disp_mode variable, or maybe use a different name (video_mode?) to make it clearer that the values it accepts are of a slightly different format (would also help to see that older documentation does not apply to this option). This fixes just sunxi, which I've been able to test only on a single board (Orange Pi PC). I'm not sure if similar changes are needed elsewhere (see last point in commit message). …

Description https://github.com/armbian/build/pull/4917#issuecomment-1513450111 @prahal 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 The 32-bit Allwinner dtb files are under /boot/dtb and not under /boot/dtb/allwinner as expected by u-boot because of the current board config. Fixed dtb location by removing the allwinner/ prefix for nanopi-r1 and nanopi duo2 boards. This issue seems to have already reported on the forums as well - https://forum.armbian.com/topic/28117-nanopi-duo-2-hang-on-boot/ How Has This Been Tested? Tested by creating edge image with the changes included in the pull request. The stable image still doesn't boot because of the ongoing issue with the 6.1.30 kernel image, but 6.2.16 kernel from edge image works [x] Created edge image and booted on nanopi duo2 Checklist:…

description of the problem https://forum.armbian.com/topic/15964-firfly-rk3399-have-not-been-booting-up-reasent-images-from-armbian/?do=findComment&comment=152547 View the full article

Description Previously we had armbian-bsp-cli- package i.e. package name didn't contained branch. When upgrading from such releases, installing armbian-bsp-cli-- package throws error. This PR fixes the same. Jira reference number AR-1795 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] Upgraded on nanopiduo2 from version 21.08 and made sure the updated armbian-bsp-cli package installs 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-und…

Description This PR fixes EXTRAWIFI=no compilation when uwe5622 driver and rockchip64 family is involved. The error was due to the fact that uwe5622 driver has been moved in misc patch directory some time ago, but a custom patch was left into family kernel patches to adapt the driver to rockchip64 platform. EXTRAWIFI=no would not patch the kernel to include the driver, but the custom patch was still applied since it was present as kernel patch and that would cause a failure. With this PR, the custom rockchip patch has been moved into misc directory as well and it is applied selectively in code, so EXTRAWIFI=no works correctly. Also uwe5622 related patches are moved into…

Description Attempt to fix build job failure - https://github.com/armbian/os/actions/runs/7675198892/job/20921297126 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 vim4 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…

https://forum.armbian.com/topic/24554-armbian-install-fails-due-to-bad-lsblk-argument/#comment-153675 Untested View the full article

Description Moved patch from uboot 35xx to uboot 3588 In order to patch. At before, the patch has not been patched. How Has This Been Tested? [x] ./compile.sh build ARTIFACT_IGNORE_CACHE=yes BOARD=firefly-itx-3588j BRANCH=vendor BUILD_DESKTOP=yes BUILD_MINIMAL=no DESKTOP_ENVIRONMENT=gnome DESKTOP_ENVIRONMENT_CONFIG_NAME=config_base KERNEL_CONFIGURE=no RELEASE=bookworm [x] observed successful patch to uboot w/o error [x] u-boot said Starting Kernel ... 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 …

Should fix #4146 message cp: missing destination file operand after '.' when building image for rockchip with ATF. View the full article

Description This pull requests adds a device tree overlay for the Odroid C4 enabling hardware SPI on pins 19, 21, 23 and 24 on the GPIO header. It doesn't require any other changes, except one additional line in the Makefile. Besides, it can replace the old device tree meson-sm1-odroid-c4-spidev.dtb (which activates wrong pins and doesn't work due to this) while offering more flexibility. How Has This Been Tested? The SPI communication has been successfully tested with a LogicPort analyzer and some custom made FPGA board (SPI readout of a Mamamatsu silicon spectrometer). [x] Logic Analyzer: timing of MOSI vs. SCK has been verified, maximum speed is about 12MHz for SCK …

Description After some experimenting I found a way to flush the journal and maintain logs in tmpfs using /run/log/journal, and only have a softlink from /var/log/journal to /var/log.hdd/journal. Additionally the cached journals are to be cleaned up when /var/log becomes too full. Some logic was needed in cases where the user decides to do Storage=volatile journal logging in /etc/systemd/journald.conf, or when the user or journald with Storage=persistent creates a /var/log/journal folder which will be moved to /var/log.hdd/journal and replaced by the softlink. I didn't find any documentation, so wasn't able to update it. Jira reference number [AR-9999] How Has This Bee…

Description Force netplan to use DHCP only on interface e* and not also on the docker interface Jira reference number AR-2430 How Has This Been Tested? [x] Test by user on forum 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 issue When using ./compile.sh rewrite-kernel-config and then running the menuconfig with ./compile.sh kernel-config, just exiting and saving without any manual changes, the kernel config may still change. This is because rewrite-kernel-config does force some kernel options without any additional checks e.g. for dependencies. Using the config menu with kernel-config does those checks automatically and solves all dependencies. Example: Using ./compile.sh kernel-config on linux-rockchip64-edge.config (e.g. with BOARD=nanopi-r5c), the option CONFIG_DEBUG_KERNEL=y is automatically selected, since it is a dependency for CONFIG_EXPERT=y, which is selected in thi…

Description mipi_dsi_driver adjust function remove return void on linux6.1 (this patch also add new: orientation custom, reset level custom) nanopct4 rt5651 sound repeat pinctrl cause problem [ 7.395164] rockchip-pinctrl pinctrl: pin gpio4-0 already requested by ff880000.i2s; cannot claim for 1-001a [ 7.395192] rockchip-pinctrl pinctrl: could not request pin 128 (gpio4-0) from group i2s-8ch-mclk on device rockchip-pinctrl How Has This Been Tested? [x] product panel_simple_dsi.ko on linux6.1 [x] nanopct4 rt5651 sound normal on linux6.1 Checklist: [x] My code follows the style guidelines of this project [x] I have performed a self-review of my own code […

Description mipi_dsi_driver adjust function remove return void on linux6.1 (this patch also add new: orientation custom, reset level custom) How Has This Been Tested? [x] product panel_simple_dsi.ko on linux6.1 and drive my dsi lcd normal 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 [x] Any dependent changes have been merged and published in downstream modules View the full article

Description ghproxy url is something like https://ghproxy.com/https://gtihub.com/armbian/build, which contains https://gtihub.com. Without this patch git will fetch from https://ghproxy.com/https://ghproxy.com/https://gtihub.com/armbian/build. Just skip modifying the url when ghproxy is set. 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 with GITHUB_MIRROR=ghproxy. 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…

Description The command added to check whether the directory is git or not was having syntax error. Fixed the same. Also it seems adding safe-directory with local doesn't really work which actually makes sense. hence reverting to using global instead. Its still safer than before as we are not adding * and are adding the actual path of the directory Fixes following error in the logs --> (9) COMMAND: git --no-pager -C /home/flash/build-fork/cache/git-bare/kernel -C rev-parse --git-dir -->--> command failed with error code 128 after 0 seconds --> (9) WARNING: stacktrace for failed command [ exit code 128:git --no-pager -C /home/flash/build-fork/cache/git-bar…

Description We have an arg UBOOT_MIRROR and it can be set to gitee to use mirror https://gitee.com/mirrors/u-boot.git. We have to fix Makefile url for it. 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] PREFER_DOCKER=no ./compile.sh uboot BOARD=fl700n BRANCH=edge UBOOT_MIRROR=gitee. fl700n is a board using uboot config firefly-rk3288_defconfig I am playing these days. 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 [ ]…

Description https://github.com/badges/shields/issues/8671 Jira reference number AR-1437 View the full article

Description I change both edge and current. vdd-log supply is pwm-supply, not vin-supply. Fixes vdd-log supply ending up the dummy regulator. [ 1.783479] pwm-regulator vdd-log: Looking up pwm-supply from device tree [ 1.783505] pwm-regulator vdd-log: Looking up pwm-supply property in node /vdd-log failed [ 1.783556] vdd_log: supplied by regulator-dummy Per https://lore.kernel.org/all/20211227234529.1970281-2-heiko@sntech.de/ there will be no functional change as the supplying regulator is an always-on fixed-regulator. 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 co…

Description It was impossible to set IMAGE_TYPE from command-line, thus it was not possible to generate user-built images. The change re-sets IMAGE_TYPE based on the BETA variable only if IMAGE_TYPE hasn't been set previously How Has This Been Tested? Run tests with IMAGE_TYPE set and unset and saw it was set/not-set to the corresponding value 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 …

No descriptionView the full article

No descriptionView the full article

Description Closing https://github.com/armbian/build/issues/4567 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-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 fix issue #6531 by disabling "command-not-found" apt hook during build-time (which takes ages under qemu) and re-enabling after succesfully creating rootfs No impact for end user as command-not-found will create/update its internal db natively on SBC transparently during first sudo apt update Jira reference number [AR-2128](https://armbian.atlassian.net/browse/AR-2128) How Has This Been Tested? [x] Build vanilla trixie for opi03 [x] Build vanilla trixie for opi5-plus Checklist: [x] My code follows the style guidelines of this project [x] I have performed a self-review of my own code View the full article

Description Minor regression fix for extensions that need to modify the root device, such as LVM and Crypto Root. Fix for newer ubuntu build host requiring re-instantiation of LVM devices mid build process. GitHub issue reference: #7210 Jira reference number AR-2489 How Has This Been Tested? The build process failed before, now builds again. Tested with Jammy and Noble, installed distributions, etc. View the full article

Description We need to pre-install the necessary dependencies if the INSTALL_HEADERS=yes key has been selected. We have to pass the architecture value to the "make" command in the kernel header compilation script. Issues reference number #4589 How Has This Been Tested? This is how the log looks with the debug code enabled: For sunxi64: Unpacking linux-headers-current-sunxi64 (23.02.0-trunk) ... Setting up flex (2.6.4-8build2) ... Setting up libssl-dev:arm64 (3.0.2-0ubuntu1.7) ... Setting up bison (2:3.8.2+dfsg-1build1) ... update-alternatives: using /usr/bin/bison.yacc to provide /usr/bin/yacc (yacc) in auto mode Setting up linux-headers-current-sunxi64 (23.02.0-trunk)…

fixes Jetson-nano legacy and installation on emmc in btrfs mode View the full article

Description Fixes compilation for meson-s4t7. Had to enable DEBUG_KERNEL to fix Khadas vendor common_drivers. Apparently they won't compile without DEBUG stuff. Beware: This is the only SOC with DEBUG_KERNEL enabled now. See discussion here: https://github.com/armbian/build/commit/01be9ecbf9773dde94e089a852c3037e0daf0a9f How Has This Been Tested? [x] ./compile.sh kernel BOARD=khadas-vim1s BRANCH=legacy 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

No descriptionView the full article

Description Fix build errors on Khadas Edge 2 vendor uboot. GitHub issue reference: https://github.com/armbian/build/issues/6862 Jira reference number AR-2402 How Has This Been Tested? [x] Now it builds with DOCKER_ARMBIAN_BASE_IMAGE="ubuntu:noble" argument. Checklist: Please delete options that are not relevant. [ ] 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 Adjusting broken links How Has This Been Tested? [x] Clicking on links 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

Fix logging for relocated output. Better (more compact) logging. Allow WSL for NO_HOST_RELEASE_CHECK. Fix sudo (pass env, ie. CONFIG=). View the full article

Description Currently, if losetup -f has to create a new device node and is run in a docker container, the device will be created on host butt will not be available to the already running container. This PR mitigates that by running losetup -f in a container in case there are no loop devices (/dev/loop0 is checked). The container exits after executing losetup and the main build container is run after. The MKNOD capability does not affect the issue, so it was removed. For additional context, previous attempts at fixing: #6576 #6642 #6927 #6936 GitHub issue reference: #6568 Jira reference number AR-2132 How Has This Been Tested? Fresh boot on a system that doesn't have…

Description adjust broken patches on CURRENT disable packaging patch on legacy Jira reference number AR-1780 How Has This Been Tested? [x] Build test 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 This is to fix wrong DRAM size detection in Orange Pi Zero 3 board with 1.5GB DRAM. Currently they are not able to boot as they detect 2GB DRAM, so after applying this patch they will boot normally. Other boards with 1GB/2GB/4GB DRAM will continue working the same way with this patch. This patch would only be applied to u-boot v2024.01 release. I will provide other patch for u-boot v2024.04 and newer. How Has This Been Tested? [X] Build image for Orange Pi Zero 3 board, flash devices with 1/1.5/2/4GB DRAM and power on with serial cable: logs will show the right memory size [X] Build image for Orange Pi Zero 3 board, flash devices with 1/1.5/2/4GB DRAM and p…

Description Fix mic for rt5651 asound.state, the origin state don't open mic route . I did test use Nanopct4, same should fixed use rt5651 codecs's board How Has This Been Tested? [x] I heared sound from Nanopct4 onboard mic record wav file 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 [x] Any dependent changes have been merged and published in downstream modules View the full article

Description Noticed typo using ./install-aml.sh on aml-s9xx-box with community image View the full article

This selection did get disabled by the BUILD_ONLY option implementation This fix will re-enable the KERNEL_ONLY selection for intermediate backward compatibility Description @The-going This PR is due to a comment from @igorpecovnik on #4455, asking, if it was inteded to switch off the interactive KERNEL_ONLY selection. I guess for now we should keep this interactive feature in for backward compatibility. This PR would fix it. This is a followup to fix this introduced by #4455 Test [x] Interactive call of ./compile.sh - the interactive KERNEL_ONLY selection dialog appears again and KERNEL_ONLY=yes is propagated to BUILD_ONLY as expected Checklist: [x] My code follows…

Description Little fixes to uwe5622 missing headers. This will make the driver compile on kernel 6.8 How Has This Been Tested? [x] Module compiles on edge kernel 6.8 [x] Module compiles on current kernel 6.6 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 Maint. Jira reference number AR-1341 How Has This Been Tested? [x] Build image 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

No descriptionView the full article

Description This fixes the recently broken patch. See #4261 and https://forum.armbian.com/topic/23824-fancontrol-service-fails-to-start-with-kernel-version-51572/ Needs to be tested on actual hardware! How Has This Been Tested? build runs 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 nanopct4 rt5651 sound repeat pinctrl cause problem [ 7.395164] rockchip-pinctrl pinctrl: pin gpio4-0 already requested by ff880000.i2s; cannot claim for 1-001a [ 7.395192] rockchip-pinctrl pinctrl: could not request pin 128 (gpio4-0) from group i2s-8ch-mclk on device rockchip-pinctrl wlan-platdata,bluetooth-platdata is from legacy kernel, it not in mainline kernel (wireless,bluetooth drive by sdio,bluethooth node in dts), now remove it from dts general-add-panel-simple-dsi.patch is a general patch drive DSI lcd display pannel by dts easy, now add this to media edge for some people's need By the way, [board-pbp-fix-wonky-wifi-bt.patch] this p…

Description Maint & not supported target. Jira reference number AR-1334 How Has This Been Tested? [x] Build and boot Checklist: [x] My code follows the style guidelines of this project [x] I have performed a self-review of my own code [x] I have commented my code, particularly in hard-to-understand areas [ ] 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 PR address the following issue while build as NFS: [ .... ] Copying files to [ /boot ] sent 18.23M bytes received 4.74K bytes 36.46M bytes/sec total size is 18.21M speedup is 1.00 find: ‘/root/armbian-onecloud/.tmp/mount-ea6d8ff5-ed2a-4888-8361-6ae990318e95/lib/modules/’: No such file or directory [ error ] ERROR in function update_initramfs [ main.sh:588 -> main.sh:549 -> debootstrap.sh:98 -> debootstrap.sh:863 -> debootstrap.sh:789 -> general.sh:0 ] [ error ] No kernel installed for the version [ 5.17.11 ] [ o.k. ] Process terminated [ error ] unmount_on_exit() called! [ main.sh:1 -> image-helpers.sh:0 ] [ o.k. ] Unmounting [ /ro…

Description I wrote the wrong path and it has now been fixed Jira reference number [AR-9999] How Has This Been Tested? Please describe the tests that you ran to verify your changes. Please also note any relevant details for your test configuration. [x] Gamepad Checklist: [x] My code follows the style guidelines of this project [x] I have performed a self-review of my own code [x] I have commented my code, particularly in hard-to-understand areas [x] I have made corresponding changes to the documentation [x] My changes generate no new warnings [x] Any dependent changes have been merged and published in downstream modules View the full article

Description This patch fixes the high interrupt issue on the Orange Pi5 Plus. Forum discussion available here. https://forum.armbian.com/topic/33360-orangepi-5-plus-rtc-hym8563-irq-issue/ The patch also adds poweroff support. Right now the Orange Pi 5 Plus just reboots when poweroff or shutdown -h now is executed. Third fix of the patch is to correct gpio_pwrctrl1 typo. 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 command ./compile.sh BOARD=orangepi5-plus BRANCH=edge RELEASE=trixie KERNEL_CONFIGURE=no BUILD_MINIMAL=yes BUILD_DESKTOP=no COMPRESS_OUT…

Description fix building issue -> https://github.com/armbian/os/actions/runs/5387359457/jobs/9778662435 Jira reference number [AR-9999] How Has This Been Tested? [x] Built and tested SPI images 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 This change includes kernel patches to provide the following overlays when using armbian-config on the Orange Pi Zero 2 and Orange Pi Zero 3 boards. I2C IR USB OTG SPI UART These boards share very similar SOCs (RH616 / RH618), and the existing configuration that was also shared with the bigtreetech board did not function correctly for the Orange Pi Zero 2/3 boards, so the Zero 2/3 board overlay configuration was split out into its own files, and the board configurations updated to reference the new overlays. Note: The patches for these overlays have been added to the 6.1, 6.6 (current), and 6.7 (edge) patch directories but it appears the 6.1 code may not b…

Changes to be committed: deleted: patch/kernel/archive/meson64-6.1/board-bananapim5-002-switch-VDDIO_C-pin-to-OP.patch - Patch upstreamed in 6.1.16: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/arch/arm64/boot/dts/amlogic/meson-sm1-bananapi-m5.dts?h=v6.1.20&id=58dccc65221c6465a35cb6bb2ff41f2b75b367f0 modified: patch/kernel/archive/meson64-6.1/board-bananapim5-003-convert-dts-to-dtsi.patcha - Fixed patch due to upstream change in 6.1.16: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/arch/arm64/boot/dts/amlogic/meson-sm1-bananapi-m5.dts?h=v6.1.20&id=e35feeb3fdbe3eeffae5e75123fa44523b5076b8 deleted: patch/k…

No descriptionView the full article

Description Currently, PocketBeagle 2 edge images cannot build (without patch 1) and fails to boot (without patch 3). The patch one just defines the missing variable for OPTEE. Patch 3 specifies root using path instead of UUID. For some reason, UUID does not work with PocketBeagle 2 U-boot. How Has This Been Tested? Tested on PocketBeagle 2 rev A0 Checklist: Please delete options that are not relevant. [x] My code follows the style guidelines of this project [x] I have performed a self-review of my own code [x] I have commented my code, particularly in hard-to-understand areas [x] My changes generate no new warnings [x] Any dependent changes have been merged and pub…

enable CONFIG_LEDS_CLASS_MULTICOLOR on current and edge rk3588 kernel configs to fix PS4 controller LED's View the full article

this patch will fix ps4 controllers not working correctly on legacy and vendor kernel View the full article

Description We somehow ended with non-bootable image yet again. Jira reference number AR-1692 How Has This Been Tested? Does not work yet, while it boots with defconfig. 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 This fixes reboot on Odroid C4 boards which boot from UHS microSD cards. The issue has been discussed before here: https://forum.armbian.com/topic/19340-odroid-c4-will-not-reboot-after-any-sort-of-kernel-update-have-tried-running-nand-sata-install/ A previous pull request removed a version of this patch here: https://github.com/armbian/build/pull/3154/files#diff-8530e3af79cd8a35329d7d1a44b2a8006ad0cd70deefb0341a9933233673a9b6 The previous version of the patch was broken by upstream changes in the kernel, and this commit contains the minimal changes needed to fix it. Standard PSCI reset functions are now called in mainline, so the patch has been updated to re…

Description Including fixes for: Nanopi Neo, Pine64so, Helios64 (removing legacy branch), Opi 2e, Sunvel r69 Jira reference number AR-1780 How Has This Been Tested? [x] Build test only View the full article

This is a critical fix, without it, all images with extlinux.conf will be broken and will not be able to run the system normally. View the full article

Description A bunch of patches did not apply anymore to rk322x/rockchip familes due to small upstream changes. This PR fixes the annoyance. How Has This Been Tested? [x] rk322x family patches apply cleanly for current kernel [x] rockchip family patches apply cleanly for current kernel 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 As per description. How Has This Been Tested? [ ] Build test Not tested on hardware. View the full article

No descriptionView the full article

Description station-p2 cannot start up properly. This is an interesting thing. Device tree name for station-p2: rk3568-firefly-roc-pc, derived from the previous media kernel family: https://github.com/armbian/build/blob/v24.05/patch/kernel/media-current/00170-v95-rk3568-firefly-roc-pc.patch But its name in the mainline kernel is: rk3568-roc-pc. But there has been an interesting change in this modification, and I am doubting whether this change is wise: https://github.com/armbian/build/commit/eb60d33abac91b25eb720bae27981a2a8950f9f7 I borrowed a station-p2 from my friend to fix this issue. How Has This Been Tested? [x] Successfully built. [x] System startup. Checkli…

Description https://github.com/armbian/build/commit/5dee9ee935703a559992478fa8045b464af72b50#commitcomment-111988535 Rockpi4 is using BL31 blobs to build uboot, so it should get configed with BOOT_SCENARIO="tpl-spl-blob". If BOOT_SCENARIO is not declared it will be only-blobs by default, which will not build tpl/u-boot-tpl.bin and spl/u-boot-spl.bin needed by spi image creating. So it's better to declare BOOT_SCENARIO="tpl-spl-blob" just like rockpro64. I don't have rock4 board so someone has to confirm this fix. 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…

Description Same fixes for rockchip 32 bit and rk322x families applied to patches for kernel 6.1 here, but for edge kernel 6.3 to let it compile happily. Can wait next release, but it should be no harm in any case How Has This Been Tested? [x] Compiled kernel deb packages for rk322x [x] Compiled kernel deb packages for rockchip 32 bit 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 pub…

Description 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 new warnings [ ] Any dependent changes have been merged and published in downstream modules View the full article

Description Four fixes: 1, board-pbp-add-dp-alt-mode.patch: there is an upstream change, so fix this patch to fit current kernel 2, board-rock3a-cec.patch: there is an already merged commit, so delete it 3, board-rock3a-hdmi-sound.patch already merged, delete it 4, board-rock3a-pcie.patch pcie2 part already merged, and pcie3 part is on the way. I deleted the pcie2 part and use pcie3 patch from upstream Still failed patch: wifi-4003-uwe5622-adjust-for-rockchip.patch. This is because base patch patch/misc/wireless-driver-for-uwe5622-allwinner.patch is not applied because of armbian-next merged to main and lib/functions/compilation/patch/kernel-drivers.sh has been drooped.…

Description Resolving same problem as https://github.com/armbian/build/pull/5148 How Has This Been Tested? Untested - no hardware around. 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 raspberry pi images were broken since #6087 as armbian.list was no longer available to install the required packages. As the description for #6087 mentioned that the change was just to remove the dormant armbian.list.disabled file, this PR does the same simply by removing the file if its present after image-late. 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 creating Raspberry pi images and also verifying that there is no leftover armbian.list.disabled file. Checklist: [ ] My code follows the style guidelines of this project [ ] I h…

Description As per subject, fix rtl8723cs on kernel 6.3 How Has This Been Tested? [x] Compilation for kernel 6.3 works [x] Compilation for kernel 6.1 works 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 As per subject, fix rtl8723du on kernel 6.3, useful until upstream driver get patched How Has This Been Tested? [x] Compilation for kernel 6.3 works [x] Compilation for kernel 6.1 works 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 As per subject, fix rtl8811cu on kernel 6.3 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] Compilation works 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 As per subject, fix rtl8812au on kernel 6.3, useful until upstream driver get patched How Has This Been Tested? [x] Compilation for kernel 6.3 works [x] Compilation for kernel 6.1 works 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 As per subject, fix rtl88x2bu on kernel 6.3, useful until upstream driver get patched How Has This Been Tested? [x] Compilation for kernel 6.3 works [x] Compilation for kernel 6.1 works 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

No descriptionView the full article

Description Some older U-Boot versions don't use semantic versioning in their code and will fail when building libfdt. This is fixed by hardcoding a semantic version. rk35xx used a very old branch from Radxa vendor U-Boot and won't build with GCC13. Bump it to the latest version. GitHub issue reference: https://github.com/armbian/build/issues/6862 Jira reference number AR-2402 How Has This Been Tested? [x] ./compile.sh uboot BOARD=radxa-e25 BRANCH=edge BUILD_DESKTOP=no BUILD_MINIMAL=no EXPERT=yes KERNEL_CONFIGURE=no RELEASE=noble ARTIFACT_IGNORE_CACHE=yes [x] ./compile.sh uboot BOARD=nanopi-r2s BRANCH=edge BUILD_DESKTOP=no BUILD_MINIMAL=no EXPERT=yes KERNEL_CONFIGURE=…

Deletes a group of 3D programs\settings for DE, which causes DE to be blocked from running with the legacy kernel. Station M2\P2\M3 Jetson Nano View the full article

Description This fixes armbian-firmware-full missing the symlinks from linux-firmware How Has This Been Tested? [x] Build an image with armbian-firmware-full and confirmed the symlinks were there and pointed to the right location 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

Fix the amlogic tvbox build's extlinux.conf to use uImage for the kernel image file instead of Image as some of the included uboot files do not support the Image format and require the uImage. Changes to be committed: modified: packages/bsp/aml-s9xx-box/boot/extlinux/extlinux.conf 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] Local build and install on multiple amlogic tv boxes [ ] 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, partic…

Fix the builddeb script so linux-image upgrades work correctly on fat /boot partitions. Currently the postinst file that is created has the following contents: ... ln -sf vmlinuz-6.0.10-meson64 /boot/Image 2> /dev/null || mv /boot/vmlinuz-6.0.10-meson64 /boot/Image touch /boot/.next mkimage -A arm64 -O linux -T kernel -C none -a 0x1080000 -e 0x1080000 -n "Linux" -d /boot/vmlinuz-6.0.10-meson64 /boot/uImage > /dev/null 2>&1 exit 0 ... In the first line on a fat filesystem the mv command leaves the system without a file named 'vmlinuz...'. The following mkimage command is looking for the vmlinuz... file that is no longer there and fails. This fix changes t…