Hello
i was looking in the android image but seems that the gpio pins are not avaliable in the
/sys/class/gpio  directory
the directory does not even exist

so please any way that we can make this think work on android:>??

of course there is no a single tablet with GPIO
of course its a TABLET
not a Development BOARD!!
 
then why have android working on the board that have more thant 50+ gpio but u cant acceso from the OS u want  to run on >??

so i think that we need some examples to control them from android
with working pwm, spi, i2c, interrupts etc...

other wise its like y get this board if u need other board to do the things u want to do with it in the first place and the board itself have the gpio u need ????

thanks! :

Hi all, today we had a small blackout and my SD card is a damaged a bit...
- it boots, I can log in, but I can't install anything, due to this error:

Error: Unable to read file „/var/lib/dpkg/triggers/File“: Input/output error

I believe that I'm not first one with this problem, but can it be solved without reflashing whole SD card with new image?
Any suggestions?

bluetooth crashes when pairing for first time. using Pine64 2gb latest debian.

Attached Files

Thumbnail(s)
   

I am new to linux and i am trying to make a disk image of the setup that i have like the ones that are on the pine64 wiki page. I am trying to dd my microsd card and output that as a .img file. However, although it outputs a .img file it doesn't seem to work even if i write that to another microsd card.

It looks like the PINE64 can now run Windows IoT core according to the Wiki entry at https://github.com/Azure/azure-iot-sdks/...-csharp.md

Anyone gonna give this a shot?

So I have been attempting to create multiple lxd containers that willl each serve small services on my network:
yunohost, cups, pihole, whatever my heart desires...

This has been pretty easy - all of that is actually easy to get going. I just haven't been able to get them going together - on separate static ips.
_____________________________________

The problem is that I cannot figure out how to staticly assign ips to each of the services.

What I want is for each service - inside its own lxc container - to be persistently static on my home LAN.

________________________

I have tried all the tutorials about lxc and have basically lost my mind.

I tried bridging - but I basically don't know what is going on with that

One of the most obvious solutions - which worked on Debian Jessie but I can't get to work on ubuntu is to create
fake ethernet interfaces - like eth0:0 and assign each staticly. (Unfortunately lxd hasn't worked for me on debian - so this isn't a soltion for me....)

I can't get persistent fake eth0:0 interfaces on ubuntu ... part of the problem is in xenial they somewhat changed their /etc/network/interfaces setup - now /etc/network/interfaces.d/ is where devices are configured... and I can't find good information on how to add entries - adding files in interfaces.d creates an interface - but it doesn't work for long....


Any help would be much appreciated.

The Pine A64 already passed the Windows 10 Azure IoT certification: https://azure.microsoft.com/en-us/docume...gurations/

For the Pine A64 Windoiws IoT installation process, please refer to https://github.com/Azure/azure-iot-sdks/...-csharp.md

For the Pine A64 Window IoT code, please download from Pine64 file server: http://files.pine64.org/os/win10-iot/Win...Pine64.ffu

Please use this thread for Win 10 IoT discussion: http://forum.pine64.org/showthread.php?tid=1939

The Pine A64 already passed the Windows 10 Azure IoT certification: https://azure.microsoft.com/en-us/docume...gurations/

For the Pine A64 Windoiws IoT installation process, please refer to https://github.com/Azure/azure-iot-sdks/...-csharp.md

For the Pine A64 Window IoT code, please download from Pine64 file server: http://files.pine64.org/os/win10-iot/Win...Pine64.ffu

For developer that interest on the Pine A64 Windows IoT SDK, please stays tune. We will release the UEFI source code and Win10 BSP SDK package in few weeks time

I've extracted the un-rooted DD image for 8GB SD card, and there is no IMG file to burn to the SD card. What am I doing wrong?!?

Thanks (complete noob)

I took an experimental stage3 tarball for arm64 (http://distfiles.gentoo.org/experimental/arm64/) and integrated that with longsleep's simple-image to get a working solution. For the actual installation I just plugged the card into a cardreader and used the normal Ubuntu image to bootstrap the system. Following the Gentoo installation handbook works just like normal, just skip the parts about building a kernel / installing a bootloader of course... so if you want to try running Gentoo on the Pine, feel free to play with this test image:

http://itsdave.co.uk/pine64/Gentoo/gentoo-pine64-20160804.img.gz  md5sum: 2F049A4C2C16A3AF827E5A43C6C46DEB

Upload fixed, thanks to ItsDave for hosting the file!

I upgraded the packages of the stage 3 tarball and rebuilt most packages on the live system afterwards, added longsleep's platform scripts and corekeeper is already running in the background. So far I didn't hit any obstacles with installing / compiling packages for ARM64...

A dhcp client and a sshd are listening on eth0 and the default user/pw is 'gentoo/gentoo' , root password is also 'gentoo' so you might want to change that :-)

Of course this all comes with no warranty for anything whatsoever, but if you have a need for Gentoo, you probably already know what you are doing.

There will be no official support for this image, but feel free to ask questions and suggest additions to the base image!

--------------------------------------------------------------------------

2016-08-07 Update 1: If you run out of RAM while building larger projects (especially C++ ), try setting MAKEOPTS="-j3" instead of -j5

--------------------------------------------------------------------------

2017-01-15 Update 2: As shaggy013 pointed out, there are actually autobuilds for arm64 stage3 tarballs : http://ftp.halifax.rwth-aachen.de/gentoo...ge3-arm64/

--------------------------------------------------------------------------