Hello everyone,
I want to setup a NextCloud instance, and thought the Rock64Pro would be awesome.

Pardon my ignorance, yet: What would you suggest in order to connect a 4TB hdd to the board?
Should I do it via USB?
I do *not* need super sata speed.
Once the hdd/nextcloud files are synchronized, I'll be good to go with USB speed.

Would connection via USB be the ideal way?
Any other suggestions?

Thank you for your help!

ANNOUNCING RECALBOX FOR THE ROCKPRO64 - BETA RELEASE

After many efforts with much teamwork, collaboration, and testing, we are very excited to provide the BETA release of RECALBOX for the ROCKPRO64 board!
-- The download is located under this repository's releases -- 
https://github.com/mrfixit2001/recalbox_...4/releases

Details on the ROCKPRO64 SoC can be found here: https://www.pine64.org/?page_id=61454

For those of you unfamiliar with Recalbox: https://www.recalbox.com/ 
"Recalbox offers a wide selection of consoles and game systems. From the very first arcade systems to the NES, the MEGADRIVE, 32-bit platforms (such as the Playstation) and even Nintendo64. With Kodi already included, Recalbox also serves as a Media Center. By connecting it to your home network, you will be able to stream videos from any compatible devices (NAS, PC, External HDD, etc.)."

Please do keep in mind that this is a BETA release, which means you should still EXPECT some things not to work quite right. We have done a LOT of testing on our own to try and resolve as many issues as we can before this release, but now you get to help! (Lucky you!) So if/when you do find things that don't work right, please use the link in github to report the issue.

When reporting issues:
- Provide logs and/or screenshots of the issue so that we can see the error(s) you are seeing
- Provide detailed steps for us to follow in order to reproduce the issue

We STRONGLY recommend that you install a heatsink on the board
CPU intensive tasks, such as 4K playback and demanding emulators, can create a substantial amount of heat. You can monitor your board's temperature and stats by enter it's IP address in a browser.

Improvements Since the Alpha Release:
Kernel Updates:
- Updated to version 4.4.169
- Various custom kernel fixes, mainline backports, stability and other enhancements
- 4K Playback @ 60fps is now smooth and Audio/Video are synced

Emulator Updates:
- Updated versions of many emulators and cores
- Buggy button re-mapping issue is resolved
- PPSSPP now performs at 100% speed for most games
- Customizable "max fps" setting in PPSSPP to fine tune your experience - set to 30fps to play GOW nice and smooth!
- PSP video scenes now play perfectly
- VirtualJaguar is now fixed and playable
- NEOGEO Core Fixed
- Bluetooth Controllers Reconnect After Reboot

Rockpro Specific Updates:
- WIFI and Bluetooth Module working (https://www.pine64.org/?product=rockpro6...4-1-module)
- RTL8812EU USB Wifi adapter working (https://www.pine64.org/?product=rock64-u...au-adapter)
- eMMC boot issues resolved
- Headphone / Audio-Out (ES8316) Fixed
- PCIe is enabled and connected storage devices have been confirmed to work correctly
- Improved Gigabit Ethernet performance
- Custom optimized resolutions for Mupen, PSP, and Reicast to hit 100% emulation speeds!
- EmulationStation menu music always playing


Some things that have been added to Recalbox that are Exclusive to my Pine64 releases:
- Upgraded Kodi (and addons) from version 17 (Krypton) to version 18 (Leia) alpha release
- Netflix Kodi app is included – you can login but it does not currently play anything (yet)
- Slight default overclock
- HDR and 4k Media Playback!
- Included Wolfenstein 3D (shareware version) in DosBox
- CEC working in KODI 
- IR working in KODI – supports multiple remotes out of the box, including the Pine64 / Rockbox remote
- Provided some emulator default settings, shader presets, and default cores
- Updated Library Versions with Buildroot 2018.2-3
- Custom patches to ES and Emulators to improve overall stability

A few things to know about this release:
When the image first boots, you can expect a delay as the partition is expanded to the full size of your disk. Please be patient and let this complete. It will not happen on every boot, but you should not interrupt this process or you may need to reimage.

Some controllers will work with KODI right out of the box without the buttons needing to be mapping (like the x360). For others, once you hit a button on the controller it will ask you to map them - you will need a keyboard to interact with KODI until your controller buttons are mapped.

N64 has multiple core options, different ROMS work better with different cores! So if your game isn't running well, try another core! So far even the most demanding games have been found to run perfectly with the right core selected.

Some emulators / cores are highly dependent on a valid BIOS files being installed (Dreamcast, for example). Be sure to read the documents in the system’s ROM folder for details on what BIOS files are needed. Further documentation is available on the Recalbox wiki.

A single ROM not working is not considered a "bug", it's often an incompatibility with the ROM and the emulator / core. We have provided multiple cores for some emulators to try and help maximize the number of ROMS that work.

If you are suddenly and unexpectedly thrown into KODI, then that means EmulationStation may have crashed. Please provide your /recalbox/es.log file so we can review.


"Where's the source code?" The source is being cleaned up and organized in preparation to be made available for the recalbox team to maintain, instead of having it hosted in this repository. Merging it with the recalbox repo allows them to maintain and update it, which ensures that you will receive their updates as they are made available.

Lastly, please remember this is a community build, and just something I've worked on in my free time. There's no pressure at all, but if you appreciate the work then feel free to send me a buck on Paypal: mrfixit2001 at gmail.

Special thanks go out to the LibreELEC and Recalbox teams, as well as LukasZ at Pine64 for his huge efforts in research, testing, and feedback!

Mr Fix-IT

A LibreELEC Beta for the RockPro64 (as well as regular Rock64) is now available directly for download.

Hi,
I want to use my rockpro64 constantly running for upto 1 year. It will run without any network and i want to get the correct time as well if sometime it gets shutdown and restarted. For that i have to use RTC power backup but what type and power of battery is required for that?
Thanks.

Hi,  I am looking for help to configure Euler Bus pin  in Pine A64+  to generate kernel interrupt. For example. Pin no. 27(PB2) in Euler Bus, have multiplexing function of PB_EINT2.
I would like to register interrupt handler for this pin in the kernel with a help of a simple kernel module.  Need help on how to define this pin characteristic in device tree file so that it can be configured to receive external interrupt. Any help will be highly apricated.

Regards
RANJIT

I am running Ayufan's linux bionic build. I started with bionic-minimal-pine64-bspkernel-0.7.29-138 (there was no bionic minimal for 7.30)

After fiddling with netplan (it didn't create a config file by default), manually setting DNS (was not working via DHCP), installing mate, and doing a bunch of updates I am now stuck with failing to get it running off the LCD. I edited the uEnv.txt under boot and added:
disp_screen0=lcd

but on boot it power cycles after trying to initialize the screen.

I have tried multiple 2.1a power adapters and cables but no go.  What is odd is I had the LCD working with an older image a while back with one of the same adapters and cables. Any advice?

thanks

Hellow everyon

ROCKPro64 board hardware encoding related questions.
I have built and installed gstreamer 1.15.0 version, gsteamer-rockchip, and mpp on the ROCKPro64 board.
For video and audio input of gstreamer, magewell's Pro HDMI capture card is installed in PCI slot.
I also built and installed gst-plugins-base, gst-plugins-good, gst-plugins-bad, gst-plugins-uqly, gst-libav, gst-omx, gst-python and gstreamer-vaapi.

gst-launch-1.0 v4l2src device = / dev / video0! video / x-raw, format = NV12, width = 640, height = 480, framerate = 30/1! queue! x264enc! queue! h264parse! mpegtsmux! filesink location = 2k.ts
With the above command, the video input is normally encoded and saved as a 2k.ts file.

However, if you enter mpph264enc as below, an error occurs.
gst-launch-1.0 v4l2src device = / dev / video0! video / x-raw, format = NV12, width = 640, height = 480, framerate = 30/1! queue! mpph264enc! queue! h264parse! mpegtsmux! filesink location = 2k.ts

Setting pipeline to PAUSED ...
mpi: mpp version: 107f498 author: Kamil Trzciński Update changelog
hal_h264e_api: vcodec type 00000000 can not find H.264 encoder device
mpp_hal: mpp_hal_init hal h264e_rkvenc init failed ret -1
mpp_hal: mpp_hal_init could not found coding type 7
mpp_enc: mpp_enc_init could not init hal
mpp: error found on mpp initialization

If you know the cause or solution to the above problem, please help me.


Thank you~

I have a project I'm working on that will be using a portable Thunderbolt 3 USB type-C display (hooray for only one cable!) and was looking for an SBC that would be able to drive it. I saw that the ROCKPRO64 has a USB type-C with DisplayPort 1.2, but I wasn't sure if that means it actually supports Thunderbolt 3 or not.

I saw that DietPi was highly recommended and had a Pinebook version.  I created a SD card with Etcher and the Pine64 Installer but neither will boot properly on my Pinebook 14 with the original 1366x768 display and the 64GB eMMC upgrade.

I see the same problem with the Dev Armbian using Kernel 4.19, so far other than the stock OS I have only been able to get Armbian Stable Kernel 3.10 to boot from SD and later install to the eMMC (had to format ext2 for it to work).

Any ideas?  I have the serial adapter on order to see if I can catch any messages on the serial console.

Is it possible to install Linux to pinebook to LUKS-encrypted partition? Is there any generic instruction (that is suitable for all or most distros)?