Igor

If network works - SSH to machine and https://docs.armbian.com/User-Guide_Armbian-Config/System/#alternative-kernels If that doesn't work https://docs.armbian.com/User-Guide_Troubleshooting/

Ports might not be default. Did you use port reported in armbian-config ?

🧟‍♂️🌙☕🛌 Since introducing of systemd (by default in most Linux assemblies in past 10-15 years), its the systemd way: https://www.freedesktop.org/software/systemd/man/latest/hostnamectl.html This way is also handled if armbian-config is used. Also for other things, consider looking into systemd* how-to. Netplan - i understand you might dislike it - is just a wrapper - for systemd-networkd or Network Manager.

Aliexpress randomly assembled electronics is expected to fail - you need to lower expectations, count on luck, read forum for clues, DIY. Little better are single board computers, then what is declared as supported, best what is platinum supported (for this use case FriendlyElec R3S would be perfect) following by Raspbbery Pi and x86 hardware. If you are looking for top first time experience buying a server, you should stick to https://www.supermicro.com/en/ I can assure you that Armbian works perfectly on any of servers they sell. But yes, price does not match.

@Mike H This is a community forum, and your message is for everyone. Armbian maintainers are part of this community, but please keep in mind that support here is provided on a best‑effort basis by volunteers and maintainers who give their time when they can. In open‑source projects, especially those maintained by communities, work is prioritized based on available time, skills, and resources. Sometimes an issue might be addressed quickly; other times it may take months — or it may not be addressed at all if the effort required is too great compared to the benefit. This is a normal reality in community‑driven software development. The concept of sunk cost often plays a role in deciding whether to invest effort in fixing certain issues. It’s worth noting that even in large, well‑funded projects, some bugs remain unresolved for years. In our case, resources are far more limited — for example, Raspberry Pi OS has a budget exceeding €1M annually for one platform, while Armbian supports many platforms with a fraction of that funding, outside few boards we have some small maintaining budget, there is only a beer money, and far fewer people. Best-effort is the only promise that can be provided under such circumstances. We appreciate bug reports, even they have nothing to do with our work as we understand users often can't judge that, but we ask that no pressure be placed on contributors to resolve them on demand. In some cases, solving an issue can take weeks or even months of work, which is not something users can reasonably expect from volunteers. And there are thousands of bugs already in the to do list. Finally, please understand that part of the challenge we face is that some projects already monetize or re‑brand our work while presenting it as inexpensive and easy to maintain — when in reality, it’s not. This can create misunderstandings about the real cost and effort behind keeping a complex software stack running. Your report is welcome, but we ask for patience, understanding, and respect for the time and resources of those trying to help. Pressuring volunteers to prioritize some issue, or expecting them to personally fund the work, is neither reasonable nor effective way to fix bugs.

armbian-config way is limited in its use - it's intended for quick start when networking is simple. When you need something more complex, its always the manual way: https://docs.armbian.com/User-Guide_Networking/ If you wanna look how Armbian deals with networking in the backstage: https://github.com/armbian/build/tree/main/extensions/network In case of desktop images (original, not self constructed), XFCE will have Network manager.

When auto login is enabled, this is how it starts - its in "show all screens" mode. I don't know how to fix this - its some Gnome settings / it doesn't bother me as click of a mouse to the empty space solves it. I saw you are trying Debian variant. Here it might be better to stick to Ubuntu based - its more polished. Weird beep you are experiencing - I haven't tested this HW for awhile, but so far I didn't notice it. Dunno where that is coming from.

@amazingfate can tell that. https://github.com/armbian/build/blob/main/config/boards/oneplus-kebab.conf#L3

That should be O.K. too.

tl;dr; This "only" difference is huge - modern kernel hw specific code is pretty much written from scratch, feature by feature. Not to mention differences in general areas between kernel 6.1 and 6.12, low level boot loader is also usually different. Further reading: https://docs.armbian.com/User-Guide_FAQ/#why-things-stop-working

Vendor kernel 6.1.y with mesa-vpu extension https://github.com/armbian/os/blob/main/userpatches/targets-extensions.map#L58 (with patched Chromium) is the only way to come close to what you want. Only this:

Here also ok: root@uefi-x86:/etc/apt/sources.list.d# LC_ALL=C apt update Get:1 https://download.docker.com/linux/debian bookworm InRelease [47.0 kB] Hit:2 http://deb.debian.org/debian bookworm InRelease Hit:3 http://security.debian.org bookworm-security InRelease Hit:4 http://deb.debian.org/debian bookworm-updates InRelease Hit:5 https://github.armbian.com/configng stable InRelease Hit:6 http://deb.debian.org/debian bookworm-backports InRelease Hit:7 https://repos.azul.com/zulu/deb stable InRelease Hit:9 https://openhab.jfrog.io/artifactory/openhab-linuxpkg stable InRelease Hit:8 https://netcup-01.armbian.com/apt bookworm InRelease Fetched 47.0 kB in 1s (67.4 kB/s) Reading package lists... Done Building dependency tree... Done Reading state information... Done 33 packages can be upgraded. Run 'apt list --upgradable' to see them. Perhaps some mirror is not in good shape, but that is automatically removed - in a cronjob.

That is over-optimism for most if not all of those chips - unless additionally cooled. I haven't played with exact this board much, so I am unaware of cooling specific for this board, but this is powerful SoC on a small board + every SoC needs some cooling in order to keep temp low. Do you have a (proper) heat sink? https://blog.armbian.com/stay-cool/ This looks quite normal: ### Boot system health: Time CPU load %cpu %sys %usr %nice %io %irq Tcpu C.St. 01:42:36 1800 MHz 0.30 52% 32% 17% 0% 1% 0% 61.1 °C 0/6 01:42:36 1800 MHz 0.30 35% 8% 26% 0% 0% 0% 59.4 °C 0/6 01:42:37 1800 MHz 0.30 32% 5% 25% 1% 0% 0% 59.4 °C 0/6 01:42:37 1800 MHz 0.30 32% 4% 25% 1% 0% 0% 59.4 °C 0/6 01:42:38 1800 MHz 0.30 30% 4% 25% 0% 0% 0% 59.4 °C 0/6 Also worth mentioning that here we only have Rockchip provided kernel. No modern kernel yet - which usually brings less aggressive performance / voltage settings.

I am running 6.12.37-current-x86 (with those changes) on my desktop and laptop, bare metal. Everything seems to work, multiple monitors, HDMI audio, acceleration, suspend / resume, BT, BT suspend, ... I would suggest you to use current kernel. I use this https://docs.armbian.com/User-Guide_Armbian-Software/Management/#cockpit for running VMs. That's for arm64 cloud image only.

Those were the days I remember compiling Linux 0.9 something .... it took a day and often nothing worked LOL. In embedded Linux, compiling kernel is nothing unusual, which is the reason why our build framework is focused into making this job easier. For tacking this parameter, you don't need to recompile everything. DTB can be recompiled on a device following by reboot https://www.google.com/search?q=recompile+device+tree+blob Device tree is just a hardware configuration that is provided to the kernel when it boots. This was the only possible related quick, cheap and easy way that I could come up with. Changing the value should have some effect - like (sometimes/always) not detecting PCI when going with weird numbers. More serious debug require a lot more time carefully checking code changes on areas that might have impact alongside with https://www.google.com/search?q=how+to+debug+pci+bus+on+signal+level Which is of course not cheap nor simple.

Welcome / Witaj! Plenty of options for quick and easy start: https://docs.armbian.com/User-Guide_Armbian-Software/ Those small things can do big things

I hope you have realistic expectations - I can only share tips and ideas - fixing is common problem in best effort way. This is most likely related to PCI driver. Which was done badly, its fragile since the day one. Try alternative kernels - and if you find a stable one, report back to forums. This might help nail down this problem.

https://docs.armbian.com/Process_CI/

Try to experiment with this value: https://github.com/armbian/build/blob/main/patch/kernel/archive/rockchip64-6.6/board-rockpro64-0001-Add-pcie-bus-scan-delay.patch As this is pulled to DT, you only need to recompile DT - on board.

We might lost WSL2 compatibility, which is experimental ... I tried same command on my Ubuntu Noble bare metal ... and it works as expected. I suggest you to use some VM to complete what you want to achieve and open a bug at https://github.com/armbian/build so this gets eventually fixed.

I assume you didn't change your power supply or add more things to USB? This could trigger crash. It would help if you could catch the crash. Enable more verbosity (loglevel) might give some clues, otherwise this can represent more serious debug / not easy to catch and resolve.

In the past we had dedicated image for rpi5 ... It could be added here: https://github.com/armbian/build/blob/main/packages/bsp/common/usr/lib/armbian/armbian-firstrun#L112-L122

If boot from USB works, you don't need to install anything, just do 1st login config as described here: https://docs.armbian.com/User-Guide_Getting-Started/#first-login If boot from USB is not supported by this hardware (I don't recall if it works on N2+ or not), you need to start with SD card, conduct previous steps following by https://docs.armbian.com/User-Guide_Getting-Started/#installation

If you plan to start from scratch and you don't want to wait hours until repository is updated, yes, rather download and use latest image. Upcoming fix will solve this problem for everyone that still use old image.

Packages are in the update process - few hours from now it will be ok. It fails only on first images, which were avail for few days.