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.

RSS Bot

Bot
  • Joined

  • Last visited

    Never

Everything posted by RSS Bot

  1. Description Rockchip has released new sdk with rk3576 support and kernel's tag is linux-6.1-stan-rkr3. I have rebased commits from rkr1 to rkr3 and this pr depends on https://github.com/armbian/linux-rockchip/pull/200. Prebuilt kernel can get downloaded from github actions: https://github.com/armbian/linux-rockchip/actions/runs/9740746614?pr=200 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=vendor DEB_COMPRESS=xz KERNEL_CONFIGURE=no KERNEL_GIT=shallow [x] Kernel boots fine on rock5b. [ ] rk356x boards need test [ ] rk3528 boads need test [ ] Other rk3588 boards need test Checklist: Please delete options that are not relevant. [x] My code follows the style guidelines of this project [x] I have performed a self-review of my own code [ ] I have commented my code, particularly in hard-to-understand areas [x] My changes generate no new warnings [ ] Any dependent changes have been merged and published in downstream modules View the full article
  2. Description Helping @SeeleVolleri from: https://github.com/armbian/build/pull/6849 The default 2017.09 u-boot for rk3588 doesn't seem to work on this board with the generic config. Try mainline u-boot. Reference: https://github.com/armbian/build/pull/6834#issuecomment-2198765229 @SeeleVolleri Please test if this works :) You can edit this message to add your tests as well. How Has This Been Tested? [ ] Test A 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 [ ] My changes generate no new warnings View the full article
  3. Description Please note that this PR does not merge to main, but to another branch for collaboration. This is a continuation of v2: https://github.com/armbian/build/pull/6800 @pyavitz has already done a nice job in v1 and v2 of this PR. Based on this work, I have put a lot of effort in trying to bring this new board family more in line with existing families as well as trying to improve maintainability for the long term. Another concern with v2 was the sheer size of the PR (~55MB which amounts to almost 10% of the repo or ~2.4 million LOC which amounts to over 50% of the current repo). v3 brings down this size considerably, to a more sane number: v2 v3 Shrinkage Lines of code 2 402 910 495 249 ~80% PR size ~ 55 MB ~17.5 MB ~66% This is possible due to using external repos for e.g. WiFi driver and vendor kernel instead of completely patching it in. Other than that, changes from v2 to v3: Include all improvements from @pyavitz into the original files/commits Use boot source directly from vendor -> only few patches needed Use vendor kernel source for legacy --> only few patches needed Use our own repo for RTL8852BS WiFi driver --> no patch needed (was huge before) Revise commit messages Downgrade BananaPi F3 to CSC since @pyavitz does not plan to be a maintainer Other little fixes and improvements like using our dt auto-patcher to make it easy to develop and add new boards Please see the commit messages for more details. To-Do I left all functionality as before, so both legacy and current kernels are still there along with the other stuff. We still need to think about whether it makes sense to keep both unless a maintainer wants to step up. But with the v3 changes, legacy and U-Boot will be a breeze to maintain. [ ] Rewrite kernel patches after they're "done" and not changing much anymore (feel free to add more tasks) How Has This Been Tested? [x] ./compile.sh kernel BOARD=bananapif3 BRANCH=current BUILD_DESKTOP=no BUILD_MINIMAL=no EXPERT=yes KERNEL_CONFIGURE=no RELEASE=noble [x] ./compile.sh kernel BOARD=bananapif3 BRANCH=legacy BUILD_DESKTOP=no BUILD_MINIMAL=no EXPERT=yes KERNEL_CONFIGURE=no RELEASE=noble [x] ./compile.sh uboot BOARD=bananapif3 BRANCH=current BUILD_DESKTOP=no BUILD_MINIMAL=no EXPERT=yes KERNEL_CONFIGURE=no RELEASE=noble [x] ./compile.sh build BOARD=bananapif3 BRANCH=legacy BUILD_DESKTOP=no BUILD_MINIMAL=no EXPERT=yes KERNEL_CONFIGURE=no RELEASE=noble [ ] Test flashing image with legacy kernel [ ] Test flashing image with current kernel Information on BananaPi F3 (Following info by @pyavitz from v2) Bluetooth firmware added to armbian/firmware. esos.elf added to: packages/blobs/riscv64/spacemit/ https://docs.banana-pi.org/en/BPI-F3/BananaPi_BPI-F3 https://gitee.com/bianbu-linux Flashing u-boot to eMMC: (This is not apart of the PR and needs to be added in the future.) echo 0 > /sys/block/mmcblk2boot0/force_ro sleep .50 dd if="bootinfo_emmc.bin" of="/dev/mmcblk2boot0" bs=512 conv=notrunc dd if="FSBL.bin" of="/dev/mmcblk2boot0" bs=512 seek=1 conv=notrunc dd if="FSBL.bin" of="/dev/mmcblk2boot0" bs=512 seek=512 conv=notrunc dd if="fw_dynamic.itb" of="/dev/mmcblk2" bs=512 seek=1280 conv=notrunc dd if="u-boot.itb" of="/dev/mmcblk2" bs=512 seek=2048 conv=notrunc sync Tested: Bluetooth and Wifi (useless without an ANT) (bluetooth is iffy) Ethernet (1 and 2) PCIe USB HDMI (LEGACY) Debug UART NOTE: One major difference between this build and the others available else where is the use of SYSLINUX/EXTLINUX instead of the ENV file. BUGS: HDMI currently broke on CURRENT. The screen just displays red. [ 5.132172] [drm:dpu_init] *ERROR* dpu_init wait cfg ready done timeout [ 5.132883] [drm:dpu_isr] *ERROR* Under Run! DPU_Mclk = 0, DPU BW = 0 View the full article
  4. Description Change to mainline uboot, fixed not booting issue, added hdmi0 audio interface alias. How Has This Been Tested? [x] ./compile.sh build BOARD=firefly-itx-3588j BRANCH=vendor BUILD_DESKTOP=yes BUILD_MINIMAL=no DESKTOP_APPGROUPS_SELECTED='browsers internet' DESKTOP_ENVIRONMENT=gnome DESKTOP_ENVIRONMENT_CONFIG_NAME=config_base KERNEL_CONFIGURE=no RELEASE=bookworm [x] 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
  5. Description Auto resize rootfs don't work if build image with: ROOTFS_TYPE=btrfs ROOTFS_TYPE=xfs How Has This Been Tested? Please describe the tests that you ran to verify your changes. Please also note any relevant details for your test configuration. [x] Build image, flash, check rootfs resized Checklist: Please delete options that are not relevant. [x] My code follows the style guidelines of this project [x] I have performed a self-review of my own code [x] I have commented my code, particularly in hard-to-understand areas [x] My changes generate no new warnings [x] Any dependent changes have been merged and published in downstream modules View the full article
  6. u-boot: add HOME env for make invocations to avoid binman/Python problems with older u-boot versions tinkerboard: rewrite u-boot patches, no changes xt-q8l-v10: rewrite u-boot patches, no changes u-boot: add HOME env for make invocations to avoid binman/Python problems with older u-boot versions this avoids trouble building certain older versions with binman as it tries to os.path.join(os.getenv('HOME'), 'bin') and gets a None and dies naming names: tinkerboard & xt-q8l-v10 (BOARDFAMILY=rockchip), which actually use binman & 22.04 combo View the full article
  7. Description Minimal fix for rk322x-box devices to restore the correct sdcard -> usb -> emmc boot order How Has This Been Tested? [x] Tested boot from sdcard and usb stick when armbian is installed in emmc 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
  8. 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. To modify the PWM-fan temperature control policy of fine3399 to adjust the fan speed to a lower level. Integrating support for xiaobaonas and fine3399 boards into the rockchip64-6.9 kernel 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: [x] short description (copy / paste of PR title) [ ] summary (description relevant for end users) [ ] example of usage (how to see this in function) How Has This Been Tested? Please describe the tests that you ran to verify your changes. Please also note any relevant details for your test configuration. [x] Test A [ ] Test B Checklist: Please delete options that are not relevant. [x] My code follows the style guidelines of this project [x] I have performed a self-review of my own code [ ] I have commented my code, particularly in hard-to-understand areas [x] My changes generate no new warnings [ ] Any dependent changes have been merged and published in downstream modules View the full article
  9. Description Lets add some system wide aliases and list some of them at https://docs.armbian.com/User-Guide_Getting-Started/ root user under BASH does not load .bash_aliases GitHub issue reference: Jira reference number [AR-9999] Documentation summary for feature / change How Has This Been Tested? [x] Tested if new aliases are available [ ] Check if aliases also works with root user Checklist: [x] My changes generate no new warnings [x] Any dependent changes have been merged and published in downstream modules View the full article
  10. aml-s9xx-box: bsp-cli hashing fixes aml-s9xx-box: inline bsp-cli preinst function so it's hashed together with the hook; half fixes #6817 this is technically cheating, but works add TODO's ref the manual include'ing of files that are not hashed in the bsp-cli aml-s9xx-box: move files included in bsp-cli from packages/bsp/aml-s9xx-box to config/optional/boards/aml-s9xx-box/_packages/bsp-cli; fixes #6817 with this: those files are automatically hashed by the bsp-cli hashing mechanism no need to copy them manually any more View the full article
  11. bsp-cli/bsp-desktop: hashing fixes bsp-cli/bsp-desktop: hashing fixes both artifacts use functions in the bsp/utils-bsp.sh file, which wasn't being hashed bsp-cli hashed non-existent 'packages/bsp-cli' directory, remove bsp-cli: be verbose when rsync'ing packages/bsp/common force sync in a few strategic spots utils-bsp.sh: be verbose when copying files (incl config/optional stuff) View the full article
  12. odroidm1/orangepi3b: use default (newer) blobs; rewrite patches; bump -rc u-boot to final patch/u-boot/v2024.04: rewrite patches, no changes odroidm1: remove custom blobs, use defaults; bump u-boot 2024.04-rc3 to 2024.04 final orangepi3b: remove custom blobs, use defaults odroidm1: u-boot: rewrite patches, no changes View the full article
  13. armbianmonitor -u: rationalize paste server retrying, use ANSI dmesg armbianmonitor: shellfmt, no changes armbianmonitor: squash shellcheck warnings around the main getopts case statement b and B were never parsed an * case is added to handle invalid options armbianmonitor -u: rationalize paste server retrying, use ANSI dmesg use PIPESTATUS to check all steps for failure avoid blaming paste server if data collection failed View the full article
  14. Description The media board family was long abandoned and most boards that formerly were using this board family already switched to rockchip64 or rk3588. @rpardini recently mentioned being in favor of getting rid of this kernel: https://github.com/armbian/build/pull/6717#discussion_r1632321571 Integrate the last remaining boards into rockchip64 and remove the media board family, including its kernel. GitHub issue reference: https://github.com/armbian/build/issues/6821 Jira reference number AR-2392 How Has This Been Tested? [x] ./compile.sh uboot BOARD=quartz64a BRANCH=edge BUILD_DESKTOP=no BUILD_MINIMAL=no EXPERT=yes KERNEL_CONFIGURE=no RELEASE=trixie [x] ./compile.sh uboot BOARD=quartz64b BRANCH=edge BUILD_DESKTOP=no BUILD_MINIMAL=no EXPERT=yes KERNEL_CONFIGURE=no RELEASE=trixie [x] ./compile.sh uboot BOARD=station-m1 BRANCH=edge BUILD_DESKTOP=no BUILD_MINIMAL=no EXPERT=yes KERNEL_CONFIGURE=no RELEASE=trixie [x] ./compile.sh uboot BOARD=station-p2 BRANCH=edge BUILD_DESKTOP=no BUILD_MINIMAL=no EXPERT=yes KERNEL_CONFIGURE=no RELEASE=trixie [x] ./compile.sh kernel BOARD=station-p2 BRANCH=edge BUILD_DESKTOP=no BUILD_MINIMAL=no EXPERT=yes KERNEL_CONFIGURE=no RELEASE=trixie [x] ./compile.sh uboot BOARD=firefly-itx-3588j BRANCH=edge BUILD_DESKTOP=no BUILD_MINIMAL=no EXPERT=yes KERNEL_CONFIGURE=no RELEASE=trixie @SeeleVolleri You can test the Firefly if you like. Your board was using the abandoned U-Boot from the media family. But it should work same as before :) Checklist: [x] My code follows the style guidelines of this project [x] I have performed a self-review of my own code [ ] My changes generate no new warnings [x] Any dependent changes have been merged and published in downstream modules View the full article
  15. nanopi-r5s: bump blobs & u-boot enhancements for UMS/otg/bootorder nanopi-r5s: bump u-boot from v2024.04-rc3 to v2024.04 "final" nanopi-r5s: add ROCKUSB_BLOB (for Maskrom / rkdevflash extension flashing) nanopi-r5s: bump up blobs 1.18/1.43 -> 1.21/1.44 nanopi-r5s: make u-boot fancy (ums, rockusb, leds, tcp networking stuff) use preboot to flash all leds for 100ms, then leave power LED on nanopi-r5s: u-boot: 2024.04: boot order: usb -> sd -> nvme -> scsi -> emmc nanopi-r5s: u-boot: 2024.04: usb otg in u-boot for working UMS/RockUSB patch/u-boot/v2024.04: rewrite patches, no changes View the full article
  16. Description rk322x has long been integrated into the rockchip family in this PR: https://github.com/armbian/build/pull/6092 Remove some leftovers in the repo, like the old kernel patch folders which are not in use anymore. @paolosabatino You may have a look at the hardware-optimization script. The tweaks for rk322x do not apply since the BOARDFAMILY does not exist anymore. If you'd like to rather integrate those optimizations in some other way (e.g. integrate them into the rockchip hardware optimizations), feel free to change it :) Also, please double check if packages/bsp/rk322x/50-rkvdec.rules is not used anymore. At least I could not find any reference when doing a search. GitHub issue reference: https://github.com/armbian/build/issues/6821 Jira reference number AR-2392 Checklist: [x] My code follows the style guidelines of this project [x] I have performed a self-review of my own code [ ] My changes generate no new warnings [x] Any dependent changes have been merged and published in downstream modules View the full article
  17. Description Some kernel patch folders were forgotten to delete when the kernel version was bumped and are now unused leftovers from the past. Please let me know if I accidentally deleted a folder that is still in use. I have checked these for reference: https://github.com/armbian/build/blob/main/config/sources/families/rockchip.conf https://github.com/armbian/build/blob/main/config/sources/families/include/meson64_common.inc https://github.com/armbian/build/blob/main/config/sources/families/include/rockchip64_common.inc GitHub issue reference: https://github.com/armbian/build/issues/6821 Jira reference number AR-2392 Checklist: [x] My code follows the style guidelines of this project [x] I have performed a self-review of my own code View the full article
  18. Description packages/extras-buildpkgs was a leftover from years ago and is not used in the build framework anymore. See https://github.com/armbian/build/issues/6820#issuecomment-2198054353 With it, remove some references for hostapd and htop. The htop customization in the firstrun script is incompatible with the new versions and throws errors in the firstrun service (see the systemd status of this service after it ran). GitHub issue reference: https://github.com/armbian/build/issues/6820 Checklist: [x] My code follows the style guidelines of this project [x] I have performed a self-review of my own code [ ] I have commented my code, particularly in hard-to-understand areas [ ] My changes generate no new warnings View the full article
  19. Description This PR is part of the big repo cleanup ✨ I tried to find references for the old toolchains. The only reference I could find that was actively using an external toolchain in meson-s4t7. There I have bumped the compiler from 7.3.1 to 7.4.1. A 2019 compiler seems like a good fit to compile a 2019 u-boot :) @viraniac Other than that, I found only this: https://github.com/armbian/build/blob/560993ac7aff4aafc94c8533b8d84eda73b4d656/lib/functions/host/external-toolchains.sh#L26-L37 I have kept every torrent that is referenced in that list, apart from the first few ones which are 10+ years old now and would probably not really work well on a modern machine anyway. Please let me know if you know that a certain compiler/torrent is still needed. Checklist: [x] My code follows the style guidelines of this project [x] I have performed a self-review of my own code [ ] I have commented my code, particularly in hard-to-understand areas [ ] My changes generate no new warnings View the full article
  20. Description armbian-installer have troubles if we are installing OS to SSD with previously defined partitions. Adding a recommended option to start with a clean drive - wiping everything - is one way. In this case, our installer starts in predicted way. Also it gives user no option to choose wrong (too small) partition, if there are more of them pre-made. Jira reference number AR-2393 https://forum.armbian.com/topic/41699-how-to-debugfix-armbian-config-for-kernel-update/#comment-195551 How Has This Been Tested? [x] Made several installs to nvme with several or no partitions Checklist: [x] My changes generate no new warnings [x] Any dependent changes have been merged and published in downstream modules View the full article
  21. The aic8800_dkms_file_name for sdio should be aic8800-sdio-dkms. I think this is a copy-paste error when this extension was added. View the full article
  22. simply because we can View the full article
  23. Description This adds mainline support for the Radxa Zero 3 (E variant at least) SBC by utilizing kwiboo's patch series for both Linux and U-Boot. How Has This Been Tested? Test device: Zero 3E 2GB [x] build edge [x] boot edge http://paste.armbian.com/osofoyuqun.yaml [x] build vendor [x] boot vendor https://paste.armbian.com/lejunireni.yaml Issues: This PR cannot be merged as it is since I have no idea what I am doing so the kernel patchset lacks proper headers. I had to strip those since the framework did not accept the patch series as they were. I don't know how to fix. Those need to be restored to give proper credit. Source: https://patchwork.kernel.org/project/linux-arm-kernel/cover/20240521202810.1225636-1-jonas@kwiboo.se/ this only works for the 3E variant but not for 3W since the vendor variant is a combination of both but mainline provides separate dtbs. This needs attention/workaround as well. BOOTPATCHDIR is just fake so no patches are applied on top of upstream sources. I assume there is a more pretty way to solve this. Raising anyways to create awareness and maybe anyone wants to pick it up and fix things. Feel free to commit adjustments here and bring it in good shape. View the full article
  24. Description removing network manager dependency. Left over from moving networking into extensions. address errors when wireless networking is still not detected Jira reference number AR-2390 Documentation summary for feature / change How Has This Been Tested? [x] Several images on board without wifi only [x] Tested making wrong wifi password 3x, exits with "Unable to connect to AP" [x] Connecting with correct credentials [x] Choosing to not connect to wireless [x] Tested on NM and systemd networkd Checklist: [x] My changes generate no new warnings [x] Any dependent changes have been merged and published in downstream modules View the full article
  25. Description As mentioned here: https://github.com/armbian/build/pull/6810#issuecomment-2194178735 Out of date blobs can be an issue if the vendor ships boards with new blobs, as recently seen for FriendlyElec with the NanoPC T6 for example. The release docs do not mention any incompatibilities between versions for rk3528 and rk3568: https://github.com/armbian/rkbin/blob/master/patch-notes/RK3528_EN.md https://github.com/armbian/rkbin/blob/master/patch-notes/RK3568_EN.md For rk3566, only one warning is listed for rk3566_ddr_1056MHz_ultra_v1.19.bin but we're not using the ultra blob (what's the difference?): https://github.com/armbian/rkbin/blob/master/patch-notes/RK3566_EN.md#rk3566_ddr_1056mhz_ultra_v119bin ROCK_USB_BLOB bump depends on https://github.com/armbian/rkbin/pull/29 being merged. Other blobs have already been merged to armbian/rkbin in the past. How Has This Been Tested? [x] RK3568: ./compile.sh uboot ARTIFACT_IGNORE_CACHE=yes BOARD=nanopi-r5c BRANCH=edge BUILD_DESKTOP=no BUILD_MINIMAL=no EXPERT=yes KERNEL_CONFIGURE=no RELEASE=trixie [ ] RK3566: Not tested - @RadxaNaoki would be great if you could test on Raxda Zero 3 or similar board 😊 [ ] RK3528: Not tested - @amazingfate @sputnik2019 would be great if you could test on a RK3528 board 😊 (although the doc does not list any incompatibilities) Checklist: [x] My code follows the style guidelines of this project [x] I have performed a self-review of my own code [ ] My changes generate no new warnings [ ] Any dependent changes have been merged and published in downstream modules View the full article

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.