All Activity

Seems like Mate change to sv_SE.UTF-8, but there are no app to change launguish in Mate. Think I have to remove mate?

Thanks for looking into this. As the docker install does not have access to apps it would be quite restricted and not really usable for many. I would certainly not use it. May be you could try to set up the supervised install (I know it is not supported anymore by HA) ? That would bring a lot of attention to Armbian ...

thanks @Arthur Gu, I will test and include into armbian

This is a work-in-progress resource for bare-metal bringup for Rockchip devices. Source code: https://github.com/petabyt/rk https://danielc.dev/rk/

The issue has been resolved. It turns out that the official release has already configured the necessary documents or files before distribution. When I used im‑config, it gave me no response at all. Following the XDG Autostart manual, I copied /usr/share/applications/org.fcitx.Fcitx5.desktop to ~/.config/autostart; after that, fcitx5 starts automatically and works normally when I reboot or log out and back in. Thanks

@sven-ola Sorry, this was indeed a mystery problem with my SSD. I replaced it, and now everything works like a charm (I just need the CLI server; Wi-Fi or GPU isn’t necessary). By the way, when is the stable release planned?

--- Hey everyone! Long-time lurker, first post here. I picked up one of those cheap RK3229 TV boxes and decided to see how far I could push it on a mainline kernel — no Android, no BSP, no blobs. What started as curiosity about whether rkvdec actually worked on kernel 6.6 turned into a full rabbit hole of GStreamer pipelines, PHY register dumps, and DRM memory bandwidth math. The whole debugging and documentation process was done collaboratively with Claude (Anthropic's AI assistant), which made it a lot easier to dig into kernel driver internals and iterate on the pipeline without spending weeks at it. All the results were validated on real hardware. Sharing here in case it saves someone else the same rabbit hole. --- [GUIDE] Hardware H.264 decode at 720p — mainline kernel 6.6, GStreamer, no blobs After spending some time on my RK3229 TV box running Armbian 24.2.5 Bookworm (kernel 6.6.22-current-rockchip), I got hardware H.264 decode working at 720p real-time using only mainline kernel drivers and open-source GStreamer plugins. Posting here in case it helps others. --- What works - H.264 720p@30fps fully hardware decoded via rkvdec (the mainline V4L2 stateless decoder) - Direct HDMI output via kmssink (DRM/KMS — no X11, no Wayland needed) - Audio output via ALSA (HDMI or analog) - YouTube streaming with audio+video in sync using a small proxy server What doesn't work and why - 1080p: The decoder itself handles it, but writing ~90 MB/s of NV12 frames to uncached DRM memory saturates the Cortex-A7 memory bus. Not a software problem — there's no fix without DMA-BUF zero-copy between rkvdec and the DRM subsystem. - YouTube in a browser: Browsers do their own software decode — no VA-API bridge exists for rkvdec on mainline. Even with a desktop environment installed, frame rate will be unusable. - HEVC / AV1: Not supported by rkvdec on RK3228/RK3229. --- The GStreamer pipeline # Local H.264 file — video only gst-launch-1.0 filesrc location=video.mp4 ! qtdemux ! h264parse \ ! v4l2slh264dec ! videoconvert ! kmssink driver-name=rockchip sync=true # YouTube streaming with audio (requires proxy — see repo) gst-launch-1.0 -e \ souphttpsrc location="http://PROXY_IP:8091/play?v=VIDEO_ID&q=720&fmt=ts" automatic-redirect=true ! \ tsdemux name=demux \ demux. ! queue ! h264parse ! v4l2slh264dec ! videoconvert ! kmssink driver-name=rockchip sync=true \ demux. ! queue ! aacparse ! avdec_aac ! audioconvert ! audioresample \ ! "audio/x-raw,rate=44100,channels=2" ! alsasink device=hw:2 Key points: - v4l2slh264dec is the stateless GStreamer element — do not use h264_v4l2m2m (that's for stateful decoders like RPi) - kmssink driver-name=rockchip uses /dev/dri/card0 (Rockchip DRM display), not the Lima GPU - For YouTube, MPEG-TS (fmt=ts) is required — fragmented MP4 with empty_moov breaks GStreamer cap negotiation --- Why this is different from Jock's media framework Jock's framework uses kernel 4.4 + RKMPP proprietary blobs. This uses kernel 6.6 mainline + rkvdec upstream driver + open-source GStreamer. No blobs, works with current Armbian, survives kernel upgrades. --- Requirements - Armbian 24.x with kernel 6.6-current-rockchip (kernel 5.15 / Bullseye not tested — V4L2 stateless API wasn't stable until 5.18) - GStreamer 1.22 from Debian Bookworm sudo apt install -y gstreamer1.0-tools gstreamer1.0-plugins-base \ gstreamer1.0-plugins-good gstreamer1.0-plugins-bad \ gstreamer1.0-libav gstreamer1.0-alsa --- Repo with scripts and full setup guide https://github.com/Reinoldo-Ozy/rk322x-mediaplayer Includes the yt-play playback script and the proxy server (yt_proxy.py) with systemd unit. The README covers the full setup, performance numbers, and a detailed limitations section. Tested on a generic MXQ Pro-style box with RK3229, 2 GB RAM, Armbian 24.2.5 Bookworm, kernel 6.6.22-current-rockchip, DTB rk322x-box.dtb.

I am running mine on Trixie, installed about a year ago. Then it worked ... Core is running inside Docker container so functionality should be O.K., but we might currently have some problem ... I will look into this when I am about to reinstall my setup, but I plan to add Docker install only, which should work well, but it has certain limitations.

@Sergioclr remove those two Failing patches you don’t need them anyways.

Really? You changed the network config, installed a massive application AND enabled apparmor in the same boot... Cmon dude... It probably does, if you don't also change the network.

@SecLyzer U-Boot can boot from a FAT32 or Linux file system. You can change this in your board configuration file.

Due to the shortage of memory chips these days, Radxa is using different emmc models in their boards. For example, I recently ordered a big batch of Rock S0 boards, but they had to be delivered with Sandisk iNAND 32GB emmc drives instead of the typical 8GB option. The problem is that Armbian did not reliably boot on these new boards. It randomly gets stuck during initialization with the onboard LED endlessly blinking. Some boards works, some did not, some only works sometimes. Long story short, in case other people also have this problem: I found the solution. I believe it is caused by Armbian's Rock S0 device tree enabling the HS200 high speed mode for the emmc device. (source) I guess not all emmc chips reliably support this. To fix it, I had to remove the line in the device tree linked in the source above. Actually this should probably be done with a proper device tree modification, but in my case, just to test, I modified the boot scripts. In /boot/boot.cmd, add these lines near the bottom, but ABOVE the "booti ..." line: fdt rm /mmc@ff490000 mmc-hs200-1_8v fdt set /mmc@ff490000 max-frequency <0x02faf080> Then recompile in terminal with: mkimage -C none -A arm -T script -d /boot/boot.cmd /boot/boot.scr If you update the kernel/armbian distro these script will probably get overwritten, hence why it should preferably done with a custom device tree instead. But in my case I have frozen updates, and either way this will serve as a starting point for others having the same issue. Actually, I cannot see this troublesome patch on the 6.18 distro source, so maybe this is old news and no longer a problem on modern images anyway. But my image is still on 6.12, so I figured I'd share anyway.

@Sand_DeathDid you extract the image and use BalenaEtcher? It works fine on my Radxa Cubie A7A board.

https://github.com/sicXnull/armbian-build/releases MXQ-PRO H313 https://github.com/sicXnull/armbian-build/archive/refs/tags/mxqpro.zip Summary: compile from source halts with error. Traceback (most recent call last): [🔨] File "/home/e***o/Downloads/armbian-build-mxqpro/lib/tools/patching.py", line 491, in <module> [🔨] raise exit_with_exception [🔨] Exception: Failed to apply 2 patches. Log uploaded and available at https://paste.armbian.com/dimokofipe Thanks in advance

The installation of Home Assistant through armbian-config ends with a reboot in order to enable AppArmor. No modification. If that installation does not work out of the box I will leave it for now as it would not provide a solid basis for the automation of an entire home.

@Taz Radxa's u-boot won’t load the kernel image. So I used vmlinux.

This topic is 2 years old and HA formally does not support supervised anymore. And doing 2 such modifications and then hoping all will be fine is false hope IMO. If you don't have a serial console cable to watch kernel en journal log etc to see what your system is doing, maybe it is time now to get one. I have an old supervised inatsllation (not use for many months, but it is plain Debian and a VM so I have free/easy CLI console.

Same here: Installed Home Assistant using armbian-config on a Rock 5b with Armbian Trixie (v26.2.1 for Rock 5B running Armbian Linux 6.18.32-current-rockchip64). I switched from NetworkManager to systemd-networkd. Reboot to enable AppArmor left a system not accessible via ssh after more than 100s. Do we have to wait somewhat longer, or is there currently an issue with the installation of Home Assistant on Armbian Trixie ?

I just received a new Radxa Cubie A7A board. I decided to try flashing @Nick A firmware (https://github.com/NickAlilovic/build/releases/tag/Radxa-Cubie-A7A-A7Z-A7S-Mainline-V0.1), but the board simply wouldn't boot. I used a Netac 32 GB microSDHC card, class 10, UHS-I. I've attached the UART logs below.load.log

Ok, just wanted to know if you used the flatpak since they indicate on their wiki that could be troublesome. When you say "none of them can start automatically", what methods did you use to configure autostart? As they state at the top of the wiki/setup: "Distribution may provides some specific tool for autostart Fcitx and usually also set up environment variable together." Take notice of the word MAY. Seems Armbian does not. So what does im-config do as described on the next line after that on the wiki page? Does it fail or give you some hints of why autostart is not working? https://fcitx-im.org/wiki/Special:MyLanguage/Setup_Fcitx_5#im-config_(Debian/Debian-based/Ubuntu) This question is more fitting to ask the devs of the application, not the operating system. If you have problems with an application on windows for example, you generally don't ask microsoft for help but rather the developers of the application. But if you provide good enough information, we might be able to help you figure it out on this forum...

none which doesn't break other boards.

1. Ubuntu 26.04 current 6.18.29 xfce / Debian 12 bookworm Xfce current6.12.23 I have tried two different Armbian community‑build images, and no matter which input method I use (ibus, gcin, fcitx4, or fcitx5), none of them can start automatically. In offical Ubuntu/Debian desktop releases, input methods normally start by themselves without such complicated setup 2. just apt install fcitx5 and more 3 i have read wiki setup fcitx5 4. i use Firefox Please check the problems Thanks

Armbian has limited resources. And given that there are hundreds of different boards out there, generally that means that new boards only get supported either because the company behind them is willing to contribute to Armbian (and Orange Pi has made if very clear that they don't do anything to support their boards software after the fact as it would reduce sales for new boards they are constantly introducing), or some volunteer from the community steps up to volunteer their time to add support. Most boards under Armbian are community supported. So it relies on volunteers like you to do the work.

More information is needed. What armbian release do you use? How did you install fcitx5? Have you followed the instructions on their wiki? https://fcitx-im.org/wiki/Special:MyLanguage/Setup_Fcitx_5 Or read the FAQ? https://fcitx-im.org/wiki/Special:MyLanguage/FAQ Are you using a chromium based browser?

Why this board, the orange pi 4 Pro, isn't supported?