Active threads

I just tested the latest Armbian distros, Armbian 26.2.0-trunk.493 XFCE and Armbian 26.2.0-trunk.493 Minimal / IOT, and none worked. Then I tried Radxa system images, rock-4se_bookworm_kde_r4.output_512.img.xz did not work. So I got confused because my Rock 4SE v 1.53 SBC worked a long time ago. Found backup of old boot image, which I used with the NVMe drive, because it could not boot on its own. And do you know what? Finally, I saw a picture on the screen with boot log information, which made me happy because it proved my SBC had not died. Then I started looking at some old system images for this board and found one which is booting, it is rock-4se_debian_bullseye_kde_b38.img.

I will try!! @Lamerjack

I`ll already done it. Switched to original Btt image. Understand what that board is didn`t love any sd-card. I`ll stopts on AP32GMCSH10UB-RA card. If card didn't made friends with the board it not boot,reboot`s,power off, halt`s.... IO pins i didnt use.... I`ll swithed to ch340 as uart, because it`s understand 3.3 and 5v levels. The board only 3.3 CAN i use on RP2040+can chip, what cost only 5$(in total), not 15$ for btt can. in a end of can bus i`ll use EBB42 so it`s have all i need.... It`s about I2C bus. Thats my story If u need help, free to ask. I`ll will help if i coud

Well since you asked in this sub-forum, feel free to start:

a few things happened since sunday: i set up a project homepage: https://langerma.github.io/dumpstore/ - screenshots, feature overview, install instructions. and a wiki of course: https://github.com/langerma/dumpstore/wiki three new things landed since the initial post: live ansible task streaming the op-log dialog now shows tasks appearing one by one as ansible runs them, instead of dumping everything at once when the playbook finishes. small thing, but makes it feel a lot more responsive. pool scrub scheduling you can now add/remove pools from the periodic scrub schedule directly from the ui. on linux it edits ZFS_SCRUB_POOLS in /etc/default/zfs (zfsutils-linux), on freebsd it manages daily_scrub_zfs_pools in /etc/periodic.conf. platform-aware, same interface. schema-driven ui all zfs property dropdowns (compression, atime, recordsize, etc.) and the shell picker for users are now driven by a single schema definition in the backend. GET /api/schema returns the full list filtered by platform. before this, the values were hardcoded in four different places — html, js, and go. adding a new property now means touching one file. nothing groundbreaking, just steady progress.

Well the only thing armbian-config does, is calling "armbian-install" which has been there for ages

What firmware are you using?

@xiboliyadongtu Your log seems normal. The problem is that the game is ~100Gb. I don't have that much free disk space to try. It looks like the game is running, but it's just not using the proper GPU renderer. By default, it will use the WineD3D renderer on top of OpenGL (panfrost). 1) You can try Zink by setting those vars: 2) Try Dxvk-stripped: Download Dxvk-stripped here: https://github.com/khanh-it/dxvk/releases/download/releases/dxvk-v1.6.1-stripped-msvc-output.zip and copy the files x64/d3d11.dll, x64/dxgi.dll to the game's folder (/media/xiboliyadongtu/固态/BlackDesert/) setting those vars: Start the game, and see how it goes?!

Find a board similar to yours and make the necessary adaptations. and on Linux Rockchip: So we can do an shutuo-v8-rk3288 compatible: many times in mainline you can do some tricks like disabling all usb

Thanks for your reply. Sorry for the bad identification of my SBC, (i have many ). The board is this one : https://www.armbian.com/orange-pi-5-plus/ Therefore, it seems that my bug report is relevant

https://www.mediafire.com/file/f2iaay5gccs163l/TV_STICK_R3_TRB.rar/file

As I had read, the maximum amount of RAM the H618 handles is 4GB, so, this 8GB TV Box should be a false information.

v25.11.2 for Orange Pi 5 Plus running Armbian Linux 6.1.115-vendor-rk35xx on mine. Just saying. You should use a spoiler for the slop. tl;dr: vendor kernel has exactly nothing in common with mainline besides the fact that it is supposed to run in the same hw.

Meson 8B is codename of s805 means its not 4k at all bro mine is also 8B i checked it with adb

According to the datasheet (https://de.scribd.com/document/948890791/MT7988A-Datasheet) the supported baudrate seems to be between 300baud and 3Mbaud. However cannot tell anything about support status. Neither do I have this hw, nor did I ever dig into this soc. Starting with device tree overlays might be a good start or check the whole device tree in general for the uart nodes if present.

logs? versions??

I managed to boot armbian from SD card without eMMC. The way achived this is by create a bootable insomwrt with venodr u boot, using my script `./run.sh custom` then replace the ROOTFS with armbian's ROOTFS from there I could boot armbian and fix the fstab. So far it's working fine root@aml-s9xx-box:~# lsblk -f NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINTS mmcblk1 ├─mmcblk1p1 vfat FAT16 BOOT 1C34-0D25 200.9M 18% /boot └─mmcblk1p2 ext4 1.0 ROOTFS 6f2edfb1-adb2-4f1b-8087-46d189763c9b 5.2G 20% /var/log.hdd / zram0 root@aml-s9xx-box:~# uname -a Linux aml-s9xx-box 6.1.66-DBAI #1 SMP PREEMPT Fri Nov 29 09:52:27 +07 2024 aarch64 GNU/Linux root@aml-s9xx-box:~# uptime 01:44:24 up 19 min, 1 user, load average: 0.00, 0.00, 0.00 root@aml-s9xx-box:~# cat /etc/os-release PRETTY_NAME="Armbian 26.2.0-trunk.563 trixie" NAME="Debian GNU/Linux" VERSION_ID="13" VERSION="13 (trixie)" VERSION_CODENAME=trixie DEBIAN_VERSION_FULL=13.3 ID=debian HOME_URL="https://www.armbian.com" SUPPORT_URL="https://forum.armbian.com" BUG_REPORT_URL="https://www.armbian.com/bugs" ARMBIAN_PRETTY_NAME="Armbian 26.2.0-trunk.563 trixie" root@aml-s9xx-box:~#

I tried the nightly build, and I'm happy with the result. Vulkan and OpenGL are still running on the CPU, but I'll try newer images in the future. I did a quick test with Yamagi Quake 2. OpenGL 1.4 doesn't even get 60fps at 640x480, but it looks playable. Should run a lot faster once we can run Vulkan on the GPU. https://github.com/yquake2/yquake2/blob/master/doc/020_installation.md This the make command I used: make WITH_GLES1=yes WITH_SDL3=no -j4 I also tested Stable Diffusion XL Turbo with OnnxStream. Image generated in 7m27s. Looks like the CPU performance is as expected. You do need gcc-14 and g++-14. They are available in the repository. https://github.com/vitoplantamura/OnnxStream You need to change the architecture string in CMakeLists.txt. -march=rv64gcv

Hello I am using: Linux nanopineo 6.12.74-current-sunxi #10 SMP Thu Feb 19 15:29:56 UTC 2026 armv7l GNU/Linux PRETTY_NAME="Armbian_community 26.2.0-trunk.464 trixie" NAME="Debian GNU/Linux" VERSION_ID="13" VERSION="13 (trixie)" VERSION_CODENAME=trixie DEBIAN_VERSION_FULL=13.3 ARMBIAN_PRETTY_NAME="Armbian_community 26.2.0-trunk.464 trixie" i am tring to bind spi1 to fbdev. Here are the configurations: /boot/armbianEnv.txt: /boot/overlay-user/spi1-st7789.dts: SPI1 is not generating any CLK or MOSI signals on the physical pins. Looking forward for any help Best regards, Genadi

Hi everyone, I'm very new to Armbian Linux. I'm about to acquire Orange Pi Zero 2W for my audio project. I have read some of the forum posts related to the SOC's native I2S, and I'd like to know if those problems mentioned in the posts have been resolved in the new kernel? Meaning that users don't have to write and compile their own device tree overlay and kernel mode driver? My project require a full duplex I2S with the CODEC as the master. Nothing fancy, just 2 channels in and 2 channels out. Hope someone can help clear the doubts so that I know for sure I will not be buying what I can not use. Thanks

when using your fork, it worked https://github.com/fensoft/rk3528-tvbox

I am currently at 7.0.0-rc1. I can upload my jump-start image so you can check if my kernel build works with your device. If you like what you see, it is only a 'prepare-jump-start ${target-mount-point}' away to install the kernel package alongside your existing system. I know about it, but since it is just another not mainline solution with another dependency mess, I am not particularly interested.

Thanks for the replies. But I've decided on Linux Mainline on ARM Chromebooks (Veyron): https://github.com/velvet-os/imagebuilder/releases/tag/251115-02 which at least works from the SD card. I'm still working on the installation. 😉

This week’s Armbian development saw a wide range of improvements and fixes across the project’s build framework, kernel support, and device compatibility. Notable changes include the transition from POSIX to Bash syntax for enhanced script reliability, expanded support for new hardware such as the Norco-EMB-3531 board, and the addition of Vulkan and improved 3D package descriptions. Several device-specific updates were made, including kernel enhancements for sm8250, mainline support for SpacemiT, and fixes for wireless and HDMI functionality on various boards. The team also introduced new features like a cache manager modal in the imager and improved marking for container-based software. Multiple bug fixes addressed issues with OS image duplication, patch timestamps, and device quirks. Security was bolstered with hardened GitHub Actions, ensuring a more robust development pipeline. Changes(#9400 P1a) Replace POSIX [ ] with bash [[ ]] across build framework. by @iav in armbian/build#9462Add manual execution and daily cron schedule for MOTD generation. by @igorpecovnik in armbian/armbian.github.io#249Add norco-emb-3531 board and norco vendor image. by @retro98boy in armbian/armbian.github.io#244add Vulkan support and expand 3D package descriptions. by @igorpecovnik in armbian/build#9494Added config improvements and fixes to ayn odin2. by @Squishy123 in armbian/build#9316bump 7.0 to rc2. by @EvilOlaf in armbian/build#9475dwc2: explicitly force host mode for USB_DR_MODE_HOST. by @igorpecovnik in armbian/build#9486feat: add cache manager modal with per-image management. by @SuperKali in armbian/imager#109feat: mark container-based software in menu and docs. by @igorpecovnik in armbian/configng#761fix(gitignore): ignore pycache at all depths (#7863). by @iav in armbian/build#9490fix(images): adapt module to new armbian-images.json structure. by @igorpecovnik in armbian/configng#756fix(manage_zsh): abort shell change if zsh package install fails. by @ajorpheus in armbian/configng#759fix: resolve OS image list duplication when switching filters. by @SuperKali in armbian/imager#110Fix: SakuraPi RK3308B WLAN broken. by @TheSnowfield in armbian/build#9478i915: fix Dell XPS 13 7390 device ID in quirk patches. by @igorpecovnik in armbian/build#9485Improve sm8250 6.19 edge kernel. by @retro98boy in armbian/build#9434meson64: bump edge to 7.0-rc1. by @EvilOlaf in armbian/build#9459meson: freeze current kernel at 6.12.28 and fix HDMI PHY frequency limit. by @igorpecovnik in armbian/build#9465nanopi-zero2: enable mainline kernel support and PCIe for M.2 WiFi. by @rubycomm in armbian/build#9453OrangePi 3B: Add device tree overlays for OrangePi 3B with I2C, PWM, SPI support. by @kskshaf in armbian/build#9460OrangePi-RV2: Fix wireless access point mode by using the correct FW. by @sven-ola in armbian/build#9504orangepi5: rewrite uboot patches against v2026.04-rc3. by @EvilOlaf in armbian/build#9457patching: fix #9028 timestamp when multiple patches touch same file. by @iav in armbian/build#9489pkg_install/pkg_remove: properly propagate apt-get exit codes. by @igorpecovnik in armbian/configng#760Removed un-needed patch for SM8550-6.18; patch has already been updat…. by @Squishy123 in armbian/build#9487rk3568: add 51.2MHz PLL rate for HDMI. by @skorobkov in armbian/build#9477rock-5b-plus: add current kernel to build targets. by @igorpecovnik in armbian/build#9464rock-5t: add current kernel to build targets. by @igorpecovnik in armbian/build#9463Rockchip64 fix patches due to upstream changes in 6.19.6 and 6.18.16. by @EvilOlaf in armbian/build#9483rockchip: Disable specific patches in 6.19 series. by @igorpecovnik in armbian/build#9493rockchip: Enable Wireguard/TUN module in vendor kernel. by @vidplace7 in armbian/build#9492Spacemit legacy loadpatch. by @sven-ola in armbian/build#9496SpacemiT: Add linux-7.0.y "mainline" support. by @pyavitz in armbian/build#9458spacemit: remove old and unused patch set. by @sven-ola in armbian/build#9497unset QEMU_CPU for aml_image_packer. by @QwaSeeK in armbian/build#9417Update odroidxu4-current to 6.6.128. by @belegdol in armbian/build#9491[StepSecurity] ci: Harden GitHub Actions. by @step-security-bot in armbian/build#9356View the full article

Update — Working fix available I've got eMMC detection working on my Radxa Zero 3W with Armbian Trixie (vendor kernel 6.1.115, SD card boot). The fix uses a device tree overlay to inject the missing voltage regulators, pinctrl references, and eMMC capabilities into the base DTB, combined with a small systemd service that rebinds the SDHCI driver to work around a deferred probe timing issue. After applying, the eMMC is detected as expected: mmc0: new HS200 MMC card at address 0001 mmcblk0: mmc0:0001 8GTF4R 7.28 GiB armbian-install works normally after that to migrate to eMMC boot. The rebind service is conditionally skipped when booting from eMMC so it doesn't interfere. I've attached a zip with all the files. The README.md inside has the full details — root cause analysis, what was tried and failed (including full DTB recompile), how the fix works, installation/verification/revert steps, and known limitations (the pinctrl phandle values are specific to this kernel build). I still working on a version that does not need the rebind service for sd cards. but for now you need the rebind on the sd card to get it to find the EMMC so you can install. emmc-fix.zip