Active threads

Attaching the kernel log see if it helps. kern.log.1

Device Opi5-Plus Further info. With Kernel-6.18.20-current-rockchip64-26.2.0-trunk.640 headphone jack (analog) also does not have audio/sound output. With kernel-6.18.10-current-rockchip64-26.2.1 headphone jack (analog) has autio/sound output.

BTT since at least Buster provides in their vendor image a script to solve issues with the Wifi. And yes it in some conditions may have some issues with the network coming up, I even run in some issues with ethernet. They are solvable by restarting the networkdevice (either ethernet or wifi) with NetworkManager as well as with systemd-networkd. From history. The CB1 Buster vendor image from BTT as well as the vendor image for Bookworm, which actually you still can download at BTTs website contain a scrit that solves the issue by checking the network state all 5 seconds and in case restart the device. I personally used the vendor Buster image and the vendor Bookworm image on the CB1 to operate Openmediavault on it and believe me reliable Network is essential for a NAS. So yes those scripts work. I finally moved to the Armbian general Trixie image, just I was courious, but I took those scripts from bookworm with me. I even copied them to my "vault" of nice to have things for any device that needs reliable network. So I suggest to get yourself A vendor Bookworm image and loop mount it. No need to flash it. (if you are on Windoof, you need to flash it and have a look at the boot partition . At least I don't know a way to mount a partion inside a dd image of a blockdvice stored with sparse option.) Then have a look at the boot partion. There is a folder scripts. Interesing ther: /scripts/btt_init.sh /script/connect_wifi.sh what they do is, they start btt_init.sh in /etc/rc.local, which means always when the system boots at the very end of the boot process and btt init.sh starts a lot of those scripts in background mode, which meens if they have an endless loop, they never die. Only thing u need is connect_wifi.sh from there, so you can hash out all other or directly start connect_wifi.sh like they do.. #!/bin/bash # original BTT code, where the device name is set to a variable in the system.cfg: # cfg_file=/boot/system.cfg #enter the name of the wlandevice to check here: WLAN=wlan0 log_file=/boot/scripts/wifi.log IFS=\" sta_mount=0 wifi_path="/etc/NetworkManager/system-connections/" function connect_wifi() { # whether there is configured wifi in the history if [[ `sudo nmcli c s | grep wifi | awk '{ for(i=NF-2; i<=NF; i++){ $i="" }; print $0 }'` =~ "${WIFI_SSID}" ]] ; then set_wifi_path="${wifi_path}${WIFI_SSID}.nmconnection" if [[ -e ${set_wifi_path} ]]; then psk=`sudo cat ${set_wifi_path} | grep ^psk | awk -F '=' '{print $2}'` if [[ ${psk} == $WIFI_PASSWD ]]; then # both ssid & passwd matched. sys_now_wifi=`sudo nmcli c s --active | grep wlan0 | awk '{ for(i=NF-2; i<=NF; i++){ $i="" }; print $0 }' | awk '{t=length($0)}END{print substr($0, 0, t-3)}'` if [[ ${sys_now_wifi} != $WIFI_SSID ]]; then sudo nmcli c up ${WIFI_SSID} echo " ===> SSID & PSK is same as history, switch to: $WIFI_SSID " >> $log_file fi echo " ===> Now is: $WIFI_SSID, need not to do anything" >> $log_file return 0 else # psk don't match, remove and reconnect. sudo nmcli c delete ${WIFI_SSID} echo " ===> Remove all: $WIFI_SSID " >> $log_file fi else # remove all WIFI_SSID info (Theoretically, never execute to here). sudo nmcli c delete ${WIFI_SSID} echo " ===> Remove all: $WIFI_SSID " >> $log_file fi fi # connect to the new wifi if [[ `sudo nmcli device wifi list` =~ $WIFI_SSID ]] then if [[ ! `sudo nmcli dev wifi connect $WIFI_SSID password $WIFI_PASSWD ifname $wlan` =~ "successfully" ]] then echo " ===> Specify the WPA encryption method: $WIFI_SSID " >> $log_file sudo nmcli c modify $WIFI_SSID wifi-sec.key-mgmt wpa-psk sudo nmcli dev wifi connect $WIFI_SSID password $WIFI_PASSWD ifname $wlan fi else echo " ===> Hide wifi_ssid: $WIFI_SSID " >> $log_file sudo nmcli c add type wifi con-name $WIFI_SSID ifname $wlan ssid $WIFI_SSID sudo nmcli c modify $WIFI_SSID wifi-sec.key-mgmt wpa-psk wifi-sec.psk $WIFI_PASSWD sudo nmcli c up $WIFI_SSID fi } function Env_init() { exec 1> /dev/null # without check_interval set, we risk a 0 sleep = busy loop if [ ! "$check_interval" ]; then echo $(date)" ===> No check interval set!" >> $log_file exit 1 fi # enable wlan [[ $(ifconfig | grep $wlan) == "" ]] && sudo nmcli radio wifi on connect_wifi sleep 6 } function is_network() { if [ $# -eq 0 ]; then get_ip=`ip route | grep "$eth proto kernel" | awk '{print $9}'` if [ -n "${get_ip}" ]; then Result=yes else get_ip=`ip route | grep "$wlan proto kernel" | awk '{print $9}'` fi else get_ip=`ip route | grep "$1 proto kernel" | awk '{print $9}'` fi if [ -n "${get_ip}" ]; then Result=yes else Result=no fi echo $Result } function startWifi_sta() { sta_mount=`expr $sta_mount + 1` echo $(date)" .... sta connecting...$sta_mount..." >> $log_file sleep 2 } function startWifi() { [[ $(ifconfig | grep $wlan) == "" ]] && nmcli radio wifi on # 确保wlan连接启动了 if [[ $sta_mount -le 2 ]]; then nmcli device connect $wlan # 连接wifi echo $(date)" .... $wlan connecting..." >> $log_file sleep 2 [[ $(is_network $wlan) == no ]] && startWifi_sta [[ $(is_network $wlan) == yes ]] && sta_mount=0 && echo $(date)" [O.K.] $wlan connected!" >> $log_file else echo $(date)" xxxx $wlan connection failure..." >> $log_file fi } source $cfg_file grep -e "^WIFI_SSID" ${cfg_file} > /dev/null STATUS=$? if [ ${STATUS} -eq 0 ]; then Env_init sleep 20 while [ 1 ]; do if [[ $(is_network) == no ]]; then # 没有网络连接 echo -e $(date)" ==== No network connection..." >> $log_file startWifi sleep 6 # 更改间隔时间，因为有些服务启动较慢，试验后，改的间隔长一点有用 fi sleep $check_interval done fi This script assumes you are using NetworkManager to manga the wifi.. if you don't one can modify it for systemd-networkd also.. :-)

@andrey.lobov openvfd is a badly written old driver, currently there is already tm16xx driver in the kernel for led front panels. You should configure your board appropriately with rk3318x-config and will enable the front panel. If your board is not in the list, please provide photos of the board (back and front) and the dtb

Some sort of logs would be great, otherwise very hard to track down

I did not look well enough and also at a local PDF copy of the wiki which I see is more than 2 years old. Same text is there, but not in red at that time. I think I noticed it at the I was soldering the wire, but I clearly forgot the typing the message i this topic. Anyway, I have no good idea how to solve your remote power issue. I use a MOSFET that has low Vgs on (works directly on 3.3V , but is not for common GND. Else PoE managed switch where I can toggle power when fatal lockup or so. Or else instruct someone to pull the plug, wait 10 seconds, stick it back in again. If you use CoW filesystems, it is no problem to do this.

One interesting thing I discovered today is that you can actually boot from a flash drive, if you don't have a SD Card! In my case, I would have to buy a SD Card and had a flash drive laying around so I thought I might just give it a try, worked on an Arm Cortex-A53 CPU. I used u-boot-s905x-912 for .ext and meson-gxl-s905x-p212.dtb.

Btw. do you know if: 1. Is it possible to use the internal dvb-s tuner in the wetek play 2 with tvheadend? "dmesg | grep -i dvb" showed nothing (an external usb dvb-c wintv solohd was found). 2. Is hardware acellerated "Moonlight Gamestream" possible? In newer/latest Libreelec, the Wetek Play 2 Tuner isnt supported and hardware accelerated x264 is buggy. I think these problems also exist in armbian, or? 🙏

Thanks @bedna Ive now got it working with read write execute on the share via Windows. I searched the Ubuntu forums and foud a couple of posts relating to the issue I was hving with an exfat formatted hard drive. For anyone else searching this forum the answer was to edit the fstab file as follows: To enable read-write access for an exFAT drive in /etc/fstab, add rw,uid=1000,gid=1000,umask=000 to the options field. Using umask=000 ensures all users have read/write access, while setting the uid and gid to your user ID (typically 1000) assigns ownership to your account. Also from Reddit Linux Add this to your /etc/fstab file (replacing the UUID and mount point): UUID=XXXX-XXXX /mnt/exfat exfat defaults,uid=1000,gid=1000,umask=000,nofail 0 0 Key Options Explained rw: Explicitly mounts the drive as read-write. uid=1000,gid=1000: Sets the user and group owner to your user account, preventing root-only lockouts. Use the id command to check your actual UID if needed. umask=000: Sets permissions to 777 (read/write/execute for all), which is usually necessary because exFAT doesn't support native Linux permissions. nofail: Allows the system to boot even if the drive is unplugged. To remove the guest share that appeared all I did was remove the [Global] settings inserted from the Samba wiki i.e. [global] map to guest = Bad User log file = /var/log/samba/%m log level = 1 server role = standalone server [guest] # This share allows anonymous (guest) access # without authentication path = /srv/samba/guest/ read only = no guest ok = yes guest only = yes All working correctly now. I just need to mount the board in a small plastic box and change the IP address to a static one on my daughters subnet.🙂

https://paste.armbian.com/xacimaxamo here's the output from the build from Bigtreetech repo (https://github.com/bigtreetech/build)

Did you ran apt update + upgrade + reboot before ? Edit: we might add warning if installed and running kernel version differs. I ran into this problem myself.

I was using hdmi cable on hdmi port to only hours later discover that it is hdmi INPUT port, the hdmi output is a usb-c type.

Hi everyone, I'm using a new MXQ box with the SK Hynix H9TP32A8JDBC-PRKM but after flash the bootloader rk322x_loader_v1.10.238_256.bin, rkdeveloptool only detect ~4GB of flash with manufacturer name is SAMSUNG. How can I fix this? Thanks!

Thanks Werner, Unfortunately I have to halt this project. Though I can now create an booting Neo3plus Armbian image based on the Zero2, it does not fit my initial requirements. Obviously u-boot requires an android partition scheme. The current version as used by the nanopi zero2 cannot be used for my own purposes. So it will need to wait until the board can boot without a vendor u-boot version.

Google's AndroidXR. Qualcomm's Snapdragon Spaces. NVIDIA CloudXR. What do they have in common? Monado, the Open Source, cross-platform OpenXR runtime Collabora launched as an alternative to proprietary XR stacks. View the full article

Thanks I got it.

Found an error in the "use proprietary GPU driver for Spacemit K1" script. Because I cannot edit here is the corrected install script. spacemit-gpu-addon.sh

I have 3 Aceline AG-216 consoles. Help me find the right image for her. QHZIW_H313_A3_2LP4. V2.0 20240603 EA6521QF 2+16G

Maybe. Trunk are untested auto-builds and support for this board is from the community. Its functionality is unknown to the Armbian team. Get serial console logs. This makes investigation way easier.

Try running a2jmidid with pw-jack a2jmidid first — that bridges ALSA MIDI to JACK MIDI, and then use pw-link or qpwgraph to connect your app's MIDI input to the resulting Midi-Bridge ports

I was able to run Steam games with GPU accelerated ofc. But since my Opi5 only has 8Gb, I mainly run non-Steam games. I can see your SBC has 32Gb, so you are good. I assume your game is 64-bit DX11. Change the Steam Play compatible layer to "GE-proton". Download Dxvk-stripped here: https://github.com/khanh-it/dxvk/releases/tag/releases Copy x64/d3d11.dll, x64/dxgi.dll to the <<game>>.exe folder. Then run the game with a command like so:

Hey there, Title: Need compatible firmware / loader for XR8223518K-V1.0 (RK3518) TV box Message: Hi, I’m trying to recover a TV box with this exact mainboard: Board code: XR8223518K-V1.0 SoC: Rockchip RK3518 Symptoms: device only shows blue LED no HDMI output device can still enter MASKROM / Rockusb mode What I already tested: RKDevTool detects “Found One MASKROM Device” using my current MiniLoaderAll.bin + ExportImage.img fails with: “Download boot fail. Please check DDR.” So I believe I need: the exact stock firmware for this board or a compatible RK3518 MiniLoaderAll.bin / loader for this exact board / DDR configuration If anyone has firmware, loader, dump, or files for XR8223518K-V1.0, I would really appreciate it. Thanks.

@boggy have you tried another SD card? You have a lot of mmc errors. which miniarch image booted for you? Maybe we can use the mmc settings from that image.

I opened PR #9590 with the really minimal change that's needed to get my desired behavior back.

Diagnosing System Issues and Getting Support with ArmbianmonitorArmbian is a lightweight operating system based on Debian/Ubuntu, highly optimized for single-board computers (SBCs) like the Raspberry Pi, Orange Pi, and many others. When facing system problems on an SBC running Armbian, the built-in utility armbianmonitor is an essential diagnostic tool. It quickly gathers crucial system data, making troubleshooting faster and more accurate for both the user and the community providing support. Key Diagnostic FunctionsThe primary use of armbianmonitor is to generate real-time performance and system configuration reports. By running the command without any arguments, you get a menu of options, but the most vital functions for diagnosis are: System Status (armbianmonitor -m): This provides a live monitoring dashboard. It displays key metrics like CPU frequency, load average, temperature, memory usage, and disk I/O. By watching this output while a problem (like a system freeze or slowdown) occurs, you can often pinpoint the bottleneck—for instance, a sudden spike in CPU temperature indicating a cooling problem, or sustained high memory usage pointing to a resource leak.System Information (armbianmonitor -u or -d): This is the most crucial function for seeking online support. It gathers a comprehensive, anonymized report including details about the kernel version, device model, installed packages, boot logs, and hardware configuration. This data is essential because the performance and stability of SBCs are often highly dependent on the specific kernel and hardware drivers used for that model.Getting Support OnlineWhen seeking help on platforms like the Armbian forum or GitHub, simply describing the symptoms is rarely enough. The person helping you needs to know the exact state of your system. By running armbianmonitor -u, the utility uploads the detailed diagnostic report to a public pastebin service (like https://www.google.com/search?q=paste.armbian.com) and provides a unique, short URL. You can then include this URL directly in your support request. This allows community members to instantly access the exact configuration, eliminating back-and-forth questions about device type, OS version, and log file locations. This standardized method is the fastest way to receive targeted, effective assistance and ensures your issue is diagnosed accurately. View the full article