Hi all,
I'm selling my Pinebook Pro (128GB eMMc version ) + NVME adapter.
I'm on USA so if anyone is interested let me know.

Asking price: $190 + shipping cost.

The wall wart (power adapter) delivered with the Pinebook Pro comes with a removable plug-end; I currently have the one with two round prongs suitable for power outlets in most EU countries.

However, since the cable plugging into the PBP is very short, and I would like to use a standard 5m power cable of which I have several in the house (used with Dell laptop power adapters), I was wondering if there is a plug-end featuring a Mickey Mouse type plughole to fit the 5m power cable.

If so, what is it called, and where can I get it?

https://fydeos.com/download/

I think fyde os would be a great OS for the pinebook.

Linux, Android compatible, and liGNUx compatible via LXC.

But I did not find images.

Also it would be funny that the Pinephone that shares SoC with the pinebook would be the first smartphone capable of running Chromium OS too.

Hello,

Has anyone had any problems with PCIe working at x4 link width? I have two Rockpro64 boards, let's call them Board A and Board B. And I have an I350-T2 PCI Express card, which has x4 Lane support. Board A only ever achieves a x2 Lane configuration after link training. Board B usually manages x4 Lane (but not always) and quite often fails on the first Configuration Register access with an External Data Abort fault.

To diagnose this further, I have modified the PCIe PHY driver, so that at startup only one Lane is turned on, the other three remaining off (by configuring GRF_SOC_CON_5_PCIE accordingly). I then boot the board with just this one Lane enabled and observe the results - obviously the system should run successfully with a x1 Lane configuration after link training. Trying each board, with each lane enabled in turn individually, I find that:

With Board A, each of Lanes 0, 1 and 2 always achieve successful link training and subsequent access to the card never fails. However, link training on Lane 3 always fails, so the card cannot be accessed with just this lane enabled - and hence explains why it always falls back to x2 mode when all four lanes are enabled.

With Board B, again each of Lanes 0, 1 and 2 always work successfully. With just Lane 3 enabled, link training succeeds (nearly always, anyway). However,  after successful link training, the first access to a register on the card fails around 50% of the time, with an External Data Abort fault, implying that the signal over this lane is not reliable. On one occasion, the first few accesses succeeded and then it failed. The frequency of the failure does diminish if you increase the bus-scan-delay-ms period, but even with this set at 3 seconds, failures still occur.

I notice on the Rockpro64 schematic (Sheet 27) that the PCIE_RX3P / PCIE_RX3N lines have additional circuitry. It appears to consist of a potential divider to hold the DC bias of the Lane 3 output from the PCIe card at 350mV, followed by a 50ohm impedance termination and AC coupling capacitor, before the signal is fed into to RK3399. I'm no hardware engineer, so I don't quite understand what the purpose of this is - and I haven't managed to find any information about it on the internet. Does anyone know what this is for? Could it be affecting the reliability of Lane 3?

(I get the same results with a second I350-T2 card, but unfortunately don't have any alternative PCIe x4 cards to test with).

I look forward to anyone's comments regarding this,
Andy

Hi all! New here. I'm having a hard time finding information about ordering dev kits? Specifically interested in buying those for pinetime, pinephone and pinebookpro depending on how broke it will leave me  . If it's possible to order these, what are the chances of getting these are before January?

I trying to find an "arm64" Ubuntu image for the PineBook Pro. 
There are no arm64 versions available here - https://github.com/ayufan-rock64/linux-b...tag/0.9.14
or in any of the recent releases. Just a minimal image is ok as long as the network connects and the display works.
Thanks.

I see in the description of the phone that there are hardware kill switches for wireless, camera, microphone, etc.

But I don't see where these are located on the device. The pictures only show power and volume buttons.
Somewhere in the description it also says that there will only be three buttons.

So... how does that work?

I downloaded the android image for microsd card today, but when I tried to write the image to my microsd card, etcher said that the image was missing a GPT table (or something like that) and probably wouldn't boot. I have tried both the 32gb and the 16gb versions, and I have also tried to DD the image to the microsd card (DD said it succeeded, but the PBP wouldn't boot at all with the flashed microsd card in). Is this a known issue with the builds?

Black Friday / cyber monday discounts ?

apt-get update problems:

W: http://ppa.launchpad.net/ayufan/rock64-0.../InRelease: The key(s) in the keyring /etc/apt/trusted.gpg.d/ayufan.key.chroot.gpg are ignored as the file has an unsupported filetype.
E: The repository 'http://ppa.launchpad.net/kupfer-team/ppa/ubuntu bionic Release' does not have a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
W: http://ppa.launchpad.net/ayufan/rock64-0.../InRelease: The key(s) in the keyring /etc/apt/trusted.gpg.d/ayufan.key.chroot.gpg are ignored as the file has an unsupported filetype.
W: http://ports.ubuntu.com/ubuntu-ports/dis.../InRelease: The key(s) in the keyring /etc/apt/trusted.gpg.d/ayufan.key.chroot.gpg are ignored as the file has an unsupported filetype.
W: http://ppa.launchpad.net/gerardpuig/ppa/.../InRelease: The key(s) in the keyring /etc/apt/trusted.gpg.d/ayufan.key.chroot.gpg are ignored as the file has an unsupported filetype.
W: http://ports.ubuntu.com/ubuntu-ports/dis.../InRelease: The key(s) in the keyring /etc/apt/trusted.gpg.d/ayufan.key.chroot.gpg are ignored as the file has an unsupported filetype.
W: http://deb.ayufan.eu/orgs/ayufan-rock64/.../InRelease: The key(s) in the keyring /etc/apt/trusted.gpg.d/ayufan.key.chroot.gpg are ignored as the file has an unsupported filetype.
W: http://repo.steampowered.com/steam/dists.../InRelease: The key(s) in the keyring /etc/apt/trusted.gpg.d/ayufan.key.chroot.gpg are ignored as the file has an unsupported filetype.
W: http://ports.ubuntu.com/ubuntu-ports/dis.../InRelease: The key(s) in the keyring /etc/apt/trusted.gpg.d/ayufan.key.chroot.gpg are ignored as the file has an unsupported filetype.
W: http://ppa.launchpad.net/oguzhaninan/sta.../InRelease: The key(s) in the keyring /etc/apt/trusted.gpg.d/ayufan.key.chroot.gpg are ignored as the file has an unsupported filetype.
W: http://ppa.launchpad.net/utappia/stable/.../InRelease: The key(s) in the keyring /etc/apt/trusted.gpg.d/ayufan.key.chroot.gpg are ignored as the file has an unsupported filetype.