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.

Werner

Administrators
  • Joined

  • Last visited

Everything posted by Werner

  1. Providing logs with armbianmonitor -u helps with troubleshooting and significantly raises chances that issue gets addressed.
  2. Werner replied to a post in a topic in Allwinner sunxi
    We cannot provide support on 3rd party forks
  3. could you elaborate?
  4. I think you hit a bad Debian mirror. Nothing we could fix.
  5. @Harry Pelekanis your post is here. do not post on multiple places for the same topic to raise attention. This is considered abusive behaviour.
  6. KERNEL_GIT=shallow (or was it GIT_KERNEL? Having hard times to keep that in mind correctly) but anyway, this will load a shallow tree with the corresponding kernel version only.
  7. vendors tend to use outdated boot loaders from the ages on all their stuff which makes them compatible with their own (also in most cases outdated) stuff. Armbian follows mainline. Either the old boot loader stuff cannot handle the chain-load the modern world or it is made in purpose ("vendor lock-in"). We may never know.....
  8. good question, never tried this. I usually just set ENABLE to false and reboot.
  9. moved to tvboxes
  10. Feel free to test and send a pr with a patch backporting this to 6.18
  11. The board should have RT8821CU as wifi chip. Since Linux 6.17 there is no out of tree driver necessary anymore, mainline i used. So perhaps this is a an issue or regression upstream. You can try to switch to edge kernel, perhaps this has been addressed but not back-ported.
  12. Yes. commit 6df6d0d607abfd59169a0ef2fddbed5fcd5b58f9 Author: EvilOlaf <werner@armbian.com> Date: Thu Feb 26 18:09:38 2026 +0000 rockchip64: 7.0: Rebase on top of main diff --git a/patch/kernel/archive/rockchip64-6.19/0000.patching_config.yaml b/patch/kernel/archive/rockchip64-7.0/0000.patching_config.yaml similarity index 100% rename from patch/kernel/archive/rockchip64-6.19/0000.patching_config.yaml rename to patch/kernel/archive/rockchip64-7.0/0000.patching_config.yaml diff --git a/patch/kernel/archive/rockchip64-6.19/add-board-helios64.patch b/patch/kernel/archive/rockchip64-7.0/add-board-helios64.patch similarity index 100% rename from patch/kernel/archive/rockchip64-6.19/add-board-helios64.patch rename to patch/kernel/archive/rockchip64-7.0/add-board-helios64.patch :
  13. Oh well, that's quite some time ago. The patchset used back then has been removed/renamed already to move on. Look at 6df6d0d607abfd59169a0ef2fddbed5fcd5b58f9 The question is has this introduced upstream or with one of the patches Armbian puts on top. Quite a journey to dig through that.
  14. This may be an issue. I know from the past Armbian and petitboot don't work well together. You need to wipe your spi to get rid of it. Then everything should work just fine. Having this package installed means nothing about the actual used boot loader. This package only provides the binaries to rewrite the boot loader if actually necessary. It is updated with package install/upgrade because doing so is rarely necessary. armbian-install can update the boot loader and will use the binaries from the package.
  15. Where did you get this uboot? I strongly believe this is not from Armbian, hence support is impossible.
  16. Providing logs with armbianmonitor -u helps with troubleshooting and significantly raises chances that issue gets addressed.
  17. nand-sata-install has been a symlink to armbian-install for quite a while and yes, this tool didn't receive much love. However it could be replaced soon by this:https://github.com/armbian/configng/pull/951
  18. split into new topic for the reason above.

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.