This is the last thing my pine write before shut down and turn off.
Can someone help me what is the problem? ):

Just thought I'd post the current version of the shell script I am using on my Pine64 to make the user controllable System LED (the one that you can attach near the headphones jack, or via the EXP header). I added it to /etc/rc.local (make sure you put an " & " at the end, so it doesn't block rc.local continuing / exiting), so now every time the pine64 starts up, I get a little heartbeat indicator going so I know it's running ok. Since it's a gist, you can also download it via wget or curl... just copy the URL you get from the 'raw' button up the top right. 

Next step will be working out how to intercept the power button... perhaps via udev, since that already responds to the power button interrupt, but doesn't know what to do with it out of the box. 

https://gist.github.com/pfeerick/00b04df...b4e1f7c168

A known issue from Raspberry Pi land that also effects the Pine64 is the need to use sudo in order to manipulate GPIO bits... which gets annoying pretty quickly... and tempts you to stay logged in as the root user, which is a bad idea.

There are some workarounds... i.e. using python GPIO, wiringPi (when available). But there is also a relatively simple fix you can apply in order to fix it up, which is to basically add two startup scripts that automatically fix the permissions. I've just run through this myself, and had to backtrack and check what I'd done, so please let me know if there are any mistakes or corrections needed. So... here we go!

Create a gpio group first:

i like it

I have a nexdoc. The pine64 will drive the display but not well, it is not crisp like it should be.
The display resolution of the nexdoc is 1366*768, but I can't select this under ubuntu on the pine (in fact I an only select one resolution (I can't remember what). Is there some way around this?
..mcf

I have a 'bad' PINE64+ board, running armbian with legacy kernel, powered via micro-USB AC adapter. NIC and UART0 serial are the only active peripherals. 100Mbps is perfectly fine, but there's a major packet loss at 1Gbps, no need for iperf to tell there's an issue.
 
VDD33 voltage is between 3.26V and 3.27V, regardless of
- 1Gbps or 100Mbps or 10Mbps link speed
- CPU idle (/sys/class/thermal/thermal_zone0/temp @ 42 degrees) or busy (/sys/class/thermal/thermal_zone0/temp @ 65 degrees)
- 3 different microUSB AC 5V adapters and cables
 
That voltage is within tolerance range of 2.97V to 3.63V for PHY VDD33 (per PHY DS). PMIC AC input tolerance range is 3.5V to 7V (per PMIC DS), so PHY should be getting conditioned ~3.3V consistently, even when microUSB AC source is used. Unfortunately I don't have a scope to monitor continuously, but if AC-IN voltage drops were affecting 1Gbps communications, I'd expect them to equally affect 100Mbps communications and that is not the case. So the issue with my board doesn't seem to be caused by PHY input voltage fluctuations.
 
However, there is a noticeable difference in the amount of packet loss with different power sources:
1. laptop USB, so <500mA, 2 feet USB cable
PC -> SBC: 30% loss
SBC -> PC: 36% loss
 
2. AC 5V/2A adapter, 6 feet USB cable
PC -> SBC: 5% loss
SBC -> PC: 11% loss
 
3. AC 5V/3A adapter, 3 feet USB cable
PC -> SBC: 15% loss
SBC -> PC: 31% loss
 
I'd speculate that there's possibly another element sensitive to AC input inconsistencies that might not be conditioned by the PMIC or that may have a narrow tolerance range. Alternatively, PINE64+ PCB layout might not be strictly following guidelines for RTL8211E IC as set forth in PHY DS, resulting in EMI affecting its operation or VDD10 conditioned input being outside of a narrow 0.95V to 1.06V tolerance range.
 
References:
PHY DS - http://files.pine64.org/doc/datasheet/pine64/rtl8211e(g)-vb(vl)-cg_datasheet_1.6.pdf
PMIC DS - http://files.pine64.org/doc/datasheet/pi...t_V1.0.pdf

https://plus.google.com/1119478323025725...jxfLtbp4iG

Pine 64 in a pine box The Pine 64 is already augmented with heat sinks and a fan. Added an Odroid wifi module 3 and USB camera. All ready for my computer vision projects. I don't need no stinking laser cutter or 3D printer when I have a rotatory tool. and old cigar box.

Hi all,

Been working on getting the camera module up a firing. Tonight I had success and got my logitech 615 webcam opening in a camera app. However it probably means that the himax 5mp camera won't work with these changes. Just out of curiosity how many people here have the himax 5mp camera? It should be possible to support both but as I don't have one I can't test it.

Will post a link to the module when its a bit more ready flag that here it is and eventually it will end up in Ayufan's Android builds.

To use the module ALPHA
https://drive.google.com/open?id=0B3jDRH...UtmcmVVckE

run adb remount

adb push 32bit/camera.tulip.so /system/lib/hw/
adb push 64bit/camera.tulip.so /system/lib64/hw/

and also everytime you start

lsmod and look for uvcvideo or ls /dev/ and look for video0

if they are not there do the following

adb shell insmod /system/vendor/modules/videobuf2-vmalloc.ko sorted in latest build, uvcvideo too
adb shell insmod /system/vendor/modules/uvcvideo.ko  (assuming kernel support)

---> these two last steps should be fixed eventually in a new os build latest Ayufan has fixed this

You should at least get a video feed with this module.

Bug Reports:

- app your using ( e.g skype, camera app)
- Device your using (camera not pine)
- adb logcat with errors
- steps to reproduce



as always I will not be held accountable if your pine melts down because you followed these instructions!

Hi,

The 2GB board arrived some months ago... but it is mostly catching the dust, not beeing used because of several issues: HDMI sync with the 1080p monitor (sometimes it works, sometimes no output, the monitor goes to sleep, have to restart the pine64 several times), unstable wifi (can set a wifi spot and connect to it but the 3 devices tested so far got disconnected every 20-30sec), network (looks like the Gb is limited to 1/10... 100Mb)... Tried both Longsleep's ubuntu and Lenny's debian.
Some protocols to test the board are already there in the forum, but either hidden in the middle of the comments or difficult to follow by newbies.

I was wondering if it would be possible to have a single thread gathering the testing protocols and their "how to use" ?

Thanks 

So I've been working with my pine for a few months now, trying to get a hadoop server running to support my work as an integration architect. My plan is to use the pine as a linux server, running multiple hadoop clusters, a postgres db and proprietary integration software from my employer. As an experiment I simply installed everything on the micro sd card, but that is not sustainable as far as size, so I experimented with using a usb thumbdrive as a pic. That only worked somewhat since I had to muck around with disk mounts etc, and ultimately as soon as I had it all working a bad shutdown corrupted the thumbdrive sending me back to square one.

I have since invested in a 1tb usb hdd, a powered usb hub, and now need to the optimal way of setting it all up. My first question is is it best to reformat the external hdd to a linux partition or leave it as ntfs. I know that ntfs has limitations with setting privileges, which is a issue with postgres. How would the linux gurus  approach this?