I'm thinking of using the Rock64 as a cheap NAS and backup device. I'll attach a dual enclosure USB3.0 bay. The bottleneck will be elsewhere but does the USB controller support UASP?

I bought a Rock64 4GB and an eMMC.

I am unable to boot the board.

I have tried booting the the board repeatedly using the eMMC and 3 different SD cards (and I have tried removing the eMMC and putting the switch on)
I have downloaded every image both hf and 64 bit, some several times. I have tried burning the SD and eMMC in different ways - using your PINE installer, etcher, disk manager, I have used linux and windows to do this. I have checked MD5s for downloaded files where available (community downloads seem to be missing these)

I have encountered three outcomes:

1. Android boots and I can interact for maybe 20 seconds before the screen freezes I can't actually do anything in that time.
   
2. Linux boots and then throws an kernel exception dumping stack trace, sometimes I can ctrl-alt-del to reboot to the same, sometimes I can't. I can only ever do that once.
   
3. The 3 lights come on and nothing else happens.
   

Hello.

I am having issue with one distro so it was suggesting I use the serial console to access to see if the distro was booting correctly.

While I see the distro properly booting, but when I try to log in I am not getting any response when I try to type in.

I am using a Prolific PL2303TA based cable with the following pins

Black cable-----GND
Green cable-----TXD
White cable-----RXD
Red cable -------VCC

I have Green connected to pin 8, White connected to pin 7, and Black connected to pin 6

Any ideas on why there is no input?

Thanks!

Hi, Im sorry to ask a basic question but the androidtool keeps saying download boot fail and idb preparation fail when i try to flash any image. How can i fix this? Thanks in advance

Hi,

I have Windows 10 IOT running on my Pine64 2Gb. Everything looks OK. I can manage it via SSH and also via the device portal (port 8080).
I have keyboard, mouse, internet, and Bluetooth.
I even have a small .Net Core "Hello World" app running on it (!).
But the problem is after about a day, I see an animated gearbox and the system is dead. Has nothing to do with the .Net Core app. It looks like a memory leak in the system. Anybody has the same problem and/or knows a solution?

Hugo

1. Download the latest image (http://wiki.pine64.org/index.php/Pine_A6...T_Releases) and burn it on an SD-Card. This sounds easy but it is not. You have to convert a ffu file to a disk image. The python script I tried did no work. I succeeded with the IOT Dashboard on a Win10 laptop. In my case it ended after 99% with an error (could not write blabla..) and a Windows popup that I have to format this disk. Do not do that. Just pull the SD-Card out.
   
2. Plug the SD-Card into your Pine64. Make sure it is connected to the local network and you have a DHCP server running. Apply power and wait for 5 minutes. You can see by the LED near the UTP connection that it is doing something.
   
3. I had a HDMI monitor attached and a Logitech wireless keyboard/mouse plugged in in the lower USB. A language select menu was displayed on the screen, but the keyboard was not recognized. After half a minute the default language is selected and an overview is displayed. For me it displayed two IP addresses but no connected devices.
   
4. Now you can connect to your Pine64 via SSH with the regular IP address (not the kernel debug one). Username/password is [email=Administrator/p@ssw0rd]Administrator/p@ssw0rd[/email] You can also inspect your system via the portal http://<YourPine64IP>:8080 with the same username/password.
   
5. I connected a USB switch to the lower USB and attached the keyboard and a usb memory stick to the switch. I tried several keyboards but they did not work. I attached an old cheap Sweex BlueTooth adapter to the switch and to my surprise I could see in the portal that it was working. And now also the Logitech keyboard was working and the USB stick was recognized as D: drive. And they were all diplayed in the overview under connected devices. I doubt whether this has something to do with plugging in the BlueTooth adapter.
   
6. You can mount your Pine64 on a PC with \\<YourPine64IP>\C$ Reading is fast, but writing is very slow (or does not work at all). This also hits you when you try to deploy and debug your App with VisualStudio.
   
7. In general SSH is working best. E.g. if you enter D: you are swapped to the D: drive. In the commandline of the Pine64 itself this does not work. Also the disk size is not reported correctly.
   
8. Do not forget to turn off the Kernel debugging as mentioned on the Pine64 site.
   

1. Install the DotNetCore 2.0 SDK on your PC.
   
2. Follow the instructions from https://www.hackster.io/Ra5tko/running-n...arm-0bb717. Instead of the pi calculation I did a simple hello world.
   
3. Use win-arm in <RuntimeIdentifiers> and publish for this identifier. Do not use win-arm64. I spend a lot of time on this. It looks like this Pine64 IOT build is 32 bit. (Which is not that bad, because now you can use Raspberry PI examples). Run the .exe from the commandline/SSH. I used a self-contained package instead of copying this preview release to Sytem32 on the Pine64.
   
4. I transferred files to my Pine64 with a USB stick, because writing via the network is too slow.
   

Hello everybody,
my pinebook finally arrived.
I was surpirsed to see that it booted straight into Ubuntu(?) Mate, but I had ordered the 64GB eMMC, and have installed it already, so I will need to re-install I think.
I am right now in the process of flashing Xenial Mate for eMMC to a microSD card I borrowed from my phone.
I hope I'm understanding this correctly:
- pinebook cannot boot from USB
- i need to create an installer on a microSD to install the OS to the internal eMMC
???
I hope this will succeed.

I have been using Linux for a long time now, but have zero experience with SBCs!
What options do I have to install a GNU/Linux based (not Android) operating system to my pinebook, with maximum configurability the way I'm used to building up my own minimal desktop from a barebones install?
Why are the images divided in sdcard and eMMC images?
Can I install all pine64 operating systems, or does it have to be specifically for the pinebook?

Can't I install a "normal" ARM Linux to the eMMC, just like to a hard drive?
How is the update process? A quick glance at the forums here gives me the impression that it is different from a normal Linux distro's package managament?

PS:
the Ubuntu(?) Mate the pinebook came preinstalled with works well enough, but I noticed straightaway that media playback is abysmal: (s)mplayer complains that "This device is too slow!" - and playback is indeed very choppy (a h264 encoded 720p full length movie), the video is some sort of hardware overlay on top of all other windows.
Is this an older version of the operating system, will the version provided by the pine64 installer (xenial mate 0.6.2-77 for eMMC) bring some improvement?

Thanks for reading this far.

Cheers,

d.

My router DHCP server is unable to assign a fixed IP address to Rock 64 running ayufan's Debian Jessie because the MAC address keeps changing after every reboot. 

In the file /etc/network/interfaces.d/eth0 , I tried to add a line "hwaddress ether 00:11:22:33:44:55"  after "iface eth0 inet dhcp" line, rebooted the Rock, but it has no effect.

I really need this fixed IP address assignment using the router DHCP to do port forwarding, etc. can any kind soul please help me?

Thanks in advance

Update: Using "dmesg | tail" command, I found some errors. It looks like something is broken here.

[   16.107739] systemd-journald[284]: Received request to flush runtime journal from PID 1
[   16.677610] rk_gmac-dwmac ff540000.eth: rk_get_eth_addr: rk_vendor_read eth mac address failed (6)
[   16.684179] rk_gmac-dwmac ff540000.eth: rk_get_eth_addr: generate random eth mac address: 46:dc:5a:a0:be:8a
[   17.087857] rk_gmac-dwmac ff540000.eth: rk_get_eth_addr: mac address: 46:dc:5a:a0:be:8a
[   17.092156] eth0: device MAC address 46:dc:5a:a0:be:8a
[   19.975103] rk_gmac-dwmac ff550000.eth: rk_get_eth_addr: mac address: 46:dc:5a:a0:be:8a
[   19.987574] eth1: device MAC address 46:dc:5a:a0:be:8a
[   21.159028] rk_gmac-dwmac ff540000.eth eth0: Link is Up - 1Gbps/Full - flow control rx/tx
[   24.618565] tty_port_close_start: tty->count = 1 port count = 2.

This is for Rock 64 LINUX beginners who wants to migrate their Debian Jessie/Stretch minimal from the SD card to a much faster (SSD) and/or bigger drive.

Assuming  the SSD has already been connected,  partitioned,  and formatted to EXT4, here are few simple steps to follow: :

1. Label the SSD partition where the root file systems will be migrated to.

Quote:sudo e2label /dev/sda1 rootfs

Quote:sudo mount /dev/sda1 /mnt

Quote:sudo cp -avx  / /mnt 

Quote:sudo nano  /boot/efi/extlinux/extlinux.conf

Quote:label kernel-4.4
    kernel /Image
    initrd /initrd.img
    fdt /dtb
    append earlycon=uart8250,mmio32,0xff130000 rw root=LABEL=linux-root rootwait rootfstype=ext4 init=/sbin/init coherent_pool=1M

Quote:sudo lsblk -f 

OK, I mastered updating the eMMC with 16.04, but the message referenced in the subject keeps coming up after booting. From what I've discovered this is because my ISP is doing something considered lazy, or at least mildly improper with access to DNS. In any even in my searching I found instructions on editing a workaround in a file in

I just got my board today and was hoping to do some performance testing of the SPI interface. I loaded up the Linaro LXDE build and can see that it's missing /dev/spidev0.0. Is the driver disabled by default? Missing? Any help would be appreciated.