devman

I remember reading the history of the Lima project a while ago, and it basically comes down to that ARM doesn't WANT an open-source implementation of the graphics drivers, as they make a not-insignificant amount of money licensing theirs.

If you check the download page under "Libre Computer", you'll see that Armbian has builds for 4 of their current models Le Potato is a supported board Tritium H3 & H5 are suitable for testing Renegade is a "community support" board. The link you provided by default points to the new La Frite board, who just recently finished it's kickstarter and nobody actually has yet. For the most part you'll find the boards are roughly comparable to their Orange Pi and FriendlyArm analogues of the same processor / memory.

Thanks for catching this so quickly, Igor. I was mid-update when it gave me a 404 on that file.

Looks like you're trying to run an x86 binary on an arm cpu.

Umm.. the Helios4 kits (full or just the board) come with all the necessary cables. SATA power, SATA data and AC adapter. The only thing you need to source yourself is the drives.

The major difference between those three images is: Stretch : modern 4.x (14? 17?) kernel, based on Debian Bionic: modern 4.x (14? 17?) kernel, based on Ubuntu Xenial: legacy 3.4 kernel, based on Ubuntu The modern kernels are generally pretty-close-to-mainline linux, thanks to the hard work of the guys in the linux-sunxi group. Since not everything has been reverse-engineered, it doesn't (yet) support all the device features. h3consumption will not work with the modern kernels, so is not included The legacy kernel is based off a vendor-provided kernel that has been cleaned up and had a few dozen (hundred) security patches on top of it. It's based of the now end-of-life 3.4.y kernel tree that was initially released in 2012 and was marked end-of-life in 2016 following the final 3.4.113 update All the hardware should work with these kernels, but the anything that relies on a modern kernel (eg. btrfs) won't work, and you'll be missing the last 2 years of security/stability updates.

Looks like a currently known / in progress issue. Forum search is your friend.

Have about a dozen boards for various things, only had two board failures (both nanopi neos, oddly enough).

You're right, it's back in the week-20 update.

100.73.80.157 is in the 100.64.0.0/10 address space for carrier-grade nat, so Technicavolous is right that this is most likely your cellular connection.

James: I'm not so worried. You'll notice that the M2 just got a refresh as the M2a, so I'm guessing there's something similar in the works for the M3. They're pin compatible chips, after all. For everyone else, Rafaello has 64 bit support running nicely by porting the Samsung Artik changes over to the 4.11.6 kernel, as well as uboot, etc. https://github.com/rafaello7/linux-nanopi-m3

On the github repository (https://github.com/friendlyarm/linux-3.4.y/issues/3) one user has gotten the artik 4.4.19 kernel to boot, although only with one core running. It's obviously not a final solution, but it's an encouraging development, as friendlyarm doesn't appear to be releasing a 64 bit kernel themselves anytime soon.

Sadly, I got bitten by this too. It was serving pretty decently as a little CUPS server mounted to the back of my printer. I can understand why they dropped it, but it was perfect for my personal use case.