Everything posted by Igor
-
build patch fails with KERNEL_CVE_PATCHES="yes"
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.
-
Instructions for updating bootloader on rock s0
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.
- Orange Pi 5 Ultra: Armbian 26.11 / Linux 6.18.60 test report and maintainer interest
- Noble GNOME: PulseAudio and PipeWire both enabled — no sound, browser video frozen at 0:00
-
Proof of concept - Realtek 1295
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.
-
orange pi zero 2w WiFi support?
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.
-
orange pi zero 2w WiFi support?
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.
- Orange Pi RV2
-
CRYPTROOT_ENABLE image did not include pkg systemd-cryptsetup in build
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.
-
CRYPTROOT_ENABLE image did not include pkg systemd-cryptsetup in build
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.
- ODroid M1S Build Debug
-
Thank you for your effort
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.
-
Newer kernels for recent CVE-2026-98432 and 99999 ?
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.
-
Thank you for your effort
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
-
Amlogic S905X4 Processor in GloriaForce RTX DUO – Hardware and Linux Compatibility Discussion
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.
- (Why?) Does Home Assistant require desktop build?
- bananapi-m5 vs builtin ram
-
Newer kernels for recent CVE-2026-98432 and 99999 ?
We have CVE system ready for testing. https://github.com/armbian/build/pull/11166 How it works? armbian/cve collects kernel security fixes that the stable kernels do not have yet. Stable releases can take weeks to include a fix, and some fixes never reach the older LTS kernels. This repository fills that gap. Tracked kernel series: 6.1, 6.12, 6.18 (LTS) and 7.3 (newest stable). Where the fixes come from The fixes come from these sources, in order of preference: stable-queue. These are fixes that the stable maintainers queued for the next point release. They are usually days ahead of the release. Mainline Linux. This is the original fix commit, used when it applies unchanged. The stable mailing list. This is a backport that the fix author posted. Backport with Claude (AI). Some fixes do not apply to an older kernel. Claude adapts these fixes, and a person reviews each one before it goes in. Two other sources decide what counts as a security fix and how urgent it is: The kernel CVE database (vulns.git). The CISA list of actively exploited vulnerabilities. A match opens an issue at once. Fixes that touch only architectures Armbian does not build are skipped. Armbian builds arm, arm64, riscv and x86. How often A check runs every 15 minutes. A full run starts only when a source has changed. Each full run that changes the fixes makes a dated release, for example patches-20261104-0022. In practice there are several releases a day. Every fix must apply cleanly on the newest stable kernel together with all the other fixes. The set must then compile. A fix is removed automatically when the stable kernel includes it. The list does not grow forever. Current state (2026-11-04) Series Base Fixes waiting for stable 6.1 6.1.191 507 6.12 6.12.115 188 6.18 6.18.60 120 7.3 7.3.1 14 The full list is in report.md. It shows what is included, what still needs a backport, and why. To check one CVE, run ./fasttrack.sh why CVE-XXXX-YYYY in a clone of armbian/cve. Plan for Armbian images Now: the repository runs and publishes fixes. Armbian images do not use them yet. Next: the build framework gets the option KERNEL_CVE_PATCHES=yes (build#11166, in review). It is off by default. At first it covers the mainline 6.18 (current) and 7.3 (edge) kernels. Then: the scheduled stable image builds turn the option on. Other builds stay without it until the fixes prove reliable. Later: more series, and the default turned on for more builds. Limits Vendor kernels (for example Rockchip 6.1 and the Raspberry Pi kernels) are not covered. They come from separate trees. The fixes apply to a kernel only when it is the exact stable version that the fixes were checked on. Otherwise the build skips them and shows a warning. "Applies and compiles" does not mean "tested on hardware". Report a problem on the forum or in the repository. Help Backports that still need work are listed in report.md under "Needs a backport". CONTRIBUTING.md explains how to help.
- user vs root
-
Thank you for your effort
Thanks. The log looks the same as before, so I need more data: dpkg -l | grep linux-image and uname -a Boot with drm.debug=0x6 log_buf_len=4M added to the kernel command line, without video=. Then share dmesg via paste. cat /sys/class/drm/card1-DP-1/modes Unfortunately, this is what R&D often looks like. A lot of time spent troubleshooting, with plenty of frustration along the way. :( Having direct access to the hardware makes this process much easier and faster. We really need to develop a service (add on to this) that allows users to enable remote debugging with a single click. Right now, there is simply too much manual back-and-forth involved.
- Thank you for your effort
-
armbian-config + docker - upgrade container image.
We need to implement update functionality and / or convert to docker compose.
-
Anyone here who switched to Canonical/Ubuntu maintained kernel?
Indeed, even its not a problem having so many kernels. We designed whole Armbian project that this is not really a problem. Canonical lack such infrastructure. Closests generic approach is https://github.com/armbian/build/blob/main/config/boards/uefi-arm64-dt.conf which supports device tree and can run multiple boards with single image. I recently moved Nvidia Jetson Nano there with practically 100% hw support. And we could / will move other similar, namely Qcom and Cix based. With addition of recently developed service https://github.com/armbian/cve we will also provide kernels with uptodate security fixes for LTS kernels. There are no reasons to run Canonical kernels.
-
Kernel Updates not automatic anymore with rolling release
Good, a temprally issue then. Like I mentioned, our daily build can stay behind in case build fails. This will happen here and there.
- Anyone have Armbian 24.11 image for Jetson Nano?