I just got my Rock64 and used the pine64 installer from pine64dev's github and installed Debian Stretch Minimal to my 32gb sd card. However, when I plug in the Rock64 and insert the sd card, nothing happens on screen. Am I doing something wrong? All 3 leds are on and I can turn the red and white ones off by holding the power button, but nothing happens on screen.

Hi,
I'm trying to run Netbeans on my Pinebook but it fail:

Error: Could not create the Java Virtual Machine.
Error: A fatal exception has occurred. Program will exit.

Anybody know why?

I like to used reversed ips and have my router assign the ip address based upon the MAC address of the network adapter.

So I find the IP address (172.16.90) assigned to the rock, and then assign an ip addressed to that MAC address. I reboot, and I can't ping it.  I look again and I see the Rock has now gotten 172.16.0.90 again.  I figure I made a mistake so I create a new one.  The same thing happens.  I'm looking at my reservations and sure enough I'm seeing different mac addresses for "linaro-alip".  I SSH into the terminal and "ip a" confirms that I'm getting a different MAC address.

What is going on here?

I just opened up my order, and while there was a nice big plastic box for the EMMC chip, it was completely empty.  Not even foam packaging inside.  Anyone else have a problem with their order?

Bummed

I'm looking at the distros on the Wiki and see that there are distros for a microSD boot device.  Will this also work if I burn the image to a EEMC device?

No idea what I can do with it, I've got a big learning curve ahead but its installed


rock64@node1:~$ kubectl get nodes
NAME      STATUS    AGE       VERSION
node1     Ready     1h        v1.7.5
node2     Ready     1h        v1.7.5
node3     Ready     1h        v1.7.5
node4     Ready     1h        v1.7.5
node5     Ready     1h        v1.7.5

Hi,

thanks to the great Q4os developers I now have a quite decent Debian Stretch system running.  After I managed to flash the eMMC with Q4os I simply editet sources.list to point to Stretch instead of Jessie and did a dist-upgrade.   I needed to fiddle a bit with the graphics since X was lost but rebuilding libump and xf86-video-fbturbo under Stretch did the trick.  (I'm a Debian developer and might consider creating at least an official libump package - need to check the license of fbturbo whether it is acceptable in Debian.)

I now try to get some reliable information about the battery status.  I'm using xfce4 but the battery plugin always says the battery is empty (even if I get a desktop notification that the battery is full when plugging in power adapter.

The command acpi does not work.

How do others check the battery status on pinebook?

Kind regards

        Andreas.

Hey, my board keeps crashing on startup. I haven't been able to use it over the past 2 weeks. I've been formatting my SD cards and have even bought several new ones, but it doesnt seem to have made an effect. What steps can I take for trouble shooting? 

Could it be a power supply issue? 


https://i.imgur.com/cJy5WRX.jpg

Just in case anyone else is having a similar problem.

My Pinebook has had a history of just shutting off at random occasions after a couple of months light use.  I had put this down to the development status of the system, however, it was getting more and more common, occasionally refusing to boot, so much so I was starting to be convinced it was hardware.  
I opened the thing up and removed the tape covering the cable from the battery to the mainboard.  The left hand side of the socket on the board was broken and the connector came away with the tape.    
The bend in the power cables meant it would not stay in position, and I didn't want to blob some epoxy on the connector in case of future upgrades.  So, several strips of tape to route the battery power leads in position and reseating the connector and it now works perfectly.  I had been worried it would be a dodgy capacitor somewhere, but a relatively simple fix.

One thing I did notice with the system when I thought it was software based was that while I was looking at the system logs in an ssh session is that the USB system lost power and came back.

Anyway, if anyone else has a similar problem with random system crashes / power offs, it may be worth a look.

Android 7.1 (SOPINE) v0.3.10-r66