So first off, while I'm a "professional computer guy", my expertise is Microsoft stuff, so before getting my raspberry pi 3 I had very little linux experience. The RPI3 has a lot of downloadable images that basically "just work" out of the box, but ROCK64 doesn't have that benefit yet. And with the more powerful hardware on this platform, I have been excited to figure this out... but to get it up and running I've had to learn quickly and do a lot of research. 

After banging my head against things, neglecting the family, angering the demon that is my wife, and having to start over again multiple times... I finally got RetroPie, RetroArch, and EmulationStation working. I figured I'd contrubute to the community with what steps I took, but I offer no support or guarantees. All I know is that now I'm "rock64ing" RP, RA, and ES

I wanted to use the newest linux builds available from ayufan but ran into problems booting (no video), so I ended up going back a few versions. I'm eventually planning to try to find a way to upgrade to the newest build without having to redo everything (if you know how, feel free to let me know, I'm still learning all this).

I started with jessie using the 0.5.10 build from ayufan (jessie-minimal-rock64-0.5.10-118-arm64.img.xz). I was using a computer monitor and an HDMI-DVI converter to configure everything on jessie, but once it got it all working I tried it on my TV and got no display : So I started over using stretch (stretch-minimal-rock64-0.5.10-118-arm64.img.xz). I'll post the details of both in case it helps anyone. And there's always a chance some of the steps I took were not necessary, but it worked out for me.

First off, as a relatively linux noob, here's my notes on some helpful linux commands that I had to learn and use in my trials: 
----------------------
To show version of installed package: apt-show-versions <package>

After a fresh OS install, run these to get everything updated:
  apt-get update
  apt-get upgrade
  apt-get dist-upgrade

To install newer/unstable versions of packages (such as gcc):
  echo "deb http://ftp.us.debian.org/debian unstable main contrib non-free" >> /etc/apt/sources.list.d/unstable.list
  apt-get update
  apt-get install -t unstable gcc-5

To downgrade/install a specific version of packages: sudo apt-get install <package-name>=<package-version-number>

To open compressed log files: zcat logfile.gz

To show all versions available for a package: apt-cache madison <package>

To show what packages depend on a specific package: apt-cache rdepends packagename

To list all installed packages: apt list --installed

To manually mount a USB drive: 
  mkdir /media/usb1 (if it doesn't already exist)
  mount /dev/sda1 /media/usb1

To Unmount a USB Drive: umount /media/usb1

To get CPU detail: lscpu

To get status of services: service --status-all

To restart a service: service <service name> restart

To force-overwrite packages after apt-get error: sudo dpkg -i  --force-overwrite  /var/cache/apt/archives/<package file name>.deb

To download a package files only without installing: aptitude download <package_name> (note: had to install aptitude)

Force network adapter to get DHCP address: dhclient eth0 -v 

To NEVER ALLOW DROP TO COMMAND and auto-start emulation station, add this to the bottom of ~/.profile:
   [[ -z $DISPLAY && $XDG_VTNR -eq 1 ]] && exec emulationstation
 (preferred method is to use retropie setup to tell ES to autorun in config)

To set the timezone: dpkg-reconfigure tzdata

To enable autologin: edit the file /lib/systemd/system/getty@.service and change the line
    ExecStart=-/sbin/agetty --noclear %I $TERM
  to
    ExecStart=-/sbin/agetty --noclear -a rock64 %I $TERM

Ways to build a debian package from source:
  checkinstall (had to add this package manually, but makes ANY INSTALLATION into a debian package and replaces the make command!)
  The next two are picky and require a true debian source package, needs to run from within the debian folder with a special file in it:
   dpkg-buildpackage -us -uc -b (this one seems to work the best)
   dpkg-deb --build <package name> 

 To add a root share after installing samba, add the below to the config /etc/samba/smb.conf (NOTE: retropie setup lets you do it without the console):
    [root]
    comment = root
    path = "/"
    writeable = yes
    guest ok = yes
    create mask = 0644
    directory mask = 0755
    force user = rock64
-------------


Now to the guts of the RP, RA, and ES installs:

For both jessie and stretch you'll need the most recent retropie source from github. Then use this pull request to make the necessary changes to the code to support a rock64 install:
https://github.com/RetroPie/RetroPie-Set...2205/files


ON JESSIE:
-----------------
First run the retropie-setup script after you've applied the pull request to source. This alone should allow you to run the retropie setup.

The release of jessie that I used has an older version of GCC and causes build errors when installing retroarch and emulationstation (unknown value 'native' for -march).
To build retroarch you'll need to upgrade GCC, so I added the unstable apt source (per my instructions above) and chose to install version 7.2.
To build emulationstation you'll need to upgrade G++, so I added the unstable apt source (per my instructions above) and chose to install version 7.2.

I attempt to install retroarch and emulationstation and after reviewing the logs find that they fail due to an attempt at overwriting existing libraries (because some are already included in the libmali-rk* packages). After the first failed installations I drop to console and apt-get remove the following:
 libsdl2-dev
 libmali-rk-utgard-2th-r7p0
 libmali-rk-dev
(don't reboot)

I then return to retropie-setup and attempt retroarch and emulationstation installations again. If I run into any failures again, I note the log file it refers to and I drop back to console and review the log and manually force the failing package to overwrite the existing one using the below command and try the install again:
  sudo dpkg -i  --force-overwrite  <full path to DEB file>

Eventually both RA and ES install successfully. But... ES doesn't start due to a segmentation fault. So, REINSTALL both libmali-rk* packages with force-overwrite. For example:
    sudo dpkg -i  --force-overwrite  /var/cache/apt/archives/libmali-rk-utgard-2th-r7p0_1.5-4ayufan12_arm64.deb
----------------------


ON STRETCH:
-----------------------
(for all below steps, whenever something doesn't install due to an overwrite, I use dpkg to force overwrite it, just like previously explained)
Ran all updates, upgrades, and dist-upgrades after the fresh image booted.
The first few times I tried this I ended up with the "unable to initialize SDL" errors and my attempts to fix it made things worse. This time I decided to be proactive and build a few packages first to try and get dependencies in place. I have no idea if this was absolutely necessary. But again, it worked.
   apt-get install xorg-dev
   apt-get build-dep xscreensaver vlc totem
I ignored any package warnings it throws at this point since I was just looking for some dependencies to get installed.
Now run the retropie-setup script after you apply the pull request from github.
Try and install Retroarch and Emulationstation. Any failures, review the listed log file and force overwrite the failing library manually using dpkg like I previously explained.
Eventually both will install, but emulationstation still returns unable to init SDL.
Did some testing and found that the libsdl2-dev package was actually on hold. I figured I'd remove and reinstall the libmali-rk-utgard package...
but it wouldn't let me due to a dependency issue. I installed aptitude to see what it recommended as a solution.
So first I let it install libmali-rk-midgard-4th-r13p0. Then I was able to successfully remove libmali-rk-utgard. 
Then I reinstalled the libmali-rk-utgard package using dpkg with overwrite.
Then I uninstalled and reinstalled libmali-dev.
------------

At this point, whether you're on jessie or stretch, you should be able to start ES and start installing your various emulators. Some will install just fine, and others will fail and you'll have to review logs and tend to the overwrites manually using the same methods we used during the install. I didn't test all the emulators but was able to get a good handful running without issues. Again, I can't make any promises or do much support on this, but I hope it helps some of you get up and rolling. If anyone has additions or runs into other required fixes, please post for the community benefit.

Good luck everyone, and happy rock64ing!

Dear all 

so happy to get yesterday my new Rock64 / 4G. 

Some issue, may some of you use to have the same issue ( Xenial and Debian distrib)

- VPN PPTP doesn t work 
      => copy/paste from my ubuntu rp3 which work
- RDP client (Remmina, freerdp, rdesktop) doesn t work
      => mouse disappear
      => screen refresh makes impossible to work on it
      => work fine on rpi3

thanks in advance

Does anyone know of a way to extend the power and reset buttons on the rock 64? Either a script for the pi2 bus or even resoldering the power button connections would work. I am a little hesitant with second option, since I do not want to damage the board. Any help would be appreciated

Rock64+android
Usb3.0 does not work
Usb 2.0 working.

Somebody can help me?
Thanks

I'm having no success booting up my Rock64 for the first time. I have successively with two 16GB Toshiba micro SD cards (backward compatible UHS-I). I first flashed a Debian image with Etcher. Then I read that it's recommended to use the Pine64 installer. So, I downloaded that and started with the Xenial Base image. Then I tried again with the Xenial Mate image thinking that the base image might not have the necessary HDMI driver. But no luck booting with any of these. The three LEDs light up solid, but nothing comes on the HDMI screen. I'm using the barrel socket power supply by Pine64 so power is not the issue. I even substituted a working micro SD card from my Raspberry Pi with a Raspbian OS, but the result is always the same. I'm a noob, but I really can't see what I'm doing wrong. Any help will be greatly appreciated!

Can anyone give a quick (hardware) run down of the delta from the Pine64 and the Pine64-LTS?

This will be a set of scripts I have been using to create a disk image and public images I have created off the current rock64 ayufan kernel and combined with Slackware Arm Current.
Install Instructions:

1. Download the latest slackware armhf release https://github.com/mwiljanen/slackrock/releases
   
2. As a privileged user please run: zcat slackware-current-minimal-rock64-0.5.10-118-armhf.img.gz | sudo dd of=/dev/sdX bs=4M status=progress
   
3. I have not created a script to autoexpand the drive so this must be done with gparted.
   
4. After boot you can login with user user: rock64 and pass: rock64 this user has sudo access.
   
5. To get this image on the internet you must use ifconfig or dhcpcd with an ethernet cable, Network manager is not installed on the slackware-minimal rootfs.
   
6. After you get a connection to the internet now you can install all the packages, but do not install the slackwarearm-current kernels, you can blacklist these in the /etc/slackpkg/blacklist. If you install this kernel your rock64 will refuse to boot. To upgrade do these steps:
   

• slackpkg update
  
• slackpkg install-new
  
• slackpkg upgrade-all
  

Hi guys ! I'm searching for a board  and i loved the many options here,  including the pinebook, and i have my 1° contact now with PINE64 ..
My objective is a cheap computer running UBUNTU.

I have some doubts , and i guess you can help me 

1.  Raspberry PI 3 X tinkerboard x ROCK64 ? Your personal experience 
2. Endless OS is supported ? https://support.endlessm.com/hc/en-us/ar...y-computer-

3. Rock64  has native wi-fi ? A Module wi-fi? 
 
4. PIDESKTOP is compatible ?  https://www.sparkfun.com/products/14354


In advance thanks .

Hello,

I tried posing about this issue on the Android forum several days ago but was not able to get help. So this is my last try I guess before just giving up.

This problem happened on the Raybuntu LibreElec build I had previously and on the Ayufan AndroidTV build I have installed currently. In androids settings it is set to sleep “Never” I’m not sure where else I should be looking. Also, I am using the power supply from Pine64 website that said it was for Rock64.

So whenever I let my system idle I come back to my tv showing “No Signal”. The lights on the Rock64 are still on like they normally are. If I short press the power button nothing happens. The only way I can get the system back on is to hit reset.

This is a very frustrating issue to have to reboot my system every time I need to use it. Especially since every time android asks me if I want to set up my SD card as memory (is there a way to stop this message?). Any help or advice would be appreciated. I’m not sure what else I should try.


Sent from my iPhone using Tapatalk

Which kind of distro do you use on Pinebook?