It was brought up in the PINE64 Discord server that there was a bit of a lack of wallpapers for the Pinebook, and certain OS image creators wanted some to include.

So I took it upon myself to create a few -- five, in fact. Each in four different variations (1080p/768p, with/without Pinebook logo), for a total of twenty total wallpapers.

Wallpaper previews:

Aurora Sky
Nebulous Sky
Evergreen
Whisps of Time
The New Leaf

All of these wallpapers are free to use for personal use, re-distribution (including bundled with OS images), or modification -- I've licensed them under CC Attribution-ShareAlike 4.0 International.

Downloads:

Google Drive: https://drive.google.com/open?id=1iv0hiJz5RhgdH5JEafV2Ha5Wdkql6Fv4


(Additionally, the GIMP 2.10 project files for all of these can be found here. Same license applies.)

Enjoy!

Hi,
I got my new boards recently.
But I found the new one comes with v2.3
Just want to know what's the difference between v2.2 and v2.3?
Also, I found something interesting, when plugging the DC power,

my v2.3 board cannot boot all sopine module at the same time.
(Need try 2 ~ 3 times to bring all of them)

usually, 1 or 2 of them will stay off. (I use 50W DC power)

But v2.2 doesn't have such an issue. Any ideas?

Thx!

Hello,

I received my first RockPro64 4GB with NAS case, 30mm heat sink, and NAS case fan. Running Armbian Debian Stretch with Ayufan kernel 4.4.167-1213-rockchip-ayufan-g34ae07687fce

This is my first ARM board. When running htop, I would see CPUs 0-3 run at "600 MHz (   .LITTLE)" when idling to "1.42 GHz (   .LITTLE)" at load and CPUs 4-5 run at "600 MHz (big.      )" when idling to "1.80GHz (big.      )" at load. I was playing around with running processes with taskset to set the affinity of processes so that I could  run them only on CPUs 4-5.

Now I'm seeing all CPUs as "1.42 GHz (   .LITTLE)", including 4-5 which I believe should be in the big cluster, not little? The A72 cores are not going up to 1.80GHz at load. I didn't mess with any configuration, only ran "sudo taskset -c 4,5 java -jar ..." to see the JVM run on the A72 cores.

Can someone help me with more information? I've tried rebooting the RockPro64 and the processors did not go back to the original big little clusters or frequencies...

Thanks for any information or help that you can give me! I am pretty new to ARM project boards. I feel like I broke something with taskset...

I'm very new to big.LITTLE clusters so there's probably something that I am misunderstanding. The temperatures have been decently cool, around 34C max, so I don't believe any kind of thermal throttling has gone into effect, especially since I rebooted the server.

Hi.

Not from me.
I could not find this link in the forum and guess that some people might be interested.

Here are instructions to install NixOS on the Pinebook:
https://nixos.wiki/wiki/NixOS_on_ARM/PINE64_Pinebook

Hello,

right now I dont have a 5V 3A power supply
but I got another 6V 5A.
Can I use that for longterm?

thx

Hi,

First i want to thank you for building Android Pie for the rock64   .

I just saw it, and i wanted to install it, but i'm facing a issue i downloaded the file from this section : 



I installed the driver successfully and the rock64 is reconized i follow all the step frop the ayufan guide : 
http://files.pine64.org/doc/rock64/guide...o_eMMC.pdf

but i'm stuck after "Download Firmware 100%", the next step is "checking : failed" then, the rock64 doesn't reboot and if i do it have a android logo with a Error.

I tried 3 time with different usb port, after a reboot but, no luck yet, what's wrong ?

Thank you

Hi Folks,

I've received my NAS case, SATA PCIe HBA and other bits.

On first look, the case is well designed and laid out for this purpose (NAS).  The drive carrier frame needs to be a bit stiffer (rolled edges would help here) because it depends on the drives for stiffness and proper shaping.  The two orientation nubs have to be "helped" to get the drive carrier frame mounted and that's a bit of a pain with 3.5" drives installed.

A simple one page sheet with recommended drive orientation would be helpful also.  If you put the drives in with the SATA connector end towards the RockPRO64 end of the case, the cables bind against the SATA HBA.

Once that is sorted, things fit very well and the case is very sturdy.

The outstanding issues in my mind for now are -

- The light pipe is pretty useless unless the unit is in a dark room
- The unit should include a proper case fan as part of the base package
- The drive carrier frame needs its edges rolled to both add needed stiffness and save our fingers

Other than those three items, this is a perfect solution for use as a media server in a home environment or a small workgroup file server.  I've currently configured it with two 12TB Seagate He drives striped using mdadm for speed and capacity.

Performance tests will follow.

Hi,

I'm using a Rockpro64 board with ArmBian distribution.
The board is connected via HDMI to a display and via USB to the touch screen controller.
When the USB of the touch screen controller is connected the RockPro64 does not boot: it stuck in the boot room, on the console the only message I get is:
 
DDR Version 1.22 20190506 
In

then it stuck waiting for something.
If instead I remove the usb connection vs the touch controller, the RockPro64 boot normally.

Any ideas about the root cause of this problem? ANy solution?
Thanks in advance
BS

Max

Building in ubuntu,  via SMC card..

And chroot,  anyway ill take any tips getting grub uboot efi to fire up...

/boot , boot/efi 
/ 
7.25 swap.. else can respec parts slightly. 

Rpi3 gentoo,  can use a few of prebuilt bins,  to take some of the woe out..

Also building pentoo pkgs , for pentester use...

Hi,

I found Android P SDK on Wiki.
Who was already downloaded and build it?

https://wiki.pine64.org/index.php/ROCKPr...ndroid_SDK

If someone tried it, i want to know how to build and burn to sd card.