Hi,
I just receive my first rock64. I installed xenial mate, all works fine.
There is a possibility to install openvc on rock64?
if it is possible can you help me to find the right way?
Thanks
Roberto

Hello all,

I plan to setup a new low cost backupserver which also should work as a NAS.
The external HDD for the backups should be completely encrypted with LUKS.

At the moment, I am doing my backups with a Raspberry Pi 3 with an USB HDD on OpenmediaVault with UrBackup.

Unfortunately, the transfer speeds are super slow (about 10MB/s) and I need a couple of days for a Full Backup (about 5TB of Data)
and I wanna speedup that.

I already looked thru the SBC Models and kept my eyes onto the PineH64 and the RockPro64.
Especially the option to upgrade with a (Mini) PCIE to 4x SATA Adapter, and the encryption
extensions in the processor are very interesting to me.

Now my question is, can you recommend the PineH64 or the RockPro64? for the job?
Did anybody already tested the LUKS and Ethernet Performance of a PineH64 / RockPro64?
Dont understand me wrong, I dont want super high speeds here and I know that SBC's are limited in their performance.

What I am imagine is an increase to about 40MB/s of total write speed via Gigabit Ethernet onto an USB3 or SATA HDD which is luks encrypted.

Is that possible with a PineH64 or a RockPro64? Or should i better use another SBC or a low power Intel/AMD PC for the Job?

Thanx in advance.

Regards

Hi,

I recently got a Rock 64 board, working fine with a Micro SD card (tested with DietPi and Debian stretch lite... No issues detected at this time !)

The problem occurs when I try to boot from the emmc module : I bought with the Rock 64 a 16G emmc Module and the USB adapter. I download the Pine64Installer to flash the emmc module with the USB adapter (debian stretch lite in the first test). No problem. Then, I install the emmc module on the Rock64, remove the micro SD and connect the power supply. It seems it cannot properly boot. I've got many error messages (I can't read anything !) and finally, get a nice : 
"end Kernel panic - not syncing : Attempted to kill init!"

I thought that something was wrong in the flash process, so I tried again : same error.

I try flashing another linux (dietPi, this image works fine on micro SD) : same error.

I can access the 2 partitions created with pine64 installer (mounted from /dev/sdb6 and /dev/sdb7.... why ? I don't know)

I tried to use a simple dd command to flash again an os on the emmc module : the process gives me the same result (the 2 same partitions) but the "kernel panic" is still there !

Is there something I forgot in the process ? Any idea to resolve this ?

Thanks in advance

Yoh

私は、タイムスタンプを修正することでコンパイルができましたが、
新たな問題が発生しました。
｢make install｣を実行しましたが、
/bin/bash ./arch/arm64/boot/install.sh 4.13.0 \
arch/arm64/boot/installsh 4.13.0\
run-parts: executing /etx/kernel/postinst.d/apt-auto-removal 4.13.0 /boot/vmlinuz-4.13.0
run-parts: executing /etc/kernel/postinst.d/initramfs-tools 4.13.0 /boot/vmlinuz-4.13.0
update-initramfs: Ganerating /boot/iniitrd.img-4.13.0
Warning: root device  does not exist
Using DTB: rk3328-rock64.dtb
Couldn't find DTB rk3328-rock64.dtb in /usr/lib/linux-image-4.13.0 or /etc/flash-kernel/dtbs
run-parts: /etc/initramfs/post-update.d//flash-kernel exited with return code 1
run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
arch/arm64/boot/Makefile:40: recipe for target 'install' failed
make[1]: *** [install] Error 1
arch/arm64/Makefile:124: recipe for target 'install' failed
make: *** [install] Error 2
と表示されてしまいました。
どうすればよいのですか?

Google Translate : 
I could compile by modifying the timestamp,
A new problem has occurred.
I run "make install"
/bin/bash ./arch/arm64/boot/install.sh 4.13.0 \
arch/arm64/boot/installsh 4.13.0\
run-parts: executing /etx/kernel/postinst.d/apt-auto-removal 4.13.0 /boot/vmlinuz-4.13.0
run-parts: executing /etc/kernel/postinst.d/initramfs-tools 4.13.0 /boot/vmlinuz-4.13.0
update-initramfs: Ganerating /boot/iniitrd.img-4.13.0
Warning: root device  does not exist
Using DTB: rk3328-rock64.dtb
Couldn't find DTB rk3328-rock64.dtb in /usr/lib/linux-image-4.13.0 or /etc/flash-kernel/dtbs
run-parts: /etc/initramfs/post-update.d//flash-kernel exited with return code 1
run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
arch/arm64/boot/Makefile:40: recipe for target 'install' failed
make[1]: *** [install] Error 1
arch/arm64/Makefile:124: recipe for target 'install' failed
make: *** [install] Error 2
And it was displayed.
What should I do?

New to ARM, but... looking over these images, a lot of them having FAT32, etc.

But none of the disk images have a partition marked bootable. (as in DOS MBR).

I know big RISCs do no use that carry over from DOS to x86/x64 unix.

How, does the ARM boot process work, in the absence of an MBR?

I have not received  a Rock64 board yet, I will be receiving a clusterboard probably sooner...

In the meantime, while awaiting the actual hardware, I have been trying to set up a dev environment, as well as emulators to test with.

In the longer term, too me, that is a better way to go rather than continually burning untested code to see if it works.

So, I pulled some images, been digging around, but really nothing current with Rock64 or Sopine emulation successfully (others, but have found none for the images in this sight)...

Has anyone using some of these images been successful loading these images in qemu-system-aarch, and booting them?

Seen talk, but even juggling around with the images, as well as command line switches to qemu. I have so far been unsuccessful.

Maybe I am missing something here.

Does anyone have anything to offer?

Hello, i bought a week ago a rock64 4g and about a month ago the hdd im using with it, and im having random crashes and they are getting me crazy, im not sure if they are because of the hdd, the rock64, the psu or what, its runing on a 16mb SD card sandisk ultra (i dont need a bigger SD since im using it as NAS). i tried everything i can imagine and im still having random crashes, im not a very advanced user, but im also not a total noob, its runing actually on the ayufan img omv over jessie arm64 0.5.15, with ssh open when the crash happens i get:

I'm looking to drive this resolution but nothing I've done so far - in any of the distros - has been able to support this resolution.  Currently I'm trying to configure DietPi manually but I just get a blank screen;  DietPi (with LXDE) also fails to return the image if it blanks due to screen timeout (which I also can't change properly).  I've tried all of the major offerings that I can find but nothing seems to work properly.


It seems so far that unless you're equipped to run 1920x1080, 1280x720, 800x600 or 720x480 you're not going to get anywhere;  is this some kind of hardware and/or screen driver issue with the Rock64's chipset?

The lxrandr program permits only these resolutions (auto seems to default to 1920x1080 which my video system squashes to display).   For reference I tried driving a Pi via this monitor (with its HDMI <> VGA adaptor) and it works ok;  I've run other HDMI outputs through this config as well (PC) and they displayed without issue.

Text display is also distorted, I think the system is desperately trying to output 1920x1080 and my adaptor is trying to compensate.   I've tried some of the manual modifications for text but desktop GUI configuration still eludes me.

Any advice or recommendations would be greatly appreciated.

Does Hyperion work with the rock64?
https://hyperion-project.org/
It's mostly used for creating your own ambilight and can be used with libreelec/kodi etc for watching movies and stuff.
It's working fine with the RPi, and since the rock GPIO Pins are supposed to be the same, it should work as well... but dunno...

I asked Raybuntu, but he does not use it..
maybe any one did try it?

What size and what brand eMMC is compatible with the ROCK64?