Werner

You do not specifically have to use numpad to enter 1234. The other numbers will work too. Alternatively you can boot it up with debug serial connected with will do auto-login on first boot.

moved since it boots w/o peripherals connected.

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

Without taking a deeper look my best guess is no. armhf vs arm64 architecture, H2+ vs H6 SoC...

Maybe it became too common knowledge that the following baud rates are most common: Amlogic and Allwinner SoCs: 115200 Rockchip SoCs: 1500000 And yes, this could be documented somewhere if it isn't already on docs.armbian.com

This topic is about legacy kernel, not edge kernel.

https://docs.armbian.com/User-Guide_Getting-Started/

I dont have this hw. Need somebody with the board to confirm if either it works or not.

Try building from source. IIRC boot on old framework on edge kernel was broken but fixed on main.

Armbian does not mess with ssh settings besides allowing root login. It uses default values that userspace packages ship. Therefore also hostkey generation is straight forward as plain Debian/Ubuntu on x86.

Oh well... https://github.com/armbian/build/pull/5069

Probably XFCE will be first. No ETA. Or Gnome/Wayland...who knows...

Probably just a mistake. Feel free to send PR

Ah. I see Kindly stealing from @SteeMan Case closed.

never heard of. I suggest to ask where you got this from.

moved. feel free to adjust tags.

try https://archive.armbian.com If not there they are gone.

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.