Werner

./compile.sh BOARD=orangepizero3 BRANCH=current RELEASE=trixie BUILD_MINIMAL=yes KERNEL_CONFIGURE=no https://docs.armbian.com/Developer-Guide_Build-Preparation/ replace BRANCH with edge if you prefer more recent kernel. replace RELEASE with noble if you prefer Ubuntu flavour. remove BUILD_MINIMAL=yes to get the choice to build a standard cli image instead of minimal/iot.

Hi, difficult task since there is no support for the whole chip family in the framework yet, but first steps are here:https://github.com/armbian/build/pull/8364 I suggest to start by getting familiar with the framework and how the mentioned pending pr it put together. moved

Switch to edge or vendor kernel (latter either with panthor overlay or proprietary mali blobs). current is a bad choice for desktop usage.

Not planned but should be possible. A good start would be to copy the mentioend 2f and extract the device tree from official image and add it to vendor kernel source. If you're lucky that's all what's needed to get it to work.

moved to offtopic. not using Armbian. If you need support with that image, ask at the place where you downloaded from.

RTL8211F is the interesting label.

moved to tvboxes for now. perhaps anyone has a clue how to get rid of Android before continuing.

Use them as command line switches, like code { font-family: Consolas,"courier new"; color: crimson; background-color: rgba(0, 0, 0, 0.2); padding: 2px; font-size: 105%; } ./compile.sh BUILD_MINIMAL=yes FULL_DESKTOP=no ... Used by CI only which kernel to do automatic build tests.

apt install f2fs-tools

moved

moved

Not an Armbian image. If you want to use this one, try to get support from where you got the image from.

moved to tvboxes

You don't have to run on bare-metal. A proper VM will do too and is probably the better solution. Yes. Cross-compiling is used for everything that's not native. You're aware that the command in the docs is just an example, right?

Armbian does not come with some sort of admin console. Please elaborate. Try different patch cable. moved

where exactly does this error show up? while downloading with your browser? while writing to the sdcard? while booting? Please elaborate. debug boot issues: https://debug.armbian.de

It seems like there is a mix-up between specs for the framework and for the OS. A lightweight desktop can run on 512MB, yes but probably not much fun, depending on applications. Won't recommend running a web browser. I'd probably get some existing cheap sbcs with similar specs and play with them to elaborate if the performance is sufficient.

IIRC until like half a year ago this also worked just fine. I assume then this check was introduced upstream which caused this - more or less cosmetical - error.

@JohnTheCoolingFan any clue?

moved. All boards using rk3588/s soc most likely work best with either vendor or edge kernel. Current has limited functionality since when this kernel became LTS only basic support was there. All further enhancements regarding hardware featureless were upstreamed later.

I think there are some directories in /etc which contain initramfs pre/post scripts. I don't have hw on hand to check right now but I believe there was some script starting with z50- filename that contained this check and there should be a 2nd one from Armbian that actually does what the upstream script refuses to do.

It would make more sense to send a PR to fix this so it is included in all upcoming images/releases.

https://docs.armbian.com/User-Guide_Getting-Started/#flash-to-sd-card

I think this "unsupported version" thingy when doing initramfs update is just a cosmetical thing. The script comes from upstream and checks for version string included in upstream (directly from Raspberry to say) kernels. However I believe this has been worked around by our own bsp which is silently executed right after. Cannot tell for sure if that's the issue I remember it is since I don't have access to hw atm.

Have you tried to get into by keyboard/hdmi or serial console? If so you could track down why sshd refuses to start