| Welcome, Guest |
You have to register before you can post on our site.
|
| Forum Statistics |
» Members: 29,772
» Latest member: d2minik
» Forum threads: 16,285
» Forum posts: 117,303
Full Statistics
|
| Latest Threads |
Window Maker Live for Pin...
Forum: Linux on Pinebook Pro
Last Post: vajak
12-24-2025, 06:00 AM
» Replies: 2
» Views: 377
|
Rrkisp issue with CSI cam...
Forum: Linux on Quartz64
Last Post: lystar
12-24-2025, 02:34 AM
» Replies: 1
» Views: 3,753
|
bookworm vs trixie discus...
Forum: Mobian on PinePhone
Last Post: Kevin Kofler
12-24-2025, 12:11 AM
» Replies: 80
» Views: 45,612
|
Fedora + Phosh for PinePh...
Forum: PinePhone Software
Last Post: shanehill@mail.com
12-23-2025, 09:12 PM
» Replies: 75
» Views: 200,954
|
Trixie - bring up the On ...
Forum: Mobian on PinePhone
Last Post: grump_fiddle_reinstall
12-23-2025, 04:34 AM
» Replies: 0
» Views: 76
|
On-Screen Keyboard Arrow ...
Forum: Mobian on PinePhone
Last Post: grump_fiddle_reinstall
12-23-2025, 04:25 AM
» Replies: 11
» Views: 6,071
|
Armbian has been released...
Forum: News
Last Post: ArmbianForSBCs
12-23-2025, 01:36 AM
» Replies: 21
» Views: 32,282
|
Alarm clock doesn’t work
Forum: Mobian on PinePhone
Last Post: biketool
12-23-2025, 12:12 AM
» Replies: 14
» Views: 24,441
|
Diagnosing and fixing fai...
Forum: PinePhone Pro Software
Last Post: biketool
12-22-2025, 11:59 PM
» Replies: 7
» Views: 622
|
No phone call audio, logs...
Forum: PinePhone Pro Hardware
Last Post: biketool
12-22-2025, 05:09 PM
» Replies: 12
» Views: 867
|
|
|
| Deinterlacing not working in Kodi 17/18 |
|
Posted by: Blinky - 08-15-2017, 08:52 PM - Forum: Android on Rock64
- Replies (1)
|
 |
Deinterlacing of videos don't seem to work in Kodi 17 or 18.
It seems to be a problem with Mediacodec.
If you turn it off deinterlacing works but then it uses 100% CPU resources and is then too choppy to play.
The problem doesn't exist on other socs like RK3288 from the same chip manufacturer.
Here is a sample video to try, the video is not deinterlaced.
With the stock video player and MXPlayer the video plays correctly.
https://drive.google.com/file/d/0BwxFVkl...VyZGM/view
Is there a way to solve it?
|
|
|
|
Rock64 Linux Image Writing Scripts Codes and Tutorial |
|
Posted by: MarkHaysHarris777 - 08-15-2017, 07:34 PM - Forum: General Discussion on ROCK64
- Replies (4)
|
 |
Greetings,
The purpose of this post is to make available as quickly as possible the Rock64 Linux Image Writing Scripts ( codes and tutorials ) as well giving theory and instructions for their use.
Both of the scripts presented her derive directly, and were ported from, ayufan's "Pinebook to eMMC" script and perform the same function, yet over the Rock64 repos ( the arm64 primary images ).
Theory
Place these scripts ( as well the "curl" and "jq" packages ) on your gnu+linux system and use them to download and write the desired image from the network repos directly to the SD card ; or even to the eMMC module using an adapter ! In addition the scripts may be placed on your bootable SD card in preparation for using the jumper setting technique for writing a network repo image directly to the eMMC memory module. The flexibility is your own choice. I have pushed the script(s) as a github PR, and eventually they will be included in the images automatically.
The Scripts
rock64_install_to_emmc.sh
Code: #!/bin/bash
set -eo pipefail
if [[ "$(id -u)" -ne "0" ]]; then
echo "This script requires root."
exit 1
fi
echo "Rock64 Release Installer!"
echo "(C) 2017. Kamil Trzciński (https://ayufan.eu)."
echo ""
usage() {
echo "Usage:"
echo "$ $0 <system> [version]"
echo ""
echo "Systems:"
echo " - xenial-minimal (https://github.com/ayufan-rock64/linux-build/releases)"
echo " - xenial-mate (https://github.com/ayufan-rock64/linux-build/releases)"
echo " - xenial-i3 (https://github.com/ayufan-rock64/linux-build/releases)"
echo ""
echo "Version:"
echo " - latest will be used if version is not defined"
exit 1
}
if [[ $# -ne 1 ]] && [[ $# -ne 2 ]]; then
usage
fi
if [[ ! -d /sys/devices/soc.0/1c10000.sdmmc/mmc_host/mmc1 ]]; then
echo "You should boot from SD card"
exit 1
fi
if [[ ! -e /dev/mmcblk1 ]]; then
echo "You should boot from SD card"
exit 1
fi
case "$1" in
xenial-minimal|xenial-mate|xenial-i3)
REPO="ayufan-rock64/linux-build"
PREFIX="$1-rock64-"
SUFFIX="-[0-9]*-arm64.img.xz"
ARCHIVER="xz -d"
;;
*)
echo "Unknown system: $1"
echo ""
usage
;;
esac
VERSION="$2"
if [[ -z "$VERSION" ]]; then
VERSION=$(curl -f -sS https://api.github.com/repos/$REPO/releases/latest | jq -r ".tag_name")
if [ -z "$VERSION" ]; then
echo "Latest release was not for $1."
echo "Please go to: https://github.com/$REPO/releases/latest"
exit 1
fi
echo "Using latest release: $VERSION from https://github.com/$REPO/releases."
fi
NAME="$PREFIX$VERSION$SUFFIX"
NAME_SAFE="${NAME//./\\.}"
VERSION_SAFE="${VERSION//./\\.}"
echo "Looking for download URL..."
DOWNLOAD_URL=$(curl -f -sS https://api.github.com/repos/$REPO/releases | \
jq -r ".[].assets | .[].browser_download_url" | \
( grep -o "https://github\.com/$REPO/releases/download/$VERSION_SAFE/$NAME_SAFE" || true))
if [[ -z "$DOWNLOAD_URL" ]]; then
echo "The download URL for $NAME not found".
echo "Look at https://github.com/$REPO/releases for correct versions."
exit 1
fi
echo "Doing this will overwrite all data stored on eMMC."
while true; do
echo "Type YES to continue or Ctrl-C to abort."
read CONFIRM
if [[ "$CONFIRM" == "YES" ]]; then
break
fi
done
echo ""
echo "Using $DOWNLOAD_URL..."
echo "Umounting..."
umount -f /dev/mmcblk1* || true
echo ""
echo "Downloading and writing to /dev/mmcblk1..."
curl -L -f "$DOWNLOAD_URL" | $ARCHIVER | dd bs=30M of=/dev/mmcblk1
sync
echo ""
echo "Done."
rock64_install_to_SD.sh
Code: #!/bin/bash
set -eo pipefail
if [[ "$(id -u)" -ne "0" ]]; then
echo "This script requires root."
exit 1
fi
echo "Rock64 Release Installer!"
echo "(C) 2017. Kamil Trzciński (https://ayufan.eu)."
echo ""
usage() {
echo "Usage:"
echo "$ $0 <system> [version]"
echo ""
echo "Systems:"
echo " - xenial-minimal (https://github.com/ayufan-rock64/linux-build/releases)"
echo " - xenial-mate (https://github.com/ayufan-rock64/linux-build/releases)"
echo " - xenial-i3 (https://github.com/ayufan-rock64/linux-build/releases)"
echo ""
echo "Version:"
echo " - latest will be used if version is not defined"
exit 1
}
if [[ $# -ne 1 ]] && [[ $# -ne 2 ]]; then
usage
fi
#if [[ ! -d /sys/devices/soc.0/1c10000.sdmmc/mmc_host/mmc1 ]]; then
# echo "You should boot from SD card"
# exit 1
#fi
#if [[ ! -e /dev/mmcblk0 ]]; then
# echo "You should boot from SD card"
# exit 1
#fi
case "$1" in
xenial-minimal|xenial-mate|xenial-i3)
REPO="ayufan-rock64/linux-build"
PREFIX="$1-rock64-"
SUFFIX="-[0-9]*-arm64.img.xz"
ARCHIVER="xz -d"
;;
*)
echo "Unknown system: $1"
echo ""
usage
;;
esac
VERSION="$2"
if [[ -z "$VERSION" ]]; then
VERSION=$(curl -f -sS https://api.github.com/repos/$REPO/releases/latest | jq -r ".tag_name")
if [ -z "$VERSION" ]; then
echo "Latest release was not for $1."
echo "Please go to: https://github.com/$REPO/releases/latest"
exit 1
fi
echo "Using latest release: $VERSION from https://github.com/$REPO/releases."
fi
NAME="$PREFIX$VERSION$SUFFIX"
NAME_SAFE="${NAME//./\\.}"
VERSION_SAFE="${VERSION//./\\.}"
echo "Looking for download URL..."
DOWNLOAD_URL=$(curl -f -sS https://api.github.com/repos/$REPO/releases | \
jq -r ".[].assets | .[].browser_download_url" | \
( grep -o "https://github\.com/$REPO/releases/download/$VERSION_SAFE/$NAME_SAFE" || true))
if [[ -z "$DOWNLOAD_URL" ]]; then
echo "The download URL for $NAME not found".
echo "Look at https://github.com/$REPO/releases for correct versions."
exit 1
fi
echo "Doing this will overwrite all data stored on eMMC."
while true; do
echo "Type YES to continue or Ctrl-C to abort."
read CONFIRM
if [[ "$CONFIRM" == "YES" ]]; then
break
fi
done
echo ""
echo "Using $DOWNLOAD_URL..."
echo "Umounting..."
umount -f /dev/mmcblk0* || true
echo ""
echo "Downloading and writing to /dev/mmcblk0..."
curl -L -f "$DOWNLOAD_URL" | $ARCHIVER | dd bs=30M of=/dev/mmcblk0
sync
echo ""
echo "Done."
Instructions for Use:
Be sure to make both scripts executable as always with :
chmod 0754 rock64_install_to_SD.sh
Both of the above scripts function the same way and have some very subtle differences, but generally have the same theory of operation; the user selects a system image and version -- the script then finds the latest ( not pre release ) build, verifies it, and then downloads it from the network repos directly to the SD card, or even to the eMMC module via an adapter.
Sample syntax of the command is :
sudo ./rock64_install_to_SD.sh xenial-mate 0.4.16
sudo ./rock64_install_to_SD.sh xenial-minimal
If the version number is omitted then the script will find the latest ( not pre release ) build release! The three primary arm64 versions are supported with this script: xenial-mate | xenial-i3 | xenial-minimal
The scripts differ mostly in their error checking, and where they write; the SD.sh script writes to /dev/mmcblk0 while the emmc.sh script writes to mmcblk1. The emmc.sh script makes sure that you're booted on the SD card first ! (very important for writing to the eMMC on the same system). Otherwise, the two scripts are mostly identical and perform the same function.
The SD.sh script may be also used to write to the eMMC module if the module is placed into an adapter for use with the PC gnu+linux system. The benefits of these scripts is two fold: 1) they are very fast with no intermediary step, and 2) the SD or eMMC is written to without having to play around with dd or Etcher ( or some other ) as well the syntax checking and command parsing is completely automatic ; all the user has to know is the system and the version.
I have tested both of these scripts within reason and have found that they are functional and useful; if the scripts are placed on your bootable SD card ( for writing to the eMMC module on-board with the jumper technique ) then they become very powerful for downloading and installing the desired image directly to the eMMC module from the network repos. This is the very same technique that is used on the Pinebook to write images to its on-board eMMC module.
The Rock64 eMMC tutorial will be updated with this information.
As with any derived work, I have left ayufan's name attached due to respect, as well copyright and dignity of propriety; however, any errors are mine alone and I am responsible to correct any errors that might be found, quickly.
|
|
|
|
| RetroPie on Rock64 |
|
Posted by: Luke - 08-15-2017, 04:17 PM - Forum: Linux on Rock64
- Replies (41)
|
 |
The purpose of this thread is to raise awareness about the endeavour to get RetroPie support for the Rock64. tllim has already sent out sample boards to BuZz from RetroPie and he happily accepted them.
While we keep our fingers crossed for official support, I feel it would certainly help if members of our community who are interested in using the R64 for the purpose of emulating retro games would help out making this happen. rtissera has already started tinkering and is trying to get a working build going.
Those who are interested in helping out - let me know 
|
|
|
|
| Ubuntu + KGDB |
|
Posted by: coinageboy - 08-15-2017, 02:59 PM - Forum: Linux on Rock64
- No Replies
|
|
I have re-compiled latest longsleep with KGDB enabled.
The kernel shows /sys/module/kgdboc/parameters/kgdboc
but I can not insert ttyS2 into it as the system claims that there is no device.
Can someone offer advice???
|
|
|
|
| Continued support? |
|
Posted by: EricL - 08-15-2017, 02:31 PM - Forum: Remix OS
- Replies (9)
|
|
Given the announcement at Jide, should we continue to use RemixOS on Pine64? It's not clear which versions of RemixOS they are abandoning (other than the PC version), and they mention supporting "enterprises" but I have no way of knowing if the Pine64 falls under that umbrella. Do we have any word from Jide as to whether or not we'll have continued support here?
|
|
|
|
| Wifi |
|
Posted by: dsmart978 - 08-15-2017, 01:30 PM - Forum: Android on Rock64
- Replies (9)
|
|
Received my Rock64 in the mail today. Didn't buy a USB wifi dongle. I want to run Android. Is there a specific USB dongle I should buy?
|
|
|
|
| Pine64 Debian Stretch/mainline [4.14.7] |
|
Posted by: CallMeFoxie - 08-15-2017, 01:01 PM - Forum: Debian
- Replies (50)
|
 |
Hi
As I've created a thread earlier last week, I've got a working image for Pine64+ with complete mainline support:
Features
Kernel 4.14 branch, few extra patches (ethernet DTB revert and few others)
U-Boot 2017.09 branch, no external patches
NO boot0! Uses U-Boot SPL
Updates via normal debian packages for kernel (metapackage linux-image-pine64 keeps up2date kernels), no u-boot automated updates yet
Docker 17.09 branch or newer (installable via Debian package docker-ce) with Overlay2 full support
Debian Stretch with Systemd
Boot log: https://github.com/CallMeFoxie/pine64-ma...ootlog.txt
Tested on 2GB Pine64+, should work on 1GB version as well, unsure about 512MB version. Definitely would need to swap DTBs around.
Docker and Kernel are hosted on my repo (https://repo.foxiehost.eu/debian stretch main) and its key is imported to the image.
Boots via U-Boot through extlinux.conf -> ext2 partition with vmlinuz-* + fdt file -> ext4 rootfs (default 4GB, can be resized).
Kernel updates trigger extlinux.conf generator, normal kernel rules apply (keep last 2 and mark the other for removal etc).
Downloads:
[b]Base build 2017-10-15
[/b]https://repo.foxiehost.eu/pine-image/pin...015.img.xz
Kernel 4.13.6/U-Boot 2017.09
Base build 2017-08-15
https://repo.foxiehost.eu/pine-image/pin...815.img.xz
Kernel 4.13.0-rc5/U-Boot 2017.09-rc2
Source configs and scripts to build the images:
https://github.com/CallMeFoxie/pine64-mainline-project
(uses Docker to compile kernel/uboot/atf)
Known issues for latest base image:
SSH keys are not re-generated! It is suggested to delete them and ssh-keygen -t them on the first bootup. (Fixed in github already)
Fixed clock (~900MHz), no cpufreq/voltage regulation - missing kernel modules in upstream (as of 4.13.0-rc5)
No HDMI output (missing drivers)
Default config:
IP: 10.0.0.199/24, gw 10.0.0.138
SSH enabled:
Login: user pine, password pine; use sudo to get root
To do:
Fix known issues 
- please use github issues for that.
Updates:
19/12/2017 - Released kernel 4.14.7 into repository, update via Apt and reboot
22/11/2017 - Released kernel 4.14.1 into repository, update via Apt and reboot
28/10/2017 - Released kernel 4.13.10 into repository, update via Apt and reboot
15/10/2017 - Released Docker-ce 17.09, update via Apt
15/10/2017 - Released new base image (*not required* to update, just rollup of kernel+base pkgs)
15/10/2017 - Released kernel 4.13.6 into repository, update via Apt and reboot
27/08/2017 - Released kernel 4.13.0-rc6 into repository, update via Apt and reboot (nothing else required)
28/08/2017 - Released kernel 4.13.0-rc7 into repository, update via Apt and reboot (rc5 should be autoremove-able)
28/08/2017 - Released Docker-ce 17.07.0-ce-rc4, update via Apt
30/08/2017 - Released Docker-ce 17.07-ce (final), update via Apt
|
|
|
|
| Wifi |
|
Posted by: dsmart978 - 08-15-2017, 12:55 PM - Forum: Android on Rock64
- No Replies
|
|
Received my Rock64 in the mail today. Didn't buy a USB wifi dongle. I want to run Android. Is there a specific USB dongle I should buy?
|
|
|
|
Serial Console for the Rock64 |
|
Posted by: MarkHaysHarris777 - 08-15-2017, 11:55 AM - Forum: General Discussion on ROCK64
- Replies (33)
|
|
Greetings;
The purpose of writing this tutorial is to provide guidance for using a serial ttl to usb bridge cable to connect the Rock64's uart (on the PI-2 bus) to a usb port on your PC or Mac, for the purpose of monitoring the boot-up process and logon from a serial terminal.
Please see this reference link:
It is important to select a bridge cable that supports at least 1.5M baud (default for Rock64 serial uart) and which has 3v3 logic ( measure the votage on the Tx pin must be no more than 3v3 !).
Most 3v3 cp2102, pl2303hx, and some ch340g chips will work.
The uart pins on the Rock64 PI-2 bus are in the same places as the RPi -- pin(6 gnd), pin(8 Tx), and pin(10 Rx). The Tx pin of the ttl adapter goes to the Rx pin of the Rock64(10) Tx-->Rx; and the Rx pin of the ttl adapter goes to the Tx pin of the Rock64(8) Rx-->Tx. Connect the ground(s) together; it is important that the ground leads are not left open. DO NOT connect the red voltage wires anywhere.
The usb end of the ttl to usb bridge cable plugs into a usb port on your PC or Mac. Terminal software (like minicom, screen, cu, or putty) is then used on the PC or Mac to connect to the appropriate usb device. The baud terminal settings are 1500000 8n1.
With the serial console running you can monitor the boot-up messages on the Rock64 (or other SBC) and get diagnostic clues (if things aren't working properly) or in the case of certain procedures (like writing to the eMMC on the Rock64) you can interrupt the uboot three second timer with the serial console.
Please check out this link too, for using the PineA64 (or other SBC) as a serial console monitor:
|
|
|
|
|
