RSS Bot

Description Uboot from rockchips's latest 6.1 rkr3 SDK is here: https://github.com/ArmSoM/u-boot/tree/rk3576-6.1-rk3.1 And the two patches fixing sd card boot is already there. Add config CONFIG_ROCKCHIP_EARLY_DISTRO_DTB to load dtb from kernel so that devices like rk806 pmic is supported by uboot: DM: v2 no mmc device at slot 1 mmc@2a310000: 1 (SD), mmc@2a330000: 0 Bootdev(atags): mmc 1 MMC1: Legacy, 52Mhz PartType: EFI 258194 bytes read in 385 ms (654.3 KiB/s) DTB(Distro): /boot/dtb/rockchip/rk3576-armsom-sige5.dtb No misc partition boot mode: None dw_dp_bind zyb enter I2c1 speed: 100000Hz PMIC: RK8060 (on=0x80, off=0x80) vdd_cpu_big_s0 init 850000 uV vdd_npu_s0 750000 uV vdd_cpu_lit_s0 init 850000 uV vdd_gpu_s0 init 750000 uV vdd_logic_s0 init 750000 uV vdd_ddr_s0 850000 uV Could not find baseparameter partition Model: ArmSoM Sige5 How Has This Been Tested? Please describe the tests that you ran to verify your changes. Please also note any relevant details for your test configuration. [x] ./compile.sh BOARD=armsom-sige5 BRANCH=vendor BUILD_MINIMAL=no DEB_COMPRESS=xz KERNEL_CONFIGURE=no RELEASE=noble KERNEL_GIT=shallow BUILD_DESKTOP=yes DESKTOP_APPGROUPS_SELECTED= DESKTOP_ENVIRONMENT=gnome DESKTOP_ENVIRONMENT_CONFIG_NAME=config_base [x] Tested with sd card and emmc 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 [ ] 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 the full article

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

Description This provide an option to set last good kernel for dedicated device. It will prevent upgrading to higher kernels which are known to be broken. For example. At this moment we have Rockchip BSP kernel which was fixed that Radxa ITX has working ports, while this fix will break NVME support on Orangepi. Also this we can use for Pinebook PRO. Configuration: BOARD BRANCH LINUXFAMILY Last good kernel package from repository orangepi5 vendor rk35xx 24.5.3 orangepi5plus vendor rk35xx 24.5.3 orangepi5|vendor|rk35xx|24.5.3 orangepi5plus|vendor|rk35xx|24.5.3 How Has This Been Tested? [x] Test with locally generated repo that contained higer version of kernel. It was hold back. Checklist: [x] I have performed a self-review of my own code [x] I have commented my code, particularly in hard-to-understand areas [x] My changes generate no new warnings [x] Any dependent changes have been merged and published in downstream modules View the full article

Description Add armbian patches from sunxi-6.7 Adapt the patch series to the new v6.10.5 kernel version Delete unused patches and add newly extracted patches. How Has This Been Tested? [x] Build for arm64 & test work on board ____ ____ _ __ __ __ _ _ | __ )| _ \(_) | \/ |/ /_ | || | | _ \| |_) | | | |\/| | '_ \| || |_ | |_) | __/| | | | | | (_) |__ _| |____/|_| |_| |_| |_|\___/ |_| Welcome to Armbian_community 24.8.0-trunk Bookworm with bleeding edge Linux 6.10.5-edge-sunxi64 No end-user support: built from trunk System load: 2% Up time: 11 min Memory usage: 6% of 1.94G IP: 192.168.100.101 CPU temp: 26°C Usage of /: 18% of 7.2G Time CPU load %cpu %sys %usr %nice %io %irq Tcpu C.St. 15:14:27 1008 MHz 0.00 5% 0% 0% 0% 3% 0% 23,3 °C 0/7 15:14:33 1008 MHz 0.00 3% 2% 0% 0% 0% 0% 22,8 °C 0/7 15:14:38 1008 MHz 0.00 2% 2% 0% 0% 0% 0% 22,2 °C 0/7 View the full article

Description Expand functions install_deb_chroot and install_artifact_deb_chroot with additional parameter. This adds support to pass additional parameters to package installer. Enable allow-downgrades to base-files to allow building images with older version than current Framework stores our base-files in rootfs cache with version that comes from trunk and when we make stable images for current or previous release, build fails with error E: Packages were downgraded and -y was used without --allow-downgrades. https://github.com/armbian/build/issues/7048 AR-2350 AR-2454 How Has This Been Tested? Manual install of broken 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] My changes generate no new warnings View the full article

Description Enable proper enumeration of usb-bluetooth modules via M2/NGFF slot - without this patch, no pcie-integrated usb-module would wourk as device-tree lacks rfkill-bt device node How Has This Been Tested? [x] Applied patch to BOARD=rock-5b BRANCH=current, got lsusb output Bus 004 Device 004: ID 0bda:b85b Realtek Semiconductor Corp. Bluetooth Radio [x] Bluetoothctl recognized bluetooth controller [x] Succesfully paired to a bluettoth device (iPhone) 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

During a search I noticed other companies are using the same unit. Lets re-brand to Amper as technically that is the product brand name. https://products.z-wavealliance.org/products/4022 View the full article

Description fixed rockchio6.10 tinker-edge-r 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] Test A [x] Test B 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 Update odroidxu4-current kernel to 6.6.47. How Has This Been Tested? [x] Reboot of my Odroid HC1 Checklist: [x] My code follows the style guidelines of this project [x] I have performed a self-review of my own code [x] I have commented my code, particularly in hard-to-understand areas [ ] I have made corresponding changes to the documentation [x] My changes generate no new warnings [ ] Any dependent changes have been merged and published in downstream modules View the full article

Description 6.11-RC4 was released on 2024-08-18 (https://kernel.org/). rewrite-kernel-patches results in no diff. How Has This Been Tested? [ ] ./compile.sh BOARD=nanopi-r6c BRANCH=edge BUILD_DESKTOP=no BUILD_MINIMAL=no EXPERT=yes KERNEL_CONFIGURE=no RELEASE=trixie EXTRAWIFI=no kernel Checklist: [x] My code follows the style guidelines of this project [x] I have performed a self-review of my own code View the full article

Description I'm working on integrating the Youyeetoo R1 V3 board into the Armbian ecosystem by writing DTS files and testing system functionality. Here is the hardware that this board supports: Feature Description Model Youyeetoo R1 V3 CPU RK3588S Memory LPDDR4 (up to 32GB) USB 1x USB 3.0, 3x USB 2.0 Ethernet 1x GbE I/O GPIO, UART, NVME PCIe 2.0, eMMC, SD Card, M.2 (WiFi) When the compatibility is fully established, I plan to move it from WIP to CSC. 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 images are downloaded https://share.superkali.me/s/CsXEGJoKTDBbDzc under the Armbian directory [x] All tests are conducted with the board [x] Here the boot log https://paste.armbian.com/atepiyeqok 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

Bumps setuptools from 72.1.0 to 72.2.0. Changelog Sourced from setuptools's changelog. v72.2.0 Features pypa/distutils#272pypa/distutils#237pypa/distuils#228#4538) Commits 76942cf Bump version: 72.1.0 → 72.2.0 780a782 Correct reference in news fragment. Ref #4539 64f10c5 Merge pull request #4539 from pypa/feature/distutils-b7ee725f3 d4ad24b Add news fragment. 0ab156c Merge https://github.com/pypa/distutils b7ee725 Apply isort. Ref pypa/distutils#240 32e5fea Rely on monkeysession to monkeypatch. 5f79f22 Merge pull request pypa/distutils#274 from msys2-contrib/ci-msvc-python-mingw... 6748224 Merge pull request pypa/distutils#273 from msys2-contrib/tests-fix-venv_insta... 1f999b9 Remove unused RangeMap Additional commits viewable in compare view Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase. Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: @dependabot rebase will rebase this PR @dependabot recreate will recreate this PR, overwriting any edits that have been made to it @dependabot merge will merge this PR after your CI passes on it @dependabot squash and merge will squash and merge this PR after your CI passes on it @dependabot cancel merge will cancel a previously requested merge and block automerging @dependabot reopen will reopen this PR if it is closed @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) View the full article

Description This reverts commit 49e0ec5d0ec6096292fc3b0e13c855d4297cbcb9. @glneo @3V3RYONE How Has This Been Tested? Ti GIT is accessible. 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 Right before release its best time to verify if board is still interested to be kept under support. Or to pull community supported under our wings. We need to know the status, someone has to be behind, etc. tl;dr; Board Support Rules - Armbian Documentation review maintainers review kernel build targets review test targets How Has This Been Tested? Smoke tests will be tested via this branch to determine best test targets. Checklist: [ ] I have performed a self-review of my own code [ ] I have commented my code, particularly in hard-to-understand areas [ ] My changes generate no new warnings [ ] Any dependent changes have been merged and published in downstream modules View the full article

Description X96Q TV Box LPDDR3 H313 How Has This Been Tested? Please describe the tests that you ran to verify your changes. Please also note any relevant details for your test configuration. [x] ./compile.sh build BOARD=x96q-tvbox BRANCH=current BUILD_DESKTOP=yes BUILD_MINIMAL=no EXPERT=yes KERNEL_CONFIGURE=no KERNEL_GIT=shallow RELEASE=noble [x] Tested on current 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 [ ] 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 the full article

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

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

Description Add megous patches Sunxi edge switch kernel to v6.10.5 How Has This Been Tested? [x] Test build on ubuntu 22.04 env the Bookworm img [x] Test work on BPI-m64 & install on eMMC ____ ____ _ __ __ __ _ _ | __ )| _ \(_) | \/ |/ /_ | || | | _ \| |_) | | | |\/| | '_ \| || |_ | |_) | __/| | | | | | (_) |__ _| |____/|_| |_| |_| |_|\___/ |_| Welcome to Armbian_community 24.8.0-trunk Bookworm with bleeding edge Linux 6.10.5-edge-sunxi64 No end-user support: built from trunk System load: 7% Up time: 0 min Memory usage: 7% of 1.94G IP: 192.168.100.101 CPU temp: 25°C Usage of /: 17% of 7.0G View the full article

Description The forked helper workflow ran regardless whether ARMBIAN_SELF_DISPATCH_TOKEN was set or not, generating errors if the secret could not be found. In addition, simplify and beautify the workflow. How Has This Been Tested? [ ] To be tested in future automatic workflow runs, if no errors are generated Checklist: [x] My code follows the style guidelines of this project [x] I have performed a self-review of my own code [x] I have commented my code, particularly in hard-to-understand areas View the full article

After rigorous debugging, a new unit testing framework was added to the backend compiler for NVK. This is a walkthrough of the steps taken to achieve this. View the full article

Description Found lost patch for JetHub D2 devicetree file. Jira reference number AR-2028 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 loop devices created by default Run a dockerized build ./compile.sh build PREFER_DOCKER=yes Checklist: [x] My code follows the style guidelines of this project [x] I have performed a self-review of my own code [x] I have commented my code, particularly in hard-to-understand areas [x] My changes generate no new warnings View the full article

Description rework to apply cleanly on 6.10.5 and 6.6.46 - root cause GitHub issue reference: #7087 Jira reference number AR-2467 special thanks: @EvilOlaf How Has This Been Tested? [x] Patch applies cleanly to meson64 edge 6.10.5 - compiling ok [x] Patch applies cleanly to meson64 current 6.6.46 - compiling 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 rework to apply cleanly on 6.10.5 and 6.6.46 - root cause GitHub issue reference: #7087 Jira reference number AR-2467 special thanks: @EvilOlaf How Has This Been Tested? [x] Patch applies cleanly to rockchip64 edge 6.10.5 - compiling ok [x] Patch applies cleanly to rockchip64 current 6.6.46 - compiling 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 The kernel supports compilation with LLVM in addition to GCC, including cross-compilation to arm and riscv. This PR adds an option to use KERNEL_COMPILER=clang to compile kernel with clang. Documentation summary for feature / change I haven't added documentation but probably should? How Has This Been Tested? [x] Built armbian with clang for one target of each architecture (x86, arm, riscv) [x] Verified that gcc build still works 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 [ ] My changes generate no new warnings View the full article