When using my Rock64 with Gigabit link, network connections are unstable (I even cannot get the dmesg output via ssh connection), no problem when using 100Mbit.

dmesg doesn't indicate any problem (retrieved after set port to 100 MBit)
eth0: Link is Up - 1Gbps/Full - flow control rx/tx
eth0: Link is Up - 100Mbps/Full - flow control rx/tx

Did a sudo apt-get update/upgrade which updated a couple of things but issue persist

Current setup:
Rock64 
4GB 
official debian image on SD card
emmc plugged in but not used yet.
Router/Switch: Fritzbox 6360

When using the same FritzBox port (configured as Gigabit port) with my laptop, no issue is seen.

Any ideas?

Thank you
Reinhard

So straight out of the case the pinebook wouldn't show any man pages.  It would say page ?/? like it didn't have any data for anything.  

I tried loading or re-loading man-db (sudo apt install man-db) with no difference.  Even a "sudo mandb -c" looked promising with 6000+ pages added but nothing would display.  Finally a "sudo apt --reinstall install groff groff-base" fixed it.  

I was close when I tried to install nroff and troff.  I kept getting a troff failed message sometime after I did a man.  When I went into console mode it would say man ended with code 2 and nroff would be at the end of the long string of commands above it.

I guess I need to do that kernel upgrade to get rid of the flickering and flashing/tearing of the screen.  I thought apt upgrade would do that but I read somewhere here that it doesn't update boot or kernel.

Hi,

I had a few minutes last night to test out my new Rock64 with the Debian Stretch minimal (0.5.1-89).  The results were not stellar; however, I only had a few minutes to play with it and so have not dug into the situation.  To provide some brief background, I have a bunch of pine64s and RPi and so am reasonably experienced with this stuff, but I am not expert like many here.

1. I created the image on a known good card and the process was flawless.
   
2. The system booted up well and threw a filesystem error requiring an fsck.  This did not impact the initial boot and everything came up including SSH.  Nice.
   
3. I was able to login via SSH over the LAN.  Extra nice. :-)
   
4. My first step was to run "sudo apt-get update", and it failed with a "size mismatch" error.  I think that this is a known issue
   
5. I was curious that the SDcard was formatted with many more partitions than my pine64
   
6. I tried to fix the disk issues with fsck, but both fdisk and gparted were unhappy and failed.  I am trying to understand if this is an SDcard issue or a issue with software image.  I will test with another card next week. (I would post the error message, but it was getting late and I did not have a chance to capture it.)
   
7. The process got me thinking about expanding the volume.  Do we have a script to automate this like we originally had with Debian or Armbian on the Pine64?
   

Does anyone know if the Pine64 is on the list of the supported ARM CPU's reportedly supported in the upcoming Windows 10 release?

I tried to compile https://github.com/rockchip-linux/gstreamer-rockchip but failed. Anyone know how to ?

Greetings,

I've been working on a Pinebook case mod which will safely expose the serial console slider switch on the main board without dismantling the Pinebook every time;  that was getting old fast-- ten tiny little screws ( its a miracle I have lost none of them yet ) !

   

The pic above is the slider switch;  look to the upper left of the pic and you'll see the pencil marks for the proposed dremel styrene work. The switch is in from the side 1.1 - 1.7 cm  and down from the back 8.1 - 8.2 cm.

   

I chose a 1.0mm carbonide cutting wheel for the dremel tool; do this from the underneath side cause it makes one dandy mess, but it cleans up nicely with a sharp modeling knife and a nail file.  Tip:  practice on another piece of styrene first ;  dremels take some getting used to.

   

This is the case opening after cleanup;  there is still ample protection, things will stay out of there, but the switch may be accessed easily.

   

Final pic is my high intensity 9 LED flashlight illuminating the slider switch inside the Pinebook case.  I use a simple slider switch access tool (toothpic) and voilà  !

I know snapchat despises anything but 'real' ™ factory default phones so will it work with this or not?

I would like to get one of these sbcs for mobile programming work instead of buying a smartphone since they don't have the government surveillance crap hardwired into them like phones do but if I need to run snapchat and if it wouldn't work then I would have to maybe get over my paranoid delusions and buy a normal phone for this work .

So has anyone run snapchat successfully on it or not?

About My Rock64 occurred kernel panic.

I bought four Rock64 board.
2 of 4GB model,2 of 2GB model.
Other 3 boards works well.
One of 4GB model occurrd this problem every time.
Im using newest xenial-minimum and xenial-mate on MicroSD.
Power supply to GPIO 5V and GND by iPad Pro's 5V 2.4A charger.
But other 3 board work well under same MicroSD,OS image,charger.
So I think comatibility problem(or initial failure?)

movie:xenial minimum on microSD
pictureame(https://drive.google.com/file/d/0B58MjMV...sp=sharing)
I know how to fix this problem.
Sorry my bad english and Thank you forum member 

OK, I'm  sure there is something I'm not doing right, but the RTC has me stumped. I use the access point in the upper right of the Mate desktop to set the RTC to use my time zone and report time in 12, instead of 24 hour format. I do this as a user with Admin privileges. And the clock changes appropriately...until the next boot, whereupon I see that it has forgotten the settings and has gone back to defaults. The menus are very explicit about setting the system clock options. So what have I missed?

This is for those less familiar with Linux, or running Linux from an SD card.
When you flash Ubuntu Xenial onto an SD card, the root filesystem size is only big enough to fit the operating system.
This is intentional; to keep the size of the image file as small as possible, making it quicker to download and flash to any size SD card (within reason).
After flashing the sd card and booting up for the first time, log in and do the following to expand the root filesystem by following these instructions.
There's a lot of code below, but the whole process took me less than 2 minutes, and you should be able to safely accept the default response to all prompts.

1. Fix the partition table to reflect the size of the SD card: