All Activity

I have exactly the same issue. Cannot boot after upgrade, also newly flashed image won't boot with exactly the same trace. I compiled latest upstream U-Boot v2025.04 as described here (Pre-Built FIP variant). https://docs.u-boot.org/en/latest/board/amlogic/odroid-c2.html Then I patched Armbian image with latest U-Boot. dd if=u-boot.bin.sd.bin of=Armbian_25.2.1_Odroidc2_bookworm_current_6.12.13_minimal.img conv=notrunc bs=512 skip=1 seek=1 And that works for me, system boots just fine

Looks like 23.5.1 with U-Boot 2022.7 works as well (23.5.1 Bookworm 6.1.30).

Have you tried applying this to the 6.12 kernel?

@going I can, yes. But at the moment I don't want to distract from the wifi issue I am trying to solve. I am building a test application that must perform real time operations. I have previously done this with other ARM boards/distributions, but for this small project I am trying to go with "simplicity" (nothing is ever simple) I can provide the 'duff -u' for your interest, but I don't know what you want me to compare it against. i have linux-sunxi64-edge.config in my userpatches/ folder. It's generated from make menuconfig, and then I removed 'CGROUP_SCHED' from armbian-kernel.sh. Real-time applications work fine now. (They do not with group scheduling) root:~/# ./cyclictest --mlockall --smp --priority=80 --interval=200 --distance=0 # /dev/cpu_dma_latency set to 0us policy: fifo: loadavg: 0.30 0.37 0.17 2/200 1471 T: 0 ( 1468) P:80 I:200 C: 379209 Min: 7 Act: 18 Avg: 10 Max: 83 T: 1 ( 1469) P:80 I:200 C: 379008 Min: 6 Act: 19 Avg: 10 Max: 68 T: 2 ( 1470) P:80 I:200 C: 378802 Min: 7 Act: 19 Avg: 10 Max: 79 T: 3 ( 1471) P:80 I:200 C: 378595 Min: 7 Act: 20 Avg: 10 Max: 75

What is your goal? 25.02 is a stable release. There is no 25.05 stable release yet (that will happen towards the end of next month). So what is out there now are daily development rolling builds of 20.05. So if you want to track development then this would make sense (note the use 0f the word 'daily' there, things can change that often, and these changes aren't well tested yet), but if you want tested stability then you should wait until the next stable release comes out.

What is the purpose of using this core? Several people have already tried to build a real-time kernel here on the forum. They all face some challenges. Perhaps, if the tasks that such a core should perform are of a general nature, we can provide a configuration for its assembly. You built it yourself. Can you provide a difference in the configuration file for the same kernel version? As diff -u command.

Thank you for your response. I pulled down one of the "Standard Support" images. I enabled the overlay, and brought the interface up, but scanning does not return anything: root@bananapim4zero:~# iw dev wlan0 scan root@bananapim4zero:~# I wanted a 6.12 kernel that had real time extensions built in. I didn't realize 'current' would handle that. I will end up replacing this with a current kernel. I can't remember how anything < 6.12 handles real time patches. Maybe Armbian does it automatically as part of its patch set.

I used this image as base and from there did in-place full-upgrade: It used to lock-up with a kernel crash after 2 - 3 days, kernel 6.6.44 till 6.6.75. I have no HDMI connected anymore, only serial console cable, SD-card, microUSB power, RJ45 and SATA 8T HDD. Now with kernel 6.12.20-current-sunxi uptime already 6 days. I have radically modified partition setup, use Btrfs for rootfs, I do not use Armbian initial repartition scripts, that seems to be the point where your M1 fails. You need serial console cable and post clear text output where it fail. Still then, it might be too complicated to or time consuming fix. You could prepare/create/build a new own image using Armbian build. Or just stick to that older working image. It could be that the GUI drivers like it was in older kernels is dropped after 5.10 kernels or so, that happens to older hardware unfortunately. What is the kernel version where it still does work?

I have installed Armbian 25.02 via an official Armbian image for Armbian 25.02 (Debian 12) Vendor Kernel 6.1.xx, is it possible (and sane) to upgrade to Armbian 25.05 (Debian 12) Vendor Kernel 6.1.xx? If so besides downloading the new image and installing fresh what are one's options?

A little clarification. Just install the EDGE core. The version must be 6.13.11 or higher.

OK .... baud rate was too low ... I went up to 1500000 and I now have a serial connection using those debug pins a a orangepi 4 lts terminal on my desktop

I'm new to the Orange Pi 4 LTS. I work SBC's headless and have installed using UART many times on RP Zero's, BananaPi's and most recently on a RockPro64. However, I am not sure if I should be using. Is there another set of UART pins besides the "debug ins"? Booted the image on an sdcard connected to the debug pins and just got 8 lines of this stuff <��6v��Ή9�.�����goO

Several patches add I2S digital output on I2S3 channel. Tested with branch 25.02 / 6.6.72 .

Sorry to bring this back up but I'm having exact same issue on latest releases. I'm able to boot an older 21.05.1 release for the PineCube but the 25.5.0-trunk.87 and 25.5.0-trunk.444 have the same issue. Upgrading the 21.05.1 via apt update && apt upgrade broke it once again with the same overlap issue. ## Loading init Ramdisk from Legacy Image at 41b00000 ... Image Name: uInitrd Image Type: ARM Linux RAMDisk Image (gzip compressed) Data Size: 11237905 Bytes = 10.7 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 41800000 Booting using the fdt blob at 0x41800000 ERROR: FDT image overlaps OS image (OS=0x41000000..0x41a72768)

The SD card problem is ruled out since I tested another system on the same card and there is no problem it works perfectly example image, 2022-04-17-ubuntu-16.04-mate-desktop-mpv-1080p-bpi-m1-m1p-r1-sd-emmc.img . Other systems like lakkaTv also work, I tried with several USB power adapters and it only generates problems with modern versions of Armbian

I suspect I'm talking to myself here, but for anyone with a clearfog base or pro system, by following similar steps to what was outlined here I've been able to get my clearfog base system to boot and operate correctly using the latest kernel image and other packages. Additionally, as I covered previously in this thread, I had been dragging an old sata-capable u-boot binary around but I installed u-boot to SPI using armbian-config and after doing that I don't think it's necessary and longer (and maybe hasn't been for a very long time...) to fuss with installing it to the boot media. Just change the jumpers to use SPI and let it go. To use the latest kernels, there's an issue where the kernel and initrd grew and overlap now which caused the breakage. Add this to /boot/armbianEnv.txt before installing the new kernel: I then unheld all the packages and rebooted and now I'm on all current software.

Did I not break anything, then? everythink is OK? my PC was rebooted and no problem was raised, but now the login console differs. I will look into the next steps to stay updated. If the information I am reading is accurate, the branch jump is risky . Some hint about How to update my system? (i came from archlinux , and the branch concept is something new for me) Thanks for the response.

Slightly off topic, but a very similar problem (if not exactly this problem) is a current issue for clearfog base and pro as they're based on the same SoC and use the same kernels. I had been running on an older kernel with some packages (including the kernel) held by dpkg. I also had never installed u-boot to SPI before (running it off my boot media instead). This morning I installed a newer u-boot to SPI (maybe not necessary), included the same offsets to armbianEnv.txt, unheld all packages, upgraded everything and rebooted - and everything worked. Thanks to everyone that contributed information here. Hopefully we can keep these systems running for a bit more now!

some photos ... and dts file with working hdmi, lan and two usb ports, "RED" led --- TESTED meson8b-sencor.dts

@firepower I tried to replace the original BCM4334B0.hcd file with these two and bluetooth did not work with either file on my Vontar H618

Remind me. Does WiFi works in image from download section? https://www.armbian.com/download/?device_support=Standard support This (EDGE kernels) raises support costs into the sky and since from open source developers position 99.5% costs are not yours ... use current kernel. Its a huge difference between those two, one has been stabilized, the other not, probably next year, most likely never and will be replaced with next EDGE, 6.14.y with stabilization attempt in more then one year from now. Also legacy 6.6.y would be better for this job. Higher number doesn't mean better functionality and less bugs, often right the opposite. Try this way: sudo ip link set wlan0 up sudo iw dev wlan0 scan

What SD card are you using? I don't believe the A20 is up to the task of running a modern desktop. It could still be a power issue if indeed no LEDs are on at all. Does the device turn off happen randomly or when the Banana Pi M1 power down when under high load? I'd advise getting a USB to Serial adapter to get a better idea of what is happening on the board. Best of luck Ryzer

A few days ago jammy and bullseye were moved to eol. While upstream may support these userspaces a few more years, Armbian does not have the resources to support more than the most current stable releases of Debian and Ubuntu, which are Bookworm and Noble at this time. You can still select them to build when passing EXPERT=yes switch to ./compile.sh but do not ask for support if something breaks. You are on your own.

@iTux Your posts are not appropriate for Armbian forums. You are using non Armbian code. You should post your information in the channels that they provide. Ophub is a fork of Armbian. They do not contribute to Armbian development, nor do they contribute to these forums. They use the Armbian name without permission and cause significant confusion as a result. (Like in your case where you think you are using Armbian and you are not).

I think this is your underlying issue. Focal was dropped from support a year ago (by both Ubuntu and Armbian). So the underlying packages you need are likely no longer in repositories.