Igor

Aha, that I haven't try. So we would need to change priorities in the boot script or proceeding into some other method?

I have successfully installed to SPI / NVME from official Armbian builds. Without any hacks, regular armbian-install.

Keeping kernel bootsplash is getting out of control ... it was disabled while we anyway moved to plymouth. Check here: https://github.com/armbian/build/pulls?q=is%3Apr+plymouth+

Armbian automated testings shows no problems with WiFi https://paste.armbian.com/yaqokonipe But this image is little further then released, made from latest sources (nightly). You can switch to the same firmware via armbian-config.

Use different SD card. Standard Amlogic issue. It can't init SD card properly. Try test images if they are better ... fix coming soon. Hopefully.

And we don't have needed capacity as you and vendor are exploiting community software development. What we do is very hard work which needs to be compensated. Support is hard work which needs to be compensated. Those who tells you otherwise are either stealing value from someone (open source piracy is also adding to the bill) / lying or is just a Dunning–Kruger enhanced newbie. Its not all dark. Instead of waiting, perhaps you can check how you can help? Serving project as a coordinator? Evangelist? Graphics designer? Ordinary soldier? Project needs many positions and hard cash just to cover basic needs. Since we are non-profit, we can't enhance our capacity ... Why do you expect we have to give you software for free and keep investing our private money so you will get more free stuff? Welcome and thank you!

Armbian is more advanced then Rpi OS. It resizes SD card automatic on 1st boot.

This is community forum, welcome! If you want to contact team, check here. But without becoming a partner nobody will be doing any research for you. In custom hardware, team doesn't know to answer without a research.

Of course. 1. Research which driver is needed, enable it or bring a tested code as external kernel driver. Make a PR to the code and make sure to stick around since it will need maintaining. 2. Hire someone to do that for you and support him to do the maintaining work for you. Its not much of work, but right enough that you need someone. 3. Support Armbian developers to do that for you.

The same way as on Debian or Ubuntu. https://www.digitalocean.com/community/tutorials?q=web+server&hits_per_page=12 https://pimylifeup.com/raspberry-pi-web-server/

Here is a problem which runs beyond my knowledge and Armbian. Vendor does not exists anymore and I assume nobody adjust web pages. Bullseye is today latest stable, year(s) back it was buster ...

This is not Armbian issue anymore - it seems Debian repository or from where you are getting ZFS is borked to some degree. I installed ZFS on Debian several time and didn't run into this. This way: I assume you started with a clean image as if this

You are saying Armbian is a problem ? https://docs.armbian.com/#what-is-armbian All those things are clear? https://docs.armbian.com/User-Guide_FAQ/

FYI. I had to give up and disable those wireless drivers due to extreme lack of time in order to move all our kernels to 6.1.y https://github.com/armbian/build/pull/4570 You are welcome to pick up from here and fix the code in case you want to have running WiFi with this kernel.

I didn't fix kernel but ZFS packages.

Try to use Armbian for reference https://www.armbian.com/uefi-x86/

Aha, I see ... didn't understand it right. Well, I have fixed one problem regarding ZFS ... We have stop making images for this hardware as we don't have not a fraction of resources for maintaining ... but kernel updates are running out and automated community (but only with test user space) builds exists (no idea about status). Its out of our control when it comes to this hardware. It might work, it might not work. I read few days ago that image made from sources works (again), but this is a rummer, not an official information. Going that route should be good I guess (sorry for directing you to the download that is outdated / non existing).

Sorry if I was not very clear. No, just download image and install ZFS the same way as you did. It should work.

That you don't try to fix this image but start with a fresh. I mean you can - if you know how.

Try to replace monitor identifier with yours. You can get names with: xrandr --query

We need something else ... In area of testings, we need (yours? and few more) part and full time engagement as a test engineer https://forum.armbian.com/staffapplications/ ... if you can pay for your time, we can't. So far all people that applied, sooner or later lost their interest in working for you. Testings is anyway automated and when a bug is found, there is nothing we can do as you don't want to compensate for the time we lost by working to fix problems you and our competitors have with those computers. Even recording a bug goes on our private bill. This is how you support us and you think a bug report for software support, which you are paying nothing for, will represent an added value?

It should work with 5.10.y, on 5.19.y (probably on 6.x too) is broken.

You can try creating a file /etc/X11/xorg.conf.d/01-armbian-defaults.conf with this content: Section "Monitor" Identifier "Monitor0" Option "DPMS" "false" EndSection Section "ServerFlags" Option "BlankTime" "0" Option "StandbyTime" "0" Option "SuspendTime" "0" Option "OffTime" "0" EndSection following by restart.

You did it right. Problem was on our side and it was corrected. Please give 48h before trying again from a fresh image to make sure our packages network is synchronised.