I had a problem compiling the rock64 kernel（https://github.com/rock64-linux?tab=repositories），
Buiding kernel and u-boot image: build/mk-kernel.sh rk3328-rock64（build/mk-uboot.sh rk3328-rock64） 
The current uboot partial compilation is OK。


 Building kernel for rk3328-rock64 board! 
 Using rockchip_linux_defconfig 
#
# configuration written to .config
#
scripts/kconfig/conf  --silentoldconfig Kconfig
  CHK     include/config/kernel.release
  CHK     include/generated/uapi/linux/version.h
  CHK     include/generated/utsrelease.h
  CHK     include/generated/timeconst.h
  CHK     include/generated/bounds.h
  CHK     include/generated/asm-offsets.h
  CALL    scripts/checksyscalls.sh
make[1]: 'include/generated/vdso-offsets.h' is up to date.
  CHK     include/generated/compile.h
  CC      arch/arm64/kernel/topology.o
  CC      block/elevator.o
  CC      crypto/ablk_helper.o
arch/arm64/kernel/topology.c: In function ‘parse_cluster’:
arch/arm64/kernel/topology.c:133:40: warning: ‘%d’ directive output may be truncated writing between 1 and 10 bytes into a region of size 3 [-Wformat-truncation=]
error, forbidden warning: topology.c:133
scripts/Makefile.build:258: recipe for target 'arch/arm64/kernel/topology.o' failed
make[1]: *** [arch/arm64/kernel/topology.o] Error 1
Makefile:983: recipe for target 'arch/arm64/kernel' failed
make: *** [arch/arm64/kernel] Error 2
make: *** Waiting for unfinished jobs....
  GZIP    kernel/config_data.gz
  CC      kernel/relay.o
crypto/ablk_helper.c: In function ‘ablk_init’:
crypto/ablk_helper.c:144:49: warning: ‘%s’ directive output may be truncated writing up to 63 bytes into a region of size 55 [-Wformat-truncation=]
error, forbidden warning: ablk_helper.c:144
scripts/Makefile.build:258: recipe for target 'crypto/ablk_helper.o' failed
make[1]: *** [crypto/ablk_helper.o] Error 1
Makefile:983: recipe for target 'crypto' failed
make: *** [crypto] Error 2
  CC      drivers/cpufreq/rockchip-cpufreq.o
block/elevator.c: In function ‘elv_register’:
block/elevator.c:839:14: warning: ‘snprintf’ output may be truncated before the last format character [-Wformat-truncation=]
error, forbidden warning: elevator.c:839
scripts/Makefile.build:258: recipe for target 'block/elevator.o' failed
make[1]: *** [block/elevator.o] Error 1
Makefile:983: recipe for target 'block' failed
make: *** [block] Error 2
kernel/relay.c: In function ‘relay_create_buf_file’:
kernel/relay.c:420:35: warning: ‘snprintf’ output may be truncated before the last format character [-Wformat-truncation=]
error, forbidden warning: relay.c:420
scripts/Makefile.build:258: recipe for target 'kernel/relay.o' failed
make[1]: *** [kernel/relay.o] Error 1
Makefile:983: recipe for target 'kernel' failed
make: *** [kernel] Error 2
^CTraceback (most recent call last):
  File "./scripts/gcc-wrapper.py", line 102, in <module>
    scripts/Makefile.build:403: recipe for target 'drivers/firmware' failed
scripts/Makefile.modbuiltin:54: recipe for target 'drivers/gpu/arm/mali400/ump' failed

I'm a CS student at the University of Arizona.  I have a $500 budget for educational supplies to kill this semester and decided I wanted to take a dive into cluster computing.  After careful research and deliberation, I decided that the clusterboard would be the best balance of power, price and desk space.  This research was hindered by the fact that I could not find a good step by step guide to setting up a clusterboard.  So I've decided to make my own.  I have a reasonable amount of experience with hardware, software, and networking so (with plenty of chat support) I was able to figure this out.  I'm still in the process of updating this post but the machine is up and running!

--------------
TL;DR

https://www.youtube.com/watch?v=vfFoCpkS_Ho

--------------
Hardware

FROM PINE64 STORE:

Cluterboard
https://www.pine64.org/?product=clusterb...dule-slots

Compute Modules - (7)
https://www.pine64.org/?product=sopine-a64

---Optional extras---

64GB eMMC (for NAS/high speed disk space)
https://www.pine64.org/?product=64gb-emmc

USB eMMC interface (for debugging)
https://www.pine64.org/?product=usb-adap...mmc-module

SOPINE baseboard (backup interface for testing compute modules)
https://www.pine64.org/?product=sopine-h...rd-model-a

USB TTY (allows terminal access through GPIO for debugging)
https://www.pine64.org/?product=padi-serial-console

---FROM AMAZON---

16gb SD Card 10 pack - (3 left over)
https://www.amazon.com/gp/product/B00WUCNGVQ/

80mm fans - (2 x exhaust)
https://www.amazon.com/gp/product/B002QVFN7G/

Fan power adapter - (1 end for 200mm that comes with the case, 2 for the back)
https://www.amazon.com/gp/product/B075NPZ94N/

Case - (This case is oversized but extra space is used for air flow)
https://www.amazon.com/gp/product/B00M2UKGSM/

Heatsinks 8 pack - (3 packs,Each compute module should get a heatsink on CPU, memory and power management unit.  21 total)
https://www.amazon.com/gp/product/B00637X42A/
**WARNING THESE MIGHT NOT COME WITH ADHESIVE**
These pads can replace the missing adhesive
https://www.amazon.com/dp/B074K55CWF/

Power Supply - (12V 12.5A 150W Provides more power than the one from the Pine store for running fans.)
https://www.amazon.com/dp/B01N3ASWZ0/

160w Power Header For board and fans - (splits power to board and fans)
https://www.amazon.com/dp/B07H1M8B1S/

-Extras
- continuous switch from my local electrical supply store
- clear acrylic to block the extra vents and create a wind tunnel.

--------------
Power

There are lots of ways to power the board.  The Pine Store sells a power supply but you'll have to modify your board to power fans.  You can use the ATX port on the board, but you'll need to soldier some pretty large resistors.  If you don't make the special ATX mods, you'll need to use a continuous switch to keep it on.
--------------
Gateway/Management Computer

The internal networking switch on the clusterboard does not provide DHCP.  As an alternative to running on my router, I've decided to build a gateway out of a first edition Pine64 from the kickstarter.  It acts as DHCP, a router allowing the cluster to access the internet via wifi, terminal access to the cluster, and a time/file/dhcp/dns/etc server.  While this is certainly something I recommend doing, how you implement it will depend on what kind of device you use.  In this guide I'll refer to things you need to do but only when dealing with the clusterboard itself will I be providing specific steps.

Ideally, the sopine LTS kit would make the best gateway.  However, the network port on it is only 10/100.  Gigabit is what you need.  Most newer boards have this just make sure to research the specs before you buy.  If you want to go all out, the rockboard pro has a NAS setup that would work nicely.  With any luck, the same linux distro on any Cortex A53 should be able to compile programs and act as part of the cluster but no promises until I can do some more testing.
--------------
Airflow/Cooling

I've added a lot of extra case space and hardware for cooling.  I've been told this is overkill but if you want experience building clusters, you should probably know that cooling takes up a good part of the budget.
--------------
Bench Testing

Before we fully assemble the machine, we're going to do all of the initial setup.  Once we know everything runs, we can put it together and put it to work.
--------------
Prepare the SD cards

https://www.armbian.com/sopine-a64/

The best image (as of this post) is Armbian because of the continuous support.  However, I had to use the 3.10 xenial image (found under "other options") instead of Stretch (Debian) or Bionic (Ubuntu).

https://etcher.io/

The armbian site recommends this software for writing the images to the SD cards.  Feel free to use whatever software you like.  I don't think it matters.
--------------
For each compute module

(Notice the ATX style power switch connection just below the ATX power connector.  Helps when you want to turn it on --


You need to plug each module in one at a time (DO NOT HOT SWAP) and do the following steps:

-Assign it a static IP address from your DHCP server
--find it when it pulls an IP address
--use the MAC address to make the assignment from the DHCP server configuration
--be sure to give it an address outside of the automatic range (ie give them *.10-16 if your DHCP server hands out *.50-100)
--make a list of the static assignments to help later

-Login (ssh client from your gateway or management computer) with root access(if using ARMbian [username: root][pw: 1234])
--complete any first time setup
--this may include generating a user account(you'll probably want to make it's the same username on all of them)
--use "hostnamectl set-hostname [myhostname]" to give each a unique hostname (ie cluster[0-6])
--be sure to shutdown before turning the power off and test the module in the slot you plan to use it.

once each module has been tested, we can move on to testing it as a whole.
--------------
csftp and cssh

These next steps will require special software on the computer you're using to access the cluster.  Linux offers an easy way to connect to all clients at once.  See your distribution's pacman or apt-get information for details on how to install it if it isn't already there.

Alternate Windows software:
https://github.com/dprokscha/cputty

I don't know of an FTP option for windows at this point.  However, if you setup RSA keys, Filezilla will at least make it easy on you.
--------------
RSA keys

The next task involves generating RSA keys so the gateway and compute modules can talk to each other without login authorization.  Linux users can use "ssh-keygen -t rsa".  With default options, that should create two files in "~/.ssh/" named "id_rsa" and "id_rsa.pub".  If you're already using RSA keys, you can direct these files to be generated elsewhere.  Rename "id_rsa.pub" to "authorized_keys".  Then you can SFTP those files in to the "~/" (known as home) folder of the account you would like to use on all the compute modules.  Personally, "sudo" has never saved me from doing anything stupid so I like to live dangerously and use root.

Windows users can generate the keys while logged in to the first node in the cluster or generate "id_rsa"(private) and "authorized_keys"(public) using an online tool like this:
https://qsandbox.com/tools/private-public-keygen

You'll need to configure your ssh/sftp client software to use the keys.
--------------
cssh/csftp clusters file

Users of cssh can create a file "/etc/clusters" that contains a text label that will allow you to tap in to all the compute modules at once just by typing "cssh [label]".
https://linux.die.net/man/1/cssh


I'm sure other clients have a way of doing this.  For now, just make sure you can with whatever software you're using.  Now that we know everything works, time to box it up.
--------------
Disassembling the case



All the sides and the top are only connected by obvious screws.  I also took out and set aside the HDD mounting brackets.  The front can be pulled off gently.  I had to take off the big fan and take apart the mounting plate for the ATX switch to put in the continuous switch.
--------------
Adhesive Thermal Pad/Heatsinks



Because The hearsinks didn't dome with any adhesive the way they're supposed to, I got up close and personal with the exacto knife.  The goal is to have a heatsink on all 3 of the major parts (CPU, memory and power)



Steer clear from the white border or you'll have trouble installing the compute modules.



This is also the point of no return for GPIO headers.  Once the heatsinks are on, they're hard to get at.  Make sure everything is running so you don't need to get at them with the serial interface.




Once they're all set up, sandwich the chips between some bubble wrap and put a softcover book on top for a couple hours / overnight to let the adhesive set.
--------------
Motherboard mounting (or how I learned to stop worrying and love zip ties)



I can't say enough bad things about the mounting holes on this board.  The placement complies with Micro ITX but their size is just a tad smaller than the holes on the case.  Not to mention that one is right up against the ATX molex.  The case came with rubber feet and zip ties so I improvised.  Afterwards, I installed the case fans and routed power.
--------------
Acrylic

I put some clear plastic over most of the vents to create a wind tunnel.  I took a picture but it wasn't very clear.
--------------
Setting up servers

From here, what software you set up will depend greatly on what task you plan to do with it.  The good news is that from here on out, every other guide for setup should be valid.  You have 7 quad core Arm64 processors running a basic setup of Linux that will allow you to do anything any other cluster would do.  (assuming they don't require a different processor architecture)  As a CS student who will be doing parallel programming in the near future, I wanted to setup Open MPI.  I wound up setting up my gateway as a time server and a file server.  I was able to use apt-get to update software on the compute modules and install packages needed to access server functionality.  As long as you can figure out how to apt-get or compile the software you want to run, you should be good to go.
--------------
Open MPI

I used the steps in this guide to get the basics of Open MPI going:
http://mpitutorial.com/tutorials/running...hin-a-lan/

But I made my own version of the "hello world" program:
https://github.com/PhillBenoit/OpenMPI-h...i_sample.c

This is what it looks like when it runs:


--------------
Final thoughts

The board itself has some hardware quirks but the processing power is real.  Setting up a server/gateway solves lots of problems and can offload what would normally be cluster0 tasks.  This build is more challenging on the software side than it is the hardware side.  I wouldn't recommend it for novice linux users / network admins.  That being said, it's not overly difficult if you can manage to work your way around Linux.  If you want to build a small ARM cluster capable of running serious tasks, this is definitely the way to go.  The board itself consolidates what would be a massive amount of space as well as preventing wiring headaches.
--------------
Thank you for reading my post.  If you have any input or suggestions (including information that needs to be updated.), please leave a comment to let me know.

Hello guys,

I would like to install a clean and official version of Ubuntu.
Is it possible to install the ARM version published by Ununtu?

Link: https://www.ubuntu.com/download/server/arm

The forum Armbian JMCC published script includes the video acceleration on rk3328.

https://forum.armbian.com/topic/9310-rk3...-renegade/

If anyone tested write a review.

When is Android 9 released?
Other companies already released Android 9 for RK3328 and Rockchip already discontinued Oreo on RK3328 a couple of months ago.

So the glued 14" screen lead to some frustration and that lead to a cracked monitor cable connector on the 14" Pinebook and that lead to some lifted/cracked contact pads ...
Long story short: I need a new Pinebook 14" mainboad. When will they be available again?

I took my work to enable audio over the I2S port and put it on github to share with everybody.  Enjoy if you want.  I started from the Armbian patches for the legacy kernel used for Ubuntu 16.04 xenial.  I only changed the DTS for the Pine64+ boards because that is what I am using.  I have a Pine64 512MB board, but haven't tried it, yet.  Enjoy: https://github.com/looperlative/linux-pine64-armbian

This question is specifically for the Clusterboard, and as dumb as it sounds, I'm serious here.

I've inserted countless sticks of RAM before, and while sometimes it takes a little force, I've never felt like I was about to break the motherboard trying to get them to snap in. My Clusterboard, on the other hand, takes so much force that I'm afraid the SOPINE module is going to fold in half.

Does anyone else have to push insanely hard to get their SOPINEs inserted? I've tried cleaning the slots with compressed air, and obviously I have the notch lined up...they won't go in backwards, but they really don't want to go in forwards, either.


For the record, I bought my Clusterboard from ameriDroid back in August. They have the disclaimer about being a pilot batch of boards with a pull-up wire glued on for the eMMC. I remember worrying that I was going to break something when I installed my first two SOPINEs back then, but I got them in and running. This week I pulled them out for some testing on the Baseboard, and now I don't think I can get them back into the Clusterboard at all. Maybe it's due to the temperature being several degrees cooler in my house this time of year, it's like the plastic has contracted or hardened to the point where the modules just won't go in.

I can't believe my board is any different from the rest of the batch, but it's surprising I can't find any posts at least mentioning this issue.

Thanks,
Jesse

Has anyone tried OpenBSD on the Pinebook 1080p?  It looks like they support other PINE64 models, but no image is available, just some installation files on their mirror.

Hi guys,

I'm looking for this problems for months now and it seems I can't find any solution to this problem.

I've bought the Rock64 especially because it has an infrared sensor build in to control it with my Harmony remote One.


Any solutions i've find doesn't work.
- program it as another media device that runs android.
- program it with the NEC code. I can't add that in the harmony software.
- program it as a pine64 device. That device doens't exist in the harmony software.

I think the only solution is to program it with the remote dat Pine64 offers but I can't find the original manifacturer or any other after sale brand that is known in the Harmony software.

I'm hoping some other members had the exact same problem and had their remote work with the Rock64.

Greetings