Hi,

I have the problem with file transfer speed with my Rock64 (4Gig ram with Pine 64 power adapter). Rock64 connected to Gigabit router port. 

From Windows Surface Book pro3 PC (connected to AC wifi) to Rock64 external USB 3.0 HDD: Only get: 10- 16 MB/s.

Back from Rock64 to Surface Book pro3 PC ONLY : 12-19 MB/s

Sent multiple email to Pine64 website and No single reply. Such a terrible company, will never buy Pine64 product anymore.

I have tried all version of OMV from ayufan, pine64 website, pre-release or stable version. Check my USB3 to SSD adapter and was confirmed with UAS support.

root@rock64:~# lsusb -t

/:  Bus 05.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 5000M

    |__ Port 1: Dev 2, If 0, Class=Mass Storage, Driver=uas, 5000M

/:  Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 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

/:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=dwc2/1p, 480M

root@rock64:~# lsusb -v -d 152d:1561 | grep -i interface

  bDeviceClass            0 (Defined at Interface level)

    bNumInterfaces          1

    Interface Descriptor:

      bInterfaceNumber        0

      bInterfaceClass         8 Mass Storage

      bInterfaceSubClass      6 SCSI

      bInterfaceProtocol     80 Bulk-Only

      iInterface              0

    Interface Descriptor:

      bInterfaceNumber        0

      bInterfaceClass         8 Mass Storage

      bInterfaceSubClass      6 SCSI

      bInterfaceProtocol     98

      iInterface              0

I have no Idea how to fix this, what is going on? ?( 

Thankful for all Ideas!

As a long time developer i recently bought a Rockpro64 for a totally unrelated development that i am working on but over the years have developed my own embedded Media OS along the lines of the original OpenELEC and more current LibreELEC or CoreELEC and am interested in moving them off the Amlogic platform over to the Rk3399 SoC and am curious as to what the general consensus with regards to the emerging SBC scene is when it comes to a fuller embedded linux system as compared to something like LibreELEC thats really more of a Kodi driven development.

Over the years i have become well aware of the issues with the newer Mali based GPU's and the lack of a real working graphics stack that actually makes use of the advantages of the Mali's being used and a few years ago a couple of us RE'd our own solution and created blobs to use with newer kernels then typically supported by the Manufactures BSP's being provided, so i understand most of the issues currently trying to be solved both privately and publicly.

Currently i am working on a Debian version with kernel 5 support as it need it for my other project but am just curious as to what peoples thoughts are as to just fixing the graphics issues in Debian and then running Kodi properly built for that as compared to splitting my time and trying to support the Media box scene. I realize that people working on Android boxes would naturally prefer something like LibreELEC but i am more interested in what people moving into the SBC scene would think is better. 

sorry if i step on someones toes but i am not in any way interested in anything to do with Anroid tho.

thanx and i look forward to seeing what peoples thoughts are.

also as a hardware guy i must say i am extremely impressed with the rockpro64 and its capabilities as compared to a few of the other boards i have looked at.

I am recently buy a rock64 board, when search using google, I found  ayufan repo, so I download the SD card image from release link below: 
https://github.com/ayufan-rock64/linux-b.../tag/0.7.9 , such as stretch-minimal-rock64-0.7.9-1067-arm64.img.xz

[url=https://github.com/ayufan-rock64/linux-build/releases/download/0.7.9/stretch-minimal-rock64-0.7.9-1067-arm64.img.xz][/url]the rock64 can start normal and into the linux system.

But when I changed some config in kernel, what is the step to create a SD image base on some components like: u-boot.img, boot.img, and buildroot rootfs.ex4.

Thanks a lot.

Hi,

I have been using a Raspberry Pi and lately a Banana Pi as a NAS. The throughput of these devices is really slow (3-4 MB/s for Raspberry Pi and 8-10 MB/s for Banana Pi). I have been looking for an alternative with USB 3.0 for several years and last year I finally found ROCK64 and I'm really happy that I bought it. 

Since I'm always connected to my NAS through a 802.11b Wifi network my bandwidth is limited by the network and not by the ROCK64. I have a throughput of 20 MB/s over Wifi which is perfect for my needs.

To help others to get started with using ROCK64 as a NAS I wrote a guide here:

https://midstar.home.blog/

Best Regards,
Joel

Hi, so I am thinking of getting a RockPro for my projects. Looks nice by specs and most importantly it looks like it supports android. So here is my question. How well does it work with it? I am thinking of doing a car media center and I wouldn't like if it would lag badly like raspberry does. Not much information on how it performs. Atleast not that I know of. So maybe someone could give me some info? How well does it perform?

Thanks and best regards!

I finally got around to putting together my RockPro64 and the NAS case.

I have the PIne64 power supply (12V/5A) as well as 2 8TB Seagate Ironwolf NAS drives.

When I booted from Armbian, NextcloudPI, and Ayufan's OMV image on an EMMC card, all is fine.

Once I added the 2 Drives, nothing...

Reimaged the EMMC and tried with 1 Drive, nothing...

Reimaged the EMMC again and tried with a WD 4TB Red NAS drive, nothing...

Reimaged again and tried with just the EMMC card and all is fine.

Guessing the Hard Drives I have are drawing too much power for the stock Pine64 power supply. Is it possible to put in a higher amp power supply? Maybe 6 or 7 amps?

Thoughts or suggestions?

Thanks!


Sent from my iPad using Tapatalk

Does anyone know the status of Parrot Linux on the Pinebooks? 

From the Parrot side many moons ago I asked their forums when I saw an announcement about a port in the press, and at the time was told there were issues with binary blobs.  Today the "other builds" downloads area has a Pine 64 ARM link
but the README.txt file there says only "Pine64 images are not yet available. We hope to release them as soon as possible."

Thanks,
rcs

hi,
I'm trying to build a rock 64 nas with a 1tb hdd to upgrade from my raspberry pi nas that topped out at 11 MB/s.
I have installed OMV multiple times and followed tutorials. Everything seems to work. I can mount the network drive however what happened is that when I would write files to it it would start at 11 MB/s and slowly tail off to zero then windows gives me a network error and i have to restart the rock 64. I've tried everything. Bought a new usb 3 adaptor, installed various flavours of linux and used samba instead but the same error. ive tried disabling the uas driver all to no avail. It seems to be able to write some data but seems to get stuck on larger files.
Any ideas?
Thanks, George

When will ROCK64 follow up?

https://androidtvbox.eu/new-firmware-a5x...-20181128/

Hey,
like how I ask in my previous post : https://forum.pine64.org/showthread.php?tid=7125 - I have connected the RP64 to an molex +12 Volt cable of my 600W ATX PSU - Its working without any pci-e card, booting up etc as expected.

If I test the voltage, my half working diagnostic tool say its arriving 13-14 Volt ... (is this normal? not 12v??) - I cant check the current (amp) but how I understand there should be enough amps, in the internet somebodys say its can be 12A depending on how many devices connected, so I have no other devices on that 600W PSU.

I try just with ayufans image : stretch-openmediavault-rockpro64-0.7.14-1081-armhf.img.xz

The SATA PCI-E Card which I bought:

• Chipset: ASMedia1061 x 4
  
• Ports: 8 SATA 6GB/s Ports
  
• Compliant with PCI-E Specification V2.0 and backward compatible with PCI-E 1.X
  
• Supports Native Command Queuing (NCQ)
  
• Compatible with SATA 6G, 3G and 1.5G Hard drives
  
• Compliant with PCI-E Specification v2.0 and backward compatible with PCI-E v1.x