Active threads

@Mateus Lima It Is not the first neither will be the last time that china manufacturers fake soc printing. Have a look on allwinner forum

It appears that the system control was not configured properly. In the default DTS the binding is "sun8i-a83t-system-controller" which appears to have been deprecated in favor of the suffix "system-control" from what I could find. So tested with "sun8i-a83t-system-control" and "sun8-h3-system-control" as a fall back option. This time we no complaints from Cedrus: ryzer@cubietruckplus:~$ sudo dmesg | grep cedrus [ 10.624985] sunxi_cedrus: module is from the staging directory, the quality is unknown, you have been warned. [ 10.652836] cedrus 1c0e000.video-codec: Device registered as /dev/video0 Second test was to ensure that the video-engine clocks are set correctly, which can be done by temporarily disabling driver suspension. ryzer@cubietruckplus:/sys/kernel$ sudo cat debug/clk/bus-ve/clk_enable_count 1 ryzer@cubietruckplus:/sys/kernel$ sudo cat debug/clk/ve/clk_enable_count 1 ryzer@cubietruckplus:/sys/kernel$ sudo cat debug/clk/dram-ve/clk_enable_count 1 Next test trying to get working which should be using the version of ffmpeg as detailed here: This is the current output of ffmpeg: ffmpeg version 5.1.7-0+deb12u1 Copyright (c) 2000-2025 the FFmpeg developers built with gcc 12 (Debian 12.2.0-14) configuration: --prefix=/usr --extra-version=0+deb12u1 --toolchain=hardened --libdir=/usr/lib/arm-linux-gnueabihf --incdir=/usr/include/arm-linux-gnueabihf --arch=arm --enable-gpl --disable-stripping --enable-gnutls --enable-ladspa --enable-libaom --enable-libass --enable-libbluray --enable-libbs2b --enable-libcaca --enable-libcdio --enable-libcodec2 --enable-libdav1d --enable-libflite --enable-libfontconfig --enable-libfreetype --enable-libfribidi --enable-libglslang --enable-libgme --enable-libgsm --enable-libjack --enable-libmp3lame --enable-libmysofa --enable-libopenjpeg --enable-libopenmpt --enable-libopus --enable-libpulse --enable-librabbitmq --enable-librist --enable-librubberband --enable-libshine --enable-libsnappy --enable-libsoxr --enable-libspeex --enable-libsrt --enable-libssh --enable-libsvtav1 --enable-libtheora --enable-libtwolame --enable-libv4l2 --enable-v4l2-request --enable-v4l2-m2m --enable-libvidstab --enable-libvorbis --enable-libvpx --enable-libwebp --enable-libudev --enable-libx265 --enable-libxml2 --enable-libxvid --enable-libzimg --enable-libzmq --enable-libzvbi --enable-lv2 --enable-omx --enable-openal --enable-opencl --enable-opengl --enable-sdl2 --disable-sndio --enable-libjxl --enable-pocketsphinx --enable-librsvg --enable-libdc1394 --enable-libdrm --enable-libiec61883 --enable-chromaprint --enable-frei0r --enable-libx264 --enable-libplacebo --enable-librav1e --enable-shared libavutil 57. 28.100 / 57. 28.100 libavcodec 59. 37.100 / 59. 37.100 libavformat 59. 27.100 / 59. 27.100 libavdevice 59. 7.100 / 59. 7.100 libavfilter 8. 44.100 / 8. 44.100 libswscale 6. 7.100 / 6. 7.100 libswresample 4. 7.100 / 4. 7.100 libpostproc 56. 6.100 / 56. 6.100 Hardware acceleration methods: vdpau vaapi drm opencl vulkan It is also worth mention that as there is no support for the SGX544 GPU, we are limited to a CLI only interface for which MPV can only be launched full-screen. MPV fails to use hardware decoding and falls back to using software. MPV version is reported as 0.35.1 [ 3.639][v][vo/gpu-next/opengl] Initializing GPU context 'drm' [ 3.643][e][vo/gpu-next] Can't handle VT release - signal already used [ 3.647][w][vo/gpu-next/opengl] Failed to set up VT switcher. Terminal switching will be unavailable. [ 3.651][v][vo/gpu-next/opengl] Initializing KMS [ 3.657][v][vo/gpu-next/opengl] Picked DRM card 0, primary node /dev/dri/card0 as the default. [ 3.662][v][vo/gpu-next/opengl] Driver: sun4i-drm 1.0.0 (0) [ 3.666][v][vo/gpu-next/opengl/kms] Connector 63 currently connected to encoder 62 [ 3.670][v][vo/gpu-next/opengl/kms] Selected Encoder 62 with CRTC 61 [ 3.675][v][vo/gpu-next/opengl/kms] Selected mode: 1920x1200 (1920x1200@60.00Hz) [ 3.679][v][vo/gpu-next/opengl] DRM Atomic support found [ 3.684][v][vo/gpu-next/opengl/kms] Using overlay plane 51 as draw plane [ 3.689][v][vo/gpu-next/opengl/kms] Using primary plane 57 as drmprime plane [ 3.693][v][vo/gpu-next] GBM_FORMAT_ARGB8888 not supported by draw plane: Falling back to GBM_FORMAT_XRGB8888. [ 3.697][v][vo/gpu-next] Supported modifier: 0x0 [ 3.702][v][vo/gpu-next] Creating GBM device [ 4.915][v][vo/gpu-next] Initializing GBM surface (1920 x 1200) [ 4.920][e][vo/gpu-next] Failed to create GBM surface. [ 4.924][e][vo/gpu-next] Failed to setup GBM. [ 5.397][v][vd] Container reported FPS: 30.000000 [ 5.405][v][vd] Codec list: [ 5.409][v][vd] h264 - H.264 / AVC / MPEG-4 AVC / MPEG-4 part 10 [ 5.414][v][vd] h264_v4l2m2m (h264) - V4L2 mem2mem H.264 decoder wrapper [ 5.418][v][vd] Opening decoder h264 [ 5.424][v][vd] Looking at hwdec h264-drm... [ 5.428][v][vd] Could not create device. [ 5.433][v][vd] No hardware decoding available for this codec. [ 5.437][v][vd] Using software decoding. [ 5.445][v][vd] Detected 8 logical cores.

It seems the Ethernet dirver is already in mainline, and oss wifi driver are available: https://github.com/lynxlikenation/aic8800

Those are images from BigTreeTech, not Armbian. Official Armbian images for CB1 are here: https://www.armbian.com/bigtreetech-cb1/ If you want to use vendor images, you should report your issue to BigTreeTech then.

Here: https://fi.mirror.armbian.de/oldarchive/helios64/archive/ you can find older images.

I’ve sent the URL and details here, hoping they can take a look

I recently noticed my ODroid XU4 was reporting weird temperature readings: cat /sys/class/thermal/thermal_zone0/temp -22000 Is this a software issue or maybe hardware failing? Also, I would like to upgrade, is there another board I could just transfer my EMMC to and be up and running? Thanks

@Jeeva Kandasamy correct

Out of curiosity, does it work if you drop my firmware build in place? dd bs=512 seek=1 conv=notrunc,fsync if=u-boot-meson.bin of=/dev/${entire-device-to-be-used} u-boot-meson.bin.tgz

Hey @Adrienne, Github thread talks about two to three ways to so solve the issue. Did you apply the one that removes the symlinks ?

A phandle is a magical number assigned during DTB assembly, whose value is irrelevant as long as it references the same node with the phandle property. The magic value can change when the structure changes because it is assigned arbitrarily; for example, by inserting an additional node.

In an XWindow environment, these are realistically expected numbers. In a Wayland environment, this is somewhat better; see glmark2-wayland-odroid-m1.log as a reference. But it is in no way comparable to a Mali G610; see glmark2-wayland-odroid-m2.log as a reference. Use WebGL Report to be sure.

debug boot issues: https://debug.armbian.de This board is community maintained, therefore Armbian core team does not monitor its status. May be broken, may not. We don't know.

@BipBip1981, can you please share again your feedback on fancontrol running on Trixie ? The site can't display the image.

He works as ili9341 and as ili9486. I use it now as ili9486. I`ll go further to make it work as native device. DRM frambuffer its something what needs to be kernel recompiled... as i know? And if i want to use it natively, i must edit or recompile u-boot.... DRM support for ILI9486 display panels modulename: ili9486.ko configname: CONFIG_TINYDRM_ILI9486 Linux Kernel Configuration └─>Device Drivers └─>Graphics support └─>Direct Rendering Manager (XFree86 4.1.0 and higher DRI support) └─>SPI support └─>DRM support for ILI9486 display panels In linux kernel since version 4.14.326 (release Date: 2023-09-23) DRM driver for the following Ilitek ILI9486 panels: * PISCREEN 3.5" 320x480 TFT (Ozzmaker 3.5") * RPILCD 3.5" 320x480 TFT (Waveshare 3.5") If M is selected the module will be called ili9486. I will use it for KlipperScreen 😆 But as i se how hard is working that orangePi PC,i`ll doubt if i need this... Any way i`ll try )) Yes. But HDMI not connected. On OrangePiOne image its switching. If HDMI is connected its use it with no output to SPI. But if no HDMI present its use SPI as basic overlay On the same board. Because OPiOne had only 1 usb, OPiPC work only 1 usb ))) if whey work all 3, i`ll didnt open up a topic 😑 ili9486.dts

I don't know if this relates, but I recently discovered an issue with a Debian Trixie file system package xfsprogs on the 25.8.1 edge kernel for the Orange PI 5 Plus: https://forum.armbian.com/topic/55599-bug-report-armbian-edge-kernel-6164-xfsprogs-trixie-package-failure-to-start-low-memory-monitorservice/

Hello, has anyone managed to get this camera to work on zero 3?

Hmmm. Never mind, maybe. I see that Armbian has it included here, but for some reason it was not installed automatically. https://github.com/armbian/build/tree/main/packages/bsp/odroid

Sorry for the late feedback. I was waiting for a new kernel update (6.12.54-bcm2711) to confirm it was all right. Just as what @Werner said, in the `/etc/initramfs/post-update.d/z50-raspi-firmware` contains snippets of the code that prints out the error. And it's indeed no actual harm. Also, without setting on-hold of the `raspi-firmware`, kernel updates works just fine. We are good. Thank you all!

If anyone in interested in a lightweight wayland desktop, inspired by openbox, you should try labwc. In orange pi zero 3, we need to stay in bookworm to get video acceleration, so this guide helps build labwc in bookworm As a greeter, I chose pi-greeter, because it is the lightest login manager I could setup, without any X11 https://github.com/robertojguerra/opiz3-labwc-setup I am open to read any improvements, or show me how I could make deb packages. In the near future, I will make a step-by-step video tutorial in Youtube.

For video acceleration, you need to stick with Bookworm.

I don't think you understand how Armbian works. This board is community supported. It does not and hasn't been an Armbian supported board. Given the hundreds of boards out there Armbian only has the resources to officially support a handful. The rest end up being supported by the user community like this board. Thus support is only as good as the community volunteers who have the board and wish to volunteer their time to support it. Armbian provides the tools and infrastruction to make supporting boards easier, but the work still needs to be done by someone for community supported boards like this.

Can I still find the image somewhere? I would like to run Armbian on my Jetson Nano 2 GB, but Armbian_community_25.11.0-trunk.367_Jetson-nano_trixie_current_6.12.54_minimal.img and older images won't boot. I have tried images repeatedly over the past six weeks, but none of them will boot. It would be a shame if the Jetson Nano 2 GB ended up as electronic waste.

Yep enabled the module and it's working now, Just sent a PR. Thank you.

@MeJune A523/T527 support still needs a lot of work. There is no HDMI support yet. So you will need to install a usb serial device to your uart to interact with your box. You can find details at the botton of the site you posted https://linux-sunxi.org/X96QPro%2B. You could try warpme minimyth2 or miniarch. He has the latest support for these boxes. I don't own a X96q pro+ so I can't help you.