I have a Rock64 with the CSR8510 USB Bluetooth adapter in the USB 2 or USB 3 port. In every case, the adapter is not recognized by Linux/Lakka/Retroarch.  My usb keyboard is working fine but I cannot get this adapter to work whatsoever in Linux/Lakka/Retroarch with the latest version installed.  

The adapter is not recognized by a bluetooth joypad, a bt headphone, a bt mouse, nor a bluetooth keyboard .... none of these pick it up.  

Does anyone know how to successfully enable the bluetooth adapter sold in the Pine64 store for the Rock64??

Does anyone have a clean solution for how to increase the size of the /boot partition on a Ubuntu Mate SD based image?

Issue: I'm trying to install updates and the free 35M (out of 50M) volume is insufficient for the requested 150M of space that Updater wants.

I have plenty of room on my SD card. However, unless I'm mistaken, /boot must be contiguous. Since Gparted will only work on non-mounted volumes...

I'm running into issues with an Ubuntu VirtualBox image mounting my SD card via USB adapter. And the USB based live Ubuntu image is not happy booting with my video configuration. So, I'm being thwarted from being able to manipulate the partitions on an alternate Linux platform.

Also, does anyone know if mmcblk0p1 must be located in a specific offset on the SD card? If I have read correctly, Pint64 support MBR type partition tables and should be somewhat flexible?

Hello,
I am looking for help with setting the Pine64 LTS upper USB port as a USB Device(serial port)

My setup:
Pine64 LTS
Armbian_5.38_Pine64so_Ubuntu_xenial_default_3.10.107( I have also tried Armbian_5.35_Pine64so_Ubuntu_xenial_default_3.10.105 with the same results)
Original kernel configuration: Original kernel configuration
My current configuration: My current configuration
Kernel sources I use are form armbian package linux-source-default-pine64_5.38_all.deb and contain git versioning information with remote repository at https://github.com/ayufan-pine64/linux-pine64

What I tried:
Rebooting without SD card into FEL mode to see if Pine will be enumerated on my PC, this works ok, so the actual connection works and the USB port on the Pine I picked is the correct one.

Armbian seem to be lacking the g_serial driver, so I recompiled the kernel with gadget support + g_serial module.
From what I understand https://www.kernel.org/doc/Documentation...serial.txt, doing :

I tried openmediavault arm64 and armhf, from the SD card and from MMC, and got really weird issues.  armhf had graphical corruption issues. arm64 would throw some SIP error every time a key was typed or a button was clicked. Neither OMV could get an IP (according to the prompt, anyway)

Android found the ethernet and got an IP, but won't travel outside the network. (I cant ping anything or load a page.) Armbian seems to be the only thing that works on this so far.

images here: https://imgur.com/a/QC7kvWM

The ROCK64 stock version Android Oreo ver 8,1 for microSD boot just released and here is the PINE64 wiki site download link: http://wiki.pine64.org/index.php/ROCK64_...ndroid_8.x

Here is the ROCK64 stock version Android Oreo ver 8,1 for eMMC boot download link: http://wiki.pine64.org/index.php/ROCK64_...d_8.x_eMMC

The ROCK64 Android Oreo ver8.1 SDK currently unloading to file server. However, this is a 67GB file and will takes some time on file uploading.

I am trying to move my NAS from a RPi2 to a ROCK64 (4GB).  Everything is working except I can't get the drives to mount at startup.  In the RPi version, it was done by adding the drive info to the fstab file.  When I do that on the ROCK64, it hangs during boot.  I can mount them manually on the command line via Putty on my Windows 10 Desktop.  After they are mounted, everything is working well, but if something causes the ROCK64 to reboot, I can't see the drives on the LAN until I mount them.  I wrote a script to mount the four drives with one command line, but I would like to have them mount automatically at startup.  I am running stretch-mate-rock64-0.5.15-136-20171222-arm64.

So I imagine the greatest interest in this SBC is the PCIe slot, so what have people used that slot for yet?
Are there any good drivers out there in the ARM world yet that people who aren't pro Linux programmers and kernel compilers can use?
I personally have plenty of small ARM boards and still need to make full use of my Rock64 board,
While I would like to have a newer CPU and GPU, all I would use it for is a glorified small form factor Linux desktop computer.
Is there anything that PCIe slot can do that would make it worthwhile the $80?
I would like to slap a affordable Nvidia GPU in that slot, is there any ARM based Linux that could drive it as a display adapter? Has anyone ran the Nouveau driver under an ARM environment before?

Thanks for any help,
MobileJAD.

How to clean the card emmc?

Hi everyone,

The Rock64Pro looks like it would make for a perfect home made nbase-t usb3 adapter, assuming that the type-c port can operate in peripheral superspeed mode. Some parts of the website indicate that the type-c port has otg support in which case I think it would be the Rock64pro would be able to behave as usb device for another computer. Also it is unclear whether the usb-c port operates in superspeed mode as either a host or a peripheral. Can someone confirm that it will behave as a superspeed peripheral?

Assuming that it can act as a superspeed type-c peripheral, then it may be possible to install an 10Gbe ethernet card into the x4 slot and turn the whole thing into a 10Gbe type-c ethernet adapter. 

Does anyone see any obvious obstacles to this idea?

Thanks

Hi,

I have just received my new ROCK64 2G, I burned the Debian on the SD card and it succeeded. But when I put the SD card into it, nothing happened. The STBY LED, PWR LED, IR LED lighted up but when I plugged it with the TV screen through HDMI, the TV screen didn't show up anything.

Is my ROCK64 dead or are the anything I need to config? Or are there any ways I can check for the life of my ROCK64?

Thank you