As it looks like that the Sata and USB3 combi on these boards is not going to be available soon, I was wondering what the performance is going to be if I would copy an CF or SD memory card (>= 32GB) over a USB3 Hub to an SSD HDD using the Rock64.

As a photographer I have a need to backup my memory cards on location.  There are commercial solutions, but the DIY in me wants to build it myself.

So I was thinking of a Rock64, USB3 hub (with or without external power?!), card reader and 256GB SSD. With the wish of placing an HDMI, or GPIO Display on top for menu and viewing images. Power supply over 18650 Powerbank (3A).

If this proves a working concept, a lot of photographers would be very happy.

So does anyone have experience in the performance copying USB3->USB3 of large files (25MB average) ?

Hi!
I just received my board and as I see there is some kind of solder on the bottom side under USB connectors, besides there is thin threads from this solder goes to the USB2 connector
I have not received power cord, so I can not test it, can anybody say is it normal? see pics

Trying to get my new Pine A64-LTS to boot. Flashed a MicroSD card using Etcher with the Armbian_5_38_Pine64so_Ubuntu_xenial_default_3.10.107 image. Etcher reported that the flash was successful.  When power is provided to the board (power supply from Pine), the green power light turns on, and a few seconds later one of the blue LED's starts flashing. The green light on the Network port comes on, and stays on, and I get periodic flashes of the yellow light on the port. That is a far as it gets. I don't see it showing up in the network connections on my router, so no IP address, so can't ssh in.

Any Suggestions?

Thanks for your time.

William.

I've tried both the 64 and 32 bit versions, internal and external network adaptors.  I can get an IP address, but I can't reach anything.  Nothing can reach the rock64, and the rock64 cant reach anything.  I can't even ping the router.

help?

root@rock64:~# cat /etc/os-release 
PRETTY_NAME="Debian GNU/Linux 9 (stretch)"
NAME="Debian GNU/Linux"
VERSION_ID="9"
VERSION="9 (stretch)"
ID=debian
HOME_URL="https://www.debian.org/"
SUPPORT_URL="https://www.debian.org/support"
BUG_REPORT_URL="https://bugs.debian.org/"
root@rock64:~# uname -a
Linux rock64 4.4.77-rockchip-ayufan-136 #1 SMP Thu Oct 12 09:14:48 UTC 2017 aarch64 GNU/Linux
root@rock64:~# 

getting these errors on the console on a periodic basis:

root@rock64:~# bash
root@rock64:~# [  354.386841] mmc0: switch to bus width 8 failed
[  354.401069] mmc0: mmc_select_hs200 failed, error -110
[  354.401897] mmc0: error -110 whilst initialising MMC card

found url's that are related:

https://patchwork.kernel.org/patch/9161131/
https://github.com/raspberrypi/linux/issues/280

using toshiba brand microssd

R64.GPIO aims to re-implement RPi.GPIO for the Rock64, with the goal of 100% code compatibility with the original Raspberry Pi module.

The following functions are currently implemented and working:

• GPIO.setmode()
  
• GPIO.setwarnings()
  
• GPIO.setup()
  
• GPIO.output()
  
• GPIO.input()
  
• GPIO.cleanup()
  
• GPIO.PWM() (start, stop, ChangeFrequency, ChangeDutyCycle)
  
• GPIO.wait_for_edge()
  

• Interrupts (GPIO.event_detect)
  

• Download the entire "R64" folder from the repo, then place the "R64" folder in the same directory as the Python script you're working on.
  
• Within your script, substitute the normal "import RPi.GPIO as GPIO" line for "import R64.GPIO as GPIO". Syntax for implemented functions should be identical to RPi.GPIO.
  

• ROCK numbering is the default. I've created a reference spreadsheet of Rock64 pins, their functions, and their GPIO numbers, which you can find here: https://github.com/Leapo/Rock64-R64.GPIO...rence.xlsx
  
• BOARD numbering works exactly like it does in RPi.GPIO. Simply input a pin number, and the correct ROCK GPIO will be selected for you.
  
• BCM numbering attempts to emulate the physical layout of the Pi. This isn't perfect (some pins had to be mapped to the P5 header, can't use some pins with MicroSD, etc.), but I figured someone might find it useful.
  

I have been working with the incredibly talented NachoParker to get NextcloudPi running on a Rock64 Board.

I am happy to say I have succeeded!

I am using the March 26th nightly version of Armbian Stretch for the Rock64. This is a testing version of Armbian so there may be some time before it's "stable".

I used Nacho's command line install script to install all the bits and pieces for NextcloudPi. So far, it's working well. Still need to do some testing and validate all the various functions are working properly.

I'll keep working with Nacho to get his going. I plan on putting together a tutorial once I have someting viable.


Sent from my iPad using Tapatalk

Hi all!

I've just got a Rock64, burned the official image (minimal Debian), connected to the monitor and the keyboard, launched it and... realized I need an internet connection. For this I can use a laptop (Debian again) connected via WiFi, which has one Ethernet port free. I've got some general descriptions about bridging and routing in Linux having WiFi but nothing worked so far. Say, I have a difficulty to connect to the Ethernet port of the WiFi access point. I believe it's quite a common case. Could someone, please, help me and provide a real case example solving such problem?

Hello all.
I am testing out the Rock64 4gb. I've installed the community Ubuntu Mate and Debian, and in both none of my Wifi dongles work.
I've found a lot of threads about this, but don't seem to find a solution.
I've got 4 dongles, none work. Here is what I get from 2 simular ones that I want to use.

With lsusb it finds the dongles:
Bus 004 Device 004: ID 148f:5370 Ralink Technology, Corp. RT5370 Wireless Adapter
Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 002: ID 148f:5370 Ralink Technology, Corp. RT5370 Wireless Adapter

This is what I get with lsusb -t

/:  Bus 05.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 5000M
/:  Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 480M
    |__ Port 1: Dev 6, If 0, Class=Vendor Specific Class, Driver=, 480M
/:  Bus 03.Port 1: Dev 1, Class=root_hub, Driver=ohci-platform/1p, 12M
/:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ehci-platform/1p, 480M
    |__ Port 1: Dev 2, If 0, Class=Vendor Specific Class, Driver=, 480M
/:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=dwc2/1p, 480M
    |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
    |__ Port 1: Dev 2, If 1, Class=Human Interface Device, Driver=usbhid, 12M

I downloaded this, but I have troubles getting it to work.
https://github.com/blahah/ralink_RT5370_linux_driver

I followed the instructions in the readme file. But when I do make, I get this message at the end.
  LD [M]  /home/rock64/Desktop/ralink_RT5370_linux_driver-master/ralink_RT5370_linux_driver-master/os/linux/rt5572sta.o
  Building modules, stage 2.
  MODPOST 1 modules
  CC      /home/rock64/Desktop/ralink_RT5370_linux_driver-master/ralink_RT5370_linux_driver-master/os/linux/rt5572sta.mod.o
  LD [M]  /home/rock64/Desktop/ralink_RT5370_linux_driver-master/ralink_RT5370_linux_driver-master/os/linux/rt5572sta.ko
make[1]: Leaving directory '/usr/src/linux-headers-4.4.77-rockchip-ayufan-136'
cp -f /home/rock64/Desktop/ralink_RT5370_linux_driver-master/ralink_RT5370_linux_driver-master/os/linux/rt5572sta.ko /tftpboot
cp: cannot create regular file '/tftpboot': Permission denied
Makefile:388: recipe for target 'LINUX' failed
make: *** [LINUX] Error 1

Can someone please help me. I've been at it for a few days now. I'm no Linux master, so I don't know what I'm doing.
Thank you.
NicoD

sudo apt-get upgrade更新已安装的包 

sudo apt-get dist-upgrade升级系统 

会出现这样的错误。

每时每刻