All Activity

I have tried to download at least 3 times this image: Armbian_25.8.1_Orangepi5-plus_noble_vendor_6.1.115_gnome_desktop.img.xz All sha256sum verified Ok. And wrote 5 times on 3 different SDCards, and this img does not boot on my OPI-5-Plus. No image on monitor, partition armbi_root not expanded, no green lights... Just unusable (for me). Other img's that boot are OK: Deb-xfce, noble-cinnamon, noble-neon... Someone got success with this img??? I'm looking for a distro that works well on OPI5-Plus, well configured, and that works with HDMI audio. The best for now is Noble-Cinnamon but failed to setup Menu button, and I cant find support until now to solve this issue. Thanks, Cury

I see on the mint website that there is nothing mentioned about Arm64, so consider mint as 'stay away' if you use Arm64. You have to do it yourself, so I would go for the most integrated solution. Mint is good for x86, because Ubuntu kernel an various proprietary HW, but that is all not the case for an OPi5+. I would take Debian as base and put Cinnamon on it. You can do it yourself by running 'sudo tasksel' or you put EDK2-UEFI v1.1 firmware on the OPi5+ and use https://dl.armbian.com/uefi-arm64/Trixie_current_cinnamon The missing start button might be complicated to fix, it can be due to some tiny error somewhere when you did setup the computer. Maybe a second try it will work, but maybe it is a real bug. I have only ran Cinnamon once for test for 15 minutes or so, it worked, but I use KDE normally, so have no clue where to look to fix it.

My post on Mint Forum was rejected: Somebody knows were Can I get support for Cinnamon on Armbian distros???

Hi all, I decided to revive my old rk3229 board with NAND. Could someone please tell me how to unbrick it?

Just an information about the `edge` kernel (6.18) when used on the cm3588-nas system. The rtc driver is not initialized on a `poweron`. After a poweron, you will see the following in the log. Nov 11 01:17:10 uhutest kernel: rtc-hym8563 6-0051: could not init device, -6 Nov 11 01:17:10 uhutest systemd[1]: System time advanced to built-in epoch: Tue 2025-11-11 01:17:09 CET If you have `fake-hwclock` running, you will see the following a moment later. fake-hwclock restores the time, but the service will not properly start, because of the rtc device error. Nov 11 01:17:12 uhutest fake-hwclock.sh[461]: Restoring saved system time Nov 20 13:22:43 uhutest fake-hwclock.sh[466]: Thu Nov 20 01:22:43 PM CET 2025 Nov 20 13:22:43 uhutest fake-hwclock.sh[468]: hwclock: Cannot access the Hardware Clock via any known method. Nov 20 13:22:43 uhutest fake-hwclock.sh[468]: hwclock: Use the --verbose option to see the details of our search for an access method. Nov 20 13:22:43 uhutest systemd[1]: fake-hwclock.service: Main process exited, code=exited, status=1/FAILURE Nov 20 13:22:43 uhutest systemd[1]: fake-hwclock.service: Failed with result 'exit-code'. Nov 20 13:22:43 uhutest systemd[1]: Failed to start Restore system time on boot and save it on shutdown. You would need to restart the fake-hwclock service, if you want that it saves time before the next restart. If you do a `restart` of the system, the rtc device will get properly initialized and time is good. Following is seen in the logs. Nov 20 13:26:14 uhutest kernel: rtc-hym8563 6-0051: registered as rtc0 Nov 20 13:26:14 uhutest kernel: rtc-hym8563 6-0051: setting system clock to 2025-11-20T12:26:11 UTC (1763641571) Nov 20 13:26:16 uhutest fake-hwclock.sh[455]: Not restoring old system time I have seen the issue right now only with the 6-18-RC kernel. The following patch mentioned here works as a pure workaround. https://patchwork.kernel.org/project/linux-rockchip/patch/20220608161150.58919-2-linux@fw-web.de/ Lets see how the development of kernel 6.18 goes and if the final version will not have this issue.

Is there any chance of this image running on a device using the RKPX30 chip? From some research, it seems to be a variant of the RK3326, and I'm not sure how similar the 3328 and 3326 are or are not. Or is there another Armbian image for the RKPX30/RK3326? Specifically looking to run Armbian on this: https://docs.revrobotics.com/duo-control/control-system-overview/driver-hub-specifications

Hello SteeMan, Thanks for your answer Its running now And I will browse the getting started pages To get this system running well It seems faster So i hope i can learn a lot at this forum Greetings Herman

https://docs.armbian.com/User-Guide_Getting-Started/#first-boot

Hello everybody, I am new at linux have ubuntu running on n old windows laptop now I found a new use for my old TVBOX i have lying around I need some help logging in to my tv box it is a T95ZPlus with a 912 soc I am booting Armbian_community_25.11.0-trunk.519_Aml-s9xx-box_plucky_edge_6.18.0-rc6_xfce_desktop.img.xz I copy u-boot-s905x2-s912 to u-boot.ext My extlinux.conf looks like this label Armbian_community kernel /Image initrd /uInitrd fdt /dtb/amlogic/meson-gxm-t95z-plus.dtb append root=UUID=8ba6ae05-2bb2-4d2c-bba6-ce6cd91ed2cb rootflags=data=writeback console=ttyAML0,115200n8 console=tty0 rw no_console_suspend consoleblank=0 fsck.fix=yes fsck.repair=yes net.ifnames=0 The system runs but after booting Armbian_community 25.11.0-trunk.519 plucky tty1 it gives me this prompt aml-s9xx-box loging the tutorial tells Basic OS configuration is conducted at first boot. You are asked to set a root password, normal user But my system asked for a login so i am stuck I hope someone have had this problem and can give a solution Greetings Ducdreamer

Quick update, having sorted this out I went on to install a CanBus device only to have to enable it again, so I'm back to the same delay

current isn't a good option for rk3588/s devices. At this point of time barely any support for this SoC was mainlined. And it seems like later revisions introduced a regression causing a crash. Since 6.18 may become next LTS kernel it will replace current current kernel at some point. So better go for an edge based image instead.

orangepi5 and 6 have nothing in common. double-check what you are actually talking about. Also there is no 0.9.9 rknpu stuff. 5.10 bsp has been abandoned long ago.

...

ok same error. The maxio module works with this snippet though : mdio { compatible = "snps,dwmac-mdio"; #address-cells = <0x01>; #size-cells = <0x00>; phandle = <0xee>; ethernet-phy@0 { compatible = "ethernet-phy-id7b74.4411", "ethernet-phy-ieee802.3-c22" reg = <0x00>; status = "okay"; phandle = <0x51>; }; };

yes. Things that can be tried: - DTS phy-mode = "rgmii-id"; or phy-mode = "rgmii-rxid"; - UBOOT CONFIG_PHY_REALTEK=y CONFIG_DWC_ETH_QOS=y CONFIG_DWC_ETH_QOS_ROCKCHIP=y CONFIG_DM_PMIC=y CONFIG_PMIC_RK8XX=y CONFIG_REGULATOR_RK8XX=y CONFIG_PWM_ROCKCHIP=y

OK do you mean boot with ethernet working using the maxio module then change DTB and reboot?

Can you boot in a working ethernet and then reboot to this trial?

I have a very similar if not the same issue on my Odroid M1. When doing a reboot it won't detect the SATA hdd. The NVME is working fine and I am booting the device via a sdcard anyway. Aparantly it has something to do with the kernel. Once I shut down the odroid and power it on again (cold reboot) the SATA device is just working fine again. I did not find a solution for this so far but I keep on digging...

@makaOK I corrected my error and tried your suggestion but i get in dmesg : [ 47.378829] rk_gmac-dwmac fe010000.ethernet end0: Register MEM_TYPE_PAGE_POOL RxQ-0 [ 47.380072] rk_gmac-dwmac fe010000.ethernet end0: __stmmac_open: Cannot attach to PHY (error: -19)

Hello comunity members, I've installed and run Armbian_community_25.11.0-trunk.437_Tanix-tx6_trixie_current_6.12.47_minimal Since my Tanix TX 6 is running pretty hot in my opinion I want to reduce the operating frequency. Please help me with some instructions how to do so, since I couldn't find any. Thank you in advance.

I know that told you the ID of your chip but also told you to switch to phy1 but you didn't. I think It is possible to use the generic driver but don't know if It will work. Changes in dtb must be accurate.

Thank you! I'm still in the middle of a long build (chromium). I'll be able to check the flash-image-DDR4-1g_1cs_5-1200_750 image with the specific device I own with frequency scaling enabled and report if it is stable or not. It will crash pretty reliably if the firmware doesn't have the change I submitted here: https://github.com/MarvellEmbeddedProcessors/mv-ddr-marvell/commit/622677674cf34ef8fdf75b0c580d27efc8628ae8

Apologies, I somehow missed this comment until after I'd posted mine Would have saved me a fair bit of searching had I read it

@maka Thanks for this suggestion. I'll look further into this. The reason I made that change was because you suggested it here : It works well to auto load the maxio module on startup without resorting to manual modprobe commands. Is it really possible to use a generic driver for this maxio NIC chip?

I would always go RPi, as I have been burned going with a different board in the past. This may not be a fair reflection on the Orange Pi, as I can only speak for having purchased an Odroid C1+ many years ago. The C1+ was a very capable board, and definitely more capable than the RPi offering at the time. However, there just is no substitute for the support and community around the RPi. I now have 3, and even my original RPi 1 Model B+ is still supported by the RPi foundation, and still gets modern kernel and OS updates. This is a board running off just 512MB RAM, A 700 MHz single-core 32-bit processer and released over 11 years ago. No one could complain if they had dropped support long ago, but they didn't, and they still show no signs of dropping support any time soon. Hardkernel, on the other hand, pretty much dumped support for the Odroid C1+ as soon as it released, so it is stuck on a 3.x kernel and a uBoot from 2011. If it wasn't for the Armbian project this board just would not be useable, and even then, we are still stuck on a 15 year old uBoot solution. None of this may be important to you, and like I say, my experience is not likely a like-for-like comparison with the Orange Pi, but the long term support you get from the RPi foundation and the wider community around it is not even close to being matched by any other vendor, and (personally) I don't like supporting vendors who effectively manufacture e-waste.