All Activity

@Igor When I first start it up, I get an error! Even if I install the packages manually, the GNOMRlE interface does not switch to Portuguese! That's strange!

In the case of the Orange PI 5 Pro, just remove OUT1 from mute mode and the ES8388 will work fine! By default, OUT1 is in MM (mute). @laibsch

I recently had to modify a device tree file for a different reason. I showed what I did (and how I did it) here: https://forum.armbian.com/topic/52118-hdmi-audio-and-analog-audio-do-not-work-on-opi5plus/?do=findComment&comment=224923 To summarize, I used the device-tree-compiler package (command line: dtc) to convert the device tree binary (.dtb) file to a device tree source (.dts) file. Then I edited the .dts file, then converted it back. The process won't show you all the variable names, but the resulting .dts is readable enough to likely see what and where you need to change... and even moreso if you have the original (pre-compiled) .dts file to compare it with. If you need to match variable names with specific numbers, they will likely be #defined in the #includes at the top of the original .dts file.

This will cause update-grub to add the following a devicetree line to all menu entries. This example is based on Debian Trixie's grub-efi. This example will expect dtb directories (or links) to be in the /boot directory, using the convention that I've seen Armbian use. Here is an example of a /boot directory listing for (pure) Debian Trixie with two kernels: -rw-r--r-- 1 root root 336036 Aug 27 04:10 config-6.12.43+deb13-arm64 -rw-r--r-- 1 root root 343394 Sep 6 12:48 config-6.16.3+deb13-arm64 lrwxrwxrwx 1 root root 42 Sep 20 16:17 dtb -> ../usr/lib/linux-image-6.16.3+deb13-arm64/ lrwxrwxrwx 1 root root 43 Sep 20 16:17 dtb-6.12.43+deb13-arm64 -> ../usr/lib/linux-image-6.12.43+deb13-arm64/ lrwxrwxrwx 1 root root 42 Sep 20 16:18 dtb-6.16.3+deb13-arm64 -> ../usr/lib/linux-image-6.16.3+deb13-arm64/ drwxr-xr-x 3 root root 4096 Sep 20 15:13 efi drwxr-xr-x 5 root root 4096 Sep 20 16:26 grub lrwxrwxrwx 1 root root 29 Sep 15 21:30 initrd.img -> initrd.img-6.16.3+deb13-arm64 -rw------- 1 root root 42521317 Sep 20 16:26 initrd.img-6.12.43+deb13-arm64 -rw------- 1 root root 43760872 Sep 20 16:25 initrd.img-6.16.3+deb13-arm64 lrwxrwxrwx 1 root root 30 Sep 15 20:38 initrd.img.old -> initrd.img-6.12.43+deb13-arm64 -rw-r--r-- 1 root root 83 Aug 27 04:10 System.map-6.12.43+deb13-arm64 -rw-r--r-- 1 root root 92 Sep 6 12:48 System.map-6.16.3+deb13-arm64 lrwxrwxrwx 1 root root 26 Sep 15 21:30 vmlinuz -> vmlinuz-6.16.3+deb13-arm64 -rw-r--r-- 1 root root 37449664 Aug 27 04:10 vmlinuz-6.12.43+deb13-arm64 -rw-r--r-- 1 root root 41507328 Sep 6 12:48 vmlinuz-6.16.3+deb13-arm64 lrwxrwxrwx 1 root root 27 Sep 15 20:38 vmlinuz.old -> vmlinuz-6.12.43+deb13-arm64 Note: The relative pathways of the dtb links above assume that the /boot directory is part of the main OS partition, not on its own boot partition. Otherwise you'd need to copy those directories to /boot/ as Armbian does. For The Current Partition's OS Entries (each devicetree will be specific to the respective kernel) 1. Open the file with a text/source editor (using sudo): /etc/grub.d/10_linux 2. Find every line that looks something like this (currently on my system, there is only one, and it's line 189) linux ${rel_dirname}/${basename} root=${linux_root_device_thisversion} ro ${args} 3. Just above it, add your own system's version of this line: devicetree ${rel_dirname}/dtb-${version}/[VENDOR SUB-DIRECTORY]/[SBC PRODUCT].dtb Specific Example: OrangePI-5-Plus devicetree ${rel_dirname}/dtb-${version}/rockchip/rk3588-orangepi-5-plus.dtb Specific Example from the resulting grub.cfg, of the current trixie-backport kernel, again on the OrangePI-5-Plus: devicetree /boot/dtb-6.16.3+deb13-arm64/rockchip/rk3588-orangepi-5-plus.dtb For Other Partitions' OS Entries, via os-prober (I'm unfamiliar with the variables in this so each devicetree will be the same generic path, regardless of kernel) 1. Open the file with a text/source editor (using sudo): /etc/grub.d/30_os-prober 2. Find every line that looks something like this (currently on my system, there are two, lines 277 and 297) linux ${LKERNEL} ${LPARAMS} 3. Just above it, add your own system's version of this line: devicetree /boot/dtb/[VENDOR SUB-DIRECTORY]/[SBC PRODUCT].dtb Specific Example: OrangePI-5-Plus devicetree /boot/dtb/rockchip/rk3588-orangepi-5-plus.dtb Then run update-grub, and take a look at the resulting /boot/grub/grub.cfg

Yes, current broke at some point. More up to date packages should be available via apt. In general the support for rk3588 in 6.12 (current as of today) is barely there but there won't be updates regarding that matter, bug fixes only due to its LTS nature. Better use vendor or edge.

Great, svvolf! This fix boot problem on OPI Zero v1 (Armbian v25.8.1, Linux 6.12.43-current-sunxi) 😁 Thank you!

Hi, I have downloaded and tested the 6.12 kernel Minimal/IOT images and they are not booting. I downloaded trixie 6.1, booted, then manually installed latest 6.12 with armbian-config and the reboot failed. I re-flashed sd card with 6.1, installed edge 6.16.4 (latest) with armbian-config and it booted fine.

T'is one reason to prefer boards that take 12V power. and yes, barrel-connectors, but I can't think of any recent boards that use 5V and barrel connectors. NanoPi-M4 vs NanoPC-T4, with a WD Blue SN500, the T4 was stable. the M4 was not. yes, the M4 used the official power supply.

As far as I know, the permissions of /var/log/postgresql after a reboot are recreated from those on /var/log.hdd/postgresql. So if you modify those as well (remove the sticky bit), the workaround should be permanent. Thanks for highlighting this problem, I've encountered the very same issue, but didn't realize it was caused by this somewhat peculiar directory permission. So I just applied your workaround (plus my extension) and hope it will fix this once and for all.

I think there are some userspace drivers needed as well. Armbian provides the kernel module only. Not exactly sure what's needed but I think the stuff is from here: https://github.com/airockchip/rknn-toolkit2/tree/master/rknpu2

I see. Well there is a similar topic, maybe this can give some clues: https://forum.armbian.com/topic/50228-i2s-audio-not-working-on-orange-pi-zero-2w-allwinner-h618-with-max98357a/

Can someone tell me the major/minor device numbers for the /dev/rknpu device? It wasn't created in the image that I'm using. I'm trying to determine if the built-in npu has enough functionality to test a llm: # cat /sys/kernel/debug/rknpu/version RKNPU driver: v0.9.8 # I'm running the latest of the linux-image-vendor-rk35xx=25.5.1 v6.1.115 $ uname -a Linux cm3588-nas 6.1.115-vendor-rk35xx #1 SMP Wed Aug 13 03:55:09 UTC 2025 aarch64 GNU/Linux $ # LD_LIBRARY_PATH=/usr/lib/aarch64-linux-gnu python3 server.py Loaded RKLLM library from '/usr/lib/aarch64-linux-gnu/librkllmrt.so' RKLLM_LOG_LEVEL: 1 Initializing model with parameters: Path: /src/models/tinyllama-v1-rk3588/tinyllama-v1.0-1.1B-rk3588.rkllm Max Context: 30000 Max New Tokens: -1 N_Keep: 32 Use GPU: True Is Async (Library Flag): False E RKNN: [23:47:17.469] failed to open rknpu module, need to insmod rknpu dirver! E RKNN: [23:47:17.469] failed to open rknn device! E RKNN: [23:47:17.570] Device is not available Get device properties failed Error: rkllm_init failed (code 1). Failed to initialize RKLLM model. Server not starting. # ls -l /dev/rknpu ls: cannot access '/dev/rknpu': No such file or directory #

Unfortunately, LLM is wrong here. There are MAX98357A boards, such as the violet one, which support (L+R)/2 and single/selected channel modes. I was able to configure the board using ESP32 and a sinus wave, so I can confirm it is possible and the board is not malfunctioning. For some reason, the sunxi driver (or ALSA) misbehaves, and I can't determine where the problem is.

Hi @Gunjan Gupta, Thanks for the info. I'm trying to do something similar but on a different board. Running the "uboot-patch" build command just seems to download uboot?? There is no pause for me to make changes then to hit enter to continue. Has the process changed or am I doing something wrong? Many Thanks, Fiery

Hi goodfvh _YT_. I wanted to know if you are using Dupont wires?

Looks like that one can take stereo input but it is mostly designed to output one channel only. Did not research on my own but asked LLM. Since you experience one channel output only it might be correct about this behavior and also the overlay seems correct. In case you're interested in the output summary:

Hi everyone, I got my OrangePi Zero 2W to work with MAX98357A board, the violet one, but I can only hear one channel. I didn't modify ALSA much, just focused on DTS: ... fragment@1 { target-path = "/soc"; __overlay__ { ahub0_plat: ahub0_plat { #sound-dai-cells = <0>; compatible = "allwinner,sunxi-snd-plat-ahub"; apb_num = <2>; /* for dma port 5 */ dmas = <&dma 5>, <&dma 5>; dma-names = "tx", "rx"; playback_cma = <128>; capture_cma = <128>; tx_fifo_size = <128>; rx_fifo_size = <128>; tdm_num = <0>; tx_pin = <0>; rx_pin = <0>; pinctrl-names = "default", "sleep"; pinctrl_used; pinctrl-0 = <&ahub_daudio0_pins_a>, <&ahub_daudio0_pins_b>, <&ahub_daudio0_pins_c>; pinctrl-1 = <&ahub_daudio0_pins_d>; status = "okay"; }; ahub0_mach: ahub0_mach { compatible = "allwinner,sunxi-snd-mach"; soundcard-mach,name = "ahubi2s0"; soundcard-mach,format = "i2s"; soundcard-mach,frame-master = <&ahub0_cpu>; soundcard-mach,bitclock-master = <&ahub0_cpu>; soundcard-mach,slot-num = <2>; soundcard-mach,slot-width = <32>; status = "okay"; ahub0_cpu: soundcard-mach,cpu { sound-dai = <&ahub0_plat>; soundcard-mach,pll-fs = <4>; soundcard-mach,mclk-fs = <0x100>; }; ahub0_codec: soundcard-mach,codec { }; }; hdmi: hdmi@6000000 { status = "disabled"; }; }; }; ... Did I miss something, and now I'm hearing only the left channel? Has anyone managed to listen to stereo using external DAC? Best!

If someone interested on this tv box: I've managed to download original firmware image (update.zip) from backup partition. Also I cleaned it from malware (at least I think so) and packed as modified update.zip. Files are located here: https://drive.google.com/drive/folders/1etPmH8ZG4UtPHI3Vf1U9MUHl5_gK_s-E Further info available here (in Russian): https://4pda.to/forum/index.php?showtopic=1016510&view=findpost&p=139209499

Join us next week in Paris for Kernel Recipes! We're delighted to sponsor this kernel-focused event and contribute with a talk on GPU drivers. View the full article

Hello @Eks Ma, how are you? Unfortunately not. I gave up trying. The TV box is just sitting here at home.

It may or may not work to use a Tinkerboard image for your Chromebook. Same processor or manufacturer does not mean much, though, in terms of compatibility.

Also note that if you are on a community build or anything that points to the "beta" armbian apt repository, you will get a new linux kernel image pushed out to you each day, which would then trigger the need for a reboot (depending on settings) for that new kernel to be run.

Thanks for your comments, I am new to ARM installation, and never convert a Chromebook to Linux NoteBook, I am retired and doing that to my grand-kids…, I am more familiar with systems using Intel, AMD processor and a standard BIOS, my computer tower is a ‘Debian-Facile’, also called ‘DFlinux’. 1) To answer ‘Laibsch’, I planed to use Armbian Thinkerboard/s simply because it was the same RK3228 processor, and they are both mfg by Asus, and according to ‘NicoD’ Youtube video, Armbian-config let me easily install French version of Debian. To answer ‘The Tall Man’ 2) Archlinux is not my 1st choice, other class equipments, with school softwares are in Debian based distributions, and Archlinux has some differences in instructions, this is why I targeted a Debian based distribution to avoid futur problem 3) Currently for testing, I remove the ‘Write protection’ screw on the board, and in ‘Developer mode’, using and external USB, with CTL+U at start, is running Lubuntu 18.04, from Zutchi group image, but this version of Linux is old, and I failed to upgrade since Ubuntu no longer have 32 bits distribution. 4) I will try your suggestion using Armhf distribution from Debian (trixie) using EFI booter, Let me few days, I have other thinks to do, and I don’t want ‘Brick’ the machine, I will read carufelly and try to install on eMMC of the C100P to avoid, for the kids using external device with CTL+U. Thanks again for your time and your usefull comments

unfortunately, your board has no maintainer in Armbian, it is only supported by the community

what version of OS are you guys running? are you possibly affected by the hardening of fancontrol in trixie?