Igor

How about now?

I had troubles with images above - sometimes network was not recognized ... so I tried to put together mvebu-next with 4.14.12 ... I only used DT from legacy, no other patches. The network works, CPU scaling works, SATA works, ... Fans. One is spinning fast and one slow. I didn't even try to resolve this PWM thingy. Download page: https://www.armbian.com/helios4/ Boot logs: http://ix.io/DIO Yes, I quickly find out that you need at least two drives so I added one at the bottom and case become stable. Eventually, I ended up in "engineering mode"

Dont know anything about this wireless chip found on recent boards. All mine have old Broadcomm chips which works. Perhaps only firmware is missing? Wrote on mobile

Nice! Known (upstream) bug, AFAIK unresolved.

Mount SD card on some Linux and add: fdt_file=imx6dl-hummingboard-som-v15.dtb or if you have HB2 fdt_file=imx6dl-hummingboard2-som-v15.dtb to the /boot/armbianEnv.txt If you have eMMC version then imx6dl-hummingboard-emmc-som-v15.dtb and imx6dl-hummingboard2-emmc-som-v15.dtb

Yes, you can. https://github.com/armbian/build

@zador.blood.stained Merging 4.4.y kernels from Marvell seems a bit problematic and wasteful. Shall we implement this workaround to the mvebu.conf: https://github.com/armbian/build/blob/master/config/sources/mvebu.conf#L16 if [[ $BOARD == helios4 ]]; then KERNELSOURCE='https://github.com/helios-4/linux-marvell' KERNELBRANCH='branch:linux-marvell-4.4' KERNELDIR='linux-helios-4' LINUXFAMILY=helios4 fi Mainline target remains mvebu-next. Any better idea?

First try beta builds, to see if this is already fixed. armbian-config -> system -> switch to beta.

People reported eMMC corruption with some variants of eMMC when using 2017.11 and mainline kernel. There are some dirty hacks in old u-boot regarding eMMCs. Perhaps it's related.

Better. We are not very much familiar with Odrobian details so it's hard to say. In case of troubles ... you will need help from both sides or some dedicated person with a lot of time. I would say rather go with a clean build. Remarks. Mainline kernel works somehow but is not yet recommended for any production environment, while the standard kernel is updated at least to the hard kernel level. In any case, I would suggest waiting for next small bugfix update. There are some small things which need attention.

http://linux-sunxi.org/UART

It should be fixed upstream - working for me, but it would be good if somebody else also checks. Related: https://github.com/armbian/build/issues/770

OK, It looks like it adds "guest" in front anyway It's done.

It can be done by admins only. After deleting, do you want your posts to remain associated with "HeinrichG" or by "Guest"?

Tritium added. I also add HDMI bits, tested only for building ... @Icenowy I didn't find your FEX so it's mainline only. It has to be added here: https://github.com/armbian/build/tree/master/config/fex and add "default," in front of next https://github.com/armbian/build/blob/master/config/boards/tritium.csc#L12

We can help only with stable builds. Here, ... there are too many possible problems. In this case, you need to attach a serial console to see where it stops. But I would rather suggest you start and stay on stable builds until those mainline are not fully stable. If you want to use the mainline/modern kernel anyway, you have to be ready that sometimes you will need to rescue your system manually. It's simply not yet polished for end users. Add. There was a change in upstream network driver on all H3/H5/A64 boards a few weeks ago and it broke everything. I managed to fix H3/H5 while A64 remain broken.

Do it.

Neo Plus2 has enabled eMMC in u-boot config ... so rather that one.

Mainline support for H3 is not (labeled) stable yet. There was a regression in HDMI driver and your board should boot but without a display. If you build your own image, the display should also work.

To some degree, it should. None of us has this board yet so we can't be 100% sure, but if it doesn't ... it can be quickly adjusted. I would suggest trying Nanopi Air image instead.

This is not Armbian. We don't support 3rd party builds. Download image here: https://www.armbian.com/orange-pi-plus-2e/ and after you boot it, you can flash it to eMMC as well.

We place notes if there are any repository updates to the: - www.armbian.com (the last update was 3.December) - twitter

Then better stay away from images made only for developers/testing and use stable builds. Automated nightly builds are made from the latest development sources and are not tested. Sometimes do work, sometimes don't.

I actually wrote the exact procedure Edit /etc/modules. Remove g_serial and add g_ether instead .... save and reboot. But remember, it's still only a theory. I haven't tested this.

Armbian uses g_serial by default with a modern kernel. With old, I lost track. I assume you only need to exchange it with g_ether? /etc/modules