Hello dears,
Anyone solve rock64pro output sound ????

Hello everyone I'm thinking of getting a Rock64 single board computer and I'm wondering if it has any type of PCie slot (slot for external gpu) because apparently it's GPU is not that good and I'm getting the 4gb variant of the Rock64 SBC because I want to use it as a mini pc when I'm out and about so please can someone answer?
--Thanks in advance
Prox

Hi forum,

I guess this is more of a suggestion to the release manager for pine64 and less of a question.

While I appreciate the dd image format's simplicity, it would make a lot more sense to distribute images lest wastefully.

Part of the reason I mention that is because the dd image that is distributed has a corrupt partition table, so it can't be copied to an SD card via more efficient means.

I run into this problem regularly and I myself am a fan of a couple of methods:

1) the bash binary

https://www.linuxjournal.com/content/add...ll-scripts

This is more useful if you want to add obscurity (not security) to the images you distribute

2) a zip file, along with 2 bash scripts that implement *an API*

This method is a bit more complex.

script 1: flash.sh

usage: flash.sh [--device|-d <device>] [--tmpdir|-t <tempdir>]

device  - a block device e.g. a default could be /dev/mmcblk0, exported as $DEVICE
tempdir - a temporary directory e.g. see man mktemp, exported as $TMPDIR

in turn, script 1 sources script 2, and script 2 exposes a few shell functions.

script 2: details.sh

fetch(): fetches all source files to $TMPDIR specified by script1
            urls are encoded in the details.sh file
            small files (e.g. patch files) can be stored in the .zip file locally
            large files can be fetched from the internet

prepare(): applies patches
                 partitions device
                 resizes partitions as appropriate
                 a really compact and scriptable way to specify a partition layout that can fill up space to the end of the disk (so you don't need to have 8GB, 16GB, and 32GB files) is using sfdisk
                 https://linux.die.net/man/8/sfdisk
                 http://download.vikis.lt/doc/util-linux-...k.examples

flash(): could use dd, or not
            a more efficient means for Pine64 would be to distribute .ext4 files or .vfat files that can be mounted as loop devices (using losetup)

3) fastboot

This is arguably the standard way of distributing Android factory images and is described in detail at the link below

https://source.android.com/setup/build/running

4) There is always yocto too.. ¯\_(ツ)_/¯

Really, there must be a better alternative than sitting here, waiting for 26 billion zeros to be written to an sd card.


Cheers,

C

Simple way to fit fan and nvme card in open enclosure would be to make aluminum legs longer by approximately 30 mm. Would PINE consider to make those?

https://www.pine64.org/?product=pine64-a...-enclosure
https://www.pine64.org/?product=rockpro6...rface-card

So I've still been having some intermittent boot issues with my USB3 SATA drive.  Every now and then u-boot randomly gives me this result during the usb startup process:

Would somebody be so kind as to port android to rp64 from any of these tv boxes H96 Max, X99, Ebox r99, RKM M39 they all work great as tv box, all use rk3399?

Lower right hand corner is screen lock and it fails. Google said Ctrl / Alt together and then L. and still nothing, please advise.

Hey guys
Does anyone have Rock64 board with *nix 100% working?
I bought 3 boards Rock64-4G and all of them does not seem to work
One is not able to read/write eMMC (and CPU becomes very hot) - I sent it back
Two others are very unstable. I've tried ayufan's Debian Stretch, Ubuntu Bionic and DietPi
All of them crash when doing intensive I/O together with intensive CPU load. No matter eMMC or external SSD drive
I believe problem lies in poor I/O bus programming in ayufan's code
Please let me know if anyone have completely working board

Hi,

I have referred wiki (http://wiki.pine64.org/index.php/PINE_A6..._Main_Page) and interested on PINE A64-LTS as it supports Android 7.
Our yearly production will be around 2000 units.

Queries:
1. Till which year you can support us on PINE A64-LTS ?
2. Do you provide Android SDK for Android 7x to customize the same from our side ? Does it require any license for commercialization ?
3. What is the PCB size and cost (for 1K unit)
4. What are the compliance (CE/FCC/UL/RoHS etc.) you have?
5. Is it possible to provide over the air (OTA) OS upgrade for future android release ?
6. What kind of support option you have ?
7. What is the lead time to order first 100 units ?

Thanks a lot in advance!
-Biplab Kundu

Dear Pine Users,

thank you for providing the discussion group for the ROCK64 platform. I tried to use a custom compiled kernel for several days now. Unfortunately, every attempt results in a system that does not boot.

The most promising way seemed to me the following with a newly installed distribution via Etcher. I took the Ubuntu 18.4. Desktop variant. Then I have executed the following commands on-board:

-----------------
sudo dpkg-reconfigure keyboard-configuration

sudo dpkg-reconfigure tzdata

sudo apt update

sudo apt upgrade

sudo apt -y install cmake build-essential python-minimal bison flex bc libssl-dev libncurses5-dev lzop make u-boot-tools binfmt-support ninja-build libfl-dev python python2.7 swig libpython-dev flash-kernel

sudo reboot

mkdir workspace

cd workspace

git clone https://github.com/ayufan-rock64/linux-m...kernel.git

cd linux-mainline-kernel

make rockchip_linux_defconfig

make -j4

sudo make modules_install

sudo make dtbs_install

sudo make install
-----------------

After this, the platform will not reboot. I just get a black screen. The LEDs of the ROCK64 just light up a few seconds. Then only the green LED remains.

I have checked the file /boot/extlinux/extlinux.conf
If I remove the entries for the newly installed kernel, the platform boots with the old kernel again (4.4.).
By the way, why do I have /boot/extlinux/extlinux.conf and /boot/efi/extlinux/extlinux.conf?

I hope, you can give me a hint, what is missing or how I can debug this issue, since I do not see any output, also not from u-boot.

Best regards,

   Stefan May