Active threads

Thanks let me try that

Agreed. A check if the package is installed (and if not install it beforehand) would be sufficient too. PRs to fix this are highly appreciated. https://github.com/armbian/build/blob/main/packages/bsp/common/usr/bin/armbian-install

I suggest to retry later

We're aware that our documentation isn't great (also about adding new hw: https://docs.armbian.com/Process_Contribute/#adding-a-new-board) but it is hard to find time for such tasks when we're crowded with other stuff already. The file extension defines a boards support status. https://docs.armbian.com/User-Guide_Board-Support-Rules/ Anyone can add .csc boards. For dts files we have dedicated folders to avoid having a patch necessary for them: https://github.com/armbian/build/tree/main/patch/kernel/archive/rockchip64-6.12/dt https://github.com/armbian/build/tree/main/patch/kernel/archive/rockchip64-6.18/dt

I've seen this post before but the link is "404 Not Found" thats why i resorted to trying to build my own multitool and armbian hahahahahha @jock The post mentions this link: https://users.armbian.com/jock/web/rk322x/armbian/beta/Armbian-unofficial_24.11.0-trunk_Rk322x-box_noble_current_6.6.56_xfce_desktop.img.xz Is there a mirror?

@snow download balena etcher and flash the image onto a sdcard. This will boot armbian off the sdcard. Unless you use armbian-config and write to emmc you will be fine.

Any comments on this would be welcome.

You'll spend the money once. Then you'll have the result thereafter. I would suggest deciding what you want, then spending whatever it costs. Orange PI is "cheap", not just in price, but in hardware reliability as well as software support. I'm not aware of such issues with Radxa. RK3588 is more powerful than Raspberry PI, but as you say Raspberry PI has great community and support. Perhaps the question is - What do you need it for? Raspberry PI might be powerful enough for your needs.

I have an Orange PI 5 Plus, and both USB-C connectors (including the one used for power delivery) are faulty. Also the second HDMI output is corrupted. Clearly their manufacturer leaves a lot to be desired.

Modproble probes modules built into the kernel itself. An external package (other than the kernel itself) shouldn't affect it. If it was present via modprobe before, and not after, that isn't the zfs package, that would indicate a module that had been built into 25.8.1 kernel, then excluded from the 25.8.2 kernel build for some reason.

@Jeeva Kandasamy I haven't had that error before. Maybe your host is out of date. Have you tried "sudo apt update && sudo apt upgrade"?

sudo rm -rf /var/lib/apt/lists/* sudo apt clean sudo apt update sudo apt upgrade works for me.

Thank you for your quick answer, Jimbolaya. Yes, I did try different cables all with the same result. I wonder if there is another way to access the serial console, J13 perhaps? Albeit with some required soldering, I suppose. Then remains the question of which headers exactly relate to GND, TX and RX.

I noticed this problem a long time ago, but now I feel it is important to fix it: I get a slim black bar on the left side, and a portion of the pixels on the right get "cropped" because they don't fit in the LCD display area? Do you get the same in your LCD? Do you know a way to fix it? I am talking about this LCD: RED PCB LCD https://www.aliexpress.us/item/3256802847521952.html?

Update: It works now, however the power LED doesn't seem to light up, but the video card is detected in /dev

I have managed to successfully install Armbian onto the DELL Wyse3040 As mentioned above, the way to do this is to use a PE environment that works on these devices. I used an old version of Hiren's BootCD and booted from it. Then I used a NTFS formatted flash drive with the unzipped image and used Roadkill's Disk Image to write it to the eMMC And it works, beautifully

Hi - thank you for the nice driver. Here is my contrbute: Device under test : T9_RK3318 (T9 Sunwell 3318 version 4+32 GB) Running: v25.11 rolling for RK3318 Box running Armbian Linux 6.12.55-current-rockchip64 Packages: Debian stable (trixie) Support: for advanced users (rolling release) Some info: RK3318:~# lsmod | grep tm tm16xx 28672 0 stmmac_platform 20480 1 dwmac_rk stmmac 241664 3 stmmac_platform,dwmac_rk pcs_xpcs 28672 1 stmmac lsmod | grep i2c i2c_gpio 16384 0 i2c_algo_bit 12288 1 i2c_gpio ls /sys/bus/i2c/devices/ 5-0024 i2c-4 i2c-5 ls /sys/class/leds/display brightness device digits map_seg7 max_brightness num_digits num_segments power segments subsystem trigger uevent value ls -l /sys/class/leds/ total 0 lrwxrwxrwx 1 root root 0 Oct 26 11:53 display -> ../../devices/platform/i2c-display/i2c-5/5-0024/leds/display lrwxrwxrwx 1 root root 0 Oct 26 11:53 display::alarm -> ../../devices/platform/i2c-display/i2c-5/5-0024/leds/display::alarm lrwxrwxrwx 1 root root 0 Oct 26 11:53 display::colon -> ../../devices/platform/i2c-display/i2c-5/5-0024/leds/display::colon lrwxrwxrwx 1 root root 0 Oct 26 11:53 display::lan -> ../../devices/platform/i2c-display/i2c-5/5-0024/leds/display::lan lrwxrwxrwx 1 root root 0 Oct 26 11:53 display::pause -> ../../devices/platform/i2c-display/i2c-5/5-0024/leds/display::pause lrwxrwxrwx 1 root root 0 Oct 26 11:53 display::play -> ../../devices/platform/i2c-display/i2c-5/5-0024/leds/display::play lrwxrwxrwx 1 root root 0 Oct 26 11:53 display::usb -> ../../devices/platform/i2c-display/i2c-5/5-0024/leds/display::usb lrwxrwxrwx 1 root root 0 Oct 26 11:53 display::wlan -> ../../devices/platform/i2c-display/i2c-5/5-0024/leds/display::wlan lrwxrwxrwx 1 root root 0 Jan 1 1970 input3::capslock -> ../../devices/platform/ff600000.usb/xhci-hcd.0.auto/usb2/2-1/2-1:1.1/0003:248A:8208.0002/input/input3/input3::capslock lrwxrwxrwx 1 root root 0 Jan 1 1970 input3::compose -> ../../devices/platform/ff600000.usb/xhci-hcd.0.auto/usb2/2-1/2-1:1.1/0003:248A:8208.0002/input/input3/input3::compose lrwxrwxrwx 1 root root 0 Jan 1 1970 input3::kana -> ../../devices/platform/ff600000.usb/xhci-hcd.0.auto/usb2/2-1/2-1:1.1/0003:248A:8208.0002/input/input3/input3::kana lrwxrwxrwx 1 root root 0 Jan 1 1970 input3::numlock -> ../../devices/platform/ff600000.usb/xhci-hcd.0.auto/usb2/2-1/2-1:1.1/0003:248A:8208.0002/input/input3/input3::numlock lrwxrwxrwx 1 root root 0 Jan 1 1970 input3::scrolllock -> ../../devices/platform/ff600000.usb/xhci-hcd.0.auto/usb2/2-1/2-1:1.1/0003:248A:8208.0002/input/input3/input3::scrolllock lrwxrwxrwx 1 root root 0 Jan 1 1970 working -> ../../devices/platform/gpio-leds/leds/working Testing... echo "1234" > /sys/class/leds/display/value echo 1 > /sys/class/leds/display\:\:lan/brightness echo 1 > /sys/class/leds/display\:\:usb/brightness All the 7 functions and 4 digits are working and correctly associated. Also trigges are working. I still have this small bug which is stopping rolling messages: display-service -c [INFO] all digits and leds on /usr/sbin/display-service: 116: cannot create /sys/class/leds/display/message: Permission denied All the function leds reacts well (all on) but the four clock digits do not switch, most likey because of the message permission denied. However they do work writing directly in the "value" as above and in the picture. Edit: I have investigated a little and it seems that I am still using the tm16xx which came with the distribution, as depmod was failng. After a fresh recompile all your module load but nodes under "leds" are not there, it seems that the dtso/dtbo is not read - nothing appears in dmesg. Attached the working dtso file. rk3318-t9.dtso

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

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 ?