Werner

Panfork is under heavy development/cutting edge so issues are to be expected. Alternative would be to use Rockchip proprietary binary blobs but they seem not to work very well either. On the bottom line nothing Armbian can fix (easily).

15Mbaud? Are you sure it is not 1.5Mbaud?

Just as a general experience from myself I never had good success on any kind of converter adapters regarding DP, HDMI, DVI or VGA when using with ARM boards. No idea what the cause is. Maybe general lack in drivers to mitigate such configurations... If somehow possible try to connect native.

Did you leave the microSD in after move? Booting directly from USB is not possible afaik but you can have the boot loader on sd which then boots from USB.

Scroll down and check for other download variants.

Probably related to

Tried using extraargs= in /boot/armbianEnv.txt?

Check output/debug folder for further clues. Try building from armbian-next branch.

FYI you are using both unsupported build and userspace.

Either use dpkg to remove "hold" of all firmware packages or apt install armbian-config

moved to userspace

Maybe because OPi simply forked and rebranded our config utility

Maybe the user account needs to be added to xrdp or similar usergroup for permission?

Try using code { font-family: Consolas,"courier new"; color: crimson; background-color: rgba(0, 0, 0, 0.2); padding: 2px; font-size: 105%; } armbian-install script.

Raise issue on vendor forums. moved fixed tag

It may, depending on your choice.

https://forum.armbian.com/terms

tried armbian-install?

Neither a tutorial nor a howto but a request. Moved.

Providing logs with armbianmonitor -u helps with troubleshooting and significantly raises chances that issue gets addressed.

https://github.com/armbian/build/issues/4765 Please share your opinion on that directly on Github.

split

No, there is no easy way to switch to stable No, there isn't anything bad besides the message about being WIP Yes, you will receive updates.

Hey there, from time to time we have to decide on which boards we drop the maintained status and stop development in order to keep (or try at least) the workload for us at a controllable level. These boards are not necessarily end-of-life (EOL) but reached a decent enough state to let them go from active development. Though after today's developer meeting we are unsure how to name these boards. Therefore we ask our community what they think. Let us know by either voting or leaving a comment below. Thank you for your feedback!