Search the Community

I am running the Ubuntu Noble 24.04 XFCE image on a Radxa Zero SBC (first generation device). Trying to play a video with parole (gstreamer video player) produces the error message "GStreamer Backend Error: Could not read from resource. " Increasing the gstreamer debug level produces the following additional information: 0:00:00.329008719 131342 0xaaab079354e0 WARN GST_ELEMENT_FACTORY gstelementfactory.c:765:gst_element_factory_make_valist: no such element factory "autoimagesink"! 0:00:05.702394971 131342 0xffff7c0013d0 ERROR v4l2bufferpool gstv4l2bufferpool.c:716:gst_v4l2_buffer_pool_streamon:<v4l2h264dec0:pool0:sink> error with STREAMON 22 (Invalid argument) 0:00:05.702572595 131342 0xffff7c0013d0 ERROR v4l2bufferpool gstv4l2bufferpool.c:2233:gst_v4l2_buffer_pool_process:<v4l2h264dec0:pool0:sink> failed to start streaming 0:00:05.703109216 131342 0xffff7c000da0 WARN v4l2 gstv4l2object.c:5887:gst_v4l2_object_poll:<v4l2h264dec0> error: poll error 1: Connection timed out (110) 0:00:05.703217049 131342 0xffff7c0011a0 WARN qtdemux qtdemux.c:7423:gst_qtdemux_loop:<qtdemux0> error: Internal data stream error. 0:00:05.703483881 131342 0xffff7c0011a0 WARN qtdemux qtdemux.c:7423:gst_qtdemux_loop:<qtdemux0> error: streaming stopped, reason error (-5) Looks like there is an issue with the v4l device provided by the meson_vdec kernel module. Removing the meson_vdec kernel module indeed eliminates problem. Videos are played without error message using software decoding. The frame rate is unfortunately low. Otherwise I would not care about hardware decoding. Interestingly, the v4l2-compliance command suggests that the v4l device for the VPU is in good shape: $ v4l2-compliance v4l2-compliance 1.26.1, 64 bits, 64-bit time_t Compliance test for meson-vdec device /dev/video0: Driver Info: Driver name : meson-vdec Card type : Amlogic Video Decoder Bus info : platform:meson-vdec Driver version : 6.6.31 Capabilities : 0x84204000 Video Memory-to-Memory Multiplanar Streaming Extended Pix Format Device Capabilities Device Caps : 0x04204000 Video Memory-to-Memory Multiplanar Streaming Extended Pix Format Detected Stateful Decoder Required ioctls: test VIDIOC_QUERYCAP: OK test invalid ioctls: OK Allow for multiple opens: test second /dev/video0 open: OK test VIDIOC_QUERYCAP: OK test VIDIOC_G/S_PRIORITY: OK test for unlimited opens: OK Debug ioctls: test VIDIOC_DBG_G/S_REGISTER: OK (Not Supported) test VIDIOC_LOG_STATUS: OK (Not Supported) Input ioctls: test VIDIOC_G/S_TUNER/ENUM_FREQ_BANDS: OK (Not Supported) test VIDIOC_G/S_FREQUENCY: OK (Not Supported) test VIDIOC_S_HW_FREQ_SEEK: OK (Not Supported) test VIDIOC_ENUMAUDIO: OK (Not Supported) test VIDIOC_G/S/ENUMINPUT: OK (Not Supported) test VIDIOC_G/S_AUDIO: OK (Not Supported) Inputs: 0 Audio Inputs: 0 Tuners: 0 Output ioctls: test VIDIOC_G/S_MODULATOR: OK (Not Supported) test VIDIOC_G/S_FREQUENCY: OK (Not Supported) test VIDIOC_ENUMAUDOUT: OK (Not Supported) test VIDIOC_G/S/ENUMOUTPUT: OK (Not Supported) test VIDIOC_G/S_AUDOUT: OK (Not Supported) Outputs: 0 Audio Outputs: 0 Modulators: 0 Input/Output configuration ioctls: test VIDIOC_ENUM/G/S/QUERY_STD: OK (Not Supported) test VIDIOC_ENUM/G/S/QUERY_DV_TIMINGS: OK (Not Supported) test VIDIOC_DV_TIMINGS_CAP: OK (Not Supported) test VIDIOC_G/S_EDID: OK (Not Supported) Control ioctls: test VIDIOC_QUERY_EXT_CTRL/QUERYMENU: OK test VIDIOC_QUERYCTRL: OK test VIDIOC_G/S_CTRL: OK test VIDIOC_G/S/TRY_EXT_CTRLS: OK test VIDIOC_(UN)SUBSCRIBE_EVENT/DQEVENT: OK test VIDIOC_G/S_JPEGCOMP: OK (Not Supported) Standard Controls: 2 Private Controls: 0 Format ioctls: test VIDIOC_ENUM_FMT/FRAMESIZES/FRAMEINTERVALS: OK test VIDIOC_G/S_PARM: OK (Not Supported) test VIDIOC_G_FBUF: OK (Not Supported) test VIDIOC_G_FMT: OK test VIDIOC_TRY_FMT: OK test VIDIOC_S_FMT: OK test VIDIOC_G_SLICED_VBI_CAP: OK (Not Supported) test Cropping: OK (Not Supported) test Composing: OK (Not Supported) test Scaling: OK (Not Supported) Codec ioctls: test VIDIOC_(TRY_)ENCODER_CMD: OK (Not Supported) test VIDIOC_G_ENC_INDEX: OK (Not Supported) test VIDIOC_(TRY_)DECODER_CMD: OK Buffer ioctls: test VIDIOC_REQBUFS/CREATE_BUFS/QUERYBUF: OK test CREATE_BUFS maximum buffers: OK test VIDIOC_EXPBUF: OK test Requests: OK (Not Supported) Total for meson-vdec device /dev/video0: 46, Succeeded: 46, Failed: 0, Warnings: 0 What is the current status of meson VPU support? Is this a known issue? Has anyone ever got video hardware decoding to work with the Radxa Zero SBC? Thanks for any hint in advance! armbianmonitor.txt

Hi, I have problems from booting emmc of my 4/64GB radxa zero. I want to make fresh install and cleaned emmc completely. By following radxa guide, I flashed latest Armbian_24.8.1_Radxa-zero_noble_current_6.6.47.img.xz image from official site. But booting failing. I attached serial monitor and saved output. Boot process stops at line 215 and If I give "boot" command, It starts booting from emmc with same warnings. I'm attaching full log. By the way, I tried updating bootloader by using armbian-config utility but nothing changed. radxa_zero_serial.log

Hey all, I'm unable to boot Armbian from the SD card of my Radxa Zero 1 GB. When I download one of the official Armbian Radxa Zero images I always get the message "ALERT! UUID=eba52b2e-b77a-47b9-9619-ebda85946883 does not exists. Dropping to a shell!" Previously I ask the Radxa community on Discord, were I received the suggestion that the CMA memory maybe was configured too high. I tried to make an image from master (4b21499534, after https://github.com/armbian/build/pull/4151 was merged) but that didn't help. When I run `dmesg` I get the following repeating error "mmc1: error -84 whilst initialising SD card" When I run `blkid` I do not get any output But when I insert the SD card in my laptop and run `blkid` I get: "/dev/sda1: LABEL="armbian_root" UUID="eba52b2e-b77a-47b9-9619-ebda85946883" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="9a366be2-01" So the uuid seems to be correct. I'm not able to boot into Armbian, but the official non-Armbian images from the Radxa site work just fine on this device with the same SD card. Does anybody know what could be the problem, or any ideas how it can be solved? (The file upload was not working for me, so this is a link to the screenshot image: https://imgur.com/a/UPakZPm)

Hi, I installed armbian_23.8.1_Radxa-zero_bookworm-current_6.1.50 on Radxa Pi Zero eMMC and I have an USB SSD drive connected as storage. Everything worked fine using it as a NAS but if I reboot there is an endless loop of reboots with the core message "scanning bus usb0ff5000000 for devices... Synchronous Abort handler, err 0x56000010". If I disconnect the USB drive it boots fine and when reconnect it after the boot process, the drive works fine. But I really need a system that is able to boot without temporarely disconnecting USB. I tried different combinations of USB with two different hubs or without hub. There are no boot flags on the partitions. I completely deleted all partitions on the drive and tried different kind of partitions and file systems. It does not change anything. Even without any partition it has the same error. I have another USB SSD that also causes a few pages of error messages but after that it does boot (from eMMC). Unfortunately that is the wrong USB drive and does not help. Switching too the newest kernel with armbian-setup also does not work. Finally I installed Radxa Ubuntu 20 and it boots without any issues while the USB SSD is connected. What can I do to solve this when using Armbian? Thanks Tobi

Hello everyone. This is my first post here. My background is software development but not very experienced in the Linux SBC world. So, I have 2x Radxa Zero 3W (not listed on Armbian) with a Rockchip 3566 MCU. And here the questions start... - why don't the Orange Pi 3B or Quartz 64B Armbian images, with the same MCU, don't work on the Radxa Zero 3W ? Aka, shouldn't an OS be portable ? I'm not expecting such of Windows, but I did expect it from Linux - what do the loaders contain exactly ? I have this situation where an older loader seems to boot with Armbian (and then shuts down) but a newer one doesn't... yet the older one doesn't work with the OS from Radxa but the newer one does. If we are talking memory address to chain-boot from, aren't these somewhat standard ? - the last time I installed some Linuxes on a PC was when socket 939 was a new thing, over 15 years ago. An installation was pretty slim, yet now a Debian image decompresses on an SD card to about 12 GB ?! - are these images actually an "in between" an official release kit and a working Linux image ? Thank you in advance for your patience !

Hello there, I'm trying to get an i2c ssd1306 screen to work with my Radxa Zero, without much luck for the time being. https://paste.armbian.com/cirulemeho I found two i2c devices, 3 and 5. sudo i2cdetect -y -r 3 0 1 2 3 4 5 6 7 8 9 a b c d e f 00: -- -- -- -- -- -- -- -- 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 20: -- -- UU -- -- -- -- -- -- -- -- -- -- -- -- -- 30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 70: -- -- -- -- -- -- -- -- sudo i2cdetect -y -r 5 0 1 2 3 4 5 6 7 8 9 a b c d e f 00: -- -- -- -- -- -- -- -- 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 30: 30 -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 70: -- -- -- -- -- -- -- -- I think the 5 is for HDMI, right? Would the UU for the 3 mean my screen is not correctly connected or detected? Thanks.

I have a Logitech C920 webcam I am trying to use on my Radxa Zero. I'm running Armbian 23.11.1 Bookworm 6.1.63 64-bit. When I run v4l2-ctl -i /dev/video1 --list-formats to query the webcam, it errors out. VIDIOC_S_INPUT: failed: Inappropriate ioctl for device ioctl: VIDIOC_ENUM_FMT Type: Video Capture Multiplanar [0]: 'NM12' (Y/UV 4:2:0 (N-C)) It seems anything relying on v4l2 is also failing to work. Anyone have ideas of what the issue may be? Thanks! ---------------------- FYI...If I use this webcam on a RaspberryPi 4 running Bookworm, it produces the following output and all v4l2 work. Video input set to 0 (Input 1: Camera, ok) ioctl: VIDIOC_ENUM_FMT Type: Video Capture [0]: 'YUYV' (YUYV 4:2:2) [1]: 'H264' (H.264, compressed) [2]: 'MJPG' (Motion-JPEG, compressed)

Hello. I have been struggling with creating a local build environment that will be guaranteed to work today, next month, next year etc. My hardware is Radxa-Zero and I want to run kernel 6.1.23. Currently I find that the build environment, in various ways, breaks the build over time. I've been chasing a stable build for kernels 6.1.23, 57, 58, 59. The build environment, by default, grabs the latest 6.1.y kernel, which is no good for me. My root FS and DTB are for 6.1.23 and I don't want to keep updating everything just because I need to make some kernel configuration changes. I have tried the BSPFREEZE and OFFLINE_WORK build options but the build environment still goes online to update various files, breaking the build over time: ./compile.sh build BOARD=radxa-zero BRANCH=current BUILD_DESKTOP=yes BUILD_MINIMAL=no DESKTOP_APPGROUPS_SELECTED='3dsupport browsers chat desktop_tools editors email internet multimedia office programming remote_desktop' DESKTOP_ENVIRONMENT=xfce DESKTOP_ENVIRONMENT_CONFIG_NAME=config_base RELEASE=jammy KERNEL_CONFIGURE=no KERNEL_KEEP_CONFIG=no BSPFREEZE=y OFFLINE_WORK=y INSTALL_HEADERS=y CREATE_PATCHES=no I am using this override in meson64_common.inc case $BRANCH in current) declare -g KERNEL_MAJOR_MINOR="6.1" # Major and minor versions of this kernel. For mainline caching. #KERNELBRANCH='branch:linux-6.1.y' KERNELBRANCH='tag:v6.1.23' KERNELPATCHDIR='meson64-current' ;; ... But, I've tried that in the past and I have found that the build environment still updates various patches etc., that eventually results in build errors. I also tried to get the files from the latest tag (23.02.0-trunk.0256). The idea was that a tag would be stable and never change. Unfortunately, that build failed for Radxa Zero (network driver issue). git clone --depth=1 -- branch=23.02.0-trunk.0256 https://github.com/armbian/build So, what is the 100% certain way to arrive at a local build environment that will work forever? Thank you. /John.

Yakov, Why do you list Armbian 23.5 Jammy as a supported load on https://www.armbian.com/radxa-zero/ Armbian 23.5 Jammy works on the 2G version of the Radxa Zero board. Armbian 23.5 Jammy does NOT work on 1G version of Radxa Zero. (and presume the .5G version) - Boot failure loop after identifying boot device on 1G version of Radxa Zero. Has this been fixed? In which version? Where do we find it? Armbian_22.08.0-trunk_Radxa-zero_bullseye_current_5.10.134_minimal.img.xz works on 1G version of Radxa Zero. - https://github.com/radxa-build/radxa-zero/releases/tag/20220801-0213

Hi, Like the title says the UART overlays are not working on the armbian radxa zero device if I use the official out-of-the-box image. Using the armbian-config I can enable UART A and B but these changes do not reflect in the /dev/tty devices (using other distros is can see /dev/ttyAML0, /dev/ttyAML1 and /dev/ttyAML4). Unless the devices are called something else i confirm that the overlays are not working. That being said I want to recompile a armbian image with the correct overlays but I am a complete noob. Here is my plan : i successfully compiled a minimal cli armbian image for the radxa zero without any modification (whooohoo) i found the overlays from the official radxa github (whooohoo) : https://github.com/radxa/overlays/blob/main/arch/arm64/boot/dts/amlogic/overlays/README.overlays Now i want to include these overlays in the armbian project so that they can be compiled in the image. Reading the documentation i think that i need to include these files somewhere in the package directory: or somewhere in the config directory I also think I need to include some compiling instructions. I feel like I'm so close but at the same time, I feel like I'm so far. Any direction is very much appreciated. Thank you ps the board is officially supported but I can't find the appropriate topic.

If I connected the serial port with my device through GPIO pin 8 and 10 (UART_AO_A_TXD, UART_AO_A_RXD), the Radxa Zero with " Armbian 23.02.2 Jammy" failed to boot. If I removed my device from the serial port, zero can boot. After booting, I connected my device to the UART port, it worked well through /dev/ttyAML0. Any suggestions? Many thanks!

I am trying to use radxa-zero with HDMI CEC support on Armbian debian. I tried all different Armbian debian versions, lsmod never give me module cec So I took a look at images provided by radxa (https://github.com/radxa-build/radxa-zero/releases/tag/20220801-0213, not armbian ones), cec is loaded by default I think this is the key: /lib/modules/SOME_KERNEL/kernel/drivers/media/cec/core/cec.ko This is in their image but not /lib/modules/6.1.11-meson64 folder (I guess also not in other kernel versions) If that's the case, CEC should not work on any meson64 devices. I saw CONFIG_CEC_CORE=y is in config. btw, another possible related missing module is meson_dw_hdmi.ko Could someone take a look and figure out why they are not there? Really appreciate your help!

I'm having trouble enabling UART_B on my Radxa Zero Ver 1.51 board using "Armbian 23.02.2 Jammy" The idea is to connect a GPS, I had already done this with a Raspberry Pi Zero and it worked fine but I need more CPU capacity and that's why I switched to this board. Has anyone had experiences to enable these serial ports? Thanks

So far I've tried several images, just wanted to update what has and hasn't worked. I know the rz isn't officially supported but I thought I'd give my feedback and maybe it will help someone. All images were written to emmc after first using the radxa-zero-erase-emmc.bin tool to erase and mount emmc as USB storage. Armbian_22.05.0-trunk_Radxa-zero_bullseye_current_5.10.113_minimal - doesn't boot radxa-zero-ubuntu-focal-server-arm64-20220501-0334-mbr - boots but just goes straight into login screen, no option to change password. root and 1234 do not work. Also no armbian_first_run.txt.template included in the image Armbian_22.02.3_Radxa-zero_jammy_edge_5.15.32_xfce_desktop - doesn't boot Armbian_22.02.3_Radxa-zero_focal_current_5.10.109_cinnamon_desktop - doesn't boot Armbian_22.02.3_Radxa-zero_bullseye_current_5.10.109 - doesn't boot Armbian_22.02.3_Radxa-zero_focal_current_5.10.109_xfce_desktop - doesn't boot Armbian_22.02.3_Radxa-zero_jammy_edge_5.15.32 - doesn't boot I have a couple of zeros so I went back and forth between the two testing the images. Used DD and Gnome Disks, neither had any luck. Currently running DietPi which seems to be doing well. CoreElec runs good too.

I need a UART in my work. Added uartC overlay via armbian-config (UART_EE_C - /dev/ttyAML4) However, after booting, the device /dev/ttyAML4 does not appear. The download log contains the following information: Using the kernel-provided DT meson-uartC.dtbo overlay fdt_overlay_apply() error: FDT_ERR_BADMAGIC base fdt has no node /__symbols__ make sure you compile with -@ Error applying DT overlays, restoring original DT I would be grateful for any help!

Hi everyone, I'm using Radxa Zero HW version 1.4, 4GB RAM with 64GB eMMC. I used long time armbian on SD card. I decided to install MMC for better performance but armbian crashes APT involving stuffs. By the way, I'm using Rzero with headless and connecting via SSH from Win11 machine. I installed with producer tools directly writing image to MMC and alternatively installed with armbian-config tool from SD card to MMC. In both way successfully boots and connects Wi-Fi. For better diagnostic, how can I get error dump? (I lost SSH connection when its crushed).

USB gadget mode does currently not work OOTB on Armbian, but it can be enabled easily with a device tree change or overlay: /dts-v1/; /plugin/; / { compatible = "radxa,zero", "amlogic,g12a"; fragment@0 { target = <&usb>; __overlay__ { dr_mode = "otg"; }; }; }; I can open a PR for adding this as device tree overlay, or enabling OTG OOTB on Radxa Zero, like vendor did: https://github.com/radxa/kernel/commit/775a467 The latter would be simple. In case of an overlay, I'd need some hint about how to do it best: Adding it to the general meson64 overlays patch seems to be right: https://github.com/armbian/build/blob/master/patch/kernel/archive/meson64-6.0/general-meson64-overlays.patch But how to prefix or set `compatible` attribute best to assure it can be applied, resp. make clear that it works on Radxa Zero only (as state of testing)?

Hello everyone, I am evaluating the purchase of an SBC (the Radxa Zero seems to be the best equipment, power / consumption) for one of my projects, but I cannot find reliable sources regarding the consumption of the SBCs. Have any of you carried out extensive tests?

Hi everyone, I have Radxa Zero 4GB-64GeMMC model. I'm using latest Armbian (22.05.3) on microSD card. I want to connect my portable SSD (500GB) to RZ with USB3.0 hub that has additional power imput to support energy hungry devices. I checked usb hub is working with 16GB usb flash. My ssd use realtek RTL9210 chip. I also get similar problem with 32gb mSD card formatted with FAT32. When I connected the SD card reader, other device that uses same hub become slaggish and do not working properly. If I unplag sd card or ssd everything back normal. I thing there is a driver problem. Radxa Zero Diagnostic Dump

Hi, I have a Radxa Zero 4+64 GB model SBC. I saw new Xiaomi 4k tv stick and it has Amlogic S905Y4 and it has similar performance to S905Y2. I wonder when radxa zero will get h/w acceleration to use all potential of SoC. If there is already got h/w acceleration support, I'm sorry for writing this questions. I tried radxa debian (official), manjaro and armbian images. All of them not able to play videos smoothly in firefox. Thanks for all replies.

Hi Dear Friends I have Sunvell R69 New version with Ram2 G Official Frimware IS android IS 10 I tested H3-R69-MXQ-S-MXQ4K-8PD3-1.1.4 This frimware Wifi and Sound Not Working Tested T3CH-ASSIS_H3_Stock Rom R69-H3-Allwinner_T3CH-ASSIS All Rom Wifi and Sound Not Working Any Fimware For Share With me ??? To fix this Problem ???? please Help ?