Gunjan Gupta

If you are not able to understand what ag123 posted, I am guessing you also have no Idea about what an NPU is. You just took some tech jargons, started a thread to look cool with no Idea about what you are asking for. And when people tried to ask for explanation or tried explaining to you that you are not making sense, then you simply started insulting everyone. If that is the case, I suggest we lock and delete this thread. Its not helping anyone.

Alright, lets move the world forward together. How about you book a session for consultation and pay for the same - https://calendly.com/armbian/consultation?month=2024-01. We can discuss about what needs to be done there. Then you fund the development and we will happily work on it maybe even fulltime depending upon how much you are willing to fund.

@MaksimarmYou are evading the first ever question asked in reply to your thread, which is what you meant by migrating io scheduler to NPU. As I believe will be the case with most of us, when someone says NPU we will think about Neural Processing Units which are for use with AI inferences and hence something that will be used by end users. It has nothing to do with IO scheduler as explained by ag123 above as well. Hence we did asked you what you mean't by it as it does seem like you are clearly not talking about the same thing or have different understanding of the same.

I guess copy paste error from Orange Pi's repository. I do remember changing it to ok, but I guess I forgot to include that in the commit.

I have never tried doing it but I will guess either https://docs.armbian.com/User-Guide_Fine-Tuning/#swap-for-experts or disabling armbian-zram-config.service should disable zram

As you mentioned you had a serial adapter plugged into zero2 but not to the pc, its possible that the uart adapter might have sent some garbage character just when it says press any key to stop booting and hence it got stopped there. I have seen that happens sometimes when my serial adapters usb plug touches some metal or when I touch the same.

Is there any output on serial console?

As this is not orange pi 4 that is being used, moved the thread to community forum and removed orange pi 4 label

from armbianmonitor logs BOARD=mkspi BUILD_REPOSITORY_COMMIT=ed589b248-dirty This is not a board that we support. Either you have patched the build framework yourself to build for this board, or you are using some third party provided image. This is important because that means we never had any patches to support this board and that is why you are having issues after upgrade. Whoever build the image needed to specify SKIP_ARMBIAN_REPO=yes to make sure that kernel won't get upgraded from Armbian repo. As we never supported this board and never had any patches for this, its pretty much common sense that upgrading kernel from our repo will break functionality Ask where you got the image from. We can't provide support for the board that we never supported.

@NicoDCould you please guide the user on how to install armbian on vim3

if you have compiled the images yourself, its possible that you will be having the headers package in the output/debs/ directory. You should be able to install them using the deb file from there.