Werner

Booting from mtd/nvme should just work. Most common problems: - dirty mtd/emmc. vendor/unmatching boot loader can cause issues. - mixup between m.2 sata and actual nvme. Correct overlay/dt must be used - wrong rootfs uuid in armbianEnv.txt after running armbian-install (after done, do not reboot but mount freshly written nvme to a random folder and check if the uuid is correct)

moved

moved to tvboxes

Since we do not add any Intel drivers this regression may come from upstream. You could test nightly build which have kernel 7.0. Also total random guess: Perhaps more recent kernels expect more recent firmware blobs, perhaps the ones on the board are outdated (or are expected to be on a different place)? No clue though through which package those are shipped though. Seems like the files have been touched last around 7 month ago: https://git.kernel.org/pub/scm/linux/kernel/git/iwlwifi/linux-firmware.git/tree/intel/iwlwifi

Perhaps related https://github.com/armbian/firmware/commit/36ec4377c197af9ced4a02aaa660ade54c83f93d

moved to tvboxes

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

Then it should not be an issue to find somebody from the community to come up with support. From official POV we do not add new boards without some sort of funding. Our resources are simply too limited.

No official plans. However anyone from the community can step up and add support for new boards

reverse engineered npu driver (called ROCKET) is upstreamed since 6.17 I believe. So kernel-wise it is there. Everyhing else necessary (like libraries) is out of scope for Armbian.

moved

First: https://forum.armbian.com/terms Second: Provide full logs

If an pre-made image is not there, just DIY. https://docs.armbian.com/Developer-Guide_Build-Preparation/

Nobody knows, nobody tried. Give it a shot. There is only one way to find out.

moved to tvboxes

closed for off-topic

We don't deal with OpenWRT. I suggest to ask at some place where OpenWRT is distributed/supported.

No, I let LLM poking at the problem.

Mirrors come and go. Check https://docs.armbian.com/Mirrors/#current-mirrors for an up to date list of active mirrors and its status.

I don't know. I don't maintain this board. Perhaps the maintainer knows which is alexl83. I don't know if he has a forums account though. Try via Github

duplicate

Nick explained above how to create such an image on your own.

We don't deal with other OS than Armbian. If you need Android, I suggest to ask at xda developers or similar place.

That's not an issue. These fixup scripts are only there to allow dt overlays being configurable via parameters rather than having hard-coded pins for example. About the actual issue, no clue. I suggest to try 7.0 kernel from "edge".

There were changes merged fairly recently. Perhaps try this: https://github.com/armbian/build/pull/9600