whenever i try to use scp to transfer a large file this happens:

sftp> put configs_all.tar.gz
Uploading configs_all.tar.gz to /home/rock64/configs_all.tar.gz
Failed to set the permissions or timestamp on the destination file: The operation was aborted because the channel closed. 
The sftp operation was aborted.

does not happen with small files

tried restarting sshd 
service sshd restart

but get same error

Here's a 3D printable case I made for the H64.  It's not perfect but it works.
Free for anyone to use/modify/distribute.

  PinerH64Case.zip (Size: 34.05 KB / Downloads: 667)
   
   

Does RockPro64 support UHS speed?
It seems that not many SBC have support the high speed SD bus due to the lower voltage requirement requires extra hardware to detect the type of card to switch to lower voltage and directly using lower voltage will breaking backward compatibility.

However, for a competent hardware like RockPro64 (2Ghz CPU, PCI-E, etc.), not having a fast SD card bus seems a bit of shame.

 Yesterday I installed bionic Linux 0.6.31 from ayufan, then I installed the desktop mate, I tried to play the video and noticed that it is possible to watch the video with hardware acceleration only through the rkmpv, but it works only in fullscreen mode and it is impossible to roll it into the window. Are there any plans for further work to improve video playback ?

Dear Pine64 community,

We are happy to announce that as of today, we are starting to distribute Rock64 SBC.

Rock64 is now available for purchase in Canada (www.ca.diigiit.com/pine64) and will soon be available in France (www.eu.diigiit.com/pine64).

For any question or associated product you would like to see in our store, please send an email at sales@diigiit.com

So i have a problem ...

My rock is on 24/7, some weeks ago i had every day the next error when i wanted to execute a sudo command

Back in August, I reviewed a Pine A64+ 2BG board, comparing it to the Raspberry Pi 3.  For most of the hardware, the Pine A64+ was better than the Pi.  Unfortunately, when it came to software availability, the Pine A64+ was behind the curve ... way behind.  At that time, I thought that this problem would be fixed "soon".  Based on what I'm seeing here, none of the "problems" that were noted in that review have been resolved.

http://www.accs.com/p_and_p/A64/index.html

Unfortunately, there's still no distribution with a modern (4.0+) Linux kernel linked from the download site ( http://wiki.pine64.org/index.php/Pine_A6...re_Release ).  What's the holdup here?  Is there ANY release that supports the 4.0+ kernel?  I'd be willing to get it from elsewhere, but I really want something current to work with.

It appears to me that they're still waiting for the GPU driver, although there could be other issues.  Until the necessary code has been integrated into the Linux mainline, these computers will have limited usefulness.  Once the product owners can offer a current Linux solution, with repositories, this excellent hardware will be in a position to gain market share.

Is there any update on the overall software situation?

Hi all, new to the forums here. I've had a Pine64 long running with OpenHAB. Recently something happened and I needed to put it on battery power. So I pulled it off it's nice shelf, and hooked it up with battery power. No issues. However, I do have a fan that came with the case. It plugged onto one of the pin sets to provide a fan over the SOC for cooling. When on battery power, it was looking to pull too much juice, so I disconnected it.

When I was done doing what I needed on battery power, I went to put things back together. I believe I may have plugged the fan power into a wrong pin set. Upon restart I was not able to get anything of use and I heard a funny noise and saw the fan start then stop immediately. Now it seems, when I attempt plugging this Pine into any power, I just get a solid red power LED and nothing else happens. No video output plugged into HDMI, No Ethernet connectivity, and no apparent signs of life.

What I'm curious of, is it possible I've somehow blown something in the board by putting the fan into the wrong pins? Or is it possible I've somehow triggered some special boot mode I don't understand? I'm just a bit lost as to what could cause this to not show any signs of life now. 

Hoping someone here might have some insight as to how I can fully validate or knows if its just simply possible and very plausible I've fried something.

Again, my older Pine-64 board does this just fine. The Pine-64 LTS seems to have trouble. 

I'm running the latest Armbian (for the touchscreen support, which I can't get working on Ubuntu+Mate). 

Installed Chromium-browser. 

It fails every time with the sad face icon that "something went wrong" and to reload. Which just repeats the cycle. 

Any ideas as to how to get this fixed? No real error messages to speak of. If started from CLI:

On 11th August I had a mail containing a code. Can I see anywhere if the BTO order went through and the status of it? 
Following the mail it says that the order is expected to ship in June which must be this year. So should I have patience or could I find the information somewhere?