All Activity

What does that mean? Panfrost is the GPU driver, for the Mali-T820 GPU. I have hardware acceleration for 3D graphics and video playback, in Armbian.

There is no gpu support in these amlogic tvbox builds.

So here's the weird thing, whenever i apply my user overlay it refuses to boot (red light stuck). But when i only run the build with the new kernel and stock dtb it works fine?? /dts-v1/; /plugin/; / { compatible = "rockchip,rk3229"; /* Wake up the Projector */ fragment@0 { target-path = "/vop@20050000"; __overlay__ { status = "okay"; }; }; /* Wake up the Cable Port */ fragment@1 { target-path = "/hdmi@200a0000"; __overlay__ { status = "okay"; }; }; /* Wake up the Display Guard */ fragment@2 { target-path = "/iommu@20053f00"; __overlay__ { status = "okay"; }; }; }; Does anyone have a clue why this is happening?

I have an x92 box with Amlogic Meson GXM (S912). The SOC has a Mali-T820 GPU, and the box has 2 GB of RAM and 16 GB of eMMC. I'm running Armbian 25.11.2 noble on it. While using the Wayfire Wayland GUI, there is a lot of kernel output like this, constantly repeating: panfrost d00c0000.gpu: shader power transition timeout panfrost d00c0000.gpu: tiler power transition timeout panfrost d00c0000.gpu: l2 power transition timeout The GUI works, and hardware 3D acceleration works. But it would be nice to get this spam out of the logs, and I also wonder if there is really some problem. Like, maybe the kernel doesn't know how to change GPU voltages. Maybe it is related to this at boot, maybe due to an issue with the device tree. kernel: panfrost d00c0000.gpu: error -ENODEV: _opp_set_regulators: no regulator (mali) found The only other sign of something being possibly wrong is that SOC temperature goes surprisingly high when playing hardware accelerated video. That ought to be energy efficient. I'm running Mopidy and Firefox at 53°C and just playing a video can get it to 70°C.

I installed Waydroid on an Amlogic Meson GXM (S912) TV box. The SOC has a Mali-T820 GPU, and the box has 2 GB of RAM and 16 GB of eMMC. This was easy to do and Waydroid worked, but it was very slow, even before it heated the SOC to 80°C, which is probably its throttling limit. I removed Waydroid because it was too slow. I wasn't trying anything demanding. Even navigating Android Settings was ridiculously slow. This is a bit surprising because the hardware was designed for running Android. I was not running much else, just Wayfire and one or two Alacritty consoles. I don't think I was running out of memory. Is it possible to get decent Waydroid performance on other arm64 hardware?

Ubuntu Noble variant already supports ZFS on 6.18.y while Trixie was added today: https://github.com/armbian/os/pull/425 Testing: Once automation completes, it will be provided via normal apt update.

Update 2: 6.16-rc1 works with issues.. Good news: It Loads and registers the rga, vpu [ 1.340230] rockchip-rga 20060000.rga: Registered rockchip-rga as /dev/video0 [ 1.345260] hantro-vpu 20020000.video-codec: registered rockchip,rk3399-vpu-enc as /dev/video2 [ 1.345656] hantro-vpu 20020000.video-codec: registered rockchip,rk3399-vpu-dec as /dev/video3 Issues: swap file is gone HDMI output not working probably more, not sure

Progress update: I managed to boot 6.6.22 with applied hantro and rkdevc drivers in the kernel, I'm not sure if this was already discovered but i found something on the 6.6.22 kernel. Hantro and some Rockchip drivers are found in the Device Drivers -> Multimedia Support -> Media Platform Devices Rockchip Raster 2D Graphic Acceleration Unit Rockchip Image Signal Processing v1 Unit Rockchip Video Decoder (on 6.6.22 this can be found in staging drivers) Hantro VPU Driver Use Reference Frame Compression for HEVC Hantro VPU Rockchip support Hantro VPU Allwinner support Current issues: No Display working, but i got ssh working enough to tell me probably what's wrong with the kernel, Now I'm going to try and do the same but this time with the 6.16-rc1 patches found in Github: Kwiboo/linux-rockchip just to see if that would work also.

@Dangrain Glad to see its working now. please do a guide on it, not only will it help other people it will also help you how to do it again in-case you forgot how to do it haha!

Hi there this is not an x96 but a 'Q10 android TV' the mb looks the same as x96 i have tried some miniarch and your armbians versions (thanks for sharing) but nothing works, anyone can identificate if this mb is compatible ? There is no information about this exact model since it looks very recent. thanks in advance

Hello. BTT says what BTT Pi and CB1 is same, but realy not. Dunno why i brought what board. But now I owner of this "piece of ****" So. New board, clean install v25.11.2 for BigTreeTech CB1 running Armbian Linux 6.12.58-current-sunxi64 Packages: Debian stable (trixie) armbianEnv: overlays=gpu tft35_spi extraargs=fbcon=rotate:2 fbcon=rotate:2 for screen rotation, because armbian not from btt and didn`t have feature like param_tft35_spi_rotate Next, help me to determine how to enable UARTs and I2C From BIGTREETECH_Pi_V1.2.1 Hardware Pdf UART0: CPUX-UTX CPUX-RX UART2 (May work as i2c0; uart2-pi-pins; i2c0-pins ) Pi5 Pi6 UART3 (May work as i2c2; uart3-pi-pins; i2c2-pi-pins ) Pi9 Pi10 I2C (i2c4-ph-pins; spi1-pins): PH6 PH7 (must work, i`ll think i2c4-ph overlay present) All pins present in sun50i-h616-bigtreetech-cb1-sd, but didnt have overlays for it... I wish to stay uart0 for u-boot console first uart setup for klipper connections to mcu. any help? If I understand right PH6 is 7*32+6=230 gpioinfo output line 230: unnamed input consumer=kernel line 231: unnamed input consumer=kernel

Totally new to this system, need some help where to start and how to do it i have the RK3328, i verified this via AIDA, how can i install armbian system on this one can someone please help which are the correct images etc.. any steps would be highly appreciated. thanks Suz

Does this mean you have a working DTS that fixes the issue with smc starting the the other 3 CPUs successfully?

Old automated builds are not kept. Only last three releases https://github.com/armbian/community/releases Its 300Gb / week

Hi, can anyone help me with my board, I tried all 4 images from the github releases for the x96q, flashing them into sd card on windows using belenaetcher, then pluging into the box and booting it, it gets stuck at red light, the moment I eject the sd card it boots into android. am I doing something wrong or I need a specific image?

It boots but does not recognize USB keyboard input. Not possible to login.

hallo @WanJiXianSheng, responding to this image, for the SUB position where the SD card is installed, there are 3 cables, what is their function? Please share here the guide for flashing to Armbian thx..

Success! Thank you so much @Harleyyyu! It now boots perfectly off the eMCP. If anyone wants it I can write a small guide on how to do this, just to make this easier and faster for folks in the future.

@Harleyyyu great , let's follow for project and keep us updated , please

moved

Hi All new here please forgive if non technical which i am , looking to install armbian into this existing X88 box I have attached photos for experts which one is the correct one to flash,

Hello @Malay, et.al, after submitting my PullRQ to the Armbian repo, I think it's best to cope first with the annotations I received from that. It complains about missing board photos, and some LLM generated blurb partly valid suggestions, partly not. The current status of Armbian's Spacemit support does not make the RV2 board a good video player: GPU support is missing and I'm pretty unsure if it's possible to include the HW video encoding / decoding feature that is in the chip. Which is 4k@30 with diverse codecs according to the chip description PDF. I am glad, that X11 framebuffer video runs and I am unsure if I can proceed here b/c I am not a video / GPU / EGL / vulkan specialist. Anyhow, thank you for the pointer to the Spacemit FAQ I did not recognize until now. While the PowerVR page from mesa3d states: "no IMG BXE-2-32" (https://docs.mesa3d.org/drivers/powervr.html), the respective Gitee repo contains closed-source BSD licensed Risc64 compiled shard objects (*.so), probably similar to the Nvida binary user space closed drivers that does the GPU support for the big videos cards. This may be worth a look, but as I wrote above, prio task is to bring the support into the Armbian tree. Best // Sven-Ola

I'm currently trying to build my own kernel for armbian bookworm, using this Github Linux-rockchip: linuxtv-rkdevc-hevc-v2 (6.16-rc1) Goal is to try and make hantro work with native mainline V4L2-Request-API to achieve zero-copy decoding and bypass the legacy Rockchip MPP. i just want to experiment the OS and the VPU it self at this point

@Dangrain If there’s no HDMI, no LEDs, and nothing at all after power-on, that usually means the SoC isn’t even loading u-boot from eMCP. In that state there are no logs to collect yet it’s failing before the kernel starts. Since the same image boots from SD, the issue is almost certainly bootloader placement or compatibility on eMCP, not the OS itself. boot using the sd-card first then try directly flashing the U-Boot to the EMCP and see if that makes it boot 🤷 dd if=u-boot.bin of=/dev/mmcblk1 bs=512 seek=64 sync (device/offset may vary by board)