Igor

Todays images and repository was rebuild after this: Add fixed Mali driver for sun8i. Needs testing

My 2cents. Wireless driver works now out of the box. Almost Firmware is at standard place, dhd driver was patched to prevent false recognition, but driver needs to be loaded twice to work I am done for the week, so if one have time to proceed from here. Probably we should need to power WiFi in u-boot ... I try with: CONFIG_MMC_SUNXI_SLOT_EXTRA=2 which I thought it could do the work, but no luck.

We moved to a new server a couple of days ago and we forgot to handle tld address. We had fixed those problems yesterday, hopefully I believe is cache related.

It's working fine for me, both cases. Configuration looks o.k. to me. Hmm Anyone else has this problem?

Yes, better this way. Alternatively you could switch repository to beta.armbian.com and do apt-get update / upgrade and switch back and do apt-get update ... it's not recommended that this repository is used in production environment.

It's a bit harder from here since you probably don't have any data sheet: by experimenting - trial and error, by using own and other experiences (reading stuff around), ... There is no straight answer on this question. Here the real hard work / fun usually begins

If you want a video acceleration, you better start with pre-build desktop even upgrade from CLI is possible. We haven't done enough tests to recommend this scenario yet. Currently we only provide a Jessie desktop, so pick that one. Note: we will change to Xenial desktop upon next build since it's base is a bit newer. In any case, you can build your own image, if our defaults does not meet yours.

We don't have report about any memory troubles of this kind. The simplest way would be to tryout new kernel (4.9+) when becomes avaliable. Currently is under development and is in working / non working state at the moment. Peek here and try OrangepiPC 4.9.0 if it boots / works for you. Note: serial console only. Try also with recompiling seti@home from sources and check their manual once again ...

Cubietruck or Banana PRO. Both has I2S while Cubietruck has also a SPDIF out. Setup from a driver developer.

Change cables and power supply.

No, it's not a known problem since stability issues are hard to detect and they are sometimes board revision related - different memory chips. Yes, it's usually related to u-boot, where low level inits are done. Because of such problems, we introduced a patch to u-boot and set RAM speed to more conservative levels. This should help and new build should have those settings. I am not sure if this is already added to 5.23 but for sure it's present in our daily build. Try upgrading from here: http://beta.armbian.com/ (beware that this is untested automated daily build) Use one of those: Legacy kernel: http://beta.armbian.com/pool/main/l/linux-u-boot-cubietruck-default/ Vanilla kernel: http://beta.armbian.com/pool/main/l/linux-u-boot-cubietruck-next/

A simple way of getting just enough(?) feedback. - armbianmonitor -u result is stored to our server by default (or by extra switch) - we build a parser, which renders collected data into human readable format. I suppose using php or python would be best to handle this job.

I made few tests with arm64 since I was thinking to move my web server to C2. I am using quite a complex install, lots' of packages and only one minor was problematic / non-existing. All others were present and I could brought the system up. The idea was abandoned for other reasons - old kernel and not enough performance. Firefox and Chromium are generally problematic on arm, 32 or 64. Yes, arm64 package base is not completely polished, but good enough to be used as a base in most cases. I believe that those minor cases will be sorted out soon. Remember, arm64 was introduced with Debian Jessie, so not so long time ago. Until then, you use this workaround and install things with :32 where it fails. So far I found only two cases.

You don't need to format a card. Just burn an image with a recommended tool.

They can / will glue stock Allwinner u-boot, Android kernel and some generic (l)Ubuntu root file system, but even that is not simple from this stage. I think they even provide one build, but you need to use Phoenix tools to burn into SD card. If it boots / works, it's usually barely usable ...

I got my board in Tuesday, most people got it today. We also got an H2+ and lot's of other tasks are already running. SDK looks pretty useless, like usually. Take a look: http://filez.zoobab.com/allwinner/h5/ At this stage, there is not enough good information to make a judgment.

It should be o.k. now.

Odroid XU4, latest desktop image from beta download. Booting normal but serial console login is not present. http://sprunge.us/FeWL

Sure, ASAP. Need to mount it from the case

It should work now. Thanks!

Yes, probably better this way. Defaults changed to "by date".

Both options are now present, default is "by name" ... the text and buttons regarding switching are very minimal, don't have better idea.

We actually added a test Vanilla build which was soon removed. Reason: people failed to read that it's a preview image, where many thing does not work and that we don't provide any end user support. Further people failed to read, that I don't provide support via email or other private channels. To lower related frustration, we simply removed those images from the download and now they are accessible elsewhere, where is little harder to find. Technically those boards have (limited at this stage) mainline support. I expect we'll put those images back soon, so I don't change this flag. Perhaps I should ?

Our major part, the build script, is issued under GPLv2 while the output, bootable image, we would need to make a research. Nevertheless Armbian is used in commercial project regardless of a licence type. In ideal world this would be moral first, legal second question: "If you make money with help of our work, give us some too." Few did this way. I am / was thinking on whether GPLv2 is the right way for this project, but am not too qualified in this area. Perhaps to move into dual or triple licencing, Mozilla? What are good and bad things and can we just change the licence?

We have multi channel HDMI audio driver on A20 boards but I am not aware of limitations.