Active threads

Thank you for your reply Igor, I have not changed anything, its using the same power supply it has been using for the past years! I had the SSH terminal open on it and just saw this random output: Message from syslogd@nanopim4v2 at Jul 24 20:22:20 ... kernel:[169328.590321] Internal error: Oops: 0000000096000004 [#2] PREEMPT SMP Message from syslogd@nanopim4v2 at Jul 24 20:22:20 ... kernel:[169328.616489] Code: 54000088 14000011 f9400273 b40001f3 (b9401a63) Not sure if it helps, but afterwards I took a new armbian-monitor capture: https://paste.armbian.com/huzanoyifi

I Know this thread is old but i installer buster on my rk3318 box and the media-buster-legacy-rk3328 package does not exist anymore does anyone have a archive of it

Can you tell me the axp### numbers on the chip? I can’t see it in your pictures. Try these images.. maybe you’ll find one that boots https://github.com/NickAlilovic/build/releases/tag/20250306

Stable images are produced every three months. Development builds are produced at least weekly depending on the support status.

You are most likely fine. But out of curiosity can you run the following: apt list --installed | grep armbian

I need a Linux image for this model that works with Wi-Fi and internal memory. No graphical interface.

Sensor integration: buy a OBD2 to USB adapter and study the OBD2 codes to read the fuel liters/hour, km and km/h. It is very possible there is a python OBD2 library. The SBC should be running continuously in the vehicle, since the car electronic control unit does not have the memory to store the information for you. Python+tkinter/pyqt6+matplotlib is very effective for this kind of apps.

yaeh, thanks very much .... i just flashed the armbian image to the sdcard copied the base img also on the sd card booted into than dd'ed the copied img to the /dev/mmcblk0 checked the partitions rebooted with removed sdcard and it works !!!

https://docs.armbian.com/Process_CI/

this is posted to Gist: https://gist.github.com/ag88/65db5434158683e43d1cc77c337ebdb5 Introduction Rpi-monitor https://github.com/XavierBerger/RPi-Monitor is a very nice app for monitoring sbc (single board computers/ actually bigger computers as well) like RPi on a web. it gives you a quick look at various system metrics cpu load, uptime, temperatures etc and more on a nice web page. and on top, makes nice time series graphs for the same, practically a dashboard. Installing in Armbian 25.8 for Orange Pi Zero 3 Rpi-monitor is normally not found in the common Apt repositories and actually the binary is a little old. I tried installing it based on the 'formal' docs but hit some invalid public keys errors, possibly expired certs. https://xavierberger.github.io/RPi-Monitor-docs/11_installation.html so here is a 'workaround' Deb packages for rpi-monitor you can find the packages in this repository (note that this may not be permanant and may change) https://github.com/XavierBerger/RPi-Monitor-deb use the **rpimonitor_latest.deb** file https://github.com/XavierBerger/RPi-Monitor-deb/tree/develop/packages install rpimonitor_latest.deb in Armbian use apt to install *rpimonitor_latest.deb* as it has varous package dependencies. e.g. download it to a folder and from there run sudo apt install ./rpimonitor_latest.deb the prior step should install rpimonitor, and check that the service is running by going to http://your_sbc_ip_address:8888 checking the setup rpi-monitor is runa as a systemd (unit) service if it is not running you can try systemctl status rpimonitor.service or journalctl -u rpimonitor.service to check what went wrong. to start / stop rpi-monitor it is as per basic systemd services e.g. systemctl start rpimonitor.service temperature 'not displaying' apparently, it is affected by this issue: https://github.com/XavierBerger/RPi-Monitor/issues/374 accordingly the fix/'workaround' is edit /etc/rpimonitor/template/temperature.conf replace #dynamic.1.postprocess=sprintf("%.2f", $1/1000) dynamic.1.postprocess=$1/1000

->a bit off topic<- Okay, if you have enough time, you can play around with PXVIRT (formerly the Proxmox port). 🙂 (https://github.com/jiangcuo/pxvirt) It's like Proxmox for ARM64 devices. I've been playing around with an 8 GB Raspberry Pi 4 with a 256 GB USB SSD lying around. In short: I installed a self-made minimal image (RPi4b). Installed PXVIRT (https://docs.pxvirt.lierfang.com/en/installfromdebian.html) Created some LXC containers (e.g., Lyrion Media Server, Heimdall, Pihole, Portainer, etc.) Created a virtual machine (Bookworm with OMV) Created a virtual machine with HAOS / -> bash -c "$(wget -qLO - https://github.com/community-scripts/ProxmoxVE/raw/main/vm/pimox-haos-vm.sh)" It's been running perfectly stable for 56 days now. 👍 Okay, it wasn't easy to set up and compile all the software components, but it's running perfectly. I plan to buy an Orange Pi 5 Plus with 32 GB RAM for these tasks next time. Regards, Markus

Colleagues, in order to fully cover the topic and make it easier to diagnose such problems in the future, please tell us what methods and where to look for information/logs about Wayland failures.

I have tested this on a NanoPi R5C as well as on NanoPC-T6 (non-LTS). For the later I also tested a vender provided Kernel / OS Installation. What happens is that whenever some Power-Saving is requested, the board will seemingly fully power down and is not responsive to anything, at best the reset button will do its work, R5C requires a power-cycle. The last kernel msgs are these (see https://www.kernel.org/doc/Documentation/power/states.txt😞 # echo freeze > /sys/power/state [ 54.373374] PM: suspend entry (s2idle) [ 54.671033] Filesystems sync: 0.297 seconds [ 54.775176] Freezing user space processes [ 54.780065] Freezing user space processes completed (elapsed 0.004 seconds) [ 54.780769] OOM killer disabled. [ 54.781078] Freezing remaining freezable tasks [ 54.782928] Freezing remaining freezable tasks completed (elapsed 0.001 seconds) [ 54.791332] r8169 0002:01:00.0 wan1: Link is Down I am at a loss how to diagnose this further. To me it appears that there is some vital power-source to CPU or RAM switched off.

Hi every one, Do we have a fix for bluetooth?

Try to experiment with this value: https://github.com/armbian/build/blob/main/patch/kernel/archive/rockchip64-6.6/board-rockpro64-0001-Add-pcie-bus-scan-delay.patch As this is pulled to DT, you only need to recompile DT - on board.

Is it just modifying the dtb? I was reading and I understand that means decompiling to dts and then recompiling but what edits would I have to do to enable eMMC?

@Error1429 If you were to submit a well thought out PR along with the necessary doc and website updates, I'm sure this would be accepted and incorporated. But I think the feedback thus far as that this isn't something of high enough priority to ever being incorporated with Armbian's very limited resources.

Hello, thank you for these clear instructions. Could you tell me where could I find the zip file?, it seems the link if broken. Thank you

@eselarm I agree with you, it's a fabulous device. And like you, hours after the post, I realized that I only need a VM host. I was thinking about the M6, but why get stuck with Windows ARM when Debian and Android also work on Intel? These bonsai devices are really appealing, but for now I've returned it to Amazon. I bought it as a gateway-media server, to have priority on the LAN and lighten Android TV, but I realized that with MediaTek there is a huge gap in network management, so I put it on the LAN, and Debian in VNC was running strong, I wanted to speed it up with Armbian. Apart from the fact that they call their community “third parties,” it still seems like a good idea to me. I could install the generic Arm64-xfce with mesa-vpu... engineering-wise, it's incredible in 6 square centimeters, but an i7 tower is more convenient for VMs.

Hi i want to know if it’s possible to connect a raxda rock 5B with armbian on a touch screen Joy-it LCD10 V2 Module écran tactile 25.7 cm (10.1 pouces) 1280 x 800 Pixel by usb and hdmi ?

Hi everyone! I have v25.8 rolling for radxa cubie a5e running Armbian Linux 6.14.0-rc1-dev-sun55iw3 runnig and it has only ttyS0 serial device. Due to device schematics it should be able to provide serail interfaces with RTS/CTS support UART4-7. Was anyone able to activate this devices? As I understand, I need an overlay .dtbo files. But those cannot be found anywhere in /boot. Also I can compile those overlays, but I need the correct .dts files.

It all depends on what version or variant of OS you are using. I have a R6C and have done many fixes and workarounds for various OSses/distros to the point that I just maybe take what generic upstream kernel does. I anyhow change/fake MAC addresses as I use bridges and also VLANs. Is in Armbian Bookworm and Opensuse Tumbleweed. Ubuntu based has and extra netplan layer that is even more a PITA as it keeps .nmconnections file also in another place (generated) then /etc/NetworkManager/system-connections/ Recently a change in scripting has been done so that name 'wan' is/or has been changed into 'wan1', so at least this does not match what is printed on the metalcase. At least that is what I remember from a quick check on github; See what is in your udev rules scripts yourself. https://github.com/armbian/build/blob/main/config/boards/nanopi-r6s.conf

I also needed a desktop on my Orange Pi Zero 2. I installed an "Armbian 25.5.1 Bookworm Minimal / IOT", then installed an XFCE desktop using some short guide I found on the Internet: sudo apt install lightdm xfce4 xfce4-goodies xorg After a reboot, my desktop started without any additional configurations. It's so good that now I have a new system with a desktop on my old hardware, which doesn't provide fresh OS images anymore.

Good news! I have finally built a new image (v0.7). It uses the v2025.07 u-boot from the 'orangepi5-pro-uboot' branch, and now the eMMC is working correctly. (Thanks to @salas for testing!)

I also tried sudo dd if=official_rock5t_image.img of=working_idbloader.img bs=512 skip=64 count=8000 sudo dd if=official_rock5t_image.img of=working_u-boot.itb bs=512 skip=16384 count=8000 sudo dd if=working_idbloader.img of=armbian_image.img bs=512 seek=64 conv=notrunc sudo dd if=working_u-boot.itb of=armbian_image.img bs=512 seek=16384 conv=notrunc then burn the img into the SD card, also be able to boot. I got the official image from https://github.com/radxa-build/rock-5t/releases but there's another issue, the hardware acceleration does NOT work in armbian, Mali-G610 is not in use