Werner

Try again

topic split. rk3399 has nothing to do with rk3588 which the OPi5+ is built around.

moved

tag switched. There is none for the pro model yet.

You can use the build framework to create your own set of packages with custom kernel config for this board including matching headers. https://github.com/armbian/build

I see. Well this should be replaced with "mainline is at experimental...." I guess That is an issue with the naming of the overlays. Glad you figured out already. I think this also will be adressed with the next generation of armbian-config.

It helps to tell you to try vendor kernel instead of mainline ("edge"). The support for the rk3588 in latter is still under heavy development and lots of stuff is still WIP and therefore missing. https://docs.armbian.com/User-Guide_FAQ/#why-does-hardware-feature-xy-work-in-old-kernel-but-not-in-more-recent-one

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

I think there is an issue with the naming of the overlays. If you check /boot/dtb/overlay or whatever that folder was, you should see lots of overlays. Enabling can be done manually by editing /boot/armbianEnv.txt If you need an example simply enable the gpu overlay and check the file again to see how that works.

needs to be enabled via overlay

https://debug.armbian.de

Armbian does not have an immutable rootfs. So reset means rewrite microsd card with a fresh OS. Alternativly you can always mount the microsd on another Linux computer and adjust root password. Check Google, there are thousands of tutorials out there.

and you assume everyone on forums know which model you have and which image you tested, right?

https://www.google.com/search?q=How+to+Rename+a+Network+Interface+in+Linux

https://docs.armbian.com/User-Guide_FAQ/#why-does-hardware-feature-xy-work-in-old-kernel-but-not-in-more-recent-one

full logs. excerpts are useless

moved neither a tutorial nor a review

The image you got is probably fake/non genuine. For such we cannot provide support. Try at the place where you got the image from. https://docs.armbian.com/User-Guide_Getting-Started/#how-to-check-download-authenticity

Where did you get an image with that old kernel?

moved

You are not using Armbian. You are using a fork of Armbian that uses the name Armbian without our permission tricking users into believing they'd receive support for it at official place (this forum to say). Also they do not participate or contribute to the core development process. You should state your issue where you got the OS from you are using.

I suggest to state your issue at their place. We cannot provide support for 3rd party OS/scripts.

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

https://github.com/armbian/build/issues/7186#issuecomment-2339093930

So if you are already using Armbian, here is the build framework: https://github.com/armbian/build/ If you need further assistance check here for a business consultation: https://www.armbian.com/contact/