Werner

armbian-config, go to system, go to hardware then you see a menu like this: Check for uart options.

Once chosen and restarted check code { font-family: Consolas,"courier new"; color: crimson; background-color: rgba(0, 0, 0, 0.2); padding: 2px; font-size: 105%; } dmesg for activated serial consoles. They probably pop up as devices like code { font-family: Consolas,"courier new"; color: crimson; background-color: rgba(0, 0, 0, 0.2); padding: 2px; font-size: 105%; } /dev/ttyS1 and so on.

Check armbian-config for DTB overlays.

If nobody sends PR nobody will do it...

Hey there, I now have my Nanopi R4S for quite a while but never got it to run stable over a longer period of time. Now I finally connected another board to its debug serial in the hopes to catch something that causes the board to freeze. Well this is what I have collected: https://p.na4.eu/?bc818aefadc9b5b2#DAunYKXghkaqcLhh8SLWMKTWABewpwPJRnHMHDemR98Y The log is complete, there is nothing missing between 08:51 and 19:14. This is how I collected it. Basically during the state of throwing errors the board becomes unresponsitive and continously heats up. Active cooling was in place so no danger of overheating. https://paste.armbian.com/ijoromadit Result is the same for current 5.15.y kernel.

Welcome!

Well ARM architecture is not as convenient as x86, not in the price range the boards we support at least Anyway even as beginner having an USB UART adapter is highly recommended since it is the best (and most of the time the only) way to track down boot issues. They are dirt cheap and extremely useful when dealing with SBCs...

Two ways: Get a UART serial adapter and use debug console to get in get an eMMC-USB adapter to mount it on a different computer and restore functionality. Also worth a try: write a fresh image to an sdcard, plug it in and boot. Ideally it should boot from SD, then mount eMMC and do adjustments.

Check archive: https://archive.armbian.com or https://github.com/armbian/community/

Use it. There is such thing like self-tests. Get better CPU. Building a kernel on a potato takes as long as it takes There is a reason why we collected money for something more powerful to speed builds up a while ago: Create a PR to the build script. https://docs.armbian.com/Process_Contribute/ https://docs.armbian.com/Developer-Guide_Adding-Board-Family/

Maybe related to

Yeah maybe. However it is quite basic knowledge that ppa's are a Ubuntu thingy IMHO...

Old ugly EOL-kernel legacy image received fixes for booting. Feel free to test. https://imola.armbian.com/dl/orangepizero2/archive/

Yes, of course. auto-correction got me

This can only be answered by you since you are responsible for the security of your device so decision is yours if firewalling is necessary.

Try to copy this file and both rename it and adjust naming inside: https://github.com/armbian/build/blob/main/config/boards/orangepipc.conf

Topic split to keep FAQ/Instructions clean.

There is not. Install code { font-family: Consolas,"courier new"; color: crimson; background-color: rgba(0, 0, 0, 0.2); padding: 2px; font-size: 105%; } iptables or code { font-family: Consolas,"courier new"; color: crimson; background-color: rgba(0, 0, 0, 0.2); padding: 2px; font-size: 105%; } nftables or a framework like code { font-family: Consolas,"courier new"; color: crimson; background-color: rgba(0, 0, 0, 0.2); padding: 2px; font-size: 105%; } ufw via apt that makes use of either one of those.

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

There are literally thousands of devices that could fit into that description. Therefore answer is impossible.

moved

We do not provide support for 3rd party images. Get a genuine Armbian image here: https://www.armbian.com/download/

We only provide a small quantity of image combinations that are possible because building and providing them all would be just insane. Check here for building your own customized image: https://github.com/armbian/build

https://github.com/McMCCRU/rtl8188gu

A bunch of 3rd party drivers come already shipped with Armbian. However the device may lack the firmware blob. Try installing the code { font-family: Consolas,"courier new"; color: crimson; background-color: rgba(0, 0, 0, 0.2); padding: 2px; font-size: 105%; } armbian-firmware-full package via apt. Maybe this is all it needs to work.