Hello, All.

I am attempting to use a Rockpro64 with bionic-minimal-rockpro64-0.7.9-1067-arm64.img as a headless server.

When initially powered on, everything works as expected, but after an amount of time that seems to vary between six hours and two days, the Rockpro64 stops responding to ssh, pings, and web requests. I tried connecting a monitor and keyboard to troubleshoot the problem. From the Rockpro64, the following things are true:

1. I can successfully ping other computers on the network by IP address, but pinging domains fails.
2. I can ssh into localhost, but cannot ssh into any other servers, even by referencing their IP addresses.
3. "arp" runs extremely slowly, but "arp -n" completes near-instantaneously.
4. Restarting the Rockpro64 fixes the problem temporarily, until it inevitably  comes back.

It looks like a DNS issue to me, but I do not know where to look from there. Do any of you wonderful people have suggestions?

My inexperience with Linux is the main problem. I'm used to solving my own technical problems, especially now that we have the Internet! With Linux, though, I keep running into walls that I have trouble overcoming.

I suspect, though, that some of my frustrations in installing wifi dongles on an A64+ may be due to bugs with software, whether Longsleep's image or other software I've installed.

Here are my steps, and the results. I'll mention installing VNC because that was a step I took. I'm still hopeful that I can get that going, but I'm open to all suggestions: 

1. Balena Etcher flash of xubuntu-xenial-mate-20161215-longsleep-pine64-8GB.img.gz onto 64gb micro SD (since I ran out of room with previous attempt using 32GB) -- Result great!

2. Sudo resize_rootfs.sh

3. Sudo apt-get update a couple times. Plus sudo apt-get upgrade and sudo apt autoremove a couple times.

4. Sudo apt-get install vnc4server -- Result: never did get it working as I have on Rasp Pi 3B+

5. Sudo apt-get install nano build-essential linux-headers-generic git

6. Mkdir ~/RTL8188EU

7. cd to above

8. git clone git://github.com/lwfinger/rtl8188eu
Result:
434 objects enumerated
434 of 434 objects counted
310 of 310 objects compressed
received 100% (12615/12615)
resolved deltas 100% (9368/9368)
connectivity checked

9. cd to ~/RTL8188EU/rtl8188eu

10. make all
Result: 
make ARCH=arm64 CROSS_COMPILE= -C /lib/modules/3.10.104/build M=/home/ubun/RTL8188EU/rtl8188eu  modules
make[1]: *** /lib/modules/3.10.104/build: No such file or directory.  Stop.
Makefile:151: recipe for target 'modules' failed
make: *** [modules] Error 2


11. Tried make instead of make all. Same result.

12. Looked in /lib/modules/ to confirm that there's a 3.10.104 folder.

13. Looked in /lib/modules/3.10.104 folder to find shortcut called "build". So it's /lib/modules/3.10.104/build. Looked at properties. The target is: /home/hxwong/build-pine64-image/linux-pine64
This will fail, right? If anything tries to build/make, whatever, it'll look for hxwong instead of ubun or whatever you have.

What did I miss? What should I do (or not have done)?

NexusDude
Early Kickstarter of Pine A64+

Are there any specific requirements on the POE side for the Rock64 rev3?

I had this board humming along for a good long while, and forgot about it for awhile.  Now whenever I apply power, I get a quick red LED blink once a second, with no other feedback.

The board is stenciled:

A64-DB-2G-Rev B
2016-02-25

I've searched and not found any report of a red LED blinking on boot, only solid red LED.

Can anyone tell me if it's a board failure, corrupted microSD, failed PSU, anything else?

Your experience and help is very much appreciated!

watou

Hi
I'm using the Pine A64+ (will update shortly to the LTS) for a project at work. 
I need to use several I2C sensors and SPI sensors too. 
Also, found the library for one of the sensors for RPi and I was wondering... the same tutorials/codes/examples/libraries from RPi work on the Pine A64?? 
I'm using Armbian Stretch, since I'm familiar with Debian

Thanks for the help

https://www.coreforge.com/blog/2019/06/r...book-wifi/

Thank my amazing friend and his skillset autism for this epic guide. 

  RA.png (Size: 368.53 KB / Downloads: 1,032)

The Retro Arena Open BETA - a custom tailored port of RetroPie - is now available for the RockPro64.
Remember that this is a beta software, which means some things may not work correctly; please report issues on The Retro Arena's GitHub.

Download Here

I ordered a 64GB eMMC for my Rock64.

The eMMC arrived preformatted in exFAT, and contained ransomware.

Hello forum-members,

I'm trying to get my bluetooth sound working on my Q4OS sd-card boot. In the standard KDE Neon image this works, but not on my new love Q4OS it doesn't work....

I am connected:

[Crosley CR8005]# devices
Device 30:21:10:2D:28:22 Crosley CR8005
Device FF:092:62:99:F8 N08CS
[Crosley CR8005]# connect 30:21:10:2D:28:22
Attempting to connect to 30:21:10:2D:28:22
[CHG] Device 30:21:10:2D:28:22 ServicesResolved: yes
Connection successful
[Crosley CR8005]#

But when I play music the sound is coming from the pinebook speakers....

Anyone an idea how to fix this?

Hi
Im new to with the system. I bought it two years ago but I was not able to use it before hehe

I want to use the Pine A64(+) to read several sensors, which are compatible with Arduino. I have two questions:

1) If I need to use the touch screen, that apparently only runs with Android 6.0.1, is there a way to also make use of the GPIO??

2) Are there libraries to use different sensors with those pins? or examples? I'm planing to use several sensors that work with analog outputs and I2C and SPI so I was wondering if there are info about that

Thanks!