FalconGate (PINE A64(+)) 20170430

I'm by no means a master at Linux so this application is fantastic for me.  

I'm trying to figure out how to use the 128gig thumbdrive as a system storage drive to load and save files to. I'd like to make it the download path for Firefox. Just not sure how to mount and direct the OS to it. Any info would be greatly appreciated. This will defiantly help me to learn Linux a little easier. Thanks again!

I've tested a few versions of OS'es on the Pinebook so far, and it's been a fun little machine. But two days ago, I was going to install the lates Mate edition, and it stopped writing to eMMC at 30%. I tried again several times, but to no avail. Now it won't boot from SDCard OS'es, and no Linux installers go past 30%. The Android installer just has a blank screen and seems like it just dies. If I try booting it without an SDCard, the screen stays blank with backlight. If I try with any SDCard, regardless of image, the Pinebook logo shows with a contributor greeting on the bottom, but nothing else.

I ordered a 32 gig eMMC a while ago (some 3 weeks), so I'll try changing that once it arrives.

Halp?! Anyone got suggestions to what I should try to wake the Pinebook from it's slumber?

I could use some help.  My Pine stopped seeing the internet.  I need some help figuring out whether it is hardware or software.

I could access the internet good for a long time.  Now it just can't see it. 

I am running Android 7.0.

On my Ethernet connection I see no green or yellow LEDs lit.

Any ideas how I can get it working again?

I got my Pine64 maxed out and was looking to set up digital Signage with it.  Has any one else done this?  I've settled on Android 5 with Rise Vision. Android 5 because it was the only version I could get an app to launch on boot.  I have never programmed with Android but have a decent programming background with many languages.  However, this doesn't use 4K but from my understanding without Graphics Acceleration I can't use it on the Linux images. I looked at Kodi, Plex, and others but current solution seems the best so far. 


Things I was looking for
static IP
local storage for speed and in case of network issues
4K
remote configuration
play on boot
able to schedule so I can turn off during the weekends.

Rise is not local, android doesn't support 4K, and I'm not sure if I can control Android device remotely. So I have something working just not perfect.  

Does anyone else have experience with Pine and Digital Signage or know how I can improve on my set up? 
Appreciate any and all feedback.

Recently, I'm having boot issues with my pine64 1GB model.

I normally run the board as a headless server and the uptime was almost 3 months. I run transmission-daemon, plexmediaserver, and ssh-server on the board. For OS, I was using Debian Jesse (I think kernel version 3.10, but not 100% sure).

Additional information:

• SSH runs on a non-standard (not 22) port (no VPN)
  
• Normally I have external HDDs plugged into the board via an externally powered USB hub
  
• Board does not boot with or without Ethernet
  
• Board does not boot with HDMI plugged in
  
• Board does not boot with or without external USB hub plugged in
  
• I've been using the OnePlus One charger as a power supply for over a year without an problem (I believe it's 5V 2A)
  
• I have tried other phone chargers as well to no avail
  
• When power is supplied, board light turns red but I cannot ssh into the board nor does it power an external display via HDMI
  
• My SD card is G.Skill 32GB Class 10 MicroSDHC
  

Hi!

I received the SOPINE A64 with motherboard. 
The problem is that the initializing SDRAM Fail
The log from serial console:

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: