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.

Igor

Administrators
  • Joined

  • Last visited

  1. Here and there yes. Things can be improved system wise in two ways: clone https://github.com/armbian/cve repo and tell AI agent to contribute. It will fix failing patches and open a PR. This has to be done each time when things fails, best daily as its not just fixing broken patches but also backport new patches. wait. Automation or someone else will eventually fix it. I do it when this job fails https://github.com/armbian/ci/actions/workflows/build-all-stable.yml (currently disabled due to releasing images) Full API driven automation burns cash quick. Prepared but disabled.
  2. Boot the only working, update your packages, then its always like this: https://docs.armbian.com/getting-started/updating/#update-the-boot-loader except some special cases. That is noted on their download pages. I think you can bypass emmc bootloader by holding one of the buttons on the board. After that you choose update bootloader on eMMC and you can run modern images.
  3. Added: https://armbian.com/boards/orangepi5-ultra Welcome to spread the word around. Also updated: https://armbian.com/boards/orangepi5
  4. I am not familiar with Lakel Box. General requirements to make it possible and to squeeze months into weeks: - schematics - hardware - serial console - vendor provided uboot and kernel sources - Claude Max account or higher - a week(s) of boredom - SD card emulator - experiences - other's people / similar board attempts W2 still uses binary blobs for bringing the SoC up. Cracking that we are looking at several weeks with uncertain outcome. Chain booting modern u-boot from factory uboot is usually possible and is considered more as a workaround when assembling a complete (u)boot flow is not possible, when boot process is undocumented / hidden, pack into binary blobs. Sadly I am busy for next couple of months.
  5. Probably worse - both This Wi-Fi hardware is poor, regardless of which Linux distribution you run. Perhaps less poor on Armbian as people have contributed patches to the driver we host, so I assume that at least some of the issues have been addressed. But expecting a smooth ride from a hardware that costs next to nothing is simply unrealistic. Especially when its support is the result of questionable business practices, no vendor involvement, fragmented market with different (cheap) chips and community-driven volunteer patching. Also AI agents can't fix the code just like that / automatically. They has to be driven by an experinced person. There are limits to what even the most dedicated open-source developers can do. And wireless network section is also one of the most technically complex one. And by the end of the day. Software cannot magically compensate for every hardware flaw.
  6. Without exaggeration, Armbian offers arguably the best Wi-Fi support among Linux distributions, particularly for the hardware we target. However, much of the hardware we deal with is super cheap. Cutting costs inevitably involves compromises, and low-cost components simply cannot be expected to deliver the same reliability and performance as first-class hardware. We regularly test Wi-Fi hardware and publish the results: https://docs.armbian.com/status/wifi-performance/ When a driver is fundamentally broken and the hardware vendor doesn't maintain it properly, there is only so much we can do. Even with extensive use of AI agents to help investigate and fix issues, we cannot compensate for every hardware limitation or poorly maintained driver. https://github.com/armbian/uwe5622 You are welcome to make it work better.
  7. Igor replied to sven-ola's topic in RISC-V
    For daily updates you need to switch to rolling https://docs.armbian.com/config/updates/#rolling
  8. Absolutly. There are lots of PR's coming up lately. For cryptoroot stuff i am doing two things: - automatic recrypt at first boot when autokey is used (set at build time) - support for encrypted rootfs in armbian-install systemd-cryptsetup package doesn't change / help in this in any way AFAIK.
  9. You are right. https://github.com/armbian/build/pull/11300/changes Feel free to open PR next time. Otherwise its missed. PS I made many improvements to LUKS encryption lately. One desktop variant is going to be released (v26.11) with a default encrypted rootfs.
  10. Igor replied to tparys's topic in Rockchip
    FYI. Might come handy here. @djurny made generalization / templating of boot scripts. If only loading address is different, it would be cleaner then cp whole script. In case you find time to look into. Not a blocker.
  11. Thanks for testing. The DP link now works correctly at 2560x1440@120. The garbage during heavy screen output is a different problem. The memory clock probably cannot increase on this boot path. The kernel has no memory timing table for the Nano ("no memory timings for RAM code 0" in your log). At 120 Hz, the display then does not get enough memory bandwidth when the screen changes a lot. Workaround for now: use a lower refresh rate. Add one of these to the kernel command line and test with a lot of text output: video=DP-1:2560x1440@100 If 100 Hz still shows garbage, use video=DP-1:2560x1440@60. Please also send the output of this command. It shows the current memory clock: sudo cat /sys/kernel/debug/clk/emc/clk_rate The real fix needs (a lot) more work in the kernel memory driver. I cannot do it right now. Your answers will tell which fix is necessary.
  12. It's an explanation of how we're approaching this problem. IMO better approach then any Linux OS out there. In the age of AI, we won't be doing this kind of operation by hand. But this means whole automation become more complex. We're looking for someone who can continuously monitor CVEs, track their status, perhaps improve its design, promote biggest gains and provide answers to questions like yours. System needs to be feed by interactive Claude or 100-150 USD of tokens to drive it fully automatic. Stable repo updating is currently under testing. Only a few kernels will be getting weekly auto-update: https://github.com/armbian/armbian.github.io/blob/main/config/repository-kernel-selection.conf while others will probably need to pass hardware validation. That role is currently unfilled, and we have no funding allocated to it. Until someone volunteers or funds this specific work, the only answer I can give you is that our best-effort policy applies. I hope by the end of the month all this is in place. Then all CVE's that are resolved are auto-included, while reported ones will require some (serious) work.
  13. Test kernel with the fix. It has the same version string as your current kernel, so install it with dpkg, not apt: sudo dpkg -i linux-image-edge-uefi-arm64-dt_26.11.0-trunk_arm64__7.3.1-*-Pa723-*.deb Reboot without video= and with drm.debug=0x6. Expected: no failed to choose link: -34, and DP shows 2560x1440@120. The 144 Hz and 165 Hz modes need more than the 600 MHz pixel clock the SOR supports. Please share dmesg and cat /sys/class/drm/card1-DP-1/modes. linux-dtb-edge-uefi-arm64-dt_26.11.0-trunk_arm64__7.3.1-S79a9-D68f5-Pa723-Cf941-Hd102-HK01ba-V3428-B0577-R448a.deb linux-image-edge-uefi-arm64-dt_26.11.0-trunk_arm64__7.3.1-S79a9-D68f5-Pa723-Cf941-Hd102-HK01ba-V3428-B0577-R448a.deb
  14. No. S4 (S905Y4) is the closest relative we support. There were a lot of issues to bring it up - we spent several weeks fulltime and with Librelec preliminary work, peer and agents help https://github.com/armbian/build/pull/10984 There are many common areas but there is still a lot of work to bring this SoC up. What SC2 (S905X4) needs that the PR doesn’t have: meson-sc2.dtsi: SC2’s clock controller, pinctrl banks, reset and power domains differ from S4. This is the bulk of the work. devmfc’s 6.12 tree and the vendor 5.15 kernel are the places to take it from. Ethernet: the Gigabit MAC with an external RGMII PHY, plus the internal 10/100 PHY. S4 only covers the internal-PHY path, which is why devmfc so far has only 100 Mbit working. USB 3.0 / PCIe combo PHY: S4 has nothing here. The T7 USB3/PCIe patches (0073–0091) might be a useful reference, but that’s a guess until the registers are compared. U-Boot: S905X4 hardware is all TV boxes with locked vendor U-Boot. These may hit the same rsvmem check rejection of mainline DTBs that older VIM1S U-Boot had. That would decide whether an extlinux/edge-style boot works at all.

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.