Active threads

Hi there, the 2 NICs are on my RPi Armbian. ip route output. > modified it abit to match but concept is below. default via 10.10.10.254 dev enp4s0 proto static metric 100 169.254.0.0/16 dev enp4s0 scope link metric 1000 192.168.100.0/24 dev eth0 proto kernel scope link src 192.168.100.10 metric 101 10.10.10.10/24 dev enp4s0 proto kernel scope link src 10.10.10.2 metric 100 I have only PC1 connected to NIC1 with 192.168.100.101 GW - 192.168.100.254 This PC1 can NOT be changed. Device1 on NIC2 10.10.10.100/24 < this have no Gateway as its only a slave device. I need to reach Device1 on NIC2 from the PC1 on NIC1..how is this achieved? I tried /etc/sysctl.conf net.ipv4.ip_forward=1 still missing something… I failed to mention is that I can only modify settings within the Linux box containing the 2 NICs. I need some sort of interlinking NIC1 on 192.168 to forward packets to 10.10 network…

Can't say I know much about X11, but after playing around with the Cinnamon version I did get a desktop by: created file:/etc/X11/xorg.conf Section "Device" Identifier "Device0" Driver "fbdev" Option "Device" "/dev/dri/card0" EndSection So I figure something in the configuration or driver related ?. And that goes for all Debian flavors I tested. All gave the same error.

Currently yes. A replacement for this package / service needs to be found and implement - in case you want to get involved. This isn't completely true. Armbian still does utilize CPUMIN/CPUMAX from /etc/default/cpufrequtils if present to set corresponding frequencies via the Armbian script armbian-hardware-optimization (packages/bsp/common/usr/lib/armbian/armbian-hardware-optimization). This script I believe runs at every system startup. So even without the cpufrequitls package installed, there is still some functionality in this area. Functionally that no one has likely touched or looked at in years.

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

Each attached memory disk must have its own unique UUID. This is its essence. This depends on the platform (BROM bootloader flashed into the chip) and possibly the switch soldered to the board.

``` root@opi5 /etc/apt/sources.list.d# apt-get update Hit:1 http://deb.debian.org/debian trixie-backports InRelease Hit:2 http://deb.debian.org/debian trixie InRelease Hit:3 http://deb.debian.org/debian trixie-updates InRelease Hit:4 http://security.debian.org trixie-security InRelease Hit:5 https://github.armbian.com/configng stable InRelease Hit:6 http://mirror.vinehost.net/armbian/apt trixie InRelease Reading package lists... Done W: https://github.armbian.com/configng/dists/stable/InRelease: Policy will reject signature within a year, see --audit for details N: Missing Signed-By in the sources.list(5) entry for 'http://deb.debian.org/debian' ``` ``` root@opi5 /etc/apt/sources.list.d# apt-get update --audit Hit:1 http://deb.debian.org/debian trixie-backports InRelease Hit:2 http://deb.debian.org/debian trixie InRelease Hit:3 http://deb.debian.org/debian trixie-updates InRelease Hit:4 http://security.debian.org trixie-security InRelease Hit:5 https://github.armbian.com/configng stable InRelease Hit:6 http://mirror.vinehost.net/armbian/apt trixie InRelease Reading package lists... Done W: https://github.armbian.com/configng/dists/stable/InRelease: Policy will reject signature within a year, see --audit for details A: https://github.armbian.com/configng/dists/stable/InRelease: Sub-process /usr/bin/sqv returned an error code (1), error message is: Signing key on DF00FAF1C577104B50BF1D0093D6889F9F0E78D5 is not bound: No binding signature at time 2025-09-08T18:12:20Z because: Policy rejected non-revocation signature (PositiveCertification) requiring second pre-image resistance because: SHA1 is not considered secure since 2026-02-01T00:00:00Z Missing key 8CFA83D13EB2181EEF5843E41EB30FAF236099FE, which is needed to verify signature. N: Missing Signed-By in the sources.list(5) entry for 'http://deb.debian.org/debian' ``` **/etc/apt/sources.list.d/armbian-config.sources** ``` Types: deb URIs: https://github.armbian.com/configng Suites: stable Components: main Signed-By: /usr/share/keyrings/armbian.gpg ``` **/etc/apt/sources.list.d/armbian.sources** ``` Types: deb URIs: http://apt.armbian.com/ Suites: trixie Components: main trixie-utils trixie-desktop Signed-By: /etc/apt/trusted.gpg.d/armbian.gpg ``` **/etc/apt/sources.list.d/debian-backports.sources** ``` # Modernized from /etc/apt/sources.list Types: deb URIs: http://deb.debian.org/debian/ Suites: trixie-backports Components: main contrib non-free non-free-firmware Signed-By: ``` **/etc/apt/sources.list.d/debian.sources** ``` # Modernized from /etc/apt/sources.list Types: deb URIs: http://deb.debian.org/debian/ Suites: trixie Components: main contrib non-free non-free-firmware Signed-By: /usr/share/keyrings/debian-archive-keyring.gpg # Modernized from /etc/apt/sources.list Types: deb URIs: http://deb.debian.org/debian/ Suites: trixie-updates Components: main contrib non-free non-free-firmware Signed-By: /usr/share/keyrings/debian-archive-keyring.gpg # Modernized from /etc/apt/sources.list Types: deb URIs: http://security.debian.org/ Suites: trixie-security Components: main contrib non-free non-free-firmware Signed-By: /usr/share/keyrings/debian-archive-keyring.gpg ``` How to fix it?

Dear Armbians, I'm thrilled to announce the launch of this digest for our amazing community. For newcomers, Armbian is a lightweight Linux distribution that breathes life into ARM-based single-board computers, transforming tiny, affordable boards into powerful servers, workstations, and IoT devices. This newsletter is our way of keeping you in the loop, sharing the latest releases, celebrating community contributions, and diving into the technical insights that power your projects. Whether you're a tech enthusiast or just getting started with your first Orange Pi, there's something here for you. Thanks for being part of this incredible journey! Igor Armbian project manager View the full article

The file exists in the sd card, as expected. root@x96q-lpddr3-v1-3:~# ls -l /boot/dtb/allwinner/sun50i-h313-x96-q-lpddr3.dtb -rw-r--r-- 1 root root 37577 Apr 2 19:41 /boot/dtb/allwinner/sun50i-h313-x96-q-lpddr3.dtb It also exists inside the installed eMMC filesystem (after installing -- without rebooting -- I mounted the /dev/mmcblk2 device and the file is there, in the correct place). root@x96q-lpddr3-v1-3:~# mount /dev/mmcblk2p1 /srv/ root@x96q-lpddr3-v1-3:~# ls -l /srv/boot/dtb/allwinner/sun50i-h313-x96-q-lpddr3.dtb -rw-r--r-- 1 root root 37577 Sep 10 21:16 /srv/boot/dtb/allwinner/sun50i-h313-x96-q-lpddr3.dtb Before rebooting, I re-ran armbian-install and used option 6 to re-write boot on eMMC just in case. Then rebooted. Then it worked!! It is booting from eMMC normally now.... Boot log from successful boot: U-Boot SPL 2025.01-armbian-2025.01-S6d41-P7151-H8869-V98f7-Bb703-R448a-dirty (Apr 02 2025 - 21:19:05 -04 00) DRAM:testing 32-bit width, rank = 2 read calibration failed! testing 32-bit width, rank = 1 DRAM:Store cfg DRAM:1st writing pattern DRAM:detecting column address bits detected 10 columns DRAM:restore cfg DRAM:reconfigure for all active rows DRAM:store cfg DRAM:2nd writing pattern DRAM:detecting row address bits detected 15 rows DRAM:restoring cfg DRAM:end of auto detect dram size MBUS port 0 cfg0 0100000d cfg1 00640080 MBUS port 1 cfg0 06000009 cfg1 01000578 MBUS port 2 cfg0 0200000d cfg1 00600100 MBUS port 3 cfg0 01000009 cfg1 00500064 MBUS port 4 cfg0 20000209 cfg1 1388157c MBUS port 5 cfg0 00640209 cfg1 00200040 MBUS port 6 cfg0 00640209 cfg1 00200040 MBUS port 8 cfg0 01000009 cfg1 00400080 MBUS port 11 cfg0 01000009 cfg1 00640080 MBUS port 14 cfg0 04000009 cfg1 00400100 MBUS port 16 cfg0 2000060d cfg1 09600af0 MBUS port 21 cfg0 0800060d cfg1 02000300 MBUS port 22 cfg0 01000009 cfg1 00640080 MBUS port 25 cfg0 0064000f cfg1 00200040 MBUS port 26 cfg0 20000209 cfg1 1388157c MBUS port 37 cfg0 01000009 cfg1 00400080 MBUS port 38 cfg0 00640209 cfg1 00200040 MBUS port 39 cfg0 20000209 cfg1 1388157c MBUS port 40 cfg0 00640209 cfg1 00200040 1024 MiB Trying to boot from MMC2 NOTICE: BL31: v2.10.14(debug):armbian NOTICE: BL31: Built : 18:07:43, Apr 2 2025 NOTICE: BL31: Detected Allwinner H616 SoC (1823) NOTICE: BL31: Found U-Boot DTB at 0x4a0b2520, model: hechuang,x96-q LPDDR3 v1.3 INFO: ARM GICv2 driver initialized INFO: Configuring SPC Controller INFO: PMIC: Probing AXP305 on RSB ERROR: RSB: set run-time address: 0x10003 INFO: Could not init RSB: -65539 INFO: BL31: Platform setup done INFO: BL31: Initializing runtime services INFO: BL31: cortex_a53: CPU workaround for erratum 855873 was applied INFO: BL31: cortex_a53: CPU workaround for erratum 1530924 was applied INFO: PSCI: Suspend is unavailable INFO: BL31: Preparing for EL3 exit to normal world INFO: Entry point address = 0x4a000000 INFO: SPSR = 0x3c9 INFO: Changed devicetree. ns16550_serial serial@5000000: pinctrl_select_state_full: uclass_get_device_by_phandle_id: err=-19 U-Boot 2025.01-armbian-2025.01-S6d41-P7151-H8869-V98f7-Bb703-R448a-dirty (Apr 02 2025 - 21:19:05 -0400) Allwinner Technology CPU: Allwinner H616 (SUN50I) Model: hechuang,x96-q LPDDR3 v1.3 DRAM: 1 GiB Core: 59 devices, 20 uclasses, devicetree: separate WDT: Not starting watchdog@30090a0 MMC: mmc@4020000: 0, mmc@4021000: 3, mmc@4022000: 1 Loading Environment from FAT... Unable to use mmc 1:1... In: serial@5000000 Out: serial@5000000 Err: serial@5000000 No USB device found Net: apply fix for AC300 ephy bb version bug ... using AC300 emac1 ephy default config ... eth0: ethernet@5030000 starting USB... No USB controllers found Hit any key to stop autoboot: 0 switch to partitions #0, OK mmc1(part 0) is current device Scanning mmc 1:1... Found U-Boot script /boot/boot.scr 4641 bytes read in 1 ms (4.4 MiB/s) ## Executing script at 4fc00000 U-boot loaded from SD Boot script loaded from mmc 252 bytes read in 0 ms Load fdt: /boot/dtb/allwinner/sun50i-h313-x96-q-lpddr3.dtb Card did not respond to voltage select! : -110 ** Bad device specification mmc 0 ** 37577 bytes read in 3 ms (11.9 MiB/s) Working FDT set to 4fa00000 Failed to load '/boot/dtb/allwinner/overlay/sun50i-h616-fixup.scr' 15483712 bytes read in 492 ms (30 MiB/s) 42621440 bytes read in 1351 ms (30.1 MiB/s) Moving Image from 0x40080000 to 0x40200000, end=0x42b50000 ## Loading init Ramdisk from Legacy Image at 4ff00000 ... Image Name: uInitrd Image Type: AArch64 Linux RAMDisk Image (gzip compressed) Data Size: 15483648 Bytes = 14.8 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 4fa00000 Booting using the fdt blob at 0x4fa00000 Working FDT set to 4fa00000 Loading Ramdisk to 4913b000, end 49fff300 ... OK Loading Device Tree to 00000000490c9000, end 000000004913afff ... OK Working FDT set to 490c9000 Starting kernel ...

Dear Armbians, I'm thrilled to announce the launch of this digest for our amazing community. For newcomers, Armbian is a lightweight Linux distribution that breathes life into ARM-based single-board computers, transforming tiny, affordable boards into powerful servers, workstations, and IoT devices. This newsletter is our way of keeping you in the loop, sharing the latest releases, celebrating community contributions, and diving into the technical insights that power your projects. Whether you're a tech enthusiast or just getting started with your first Orange Pi, there's something here for you. Thanks for being part of this incredible journey! Igor Armbian project manager View the full article

I looked at this for an hour and unfortunately can't figure it out. It seems that Olimex didn't 'fork' from Armbian, instead did something else to make their clone of your code.

Hi, I'm still having this issue after installing qemu-emulators-full and qemu-user-static on the host (arch) does anyone have any idea or workaround ?

I'm thinking of getting https://www.beagleboard.org/boards/beagley-ai I see there is this page for it https://www.armbian.com/beagley-ai/ I also see references to it in the code: https://github.com/search?q=org%3Aarmbian+beagley&type=code Are there any pre-built images available for it? Or would I have to build one?

my uboot was armbian 2025.1, so I have no idea why it wasn't working with even Armbian mainline trixie.

The easiest route is to simply flash it to a microsd card and boot from it. Once booted issue "armbian-install" to move the OS and boot loader to eMMC. eMMC should be accessible directly if tools like rkdeveltool or whatever that is called is used. Never used that personally, seems tricky to use. Prefer first path.

I was able to find a UART module to read out the boot. See the file attached of the full log I was able to capture. It seems to fail on this part: Starting kernel ... done. Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done. Begin: Running /scripts/local-premount ... Scanning for Btrfs filesystems done. Begin: Waiting for root file system ... Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. done. Gave up waiting for root file system device. Common problems: - Boot args (cat /proc/cmdline) - Check rootdelay= (did the system wait long enough?) - Missing modules (cat /proc/modules; ls /dev) ALERT! UUID=0a0755af-1936-4167-9d26-9ca9a87a9103 does not exist. Dropping to a shell! U-Boot SPL 2025.10-rc3-armbian-2025.txt

Modified based on nanopi-r76s.dts, both wireless and Bluetooth networks are working properly. There is no 3.5 interface fiber optic interface audio in DTS, and the standard infrared remote control cannot be used 4k hardware acceleration mpv kodi is normal Compile-configuration.zip

Hi @Kelvie Wong I have a similar problem with rk3568 on 6.12.45 with HDMI: it works on some displays and not on others. Can you share how you solved the problem?

Terrific! You're welcome!

@Rodrigo Campos@Nick A This guy seems to have created a u-boot that can get 4gb ram for M98-8K. https://github.com/nitrolack/M98-8K-Linux/blob/main/U-Boot Screen 20-03-2024

For anyone interested in solving this temporarily, doing the following steps worked for me: sudo systemctl edit systemd-networkd ### Editing /etc/systemd/system/systemd-networkd.service.d/override.conf ### Anything between here and the comment below will become the new contents of the file [Service] ExecStartPre=/bin/sleep 5 ### Lines below this comment will be discarded sudo systemctl daemon-reexec sudo reboot

Guys, please do keep us all updated on the rk3528. I was just about to buy a job lot of boards for a grid computing project when I found it's not supported yet. I found that my old TV rk32xx box was well supported, so am prepared to wait.

@snow try the transpeed image https://github.com/NickAlilovic/build/releases/tag/20250306

Thanks for the reply. In the end I soved it by following also a few steps from over here. I don't know exactly what did the trick, but actually I assume it was pure coincidence: my ethernet device is actually called en0, not eth0. During my first run through this tutorial I wasn't aware of that. I think I simply forgot to change this bit in my recent try and luckily got it working that way. About the systemd-cryptsetup: I don't know if I understand correctly, but doesn't this do some of the steps automatically which we set up manually? If so, maybe it should be adopted to this tutorial in the future …

There are three ways to do this. The first simplest is to assemble a binary debian package using the Armbiyan assembly system and then convert it to a rpm package directly in a running OpenSuse OS. The second way is more complicated but it is more correct. You can take patches directly from the build system and apply them to OpenSuse kernel sources in the sequence in which the build system does this while running. Next, build the kernel package using rpmbuild. The third way is the same as the second but use OBS. This will allow you to have your own repository of signed packages and install them using zypper. You can find like-minded people anywhere on our planet, including this place. Hope this helps you.

Hey, I think I'm impacted by the same issue. I've replaced the original fan of the HC4 with a Noctua NF-A4x10 5V PWM earlier this year. It was working as expected, but since couple weeks the fan is at 100% speed continuously, which is loud. It sounds like it's a software upgrade that broke the PWM control, but no idea which one. I've done part of the same testing you mentioned but didn't managed to find a fix neither. I'm probably even more beginner than you, so I don't think I can help much unfortunately. How can we get more eyes on this issue? Did you post on Odroid Forum?