Hi. At first I'd like to apologize for the tone of this post, but there are things that I've been fighting with, without any success, for a long time.
Problem 1.
I have, as it seems, a very common problem with Armbian on RK3399.
I burned Armbian 23.8.1 for the Rock Pi 4C+ onto an eMMC module, which booted, but there is no HDMI video output.
I can't SSH into it over ethernet and provide more details because the server is disabled by default.
I assume that the problem here is the same one as I often see coming back to all RK3399 boards and the solution is always the same - "libreelec patches for the HDMI subsystem" (whatever they are). If it's so common then why is it that Armbian releases never work out of the box? With all due respect for the maintainers of course. At this point wouldn't it be easier for RK3399 boards maintainers to just make a tutorial on how to patch the thing up so that new users could do it themselves without waiting or taking up their time?
Problem 2
Also another thing I wanted to ask is why do Armbian people never care about providing overlays for interfaces and peripherals that manufacturers do support in their own images? I'm sorry for sounding arrogant and demanding even though I have no idea how to do things on my own (although I would if I knew how), but I've been tinkering with many different boards over the past months and there's always the dilemma - either use Armbian which has the most up-to-date kernel, often mainline support and graphics drivers but completely non-existent interface/peripheral support, or use the manufacturer provided images which have good interface/peripheral support, but are often quite inflexible and maybe a little outdated. Can't have both and it's all extremely annoying to deal with, especially since getting into building your own images and doing it right, figuring out all the quirks and actually creating support for features is extremely hard because it isn't exactly explained anywhere. As I said, I've been tinkering for months and I only scratched the surface so far. I really don't want to be the "somebody please" guy, but [...].
This is the problem with community-provided support.
And it's just so natural for Linux to constantly have problems because of this development model... Not just on ARM SBCs...
No structure, no clear goals, no group efforts, low funding... Just random people doing random stuff in their free time mostly (you're welcome to yell at me if I'm wrong)...
In the end it's a coin toss if things work or not.
