I've just received my PBP and NVMe SSD adapter. Are there any instructions about how to install it? Most of the threads to date have been about early boards, clearances and whether or not which make/model SSD will fit. I cannot find anything that will help a noob install this board.

My board is labelled:
PineBookPro-NGFF / M2 M-KEY
V2.1-2019-0809

There's also a FS logo and the digits 1935 printed after it.

I have a small plastic bag containing three tiny black screws, one small silver screw and a brass standoff (look like a thick washer). I also have a ribbon cable labelled SSD at one end and PCBA at the other.

Are there any step-by-step instructions for how to install this in the PBP? There's nothing in the wiki and nothing concise in the forums.

I don't have great experience with electronics hardware, so any noob guide to help me (and others) would be massively appreciated.

Thanks!

I was wondering what number you get on this? I think it will be most accurate on a browser restart with no other tabs 
https://chromium.github.io/octane/

Do any of you use vs code or code oss? Does it run well?

If anyone is looking for an NVME drive for their Pinebook Pro, I have tested the 512GB Intel 660p M.2 2280 SSD on battery power and I am happy to report and recommend it.

I tested it on the Manjaro Preview 4.  At 5% battery power Manjaro warns that the battery is low and that you should either select Hibernate, Suspend or Shutdown.


I kept the Pinebook Pro powered on for about 9 Hrs with drive mounted and the screen turned off.

Occasionally I would turn on the screen and copy a 14GB file from the SSD to the emmc.

I also duplicated the 14GB file on the SSD.  On the SSD my speed was was consistently about 230 mb/sec.

I decided to keep on running and was copying 5GB of 14GB when the laptop appeared to try and turn off at 2% battery power.

I should note that for the last 1.5 hours I had the screen on at about 50% brightness.

The Inted SSD operates at 3.3V and draws a maximum 1.35 amps.  So that works out to 4.46 watts.

The part number is SSDPEKNW512G8X1.

The December Community Update is now live.

Discuss away

Hi everyone,

I'd like everyone's input on what you think we did well this year and what could be done better.

Thank you for 2019!

I've not yet received my Pinebook Pro yet, so some of this may be obvious once I begin to work with various images.

On these threads, I see a lot of discussion about the function and performance of different DEs - XFDE, KDE, Gnome 3 - and nearly all of these reference the state of Wayland and the Panfrost driver for Mali T860 MP.

My own experience with Wayland is reasonable. Enough to determine that it is promising, but not yet mature enough in support by all applications and cases for my daily use with Gnome 3. Especially scaling with XWayland, but also other controls and decorations rendering. 

Are there obstacles on the Pinebook Pro that make use of X11 sessions for DE problematic? Are they slower, or is image size noticeably more bloated? Does Panfrost have notable impediment driving X11?  X is stable and easily configurable since X.org took over from XFree86, and I'd prefer my configurations to eliminate issues that on these forums, seem to have Wayland or Panfrost complexities.

Building kernels is no great barrier for me. I'm liable to try alternatives to Panfrost if they are a compilation or modules.conf effort.

Thanks!
— Jeremiah

I'm selling my new Pinebook Pro with 128 MB eMMC flash storage. I'm asking only $100 plus shipping. Post questions here. Please contact me for sales by private message through this site (https://forum.pine64.org/private.php).

(11-08-2019, 05:52 PM)Arglebargle Wrote: RE u-boot: The script to patch u-boot on the eMMC is simple enough that it should just work, I don't think it's doing anything that would fail on chromeOS.

If for some reason it does fail I hacked a copy so I could flash to a specified device instead of the detected root; I used this to patch loopback mounted copies of ayufan's images so they're ready to use again if I need them. Just edit DEVID to point at the device you want to flash updated u-boot onto: https://pastebin.com/raw/EeK074XB.

You don't want to be working in crosh, either switch to the debug shell (ctrl+alt+f2) or drop to a proper shell from crosh by running "shell" and then switch to root. I usually just "sudo -i bash" as cronos (default password is "cronos") and away you go.

--

I tried the ChromeOS build out for a bit last night and it seemed to work well. Netflix video playback seemed significantly smoother compared to Linux, is there better support for hardware accelerated video here vs the Linux builds? My only real gripe with the experience was the touchpad, otherwise the PBP makes a pretty decent chromebook.

I've just ordered my pinetime devkit so it'll be a while before it arrives, but I was thinking the first thing we should probably do in common before we all go off to do our own things is develop a bootloader that will work in common with all our projects. It's all very well writing the flash via SWD with the devkits, but in the production version presumably we're going to need another way of writing the flash that doesn't involve opening the case.

The bootloader should be able to:

• Drive the display, bluetooth and SPI flash.
  
• Present a nice liveness/progress bar indicator during the boot process.
  
• Delay on boot, check if the button is pressed.
  
• If the button is pressed, enter "rescue" mode that will offer a serial console over bluetooth with xmodem (or similar) support to download a (compressed?) firmware image.
  
• Write any firmware image received to SPI flash, verify checksums.
  
• Check on boot if a new firmware image is available in external flash, if so write it to internal (memory mapped) flash.
  
• Protect the internal flash.
  
• Set the watchdog timer.
  
• Branch to whatever address we agree the kernel entry point should live at.
  

Hello to all

Unfortunately, for RealVNC server is no install package available, so I#m looking for a SW to access my Rock64 desktop over the internet.
It should be something cloud based and not a port release.
Teamviewer? 

Any suggestions?