Skip to content
View in the app

A better way to browse. Learn more.

Armbian Community Forums

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

SBC News

Atom feed, Pull requests awaiting review and other tech news

  1. Description Found we had cvbs support for allwinner H3 for current kernel. It had bits to make it working for H5 as well with only thing missing was the overlay to enable the it. Hence added the overlay for H5. Also as the patch was missing in edge kernel, added 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] Created a server image for OrangePi Prime and attached a CVBS/AV display to it. The console was also shown on the AV monitor. Checklist: [ ] My code follows the style guidelines of this project [ ] I have performed a self-review of my own cod…

    • Reputation Points

    • 0 replies
    • 716 views
  2. kernel/memoize: allow customizing memoize's default TTL of 3600 seconds; allow customizing kernel TTL via KERNEL_GIT_CACHE_TTL kernel/memoize: allow customizing memoize's default TTL of 3600 seconds; allow customizing kernel TTL via KERNEL_GIT_CACHE_TTL View the full article

    • Reputation Points

    • 0 replies
    • 692 views
  3. Description Bumping Khadas vim1s and vim4 kernel to 5.15. This seems to resolve the display issue on cinnamon, but this seems to have the same edid parsing based monitor filtering and hence some monitors are back to not working. I am working on figuring that out and will raise a separate PR for that later. This also solves the issue where disconnecting wifi was raising kernel oops How Has This Been Tested? Please describe the tests that you ran to verify your changes. Please also note any relevant details for your test configuration. [X] Booted on vim1s and vim4 Checklist: [ ] My code follows the style guidelines of this project [ ] I have performed a self-review of …

    • Reputation Points

    • 0 replies
    • 804 views
  4. Description This however only works for selected monitors with 1920x1080 and 4K resolutions. Also display seems to render extremely slowly. If the monitor is turned off and then on or is disconnected and reconnected while Armbian is running, monitor is not detected until a device reboot is performed. All of these however seems to be Khadas's kernel/u-boot limitations 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 attaching vim1s to samsung's 1920x1080 monitor [X] Rpardini tested on 4k display Checklist: [ ] My code follows the style guidelines of th…

    • Reputation Points

    • 0 replies
    • 924 views
  5. Description This fixes montior not working after its turned off and on again. This also helps getting the monitors working that doesn't work by default by setting hdmimode=1080p60hz and outputmode=1080p60hz in boot/armbianEnv.txt file. The fix is based on hdmitx21 commit used on vim4. The same change was missing for hdmitx20 that is used on vim1s. 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 on vim1s. Monitor hotplug works. Non-working monitor now works with manual configuration Checklist: [ ] My code follows the style guidelines of this project […

    • Reputation Points

    • 0 replies
    • 814 views
  6. Khadas VIM3/VIM3L u-boot 23.07-rc4 + SPI-NOR/MTD booting support (with old FIP blobs) khadas-vim3: bump u-boot to 2023.07-rc4, add KBI support for easy PCI/USB3 switching this introduces the v2023.07 u-boot patch directory, with the boot-usb-nvme-scsi-first patch rebased add myself as BOARD_MAINTAINER khadas-vim3: introduce SPI-NOR/MTD u-boot build, using old(er) FIP blobs move FIP signing code from meson-g12b.conf's uboot_custom_postprocess() to the board's own post_uboot_custom_postprocess hook fetch a secondary FIP blob repo at a revision with working FIP blobs for SPI (see https://github.com/LibreELEC/amlogic-boot-fip/pull/10) implement post_uboot_custom_postproc…

    • Reputation Points

    • 0 replies
    • 1.3k views
  7. Description Khadas Edge 2 images has been shipped without Uboot and it may cause some problems like not-booting when eMMC and SPI is empty. This PR adds vendor's uboot to Edge 2 images. I've also added BL32 blob because the board doesn't boot when SPI has BL32 blobs and SD card doesn't have. cc @rpardini @viraniac How Has This Been Tested? [x] SPI + SD card [ ] Empty SPI + SD card [ ] SPI + eMMC [ ] Empty SPI + eMMC 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 gener…

    • Reputation Points

    • 0 replies
    • 898 views
  8. Description Rename audios like other rk3588 boards. 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 r…

    • Reputation Points

    • 0 replies
    • 836 views
  9. I have started this months ago, but due to high demand from other subjects (armbian-next) haven't had time to finish. What I did here was take Khadas tree (.66) and rebase it on top of rk3.4/Radxa tree (.110) for the rock-5b, similar to what was done for the OrangePi5. Some patches conflicted and I intervened (those are marked as intervention). This needs review, a board file, a developer with the new Khadas I/O board for UART, and some luck, patience to fix my mistakes, and might just work. Who knows? If it's useless just bin this... There's two patch files, one with stuff I deemed "required" and other with stuff "might be nice". The MCU stuff of Khadas is heavily ent…

    • Reputation Points

    • 0 replies
    • 1k views
  10. khadas-vim3: bump to u-boot v2024.01; boot-usb-first patch in board folder khadas-vim3: bump to u-boot v2024.01; boot-usb-first patch in board folder patch is slightly different for 2024.01 View the full article

    • Reputation Points

    • 0 replies
    • 771 views
  11. khadas-vim3: fix stray closing brace in board file khadas-vim3: fix stray closing brace in board file a stray closing brace, meant for the function, that ends up doing the wrong config change View the full article

    • Reputation Points

    • 0 replies
    • 756 views
  12. CHANGE: This version tries to boot SD first (thus SD -> USB -> NVMe -> eMMC); before it would boot USB before SD as Armbian u-boot is possibly deployed to SPI, try to make as compatible as possible; eg enable squashfs support enable setexpr and fileenv, used by HAOS HAOS already has support for booting VIM3 from NVMe: https://github.com/home-assistant/operating-system/pull/3784 borrowed fileenv patch from v2025.01 to .04 Similar treatment that odroidm1 got in https://github.com/armbian/build/pull/7769 note: I will be leaving my VIM3 behind in the other side of the globe, so this is my last chance to test View the full article

    • Reputation Points

    • 0 replies
    • 817 views
  13. khadas-vim3/khadas-vim3l: bump to u-boot v2023.10; single-FIP for both SD/eMMC and SPI u-boots khadas-vim3/vim3l: back to single-FIP for both SD/eMMC and SPI u-boots also use flashcp to write to mtd khadas-vim3: bump to u-boot v2023.10; boot-usb-first patch now only in board folder drop kbi patch khadas-vim3l: bump to u-boot v2023.10; boot-usb-first patch now only in board folder drop kbi patch View the full article

    • Reputation Points

    • 0 replies
    • 737 views
  14. khadas-vim3/khadas-vim3l: u-boot v2024.01: enable more compression, kaslr, and led config options via hook khadas-vim3l: bump to u-boot v2024.01; boot-usb-first patch in board folder patch is slightly different for 2024.01 khadas-vim3l: u-boot v2024.01: enable more compression, kaslr, and led config options via hook khadas-vim3: u-boot v2024.01: enable more compression, kaslr, and led config options via hook View the full article

    • Reputation Points

    • 0 replies
    • 700 views
  15. khadas-vim3l/khadas-vim3: enable networking cmds in u-boot khadas-vim3l: enable networking cmds in u-boot khadas-vim3: enable networking cmds in u-boot View the full article

    • Reputation Points

    • 0 replies
    • 793 views
  16. Work in progress, submitted for brainstorm and coordination prior to merge request and stuff Peer-reviews appreciated just don't treat it as ready to merge thing, most of the stuff are my tags to figure out :p View the full article

    • Reputation Points

    • 0 replies
    • 721 views
  17. Description pull_request_review might not grant required permissions. pull_request_target runs in the context of the base repository (i.e., the one the PR is targeting), giving the correct access to secrets and permissions. 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 warning…

    • Reputation Points

    • 0 replies
    • 774 views
  18. Description GitHub Actions security feature. https://github.com/crazy-max/ghaction-github-labeler/issues/184 How Has This Been Tested? We use this way on armbian/os https://github.com/armbian/os/blob/main/.github/workflows/labeler.yml View the full article

    • Reputation Points

    • 0 replies
    • 790 views
  19. Description Improve labelling action process. How Has This Been Tested? Tested on private repo. Checklist: [x] My code follows the style guidelines of this project [x] My changes generate no new warnings View the full article

    • Reputation Points

    • 0 replies
    • 1k views
  20. Description Simple change to h616 OrangepiZero2 LED's functioning. Resembles Legacy kernel behavior, symbolically signifies more active development OrangepiZero2 How Has This Been Tested? [x] Test A compiled and booted with expected result [ ] Test B Checklist: [x] 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 [x] Any dependent changes have been merged and published in downstream modules View the full article

    • Reputation Points

    • 0 replies
    • 716 views
  21. legacy kernel custom uImage/etc via new pre_package_kernel_image hook; fixes for orangepizero2/sun50iw9/legacy kernel: introduce new hook pre_package_kernel_image; show vmlinuz file magic before/after hook; add -HK hook hash to kernel artifact version arch configs (all): default, but do not overwrite, KERNEL_IMAGE_TYPE/KERNEL_INSTALL_TYPE/etc: allow board/family to set first orangepizero2/sun50iw9/legacy: implement pre_package_kernel_image hook to convert vmlinuz to uImage manually; fix legacy u-boot build sourceaddr 0x40008000 was found in Xunlong's legacy kernel source squashed into a huge commit. Thanks, Xunlong! bring busybox dependency with inline hook for legacy u…

    • Reputation Points

    • 0 replies
    • 791 views
  22. Description For bootable/workable kernel, dtb is necessary. How Has This Been Tested? [X] Build [X] Run apt show linux-image-current-meson to check whether dtb is a dependency. [X] Run apt purge --autoremove linux-image-current-meson to check if dtb will be removed automatically. Checklist: [ ] 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

    • Reputation Points

    • 0 replies
    • 859 views
  23. Description This address https://github.com/armbian/build/pull/4189#issuecomment-1279676914 How Has This Been Tested? [X] Build Checklist: [ ] My code follows the style guidelines of this project [X] I have performed a self-review of my own code [ ] I have commented my code, particularly in hard-to-understand areas [ ] I have made corresponding changes to the documentation [X] My changes generate no new warnings [ ] Any dependent changes have been merged and published in downstream modules View the full article

    • Reputation Points

    • 0 replies
    • 864 views
  24. lib & config: give shellcheck directions (to /dev/null for dynamic, to repo-relative path for static) for all sourced references lib & config: give shellcheck directions (to /dev/null for dynamic, to repo-relative path for static) for all sourced references in preparation for tightening the shellcheck severity level it needs to be able to follow all sources; dynamic ones are ignored, static ones need root-relative prefix View the full article

    • Reputation Points

    • 0 replies
    • 828 views
  25. lib: drop old boot_logo code; keep png/gif as they're used for plymouth lib: drop old boot_logo code; keep png/gif as they're used for plymouth origins of what's being dropped: https://github.com/armbian/build/pull/2065 View the full article

    • Reputation Points

    • 0 replies
    • 712 views
  26. Description Make it possible to toggle EXTRAWIFI as a way to disable all extra network patches. For patches for one or more chipsets, user can use KERNEL_DRIVERS_SKIP 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 EXTRAWIFI=no and EXTRAWIFI=yes, checked that patches gets skipped when EXTRAWIFI=no is set to no and gets applied by default or when EXTRAWIFI=yes Checklist: [X] 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 […

    • Reputation Points

    • 0 replies
    • 720 views
  27. /bin/bash doesn't exists on Nix-like Operating systems + it's malpractice to hardcode binary path as it will depend on file system hierarchy This solution replaces that to use environment for binaries + adds option to change Bash binary during runtime through using BASH variable View the full article

    • Reputation Points

    • 0 replies
    • 669 views
  28. Description licheepi-4a: add a .wip for Sipeed LicheePi 4A board The u-boot of LicheePi 4A can be updated without the need to flash the system. Users can manually update it according to the instructions provided by Sipeed's wiki when needed. The opensbi used in LicheePi 4A is not packaged within u-boot using a fit image. Therefore, it is stored in the repository as a binary file. During startup, LicheePi 4A requires loading audio and aon firmware. These two files will also be stored in the repository in binary format. 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 configuratio…

    • Reputation Points

    • 0 replies
    • 787 views
  29. Got the board too and doing OSHW development for the platform View the full article

    • Reputation Points

    • 0 replies
    • 861 views
  30. See rationale on https://www.shellcheck.net/wiki/SC2086 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? Blind edit 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 modu…

    • Reputation Points

    • 0 replies
    • 728 views
  31. Description When boards are changes listen only to branch "main" as we don't want to trigger this elsewhere. Jira reference number AR-1664 How Has This Been Tested? No need View the full article

    • Reputation Points

    • 0 replies
    • 781 views
  32. Description I'm trying to generate a debian iso with armbian's kernel, but live-build keep installing linux-image-rt-arm64. I find it as rec dependency of wireguard-tools. And both linux-image-rt-arm64 from debian and linux-image-generic from ubuntu are providing 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] ./compile.sh kernel BOARD=rock-5b BRANCH=vendor DEB_COMPRESS=xz 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 commente…

    • Reputation Points

    • 0 replies
    • 737 views
  33. Description linux-rk3399-legacy.conf is unused. Remove it. How Has This Been Tested? No references to file found in build system, only to linux-rockchip64-legacy.conf, which is for the same kernel. 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

    • Reputation Points

    • 0 replies
    • 714 views
  34. 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…

    • Reputation Points

    • 0 replies
    • 1.7k views
  35. linux-rk35xx-legacy.config: enable VHOST_NET and others for hosting VM's linux-rk35xx-legacy.config: enable VHOST_NET and others for hosting VM's View the full article

    • Reputation Points

    • 0 replies
    • 879 views
  36. linux-rk35xx-vendor: enable CONFIG_KPROBES linux-rk35xx-vendor: enable CONFIG_KPROBES for tetragon & co View the full article

    • Reputation Points

    • 0 replies
    • 999 views
  37. linux-rockchip-rk3588-6.11.config: enable CONFIG_INPUT_PWM_BEEPER=m linux-rockchip-rk3588-6.11.config: enable CONFIG_INPUT_PWM_BEEPER=m mostly for the cm3588 nas; mainline kernel has a compatible = "pwm-beeper"; buzzer impl on pwm8 see https://github.com/torvalds/linux/blob/3d5f968a177d468cd13568ef901c5be84d83d32b/arch/arm64/boot/dts/rockchip/rk3588-friendlyelec-cm3588-nas.dts#L63-L68 View the full article

    • Reputation Points

    • 0 replies
    • 1.1k views
  38. Description The board config is only contain some variable assignments, so it should be safe to be sourced twice. If it doesn't, we can fix easily. With this, we can overwrite the family config. So we don't need to check BOARD in family config ( e.g. the u-boot config ) . Just define it in board config. How Has This Been Tested? [ ] Build and run test for all board Checklist: [ ] 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 ch…

    • Reputation Points

    • 0 replies
    • 800 views
  39. I am "almost" giving up on the "bright black" == "gray" thing. There's enough bad default themes out there, and not the first time people (rightfully) complained... ref #4865 View the full article

    • Reputation Points

    • 0 replies
    • 741 views
  40. argument list too long detected by @amazingfate also is in general a bit leaky, people are developing and changes "leak" into logs with this same info could be better obtained by consolidating the logs (docker/build) into a single one later View the full article

    • Reputation Points

    • 0 replies
    • 649 views
  41. Description longanpi-4b: add support for Sipeed LonganPi 4B. Add virt drivers for sun55iw3-syterkit. 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

    • Reputation Points

    • 0 replies
    • 931 views
  42. Description We have some Python scripts now so we need to move that out Jira reference number AR-1588 How Has This Been Tested? [x] 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] My changes generate no new warnings View the full article

    • Reputation Points

    • 0 replies
    • 857 views
  43. Description During testing new test procedure for automated kernel switching I have noticed that some boards sometimes hangs in the test process. It looks like it is possible to mitigate this by lowering CPU clock. IMO it is good enough if we do this in user space. Jira reference number AR-1797 How Has This Been Tested? [ ] Running smoke tests 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 View the full article

    • Reputation Points

    • 0 replies
    • 645 views
  44. main-config.sh: workaround: set the default ARCH to arm64 (replacing armhf) main-config.sh: workaround: set the default ARCH to arm64 (replacing armhf) armhf was disabled for some releases and now we get spurious failures building certain artifacts (firmware) Signed-off-by: Ricardo Pardini ricardo@pardini.net View the full article

    • Reputation Points

    • 0 replies
    • 988 views
  45. Description Support for mainline for Rock 5B. Currently working is just EMMC. There is also ethernet support, but rock 5b uses PCIe for ethernet. How Has This Been Tested? Booted my Rock 5B fine, but have no EMMC, so the init could not mount the root drive. If someone can help with the testing... 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 t…

    • Reputation Points

    • 0 replies
    • 858 views
  46. mainline-kernel: bump to 6.10-rc7 mainline-kernel: bump to 6.10-rc7 just rockchip-rk3588 for now rockchip-rk3588 / edge: rebase onto 6.10-rc7 win: notice how one can actually spot relevant changes now case in point, 1022-arm64-dts-rockchip-support-poweroff-on-rock-5a.patch -- will drop it in separate commit rockchip-rk3588 / edge: drop patch that landed in 6.10-rc7 1022-arm64-dts-rockchip-support-poweroff-on-rock-5a.patch landed https://github.com/torvalds/linux/commit/d05f7aff7ac23884ed9103a876325047ff9049aa View the full article

    • Reputation Points

    • 0 replies
    • 867 views
  47. Update maintainers synched from the database View the full article

    • Reputation Points

    • 0 replies
    • 833 views
  48. Update maintainers synched from the database View the full article

    • Reputation Points

    • 0 replies
    • 798 views
  49. Update maintainers synched from the database View the full article

    • Reputation Points

    • 0 replies
    • 692 views
  50. Update maintainers synched from the database View the full article

    • Reputation Points

    • 0 replies
    • 670 views
  51. Update maintainers synched from the database View the full article

    • Reputation Points

    • 0 replies
    • 869 views
  52. Update maintainers synched from the database View the full article

    • Reputation Points

    • 0 replies
    • 708 views
  53. Description https://github.com/torvalds/linux/commit/4c7be57f2772c8ce4e1e43c6a79b8f8d401a4795 linux kernel make install by default will install the old non-compressed one. Then now, it will product vmlinux not vmlinuz lib/functions/compilation/kernel-debs.sh will not found vmlinuz in boot dir View the full article

    • Reputation Points

    • 0 replies
    • 689 views
  54. Description Since difference between desktop and CLI overhead is gone, we can remove this check and make both on the same value. Also previously overhead was not enough due to added Plymouth package. Jira reference number AR-1330 How Has This Been Tested? [x] Build test CLI images https://github.com/armbian/scripts/actions/runs/3052426276 [x] Build and boot Rpi4 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 dependen…

    • Reputation Points

    • 0 replies
    • 847 views
  55. Without this, when mkimage fails (for example because the boot partition is too small), install.log shows an error like: mkimage: Write only 16310208/17794920 bytes, probably no space left on the device But this does not terminate the build, so the compile script shows no error and an image is generated, but it is unbootable. This runs the script with -e, so when mkimage fails, the script fails, which makes update-initramfs fail, which makes the build fail. 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 for Orange Pi PC with BOOTFS_TYPE="fat" …

    • Reputation Points

    • 0 replies
    • 965 views
  56. Description This fixes the readability of colorized output of compile.sh when running on a terminal with a light background. It uses the COLORFGBG environment variable similarly to how the ip(8) command does. Before: After: How Has This Been Tested? Compile command: ./compile.sh BOARD=nanopim1 RELEASE=bookworm KERNEL_CONFIGURE=no BUILD_MINIMAL=yes PREFER_DOCKER=no BRANCH=edge BUILD_ONLY=u-boot [X] Run in Konsole on a light background (COLORFGBG=0;15) [X] Run in Konsole on a light background (COLORFGBG unset) [X] Run in Konsole on a dark background (COLORFGBG=15;0) [X] Run in Konsole on a dark background (COLORFGBG unset) [X] Visually inspect the results Checkli…

    • Reputation Points

    • 0 replies
    • 1.1k views
  57. Description fix build error with new compiler update uboot to v2024.04 ras314: fix sd-card regulator error How Has This Been Tested? [x] Build and Boot CLI/Gnome image on mba8mp [x] Build and Boot CLI/Gnome image on mba8mp-ras314 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

    • Reputation Points

    • 0 replies
    • 785 views
  58. MBa8MPxL: rework uboot patches Description The U-Boot Repo get some updates. This reworks the patches depending on these updates. How Has This Been Tested? [x] Build images for mba8mp-ras314 and mba8mpxl with new patches [x] Boot test "bookworm_current" mba8mp-ras314 [x] Boot test "bookworm_current" mba8mpxl 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

    • Reputation Points

    • 0 replies
    • 844 views
  59. Description a new atf version is now available on GitHub (v2.10) the new version is compatible with GCC13 Jira reference number AR-2441 How Has This Been Tested? [x] Build images for mba8mp-ras314 and mba8mpxl with new patches [x] Boot test "bookworm_current" mba8mp-ras314 [x] Boot test "bookworm_current" mba8mpxl NOTICE: BL31: v2.10.0 (release):armbian NOTICE: BL31: Built : 08:58:44, Aug 26 2024 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

    • Reputation Points

    • 0 replies
    • 725 views
  60. test all model use media View the full article

    • Reputation Points

    • 0 replies
    • 825 views
  61. Description ARM_PSCI_CPUIDLE is not enabled in media boardfamily previousely. [ 3.141431] psci_checker: cpuidle not available on CPU 0, ignoring [ 3.141987] psci_checker: cpuidle not available on CPU 1, ignoring [ 3.142539] psci_checker: cpuidle not available on CPU 2, ignoring [ 3.143091] psci_checker: cpuidle not available on CPU 3, ignoring [ 3.143642] psci_checker: cpuidle not available on CPU 4, ignoring [ 3.144229] psci_checker: cpuidle not available on CPU 5, ignoring Enabling CPU idle can lower CPU power at low load, as well as killing these warning messages. How Has This Been Tested? [x] boot normally (testers x2) [x] stable at running Chec…

    • Reputation Points

    • 0 replies
    • 855 views
  62. Description media: fix firefly-rk3399 mini-pcie slot. Problem description: The 3G/4G module is not available on the firefly-rk3399. According to the schematic, the "MINI PCIE" on the firefly-rk3399 only has USB2 functionality. Comparing with the official kernel device tree, it is found that the vcc3v3-3g-regulator power supply node is missing. However, the pins used by this node conflict with the leds node referenced in the kernel device tree for roc-rk3399-pc. This node is redundant in firefly-rk3399, so it is defined as "node deletion". Summary of modifications: Added vcc3v3-3g-regulator power supply node. Defined node deletion. How Has This Been Tested? [x] Su…

    • Reputation Points

    • 0 replies
    • 1.3k views
  63. mekotronics 3588: add SRC_CMDLINE, for use with u-boot-menu extension mekotronics 3588: add SRC_CMDLINE, for use with u-boot-menu extension does nothing otherwise View the full article

    • Reputation Points

    • 0 replies
    • 626 views
  64. mekotronics 3588: fix entering RK LOADER mode by keeping the RECOVERY button pressed during boot mekotronics 3588: fix entering RK LOADER mode by keeping the RECOVERY button pressed during boot those patches are a mess, hopefully I'll find time to squash soon mekotronics 3588: squash u-boot patches same as before but not touching the same file twice+ View the full article

    • Reputation Points

    • 0 replies
    • 918 views
  65. mekotronics rk3588: rebase & unify u-boot patches; restore attribution for one patch mekotronics rk3588: rebase & unify u-boot patches; restore attribution for one patch no functional changes, only a double patch I'd rather not have View the full article

    • Reputation Points

    • 0 replies
    • 700 views
  66. mekotronics-r58x-pro.wip: add new board Mekotronics R58X-Pro mekotronics-r58x-pro.wip: add new board Mekotronics R58X-Pro View the full article

    • Reputation Points

    • 0 replies
    • 815 views
  67. mekotronics: rk3588: u-boot: borrow patch to fix build on newer gcc mekotronics: rk3588: u-boot: rewrite u-boot patches, no changes rewritten against 609a77ef6e99c56aacd4b8d8f9c3056378f9c761 - a specific commit in radxa's next-dev mekotronics: rk3588: u-boot: borrow patch to fix build on newer gcc View the full article

    • Reputation Points

    • 0 replies
    • 780 views
  68. mekotronics: u-boot: join rockchip-rk3588's default u-boot-radxa-rk35xx scheme mekotronics: u-boot: join rockchip-rk3588's default u-boot-radxa-rk35xx scheme rebased 2 patches moved null patches for dts & defconfigs to dt / defconfig dirs rename defconfigs since we're at it; use board-specific only defconfigs re-saved View the full article

    • Reputation Points

    • 0 replies
    • 909 views
  69. 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…

    • Reputation Points

    • 0 replies
    • 1.3k views
  70. Description merge and remove special kernel config drop rk3568-odroid kernel family port DT from mainline 6.6 to rockchip64-current with a single patch No other changes, board is staging, probably will go to community maintained, should be safe to merge. Jira reference number AR-1737 How Has This Been Tested? [x] build and boot current 6.1 image [x] build and boot current 6.6 image 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 [x] Any dependent changes have been merged and published in downstream modules View the full article

    • Reputation Points

    • 0 replies
    • 712 views
  71. Description I just move config/kernel/linux-rockchip-rk3588-legacy.config to config/kernel/linux-rk35xx-legacy.config, and make them share the same family rk35xx. Now rk356x will use the same kernel rk3588 legacy is using. I tested the new kernel on my rock3a, working 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] Build legacy kernel of rock3a and rock5b, same result. [x] New kernel 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, parti…

    • Reputation Points

    • 0 replies
    • 1.2k views
  72. Description Bookworm is the latest stable release of debian from 2023, with mesa 22 in its repo, which will not support rk3588 panthor mainline gpu driver. I backported mesa 24.1.3 in obs: https://build.opensuse.org/project/show/home:amazingfate:mesa-bookworm-backport. And here is the instruction of updating mesa from obs's repo: https://software.opensuse.org//download.html?project=home%3Aamazingfate%3Amesa-bookworm-backport&package=libgl1-mesa-dri 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=rock-5b BRANCH=edge BUILD_MINIMAL=no DEB_…

    • Reputation Points

    • 0 replies
    • 3.1k views
  73. Description Ship images with Chromium v126 instead of v124 How Has This Been Tested? [x] VP9 and H264 works well with chromium and haven't caught any crash in various websites. 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

    • Reputation Points

    • 0 replies
    • 1.4k views
  74. Started by RSS Bot,

    Description Small tweak How Has This Been Tested? [X] Build, burn and run Checklist: [ ] My code follows the style guidelines of this project [X] I have performed a self-review of my own code [ ] I have commented my code, particularly in hard-to-understand areas [ ] I have made corresponding changes to the documentation [X] My changes generate no new warnings [ ] Any dependent changes have been merged and published in downstream modules View the full article

    • Reputation Points

    • 0 replies
    • 745 views
  75. BPI-CM4: Add support for the waveshare cm4-io-base-b https://www.waveshare.com/wiki/CM4-IO-BASE-B BPI-CM4: Enable usb support on waveshare baseboards via overlay BPI-SM1: Removed UART_B overlay. Short of it being an available option in the vendor kernel via overlay. I can't find any docs to support why that is. I feel it is safer that we just remove it. BPI-SM1: Add UART_A "pin-ctrl: cts rts" 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 …

    • Reputation Points

    • 0 replies
    • 707 views
  76. Description Removed lcd node when screen is not attached. Turns out the Khadas u-boot has some code hidden deep within pxe.c file to enable and disable lcd screen. As we don't use extlinux for vim1s and vim4, that doesn't get executed for us leaving the device to detect ghost screens. Hence copied the code to bootscript in order to disable the lcd screens when they are not really present. This makes the vim4 and vim1s a lot more responsive. Also fixes issue where we can't login to gnome because login screen was being rendered on non-existent lcd screen. Fixed issue that prevented armbian-bsp-cli package for meson-s4t7 family to uninstall because of the added /etc/initram…

    • Reputation Points

    • 0 replies
    • 844 views
  77. Description Fixed the compilation issue with new khadas u-boot. The fix is actually quite ugly. We are now compiling u-boot twice, once with gcc 11.4 and then with linaro toolchain v7.3.1. Also as Linaro's compiler is only available for x86 platform, uboot for these boards will not build on arm platforms. But I guess we have to live with it for now. 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 building uboot for khadas vim1s Checklist: [ ] My code follows the style guidelines of this project [ ] I have performed a self-review of my own code [ ] I ha…

    • Reputation Points

    • 0 replies
    • 884 views
  78. Description Turns out the Khadas u-boot has some code hidden deep within pxe.c file to enable and disable lcd screen. As we don't use extlinux for vim1s and vim4, that doesn't get executed for us leaving the device to detect ghost screens. Hence copied the code to bootscript in order to disable the lcd screens when they are not really present. This makes the vim4 and vim1s a lot more responsive. Also fixes issue where we can't login to gnome because login screen was being rendered on non-existent lcd screen. 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] Tes…

    • Reputation Points

    • 0 replies
    • 778 views
  79. Description The kernel headers package is not getting installed due to missing common_drivers/header_include.mk file. Jira reference number AR-2072 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 installing kernel headers on vim1s 24.02 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 chang…

    • Reputation Points

    • 0 replies
    • 762 views
  80. Description Fixed issue that prevented armbian-bsp-cli package for meson-s4t7 family to uninstall because of the added /etc/initramfs-tools/modules file. As this required custom code to be added in the postrm script of the package, I have added support for the same in armbian-bsp-cli package similar to how things worked for postinst script. 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 armbian-bsp-cli-vim4-legacy package uninstalls fine. Checklist: [ ] My code follows the style guidelines of this project [ ] I have performed a self-review of m…

    • Reputation Points

    • 0 replies
    • 823 views
  81. Description Bumped uboot and overlays to match Fenix 1.6.4 release. I also noticed that since my last PR, my u-boot patch to enable setexpr command was not getting applied. Turns out we were not handling patching if build_custom_uboot extension was being used. Hence moved the relevant code so that its used in both cases. How Has This Been Tested? Please describe the tests that you ran to verify your changes. Please also note any relevant details for your test configuration. [X] built and booted image for khadas-vim4 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, parti…

    • Reputation Points

    • 0 replies
    • 779 views
  82. Description Reworked u-boot compilation for meson-s4t7 to make sure we are following same process for u-boot compilation as Khadas. Now we are not compiling it twice like we were doing it before as mentioned in #6112. Added post install script in uboot with option to force upgrade the same. The code is based on what is being used in armbian-config's bootloader update code. Also moved tinkerboard specific code out to tinkerboards's config How Has This Been Tested? Please describe the tests that you ran to verify your changes. Please also note any relevant details for your test configuration. [X] Tested both vim1s and vim4 boots [X] Tested upgrade with using deb files. I…

    • Reputation Points

    • 0 replies
    • 860 views
  83. Description meson bump current to v6.1 edge to v6.2 How Has This Been Tested? [X] Build and run current [X] Build and run edge Checklist: [ ] My code follows the style guidelines of this project [X] I have performed a self-review of my own code [ ] I have commented my code, particularly in hard-to-understand areas [ ] I have made corresponding changes to the documentation [X] My changes generate no new warnings [ ] Any dependent changes have been merged and published in downstream modules View the full article

    • Reputation Points

    • 0 replies
    • 719 views
  84. Description bump edge to thirdparty linux-5.18-rc7 bump current to linux-5.15 change legacy back to LTS linux-5.10 edge and current enable NTFS3 driver. How Has This Been Tested? [X] Build [X] Run Checklist: [ ] My code follows the style guidelines of this project [X] I have performed a self-review of my own code [ ] I have commented my code, particularly in hard-to-understand areas [ ] I have made corresponding changes to the documentation [X] My changes generate no new warnings [X] Any dependent changes have been merged and published in downstream modules View the full article

    • Reputation Points

    • 0 replies
    • 898 views
  85. Description Remove some useless modules and enable some modules. 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 and run Checklist: [ ] My code follows the style guidelines of this project [X] I have performed a self-review of my own code [ ] I have commented my code, particularly in hard-to-understand areas [ ] I have made corresponding changes to the documentation [X] My changes generate no new warnings [ ] Any dependent changes have been merged and published in downstream modules View the full article

    • Reputation Points

    • 0 replies
    • 878 views
  86. Description meson: branch current and legacy support HDMI How Has This Been Tested? [X] Build and burn Checklist: [ ] My code follows the style guidelines of this project [X] I have performed a self-review of my own code [ ] I have commented my code, particularly in hard-to-understand areas [ ] I have made corresponding changes to the documentation [X] My changes generate no new warnings [ ] Any dependent changes have been merged and published in downstream modules View the full article

    • Reputation Points

    • 0 replies
    • 986 views
  87. Description meson: edge: bump to linux-6.3.y How Has This Been Tested? [X] Build [X] Burn and test Checklist: [ ] My code follows the style guidelines of this project [X] I have performed a self-review of my own code [ ] I have commented my code, particularly in hard-to-understand areas [ ] I have made corresponding changes to the documentation [X] My changes generate no new warnings [ ] Any dependent changes have been merged and published in downstream modules View the full article

    • Reputation Points

    • 0 replies
    • 768 views
  88. Description Switch back to mainline kernel. Use patch to support HDMI. How Has This Been Tested? [X] Build [X] Burn and test Checklist: [ ] My code follows the style guidelines of this project [X] I have performed a self-review of my own code [ ] I have commented my code, particularly in hard-to-understand areas [ ] I have made corresponding changes to the documentation [X] My changes generate no new warnings [ ] Any dependent changes have been merged and published in downstream modules View the full article

    • Reputation Points

    • 0 replies
    • 1k views
  89. Description meson: edge: Bump to v6.4 How Has This Been Tested? [X] Build [X] Burn and test Checklist: [ ] My code follows the style guidelines of this project [X] I have performed a self-review of my own code [ ] I have commented my code, particularly in hard-to-understand areas [ ] I have made corresponding changes to the documentation [X] My changes generate no new warnings [ ] Any dependent changes have been merged and published in downstream modules View the full article

    • Reputation Points

    • 0 replies
    • 1.6k views
  90. Description meson: edge: Bump to v6.6 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 [X] Burn and test Checklist: [ ] My code follows the style guidelines of this project [X] I have performed a self-review of my own code [ ] I have commented my code, particularly in hard-to-understand areas [ ] I have made corresponding changes to the documentation [X] My changes generate no new warnings [ ] Any dependent changes have been merged and published in downstream modules View the full article

    • Reputation Points

    • 0 replies
    • 672 views
  91. Description meson: Bump edge to v5.19 How Has This Been Tested? [X] Build and run Checklist: [ ] My code follows the style guidelines of this project [X] I have performed a self-review of my own code [ ] I have commented my code, particularly in hard-to-understand areas [ ] I have made corresponding changes to the documentation [X] My changes generate no new warnings [ ] Any dependent changes have been merged and published in downstream modules View the full article

    • Reputation Points

    • 0 replies
    • 724 views
  92. Description meson: Bump edge to v6.0 How Has This Been Tested? [X] Build and run Checklist: [ ] My code follows the style guidelines of this project [X] I have performed a self-review of my own code [ ] I have commented my code, particularly in hard-to-understand areas [ ] I have made corresponding changes to the documentation [X] My changes generate no new warnings [ ] Any dependent changes have been merged and published in downstream modules View the full article

    • Reputation Points

    • 0 replies
    • 701 views
  93. Description Enable some net modules for meson. How Has This Been Tested? [X] Build and run Checklist: [ ] My code follows the style guidelines of this project [X] I have performed a self-review of my own code [ ] I have commented my code, particularly in hard-to-understand areas [ ] I have made corresponding changes to the documentation [X] My changes generate no new warnings [ ] Any dependent changes have been merged and published in downstream modules View the full article

    • Reputation Points

    • 0 replies
    • 683 views
  94. Description Fix broken patches How Has This Been Tested? [X] Build [X] Burn to device and boot Checklist: [ ] My code follows the style guidelines of this project [X] I have performed a self-review of my own code [ ] I have commented my code, particularly in hard-to-understand areas [ ] I have made corresponding changes to the documentation [X] My changes generate no new warnings [ ] Any dependent changes have been merged and published in downstream modules View the full article

    • Reputation Points

    • 0 replies
    • 768 views
  95. Description meson: fix: Fail to register VCC_CORE regulator How Has This Been Tested? [X] Build [X] Burn and run Checklist: [ ] My code follows the style guidelines of this project [X] I have performed a self-review of my own code [ ] I have commented my code, particularly in hard-to-understand areas [ ] I have made corresponding changes to the documentation [X] My changes generate no new warnings [ ] Any dependent changes have been merged and published in downstream modules View the full article

    • Reputation Points

    • 0 replies
    • 848 views
  96. Description meson: legacy: bump to 5.10.155 How Has This Been Tested? [X] Build, burn and run Checklist: [ ] My code follows the style guidelines of this project [X] I have performed a self-review of my own code [ ] I have commented my code, particularly in hard-to-understand areas [ ] I have made corresponding changes to the documentation [X] My changes generate no new warnings [ ] Any dependent changes have been merged and published in downstream modules View the full article

    • Reputation Points

    • 0 replies
    • 589 views
  97. Description For Onecloud: Resort DTS node Fix slow ethernet uplink Update GPIO descriptions Corrent eMMC DTS node Enable USB0 OTG mode How Has This Been Tested? [X] Build and run Checklist: [ ] 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

    • Reputation Points

    • 0 replies
    • 1.1k views
  98. Description legacy was broken. Let's drop it since current and edge work well. How Has This Been Tested? Unnecessary. Checklist: [ ] My code follows the style guidelines of this project [X] I have performed a self-review of my own code [ ] I have commented my code, particularly in hard-to-understand areas [ ] I have made corresponding changes to the documentation [X] My changes generate no new warnings [ ] Any dependent changes have been merged and published in downstream modules View the full article

    • Reputation Points

    • 0 replies
    • 694 views
  99. meson64 / rockchip64 / uefi / rk3568-odroid: edge 6.6: bump to 6.6-rc7; rebase/rewrite patches for 6.6-rc7 meson64 / rockchip64 / uefi / rk3568-odroid: edge 6.6: bump to 6.6-rc7; rebase/rewrite patches for 6.6-rc7 View the full article

    • Reputation Points

    • 0 replies
    • 1.3k views
  100. meson64 / rockchip64 / uefi / rk3568-odroid: edge 6.6: bump to 6.6.y; rebase patches to v6.6(.0) meson64 / rockchip64 / uefi / rk3568-odroid: edge 6.6: bump to 6.6.y; rebase patches to v6.6(.0) View the full article

    • Reputation Points

    • 0 replies
    • 911 views

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.