guess it kernel/driver issue The driver does not request the stmmaceth (emac1-25M) clock during probe. Without this clock the MDIO bus does not function on cold boot - PHY ID reads as 0x00000000 and kernel falls back to Generic PHY instead of YT8531. Ethernet does not work until warm reboot.

I've just installed Ubuntu KDE vendor image and now the proper refresh rates are detected. Thank you However, now it seems video players are not working properly. No HW decoding and no audio. It works if I play youtube videos through via Chrome though Strange thing is that after the clean installation, lots of basic KDE packages were missing (dolphin, Konsole, mpv, etc), which I had to install via apt. After that I also performed a apt full-upgrade, but it didnt solve the problem Tried to play h264 and 265 with no success I add some logs, but feel free to request more if they may help

I have a Orange Pi Zero 3 4GB Board. It uses a Micron LPDDR4X RAM and H618 Processor. I have tried a plethora of distros and tried to change Uboot and DTB but unable to make it work. Spent days on Gemini and Claude but no luck. Below is the output from UART debuggger: The Highlight being Unhandled Exception EL3. U-Boot SPL 2025.04-armbian-2025.04-S3482-Pf089-H8869-V3d5b-Bb703-R448a-dirty (May 25 2025 - 14:46:18 +0000) DRAM base address is defined as 0x40000000 DRAM has 16 b/raw, 10 b/col, 4 B/width, 2 #rank and 8 #bank DRAM top address must be less than 0x100000000 DRAM: 4096 MiB Trying to boot from MMC1 Unhandled Exception in EL3. uart_opizero3.txt

how to enable KVM on Armbian ?

I think most important is that people make sure they can fix their own issues if a HW/computer fails. I found high-availability interesting, but for just my house (or even 2 places/countries at the same time) I found it too much to make it all work. The thing I could maybe use is DRDB, however I see v9 is under development since 2011 and it still is not in mainline kernel. Compared to that I have some script to transfer latest differential Btrfs snapshot from 1 computer to the other on-the-fly, I doubt I can really benefit from DRDB, but maybe I set up a test and see what it does. I use only ARM64 for 24/7 servers, so no x86_64 <=> ARM64 incompatibility. So same as for ZFS for example, it is external to Linux distro and my experience is that complicated issues/failures always happen at the wrong moment, e.g. also no internet and/or mains power failure etc. So I try to minimize the amount of 'external' HW/SW modules, certainly if the backing company is commercial and in whatever country far away from where I am. Proxmox is nice, but also 'external'. Same for even Docker, so I have actually no such containers. But it all depends on how much you are involved in various HW and SW. As you can see in my earlier message, I already forgot HA was available as generic aarch64 image, so that says enough. I use several custom (own) HW (like 'changed' solar inverter) and HomeAssistent does not support it, so I actually do not really use it. It is mostly C-code and Node-RED in conjunction with various micro-controllers. A good test is to disconnect internet (power-off fiber-RJ45 box in my case) and/or also do an ad-hoc power cut (no cheating with UPS). And then see if you can get it all running again within a certain time frame (what you think is acceptable, like before temperature in freezer gets > -10 or so).