Igor

Nope. Armbian is not Canonical. You should do some forum search - there are many happy ZFS users around here. Me included. sudo apt install zfsutils-linux zfs-dkms ... but unfortunately there is a bug in headers which needs some time. That is on you to fix or wait ... but it can take months since bug is with us also months. Workaround is using stable kernels (current). You can switch to them within armbian-config, install headers there and install dkms package again.

armbian-config -> software -> install_headers

To be able to find a problem, we need to know the exact steps you made. Everything, not just "debian xfce10". There is output/debug folder with logs. Check them for clues.

Will be provided for the future https://github.com/armbian/build/pull/3087 Repository rebuild time is prolonged at each update and one block (stretch buster focal) takes approximately the same time to re-publish. Now - perhaps its not coded well, but we have no time to diagnose the tool and/or our implementation - or switch to another tool. Too complicated. Better hardware also won't help here, since its already running on a Threadripper 3990 and it its run is barely noticed. If you want to help: https://forum.armbian.com/forum/54-help-wanted/ If you have some solid hardware / vm with 32Gb and many recent cores we could use it for build runner to get down with images rebuilt time.

Problem recognised = we believe it is real. Not something that is affected by one users wrong powering or similar hw problem. When a problem gets a chance that it will be recorded into our internal to do list. Help on areas you are good at. There are plenty ideas what kind of help we need, https://armbian.atlassian.net/jira/projects is full of recognised but unsolved problems. To my understanding its something related with u-boot, but knowing more could easily cost week(s) of dedication and investigation. I have already asked a skilled person in this area to investigate deeper. But he is also doing something else and can only look when his personal time permits. Not right now. With a few thousands which we receive from you, we can't have specialist standing by waiting for problem to happen. We only cover electricity. According to your questions - I think you can't help here. Putting a pressure - asking questions without adding value - is pointless. This is forum, not a support you have paid for.

Default Armbian setup stops at basic functionality - it provides you possibility to login from network, serial and usb (optional). The rest is in users domain. Providing anything more advanced represent serious expense and since the most important things are only covered with 0.5% ... There are many other small and big ideas waiting to get developers investments (which is most likely not going to happen): https://forum.armbian.com/forum/38-feature-requests/ Also good to check to understand the background: https://docs.armbian.com/User-Guide_FAQ/ However, we might develop better networking setup, we have knowledge, but it takes a lot of precious private time - at least a year to get general config in beta stage. If that is needed at all?

If things doesn't work out of the box, you have to prepare serious resources to get going. Then start here https://linux-sunxi.org/AR100/HardwareSharing This forum provide best effort support for Armbian. For other distributions, seek their support channels. If any. If none, too bad. Since you are new, welcome to read FAQ 1st. This give you some perception what you are asking for and its a way to save precious time and keep forum cleaner.

We know that all Allwinner 32bit boards are affected when using latest u-boot. I have pushed old u-boot - try this:

Since you are obviously new, welcome to check FAQ: https://docs.armbian.com/User-Guide_FAQ/ and a support contract you have: https://github.com/armbian/build#support It doesn't give you any power to change project R&D focus which is needed to be changed to diagnose such issues. Remember - you have as much developers you support. Problem was recognised and it seems fixed from engineering perspective. We will (double) check when time permits. Perhaps soon, perhaps next year. Its irrelevant since we are totally overloaded and you don't seems to notice. In the mean time check if you can help - where you can. U-boot version on those builds?

Last change in legacy kernel is several years old - if there are no changes to kernel sources for years, there is no point in building and updating packages with newer versions.

You are only covering 0.5% of our running costs and there are 1000 people with some wishes before you. However, helping working on our agenda for your benefits changes things dramatically. This is open source, you can add this on your own (we will review, but you have to test) or hire someone if you are not close enough. Why do you think adding this feature should be Armbian maintainers expense? Even you do things right, you are too later for next release. We accept bug fixes only, new features will have to wait. Also make sure to read FAQ - it might give you some ideas why we can't do anything about this and many other things that users would want that are fixed, improved, developed, ...

Today's beta was tested manually (on C4) https://imola.armbian.com/dl/odroidhc4/nightly/

Perhaps we were not clear enough. We only ship that kernel, while I don't know many if any person that will be doing anything with it. Dealing with that dirty code is too big waste of our precious time. We are already loosing 50-70 hours every day to provide you this. Remember you only notice what doesn't work ... The easiest way - armbian-config -> system -> enable hardware (overlays that are prepared and tested) doesn't exists. I don't have any knowledge if pwm works or not - on this particular board / chip. Anything from here is research, where is a long long line ... I am pretty sure you don't need to poke around u-boot to get this working.

@lanefu I have added - lets see if it doesn't break anything https://github.com/armbian/build/pull/3087

This is now the second post that I had to merge with this topic

Found a problem: https://armbian.atlassian.net/browse/AR-885 Images build from sources should already be fixed - repository fixing and images rebuild will take a day or two.

I also tried - it seems we do have an issue. Investigating ...

Oh, yes. But they are not that different and it should boot. @rpardini was trying to bring things together and this is the last addition: https://github.com/armbian/build/commit/13329ebcd0f3f0270c7813e33599fa75d939bb24#diff-b79606fb3afea5bd1609ed40b622142f1c98125abcfe89a76a661b0e8e343910 I don't have HC4, only C4. There is an image for HC4 as well, but it would be good that someone else test this too. So we can be sure it boots: https://imola.armbian.com/dl/odroidhc4/nightly/

If you can boot the board, you can easily update boot loader and those troubles should be gone. Recovery methods are needed when you can't. 1. sudo armbian-config 2. system -> install -> Install / update the bootloader on SD/eMMC 3. reboot We used to have automated boot loader update, but that brought more problems so we went (years ago) back to manual updating.

Nightly images at the bottom of the board download pages. For the rest, make sure to get familiar with first: https://www.armbian.com/bugs/ (how to best talk about issues) https://docs.armbian.com/User-Guide_FAQ/ (good to know) https://armbian.atlassian.net/jira/ (development progress)

Those are development boards But I think we are close to getting stable support based on clean open source. We want to get rid of vendors proprietary solutions as soon as possible. Troubles as you have are the price that needs to be paid. Boot from SPI is also under development - not sure if it will be done before this major release. We are just about (this month) to push out major update, where many things for this board was fixed. Try this image: https://imola.armbian.com/dl/odroidc4/nightly/Armbian_21.08.0-trunk.114_Odroidc4_hirsute_edge_5.13.8.img.xz It works perfectly on my C4: ___ _ _ _ ____ _ _ / _ \ __| |_ __ ___ (_) __| | / ___| || | | | | |/ _` | '__/ _ \| |/ _` | | | | || |_ | |_| | (_| | | | (_) | | (_| | | |___|__ _| \___/ \__,_|_| \___/|_|\__,_| \____| |_| Welcome to Armbian 21.08.0-trunk.113 Hirsute with Linux 5.13.8-meson64 No end-user support: untested automated build System load: 7% Up time: 1 min Memory usage: 4% of 3.73G IP: 10.0.30.121 CPU temp: 38°C Usage of /: 6% of 29G [ 0 security updates available, 7 updates total: apt upgrade ] Last check: 2021-08-07 20:17 [ General system configuration (beta): armbian-config ] Logs: http://ix.io/3vhZ

Modern kernel luxury comes with a price: https://docs.armbian.com/User-Guide_FAQ/#why-does-hardware-feature-xy-work-in-old-kernel-but-not-in-more-recent-one If you want Armbian with the same functionality, but also no updates to the kernel, pick Armbian with a kernel 4.4.y which is still provided for this hardware.

All A20 boards have the same problem - check those posts for workaround.

Updating u-boot: https://docs.armbian.com/User-Guide_Recovery/

IIRC there were some issues on Debian user land and 3d acceleration and I assume they still exists (Buster is too old for fancy stuff). Its known that it works on Focal / Hirsute. Since we just started on adding 3D support, this is certainly not present on images that are currently available. Its coming with a next release 21.08 / this month. We only have packages for Ubuntu based builds - they came from here. We have no plans to support 3d on Debian desktops since this represent extra work and maintenance burden. As i notice https://github.com/armbian/build/blob/master/config/targets.conf#L522-L530 we didn't enable on 32bit probably because we need someone to test if it works. Build from sources is needed at this point. And remember to enable 3D since its not enabled by default.