RSS Bot

Description The media board family was long abandoned and most boards that formerly were using this board family already switched to rockchip64 or rk3588. @rpardini recently mentioned being in favor of getting rid of this kernel: https://github.com/armbian/build/pull/6717#discussion_r1632321571 Integrate the last remaining boards into rockchip64 and remove the media board family, including its kernel. GitHub issue reference: https://github.com/armbian/build/issues/6821 Jira reference number AR-2392 How Has This Been Tested? [x] ./compile.sh uboot BOARD=quartz64a BRANCH=edge BUILD_DESKTOP=no BUILD_MINIMAL=no EXPERT=yes KERNEL_CONFIGURE=no RELEASE=trixie [x] ./compile.sh uboot BOARD=quartz64b BRANCH=edge BUILD_DESKTOP=no BUILD_MINIMAL=no EXPERT=yes KERNEL_CONFIGURE=no RELEASE=trixie [x] ./compile.sh uboot BOARD=station-m1 BRANCH=edge BUILD_DESKTOP=no BUILD_MINIMAL=no EXPERT=yes KERNEL_CONFIGURE=no RELEASE=trixie [x] ./compile.sh uboot BOARD=station-p2 BRANCH=edge BUILD_DESKTOP=no BUILD_MINIMAL=no EXPERT=yes KERNEL_CONFIGURE=no RELEASE=trixie [x] ./compile.sh kernel BOARD=station-p2 BRANCH=edge BUILD_DESKTOP=no BUILD_MINIMAL=no EXPERT=yes KERNEL_CONFIGURE=no RELEASE=trixie [x] ./compile.sh uboot BOARD=firefly-itx-3588j BRANCH=edge BUILD_DESKTOP=no BUILD_MINIMAL=no EXPERT=yes KERNEL_CONFIGURE=no RELEASE=trixie @SeeleVolleri You can test the Firefly if you like. Your board was using the abandoned U-Boot from the media family. But it should work same as before :) Checklist: [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 [x] Any dependent changes have been merged and published in downstream modules View the full article

nanopi-r5s: bump blobs & u-boot enhancements for UMS/otg/bootorder nanopi-r5s: bump u-boot from v2024.04-rc3 to v2024.04 "final" nanopi-r5s: add ROCKUSB_BLOB (for Maskrom / rkdevflash extension flashing) nanopi-r5s: bump up blobs 1.18/1.43 -> 1.21/1.44 nanopi-r5s: make u-boot fancy (ums, rockusb, leds, tcp networking stuff) use preboot to flash all leds for 100ms, then leave power LED on nanopi-r5s: u-boot: 2024.04: boot order: usb -> sd -> nvme -> scsi -> emmc nanopi-r5s: u-boot: 2024.04: usb otg in u-boot for working UMS/RockUSB patch/u-boot/v2024.04: rewrite patches, no changes View the full article

Description rk322x has long been integrated into the rockchip family in this PR: https://github.com/armbian/build/pull/6092 Remove some leftovers in the repo, like the old kernel patch folders which are not in use anymore. @paolosabatino You may have a look at the hardware-optimization script. The tweaks for rk322x do not apply since the BOARDFAMILY does not exist anymore. If you'd like to rather integrate those optimizations in some other way (e.g. integrate them into the rockchip hardware optimizations), feel free to change it :) Also, please double check if packages/bsp/rk322x/50-rkvdec.rules is not used anymore. At least I could not find any reference when doing a search. GitHub issue reference: https://github.com/armbian/build/issues/6821 Jira reference number AR-2392 Checklist: [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 [x] Any dependent changes have been merged and published in downstream modules View the full article

Description Some kernel patch folders were forgotten to delete when the kernel version was bumped and are now unused leftovers from the past. Please let me know if I accidentally deleted a folder that is still in use. I have checked these for reference: https://github.com/armbian/build/blob/main/config/sources/families/rockchip.conf https://github.com/armbian/build/blob/main/config/sources/families/include/meson64_common.inc https://github.com/armbian/build/blob/main/config/sources/families/include/rockchip64_common.inc GitHub issue reference: https://github.com/armbian/build/issues/6821 Jira reference number AR-2392 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 packages/extras-buildpkgs was a leftover from years ago and is not used in the build framework anymore. See https://github.com/armbian/build/issues/6820#issuecomment-2198054353 With it, remove some references for hostapd and htop. The htop customization in the firstrun script is incompatible with the new versions and throws errors in the firstrun service (see the systemd status of this service after it ran). GitHub issue reference: https://github.com/armbian/build/issues/6820 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 View the full article

Description This PR is part of the big repo cleanup ✨ I tried to find references for the old toolchains. The only reference I could find that was actively using an external toolchain in meson-s4t7. There I have bumped the compiler from 7.3.1 to 7.4.1. A 2019 compiler seems like a good fit to compile a 2019 u-boot :) @viraniac Other than that, I found only this: https://github.com/armbian/build/blob/560993ac7aff4aafc94c8533b8d84eda73b4d656/lib/functions/host/external-toolchains.sh#L26-L37 I have kept every torrent that is referenced in that list, apart from the first few ones which are 10+ years old now and would probably not really work well on a modern machine anyway. Please let me know if you know that a certain compiler/torrent is still needed. 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 View the full article

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 and published in downstream modules View the full article

The aic8800_dkms_file_name for sdio should be aic8800-sdio-dkms. I think this is a copy-paste error when this extension was added. View the full article

simply because we can View the full article

Description This adds mainline support for the Radxa Zero 3 (E variant at least) SBC by utilizing kwiboo's patch series for both Linux and U-Boot. How Has This Been Tested? Test device: Zero 3E 2GB [x] build edge [x] boot edge http://paste.armbian.com/osofoyuqun.yaml [x] build vendor [x] boot vendor https://paste.armbian.com/lejunireni.yaml Issues: This PR cannot be merged as it is since I have no idea what I am doing so the kernel patchset lacks proper headers. I had to strip those since the framework did not accept the patch series as they were. I don't know how to fix. Those need to be restored to give proper credit. Source: https://patchwork.kernel.org/project/linux-arm-kernel/cover/20240521202810.1225636-1-jonas@kwiboo.se/ this only works for the 3E variant but not for 3W since the vendor variant is a combination of both but mainline provides separate dtbs. This needs attention/workaround as well. BOOTPATCHDIR is just fake so no patches are applied on top of upstream sources. I assume there is a more pretty way to solve this. Raising anyways to create awareness and maybe anyone wants to pick it up and fix things. Feel free to commit adjustments here and bring it in good shape. 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 As mentioned here: https://github.com/armbian/build/pull/6810#issuecomment-2194178735 Out of date blobs can be an issue if the vendor ships boards with new blobs, as recently seen for FriendlyElec with the NanoPC T6 for example. The release docs do not mention any incompatibilities between versions for rk3528 and rk3568: https://github.com/armbian/rkbin/blob/master/patch-notes/RK3528_EN.md https://github.com/armbian/rkbin/blob/master/patch-notes/RK3568_EN.md For rk3566, only one warning is listed for rk3566_ddr_1056MHz_ultra_v1.19.bin but we're not using the ultra blob (what's the difference?): https://github.com/armbian/rkbin/blob/master/patch-notes/RK3566_EN.md#rk3566_ddr_1056mhz_ultra_v119bin ROCK_USB_BLOB bump depends on https://github.com/armbian/rkbin/pull/29 being merged. Other blobs have already been merged to armbian/rkbin in the past. How Has This Been Tested? [x] RK3568: ./compile.sh uboot ARTIFACT_IGNORE_CACHE=yes BOARD=nanopi-r5c BRANCH=edge BUILD_DESKTOP=no BUILD_MINIMAL=no EXPERT=yes KERNEL_CONFIGURE=no RELEASE=trixie [ ] RK3566: Not tested - @RadxaNaoki would be great if you could test on Raxda Zero 3 or similar board 😊 [ ] RK3528: Not tested - @amazingfate @sputnik2019 would be great if you could test on a RK3528 board 😊 (although the doc does not list any incompatibilities) Checklist: [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 [ ] Any dependent changes have been merged and published in downstream modules View the full article

Description Also group all u-boot make environment variables together for easier maintainability Fixes u-boot requiring pyelftools Fixes commit https://github.com/armbian/build/commit/04f619dc06d12449b1315f01bb8fe70003316761 GitHub issue reference: https://github.com/armbian/build/pull/6799#issuecomment-2196438786 How Has This Been Tested? [x] sudo apt remove python3-pyelftools and then ./compile.sh uboot ARTIFACT_IGNORE_CACHE=yes BOARD=nanopi-r6c BRANCH=edge BUILD_DESKTOP=no BUILD_MINIMAL=no EXPERT=yes KERNEL_CONFIGURE=no RELEASE=trixie [x] ./compile.sh uboot ARTIFACT_IGNORE_CACHE=yes BOARD=radxa-zero3 BRANCH=edge BUILD_DESKTOP=no BUILD_MINIMAL=no EXPERT=yes KERNEL_CONFIGURE=no RELEASE=trixie 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

(partially) Revert "python: Move python3-setuptools and python3-pyelftools to requirements.txt" (partially) Revert "python: Move python3-setuptools and python3-pyelftools to requirements.txt" "Fixes" https://github.com/armbian/build/pull/6799 This (partially) reverts commit 04f619dc View the full article

rtl_bt: Update RTL8822C BT UART firmware to 0xB5D6_6DCB View the full article

Description Update odroidxu4-current kernel to 6.6.36. 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 A new issue template for Tasks will make project/task tracking easier on GitHub. See for example how Pi-Hole does project tracking: https://github.com/orgs/pi-hole/projects/22 The tasks will be automatically uploaded to Jira, so no changes there. How Has This Been Tested? [ ] To be tested in future issues 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 View the full article

Description station-m2: update u-boot patches. Add u-boot device tree for station-m2. How Has This Been Tested? [x] Successfully built. [x] System startup. Checklist: [x] My code follows the style guidelines of this project [x] I have performed a self-review of my own code [x] I have commented my code, particularly in hard-to-understand areas [x] My changes generate no new warnings [x] Any dependent changes have been merged and published in downstream modules View the full article

With each board running a mainline-first Linux software stack and tested in a CI loop with the LAVA test framework, the Farm showcased Collabora's recent hardware enablement and Continuous integration (CI) efforts. 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] 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: [] short description (copy / paste of PR title) [ ] summary (description relevant for end users) [ ] example of usage (how to see this in function) 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: 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

rk3588: bump default blobs (DDR:1.16, BL31:1.45); remove board-specific blobs from boards that used those versions rk3588: bump default blobs (DDR:1.16, BL31:1.45); remove board-specific blobs from boards that used those versions in practice: boards that didn't specify their own blobs: bump DDR 1.08->1.16 ; BL31 1.28 -> 1.45 (example: rock-5b!) boards that specified 1.16/1.45 individually now follow the defaults (no change) boards that specified a different version: no change; just a TODO suggesting review/removal/go-with-the-defaults Mekotronics boards: bump from 1.11/1.38 to defaults (1.16 / 1.45) View the full article

fix: partitioning: disable orphan_file (FEATURE_C12) for ext4 filesystems on 1.47+ e2fsprogs host fix: partitioning: disable orphan_file (FEATURE_C12) for ext4 filesystems on 1.47+ e2fsprogs host otherwise:fsck.ext4 -a -C0 /dev/mmcblk0p1 /dev/mmcblk0p1 has unsupported feature(s): FEATURE_C12 e2fsck: Get a newer version of e2fsck! orphan_file can only be disabled on recent-enough e2fsprogs, thus check version and compare View the full article

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

Description The color hex code cannot be prefixed with #. See https://github.com/armbian/build/actions/runs/9683062190/job/26717603287 How Has This Been Tested? [ ] To be tested in future PRs Checklist: [x] My code follows the style guidelines of this project View the full article

WirePlumber 0.5 arrived recently with many new and essential features including the Smart Filter Policy, enabling audio filters to automatically insert themselves in between client streams and devices. View the full article