All Activity

Hi all, sorry for a kiddy queston but it the first time when I'm using Armbian. I need to enter to u-boot menu/enviroment/shell and I can't I try to press any button when I'm rebooting but nothing happened and i've just have a booted system I have only UART to my system. In other devices I have some time to press any key to enter to u-boot shell but there I don't have time. U-boot exec bootcmd immediately I need to enter to u-boot shell and reconfigure some env for my work. I use Armbian 25.8.2 noble

Same deal using Noble; https://paste.armbian.com/orexafoxen.less

Hi Unfortunately, I use an Odroid N2 (and N2+) for nextcloud installed via the nextcloudpi script. Now, the support is gone and there are no longer updates for nextcloud beyond version 30.0.x available. Currently I am running nextcloud 30.0.17. The version 30.0.x will reach end-of-support soon. I can imagine the following alternatives: Use armbian-config to install nextcloud - but will it do the update correctly or at all esp. for my external disks which nextcloud is using ? Use the image for the Odroid C2 (another arm-based SBC) and replace the kernel by the one for the Odroid N2+ Port the script from the Odroid C2 image to my Odroid N2 Buy an Raspi 4 or, even better, a Raspi 5 and use the images for that HW - how about a migration path ? So what do you suggest ? I think I could do all of those alternatives myself and I have an Odroid N2 and an Odroid N2+ useable for testing purposes. One of those was planned to run HomeAssistant and I'm happy that HAOS is supported on my hardware. But that can be postponed to later. Kind regards Norbert Edit: Added question for the migration path if HW changed to Raspi 4 or 5

I am using the Noble image. I have added the following entries to config.txt: usb_max_current_enable=1 enable_uart=1 dtoverlay=uart0 dtparam=pciex1 dtparam=pciex1_gen=3 max_current_enable=1 dtoverlay=disable-wifi dtoverlay=disable-bt I now have both ttyAMA* devices. As the next step, I tried to remove the ttyAMA10 getty and add a ttyAMA0 one: systemctl disable serial-getty@ttyAMA10 systemctl enable --now serial-getty@ttyAMA0 But it doesn't seem to work. I'm still not seeing any activity in minicom. (It worked right after installation, and I haven't touched the wiring since.)

I installed a fresh Trixie img to SD, made the adjustments I suggested, booted, upgraded and rebooted. root@rpi5b:~# ls /dev/ttyAMA* /dev/ttyAMA0 /dev/ttyAMA10 Still there.

@Gilliard Gabriel Rodrigues Mark was using my Transpeed image. https://github.com/NickAlilovic/build/releases/tag/20250306

Yes, I kind of reached the same conclusion, unfortunately. BTW, does it have any mode, where it would do a dry run, and tell you what it would modify? As for ttyAMA0, I don't seem to have it, even though have the UART enabled in config.txt: The priority increase seems to work, in the sense that serial now likely has the upper hand, but the system is not booting, so something is likely not working. I will try reverting the console priority.

Without it being enabled in the config.txt file `ttyAMA0` isn't visible under /dev, last I checked. pibox: ~ $ cat /boot/firmware/config.txt | grep "enable_uart*" enable_uart=1 pibox: ~ $ ls /dev/ttyAMA* /dev/ttyAMA0 /dev/ttyAMA10 I wouldn't use `raspi-config` on an img that isn't RASPIOS. I feel that is bound to produce failure.

Give serial priority console=tty1 console=serial0,115200

Furthermore, I found the following: I used the noble xfce image from 2025-08-08 The serial console (login console, not boot console!) worked initially After the install, I did an apt-upgrade, and also used raspi-config to enable the serial console After that, the systemd console service seems to have moved from ttyAMA0 to ttyAMA10, and I am gettin no output in minicom So I have mixed feelings.

Hi all, digging into the Orange Pi 6 Plus specs for a potential build. Can anyone confirm the M.2 slots (the two Key-M 2280 ones) are PCIe Gen 4 with x4 lanes each? Official docs mention NVMe support but are light on details. I'm curious if this could handle a low-end GPU like an RX 570 (or even lower) through an NVMe-to-PCIe adapter/riser—thinking for light gaming or compute tasks. Has anyone tried eGPU setups on this board or similar ARM SBCs? What about power delivery, drivers, and performance? Running Linux (Ubuntu/Debian probably). Thanks for any insights or benchmarks!

Hey everyone, I'm eyeing the Orange Pi 6 Plus for some edge AI projects, given its 12-core CIX SoC, up to 28.8 TOPS NPU, and massive RAM options (16/32/64GB LPDDR5). Has anyone gotten Ollama running on it with NPU acceleration? Does it support it out of the box, or do you need to convert models (e.g., to INT4/INT8 formats) using custom tools like rkllama or similar? Additionally, with the higher RAM, can it handle bigger LLMs (like 13B+ models) more smoothly than lower-spec SBCs? Any benchmarks or tips on setups (e.g., Ubuntu/Debian installs, frameworks like MLC-LLM)? I'd love to hear real-world experiences—thanks!

https://github.com/armbian/build/blob/main/patch/kernel/archive/rockchip64-6.18/dt/rk3568-yy3568.dts

Simple GPIO toggling has been a long term issue and it is clear to me that it need continued attention. I only use pin toggle on RPi1 and NanoPi-NEO, so BCM2735 and AllwinnerH3. I use generic Linux gpiod, still a bit a workaround for really proper handling, but it is OK for non-critical tasks at home. I used orignal WiringPi on RPi before (from Gordon), but many forks now. See also: https://forums.raspberrypi.com/viewtopic.php?t=369361 'latest' seems to be here: https://github.com/WiringPi/WiringPi?tab=readme-ov-file Note what is written under Ports w.r.t. Python. I guess Werner's guess is correct. I am not good at Python so prepared a bit for own C-code implementation, also w.r.t. high speed PWM. On AllwinnerH3 running Armbian Trixie, using the lgpio examples was easy to toggle a pin. I currently have Domoticz doing it, so also easy MQTT messaging, but it is overkill and also Domoticz build for ARMv6 is not available anymore (needed for RPi0/1), so already replaced that.

Thanks @eselarm for the details, very helpful! That's what i was expecting, but not sure. There is a /dev/media# device separated for each decoder and encoder, each with the source / proc / sink pipeline plus /dev/video# for each. Meanwhile i figured out there is a bug inside the sunxi_cedrus driver (enc by bootlin) but im still not done with the fix. As of now, since this morning i've now both video# devices where video0 appears as the decoder (as before) and now there is video2, encoder! T. btw. Thanks Paul @ bootlin 😃 👏 👍

Okay, I tested, but it works kind of weird: they work in tandem, but the boot messages were only output to the video console, not on the serial one. Once after the initial automatic login, the output started to go to both consoles, but the initial and systemd boot messages were only output to the video console, which would have made sharing the details of the initial problem difficult.

@c0rnelius Thanks for stepping in to help. I've added enable_uart=1 to config.txt In cmdline.txt, I currently have: console=serial0,115200 console=tty1 ... Do the two settings work in tandem, or do they override each other?

We don't deal with android. I suggest to ask at xda developer forums or similar.

Just a wild guess: The code from orangepi wiringpi is old and no longer compatible with newer python which is shipped in Trixie.

Success! It's still showing that first error, but using meson-gxbb-wetek-play2.dtb it was able to boot up and configure. Wifi works also. You guys are amazing! Thanks for all your inputs.

I'm trying to download and reinstall android os on an x88 pro 10 to try and get it working. I have downloaded the file and flashed the device several times but cannot get past the boot up screen I have attached a usb keyboard and mouse but no luck.looking for someone i can chat with step by step

Hello everyone! First of all, thanks for the useful thread. I'd like to know if you got the files for the SD card, Guillaume lopéré. And if installing this armbian I'd be able to use the tv box as a home server, deploying a Node.js project and using Docker. Best Regards, Gilliard

can you please share the config for the 3568 / or patch so I can refer to for the 3399 chip? Thank you!

I tried Armbian_community_25.11.0-trunk.413_Aml-s9xx-box_plucky_edge_6.18.0-rc3.img I think the same is happening ... I did end up with the first error, as seen in the first pic above: https://photos.app.goo.gl/Y5GM3a6XUy6SZ6JA6 But then I got a nice Armbian splash screen, eventually it ended up going to initramfs, but interestingly no error about waiting for the FS was reported this time.. .... Begin: Loading essential drivers ... done. Begin: Running /scripts/init-premount ... BusyBox v1.37.0 (Ubuntu 1:1.97.0-4ubuntul) built-in shell (ash) Enter ‘help' for a list of built-in commands. (initramfs)

Try a build using a newer edge kernel as a test