SBC News
Atom feed, Pull requests awaiting review and other tech news
4463 topics in this forum
-
Description Update odroidxu4-current kernel to 6.6.43. 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 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 Update odroidxu4-current kernel to 6.6.51. 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 Update odroidxu4-current kernel to 6.6.93. 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 Expand oneshot eth reset service for JetHub J100. Changed only JetHub BSP Jira reference number AR-1098 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. [ ] builds ok [ ] 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…
-
Description Add more generic patches to legacy kernel and re-enable legacy images as those works decently while mainline is too fragile. Jira reference number AR-1396 How Has This Been Tested? [x] Generated image, run several tests, [x] installed headers, run zfs-dkms module compilation Checklist: [x] My code follows the style guidelines of this project [x] I have performed a self-review of my own code [x] I have commented my code, particularly in hard-to-understand areas [ ] My changes generate no new warnings [x] Any dependent changes have been merged and published in downstream modules View the full article
-
Create a overlay_prefix to h616 for orangepizero3. Description There are no overlays nor fixup scripts for h618. Since the orangepizero3 is i/o hardware identical to the orangepizero2, it makes sense to just point the zero3 to the zero2 overlays. Jira reference number [AR-9999] How Has This Been Tested? An image for orangepizero3 with this change was generated. It ran the fixup script on boot. Armbian-config -> System-> Hardware was used to enable an spidev. On reboot the overlay was loaded. 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…
-
Readability/grammatical improvements Removed icon to fix broken Contribution link in TOC View the full article
-
replace master with main. Untested Adressese https://github.com/armbian/build/issues/5870#issuecomment-1783812910 View the full article
-
No descriptionView the full article
-
Description Update ddr and bl31 blobs for opi5 and nanopi r6s Jira reference number [AR-9999] How Has This Been Tested? [x] Built and booted R6S fine [x] Orange Pi 5 was already working fine with https://github.com/armbian/build/commit/084fba8524937298a05fea55076ced540924cd22 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 add recent blobs from https://github.com/rockchip-linux/rkbin/tree/master/bin/rk35 depends on: https://github.com/armbian/rkbin/pull/18 Jira reference number [AR-9999] How Has This Been Tested? [x] Built and booted on opi5 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 PR updates rk3588-edge kernel branch to 6.7-rc.1 and adds support for initial VOP2, crpto and HW RNG support. Jira reference number [AR-9999] How Has This Been Tested? [x] Orange Pi 5 Plus boots well. [x] Type-c and type-a ports work with OPI5+. [x] HW RNG and crypto tested. [x] VOP2 works but not really stable. [x] ES8388 audio should work, i have no speakers to test it. 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 warni…
-
Description Rockchip has released legacy kernel 5.10 supporting rk3568, and friendlyarm has been using it on nanopi5: https://github.com/friendlyarm/kernel-rockchip/tree/nanopi5-v5.10.y_opt/. I did tried the legacy kernel that rk3588 uses on rk3568 board but failed to boot with pcie devices. So although this friendlyarm kernel is mostly the same as the legacy kernel rk3588 uses, it is still the best supported 5.10 kernel for rk3568. Since we have patch board-rock3a-Add-DT-link-for-backward-compatibility.patch, we can use the default device tree file rockchip/rk3568-rock-3a.dtb same as the edge kernel. Device tree file is from radxa's legacy 4.19 kernel repo modified wit…
-
Description Also update rk35xx to 5.10 rkr4 for rk356x 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] Build legacy image for rock3a [x] Image works on rock3a 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 My rock5b always encountered system hang with the old rkbin files when ddr freq is 2112MHz. After updating these binaries there is no system hangs. 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] u-boot build successfully [x] no system hangs after updating u-boot 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…
-
Description Use Radxa's upstream dtb from here. How Has This Been Tested? Built, flashed, booted on a CM5 I/O board. 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
-
Update the version of U-boot used with Radxa rock 4 se to v2025.04. Tested locally on my board after building an armbian image. ubuntu@rock-4se:~$ strings /dev/mmcblk1 | grep U-Boot U-Boot SPL 2025.04-armbian-2025.04-S3482-P4a0b-H3d34-Va9af-Bb703-R448a (Apr 22 2025 - 10:05:17 +0000) U-Boot phase U-Boot FIT image for U-Boot with bl31 (TF-A) Description Update the version of U-boot used with Radxa rock 4 se. GitHub issue reference: 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] Image built using armbian/build [x] Flashed and…
-
Description I copy the patches from rockchip64-5.18 to rockchip64-5.19 and make these changes: 1, rk3328-dtsi-add-rkvdec-node.patch removed because upstream merged. 2, add-board-roc-pc.patch rename rkvdec to vdec 3, add-board-tvbox-rk3318.patch rename rkvdec to vdec, rename rkvdec_mmu to vdec_mmu. 4, board-firefly-rk3399-dts.patch removed since @150balbes said this board is in media family. 5, board-pbp-add-suspend.patch moved to need_checking. Upstream code has changed a lot and I don't know how to do with this patch. 6, refactor-iommu-initialisation.patch removed since already merged to upstream 7, wifi-4005-uwe5622-makefile.patch modified due to upstream change 8, gene…
-
Description Two kernel branches have been added to 8250, as some of its features were compromised in 6. x, the latest branch is needed for testing Jira reference number [AR-9999] How Has This Been Tested? Both kernels were compiled on UMI and passed [x] Legacy [x] Edge 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 sunxi-6.6: patches: A small cleaning was done. Delete unused ones. Update the changed ones. mk_format_patch: Copy only those patches that have changes in chunks View the full article
-
Update support for Recore boards Adding support for Recore 3D printer control boards A5 through A8. There is support for these boards in an older version of build, but they don't seem to have been propagated. There are some improvements in this version (thus the "update" in the description) and also support for a newer version of the hardware. Recore is a 3D printer control board. Documentation summary for feature / change [x] short description (copy / paste of PR title) [x] summary (description relevant for end users) How Has This Been Tested? It has been tested on the following hardware: [x] Recore A5 [x] Recore A6 [x] Recore A7 [x] Recore A8 Checklist: [x] I h…
-
Description Update symlink for bluetooth firmware on JetHub D1 Jira reference number AR-2022 How Has This Been Tested? Please describe the tests that you ran to verify your changes. Please also note any relevant details for your test configuration. [X] JetHub D1 build and run ok Checklist: [ ] My code follows the style guidelines of this project [ ] I have performed a self-review of my own code [ ] I have commented my code, particularly in hard-to-understand areas [ ] I have made corresponding changes to the documentation [ ] My changes generate no new warnings [ ] Any dependent changes have been merged and published in downstream modules View the full article
-
Update wording from sponsors to partners and moved 'Friends' to authors page on website and link under 'Also' as 'Friends and individuals' 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 commente…
-
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 MAN-86 Checklist: [x] I have made corresponding changes to the documentation View the full article
-
Description Radxa has changed the config name for rock-3a: https://github.com/radxa/u-boot/commit/41ffd0087708e3381e7e166c4ca646f31cd9e097. We have to update 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] u-boot build successfully 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 mer…
-
Description Update u-boot patches for JetHub D1/D1+ add rescue boot from microSD revert JetHub D1 eth mac generation with manufacturer OUI Jira reference number AR-1448 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 m…
-
Description Update u-boot to use 2023.01, which contains fixes to u-boot environment handling How Has This Been Tested? [ ] Test on ebin v5 [ ] Test on ebin v7 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
-
Not sure why this hasn't been adjusted yet... View the full article
-
Description Add missing kernel dependencies. How Has This Been Tested? [ ] Build 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 [ ] Any dependent changes have been merged and published in downstream modules View the full article
-
Description Maint. Jira reference number AR-1343 How Has This Been Tested? [x] Build and boot CURRENT [x] Build and boot EDGE View the full article
-
Description update-apt-xapian-index takes an insane amout of time during buid - compounding over dozens of builds you get a nice overhead in compute-time in the hours range This PR disables update-apt-xapian-index for unstable releases ( $BETA = yes ) 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 orangepi5-plus desktop with and without BETA=yes, results below Baseline 1st run ( CLEAN_LEVEL="debs,cache" ) Repeat Build Options [ ./compile.sh opi5plus build BRANCH=edge BUILD_DESKTOP=yes CLEAN_LEVEL=debs,cache DESKTOP_APPGROUPS_SELECTED='browsers chat d…
-
Description Rewrite patches since we have stable git hash length KERNELPATCHDIR is no longer $LINUXFAMILY-$BRANCH, so declare it in board config file Bump kernel to 6.7.y Add support for nintendo pro/joycon controller since this device can run yuzu emulator well. 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 kernel BOARD=xiaomi-elish BRANCH=sm8250 DEB_COMPRESS=xz KERNEL_GIT=shallow [x] Xiaomi elish boots fine Checklist: [x] My code follows the style guidelines of this project [x] I have performed a self-review of my own code [ ] I have comm…
-
Made the file as advised equal to prepare-host.sh adviced in the prepare-host.sh pull request.. There where also some other Ubuntu distributions not added to this file. The are now also added. Hope i did this pull request on the right way :) View the full article
-
No descriptionView the full article
-
Description Updated rockchip RND driver from the v4.4 legacy version to one found packaged with a v5.10 kernel @paolosabatino says this supports more Rockchip SOCs 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] Builds updated image [x] Verified that RK3308 HW RNG still functions with updated driver [ ] @paolosabatino should verify that additional SOCs are, in fact, supported 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, pa…
-
Updates for Radxa's Amlogic boards (radxa-zero and radxa-zero2) A few updates, mostly from https://github.com/radxa-repo/bsp; also bump u-boot to v2202.10 with a clearly-non-existing patchdir so it's pure mainline. Also required: https://github.com/armbian/firmware/pull/40 (merged, Wifi firmware) https://github.com/armbian/build/pull/4408 (merged, allows using SDXC cards) Still not working: SDIO Wifi on my Zero (rev 1.51, 2gb RAM/32gb eMMC) which is failing; see https://discord.com/channels/855634073376260096/855657603378839582/1040610755671756911 ; it's very possible other boards work. View the full article
-
Updates to grammar and wording for Armbian Partners section. 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 correspond…
-
Description fixing links removing notes for old branch View the full article
-
Tested on models of the media\station group View the full article
-
Description Maintenance. Break key implementation changes so our SPACE -> CTRL C patch doesn't work anymore. Jira reference number AR-1319 How Has This Been Tested? [x] Build tests [x] Boot test on Opi3LTS, 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 Upgrade vcgencmd without tmp vulnerability and inclusion for bananapim2ultra See also https://github.com/armbian/build/pull/5095#issuecomment-1521626783 How Has This Been Tested? [x] Pine64 [x] Rock64 [x] Banana Pi M2 Ultra 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 the tittle. Solution / workaround = attach it to last known working commit id. Jira reference number AR-1282 How Has This Been Tested? [x] Tested with 5.4.y and 5.19.y 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 beaglev, edge, sid, cli, ubuntu-latest error! Could not download 'http://deb.debian.org/debian-ports/pool/main/b/base-files/base-files_12.4_riscv64.deb' https://deb.debian.org/debian-ports/pool -> pool-riscv64 Jira reference number AR-1733 How Has This Been Tested? [ ] Manual rebuild 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 t…
-
Description When LABEL is longer than 11 characters, mkfs.fat 4.2 (2021-01-31) will fail while mkfs.fat 4.1 (2017-01-24) will cut it. I want to split out a new function for formating filesystem. But unfortunally, there is a hook pre_prepare_partitions and prepare_partitions_custom. And bcm2711 use it for LABEL. Here is my try: hzyitc/armbian-onecloud#6c190484 The source of mkfs.fat: v4.1: https://github.com/dosfstools/dosfstools/blob/v4.1/src/mkfs.fat.c#L1500: case 'n':/* n : Volume name */ sprintf(volume_name, "%-11.11s", optarg); for (i = 0; volume_name[i] && i < 11; i++) /* don't know if here should be more strict !uppercase(label[i]) */ if (islow…
-
Description CI optimisation View the full article
-
Description The "optional/boards" directory seems to have been deprecated and actually never used so much. Remove the last board support package there (rk3318-box) and move into extension as suggested by @rpardini. Ancillary BSP files have been removed too. The extension may have global interest because it was a workaround for X.Org and Lima driver: the former was not able to autodetect the latter with some revision combinations. That configuration fixes the autodetection. At the moment, it has been enabled in rk3318-box board and rk322x family. How Has This Been Tested? [x] Compile debian bookworm image for rk3318-box and verify 40-serverflags.conf presence [x] Compi…
-
Description I was unable to boot from m2 ssd (of course with SPI NOR FLASH) when bootfs part was ext4. Then i used bootfs part as fat and it worked. I think Xunlong's Uboot source doesn't support Ext4 bootfs parts. How Has This Been Tested? [x] Tested on my Orange Pi 5 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 Sadly ghproxy.com is down. But this site is based on https://github.com/hunshcn/gh-proxy and has many candidates. I did create one with a cloudflare accout: gitboost.haguro.workers.dev. So add GHPROXY_ADDRESS to let user choose their own proxy url. Default url is still ghproxy.com if GHPROXY_ADDRESS is not 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 extra args GITHUB_MIRROR=ghproxy GHPROXY_ADDRESS=gitboost.haguro.workers.dev Checklist: [x] My code follows the style guidelines of this project [x] I have performed a self-review…
-
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. [x] test with command ./compile.sh build GITHUB_MIRROR=ghproxy REGIONAL_MIRROR=china BOARD=licheepi-4a BRANCH=legacy BUILD_DESKTOP=no BUILD_MINIMAL=yes KERNEL_CONFIGURE=yes RELEASE=jammy SKIP_EXTERNAL_TOOLCHAINS=no,can download releate package success as: [🐸] wget --no-verbose --progress=dot:giga -O…
-
Description The type names will cause build problem in focal (use sfdisk v2.34) and bullseye (use sfdisk v2.36) The partition type is given in hex for MBR (DOS) where 0x prefix is optional; a GUID string for GPT; a shortcut or an alias. It’s recommended to use two letters for MBR hex codes to avoid collision between deprecated shortcut 'E' and '0E' MBR hex code. For backward compatibility sfdisk tries to interpret type as a shortcut as a first possibility in partitioning scripts although on other places (e.g. --part-type command) it tries shortcuts as the last possibility. Since v2.36 libfdisk supports partition type aliases as extension to shortcuts. The alias is a si…
-
use hooks for main kernel/u-boot version defaulting/overriding; remove symlink usage from many families [cleanup] extensions: flash-kernel: removed (and a few references to it) thanks to Gunjan for replacing it [cleanup] rk3399: remove defunct patches & dangling symlinks for rk3399-legacy and rk35xx-legacy [cleanup] rockchip64 legacy: remove long dead 4.4 patches (family/common didn't define legacy branch for a while) core: semantic change, KERNELSOURCE must be explicitly 'none' to avoid kernel compilation (not unset) main-config: mark mirror variables readonly; add todo's lib/family config: remove resquices of KERNELDIR which is completely unused for a long time …
-
Description Couple small fixes I found when starting to add support for TI SK boards. Wanted to test the waters with these patches before working to add board support. How Has This Been Tested? Built a couple platforms without issue due to this change. 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 Mainline kernel 6.3 and above implements yt8531 driver. This pull request removes the legacy driver patch and fix the device tree for Orange Pi 4 LTS and other devices to use that driver. Note: this PR has a "dependency" upon this other PR (https://github.com/armbian/build/pull/5290) - these two PRs are unrelated, but the PR-5290 bug does not allow me to easily test without having conflicts later. This is just a note, everything should go on flawlessy once PR-5290 is merged. Jira reference number AR-1774 How Has This Been Tested? [x] Tested dtb on a live Orange Pi 4 LTS system [ ] Tested on Orange Pi R1 LTS (@schwar3kat) Checklist: [x] My code follows th…
-
Description Add parallel compression for xz with the option XZ_OPT="--threads=0" gzip and bzip were already using parallel compressors. xz has this option built-in, so add the argument to make use of it. Source: https://lore.kernel.org/lkml/20200901151002.988547791@linuxfoundation.org/ Also change KBUILD user and host to make cat /proc/version show something like Linux version 6.9.8 (build@armbian) instead of Linux version 6.9.8 (armbian@next). build@armbian refers to the Armbian build framework (this repository) How Has This Been Tested? [x] ./compile.sh build BOARD=nanopi-r6c BRANCH=edge BUILD_DESKTOP=no BUILD_MINIMAL=no EXPERT=yes KERNEL_CONFIGURE=no RELEASE=trixi…
-
Description We download some newer gcc but we didn't use it. Since buster is eos, #2403 isn't a issue now. So let use newer gcc. 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 arm [X] Build aarch64 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 [ ] My changes generate no new warnings [ ] Any dependent changes have been merged and published in downstre…
-
Description The default power_allocator governor will not speed up the pwm fan when temp rises up, but step_wise will do according to cooling_level defined in the devicetree. Before this commit I have to set the governor manually by command echo step_wise > /sys/class/thermal/thermal_zone0/policy on rock5b. Since there are many rk3588 boards have pwm-fan node defined in the devicetree, I think it's better to set this governot to default. 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] No need to manualy set the governor after installing the kernel Checkli…
-
Description There are many rk3588 boards using u-boot from radxa, and they share the same patch fix_source_so_boot_scr_works.patch. It's better to have just one patch in the repo. So I create one common patch dir legacy/u-boot-radxa-rk3588 for all boards using radxa's u-boot. Since 0001-Add-defconfig-and-dtb-of-nanopi6.patch and add-board-mekotronics-r58.patch won't harm other boards so I also move them to the common dir. If someone want board specfic patches, he can put them to patch/u-boot/legacy/u-boot-radxa-rk3588/board_${BOARD}, just like patch/u-boot/legacy/u-boot-radxa-rk3588/board_hinlink-h88k/uboot-hinlink-h88k-config.patch. How Has This Been Tested? Please desc…
-
Description On older kernels like v6.1.x the TI devices are better supported by the TI vendor kernel than the upstream kernel. For the current kernel let's use the TI kernel for these boards. While here bump the edge kernel to v6.6.x which also has better support for features found on these platforms than v6.5.x. How Has This Been Tested? [x] Build and boot SK-AM64B with current kernel [ ] Build and boot SK-AM62B with current kernel [x] Build and boot SK-TDA4VM with current kernel [x] Build and boot SK-AM64B with edge kernel [ ] Build and boot SK-AM62B with edge kernel [ ] Build and boot SK-TDA4VM with edge kernel Checklist: [x] My code follows the style guidelines of…
-
Description Checklist: Please delete options that are not relevant. [x] My code follows the style guidelines of this project View the full article
-
Description The command takes long time to continue and it makes it seem like the build halted, so this adds an alert to mitigate this --> (3) COMMAND: fakeroot dpkg-deb -b -Znone /armbian/.tmp/work-cfd2d6ad-1f9b-473e-80e7-cbcf9d157c68/uboot-Bd1Ms /armbian/output/packages-hashed/gl> dpkg-deb: building package 'linux-u-boot-sipeed-lichee-pi-4a-current' in '/armbian/output/packages-hashed/global/linux-u-boot-sipeed-lichee-pi-4> --> (372) INFO: Built u-boot deb OK [ linux-u-boot-sipeed-lichee-pi-4a-current 2022.07-Se092-P0000-H6f49-V9cb9-B9963-R448a ] Jira reference number [AR-9999] How Has This Been Tested? Builds on my end Checklist: [X] My code follows …
-
utils-dpkgdeb: fix wrong DEBIAN/md5sums generation remove the prefix, otherwise a temporary path is included don't include DEBIAN/* files themselves AR-1714 View the full article
-
Description Some users reported bluetooth not working sometimes after reboot. Turns out that sometimes hciattach binary that we use segfaults during reboot. Replacing the binary with the one present in orangepi_build repository as it seems it solves the issue. 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 the user by rebooting their device 5 times. Bluetooth worked fine consistently after every reboot. Checklist: [ ] My code follows the style guidelines of this project [ ] I have performed a self-review of my own code [ ] I have commented my cod…
-
Description On devices using uwe5622 wireless, a kernel warn message and corresponding stacktrace is shown in dmesg for incorrect netdev-dev_addr. 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] Tested that warning message is gone on Orange Pi 3 LTS when booted with a kernel with this patch applied and that wireless 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 ha…
-
Description display armbian-install command only up to one day and if armbian-install was not run yet. hide displaying BASH shell at first login when this is the only option (minimal images). De-clutter 1st login screen. add variable INSTALLED=true to /etc/armbian-image-release indicating armbian-install was executed. How Has This Been Tested? Manual run. Checklist: [x] My code follows the style guidelines of this project [x] I have performed a self-review of my own code [x] I have commented my code, particularly in hard-to-understand areas [x] My changes generate no new warnings View the full article
-
Description UX improvements. View the full article
-
The 3rd revision of the patch has been applied upstream. https://lore.kernel.org/linux-wireless/87cyvqsabo.fsf@kernel.org/T/#t I've been using this revision for about week now and all seems 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 in downstream modules View the full article
-
This does not affect the downloaded ready-made ROOTFS, but the new compression value dramatically increased the process time (2-4 times) for user configurations. Adding a variable indicating the compression ratio will make it easy to select the desired value according to the conditions of use of the assembly system. By default, the previous value is set, for a mass build (which is executed from command scripts), it is easy to add any value of the maintainer's choice and will allow you to maintain a high build speed for custom versions that are usually executed on conventional ARM devices with low performance. View the full article
-
Description Due to reports of possible corruption in images, we need to implement more checks. Jira reference number AR-1236 How Has This Been Tested? Not working yet. Just POC. 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 For some weird reason, vim1s's kernel is extremely sensitive to gzipped initramfs image and it fails to load the same. For this reason, we had a pre_update_initramfs hook to change the initramfs compression algorithm from gzip to xz. But it turns out armbian-bsp-cli package has a well hidden pre-install script that changes compression to gzip if armbian-bsp-cli package is upgraded. This PR moves the compression change logic from previously added pre_update_initramfs hook to postinst script of armbian-bsp-cli. This way we can provide the value from getting overwritten and hence fix the upgrade failure. Jira reference number AR-1976 How Has This Been Tested? …
-
Description The u-boot was tied to a specific tag. Now I am setting it to branch so that updates can be directly pulled into Armbian as well. Also removed a patch that since has been merged into the upstream repository and rebased the patches. The compilation of u-boot used to crash the docker desktop on my macbook, so included a fix for that as well. 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=khadas-vim4 BRANCH=legacy u-boot Checklist: Please delete options that are not relevant. [ ] My code follows the style guidelines of this pro…
-
Description When booting from UHS-I cards on VIM4 and VIM1S, mine was Samsung EVO Plus card (MB-MC64KA), booting only worked 1 out of 5 reboots. Other times the device either tried booting from EMMC or from SPI flash. The following logs appear when booting doesn't work from sdcard mmc0 is current device sd: resp crc error, cmd17, status=0x1ff2400 ** Can't read partition table on 0:0 ** sd: resp crc error, cmd17, status=0x1ff2400 ** Can't read partition table on 0:0 ** ** Invalid partition 1 ** Using git bisect brought me to bfa451f commit and reverting the same solves the issue. Booting now works reliably from SD card every time I restart the same. Jira reference numbe…
-
Description Refresh kernel config to match fenix 1.6.4. This enables CONFIG_W1_SLAVE_THERM which was enabled on fenix as well. On bookworm, and also possibly on newer version of ubuntu, systemd starts all of the services present on first boot. Making the /etc/machine-id file empty ensures that machine id is still initialized on first-boot, while other services are not started automatically. This also seems to be observed by alex3d as well as reported in #6264 . However I was not able to reproduce the same issue on any of the other boards I have. Hence I have currently only handled it for meson-s4t7 family. This also makes the previous hack of masking chrony-wait.service …
-
Description Add bluetooth support for Khadas VIM1S and VIM4. Jira reference number AR-1917 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 scanning for nearby bluetooth devices works on VIM1S [X] Tested scanning for nearby bluetooth devices works on VIM4 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 depe…
-
Description As per the title. Allows using emmc for boot partition and nvme or usb for root partition when installing via armbian-install. How Has This Been Tested? [X] Created and booted image on VIM1S with emmc+USB combo 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 Add support to build VIM1S/VIM4 images on arm64 platform. Currently only x86_64 platform was supported as build host as the gcc-linaro-aarch64-elf compiler version 7.3.1-2018.05 was not available for aarch64 platform. I have built the compiler myself on vim4 using the commands given here How Has This Been Tested? [X] Compiled u-boot for VIM1S and VIM4 [X] Created a minimal bookworm image for VIM1S and booted on the same 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] My changes generate no new warnings [ ] Any dep…
-
Description Set correct video firmware based on the device being used. Fixes - https://forum.khadas.com/t/ffmpeg-and-hardware-h264-decode/19033/24 How Has This Been Tested? Please describe the tests that you ran to verify your changes. Please also note any relevant details for your test configuration. [X] Checked that the preload service starts correctly on vim4 and video_code.bin file points to correct firmware file. 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 gen…
-
Description Same as #6588 for v24.05 branch View the full article
-
Description Some high-resolution monitors (QHD/4K) will not output the desktop, and will enter sleep mode, directly after booting up an Armbian 23.8.1 desktop image and completing the initial setup questions. When such a monitor is attached, the kernel will auto-detect the SimpleDRM graphics driver, which is then prioritized over the Panfrost graphics driver. However, SimpleDRM outputs to a virtual output, while Panfrost outputs to the actual HDMI port. This causes the monitor to not receive any data. By blacklisting the simpledrm kernel module, Panfrost will take care of accelerated graphics (for any monitor) by default. Advanced users can still access simpledrm if req…
-
Set fan max speed to kick in at 65C. This keeps the unit roughly at 70C or lower, when pusing all cores for an extended period of time. 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 Forgot to add this to the script linter at PR. Jira reference number AR-1399 View the full article
-
Description Bug fix View the full article
-
Description Run apt update or it will fail to install dependencies. Jira reference number AR-1405 How Has This Been Tested? [x] Manual run View the full article
-
Description Some has this package dependency, some not. This makes sure that PPA is always installed. Jira reference number AR-1405 How Has This Been Tested? [x] Test build 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 Each family should build the same 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] ./compile.sh kernel BOARD=armsom-sige5 BRANCH=vendor DEB_COMPRESS=xz KERNEL_CONFIGURE=no KERNEL_GIT=shallow 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…
-
Description Copy missing common.mk for build Comment undefined RTW_WARN_LMT Fix wrong dir name in Makefile Remove sed CONFIG_PLATFORM_SPACEMIT for bpif3 because source code has alraedy enabled it, and fix sed CONFIG_PLATFORM_ARM_ROCKCHIP for 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 kernel BOARD=armsom-sige5 BRANCH=vendor DEB_COMPRESS=xz KERNEL_CONFIGURE=no KERNEL_GIT=shallow [x] wifi works on armsom sige5 Checklist: Please delete options that are not relevant. [x] My code follows the style guidelines of this project [x] I …
-
Description In an effort to reduce wifi driver burdens AR-1745, I went through the 6.10 kernel to check if any third party wifi drivers can be removed. The following drivers are part of the mainline kernel as of 6.10: RTL8723CS (driver: RTW88) RTL8811CU and RTL8821C (driver: RTW88) RTL8192EU (driver: RTL8XXXU) To give them some more time in the oven, use them not from 6.10 but from 6.11 onwards. I went through the Armbian forums, Atlassian and GiHub issues to see if anyone had used those drivers for these chips in the past and had reported issues. But I haven't found anything yet. RTL8723DS is also supported by RTW88, but I have not touched that driver since it is st…
-
Description Add windows dev kit 2023 support Jira reference number [AR-9999] How Has This Been Tested? Tested on windows dev kit 2023 [X] installed on sd card and device is booting fine 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 RK3588S board. Device Tree and Uboot from @stvhay WIP draft PR for commentary View the full article
-
DMESG; https://paste.debian.net/1308388/ Wifi / Bluetooth patrick@bananapim4zero:~$ ip a 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host noprefixroute valid_lft forever preferred_lft forever 3: wlx9803cf623b3f: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 98:03:cf:62:3b:3f brd ff:ff:ff:ff:ff:ff inet 10.0.0.172/24 brd 10.0.0.255 scope global dynamic noprefixroute wlx9803cf623b3f …
-
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.s…
-
Description Add script to generate CODEOWNERS How Has This Been Tested? [X] Run and check CODEOWNERS 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 [X] Any dependent changes have been merged and published in downstream modules View the full article
-
This skips all git checkout, patching, configuring and cleaning when USE_EXISTING_KERNEL_TREE=yes is passed. This can be useful when doing kernel development by making changes directly to the kernel sourcetree in cache/sources, while still allowing to use the compile.sh to use the same compilation commands, deb package building, ccache, etc. It is also useful when bisecting a kernel issue. Can be used something like this: USE_EXISTING_KERNEL_TREE=yes ./compile.sh default kernel To produce a kernel deb in a few minutes ready to be installed on a device. This is mostly a proof of concept to explore the usecase. In particular: I am not happy with the USE_EXISTING_KERN…
-
Googulator's midline kernel repo w/ monka's kernel config 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. GitHub issue reference: 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) [ ] …
-
Description See title. This fixes kernel compilation for 6.8.2 How Has This Been Tested? [x] Apply wireless patches to rockchip64-edge (which is 6.8) 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 Due to crypto policy update, apt now (since v2.7.13, see the commit) requires repositories to be signed using one of the following public key algorithms: RSA with at least 2048-bit keys Ed25519 Ed448 Affected: Ubuntu Oracular when adding Mesa PPA. More info https://ubuntuhandbook.org/index.php/2024/04/workaround-apt-warning-signature-key-uses-weak-algorithm/ Jira reference number AR-2359 How Has This Been Tested? [x] https://github.com/armbian/os/actions/runs/9434613892 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 a…
-
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 on unsupported desktop. Found due better logging in next. View the full article
-
WSL2 "boards" wsl2-x86/wsl2-arm64 with current (6.1.y) and edge (6.6.y) kernels with Microsoft patches WSL2 "boards" wsl2-x86/wsl2-arm64 with current (6.1.y) and edge (6.6.y) kernels with Microsoft patches tl,dr: add 4 small-ish UEFI-like kernels, with Microsoft patches & fixes, for use with Microsoft WSL2 on x86/arm64 and 6.1.y/6.6.y the boards are UEFI derivatives, using a common microsoft vendor include to modify KERNELPATCHDIR/LINUXFAMILY (for now, we don't want those patches in regular UEFI builds / .debs) disable EXTRAWIFI (kernel is for a VM, will never have wifi so doesn't need any drivers) LINUXCONFIG, so we can use Microsoft's own monolithic kernel, re…