Active threads

I haven't used samba for a long time so I'm probably not the best to ask, but I checked my old notes about samba, and this was my goto config: [samba] path = /path/to/mountlocation/ browsable = yes writable = yes read only = no force user = <your_username> force group = <your_usergroup> create mask = 0644 direcotry mask = 0755 # make sure this works on debian, errors on arch (edit, this was in my notes, so I guess 755 instead of 0755.. maybe..) public = no Changing the directory permissions on the server does not matter at all when it comes to samba. As you can see in the conf I provided, the mask is defined there, and all files will get that mask (if ext4, exfat does not support user/group/all masks, what you see in your filesystem is what you set in fstab for exfat).

Now flashed with Rufus (very popular windows program) and of course also no boot. I just strictly follow Google KI: Step-by-Step Instructions: Download Image: Download a suitable Armbian image for Amlogic S905/S905X devices (e.g., from the Armbian forum threads by balbes150). Flash SD Card: Use BalenaEtcher or Rufus to flash the image to a MicroSD card. Configure DTB: Open the SD card's boot partition, navigate to dtb/amlogic/, and locate a file for the S905H or generic S905 (gxbb_p200_wetek_play2.dtb or similar). Edit uEnv.txt or extlinux/extlinux.conf to point FDT to this file. Wetek Play 2 dtb on "Minix Neo U1" because: 1. 2. Its the only dtb which makes all working with a Minix Neo U1 in Libreelec. So now i need a detailed step by step manual on how to get a working armbian on a wetek play 2 or minix neo u1!

That's the proprietary trust OS problem Let me understand: if you erase the emmc, and boot armbian from sdcard, doesn't it freeze anymore?

same thing with edge kernel: https://paste.armbian.com/orivozogil

I tried to build a image from the current main branch (kernel: 6.18.20) and I found the problem is the same. I changed KERNELBRANCH to "tag:v6.18.18" from "branch:linux-6.18.y" and rebuild. It can boot to desktop as expected. It seems some change in the 6.18.19 kernel causes the problem

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

Example for adding a new board with already existing board family: https://github.com/armbian/build/pull/9456/changes

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

Nice! I actually did something similar. In my case I ended up using an old PWM fan I had lying around, powering it through the 12V pin input. Then I used ground on pin 6 and the PWM signal from GPIO pin 11. I wrote a bash script and set it up as a service that controls the fan speed based on five temperature levels. Right now I’m running it on FriendlyElec CM3588 NAS with Armbian Linux 6.1.115-vendor-rk35xx (v26.2 rolling). The repo is in Spanish for now, but I’m planning to translate it to English soon: https://github.com/jgomezriesgobancario/cm3588-fan-controller **edited** Fix typos

https://forums.kali.org/ There is an arm64 section.

Thank Igor that explains it. I'll look at your suggestion or just go back to an SMB share

The same issue has occurred again. I had to take this measure again today to fix the zfs module. I had to revert the kernel, headers and dtb back to 25.11.2 from 26.2.1 of linux(meson64:arm64)

Hello. I installed Armbian 26.2.1 Minimal Debian 13 (Trixie), but the Wi-Fi still doesn't work. It doesn't connect to the AP during initial setup. After reconfiguring via armbian-config, it works until the first reboot.

moved to staging

Also: # apt install -y iptables # iptables -v iptables v1.8.11 (nftables): no command specified https://wiki.debian.org/nftables AFAIK using iptables syntax should still work, but nft is what you probably should learn to use instead. https://wiki.nftables.org/wiki-nftables/index.php/Moving_from_iptables_to_nftables

Add to /etc/rc.local and reboot. echo "1" > /sys/devices/system/cpu/cpufreq/boost && echo "performance" | tee /sys/devices/system/cpu/cpu[0-9]/cpufreq/scaling_governor &&

I tried installing armbian on tx6 because I saw a .img file for the tanix tx6 to turn it as a Minecraft server but I quickly run into problems