This is basically a place to try and document what I have done, and find out what I need do in order to get this working. I've flagged it as pine64 and pinebook related as ayufan's builds support both at this point in time.

So, what am I trying to do? Basically, I have crappy internet, and come computers around which are more than capable of grunting their way through compiling and building images for the pine64 / pinebook. This would also let me look into customising the images, and doing some work on them myself... maybe. I've played with docker a little bit, and have used Travis CI in the past, so thought how hard could this be? Famous last words.

I decided one of my pine64 servers could be the jenkins boss, so loaded jenkins 2.46 (as it's the LTS version) on that that. Easy peasy, had everything up and running in under 20 minutes. Set up a build node or two on the ubuntu x64 boxes, so that they could be responsible for the actual builds, so the pine64 only had to manage them from afar. Since the Jenkins file in the repo wanted a node with both the docker and linux-build tags, I made sure one of them had that, was running LTS 16.04, and had docker on it, and had actually also manually build the build-environment docker on it also (but that was more to test if it was working than actually configure anything, and I did end up deleting it at one point just in cause it was the cause of the issue).

I then setup the new pipeline, configured it as a pipeline script from SCM -> Git -> https://github.com/ayufan-pine64/linux-build and left pretty much everything else as defaults. Tried running the pipeline, had to double back and install the AnsiColor plugin, and then the build ran. It downloaded the repo file, logged into the build node, and started building the docker container without any dramas. So it gets to the end of the docker build, and promptly and consistently dies. I'll include some logs below, but does anyone (especially ayufan or tkaiser) have any ideas what I'm doing wrong? Am I missing some blindingly obvious configuration step that I should have known about before attempting any of this?

I even setup jenkins on the same machine that was doing the build, and set it as the docker/build node, tried playing with docker plugins with no luck, and installed blue ocean just incase it was related to a plugin it added.

I *think* the issue is related to this entry in the log, but I'm not sure, and I don't know how to correct it, hence this post. asus-h55d is the host-name of the node which the build was slaved out to, and it's this line that stands out as different from the logs from ayufan's builds.

So I haven't seen it mentioned in this section that on the Wiki page there is a newer Remix OS release dated 2017/01/05.  What exactly is the difference/advantage to running that version over the latest version discussed here? I don't see any mention of it here, so I am unsure whether there is any difference/advantage?

It's getting a bid odd having multiple versions of the same OS, in different places. Some of the OS's on the Wiki page seem to be the "wrong" version. Example - people are being told to use the Android 6 img that's from ayufan on the forum/github, but there are three android v6 builds there - two of them being newer than ayufan's builds.

Cheers

Hi,

I'm trying to use the chip wolfosn wm8960, that is connected with I2C interface and I2S bus.
Polling it on the I2C bus, the peripheral is recognized with address 0x1a on i2c-1, but nothing related to this device like sound card found.

Another preliminary step follewed is the kernel compilation, making by activation the driver wm8960 found in sound/soc/devices/ like built-in and enabling all voices found in  "--- ASoC support for SUNXI" of menuconfig.

At this step, applying the new kernel, I don't found any peripheral with arecord -l or aplay -l or with pactl command and there isn't any row in the syslog/kernlog that show me that the wm8960 device is found.

There are few references for this codec, but I'm trying to follow the guide posted for another soc (i.MX6) in which the device driver already built-in inside the kernel source tree, showed at: https://community.nxp.com/docs/DOC-106295

Another link (for i-MX6) report also that:

I want to install Ubuntu Mate on the latest version of Armbian. I am using Armbian since the latest version has support for the 7" touchscreen. I have never installed a GUI desktop, so any help would be appreciated.

Special thanks to ayufan, Icenowy, lennyraposo, longsleep, lukasz, tkaiser, Xalius and PINE64 community contributors.

For release notes on all the Xenial Images (Pinebook) 0.5.2-59 below, please visit ayufan's GitHub.

Xenial Mate (Pinebook eMMC) 0.5.2-59
- THIS IS FOR eMMC!!!
- MD5 (XZ file): 83bc17a0b4349286ba9aadb992e6809b
- This build is based on ayufan's 0.5.2: jenkins-linux-build-pine-a64-59

Xenial Mate (Pinebook SDCard) 0.5.2-59
- THIS IS FOR SDCard BOOT!!!
- MD5 (XZ file): e6b5f3fa312aaa50dc92c6be7a40ec2c

Xenial Minimal Image (Pinebook SDCard) 0.5.2-59
- THIS IS FOR SDCard BOOT!!!
- MD5 (XZ file): f8ce8b2c6199e93ddba67e4477039042

i3 (Pinebook SDCard) 0.5.2-59
- THIS IS FOR SDCard BOOT!!!
- MD5 (XZ file): 324e63f5e94aa9d9aec8066985880477

Xenial Minimal Image (PINE A64(+)) 0.5.2-59

Paid for my 14 inch pine book over a month ago, and patiently waiting for any sign of shipping info...

Have emailed and gotten responses about late may to early june.

maddening to want new tech and have it just out of reach!

Ladies?? and Gentlemen!

After so loooooooooong silence, I have several good news for you guys who care about Windows 10 IoT Core on PINE64.

We have released the latest RS2 version image to Lim, and he will upload it soon.

In this release, we have fixed some serious bugs such as Ethernet. (oh oh oh~~~ we can use Ethernet eventually!!! )

And another bomb!  I uploaded core driver binaries and packaging toolchains on GitHub!

Here is the repo address: https://github.com/Leeway213/BSP-aw1689

And also some driver source code here with A64 datasheet in readme: https://github.com/Leeway213/driver-samples

Welcome makers developers and anyone-elsers to post your feedback.

Updated on 20170626:

Update all source code of UEFI boot on GitHub: https://github.com/Leeway213/WinIoTBoot

Hey all,

First, I apologize if this is not in the right section.  Please move it if there is a better section!

Second, I did a search and from what I could tell, there was only one other thread regarding using an audio extractor and they never mentioned if they tried it or if it worked.

I recently bought one of those cheap audio extractors off Ebay to try to get optical audio to my receiver.  It doesn't have an option to pull the audio directly out of the HDMI signal.  Unfortunately, I cannot seem to get the device to work with the Pine.  It doesn't appear to ever negotiate the HDMI signal or something so it displays no video and no sound.  As a test, I used my laptop and it is able to display video and extract audio (albeit at only 2 channels) just fine.  Has anyone been successful in getting one of these devices to work?

I'm trying to use Android TV to use the Pine as an HTPC replacement.  I have never been able to get the analog audio jack to work either, if that makes any difference.  I bought my Pine (1GB model) through the kickstarter campaign.

Thanks in advance!

Hello,

I have Remix OS on my Pine64+ set up to act as a proxy for my security camera dvr setup because the dvr is very insecure.  I'm using IP Cam by Robert Chou as a front end which at least closes the glaring holes in the dvr, but I'd like to add an additional layer of security in front of that by using nginx as a proxy with password protection before the IP Cam webserver can be accessed.   

Is it possible to install and configure nginx on Remix OS?

Thanks!

Mitch