All Activity

@Werner https://paste.armbian.com/izobaqaguk here the link So do you think docker cannot run well on this device?

Make sure that the octoprint project still supports 32 bit CPUs For low ram sbc's, I suggest doing a classic installation, instead of Docker You can skip the webcam portion installation, and give you no problems. I had my opiz LTS (512MB) running octoprint last year, and the webcam function works well... but I only used octoprint-Docker when I had 2GB of RAM server.

moved Providing logs with armbianmonitor -u helps with troubleshooting and significantly raises chances that issue gets addressed.

What CPU does your box have? This should be filed under the corresponding CPU archtecture sub forum.

Hi, I installed on my Orange Pi Zero (not plus) armbian and using armbian-config I am trying to install Octoprint to control my 3d printer. I got an error: docker: Error response from daemon: error gathering device information while adding custom device "/dev/video0": no such file or directory I have no webcam attached and I am not planning to use it for now, Can I disable this check?

Hello everyone! I have a TVBox Tanix V2 with Debian Trixie installed. I'd like to know if I can use /dev/ttyS0 to connect a zigbee coordinator? He doesn't seem to be doing anything. tvbox:/#lsof -n | grep /dev/ttyS0 lsof: no pwd entry for UID 1883 [ 0.000899] printk: legacy console [tty0] enabled [ 0.257827] fe07a000.serial: ttyS0 at MMIO 0xfe07a000 (irq = 14, base_baud = 1500000) is a meson_uart This is what is available from the console. Thanks in advance!

the issue is as follows: 1. When using the Type-C interface to connect to an external monitor, the display works normally if the monitor is connected after the development board has started. 2. If the monitor is disconnected and then reconnected after approximately several hours (possibly more than 6 hours), the display fails to show any image. I used the `armbianmonitor -u` command, and it output the following URL. https://paste.armbian.com/foyecusoju If the Type-C interface is functioning normally, the latest output from `dmesg -w` would show the following: [ 1155.922647] xhci-hcd xhci-hcd.15.auto: xHCI Host Controller [ 1155.922692] xhci-hcd xhci-hcd.15.auto: new USB bus registered, assigned bus number 7 [ 1155.922885] xhci-hcd xhci-hcd.15.auto: hcc params 0x0220fe64 hci version 0x110 quirks 0x0002008002010010 [ 1155.922937] xhci-hcd xhci-hcd.15.auto: irq 116, io mem 0xfc000000 [ 1155.923133] xhci-hcd xhci-hcd.15.auto: xHCI Host Controller [ 1155.923152] xhci-hcd xhci-hcd.15.auto: new USB bus registered, assigned bus number 8 [ 1155.923173] xhci-hcd xhci-hcd.15.auto: Host supports USB 3.0 SuperSpeed [ 1155.923455] usb usb7: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 6.01 [ 1155.923476] usb usb7: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 1155.923491] usb usb7: Product: xHCI Host Controller [ 1155.923502] usb usb7: Manufacturer: Linux 6.1.115-vendor-rk35xx xhci-hcd [ 1155.923515] usb usb7: SerialNumber: xhci-hcd.15.auto [ 1155.924750] hub 7-0:1.0: USB hub found [ 1155.924811] hub 7-0:1.0: 1 port detected [ 1155.925434] usb usb8: We don't know the algorithms for LPM for this host, disabling LPM. [ 1155.925607] usb usb8: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 6.01 [ 1155.925625] usb usb8: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 1155.925638] usb usb8: Product: xHCI Host Controller [ 1155.925649] usb usb8: Manufacturer: Linux 6.1.115-vendor-rk35xx xhci-hcd [ 1155.925660] usb usb8: SerialNumber: xhci-hcd.15.auto [ 1155.928950] hub 8-0:1.0: USB hub found [ 1155.929019] hub 8-0:1.0: 1 port detected [ 1156.590377] rockchip-vop2 fdd90000.vop: [drm:vop2_crtc_atomic_enable] Update mode to 3840x2160p60, type: 10(if:DP0, flag:0x0) for vp2 dclk: 533120000 [ 1156.590574] rockchip-vop2 fdd90000.vop: [drm:vop2_crtc_atomic_enable] dclk_out2 div: 2 dclk_core2 div: 2 [ 1156.590639] rockchip-vop2 fdd90000.vop: [drm:vop2_crtc_atomic_enable] set dclk_vop2 to 533120000, get 533119995 [ 1156.621808] dw-dp fde50000.dp: full-training link: 4 lanes at 5400 MHz [ 1156.635430] dw-dp fde50000.dp: clock recovery succeeded [ 1156.644918] dw-dp fde50000.dp: channel equalization succeeded [ 1156.657348] rockchip-vop2 fdd90000.vop: [drm] vop enable intf:200 [ 1157.337766] dw-dp fde50000.dp: test_type0 is not support [ 1157.339516] dw-dp fde50000.dp: test_type0 is not support [ 1159.801886] usb 7-1: new high-speed USB device number 2 using xhci-hcd [ 1159.942247] usb 7-1: New USB device found, idVendor=1a40, idProduct=0101, bcdDevice= 1.11 [ 1159.942271] usb 7-1: New USB device strings: Mfr=0, Product=1, SerialNumber=0 [ 1159.942278] usb 7-1: Product: USB 2.0 Hub [ 1159.978762] hub 7-1:1.0: USB hub found [ 1159.978833] hub 7-1:1.0: 4 ports detected [ 1160.375255] usb 7-1.3: new full-speed USB device number 3 using xhci-hcd [ 1160.583425] usb 7-1.3: New USB device found, idVendor=222a, idProduct=0001, bcdDevice= 0.02 [ 1160.583438] usb 7-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 1160.583441] usb 7-1.3: Product: ILITEK-TP [ 1160.583443] usb 7-1.3: Manufacturer: ILITEK [ 1160.653326] input: ILITEK ILITEK-TP as /devices/platform/usbdrd3_0/fc000000.usb/xhci-hcd.15.auto/usb7/7-1/7-1.3/7-1.3:1.0/0003:222A:0001.0005/input/input26 [ 1160.708695] input: ILITEK ILITEK-TP Mouse as /devices/platform/usbdrd3_0/fc000000.usb/xhci-hcd.15.auto/usb7/7-1/7-1.3/7-1.3:1.0/0003:222A:0001.0005/input/input28 [ 1160.709353] hid-multitouch 0003:222A:0001.0005: input,hiddev97,hidraw2: USB HID v1.10 Mouse [ILITEK ILITEK-TP] on usb-xhci-hcd.15.auto-1.3/input0 If it is not functioning normally, it will not output any content.

Hello everyone, I'm trying to get an ST7735S LCD display working with my Orange Pi Zero 2 (H616). This setup was working correctly with older Armbian kernels, but after a recent update, I can no longer get the SPI device to appear. I have already tried a couple of different configuration methods without success. System Information: Board: Orange Pi Zero 2 (H616) Display: ST7735S (SPI) Kernel Version: Linux orangepizero2 6.12.43-current-sunxi64 #2 SMP Wed Aug 20 16:30:58 UTC 2025 aarch64 GNU/Linux I have recently updated armbian-config by running the update from the script itself. Attempt 1: Using armbianEnv.txt My first attempt was to edit /boot/armbianEnv.txt and add the required overlays. Here is my configuration: verbosity=1 bootlogo=false console=both disp_mode=1920x1080p60 rootdev=UUID=aef396b8-ac79-477c-b797-466fc4d881a6 rootfstype=ext4 overlays=sun50ih616spidev1_0 sun50ih616spidev1_1 sun50ih616spispidev sun50ih616tft35_spi usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u After rebooting with this configuration, the device nodes are not created. The output of ls /dev/spidev* is empty. Attempt 2: Using a custom user overlay Next, I tried creating a custom Device Tree Overlay. I created the file /boot/overlay-user/sp1-spidev.dts with the following content: /dts-v1/; /plugin/; / { compatible = "allwinner,sun50i-h616"; fragment@0 { target = <&spi1>; __overlay__ { status = "okay"; pinctrl-names = "default"; #address-cells = <1>; #size-cells = <0>; spidev@0 { compatible = "spidev"; reg = <0>; spi-max-frequency = <50000000>; }; }; }; }; I then added sp1-spidev to the overlays line in armbianEnv.txt. This method seems to be partially working. After a reboot, I can see the SPI master controller: $ ls /sys/class/spi_master/ spi0 spi1 However, the spidev device is still missing. ls /dev/spidev* is still empty. Diagnostic Information Here is the output of dmesg filtered for "spi". It seems to refer to spi0, not spi1 which I am trying to configure, but I'm including it for completeness. $ dmesg | grep -i spi [ 2.821043] spi-nor spi0.0: supply vdd not found, using dummy regulator My Question I don't understand why the /dev/spidev* device is not being created, even when the spi1 master appears to be correctly enabled via the overlay. It seems like the spidev driver is not binding to the device. Since this worked on older kernels, has the method for enabling SPI devices changed? What is the correct procedure now? Is there something I'm missing in my overlay file or configuration? Thank you for your help

@laibsch thank you for reaching out. I apologize for the delay in responding. I want to inform you that I am actively seeking assistance from the community and am willing to contribute by developing code to address the issues I've observed on this board. However, despite my efforts to engage with the community, I have not received any responses and am not sufficiently experienced to thoroughly troubleshoot and resolve these problems on my own. Although I have some knowledge of programming languages, I am not well-versed in Linux. For example, this morning, I suggested a potential solution to the Bluetooth issue on the IRC channel but received no feedback. For the GPU, it appears that acceleration is now present, as the CPU is no longer at 100%. However, I am unable to set the resolution to 4K without encountering screen artifacts, and I can only achieve Full HD resolution.

Next week, Collabora will be taking part in the 2025 edition X.Org Developer's Conference! Taking place in Vienna, our engineers will be presenting 6 talks and a workshop to help local students discover the embedded graphics stack! Join us! View the full article

@blood like a charm dude

Kernel packages comes from the same (main) repository. This won't cause you problems, if you upgrade from bookworm to trixie, but we can't guarantee for packages that comes from Debian. You might try this way: https://docs.armbian.com/User-Guide_Armbian-Config/System/#stable-distro-upgrade Note that you might need to download updated Armbian key: wget -qO - https://apt.armbian.com/armbian.key | gpg --dearmor | \ sudo tee /usr/share/keyrings/armbian.gpg > /dev/null cat << EOF | sudo tee /etc/apt/sources.list.d/armbian-config.sources > /dev/null Types: deb URIs: https://github.armbian.com/configng Suites: stable Components: main Signed-By: /usr/share/keyrings/armbian.gpg EOF

About a year ago, I installed the OpenMediaVault image for CM3588-NAS from here: https://www.armbian.com/nanopc-cm3588-nas/ The image is debian-bookworm, which has since become oldstable, while trixie is the new stable. Is it possible to upgrade the distribution and move to trixie packages, even though there are no trixie images for CM3588-NAS? In theory this seems completely feasible as my apt configurations seem completely standard with something like deb http://deb.debian.org/debian bookworm main contrib non-free non-free-firmware and deb [signed-by=/usr/share/keyrings/armbian.gpg] http://apt.armbian.com bookworm main bookworm-utils bookworm-desktop If I attempt the upgrade, will I run into problems with some packages (like armbian-bsp-cli-cm3588-nas-vendor or linux-image-vendor-rk35xx) not actually existing for the target release and platform and just end up bricking my system?

Hard to tell without any logs whatsoever In general it works on x86 since a few month ago I used it to move the OS from an old NUC-like pc from sd to built-in emmc which was flawless (besides I had to get rid of Ventoy since it messes up Armbian boot).

has any progress been made toward fixing this

here is my dts for android rkr7.1 sdk 6.1.141 with everything working usb2 host usb3 otg/host hdmi ethernet 3.5mm spdif IR + wakeup wifi BT collect info for adding your remote to dts echo 1 > /sys/module/rk_pwm_remotectl/parameters/code_print m9.dts

Hi @jock, Thanks for suggestion, led me to dig down and found your update on R29 GPIO. Since multitool hdmi was working, I used it's bash to mount emmc and add overlays=led-config7 to armbianEnv.txt. It worked!!!! Thanks a lot for all your contribution!

thanks, it works - with a lot of time on google 😉 can you say why the armbian-install script dont work? A bug or a bad constellation of hardware e.g.?

login via ssh

Hi @fabiobassa Thanks for your input. I believe this board has eMMC only—the storage chip is KLMAG1JENB-B041 (image attached, RAM visible too). Multitool also confirms eMMC when attempting to burn an image. Interestingly, CPU-Z shows Rockchip 3066 logo, while ADB reports RK3229. I trusted the ADB output more, and seeing Multitool running, I believe it’s an RK3229 only. I haven’t removed the heatsink yet to verify physically. I am attaching hardware report that i could extract using adb. Any idea why Multitool runs fine but no Armbian image boots? I’ve tried 2024 Ubuntu/Debian builds and a latest self-compiled Armbian image using Armbian Build, tried both flashing to eMMC and run from SD, including using the hidden button, nothing works—LED blinks, but no HDMI output. I really want to run linux on this Again thanks for all your contribution in the thread. Edit1- Attaching Multitool Dmesg too, if it helps. rk3229_hardware_profile.txt dmesg.multitool.log

@Kiranmoy Saha I guess you have a box with NAND , not emmc You must use an old image that supports nand , typiclly kernel 4.4.xxx and follow 1st post jump start on nand Any newer kernel doesn't have nand support

I don't know and I won't spend time investigating. We cannot provide support for 3rd party images/software. Moved to off-topic since OP is not using Armbian.

You just have to create the nginx folder in /var/log with owner www-data (it is not created automatically): mkdir /var/log/nginx chown -R www-data:www-data /var/log/nginx systemctl restart nginx

Hi @jock, Thanks for the quick response. I’ve opened the box and attached the board images. On the back it says R29-MXQ-V2.1-221#. Sorry if I’m missing something—I’m a beginner. I thought rk322x-config runs only after Armbian boots. In my case, after flashing the image to eMMC and removing the SD, the box just blinks LED with no HDMI output. Only Multitool runs fine from SD. How can I run rk322x-config in this situation? Thanks again.

These drivers should not differ much from each other, right? Anyway, I found a reasonable patch to fix this behavior. I couldn't see this in the Armbian kernel, but what I need is: patch.