All Activity

FYI: My node running 25.02.0-trunk as mentioned above has stability issues after ~30 days. I had to reboot it at least 2 times. Cause unknown. Maybe not an issue depending on the workload/use case:

Am I missing something?

@Ángel Luis Pérez You don't have to apologize because the type of image was very clear in the post where you reported it... it's just a matter of reading 🙂

I never said this was Armbian, sorry. What I said was: "This message was just to say that OPi's Debian is working fine when rebuilt from scratch, in case someone needs a working system right now." Sorry if I didn't explain clearly. Regards.

https link isn't functioning. I click and a new window opens and rapidly closes without automatic download. Using the latest Chrome (Version 135.0.7049.85 (Official Build) (64-bit)) within Windows 11 Pro, no pop-up blocker enabled.

Finally Armbian 25.2.3 (kernel 6.12.20) fixes the boot problem on PC2! Upgrade from 23.11/6.1.x to 25.2.3/6.12.20

When I try a sudo apt update it works. However, when I try a sudo apt upgrade or sudo apt full-upgrade they fail, Here is an example of what I am getting: sudo apt full-upgrade Reading package lists... Done Building dependency tree... Done Reading state information... Done You might want to run 'apt --fix-broken install' to correct these. The following packages have unmet dependencies: libraspberrypi0 : Depends: raspberrypi-bootloader but it is not installable or raspi-firmware but it is not installed E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution). any help would be appreciated.

Angel Luis Pérez I don't understand, where is Armbian here?

Fred K's February 27 instructions worked great for me as well. It rescued my Helios4 using OMV without any data loss. Thank you! Someone had mentioned that they had trouble downloading https://images.solid-run.com/A38X/U-Boot/v2024.04/2025-02-08_695f767/u-boot-helios-4-sd.kwb I had trouble as well, but how was able to get it was go to the parent folder in that URL, then click on the u-boot-helios-4-sd.kwd file shown there, and that downloaded perfectly fine for me (not sure why the direct link didn't want to work).

There is no ftp available. http/https only.

Does anyone have the i2c working in the orange pi 4a? I tried the debian official image and build my image with the orange pi source code but I can't get it to work, everything works including spi gpio, any help will be appreciated, also I want to build Armbian for the orange pi 4a

@g2t - the overlay you posted wasn't compatible with my 6.1.99-vendor-rk35xx kernel, so I changed it a bit until it started to work. /dts-v1/; /plugin/; / { /* Add new thermal trip points for active cooling */ fragment@0 { target-path = "/thermal-zones/bigcore0-thermal/trips"; __overlay__ { bigcore0-active1 { /* 55 degree with hysteresis of 5 deg */ temperature = <55000>; hysteresis = <5000>; type = "active"; phandle = <0x1001>; }; bigcore0-active2 { /* 60 degree with hysteresis of 2 deg */ temperature = <60000>; hysteresis = <2000>; type = "active"; phandle = <0x1002>; }; }; }; /* Set polling delay for active cooling */ fragment@1 { target-path = "/thermal-zones/bigcore0-thermal"; __overlay__ { /* for active cooling, in milliseconds */ polling-delay = <2000>; }; }; /* Enable PWM fan and adjust cooling levels */ fragment@2 { target-path = "/pwm-fan"; __overlay__ { status = "okay"; cooling-levels = <0 45 80 120 160 255>; }; }; /* Add cooling maps to associate thermal trips with fan cooling levels */ fragment@3 { target-path = "/thermal-zones/bigcore0-thermal"; __overlay__ { cooling-maps { map1 { trip = <0x1001>; cooling-device = <&fan 0 1>; }; map2 { trip = <0x1002>; cooling-device = <&fan 2 5>; }; }; }; }; __symbols__ { fan = "/pwm-fan"; }; };

Domain resolves, but ftp is not responding, hence links don't work.

that's really a good performance, congratulations for comparison i do 3fps 320x240 on rk3566

I think my issue is actually that CONFIG_RT_GROUP_SCHED is enabled. I was certain I had disabled it. After some sluething.. It turns out I don't know how to configure/build a kernel. I run ./compile.sh BOARD=bananapim4zero BRANCH=edge kernel-config I then make some changes and tell it to save: For instance when I enter menuconfig, I see this. I then REMOVE the check. I say YES OOPS. I realized I wanted to make another change. And now it's back. After unchecking this, and building the kernel, moving the kernel, installing, and rebooting I see the config hasn't change on board. So, I must have a misunderstanding of how this is supposed to work. I checked here: https://docs.armbian.com/Developer-Guide_Build-Commands/ Which says "Add or Remove" modules, but doesn't elaborate if it's copying some defaults or where they might be coming from.

The automated script has been updated to support the Nano Pi M6 (Noble mainline kernel IOT/minimal image and Noble Gnome desktop vendor kernel image both tested). Use the -m option to include all loaded modules in the initrd. The boot partition size has also been increased to 400MB, which should fix out-of-space errors when upgrading via apt. The tutorial has been updated accordingly.

I rebuild with above corrections and also changed the bluetooth GPIO pins to be same as transpeed. Now I can see bluetooth before it was missing.

Found the issue and submitted a PR to the repository. It will take some time to get merged and then the new kernel built and put into the apt repository.

I'm running Proxmox VE on small x86-64 hardware with multiple nics and then various LXC containers / VMs. One for OpenWRT, Unifi, Adguard Home, NextCloud, HomeAssistant, Freifunk-Offloader, ...

Exactly. Kernel support for this board might not be good enough (yet) or even might work just fine but if the hw doesn't cut it, it might be just a big waste of time.

I've tried starting with edge, but none of them work for me. Maybe I have an old u-boot? Mine's on SPI, made with one of your EFI images from 2023.

I'm hesitant to post this here, because I am not really sure that this is an armbian issue to begin with. But I'm somewhat stumped. During the build process I configured the kernel to enable real time threads. CONFIG_NO_HZ_COMMON=y CONFIG_HZ_1000=y CONFIG_HZ=1000 CONFIG_PREEMPT_RT=y However, as I started to migrate my development I discovered I couldn't create a real time thread. So I pulled down areal time test suite (https://wiki.linuxfoundation.org/realtime/documentation/howto/tools/rt-tests) And confirmed it has the same issue: Unable to change scheduling policy! either run as root or join realtime group I am root, it is a real time kernel. Linux bananapim4zero 6.13.7-edge-sunxi64 #1 SMP PREEMPT_RT Thu Mar 13 12:08:08 UTC 2025 aarch64 GNU/Linux I am not sure what might be driving this. For the past several months I've been doing some dev work on a TI AM625 based board that I built a yocto distribution on and it's fine. I know that is a completely different board, but my kernel setting for real time enablement are the same. I pulled them from that build since. Appreciate any input!

hi, its too late (and glad you got documented thing as recommended in FAQ too), but recently I saw quite interesting presentation about reverse engineering unknown old routers, with plenty of info, but only as fun and relax ... at least info that ghidra decompiles any cpu isa into pseudo-c was new to me and it is very close to what I am (OT) trying around my risc-v-alike thing (search github apws vmex) as "aslix", thing slighlty below C ... )) youtube: MEnAKAbz-Y

I just saw your wifi chip in the picture. Unfortunately, this chip only has drivers for older kernel versions. You’ll need to use a usb wifi device or Ethernet.

When select the option of install the driver of wifi, return a message error: Invalid overlay_prefix sun50i_h616 @Nick A