PINE64 - User contributions [en]

Talk:Pinebook Pro Installing Arch Linux ARM

2023-08-25T01:42:20Z

BenTheTechGuy: change other mention of wrong user

== Tow-Boot ==

I would recommend installing Tow-Boot on SPI, it really simplifies things and also enables boot from nvme, if installed.--[[User:WoC|WoC]] ([[User Talk:WoC|talk]]) 05:05, 19 September 2022 (UTC)

Talk:Pinebook Pro Installing Arch Linux ARM

2023-08-25T01:38:20Z

BenTheTechGuy: I didn't write that…

== Tow-Boot ==

I would recommend installing Tow-Boot on SPI, it really simplifies things and also enables boot from nvme, if installed.--[[User:BenTheTechGuy|BenTheTechGuy]] ([[User Talk:WoC|talk]]) 01:05, 19 September 2022 (UTC)

Talk:Pinebook Pro Installing Arch Linux ARM

2023-02-20T04:00:29Z

BenTheTechGuy: BenTheTechGuy moved page Talk:Pinebook Pro Installing Arch Linux ARM to Talk:Installing Arch Linux ARM On The Pinebook Pro over redirect: This particular naming is already used for other devices and operating systems. See "Installing Arch Linux ARM on the Quartz64" and "Installing Void Linux ARM on the Pinebook Pro"

I would recommend installing Tow-Boot on SPI, it really simplifies things and also enables boot from nvme, if installed.

Pinebook Pro Installing Arch Linux ARM

2023-02-20T04:00:29Z

BenTheTechGuy: BenTheTechGuy moved page Pinebook Pro Installing Arch Linux ARM to Installing Arch Linux ARM On The Pinebook Pro over redirect: This particular naming is already used for other devices and operating systems. See "Installing Arch Linux ARM on the Quartz64" and "Installing Void Linux ARM on the Pinebook Pro"

These instructions can be followed to install Arch Linux ARM on an SD Card, USB Flash Drive, eMMC, or even NVMe if your U-Boot supports it (example Tow-Boot on SPI).

Commands to be run as a normal user are prefixed with <code>$</code>, commands to be run as root (or with <code>sudo</code>) are prefixed with <code>#</code>.
The target device is assumed to be <tt>/dev/sdb</tt>, adjust accordingly.

== Partitioning ==
=== Flashing U-Boot ===
{{note|While any U-Boot for the Pinebook Pro can be used, this tutorial uses [https://tow-boot.org Tow-Boot].
The process of installing Tow-Boot is different from any other U-Boot, so large parts of the partitioning section will need to be changed if you want to use something else.
If you already have Tow-Boot installed via SPI, you can skip this step. Use fdisk to create a blank GPT partition table. <tt>/boot</tt> will be partition 1, and <tt>/</tt> partition 2.}}

Download and extract the latest release of Tow-Boot for the Pinebook Pro from https://github.com/Tow-Boot/Tow-Boot/releases.
<nowiki>$ wget https://github.com/Tow-Boot/Tow-Boot/releases/download/release-2021.10-004/pine64-pinebookPro-2021.10-004.tar.xz</nowiki>
$ tar xf pine64-pinebookPro-2021.10-004.tar.xz

Flash Tow-Boot to <tt>/dev/sdb</tt> (replace this with the device you actually intend to use).
# dd if=pine64-pinebookPro-2021.10-004/shared.disk-image.img of=/dev/sdb bs=1M oflag=direct,sync

This creates the partition table for the device, with the first partition serving to protect Tow-Boot. Do not move or write to this partition.

=== Creating the partitions ===
Use <code>fdisk</code> to add partitions to <tt>/dev/sdb</tt>.

# fdisk /dev/sdb

Create the <tt>/boot</tt> partition.
* Type '''n''' to create a new partition.
* Press enter for partition number two.
* Press enter for the default start sector.
* Type '''+256M''' to make the new partition 256 MiB.

Mark the <tt>/boot</tt> partition bootable.
* Type '''x''' to enter expert mode.
* Type '''A''' to mark a partition bootable.
* Type '''2''' to select partition two.
* Type '''r''' to exit expert mode.

Create the root partition.
* Type '''n''' to create a new partition.
* Press enter for partition number three.
* Press enter for the default start sector.
* Press enter to fill the rest of the device.

Write the changes to disk.
* Type '''w''' to write the changes and exit.

=== Formatting the partitions ===
Format the <tt>/boot</tt> partition as a filesystem supported by your U-Boot. ext4 is recommended:
# mkfs.ext4 /dev/sdb2

Format the root partition as any filesystem supported by Arch Linux ARM. btrfs for example:
# mkfs.btrfs /dev/sdb3

== Installing the root filesystem ==
=== Mounting the partitions ===
# mount /dev/sdb3 /mnt
# mkdir /mnt/boot
# mount /dev/sdb2 /mnt/boot

=== Downloading and verifying the rootfs tarball ===
Download the tarball and its PGP signature.
<nowiki>$ wget http://os.archlinuxarm.org/os/ArchLinuxARM-aarch64-latest.tar.gz{,.sig}</nowiki>

Import the Arch Linux ARM signing key.
$ gpg --keyserver keyserver.ubuntu.com --recv-keys 68B3537F39A313B3E574D06777193F152BDBE6A6

Verify the tarball's authenticity.
$ gpg --verify ArchLinuxARM-aarch64-latest.tar.gz.sig

Verifying the authenticity of the tarball protects you in two ways:
# Makes sure the tarball came directly from Arch Linux ARM and was not tampered with
# Prevents you from using a corrupt tarball (for example from an interrupted download)

=== Extracting and configuring the root filesystem ===
==== Extracting the root filesystem ====
# bsdtar -xpf ArchLinuxARM-aarch64-latest.tar.gz -C /mnt

==== Editing fstab ====
Find the partitions' UUIDs with <code>blkid</code>.
# blkid /dev/sdb3 /dev/sdb2

Example output:
/dev/sdb3: UUID="c1ec9712-5c64-46da-852c-9d665416e8a6" UUID_SUB="90e5b654-6967-471a-9d35-8997488b1ba8" BLOCK_SIZE="4096" TYPE="btrfs" PARTUUID="885dd863-a550-2d47-89dd-f54fd6744ca5"
/dev/sdb2: UUID="21bbff3f-b82e-416e-93c8-e6d44c3daf82" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="be571200-1a56-5d4c-9a5b-88a5f36a295e"

Add the following lines to <tt>/mnt/etc/fstab</tt>, substituting the example UUIDs with those you received from <code>blkid</code>.
UUID=c1ec9712-5c64-46da-852c-9d665416e8a6 / btrfs defaults 0 1
UUID=21bbff3f-b82e-416e-93c8-e6d44c3daf82 /boot ext4 defaults 0 2

==== Creating extlinux.conf ====

Create a file <tt>/mnt/boot/extlinux/extlinux.conf</tt> with the following contents, replacing the example UUID with the one for <tt>/dev/sdb3</tt> from <code>blkid</code>.
DEFAULT arch
MENU TITLE Boot Menu
PROMPT 0
TIMEOUT 50

LABEL arch
MENU LABEL Arch Linux ARM
LINUX /Image
INITRD /initramfs-linux.img
FDT /dtbs/rockchip/rk3399-pinebook-pro.dtb
APPEND root=UUID=c1ec9712-5c64-46da-852c-9d665416e8a6 rw

LABEL arch-fallback
MENU LABEL Arch Linux ARM with fallback initramfs
LINUX /Image
INITRD /initramfs-linux-fallback.img
FDT /dtbs/rockchip/rk3399-pinebook-pro.dtb
APPEND root=UUID=c1ec9712-5c64-46da-852c-9d665416e8a6 rw

== Booting and finishing setup ==
Boot into Arch Linux ARM and log in as <tt>root</tt> with password <tt>root</tt>.

Initialize the pacman keyring.
# pacman-key --init
# pacman-key --populate archlinuxarm

For security, change the default passwords for root and the default user <tt>alarm</tt>.
# passwd
# passwd alarm

Congratulations, you have now installed Arch Linux ARM on your PineBook Pro!

Pinebook Pro Installing Arch Linux ARM

2023-02-20T03:58:09Z

BenTheTechGuy: These steps are already implicitly included and done automatically

Pinebook Pro Installing Arch Linux ARM

2022-10-16T02:48:16Z

BenTheTechGuy: Wording

These instructions can be followed to install Arch Linux ARM on an SD Card, USB Flash Drive, eMMC, or even NVMe if your U-Boot supports it (example Tow-Boot on SPI).

Commands to be run as a normal user are prefixed with <code>$</code>, commands to be run as root (or with <code>sudo</code>) are prefixed with <code>#</code>.
The target device is assumed to be <tt>/dev/sdb</tt>, adjust accordingly.

== Partitioning ==
=== Flashing U-Boot ===
{{note|While any U-Boot for the Pinebook Pro can be used, this tutorial uses [https://tow-boot.org Tow-Boot].
The process of installing Tow-Boot is different from any other U-Boot, so large parts of the partitioning section will need to be changed if you want to use something else.
If you already have Tow-Boot installed via SPI, you can skip this step. Use fdisk to create a blank GPT partition table. <tt>/boot</tt> will be partition 1, and <tt>/</tt> partition 2.}}

Download and extract the latest release of Tow-Boot for the Pinebook Pro from https://github.com/Tow-Boot/Tow-Boot/releases.
<nowiki>$ wget https://github.com/Tow-Boot/Tow-Boot/releases/download/release-2021.10-004/pine64-pinebookPro-2021.10-004.tar.xz</nowiki>
$ tar xf pine64-pinebookPro-2021.10-004.tar.xz

Flash Tow-Boot to <tt>/dev/sdb</tt> (replace this with the device you actually intend to use).
# dd if=pine64-pinebookPro-2021.10-004/shared.disk-image.img of=/dev/sdb bs=1M oflag=direct,sync

This creates the partition table for the device, with the first partition serving to protect Tow-Boot. Do not move or write to this partition.

=== Creating the partitions ===
Use <code>fdisk</code> to add partitions to <tt>/dev/sdb</tt>.

# fdisk /dev/sdb

Create the <tt>/boot</tt> partition.
* Type '''n''' to create a new partition.
* Press enter for partition number two.
* Press enter for the default start sector.
* Type '''+256M''' to make the new partition 256 MiB.

Mark the <tt>/boot</tt> partition bootable.
* Type '''x''' to enter expert mode.
* Type '''A''' to mark a partition bootable.
* Type '''2''' to select partition two.
* Type '''r''' to exit expert mode.

Create the root partition.
* Type '''n''' to create a new partition.
* Press enter for partition number three.
* Press enter for the default start sector.
* Press enter to fill the rest of the device.

Write the changes to disk.
* Type '''w''' to write the changes and exit.

=== Formatting the partitions ===
Format the <tt>/boot</tt> partition as a filesystem supported by your U-Boot. ext4 is recommended:
# mkfs.ext4 /dev/sdb2

Format the root partition as any filesystem supported by Arch Linux ARM. btrfs for example:
# mkfs.btrfs /dev/sdb3

== Installing the root filesystem ==
=== Mounting the partitions ===
# mount /dev/sdb3 /mnt
# mkdir /mnt/boot
# mount /dev/sdb2 /mnt/boot

=== Downloading and verifying the rootfs tarball ===
Download the tarball and its PGP signature.
<nowiki>$ wget http://os.archlinuxarm.org/os/ArchLinuxARM-aarch64-latest.tar.gz{,.sig}</nowiki>

Import the Arch Linux ARM signing key.
$ gpg --keyserver keyserver.ubuntu.com --recv-keys 68B3537F39A313B3E574D06777193F152BDBE6A6

Verify the tarball's authenticity.
$ gpg --verify ArchLinuxARM-aarch64-latest.tar.gz.sig

Verifying the authenticity of the tarball protects you in two ways:
# Makes sure the tarball came directly from Arch Linux ARM and was not tampered with
# Prevents you from using a corrupt tarball (for example from an interrupted download)

=== Extracting and configuring the root filesystem ===
==== Extracting the root filesystem ====
# bsdtar -xpf ArchLinuxARM-aarch64-latest.tar.gz -C /mnt

==== Editing fstab ====
Find the partitions' UUIDs with <code>blkid</code>.
# blkid /dev/sdb3 /dev/sdb2

Example output:
/dev/sdb3: UUID="c1ec9712-5c64-46da-852c-9d665416e8a6" UUID_SUB="90e5b654-6967-471a-9d35-8997488b1ba8" BLOCK_SIZE="4096" TYPE="btrfs" PARTUUID="885dd863-a550-2d47-89dd-f54fd6744ca5"
/dev/sdb2: UUID="21bbff3f-b82e-416e-93c8-e6d44c3daf82" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="be571200-1a56-5d4c-9a5b-88a5f36a295e"

Add the following lines to <tt>/mnt/etc/fstab</tt>, substituting the example UUIDs with those you received from <code>blkid</code>.
UUID=c1ec9712-5c64-46da-852c-9d665416e8a6 / btrfs defaults 0 1
UUID=21bbff3f-b82e-416e-93c8-e6d44c3daf82 /boot ext4 defaults 0 2

==== Creating extlinux.conf ====
Create a file <tt>/mnt/boot/extlinux/extlinux.conf</tt> with the following contents, replacing the example UUID with the one for <tt>/dev/sdb3</tt> from <code>blkid</code>.
DEFAULT arch
MENU TITLE Boot Menu
PROMPT 0
TIMEOUT 50

LABEL arch
MENU LABEL Arch Linux ARM
LINUX /Image
INITRD /initramfs-linux.img
FDT /dtbs/rockchip/rk3399-pinebook-pro.dtb
APPEND root=UUID=c1ec9712-5c64-46da-852c-9d665416e8a6 rw

LABEL arch-fallback
MENU LABEL Arch Linux ARM with fallback initramfs
LINUX /Image
INITRD /initramfs-linux-fallback.img
FDT /dtbs/rockchip/rk3399-pinebook-pro.dtb
APPEND root=UUID=c1ec9712-5c64-46da-852c-9d665416e8a6 rw

== Booting and finishing setup ==
Boot into Arch Linux ARM and log in as <tt>root</tt> with password <tt>root</tt>.

Initialize the pacman keyring.
# pacman-key --init
# pacman-key --populate archlinuxarm

For security, change the default passwords for root and the default user <tt>alarm</tt>.
# passwd
# passwd alarm

Congratulations, you have now installed Arch Linux ARM on your PineBook Pro!

Pinebook Pro Installing Arch Linux ARM

2022-03-18T22:37:59Z

BenTheTechGuy: Add bootable flag to /boot partition

These instructions can be followed to install Arch Linux ARM on an SD Card, USB Flash Drive, eMMC, or even NVMe if your U-Boot supports it.

Commands to be run as a normal user are prefixed with <code>$</code>, commands to be run as root (or with <code>sudo</code>) are prefixed with <code>#</code>.
The target device is assumed to be <tt>/dev/sdb</tt>, adjust accordingly.

== Partitioning ==
=== Flashing U-Boot ===
{{note|While any U-Boot for the Pinebook Pro can be used, this tutorial uses [https://tow-boot.org Tow-Boot].
The process of installing Tow-Boot is different from any other U-Boot, so large parts of the partitioning section will need to be changed if you want to use something else.}}

Download and extract the latest release of Tow-Boot for the Pinebook Pro from https://github.com/Tow-Boot/Tow-Boot/releases.
<nowiki>$ wget https://github.com/Tow-Boot/Tow-Boot/releases/download/release-2021.10-004/pine64-pinebookPro-2021.10-004.tar.xz</nowiki>
$ tar xf pine64-pinebookPro-2021.10-004.tar.xz

Flash Tow-Boot to <tt>/dev/sdb</tt> (replace this with the device you actually intend to use).
# dd if=pine64-pinebookPro-2021.10-004/shared.disk-image.img of=/dev/sdb bs=1M oflag=direct,sync

This creates the partition table for the device, with the first partition serving to protect Tow-Boot. Do not move or write to this partition.

=== Creating the partitions ===
Use <code>fdisk</code> to add partitions to <tt>/dev/sdb</tt>.

# fdisk /dev/sdb

Create the <tt>/boot</tt> partition.
* Type '''n''' to create a new partition.
* Press enter for partition number two.
* Press enter for the default start sector.
* Type '''+256M''' to make the new partition 256 MiB.

Mark the <tt>/boot</tt> partition bootable.
* Type '''x''' to enter expert mode.
* Type '''A''' to mark a partition bootable.
* Type '''2''' to select partition two.
* Type '''r''' to exit expert mode.

Create the root partition.
* Type '''n''' to create a new partition.
* Press enter for partition number three.
* Press enter for the default start sector.
* Press enter to fill the rest of the device.

Write the changes to disk.
* Type '''w''' to write the changes and exit.

=== Formatting the partitions ===
Format the <tt>/boot</tt> partition as either FAT32 or ext4.

FAT32:
# mkfs.fat -F32 /dev/sdb2
ext4:
# mkfs.ext4 /dev/sdb2

Format the root partition as any filesystem supported by Arch Linux ARM. For this example ext4 is used:
# mkfs.ext4 /dev/sdb3

== Installing the root filesystem ==
=== Mounting the partitions ===
# mount /dev/sdb3 /mnt
# mkdir /mnt/boot
# mount /dev/sdb2 /mnt/boot

=== Downloading and verifying the rootfs tarball ===
Download the tarball and its PGP signature.
<nowiki>$ wget http://os.archlinuxarm.org/os/ArchLinuxARM-aarch64-latest.tar.gz{,.sig}</nowiki>

Import the Arch Linux ARM signing key.
$ gpg --keyserver keyserver.ubuntu.com --recv-keys 68B3537F39A313B3E574D06777193F152BDBE6A6

Verify the tarball's authenticity.
$ gpg --verify ArchLinuxARM-aarch64-latest.tar.gz.sig

Verifying the authenticity of the tarball protects you in two ways:
# Makes sure the tarball came directly from Arch Linux ARM and was not tampered with
# Prevents you from using a corrupt tarball (for example from an interrupted download)

=== Extracting and configuring the root filesystem ===
==== Extracting the root filesystem ====
# bsdtar -xpf ArchLinuxARM-aarch64-latest.tar.gz -C /mnt

==== Editing fstab ====
Find the partitions' UUIDs with <code>blkid</code>.
# blkid /dev/sdb2 /dev/sdb3

Example output:
/dev/sdb2: UUID="21bbff3f-b82e-416e-93c8-e6d44c3daf82" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="be571200-1a56-5d4c-9a5b-88a5f36a295e"
/dev/sdb3: UUID="d22c5207-0f87-4fe9-91ce-6d6e0fb9a13e" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="1d3603f4-bcd4-3c41-8d6d-23e65b405e5a"

Add the following lines to <tt>/mnt/etc/fstab</tt>, substituting the example UUIDs with those you received from <code>blkid</code>.
UUID=d22c5207-0f87-4fe9-91ce-6d6e0fb9a13e / ext4 defaults 0 1
UUID=21bbff3f-b82e-416e-93c8-e6d44c3daf82 /boot ext4 defaults 0 2

==== Creating extlinux.conf ====
Create a file <tt>/mnt/boot/extlinux/extlinux.conf</tt> with the following contents, replacing the example UUID with the one for <tt>/dev/sdb3</tt> from <code>blkid</code>.
default arch
menu title Boot Menu
prompt 0
timeout 50

label arch
menu label Arch Linux ARM
linux /Image
fdt /dtbs/rockchip/rk3399-pinebook-pro.dtb
append initrd=/initramfs-linux.img root=UUID=d22c5207-0f87-4fe9-91ce-6d6e0fb9a13e rw

== Booting and finishing setup ==
Boot into Arch Linux ARM and log in as <tt>root</tt> with password <tt>root</tt>.

Initialize the pacman keyring.
# pacman-key --init
# pacman-key --populate archlinuxarm

For security, change the default passwords for root and the default user <tt>alarm</tt>.
# passwd
# passwd alarm

Congratulations, you have now installed Arch Linux ARM on your Pinebook Pro!

Pinebook Pro Software Releases

2022-03-18T21:39:25Z

BenTheTechGuy: Add official Arch Linux ARM install instructions

= Linux OS Image Releases =
For information on how to install these images onto your device, please see the [[NOOB]] Page, which includes information on writing images to the device eMMC or an SD card

== Manjaro ARM ==
[[File:Manjaro.png|right|100px]]

The Manjaro project offers a mainline kernel with patches and modules to support PBPro hardware. To learn more about Manjaro please visit [https://forum.manjaro.org/c/arm/ Manjaro Forum]. You can follow the ongoing discussion about Manjaro on the [https://forum.pine64.org/showthread.php?tid=8207 PINE64 forum].
All images boot from both SD card and the internal eMMC module.

=== Manjaro ARM with KDE Plasma ===

* [https://manjaro.org/downloads/arm/pinebook-pro/arm8-pinebook-pro-kde-plasma/ Direct download from Manjaro]

=== Manjaro ARM with Xfce ===

* [https://manjaro.org/downloads/arm/pinebook-pro/arm8-pinebook-pro-xfce/ Direct download from Manjaro]

=== Manjaro ARM with Gnome ===

* [https://manjaro.org/downloads/arm/pinebook-pro/arm8-pinebook-pro-gnome/ Direct download from Manjaro]

=== Manjaro ARM with Sway ===
* [https://manjaro.org/downloads/arm/pinebook-pro/arm8-pinebook-pro-sway/ Direct download from Manjaro]

=== Manjaro ARM with no desktop ===
* [https://manjaro.org/downloads/arm/pinebook-pro/arm8-pinebook-pro-minimal/ Direct download from Manjaro]

== Armbian ==
[[File:armbian.png|right|100px]]
As of Nov. 3rd, 2021, Pinebook Pro has No official support (CSC) from Armbian.

To find out more about Armbian and available options please visit their [https://www.armbian.com/pinebook-pro/ site].

=== Armbian Ubuntu Focal with Xfce (mainline kernel) ===

Armbian provides a mainline kernel build images for Ubuntu Focal with Xfce Desktop. It boots from microSD card and from eMMC.

'''Download location'''

Get the latest image here: [https://dl.armbian.com/pinebook-pro/Focal_current_desktop Armbian's Pinebook Pro Ubuntu Focal Xfce]

=== Armbian Ubuntu Focal with Gnome (mainline kernel) ===

Armbian provides a mainline kernel build images for Ubuntu Focal with GNOME Desktop. It boots from microSD card and from eMMC.

'''Download location'''

Get the latest image here: [https://redirect.armbian.com/region/NA/pinebook-pro/Focal_current_gnome]

=== Armbian Ubuntu Focal with Xfce (legacy kernel) ===

Armbian provides a legacy kernel 4.4 build images for Ubuntu Focal with Xfce Desktop. It boots from microSD card and from eMMC.

'''Download location'''

Get the latest image here: [https://dl.armbian.com/pinebook-pro/Focal_legacy_desktop Armbian's Pinebook Pro Ubuntu Focal Xfce]

=== Armbian Debian Buster with Xfce (legacy kernel) ===

Armbian provides a legacy kernel 4.4 build images for Debian Buster with Xfce Desktop. It boots from microSD card and from eMMC.

'''Download location'''

Get the latest image here: [https://dl.armbian.com/pinebook-pro/Buster_legacy_desktop Armbian's Pinebook Pro Debian Buster Xfce]

=== Armbian Ubuntu Bionic with Xfce (legacy kernel) ===

Armbian provides a legacy kernel 4.4 build images for Ubuntu Bionic with Xfce Desktop. It boots from microSD card and from eMMC.

'''Download location'''

Get the latest image here: [https://dl.armbian.com/pinebook-pro/Bionic_legacy_desktop Armbian's Pinebook Pro Ubuntu Bionic Xfce Desktop download site]

== Twister OS ==
[[File:Twister_OS.png|right|100px]]

Twister OS Armbian-Reforged with Xfce. It boots from microSD card and from eMMC. For more information on Twister OS, please visit this [https://twisteros.com/ official site]. You can follow the ongoing discussion about Twister OS on the [https://forum.pine64.org/showthread.php?tid=12192 PINE64 forum].

'''Installation'''

* After flashing image, edit /boot/armbianEnv.txt, replace the dtb name with <code>rk3399-pinebook-pro.dtb</code>

'''Download location'''

Get the latest image here: [https://twisteros.com/twisterarmbian.html Direct download latest images from Twister OS's website] (size: 2.8GB)

'''Password'''

asdasd

== Fedora ==
[[File:fedora1.png|right|100px]]

=== Fedora Official ===

Using this [https://nullr0ute.com/2021/05/fedora-on-the-pinebook-pro/ blog post] it is now possible to run Official Fedora on the Pinebook Pro.

'''Notes'''
Upstream Fedora uses SPI flash on the Pinebook Pro to manage uboot.

=== Fedora 32 with Cinnamon ===

This image contains an install of Fedora with [https://cinnamon-spices.linuxmint.com/ Cinnamon] desktop environment. It boots from microSD card and from eMMC. To learn more about Fedora please visit the [https://getfedora.org/ official website].

'''Download location'''

Get the latest image here: [https://builds.armdevelopers.com/pinebook-pro/releases/dev/Fedora32-Cinnamon-Desktop-202009.0.pinebook-pro.img.xz Fedora 32 Pinebook Pro Image]

'''Username and password'''

root/fedora

=== Fedora 32 with KDE ===

This image contains an install of Fedora with [https://kde.org/ KDE aka Plasma] desktop environment. It boots from microSD card and from eMMC. To learn more about Fedora please visit the [https://getfedora.org/ official website].

'''Download location'''

Get the latest image here: [https://builds.armdevelopers.com/pinebook-pro/releases/dev/Fedora32-KDE-Desktop-202009.0.pinebook-pro.img.xz Fedora 32 Pinebook Pro Image]

'''Username and password'''

root/fedora

=== Fedora 32 with Xfce===

This image contains an install of Fedora with [https://xfce.org/ Xfce] desktop environment. It boots from microSD card and from eMMC. To learn more about Fedora please visit the [https://getfedora.org/ official website].

'''Download location'''

Get the latest image here: [https://builds.armdevelopers.com/pinebook-pro/releases/dev/Fedora32-Xfce-Desktop-202009.0.pinebook-pro.img.xz Fedora 32 Pinebook Pro Image]

'''Username and password'''

root/fedora

=== Fedora 32 with Gnome ===

This image contains an install of Fedora with [https://www.gnome.org/gnome-3/ GNOME 3] desktop environment. It boots from microSD card and from eMMC. To learn more about Fedora please visit the [https://getfedora.org/ official website].

'''Download location'''

Get the latest image here: [https://builds.armdevelopers.com/pinebook-pro/releases/dev/Fedora32-Workstation-202009.0.pinebook-pro.img.xz Fedora 32 Pinebook Pro Image]

'''Username and password'''

root/fedora

== Arch Linux ARM ==
[[File:Archlinux-logo.png|right|100px]]

=== Official Installation ===
See [[Installing Arch Linux ARM On The Pinebook Pro]] for instructions on how to install the official Arch Linux ARM.

=== Customized Premade Image ===
Arch Linux ARM root filesystem customized for the Pinebook Pro using Manjaro kernel. Instructions are included for installation on microSD card, eMMC module and NVME SSD.

'''Download location'''

[https://github.com/SvenKiljan/archlinuxarm-pbp/releases/latest Get the latest image from GitHub] (size: 591 MB).

'''Installation'''

Make sure to thoroughly read the [https://github.com/SvenKiljan/archlinuxarm-pbp/blob/main/README.md readme], [https://github.com/SvenKiljan/archlinuxarm-pbp/blob/main/README.md installation instructions] and [https://github.com/SvenKiljan/archlinuxarm-pbp/blob/main/FAQ.md FAQ].

'''Username and password'''

The default Arch Linux ARM user credentials.

Username: alarm

Password: alarm

The password for the root account is 'root'.

== postmarketOS ==
[[File:PostmarketOS logo.png|right|100px]]

Official postmarketOS build with the GNOME desktop for the Pinebook Pro. It boots from microSD card and from eMMC.

'''Download location'''

Get the latest image here: [https://images.postmarketos.org/bpo/edge/pine64-pinebookpro/ Direct download latest images from postmarketOS] (size: 400 MB)

'''Username and password'''

demo/demo

or:

demo/147147

==Kali Linux==
[[File:Kali.jpeg|right|100px]]

=== Kali Linux prebuilt OS images for Pinebook Pro===

Official pre-built OS images of Kali Linux for the Pinebook Pro featuring all tools you'd expect from the distribution. It boots from microSD card and from eMMC.

'''Download location'''

Get the latest image here: [https://www.offensive-security.com/kali-linux-arm-images/ Direct download latest images from Offensive Security's website] (size: 2.0 GB)

'''Username and password'''

kali/kali

== Q4OS ==
[[File:q4os.png|right|100px]]

Q4OS is advertised as a 'fast and powerful operating system based on the latest technologies while offering highly productive desktop environment'. It boots from microSD card and from eMMC. To learn more please visit the [https://forum.pine64.org/showthread.php?tid=8385 PINE64 forum] or official [https://q4os.org/index.html Q4OS website].

'''Download location'''

Get the latest image here: [https://sourceforge.net/projects/q4os/files/stable/ Direct download latest release build from SourceForge]

'''Username and password'''

User account and password are created on first run.

== DietPi ==
[[File:dietpi.png|right|100px]]

* DietPi is a '''lightweight''', yet '''easy to setup''' and '''feature-rich''' Linux distribution, based on '''Debian'''.
* To find out more about DietPi, please visit the [https://dietpi.com/docs/ official documentation].
* Discuss the Pinebook build on the [https://forum.pine64.org/showthread.php?tid=14061 PINE64 forum thread].
* DD image (for 4 GiB micro SD card and above)
** [https://dietpi.com/downloads/images/DietPi_PinebookPro-ARMv8-Bullseye.7z Direct download from dietpi.com]
* Login with
** Username: '''root'''
** Password: '''dietpi'''

== openSUSE ==
[[File:opensuse-distribution.png|right|100px]]

'''Download location'''

Get the latest openSUSE Tumbleweed images for Pinebook Pro here: [https://en.opensuse.org/HCL:Pinebook-Pro-RK3399]

Credits to [https://bugzilla.opensuse.org/show_bug.cgi?id=1194491]
Step 1. Flash Tow-Boot[https://github.com/Tow-Boot/Tow-Boot] to SPI
Step 2. Flash openSUSE image to sd card & insert it
Step 3. When it loads grub, press e and add the following line:

devicetree /boot/dtb/rockchip/rk3399-pinebook-pro.dtb

Press ctrl + x to boot

Work : display, wifi
Not tested : bluetooth
Doesn't work : audio

You may build rpms and see if it fix issues from this repository: [https://github.com/bengtfredh/pinebook-pro-copr]

== FydeOS ==
An operating system based on the Chromium Project

https://fydeos.io/download/device/pinebook-pro

= BSD =

==NetBSD==
[[File:netbsd.png|right|100px]]

The image boots from microSD card and from eMMC. To learn more about NetBSD please visit [https://www.netbsd.org/ NetBSD main page]

'''Download location'''

Get the latest image here: [http://www.armbsd.org/arm/ Direct download from NetBSD]

'''Installation'''

Instructions concerning enabling SSH can be found [https://www.netbsd.org/docs/guide/en/chap-boot.html#chap-boot-ssh here].

'''Username and password'''

root/(none)

==OpenBSD==
[[File:Puffy_mascot_openbsd.png|right|100px]]

The image boots from microSD card and from eMMC. To learn more about OpenBSD, please visit [https://www.openbsd.org/ OpenBSD main page]

'''Download location'''

ARM64 images, (including support for Pinebook Pro), can be found here [https://www.openbsd.org/arm64.html OpenBSD arm64]

= Linux Installer Releases =

== Manjaro ARM ==
[[File:Manjaro.png|right|100px]]

The [https://gitlab.manjaro.org/manjaro-arm/applications/manjaro-arm-installer manjaro-arm-installer] script is intended to install Manjaro ARM directly to SD/eMMC cards without the need for images (including LXQT, Mate & CuboCore editions, as well as full disk encryption). Running on a Linux x86 computer, it can install Manjaro ARM directly to an empty eMMC using an eMMC to USB adapter. The script can also be run from SD to install an image to the eMMC.

== Debian ==
[[File:debian.png|right|100px]]

* Uses only the upstream kernel and firmware without special patches
* Display doesn't always work properly on first boot of installer, usually fixed after a couple tries
* Requires adding the non-free component to your /etc/apt/sources.list file and installing the "firmware-linux" package for Wi-Fi and Bluetooth support
* Installer is loaded into RAM, can install onto the same media from which it’s booted
* Supports automatic partitioning and full disk encryption through LVM
* Installer currently doesn't install a functional bootloader, leaving the installed system in an unbootable state until it's manually added (if installed to eMMC, the system cannot be booted even to an SD card unless the eMMC is physically switched off or there is U-Boot in the SPI)

[https://d-i.debian.org/daily-images/arm64/daily/netboot/SD-card-images/ The relevant files are built daily here] and may sometimes be unavailable if the build system is having issues. The "README.concatenateable_images" file provides instructions on how to combine the partition.img.gz file with the firmware.pinebook-pro.rk3399.img.gz file in order to create a DD-able image.

The official images are '''not''' recommended yet until the display begins working consistently and the installer properly installs the bootloader. Most users will want to see [[Pinebook Pro Debian Installer|Daniel Thompson's Debian Installer]] instead.

== Gentoo ==
[[File:GentooLogo.png|right|100px]]

There is a script that prepares a Gentoo arm64 stage 3 tarball for the Pinebook Pro. Unfortunately, this script is not currently functional, and requires extensive troubleshooting to make work. New instructions are currently being created and will be available here.

'''Word to the wise'''

Currently, following the instructions on the Pinebook pro gentoo github page will *not* result in a functional system. Therefore it is neccesary to follow the instructions given here. Please bear in mind that the Pinebook pro's six arm cores and 4gb of ram are extremely anemic. For example, emerging the package net-libs/webkit-gtk in order to build the minimalist web-browser "surf", a process which takes eighty minutes on an intel core i5-8250U with 8gb of ram, required eight hours of compile time,
Basic installation alone can take 24 hours of compillation, dozens of reboots, and hours of troubleshooting. After that, even installing firefox would take 17 hours.
Now that that's out of the way, we may begin the installation.

'''Preparing the bootloader'''

Installing a functional bootloader can be difficult. Luckily, the tow-boot project provides a UEFI-like experience for some arm-based devices. Furthermore, it is not neccesary install this bootloader manually, as it will continue to be useable even after the disk has been reformatted, as long as the bootloader remains unscathed.

https://manjaro.org/downloads/arm/pinebook-pro/arm8-pinebook-pro-minimal/

No-matter where you intend to install gentoo, the bootloader should always be installed on the eMMC flash, although technically the SD card slot could also be used. Either way, install any of the official Manjaro arm disk images to the internal eMMC (there's no reason not to use the minimal image, as you will not be using this OS for anything). You may use a second operating system installed on an SD-card, or the official Pine64 eMMC USB adapter. Boot into this operating system to ensure that the bootloader functions, but after that you have no further need of it.

Next, if you already have an OS on an SD card, you can use that for installing gentoo. If you don't, you may be pleasantly suprised to find that tow-boot is cabable of booting from a USB drive. Therefore, you may install the same Manjaro image to your USB drive or SD card, and select it from the boot menu. You should now have an unused but bootable OS on the eMMC, and another bootable, usable OS on your external storage.

'''Preparing the Disks'''

Log into your host device as root with the following command:

<code> sudo su </code>

Enter your password.

Let the device on which you intend to install gentoo be refered to hereafter as /dev/<gentoo>. Use the following command to prepare this disk for installation:

<code> fdisk -B /dev/<gentoo> </code>

Note: don't just copy these commands! You should substitute <gentoo> for mmcblk2 for the internal eMMC flash storage.

Note that the first block of the boot partition is block 62500. Delete all partitions, but *do not* re-format the disk. Create a new boot partition starting at 62500, and as it's size select "+1GB". Create a new swap partition. fdisk will try to start it at the beginning of the volume (before the boot partition) Instead, when it prompts you for the starting position, enter in the end sector of the boot partition. It should then tell you that this is within an existing partition, and recommend a slightly higher value. Press enter, and give for the size of the partition any value greater than "+4gb". You need this much ram to be able to suspend your system, and emerge large packages. Don't be stingey - you still have SD cards. I reccomend "+8gb".
Finally, add a root partition starting at the end sector of the swap partition, and use the rest of the disk for it. That should be 50-60 GB depending on the size of your swap and boot partitions.

Lastly, press "t" to set the type of each partition. You may set partition 1 to type 6, 2 to type 82, and 3 to type 83.

to set the partition types of the three partitions.

<code>lsblk</code>

to remind yourself which disk is /dev/<gentoo>
Write the filesystems to these three partitions with the commands:

<code>mkfs.vfat /dev/<gentoo>p1

mkswap /dev/<gentoo>p2

mkfs.ext4 /dev/<gentoo>p3</code>

This may be a slightly different format if you're installing to a usb stick.

'''Installation'''

make the directory for mounting the filesystem you just created. These should be made on the external OS.

<code>mkdir /mnt/gentoo

mount /dev/<gentoo>p3 /mnt/gentoo</code>

cd into this directory and fire up links. Navigate to gentoo.org/downloads and select the stage 3 minimal stage 3 tarball. Download it to your current directory, or move it to that directory from wherever it has been downloaded to. Once you are in the correct directory, unpack the tarball.

<code>tar xpvf stage3-arm64-<blah blah blah></code>

Mount the boot partition.

<code>mount /dev/<gentoo>p1 /mnt/gentoo/boot</code>

Chroot into the mounted directory and Install the operating system as per the AMD64 manual [https://wiki.gentoo.org/wiki/Handbook:AMD64]. Before you emerge anything, however, be sure to set your use flags as follows:

<code>nano /etc/portage/make.conf</code>

<code>MAKEOPTS="-j4 -l4"

ACCEPT_KEYWORDS="* **"

ACCEPT_LICENSE="*"

USE="X gtk bluetooth pulseaudio"
</code>

You can use your own options instead of these if you know what you're doing. It's not super difficult.

Continue installing the operating system, but stop just before emerging the @world set. I don't know if this is necessary, but I haven't had the time to try without doing this. Clone Janikk2099's github repo. It doesn't matter where, and run the script. If it fails run it a couple more times.

<code>git clone https://github.com/Jannik2099/gentoo-pinebookpro

./gentoo-pinebookpro/prepare.sh</code>

Don't follow any of Janikk's other instructions. They appear to be out of date (no offense bro). Let me be clear: DO NOT INSTALL U-BOOT. I don't know what will happen, but it won't be an improvement over the existing boot-loader so don't worry about it.

Finish installing your system until you come to the kernel.

'''Custom Kernel'''

Use sys-kernel/gentoo-kernel-bin as your kernel. You will need to manually edit the kernel configuration. First, select it as your kernel.

<code>eselect kernel list</code>

This should list only one option. Otherwise, select the number matching <code>linux-5.<whatever is latest>-gentoo-dist</code>, and cd into the kernel source directory.

<code>eselect kernel set <number>

cd /usr/src/linux</code>

Begin the kernel configuration

<code>make menuconfig</code>

At this point, you're almost on your own. I don't know a strict cause-and-effect relationship between my kernel config and the behavior of my system. For starters, just go into platform selection and deselect everything except rockchip platforms. Once you're done save your configuration and exit. Make sure boot is mounted, and your fstab is set up with your swap mounted. Make sure dracut is installed.

<code>make

make modules

make dtbs

make install

make modules install

make dtbs_install

ls /lib/modules

dracut -f --kver <name of directory in /lib/modules matching your kernel, *not* the kernel name from eselect>
</code>

emerge the package extlinux and run <code>u-boot-update</code>. Open the extlinux configuration file.

<code>nano /boot/extlinux/extlinux.conf</code>

And configure it as follows:

LABEL <label of your choice, for example GENTOO ARM>

KERNEL /<name of your vmlinuz kernel image. Include the slash, but be relative to boot, not root.>

FDT /dtbs/<kernel-version>/rockchip/rk3399-pinebook-pro.dtb

APPEND initrd=/<name of initramfs image> root=PARTUUID-<nboot partition's PARTUUID, no quotes> rw rootwait
</code>

You can use the blkid command to find the PARTUUID of every partition on the machine. None of this configuration is guaranteed to work, but it worked for me, and given enough fiddling you can get it to work as well.

Now you should reboot the machine and see if it boots into gentoo. If it does: congratulations! If not, too bad. Try again.

== Kali Linux ==
[[File:Kali.jpeg|right|100px]]

There is a script to create official Kali Linux OS images for the Pinebook Pro. The script carries out the build process in entirety and is Pinebook Pro specific.

'''Installation'''

* Please pull the latest [https://gitlab.com/kalilinux/build-scripts/kali-arm/blob/master/pinebook-pro.sh Kali Linux install script] from the project's GitLab.
* For more information regarding building the OS image please read the README instruction at https://gitlab.com/kalilinux/build-scripts/kali-arm/blob/master/README.md

== K1ss OS ==
[[File:K1ss.png|right|100px]]

There is a repository containing an unofficial port of KISS Linux to AARCH64. The tarball is built for generic aarch64, currently being tested on the Pinebook Pro. You can follow the ongoing discussion about K1ss Linux on the [https://forum.pine64.org/showthread.php?tid=9304 PINE64 forum].

'''Installation'''

* Please pull the latest [https://github.com/jedavies-dev/kiss-aarch64 K1ss Linux install script] from the project's GitHub.

== NixOS ==
[[File:nixos.png|right|100px]]

You can follow the ongoing discussion about NixOS on the [https://forum.pine64.org/showthread.php?tid=10524 PINE64 forum]. There is a good chance we will see Tier 1 support for aarch64, including the Pinebook Pro, in 2021 (see https://github.com/NixOS/rfcs/pull/87).

'''Installation'''

* This is instructions to install NixOS on the Pinebook Pro: https://nixos.wiki/wiki/NixOS_on_ARM/PINE64_Pinebook_Pro
* Please pull the latest [https://github.com/samueldr/wip-pinebook-pro samueldr's repository ] from the project's GitHub.
* [[NixOS Tutorials]]

== SkiffOS ==
[[File:SkiffOS-Icon-1.png|right|100px]]

'''Installation'''

* Instructions to build/install on the Pinebook Pro: https://github.com/skiffos/SkiffOS/tree/master/configs/pine64/book
* Please pull the latest version from the project's GitHub.
* Compiling the boot image takes approximately 30 minutes.
* Easily configure the kernel, compiler, etc with Buildroot.
* Pre-built ISOs will be available with the upcoming 2021.02 release.

[[Category:PineBook Pro]]

Pinebook Pro Installing Arch Linux ARM

2022-03-18T21:38:50Z

BenTheTechGuy: Create Arch Linux ARM installation page

These instructions can be followed to install Arch Linux ARM on an SD Card, USB Flash Drive, eMMC, or even NVMe if your U-Boot supports it.

Commands to be run as a normal user are prefixed with <code>$</code>, commands to be run as root (or with <code>sudo</code>) are prefixed with <code>#</code>.
The target device is assumed to be <tt>/dev/sdb</tt>, adjust accordingly.

== Partitioning ==
=== Flashing U-Boot ===
{{note|While any U-Boot for the Pinebook Pro can be used, this tutorial uses [https://tow-boot.org Tow-Boot].
The process of installing Tow-Boot is different from any other U-Boot, so large parts of the partitioning section will need to be changed if you want to use something else.}}

Download and extract the latest release of Tow-Boot for the Pinebook Pro from https://github.com/Tow-Boot/Tow-Boot/releases.
<nowiki>$ wget https://github.com/Tow-Boot/Tow-Boot/releases/download/release-2021.10-004/pine64-pinebookPro-2021.10-004.tar.xz</nowiki>
$ tar xf pine64-pinebookPro-2021.10-004.tar.xz

Flash Tow-Boot to <tt>/dev/sdb</tt> (replace this with the device you actually intend to use).
# dd if=pine64-pinebookPro-2021.10-004/shared.disk-image.img of=/dev/sdb bs=1M oflag=direct,sync

This creates the partition table for the device, with the first partition serving to protect Tow-Boot. Do not move or write to this partition.

=== Creating the partitions ===
Use <code>fdisk</code> to add partitions to <tt>/dev/sdb</tt>.

# fdisk /dev/sdb

Create the <tt>/boot</tt> partition.
* Type '''n''' to create a new partition.
* Press enter for partition number two.
* Press enter for the default start sector.
* Type '''+256M''' to make the new partition 256 MiB.

Create the root partition.
* Type '''n''' to create a new partition.
* Press enter for partition number three.
* Press enter for the default start sector.
* Press enter to fill the rest of the device.

Write the changes to disk.
* Type '''w''' to write the changes and exit.

=== Formatting the partitions ===
Format the <tt>/boot</tt> partition as either FAT32 or ext4.

FAT32:
# mkfs.fat -F32 /dev/sdb2
ext4:
# mkfs.ext4 /dev/sdb2

Format the root partition as any filesystem supported by Arch Linux ARM. For this example ext4 is used:
# mkfs.ext4 /dev/sdb3

== Installing the root filesystem ==
=== Mounting the partitions ===
# mount /dev/sdb3 /mnt
# mkdir /mnt/boot
# mount /dev/sdb2 /mnt/boot

=== Downloading and verifying the rootfs tarball ===
Download the tarball and its PGP signature.
<nowiki>$ wget http://os.archlinuxarm.org/os/ArchLinuxARM-aarch64-latest.tar.gz{,.sig}</nowiki>

Import the Arch Linux ARM signing key.
$ gpg --keyserver keyserver.ubuntu.com --recv-keys 68B3537F39A313B3E574D06777193F152BDBE6A6

Verify the tarball's authenticity.
$ gpg --verify ArchLinuxARM-aarch64-latest.tar.gz.sig

Verifying the authenticity of the tarball protects you in two ways:
# Makes sure the tarball came directly from Arch Linux ARM and was not tampered with
# Prevents you from using a corrupt tarball (for example from an interrupted download)

=== Extracting and configuring the root filesystem ===
==== Extracting the root filesystem ====
# bsdtar -xpf ArchLinuxARM-aarch64-latest.tar.gz -C /mnt

==== Editing fstab ====
Find the partitions' UUIDs with <code>blkid</code>.
# blkid /dev/sdb2 /dev/sdb3

Example output:
/dev/sdb2: UUID="21bbff3f-b82e-416e-93c8-e6d44c3daf82" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="be571200-1a56-5d4c-9a5b-88a5f36a295e"
/dev/sdb3: UUID="d22c5207-0f87-4fe9-91ce-6d6e0fb9a13e" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="1d3603f4-bcd4-3c41-8d6d-23e65b405e5a"

Add the following lines to <tt>/mnt/etc/fstab</tt>, substituting the example UUIDs with those you received from <code>blkid</code>.
UUID=d22c5207-0f87-4fe9-91ce-6d6e0fb9a13e / ext4 defaults 0 1
UUID=21bbff3f-b82e-416e-93c8-e6d44c3daf82 /boot ext4 defaults 0 2

==== Creating extlinux.conf ====
Create a file <tt>/mnt/boot/extlinux/extlinux.conf</tt> with the following contents, replacing the example UUID with the one for <tt>/dev/sdb3</tt> from <code>blkid</code>.
default arch
menu title Boot Menu
prompt 0
timeout 50

label arch
menu label Arch Linux ARM
linux /Image
fdt /dtbs/rockchip/rk3399-pinebook-pro.dtb
append initrd=/initramfs-linux.img root=UUID=d22c5207-0f87-4fe9-91ce-6d6e0fb9a13e rw

== Booting and finishing setup ==
Boot into Arch Linux ARM and log in as <tt>root</tt> with password <tt>root</tt>.

Initialize the pacman keyring.
# pacman-key --init
# pacman-key --populate archlinuxarm

For security, change the default passwords for root and the default user <tt>alarm</tt>.
# passwd
# passwd alarm

Congratulations, you have now installed Arch Linux ARM on your Pinebook Pro!

Pinebook Pro Troubleshooting Guide

2022-03-11T18:18:54Z

BenTheTechGuy: Fix spelling error, clear up confusion about NVMe issue that's been solved for some time, and update firmware link

=Useful Links=

[[Pinebook_Pro|Back to the main Pinebook Pro page]]

[[Pinebook_Pro_Hardware_Accessory_Compatibility|Hardware Compatibility page]]

[[Pinebook Pro Software Release]]

=Tips, tricks and other information for troubleshooting your Pinebook Pro=

If something has gone wrong, the key thing is remain calm and not do anything hasty and make things worse, particularly when flashing the eMMC or firmware. Try and make a record of all the things you did in the run-up to the problem (even to the point of using a camera to take a note of errors on the screen, this record can be vital later).

=Manjaro Updates Fail With 404=
If you have an old Manjaro installation then it will have the wrong repositories/mirrors set up and they won't work. Set up new repositories by following these instructions:
https://forum.manjaro.org/t/another-mirror-transition-manual-intervention-required/132302

=Power And Boot=

== New from the factory - Pinebook Pro won't boot / power on ==
* Some Pinebook Pros came from the factory with the eMMC switch in the disabled position. It should be switched towards the back / hinge to enable the eMMC.
* The eMMC may have come loose during shipment. [[Pinebook Pro#Accessing the Internals - Disassembly and Reassembly|Open the back]] and verify that the eMMC is firmly seated.
* You may want to try unplugging the SD card daughterboard ribbon cable and see if it powers on (remove the battery and peel off a bit of the tape before unplugging it to avoid damage). If it does, try reseating it on both sides. It might have come loose during shipping.
* It's possible that your eMMC is empty from the factory. Simply [[NOOB|create]] a bootable [[Pinebook_Pro#Pinebook_Pro_images|SD card]] and see if your Pinebook Pro [[Pinebook_Pro#Boot_sequence_details|boots]]. If so, you can then [[NOOB|write]] an OS image to the eMMC.

== Pinebook Pro will not power on after toggling the eMMC enable/disable switch ==
* This may happen if you meant to toggle the UART/Headphone switch (9) towards touchpad for headphone use and instead you toggled the eMMC enable/disable switch (24).
* After reenabling eMMC by toggling switch (24) towards hinge, if Pinebook Pro does not turn on then press the RESET button (28). It is clearly marked 'reset' on the PCB board.

== Pinebook Pro will not power on after removing and replacing EMI shielding ==
* Closely inspect that the shielding is firmly seated in the clips on all sides. You can be seated in the clips on one axis, and have missed on an another axis.

== Pinebook Pro won't boot when using UART console cable ==
* If you're using the [[Pinebook_Pro#Using_the_UART|UART]] cable sold on the [https://pine64.com/product-category/pinebook-pro/ Pine Store], you may want to see if it boots after you disconnect it. Some users report that custom-made cables based on FTDI UART adapters do not cause this issue.
* Make sure your USB to serial UART device is 3.3v. Many are 5v and some even +-12v. Pinebook Pro's only support 3.3v and may act eratically when using higher voltage. Further, higher voltage could permananetly damage the Pinebook Pro's SoC.

== Pinebook Pro will not sleep with lid closed ==
A problem with the positioning of the lid magnet has been identified by several forum users in mid-2020 models of the Pinebook Pro. The magnetic field from the lid magnet operates a hall effect sensor located on the daughterboard (smallboard), which causes the Pinebook Pro to sleep when the lid is closed. If the magnet is not positioned correctly, the Pinebook Pro will not sleep when the lid is fully closed, but may sleep if the lid is open about an inch. If you experience this problem, repositioning of the magnet may be necessary.
=== Lid Magnet Repositioning Step-by-Step ===
*Read these steps thoroughly before starting. This is a somewhat laborious process involving fragile parts!
# Remove bottom cover.
# Disconnect LCD and webcam ribbon cable from main board. Flip the small black strip on the connector upward and the ribbon cable can be easily removed. Do not pull the cable out without first raising the black retaining mechanism.
# Remove the small black plastic standoffs on each hinge and set aside.
# Remove the three screws from each hinge on the display assembly.
# Move the hinges upward to a 90 degree angle independently from the main body. Then lift the main body to the same 90 degree angle and you should be able to separate the display assembly from the main body. Set the main body aside.
# Remove the plastic hinge cover on the display assembly. There's not really an easy way to do this, just work slowly and deliberately so as not to damage the sensitive cable inside. Start from either end and work your way inward. Use a small flathead screwdriver or similar tool to get started.
# Remove the hinges from the display assembly.
# Remove the rubber bumpers at the top corners of the display assembly to expose two screws. Remove the screws.
# Starting at the corners, separate the bezel from the lid. The clips that hold it in place are similar to those found on the hinge cover. Again, slow deliberate work will get it done. Work from the top down. Take care not to damage the cables in the bottom.
# With the bezel separated from the lid, feed the cable through the slot and set the bezel aside.
# Without removing the LCD panel completely, lift and move the panel slightly to the left, taking care not to damage the cable running underneath up to the webcam. This will give you room to remove the magnet without risking damage to the panel.
# The magnet is a silver colored bar near the bottom right side of the lid. Pry the magnet out with a small flathead or similar tool and set it aside. There is some adhesive but it's not very strong.
# Put the LCD panel back where it belongs. Note the foam pads on either side of the panel. The magnet is the same width as the foam pad that keeps the panel in place, and should fit perfectly in the same channel.
# The magnet should be placed about 1 to 1.5cm lower than where it was originally. There should be no need for adhesive, as the magnet will stick to the LCD panel. For reference, the hall effect sensor that the magnet interacts with is in between the USB port and audio jack.
# Reassemble using these steps in reverse order.

Your PineBook Pro should now sleep properly when the lid is closed.

=WiFi And Bluetooth=

== WiFi issues ==
* First, check the privacy switches to make sure your WiFi is enabled. They are persistant. See [[Pinebook_Pro#Privacy_Switches|Privacy Switches]]
* Next, you may have to modify the <code>/etc/NetworkManager/NetworkManager.conf</code> as root user, and replace <code>managed=false</code> with <code>managed=true</code>. Then reboot.
* For connections that drop and resume too often, it might be due to WiFi power management from earlier OS releases. Later OS releases either removed WiFi power management, or default to full power. (Power management can be turned off via command line with <code>iw dev wlan0 set power_save off</code> or <code>iwconfig wlan0 power off</code>, although it is not persistent through re-boot.)
* For connections that drop under load on the default Debian, remove <code>iwconfig wlan0 power off</code> in the file <code>/etc/rc.local</code>.
* If WiFi is un-usable or often crashes when using an alternate OS, then it might because its WiFi firmware is not appropriate for the WiFi chip in the Pinebook Pro. Try the latest firmware patch from [https://gitlab.manjaro.org/tsys/pinebook-firmware/tree/master/brcm https://gitlab.manjaro.org/tsys/pinebook-firmware/tree/master/brcm]
* After re-enabling WiFi via the privacy switch, you have to reboot to restore function. There is a work around for the default Debian, (and may work with others);
        <code>sudo tee /sys/bus/platform/drivers/dwmmc_rockchip/{un,}bind <<< 'fe310000.dwmmc'</code>
* On extremely rare occasions, the WiFi antenna connection is loose. To fix, simply open up the bottom, re-connect the WiFi antenna cable. This may show up as any of the following symptoms:
** Can't connect to any network, but the network manager software sees the WiFi device, (so it has not been disabled by the Privacy Switch)
** Very limited range, meaning you can make a connection if the Pinebook Pro is next to the WiFi router. But not the next room.
** Unreliable connections, that are also limited by range.

== Bluetooth issues ==

* When connecting a Bluetooth device, such as a Bluetooth mouse, it does not automatically re-connect on re-boot. In the Bluetooth connection GUI, there is a yellow star for re-connect on boot. Use that button to enable a persistent connection. It can be changed back later.
* Bluetooth-attached speakers or headset require the pulseaudio-module-bluetooth package. If not already installed, it can be installed with a package manager or using the following:
<pre>sudo apt-get install pulseaudio-module-bluetooth</pre>
* When using Bluetooth-attached speakers or headset and 2.4Ghz WiFi at the same time, you may experience stuttering of the audio. One solution is to use 5Ghz WiFi if you can. Or you may try using a different 2.4Ghz channel, perhaps channel 1 or the top channel, (11 in the USA, or 13/14 in some other countries).

= Sound issues =

* Many reports of no sound are due to the OS, incorrect settings, or other software problems (eg. PulseAudio). So first test to see if it is a software or hardware problem, by trying another OS via SD card. (For example, if Debian is installed on the eMMC, try Ubuntu on SD.)
* If you cannot get sound from the headphone jack, but can get sound from the speakers, then the headphone / UART console switch may be set to the UART mode. You can open the back and check the position of the switch. If set to UART mode, switch it to headphone mode. See the parts layout for the location and correct position of the switch.
* When using the USB C alternate DisplayPort mode, it is possible that the audio has been re-directed through this path. If your monitor has speakers, see if they work.
* See [https://gitlab.manjaro.org/manjaro-arm/packages/community/pinebookpro-post-install/blob/master/asound.state manjaro-arm/pinebookpro-post-install /var/lib/alsa/asound.state] for some ALSA tweaks.
* See [https://gitlab.manjaro.org/manjaro-arm/packages/community/pinebookpro-audio manjaro-arm/pinebookpro-audio] for how to handle 3.5mm jack plug/unplug events with ACPID.
* Serveral users have reported that one internal speaker had reversed polarity. Thus, sound from the speakers is like an echo effect.
** There is a software fix using alsamixer and then enable either "R invert" or "L invert", however, now the headphones have incorrect audio.
** The permanent fix is to re-wire one speaker, though this requires soldering small wires.
* Sound playback may be affected by the "mirroring" between the right and left channels, which results in distorted sound image. The root cause is the [https://linux.die.net/man/1/alsamixer ALSA mixer] setting named "DAC Stereo Enhancement", which needs to be changed to 0% to fix this issue. Please see [https://forum.pine64.org/showthread.php?tid=12631&pid=87372#pid87372 this forum post] for further information.

= NVMe SSD issues =

Many PineBook Pro users have reported issues with NVMe SSD drives, including random Linux lockups and crashes. Some of these issues are related to the [https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=712fa1777207 RK3399's errata] that disables Gen2 (5 GT/s) speed for the PCI Express link used by the NVMe SSD, reducing it down to Gen1 speed (2.5 GT/s). However, Linux distributions that use Linux kernels older than version 5.12 still configure the PCI Express link to run at Gen2 speed, which requires [https://forum.pine64.org/showthread.php?tid=11683 manual reconfiguration] to Gen1 speed in case system instability is experienced. See also this [https://patchwork.kernel.org/project/linux-rockchip/patch/20200423150510.6216-1-pgwipeout@gmail.com/ related discussion]. This issue does not affect distros with recent (newer than May 2021) kernels such as Manjaro ARM which seem to work with no modifications.

Some PineBook Pro users have reported issues with the default settings for the APST (Autonomous Powe State Transition) power saving, which cause an NVMe drive to disappear from the system or lock up after a certain period of time. Please see [https://forum.pine64.org/showthread.php?tid=11337&pid=87711#pid87711 this forum thread] for further information.

= Keyboard and trackpad =

== Random Duplicated Key-Presses ==

Whether caused by an error in the Hailuck Keyboard firmware, or a physical defect in the membrane, the Pinebook Pro keyboard may randomly register some key-presses twice. The solution to this problem is trivial. Simply run the following command:

<code>xkbset bouncekeys 20</code>

If this return the following error:

<code>bash: xkbset: command not found</code>

Or some other similar error, you will need to install the command. It can most likely be found in your distro's repository.

You may substitute some other value for 20 -- this number denoting the time in milliseconds during which successive, duplicate key-presses will be rejected -- with any value of your choice. If you are still receiving duplicates, consider increasing the number -- perhaps by half. If you are consistently writing "aple", try decreasing this number -- perhaps by 25%.

== Keys not registering / missing keys when typing ==
This issue occurs when your thumb or edge of the palm makes contact with left or right tip of the trackpad when you type. This is due to the palm rejection firmware being too forceful. Instead of only disabling the trackpad, so your cursor does not move all over the screen, it disables both the trackpad and the keyboard.

Using Fn+F7 to disable the touchpad will keep it from also disabling the keyboard.

A [[Pinebook_Pro#Trackpad|firmware update]] has been released to address this.

== Key mapping ==
* See this [https://gitlab.manjaro.org/manjaro-arm/packages/community/pinebookpro-post-install/blob/master/10-usb-kbd.hwdb /etc/udev/hwdb.d/10-usb-kbd.hwdb] for some key mapping tweaks

== Pinebook Pro gets stuck after first reboot in Trackpad Firmware Update ==
This refers to the firmware update shown here:
https://github.com/dragan-simic/pinebook-pro-keyboard-updater#update-all-firmware-images
* If the system is not responding after the 1st reboot, it might be easiest to do a system restore or boot an sdcard-only OS, and follow up by running the second step of the trackpad firmware update with a USB keyboard and mouse plugged in
* System restore https://forum.pine64.org/showthread.php?tid=8229
* Firmware update https://github.com/dragan-simic/pinebook-pro-keyboard-updater#update-all-firmware-images

== ANSI Fn + F keys wrong for F9, F10, F11 and F12 ==

There appears to be a minor firmware issue for ANSI keyboard models of the Pinebook Pro. Some discussion and fixes have been proposed;
* Discussion thread [https://forum.pine64.org/showthread.php?tid=8744&pid=57678#pid57678 Fn + F keys screwy for F9, F10, F11 and F12]
* Proposed fix [https://github.com/ayufan-rock64/pinebook-pro-keyboard-updater/issues/14#issuecomment-576825396 (ANSI) Fn + F(9-12) has wrong assignment after firmware update #14]

= USB docks & USB C alternate mode video =

The Pinebook Pro uses the RK3399 SoC (System on a Chip). It supports a video pass through mode on the USB C port using DisplayPort alternate mode. This DisplayPort output comes from the same GPU used to display the built-in LCD.

Here are some selection criteria for successfully using the USB C alternate mode for video:
* The device must use USB C alternate mode DisplayPort. Not USB C alternate mode HDMI, or other.
* The device can have a HDMI, DVI, or VGA connector, if it uses an active translater.
* If USB 3 is also desired from a USB dock, the maximum resolution, frame rate and pixel depth is reduced to half the bandwidth. For example, 4K @ 30hz instead of 60hz.
* USB docks that also use USB C alternate mode DisplayPort will always have USB 2 available, (480Mbps, half-duplex).

=Screen=

Also see above about external screen using USB-C adaptor

== After changing builtin LCD resolution, blank screen ==
Some people find that the text or icons are too small, so they attempt to change the resolution of the built-in display. Afterwards, the display is blank.
Use the following to fix when logged into a text console as yourself, pressing Control-Alt-F1 through F6. After listing the resolutions, select the native resolution, (1920x1080 aka 1080p).

<pre>export DISPLAY=:0.0
xrandr -q
xrandr -s [resolution]</pre>

Once the screen resolution is restored, try using the software settings to configure the desired screen scaling.

If the above fix did not work, you can try this:
* Using a text console, (Control-Alt-F1), login with your normal user ID
* Edit the file <code>nano ~/.config/monitors.xml</code>
* Change the "width" value to "1920"
* Change the "height" value to "1080"
* If there is more than one monitor configuration listed, edit that one too. Be careful to make no other changes. If needed, exit without saving and re-edit.
* Save the file and exit.
* Login using the GUI and test
* If you are still loggied in via the GUI, you will have to reboot using <code>sudo shutdown -r now</code>. After the reboot, you should be able to login to the GUI login and have the resolution back to normal.

After restoring the usability of your Pinebook Pro's graphical screen, also see [[Pinebook Pro#Improving readability|this section]] on improving readability and usability.

=Outer Shell=

== Cracks in the plastic ==
There have been multiple reports of cracks in the plastic keyboard and trackpad part of the case. These are generally near:
* Hinges
* USB ports
* Top side, around the corners

This seems to apply to the first batches in 2019. Later versions of the keyboard and trackpad have used better plastic. With replacements now in the Pine64 Store, it's possible to simply order a replacement.

There have been a few reports of cracks in the plastic around the LCD display, but these appear to be less common. There are replacement LCDs with top cases available in the Pine64 Store.

[[Category:PineBook Pro]][[Category:Guide]]

Pinebook Pro Hardware Accessory Compatibility

2022-03-11T18:01:49Z

BenTheTechGuy: Add USB WiFi dongle and microSD card

Please test as many things as you can find with your [[Pinebook Pro]] and share the results here. Some devices which should work don't!

= Storage =

== NVMe SSD drives ==
Only PCI Express M.2 drives can work, due to the available connectivity of the Pinebook Pro. Consequently, SATA or USB M.2 cards will not work.

You need to buy and install the M.2 adapter in order to fit one, please see [[Pinebook Pro#Using the optional NVMe adapter]]

Please see [[Pinebook Pro Troubleshooting Guide#NVMe SSD issues|a separate section]] that describes reported issues with the NVMe drives in PineBook Pro.

{| class="wikitable sortable"
!Type || Make/Model || Size || Hardware IDs || Result || Notes || Power options Active only || Save power setting?
|-
| 2280 || Corsair MP300 || 120 GB || CSSD-F120GBMP300 || good || || PS 0: 3.00W PS 1: 2.00W PS 2: 2.00W PS 3: 0.1W PS 4: 0.005W APSTE Disabled by default ||
|-
| 2280 || Corsair MP400 || 1 TB || CSSD-F1000GBMP400R2 || fail || || PS 0: 5.55W PS 1: 4.49W PS 2: 3.97W PS 3: 0.0490W PS 4: 0.0018W APSTE Disabled by default ||
|-
| 2280 || Crucial P1 || 1 TB || CT1000P1SSD8 || good || With PS 2 and APST impact on battery life seems to be minimal. Running powerstat seems to confirm little additional power draw. || PS 0: 9.00W PS 1: 4.60W PS 2: 3.80W PS 3: 0.0300W PS 4: 0.0030W APSTE: enabled by default || Yes
|-
| 2280 || Crucial P2 || 500GB || CT500P2SSD8 || ok || problems loading from u-boot [http://u-boot.10912.n7.nabble.com/NVMe-boot-issues-on-RockPro64-td424863.html] || PS 0: 3.50W PS 1: 1.90W PS 2: 1.50W PS 3: 0.0700W PS 4: 0.0020W APSTE: enabled by default || No
|-
| 2280 || Kingston A2000 || 250 GB || SA2000M8250G || good || || PS 0: 9.00W PS 1: 4.60W PS 2: 3.80W PS 3: 0.045W PS 4: 0.004W APSTE: enabled by default || Yes
|-
| 2280 || Kingston A2000 || 1 TB || SA2000M81000G || good || || same as 250 GB || Yes
|-
| 2280 || Kingston KC2500 || 2 TB || SKC2500M82000G || good || PCB too thick for supplied holder nut, used another one || same as A2000 models above || Yes
|-
| 2242 || Toshiba OCZ RC 100 || 240 GB || RC100-M22242-240G || good || || ||
|-
| 2242 || Lexar NM520 || 256 GB || LNM520-256RBNA || good ||For some data on power use and performance, see [https://forum.pine64.org/showthread.php?tid=9029 here.] || PS 0: 3.05W PS 1: 2.44W PS 2: 2.02W || No. See [https://forum.pine64.org/showthread.php?tid=8737&pid=56481#pid56481 workaround].
|-
| 2280 || XPS SX8200 || 512 GB || ASX8200PNP-512GT-C || good || Performed [https://forum.pine64.org/showthread.php?tid=8322 these] steps for physical installation. Currently rooting from drive. || ||
|-
| 2280 || Intel 660p M.2 || 512 GB || SSDPEKNW512G8X1 || good || PS 1 (2.70W) will work without issues, even under heavy load. Recommended over PS 2, as PS 2 will incur an additional 80% performance penalty. APSTE shows enabled but drive does not support it. || PS 0: 3.50W PS 1: 2.70W PS 2: 2.00W || No
|-
| 2280 || Intel 660p M.2 || 1 TB || SSDPEKNW010T8X1 || good || || PS 0: 4.00W PS 1: 3.00W PS 2: 2.20W APSTE Disabled by default || No
|-
| 2280 || Intel 660p M.2 || 2 TB || SSDPEKNW020T8 || good || [https://forum.pine64.org/showthread.php?tid=7524&pid=49300#pid49300 Performance tests results] || PS 0: 5.50W PS 1: 3.60W PS 2: 2.60W PS 3: 0.0300W PS 4: 0.0040W || No
|-
| 2280 || Intel 760p M.2 || 128 GB || SSDPEKKW128G8 || good || Firmware Revision 004C || PS 0: 9.00W PS 1: 4.60W PS 2: 3.80W PS 3: 0.045W PS 4: 0.004W APSTE: disabled by default with 4.4 kernel (mrfixit Debian), enabled by default with 5.6 kernel (Manjaro KDE) || Yes
|-
| 2280 || Intel 760p M.2 || 256 GB || SSDPEKKW256G8 || good || Firmware Revision 004C || PS 0: 9.00W PS 1: 4.60W PS 2: 3.80W PS 3: 0.045W PS 4: 0.004W Need to use lower power. ||
|-
| 2280 || integral 256GB SSD M.2 2280 NVME || 256 GB || INSSD256GM280NM1 || usable || || PS 0: 9.00W || No
|-
| 2280 || PNY CS1030 || 500GB || CS1030 || good || || PS 0: 4.50W PS 1: 2.70W PS 2: 2.16W PS 3: 0.0700W PS 4: 0.0050W APSTE: Enabled||
|-
| 2280 || PNY CS3030 || 1 TB || M280CS3030-1TB-RB || || || PS 0: 10.57W PS 1: 7.00W PS 2: 5.22W PS 3: 0.0490W PS 4: 0.0018W APSTE: ||
|-
| 2280 || Samsung 970 EVO Plus || 250 GB || MZ-V7S250BW || fail || Tested on Manjaro-ARM as root drive. Limited to PS 2 and Volatile Write Cache off gives the most stable results, but it will still hang on a hdparm test. || ||
|-
| 2280 || Samsung 970 EVO Plus || 500 GB || MZ-V7S500 || fail || Too power hungry? || PS 0: 6.2W PS 1: 4.3W PS 2: 2.1W ||
|-
| 2280 || Samsung 970 EVO || 1 TB || MZ-V7E1T0BW || fail || Too power hungry? || ||
|-
| 2280 || Samsung 970 PRO || 1 TB || MZ-V7P1T0BW || good || || PS 0: 6.20W PS 1: 4.30W PS 2: 2.10W PS 3: 0.04W PS 4: 0.005W APSTE: enabled by default || Yes
|-
| 2280 || Silicon Power P34A60 || 1TB || SP001TBP34A60M28 || Usable || Power eager, but doesn't seem to use all 9W all the time, only under heavy I/O || PS 0: 9W || N/A
|-
| 2280 || Silicon Power P34A60 || 256 GB || SPCC M.2 PCIe SSD || detected || ASIN B07ZH6QR8Q "Silicon Power PCIe M.2 NVMe SSD 256GB Gen3x4" / PCIe A60 || PS 0: 6.77W PS 1: 5.71W PS 2: 5.19W APSTE Enabled by default || No
|-
| 2280 || Silicon Power P34A60 || 256 GB || ??? || fail || Isn't detected || ||
|-
| 2280 || Sabrent Rocket || 256 GB || SB-ROCKET-256 || good || || || No
|-
| 2242 || Sabrent Rocket Nano || 512 GB || SB-1342-512 || good* || No touchpad issues, didn't trim NVME adapter board. (*Might be too power hungry. More testing needed.) || ||
|-
| 2242 || Sabrent Rocket || 1 TB || SB-RKTQ-1TB || good || || PS 0: 5.55W PS 1: 4.49W PS 2: 3.97W PS 3: 0.049W PS 4: 0.0018W APSTE: available || Yes
|-
| 2280 || MyDigitalSSD SBXe || 960 GB || || good || || APST enabled Power states N/A || N/A
|-
| 2280 || HP SSD EX900 || 250GB || || good || No low-power modes available || ||
|-
| 2280 || HP SSD EX950 || 512GB || || good || Unsure about low-power modes || ||
|-
| 2280 || WD BLUE SN550 || 1TB || WDC WDS100T2B0C-00PXH0 || good || Booted successfully from NVMe (Bionic MATE) || PS 0: 3.50W PS 1: 2.70W PS 2: 1.90W PS 3: 0.0250W PS 4: 0.0050W APSTE Disabled by default || N/A
|-
| 2280 || WD Blue SN550 || 500GB || WDC WDS500G2B0C-00PXH0 || good || || PS 0: 3.50W PS 1: 2.40W PS 2: 1.90W APSTE enabled by default with 5.9 kernel (Manjaro XFCE) || No
|-
| 2280 || WD Blue SN500 || 500GB || WDS500G1B0C || fail || Works OK on power state 2 (2.5W), but hangs the system whenever there is intense IO (peak draw) on the drive || ||
|-

| 2242 || WD PC SN520 || 256GB || - || fail || Power LED Flashes. Nothing else happens. || ||
|-
| 2280 || WD PC SN730 || 512GB || SDBPNTY-512G-1032 || good || No touchpad issues. Works after latest updates. ||APST enabled by default PS 0: 5.50W PS 1: 3.50W PS 2: 3.00W PS 3: 0.0700W PS 4: 0.0025W || No
|-
| 2280 || WD BLACK SN750 || 250GB || WDS250G3X0C-00SJG0 || good || No touchpad issues, didn't trim NVME adapter board. || APSTE disabled by default PS 0: 5.00W PS 1: 3.50W PS 2: 3.00W||
|-
| 2280 || WD BLACK SN750 || 500GB || WDS500G3X0C-00SJG0 || good || No tp issues. had to charge battery for 20% initially. || APSTE disabled by default PS 0: 5.50W PS 1: 3.50W PS 2: 3.00W PS 3: 0.07W PS 4: 0.0025W||
|-
| 2280 || WD BLACK SN750 || 1TB || WDS100T3X0C-00SJG0 || mixed || Drive works as expected (so far) though with 50% reduction in battery life. Unable to set power mode (due to APST being enabled?). Also unable to suspend PineBook Pro with NVMe drive attached. From dmesg: rockchip-pcie f8000000.pcie: PCIe link enter L2 timeout! PM: dpm_run_callback(): rockchip_pcie_suspend_noirq+0x0/0x100 returns -110 PM: Devvice f8000000.pcie failed to suspend noirq: error -110 PM: no irq suspend of devices failed || APST enabled by default PS 0: 6.00W PS 1: 3.50W PS 2: 3.00W PS 3: 0.1000W PS 4: 0.0025W || No
|-
| 2242 || KingSpec NE-512 || 512 GB || NE512 || good || || APST enabled Power states N/A || N/A
|-
| 2230 || Kioxia BG4 256GBTB|| 256 GB || KBG40ZNS256G || good || || APST enabled by default Power states PS 0: 3.60W PS 1: 2.60W PS 2: 2.20W PS 3: 0.005W PS 4: 0.005W ||
|-
| 2280 || Patriot P300 || 256 GB || P300P256GM28US || good || Booted successfully with / on NVMe and /boot on eMMC (Armbian Buster) || APSTE disabled by default PS 0: 4.50W PS 1: 2.70W PS 2: 2.16W PS 3: 0.07W PS 4: 0.002W||
|-
| 2280 || Team Group MP33 || 128 GB || TM8FP6128G0C101 || good || || ||
|-
| 2280 || Team Group MP34 || 512 GB || TM8FP6512G0C101 || fail ||APST enabled by default and scripts do not change the power mode. Higher power consumption modes cause the PBP to crash || PS 0 5.55W PS 1 4.49W PS 2 3.97W PS 3 0.0490W PS 4 0.0018W ||No
|-
| 2280 || Digifast Ace || 256 GB || DGFA256M2L01 || good ||No touchpad issues. Board not trimmed. || PS 0 6.77W PS 1 5.71W PS 2 5.19W PS 3 0.0490W PS 4 0.0018W ||Yes
|-
| 2280 || Toshiba XG6 || 256 GB || KXG60ZNV256G || good || || PS 0: 6.00W PS 1: 2.70W PS 2: 1.30W PS 3: 0.0500W PS 4: 0.0050W PS 5: 0.0030W APSTE: enabled by default || No
|-
| 2280 || SK hynix Gold P31 gen3x4 || 500 GB || SHGP31-500GM-2 || good || SvenKiljan's arch+towboot with 5.15.8-1-manjaro arm kernel ps1:574.65MB/s (ps0 0.500-2.1GB/s)343 MB/s r/w ps2:63.78-187/45.1 MB/s r/w on encrypted root /tmp || PS 0: 6.30W PS 1: 2.40W PS 2: 1.90W PS 3: 0.0500W PS 4: 0.0040W APSTE: enabled || No, see "workaround(cron job+nvme-cli)"
|-
|}

== microSD Cards ==
{| class="wikitable sortable"
!Type || Make/Model || Hardware IDs || Result || Notes
|-
|SD Card || Samsung Evo Select 512GB || MB-ME512GA/AM || good ||
|-
|SD Card || Samsung Evo Plus 64GB || || good || Hdparm tested 44MBps read speeds
|-
|SD Card || Sandisk Ultra 400GB || || good || Works fine as a storage extension. Mounted for pictures, etc.
|-
|SD Card || Sandisk Ultra 16GB || || fail || Works for a short period of time but locks up completely after a certain amount of written data
|-
|SD Card || Sandisk Ultra 64GB (Old from 2015) || || fail || ^
|-
|SD Card || Sandisk Ultra Plus 64GB || || good ||
|-
|SD Card || Sandisk Ultra Plus 128GB || || good ||
|-
|SD Card || Sandisk Extreme 64GB || || good || Speeds seem a little slow (67MB/s read compared to 160MB/s rating) but response time and reliability is good
|-
|SD Card || Sandisk Extreme Pro 64GB || || good ||
|}

= USB hardware =

== USB Card Readers ==

Standalone card readers only, please; see below for multifunction devices.

{| class="wikitable sortable"
!Type || Make/Model || Hardware IDs || Result || Notes
|-
|USB-2 SDHC reader || Sandisk MobileMate+ || 0781:b2b3 || good ||
|-
|USB-3 SDHC/CF reader || Transcend TS-RDF8K || 8564:4000 || good ||
|}

== USB Networking ==

Standalone network devices only, please; see below for multifunction devices

{| class="wikitable sortable"
!Type || Make/Model || Hardware IDs || Result || Notes
|-
|USB-2 Fast Ethernet adapter || Realtek RTL8152 || 0bda:8152 || good ||
|-
|USB-2 Ethernet adapter || ASIX AX77882 || 0b95:7720 || good ||
|-
|USB 3 to Gigabit Ethernet Adapter || Pluggable USB 3.0 to Ethernet Gigabit (ASIX AX88179 chipset) || 0b95:1790 || good ||
|-
|USB WiFi Dongle || TP-Link TL-WN725N || 0bda:8179 || good || RTL8188EUS, Driver=rtl8188eu from MrFixit stock Debian, works better than internal Broadcom, but signal still not great, https://www.amazon.com/gp/product/B008IFXQFU/
|-
|USB WiFi Dongle || Shenzhen Dudes Tech #8541553244 || 0bda:c811 || mixed || plug/play on stock Armbian Buster with driver rtl8821cu; could not get operating driver built on MrFixit Debian or Manjaro KDE Plasma. Works 2x+ better than internal Broadcom on Armbian. https://www.amazon.com/gp/product/B07F595V22/
|-
|USB WiFi Dongle || Edimax EW-7811Un || 7392:7811 || good || Plug and play on Manjaro ARM and stock Debian from official images with driver rtl8192cu. https://www.amazon.com/gp/product/B003MTTJOY/
|}

== USB Multifunction Devices ==

{| class="wikitable sortable"
!Type || Make/Model || Hardware IDs || Result || Notes
|-
|USB-C Hub || Samsung EE-P5000 || || Power is passed through from hub to Pinebook Pro; Ethernet, HDMI, and USB-A do not work ||
|-
|USB-C Hub || Insignia NS-PU378CHM || || Power is passed through from hub to Pinebook Pro; USB-A works; HDMI does not work ||
|-
|USB-C Hub || Dell WD19TB || || Power is passed through from hub to Pinebook Pro; Ethernet and USB-A work; Neither Display Port nor HDMI work; audio not tested ||
|-
|USB-C Hub || Totu 8-in-1 || 058f:8468, 2109:0817 USB3, 1a40:0801, 2109:2817 USB2, bda:8153 RTL8153 Gigabit Ethernet || Network, USB, Card Reader, Power Good, HDMI Not Working || Amazon Smile [https://smile.amazon.com/gp/product/B07FX2LW35/]
|-
|USB-C Hub || Delock 87721 || || Network Works, USB Works, Card Reader not tested, Power Good, HDMI Works but does not show as an extra output in X. It just mirrors the default display || Delock 87721 [https://www.delock.de/produkte/G_87721/merkmale.html?setLanguage=en]
|-
|USB-3 combo hub (network, card slots, usb ports) || generic || 05e3:0610 hub, 0bda:8153 gigE, 05e3:0743 card reader || Network good, usb ports good, card reader good ||
|-
|USB-C combo hub (network, card slots, usb ports) || generic || 05e3:0612 hub, 0bda:8153 realtek gigE || Network good, usb ports fail, card reader fail ||
|-
|5-1 USB-C hub || [https://www.aliexpress.com/item/32954358411.html from aliexpress] || 05e3:0626 hub || HDMI, Network, USB-3, USB-C PD [http://www.sympato.ch/~dryak/files/usbc-dock.jpg good] || Might need changing orientation or USB-C cable
|-
|4 Port USB 3 NIC || Delock 62966 || || good || 4 individually controllable Gigabit Ethernet Ports. Consider using it with own power supply
|-
|USB-C combo hub || [https://www.amazon.com/gp/product/B07XKRGQQ2/ from Amazon] || 0c76:161f 0c45:6321 2109:0813 1a40:0101 || good || Everything works: AltMode DP, Ethernet, SD card, USB-A and C, and charging using the stock Debian, and Ubuntu.
|-
|USB-C dock || i-Tec USB-C Metal Nano Dock 4K HDMI w/ LAN || 0bda:0411 hub, 0bda:8153 ethernet || mixed || plug & play with Manjaro, HDMI tested w/ fullHD only, works but only in one polarity. Sound output works, USB hub works. HDMI output may not be recognized by Plasma if dock is connected with HDMI port disconnected. NIC recognized by kernel, but untested if link actually works. USB power delivery works only in one polarity. Unfortunately HDMI works with opposite polarity than USB PD.
|-
|USB-C dock || Planet Computers Gemini USB-C hub || 0bda:0411 hub, 0bda:8153 ethernet || good || USB works, NIC recognized by kernel, but untested if link actually works. Interestingly, dmesg shows unconnected alternate mode DP, but no connector is present. It seems as if PlanetCom actually made custom version of above i-Tec device.
|-
|USB-C dock || DELL USB-C to HDMI/VGA/Ethernet/USB 3.0 DA200g || idVendor=05e3, idProduct=0610, bcdDevice=49.70 || mixed || USB works, detected as u port usb hub, the rest is not working
|-
|USB-C dock || Lenovo ThinkPad 40A9 || 17ef:3063 17ef:1021 17ef:1026 17ef:3060 17ef:3062 17ef:1025 || mixed || USB hub works, audio device works, ethernet device works, display does NOT despite plug's orientation
|}

== USB C alternate mode DP ==
Note that only USB C alternate mode Display Port will pass video. Any HDMI, DVI or VGA port must be converted internally by the device from Display Port - or the device won't work for video.
{| class="wikitable sortable"
!Type || Make/Model || Hardware IDs || Result || Notes
|-
|USB-C to HDMI adapter 201018 || Cable Matters || || good || Tested up to 1080p30, audio works
|-
|USB-C to HDMI adapter || Choetech HUB-H06 || || good || Advertises support for 4K@60Hz, tested up to 1080p@60Hz, worked in both Debian and Manjaro 2020-04-04
|-
|USB-C to HDMI adapter || generic || || good || Tested up to 4k60
|-
|USB-C to DP Adapter || OrxnQ || 04b4:5210 || good || Advertises support for 4K@60Hz, tested up to 1080p. Only FullHD resolutions available on Debian.
|-
|USB-C HDMI adapter (DP-alt mode) || QGeeM || || good || Manjaro 2020-01-25
|-
|USB C Hub to HDMI VGA SD TF Card Reader 3USB 3.0 and USB C Power Pass-Through Port || MOKiN|| || good || tested to 1080p, sdcards can read from one write to another --Manjaro 2020-11-11 https://smile.amazon.com/gp/product/B07MP9P6B7/
|-
|USB-C combo hub (HDMI, network, card slots, USB ports) || generic || || fail ||
|-
|USB-C combo hub (HDMI, VGA, Ethernet, card slots, USB 2 & 3 || Powlaken || 05e3:0610 0bda:8153 || USB, Power, Ethernet and SD good, HDMI and VGA fail
|-
|USB-C Dock (HDMI, VGA, Ethernet, microSD/SD card slots, 2 USB 3 Ports, 1 USB-C Port, USB-Power Passthru || Digitus DA-70865 || || USB, Ethernet and MicroSD/SD good, video crashes System (fail). || Tested on Manjaro w/ Kernel 5.5. You have to turn the USB-C connector upside down for it to work. Video seems to be a driver issue.
|-
|USB-C Dock (HDMI, VGA, Ethernet, microSD/SD card slots, 2 USB 3 Ports, 1 USB-C Port, USB-Power pass-through) || generic || || Ethernet and MicroSD/SD good, USB fail, video up to 1080p. || https://forum.pine64.org/showthread.php?tid=8728
|-
|USB-C Dock (DP, HDMI, 1Gbps Ethernet, SD card slot, 2 USB 3 Ports, USB-C power in port || goFanco || || DP, Ethernet & USB good, (HDMI & SD card untested). Video tested good to 1080p || Tested on default Debian
|-
|USB-C Dock (HDMI, USB 3.0 x 2, USB-C PD Pass Thru Power Port Up to 100W, SD/TF Card Reader || Hiearcool 7-in-1 || || HDMI, USB, Power Port good, SD/TF Reader fail || Default Debian
|-
|USB-C 3.0 Multi-Port Hub (HDMI, USB 3.0 x 1, USB-C charge only) || Linden LITCAD17 || || HDMI and USB good, Power Port fail || Default Debian & ayufan Ubuntu
|-
|USB-C to DP adapter || Nekteck || 04b4:5210 || good || Shows up as "Cypress Semiconductor Corp. Billboard Device" in lsusb and dmesg output. Works in latest Manjaro (as of January 26, 2020) with no issues. Only FullHD resolutions available on Debian.
|-
|USB-C to HDMI adapter || MHL TH002 || || good || Tested at 1080p@60
|-
|USB-C combo hub (USB-C power, HDMI, 2xUSB, 1xUSB-C(no power)) || Baseus || || good
|-
|USB-C Travel Dock with DP ALT-MODE || Targus DOCK411-A || 0835:2a01 (BILLBOARD DEVICE) 0bda:8153 (RTL8153 GbE Adapter) || GbE: works, HDMI: works, USB3.0 port: works, VGA: unknown || HDMI@1080p@60Hz: works OK, HDMI@4K@30Hz: works but buggy. GbE is only picked up when the USB C is plugged in with one certain side facing upwards. It is not detected the other way around. (Sounds weird, but reproduced it multiple times.)
|-
|USB-C to DP adapter || MediaGearPro AC0011 || 2109:0100 (USB 2.0 BILLBOARD) || DP: works || Only 1080p@60Hz is available, 4K resolutions not possible in contrast to what the manufacturer claims.
|-
|USB-C to DP cable || Generic on ebay || || good but with issues || Had some wonky framerates when tested on a 144hz monitor, 60hz mode was actually sent as ~48hz, 120hz mode was actually sent at ~112hz and 144hz mode was actually sent at ~120hz
|-
|UGREEN Hub USB C 9 in 1 HDMI and VGA || UGREEN || || good || VGA and HDMI works but not at the same time. HDMI audio not tested. Switching between HDMI and VGA need to replug the hub.
|-
|USB-C Dock 6-in-1 HDMI || Ugreen 50771 || || HDMI: works, Ethernet: works, 3x USB: works, USB-PD: works || Tested on Manjaro 2020/03/18 Works USB-C PD Chargers provided they can do 5V3A, works with 5V3A USB-C Raspberry Pi 4 power supply (Doesn't work with 5V2A USB-C). No HDMI Audio.
|-
|USB-C to DP cable || [https://www.amazon.es/gp/product/B01N5RFAI4/ CHOETECH V-XCP-0012BK] || || good
|-
| [https://www.apple.com/ca/shop/product/MQ4H2AM/A/thunderbolt-3-usb%E2%80%91c-cable-08-m Thunderbolt 3 (USB‑C) Cable (0.8 m)] || Apple || || Display Port Alternate Mode: Fails, USB-PD: works || Tested on Manjaro 2020/05/29 - Charges but no video
|-
|USB-C to HDMI cable || Planet Computers USB-C to HDMI cable || || fail || does not work regardless of orientation in USB slot
|-
|USB-C combo hub || Moreslan 11in1 (https://www.amazon.fr/gp/product/B08397B66G) || || good || GbE: OK, HDMI: OK, 4 usb ports: OK, Power via USB-C: OK, microSD: OK, TFT: OK, Jack: OK, VGA: Not tested; UPDATE: HDMI Display not working anymore since Manjaro release 20.08
|-
|USB-C Multiport Adapter || [https://www.wentronic.com/en/usb-ctm-multiport-adapter-hdmi-ethernet-pd-white-62105 Goobay 62105] || || Fail || GbE: OK, UBS port: OK, Power via USB-C: OK, HDMI: Does generate an image, but it jumps X pixels right from time to time (4K@30 and FHD)
|-
| USB Type-C to HDMI Adapter || Insignia NS-PU369CH-WH || 0bda:5400|| good || tested on kernel 5.5.0, video out works, audio not tested
|-
| Portable USB Display || UPerfect 15.6 inches 1080P Portable Monitor Stand for Mobile Touchscreen (https://www.uperfectmonitor.com/collections/15-6-inches-portable-monitor/products/15-6-inches-1080p-portable-monitor-stand) || || Power via USB-C: works, DP-Alt video: works, Touchscreen fails || Tested on armbian on 20210820
|}

== USB other ==
{| class="wikitable sortable"
!Type || Make/Model || Hardware IDs || Result || Notes
|-
|Wireless Mouse || Logitech M705 Marathon || || good || Uses Logitech receiver. Battery level detected in power settings.
|-
|Wireless Mouse || Logitech G305 || || good || Uses Logitech receiver
|-
|Gamepad || Sertronics SNES Style Controller || || good || Tested in retroarch, Sertronics is also known as Berrybase
|-
|Drawing tablet || XP Pen G430s || 28bd:0913 || good || Hardware works, official software not used, tablet was configured using udev rules which are more functional than official software anyway
|-
|Yubikey original || Yubico || 1050:0010 || good ||
|-
|}

----

= Bluetooth hardware =
{| class="wikitable sortable"
!Type || Make/Model || Hardware IDs || Result || Notes
|-
|Bluetooth Mouse || HP Z5000 || E5C13AA || good ||
|-
|Bluetooth Mouse || Logitech M557 || || good ||
|-
|Bluetooth Mouse || Kensington Expert Wireless Trackball || || good ||
|-
|Bluetooth Mouse || Logitech MX Vertical || || good || Battery level is not detected over bluetooth, detected when using the logitech receiver
|-
|Bluetooth Mouse || Logitech Triathlon M720 || || good ||
|-
|Bluetooth Mouse || Logitech Ultra-Thin Touch Mouse || || good || Detects battery level as "keyboard"
|-
|Bluetooth Mouse || Logitech MX Anywhere 2 || || good ||
|-
|Bluetooth Mouse || Logitech M535 || 910-004432 || good ||
|-
|Bluetooth Mouse || Microsoft Bluetooth Mouse || RJN-00002 || good ||
|-
|Bluetooth Mouse || Fenifox low profile || MX106-Black || good ||
|-
|Bluetooth Mouse || Technet || MGS479 || good ||
|-
|Bluetooth Keyboard || Logitech MX Keys || || good || Battery level is not detected over bluetooth, detected when using the logitech receiver
|-
|Bluetooth Speaker || Ivation Acoustix || || good || Use audio sink profile
|-
|Bluetooth Headphones || Sony WH-1000XM2 || || good* || Needs pulseaudio-module-bluetooth. *Recording untested.
|-
|Bluetooth Headphones || COWIN SE7 Noise Cancelling Headphones || || good || Pairs and plays audio with stock Debian OS. More detail [https://forum.pine64.org/showthread.php?tid=8192&pid=60682#pid60682 here].
|-
|USB Audio & Bluetooth Headset || Sony SBH90C || || good || Works well connected via USB Type-C and Bluetooth.
|-
|Bluetooth Headset || BlueAnt Ribbon || 7252A-RB || good || a2dp mode works, headset mode seems to work, out of box with manjaro
|-
|Bluetooth Headphones || DO-SV-BTIES03 || || good || Tested on Manjaro ARM - kde
|-
|Bluetooth Headset || TaoTronics TT-BH090 || || good || Microphone not tested but should work as expected of a normal Linux machine
|-
|Bluetooth Mouse || Logitech MX Ergo || || good || Works flawlessly both on Manjaro and Armbian.
|}

----

= Other hardware =

{| class="wikitable sortable"
!Type || Make/Model || Hardware IDs || Result || Notes
|-
|[https://www.aliexpress.com/item/32831647303.html USB charging cable] || - || - || good || Got the cable a while back so may not be identical to current product
|-
|Printer || HP DeskJet Ink Advantage 3775 || || good* || Using hplip-gui: via USB and WiFi. *Only print function tested.
|-
|}

[[Category:PineBook Pro]]

Pinebook Pro Software Releases

2022-02-07T07:03:25Z

BenTheTechGuy: Update Debian Installer to reflect current state more accurately

Main Page

2021-10-19T01:13:34Z

BenTheTechGuy: Reword Matrix Space and rearrange some things above table

PINE64 is a community-driven company focused on creating high-quality, low-cost ARM devices and, more recently, RISC-V devices for individuals and businesses around the globe. PINE64 made its debut with the [[PINE A64|PINE A64]] single-board computer, which successfully launched on Kickstarter in 2015. PINE64 has since released a multitude of other devices, including both development boards and end-user devices.

PINE64 has a large, diverse and active community, and offers a variety of resources for hobbyists and businesses to successfully leverage various PINE64 products. To become connected and involved with the community, please see [[Main Page#Community and Support|Community and Support]] for a list of available channels and chat platforms. To learn more about PINE64, please visit the [https://www.pine64.org/ PINE64 website] and the [https://www.pine64.com/ PINE64 store]'''.

For information about PINE64 branding, including the usage of the PINE64 logo in non-commercial and other applications please read the [https://wiki.pine64.org/wiki/PINE64_brand_and_logo article about our brand and logo].

= Devices =

[[File:Marchupdate-1024x594.jpg|thumb|upright=1.2|[[Pinebook Pro]] (left) and [[PinePhone]] (right)]]

You can learn more about the following ARM and RISC-V devices manufactured by PINE64:

* Phones: '''[[PinePhone]]''' and '''[[PinePhone Pro]]'''
* Tablets: '''[[PineNote]]''' and '''[[PineTab]]'''
* Smartwatch: '''[[PineTime]]'''
* Laptops: '''[[Pinebook]]''', '''[[Pinebook Pro]]''' and '''[[Pinebook Pro Dock|Pinebook Pro Docking station]]'''
* Single-board computers: '''[[Quartz64]]''', '''[[ROCKPro64]]''', '''[[ROCK64]]''', '''[[PINE A64]]''', '''[[PINE A64-LTS/SOPine|PINE A64-LTS]]''' and '''[[PINE H64]]'''
* Clusters and modules: '''[[Clusterboard]]''', '''[[SOPine]]''', '''[[SOPine Baseboard]]''' and '''[[SOEdge]]'''
* IP camera: '''[[PineCube]]'''
* Makerspace: '''[[Pinecil]]''', '''[[PinePower]]''', '''[[PineCone]]''' and '''[[Pinedio]]'''

= Community and Support =

Community collaboration and support is focused around the chat platforms and forums described below. As an example of the collaborative efforts of the community, recent activity has resulted in drafting a [[PineFlash|proposal]] for a new flash-based storage device. See [https://www.pine64.org/gettings-started/ Getting Started | PINE64] for tips about how to get started with the PINE64 community.

== Chat Platforms ==

PINE64 has a large and very active community. Community discussion takes place on a variety of chat platforms, which are all bridged together so the messages sent via one platform are sent to all other platforms automatically. The other networks and their users are represented by P64ProtocolBot.

{{note|1=The activity of community members varies depending on the time of day and the number of active users, so please be patient and do not expect questions to be answered immediately.}}

The community chat platforms are the following:
* '''Discord''': Use the [https://discordapp.com/invite/DgB7kzr invite link]. All channels are available.
* '''IRC''': The server is irc.pine64.org. There is a WebIRC client on www.pine64.org/web-irc, but use of a dedicated client is advised. Use <code>/list</code> command or the table below to see the full list of channels.
* '''Matrix and Telegram''': See the table below.

{| class="wikitable"
! Channel !! Matrix !! Telegram !! IRC
|-
| PINE64 News
| [https://app.element.io/#/room/#pine64-announcements:matrix.org #pine64-announcements:matrix.org]
| [https://t.me/PINE64_News @PINE64_News]
| Unavailable
|-
| General PINE64 chat
| [https://app.element.io/#/room/#pine64:matrix.org #pine64:matrix.org]
| [https://t.me/mtrx_pine64 @mtrx_pine64]
| #pine64
|-
| PINE A64(+), A64-LTS & SOPine
| [https://app.element.io/#/room/#pine64sopine:matrix.org #pine64sopine:matrix.org]
| [https://t.me/pine64sopine @pine64sopine]
| #lts-sopine
|-
| ROCK64 / ROCKPro64
| [https://app.element.io/#/room/#rock64:matrix.org #rock64:matrix.org]
| [https://t.me/mtrx_rock64 @mtrx_rock64]
| #rock64
|-
| Quartz64
| [https://app.element.io/#/room/#quartz64:matrix.org #quartz64:matrix.org]
| [https://t.me/joinchat/Vq50DXkH31e0_i-f Quartz64]
| #quartz64
|-
| Quartz64 Development
| [https://app.element.io/#/room/#quartz64-dev:matrix.org #quartz64-dev:matrix.org]
| [https://t.me/q64dev @q64dev]
| #quartz64-dev
|-
| Pinebook and Pinebook Pro
| [https://app.element.io/#/room/#pinebook:matrix.org #pinebook:matrix.org]
| [https://t.me/mtx_pinebook @mtx_pinebook]
| #pinebook
|-
| PinePhone
| [https://app.element.io/#/room/#pinephone:matrix.org #pinephone:matrix.org]
| [https://t.me/pinephone @pinephone]
| #pinephone
|-
| PineNote
| [https://app.element.io/#/room/#pinenote:matrix.org #pinenote:matrix.org]
| [https://t.me/pinenote @PineNote]
| #pinenote
|-
| PineTab
| [https://app.element.io/#/room/#pinetab:pine64.org #pinetab:matrix.org]
| [https://t.me/PineTab @PineTab]
| #pinetab
|-
| PineTime
| [https://app.element.io/#/room/#pinetime:matrix.org #pinetime:matrix.org]
| [https://t.me/pinetime @pinetime]
| #pinetime
|-
| PineTime Development
| [https://app.element.io/#/room/#pinetime-dev:matrix.org #pinetime-dev:matrix.org]
| [https://t.me/pinetime_dev @pinetime_dev]
| #pinetime-dev
|-
| Pinecil
| [https://app.element.io/#/room/#pinecil:matrix.org #pinecil:matrix.org]
| [https://t.me/joinchat/Kmi2S1iej-_4DgrVf3jjnQ Pinecil]
| #pinecil
|-
| Pinetalk Podcast || Unavailable || Unavailable || Unavailable
|-
| Cube
| [https://app.element.io/#/room/#cube64:matrix.org #cube64:matrix.org]
| [https://t.me/pinecube @pinecube]
| #cube
|-
| Nutcracker
| [https://app.element.io/#/room/#pine64-nutcracker:matrix.org #pine64-nutcracker:matrix.org]
| [https://t.me/joinchat/Kmi2S0nOsT240emHk-aO6g Nutcracker]
| #nutcracker
|-
| LoRa
| [https://app.element.io/#/room/#pinelora:matrix.org #pinelora:matrix.org]
| [https://t.me/pine64lora @pine64lora]
| #lora
|-
| Off-topic
| [https://app.element.io/#/room/#offtopic64:matrix.org #offtopic64:matrix.org]
| [https://t.me/pine64offtopic @pine64offtopic]
| #Offtopic
|}

There is also an unofficial Matrix Space at [https://app.element.io/#/room/#pine64-space:matrix.org #pine64-space:matrix.org] for supported clients that organizes all of the above matrix channels into one place.

== Forums ==

PINE64 runs an official forum powered by the open-source forum server software MyBB. The forum can be used to report issues, help out other users, offer findings and new information and more. Users can also engage directly with the community and the developers of partner projects, as well as with the PINE64 members.

The official PINE64 forum can be accessed here:
* [https://forum.pine64.org/ Official PINE64 Forum]

Also, these are the official Subreddits:

* [https://www.reddit.com/r/PINE64official/ Official PINE64 Reddit]
* [https://www.reddit.com/r/PinePhoneOfficial/ Official PinePhone Reddit]

= Helpful Information for Beginners =

* '''[[NOOB | Getting started]]''': Basic information on setting up and handling PINE64 devices, such as how to write (flash) OS images to microSD cards and eMMC modules
* '''[[Notes | PINE64 Wiki contributing Notes]]''': Some notes on prioritized and suggested writing or editing to this Wiki, as well as long-term goals and wiki housekeeping tasks.
* '''[[:Category:Guide]]''': Lists other guide pages than those two above, some are delicated to spicific devices.

Main Page

2021-09-26T21:49:46Z

BenTheTechGuy: added matrix space

PINE64 is a community-driven company focused on creating high-quality, low-cost ARM devices and, more recently, RISC-V devices for individuals and businesses around the globe. PINE64 made its debut with the [[PINE A64|PINE A64]] single-board computer, which successfully launched on Kickstarter in 2015. PINE64 has since released a multitude of other devices, including both development boards and end-user devices.

PINE64 has a large, diverse and active community, and offers a variety of resources for hobbyists and businesses to successfully leverage various PINE64 products. To become connected and involved with the community, please see [[Main Page#Community and Support|Community and Support]] for a list of available channels and chat platforms. To learn more about PINE64, please visit the [https://www.pine64.org/ PINE64 website] and the [https://www.pine64.com/ PINE64 store]'''.

For information about PINE64 branding, including the usage of the PINE64 logo in non-commercial and other applications please read the [https://wiki.pine64.org/wiki/PINE64_brand_and_logo article about our brand and logo].

= Devices =

[[File:Marchupdate-1024x594.jpg|thumb|upright=1.2|[[Pinebook Pro]] (left) and [[PinePhone]] (right)]]

You can learn more about the following ARM and RISC-V devices manufactured by PINE64:

* Phones and tablets: '''[[PinePhone]]''', '''[[PineNote]]''' and '''[[PineTab]]'''
* Smartwatches: '''[[PineTime]]'''
* Laptops: '''[[Pinebook]]''', '''[[Pinebook Pro]]''' and '''[[Pinebook Pro Dock|Pinebook Pro Docking station]]'''
* Single-board computers: '''[[Quartz64]]''', '''[[ROCKPro64]]''', '''[[ROCK64]]''', '''[[PINE A64]]''', '''[[PINE A64-LTS/SOPine|PINE A64-LTS]]''' and '''[[PINE H64]]'''
* Clusters and modules: '''[[Clusterboard]]''', '''[[SOPine]]''', '''[[SOPine Baseboard]]''' and '''[[SOEdge]]'''
* IP cameras: '''[[PineCube]]'''
* Makerspace: '''[[Pinecil]]''', '''[[PinePower]]''', '''[[PineCone]]''' and '''[[Pinedio]]'''

= Community and Support =

Community collaboration and support is focused around the chat platforms and forums described below. As an example of the collaborative efforts of the community, recent activity has resulted in drafting a [[PineFlash|proposal]] for a new flash-based storage device. See [https://www.pine64.org/gettings-started/ Getting Started | PINE64] for tips about how to get started with the PINE64 community.

== Chat Platforms ==

PINE64 has a large and very active community. Community discussion takes place on a variety of chat platforms, which are all bridged together so the messages sent via one platform are sent to all other platforms automatically. The community chat platforms are the following:

* '''Discord''': use the [https://discordapp.com/invite/DgB7kzr invite link]. All channels are available.
* '''Matrix''' and '''Telegram''':
{| class="wikitable"
! Channel !! Matrix !! Telegram
|-
| PINE64 News || [https://riot.im/app/#/room/#pine64-announcements:matrix.org #pine64-announcements:matrix.org] || [https://t.me/PINE64_News @PINE64_News]
|-
| General PINE64 chat || [https://riot.im/app/#/room/#pine64:matrix.org #pine64:matrix.org] || [https://t.me/mtrx_pine64 @mtrx_pine64]
|-
| PINE A64(+), A64-LTS & SOPine || [https://riot.im/app/#/room/#pine64sopine:matrix.org #pine64sopine:matrix.org] || [https://t.me/pine64sopine @pine64sopine]
|-
| ROCK64 / ROCKPro64 || [https://riot.im/app/#/room/#rock64:matrix.org #rock64:matrix.org] || [https://t.me/mtrx_rock64 @mtrx_rock64]
|-
| Quartz64 || [https://riot.im/app/#/room/#quartz64:matrix.org #quartz64:matrix.org] || [https://t.me/joinchat/Vq50DXkH31e0_i-f Quartz64]
|-
| Quartz64 Development || [https://riot.im/app/#/room/#quartz64-dev:matrix.org #quartz64-dev:matrix.org] || [https://t.me/q64dev @q64dev]
|-
| Pinebook and Pinebook Pro || [https://riot.im/app/#/room/#pinebook:matrix.org #pinebook:matrix.org] || [https://t.me/mtx_pinebook @mtx_pinebook]
|-
| PinePhone || [https://riot.im/app/#/room/#pinephone:matrix.org #pinephone:matrix.org] || [https://t.me/pinephone @pinephone]
|-
| PineNote || [https://riot.im/app/#/room/#pinenote:matrix.org #pinenote:matrix.org] || [https://t.me/pinenote @PineNote]
|-
| PineTab || [https://riot.im/app/#/room/#pinetab:pine64.org #pinetab:matrix.org] || [https://t.me/PineTab @PineTab]
|-
| PineTime || [https://riot.im/app/#/room/#pinetime:matrix.org #pinetime:matrix.org] || [https://t.me/pinetime @pinetime]
|-
| PineTime Development || [https://riot.im/app/#/room/#pinetime-dev:matrix.org #pinetime-dev:matrix.org] || [https://t.me/pinetime_dev @pinetime_dev]
|-
| Pinecil || [https://riot.im/app/#/room/#pinecil:matrix.org #pinecil:matrix.org] || [https://t.me/joinchat/Kmi2S1iej-_4DgrVf3jjnQ Pinecil]
|-
| Pinetalk || Unavailable || Unavailable
|-
| Cube || [https://riot.im/app/#/room/#cube64:matrix.org #cube64:matrix.org] || [https://t.me/pinecube @pinecube]
|-
| Nutcracker || [https://riot.im/app/#/room/#pine64-nutcracker:matrix.org #pine64-nutcracker:matrix.org] || [https://t.me/joinchat/Kmi2S0nOsT240emHk-aO6g Nutcracker]
|-
| LoRa || [https://riot.im/app/#/room/#pinelora:matrix.org #pinelora:matrix.org] || [https://t.me/pine64lora @pine64lora]
|-
| Off-topic || [https://riot.im/app/#/room/#offtopic64:matrix.org #offtopic64:matrix.org] || [https://t.me/pine64offtopic @pine64offtopic]
|-
|}

* '''Matrix''': There is an unofficial Matrix Space at [https://riot.im/app/#/room/#pine64-space:matrix.org #pine64-space:matrix.org] that organizes all of the channels into one place. Requires the spaces beta to be enabled in Element or other supported clients.

* '''IRC''': The IRC channels can be reached via irc.pine64.org. Support requests via IRC are discouraged, users are advised to look into the Matrix communication protocol as contemporary solution instead.

== Forums ==

PINE64 runs an official forum powered by the open-source forum server software MyBB. The forum can be used to report issues, help out other users, offer findings and new information and more. Users can also engage directly with the community and the developers of partner projects, as well as with the PINE64 members.

The official PINE64 forum can be accessed here:
* [https://forum.pine64.org/ Official PINE64 Forum]

Also, these are the official Subreddits:

* [https://www.reddit.com/r/PINE64official/ Official PINE64 Reddit]
* [https://www.reddit.com/r/PinePhoneOfficial/ Official PinePhone Reddit]

= Helpful Information for Beginners =

* '''[[NOOB | Getting started]]''': Basic information on setting up and handling PINE64 devices, such as how to write (flash) OS images to microSD cards and eMMC modules
* '''[[Notes | PINE64 Wiki contributing Notes]]''': Some notes on prioritized and suggested writing or editing to this Wiki, as well as long-term goals and wiki housekeeping tasks.
* '''[[:Category:Guide]]''': Lists other guide pages than those two above, some are delicated to spicific devices.

Pinebook Pro Hardware Accessory Compatibility

2021-08-13T17:05:53Z

BenTheTechGuy: Revert unnecessary deletions of tested devices

Please test as many things as you can find with your [[Pinebook Pro]] and share the results here. Some devices which should work don't!

= Storage =

== NVMe SSD drives ==
Only PCI Express M.2 drives can work, due to the available connectivity of the Pinebook Pro. Consequently, SATA or USB M.2 cards will not work.

You need to buy and install the M.2 adaptor in order to fit one, please see [[Pinebook_Pro#Using_the_optional_NVMe_adapter]]

Please see [[Pinebook Pro Troubleshooting Guide#NVMe SSD issues|a separate section]] that describes reported issues with the NVMe drives in PineBook Pro.

{| class="wikitable sortable"
!Type || Make/Model || Size || Hardware IDs || Result || Notes || Power options Active only || Save power setting?
|-
| 2280 || Crucial P1 || 1 TB || CT1000P1SSD8 || good || With PS 2 and APST impact on battery life seems to be minimal. Running powerstat seems to confirm little additional power draw. || PS 0: 9.00W PS 1: 4.60W PS 2: 3.80W PS 3: 0.0300W PS 4: 0.0030W APSTE: enabled by default || Yes
|-
| 2280 || Crucial P2 || 500GB || CT500P2SSD8 || ok || problems loading from u-boot [http://u-boot.10912.n7.nabble.com/NVMe-boot-issues-on-RockPro64-td424863.html] || PS 0: 3.50W PS 1: 1.90W PS 2: 1.50W PS 3: 0.0700W PS 4: 0.0020W APSTE: enabled by default || No
|-
| 2280 || Kingston A2000 || 250 GB || SA2000M8250G || good || || PS 0: 9.00W PS 1: 4.60W PS 2: 3.80W PS 3: 0.045W PS 4: 0.004W APSTE: enabled by default || Yes
|-
| 2280 || Kingston A2000 || 1 TB || SA2000M81000G || good || || same as 250 GB || Yes
|-
| 2242 || Toshiba OCZ RC 100 || 240 GB || RC100-M22242-240G || good || || ||
|-
| 2242 || Lexar NM520 || 256 GB || LNM520-256RBNA || good ||For some data on power use and performance, see [https://forum.pine64.org/showthread.php?tid=9029 here.] || PS 0: 3.05W PS 1: 2.44W PS 2: 2.02W || No. See [https://forum.pine64.org/showthread.php?tid=8737&pid=56481#pid56481 workaround].
|-
| 2280 || XPS SX8200 || 512 GB || ASX8200PNP-512GT-C || good || Performed [https://forum.pine64.org/showthread.php?tid=8322 these] steps for physical installation. Currently rooting from drive. || ||
|-
| 2280 || Intel 660p M.2 || 512 GB || SSDPEKNW512G8X1 || good || PS 1 (2.70W) will work without issues, even under heavy load. Recommended over PS 2, as PS 2 will incur an additional 80% performance penalty. APSTE shows enabled but drive does not support it. || PS 0: 3.50W PS 1: 2.70W PS 2: 2.00W || No
|-
| 2280 || Intel 660p M.2 || 1 TB || SSDPEKNW010T8X1 || good || || PS 0: 4.00W PS 1: 3.00W PS 2: 2.20W APSTE Disabled by default || No
|-
| 2280 || Intel 660p M.2 || 2 TB || SSDPEKNW020T8 || good || [https://forum.pine64.org/showthread.php?tid=7524&pid=49300#pid49300 Performance tests results] || PS 0: 5.50W PS 1: 3.60W PS 2: 2.60W PS 3: 0.0300W PS 4: 0.0040W || No
|-
| 2280 || Intel 760p M.2 || 128 GB || SSDPEKKW128G8 || good || Firmware Revision 004C || PS 0: 9.00W PS 1: 4.60W PS 2: 3.80W PS 3: 0.045W PS 4: 0.004W APSTE: disabled by default with 4.4 kernel (mrfixit Debian), enabled by default with 5.6 kernel (Manjaro KDE) || Yes
|-
| 2280 || Intel 760p M.2 || 256 GB || SSDPEKKW256G8 || good || Firmware Revision 004C || PS 0: 9.00W PS 1: 4.60W PS 2: 3.80W PS 3: 0.045W PS 4: 0.004W Need to use lower power. ||
|-
| 2280 || integral 256GB SSD M.2 2280 NVME || 256 GB || INSSD256GM280NM1 || usable || || PS 0: 9.00W || No
|-
| 2280 || PNY CS1030 || 500GB || CS1030 || good || || PS 0: 4.50W PS 1: 2.70W PS 2: 2.16W PS 3: 0.0700W PS 4: 0.0050W APSTE: Enabled||
|-
| 2280 || Samsung 970 EVO Plus || 250 GB || MZ-V7S250BW || fail || Tested on Manjaro-ARM as root drive. Limited to PS 2 and Volatile Write Cache off gives the most stable results, but it will still hang on a hdparm test. || ||
|-
| 2280 || Samsung 970 EVO Plus || 500 GB || MZ-V7S500 || fail || Too power hungry? || PS 0: 6.2W PS 1: 4.3W PS 2: 2.1W ||
|-
| 2280 || Samsung 970 EVO || 1 TB || MZ-V7E1T0BW || fail || Too power hungry? || ||
|-
| 2280 || Samsung 970 PRO || 1 TB || MZ-V7P1T0BW || good || || PS 0: 6.20W PS 1: 4.30W PS 2: 2.10W PS 3: 0.04W PS 4: 0.005W APSTE: enabled by default || Yes
|-
| 2280 || Corsair MP300 || 120 GB || CSSD-F120GBMP300 || good || || PS 0: 3.00W PS 1: 2.00W PS 2: 2.00W PS 3: 0.1W PS 4: 0.005W APSTE Disabled by default ||
|-
| 2280 || Silicon Power P34A60 || 1TB || SP001TBP34A60M28 || Usable || Power eager, but doesn't seem to use all 9W all the time, only under heavy I/O || PS 0: 9W || N/A
|-
| 2280 || Silicon Power P34A60 || 256 GB || SPCC M.2 PCIe SSD || detected || ASIN B07ZH6QR8Q "Silicon Power PCIe M.2 NVMe SSD 256GB Gen3x4" / PCIe A60 || PS 0: 6.77W PS 1: 5.71W PS 2: 5.19W APSTE Enabled by default || No
|-
| 2280 || Silicon Power P34A60 || 256 GB || ??? || fail || Isn't detected || ||
|-
| 2280 || Sabrent Rocket || 256 GB || SB-ROCKET-256 || good || || || No
|-
| 2242 || Sabrent Rocket Nano || 512 GB || SB-1342-512 || good* || No touchpad issues, didn't trim NVME adapter board. (*Might be too power hungry. More testing needed.) || ||
|-
| 2242 || Sabrent Rocket || 1 TB || SB-RKTQ-1TB || good || || PS 0: 5.55W PS 1: 4.49W PS 2: 3.97W PS 3: 0.049W PS 4: 0.0018W APSTE: available || Yes
|-
| 2280 || MyDigitalSSD SBXe || 960 GB || || good || || APST enabled Power states N/A || N/A
|-
| 2280 || HP SSD EX900 || 250GB || || good || No low-power modes available || ||
|-
| 2280 || HP SSD EX950 || 512GB || || good || Unsure about low-power modes || ||
|-
| 2280 || WD BLUE SN550 || 1TB || WDC WDS100T2B0C-00PXH0 || WARNING good || WARNING mine was SATA and does NOT work! Booted successfully from NVMe (Bionic MATE) || PS 0: 3.50W PS 1: 2.70W PS 2: 1.90W APSTE Disabled by default || N/A
|-
| 2280 || WD Blue SN550 || 500GB || WDC WDS500G2B0C-00PXH0 || good || || PS 0: 3.50W PS 1: 2.40W PS 2: 1.90W APSTE enabled by default with 5.9 kernel (Manjaro XFCE) || No ||
|-
| 2280 || WD Blue SN500 || 500GB || WDS500G1B0C || fail || Works OK on power state 2 (2.5W), but hangs the system whenever there is intense IO (peak draw) on the drive || ||
|-

| 2242 || WD PC SN520 || 256GB || - || fail || Power LED Flashes. Nothing else happens. || ||
|-
| 2280 || WD PC SN730 || 512GB || SDBPNTY-512G-1032 || good || No touchpad issues. Works after latest updates. ||APST enabled by default PS 0: 5.50W PS 1: 3.50W PS 2: 3.00W PS 3: 0.0700W PS 4: 0.0025W || No ||
|-
| 2280 || WD BLACK SN750 || 250GB || WDS250G3X0C-00SJG0 || good || No touchpad issues, didn't trim NVME adapter board. || APSTE disabled by default PS 0: 5.00W PS 1: 3.50W PS 2: 3.00W||
|-
| 2280 || WD BLACK SN750 || 500GB || WDS500G3X0C-00SJG0 || good || No tp issues. had to charge battery for 20% initially. || APSTE disabled by default PS 0: 5.50W PS 1: 3.50W PS 2: 3.00W PS 3: 0.07W PS 4: 0.0025W||
|-
| 2280 || WD BLACK SN750 || 1TB || WDS100T3X0C-00SJG0 || mixed || Drive works as expected (so far) though with 50% reduction in battery life. Unable to set power mode (due to APST being enabled?). Also unable to suspend PineBook Pro with NVMe drive attached. From dmesg: rockchip-pcie f8000000.pcie: PCIe link enter L2 timeout! PM: dpm_run_callback(): rockchip_pcie_suspend_noirq+0x0/0x100 returns -110 PM: Devvice f8000000.pcie failed to suspend noirq: error -110 PM: no irq suspend of devices failed || APST enabled by default PS 0: 6.00W PS 1: 3.50W PS 2: 3.00W PS 3: 0.1000W PS 4: 0.0025W || No
|-
| 2242 || KingSpec NE-512 || 512 GB || NE512 || good || || APST enabled Power states N/A || N/A
|-
| 2230 || Kioxia BG4 256GBTB|| 256 GB || KBG40ZNS256G || good || || APST enabled by default Power states PS 0: 3.60W PS 1: 2.60W PS 2: 2.20W PS 3: 0.005W PS 4: 0.005W ||
|-
| 2280 || Patriot P300 || 256 GB || P300P256GM28US || good || Booted successfully with / on NVMe and /boot on eMMC (Armbian Buster) || APSTE disabled by default PS 0: 4.50W PS 1: 2.70W PS 2: 2.16W PS 3: 0.07W PS 4: 0.002W||
|-
| 2280 || Team Group MP33 || 128 GB || TM8FP6128G0C101 || good || || ||
|-
| 2280 || Team Group MP34 || 512 GB || TM8FP6512G0C101 || fail ||APST enabled by default and scripts do not change the power mode. Higher power consumption modes cause the PBP to crash || PS 0 5.55W PS 1 4.49W PS 2 3.97W PS 3 0.0490W PS 4 0.0018W ||No
|-
| 2280 || Digifast Ace || 256 GB || DGFA256M2L01 || good ||No touchpad issues. Board not trimmed. || PS 0 6.77W PS 1 5.71W PS 2 5.19W PS 3 0.0490W PS 4 0.0018W ||Yes
|-
| 2280 || Toshiba XG6 || 256 GB || KXG60ZNV256G || good || || PS 0: 6.00W PS 1: 2.70W PS 2: 1.30W PS 3: 0.0500W PS 4: 0.0050W PS 5: 0.0030W APSTE: enabled by default || No

|}

== microSD Cards ==
{| class="wikitable sortable"
!Type || Make/Model || Hardware IDs || Result || Notes
|-
|SD Card || Samsung Evo Select 512GB || MB-ME512GA/AM || good ||
|-
|SD Card || Samsung Evo Plus 64GB || || good || Hdparm tested 44MBps read speeds
|-
|SD Card || Sandisk Ultra 400GB || || good || Works fine as a storage extension. Mounted for pictures, etc.
|-
|SD Card || Sandisk Ultra 16GB || || fail || Works for a short period of time but locks up completely after a certain amount of written data
|-
|SD Card || Sandisk Ultra 64GB (Old from 2015) || || fail || ^
|-
|SD Card || Sandisk Ultra Plus 64GB || || good ||
|-
|SD Card || Sandisk Extreme 64GB || || good || Speeds seem a little slow (67MB/s read compared to 160MB/s rating) but response time and reliability is good
|-
|SD Card || Sandisk Extreme Pro 64GB || || good ||
|}

= USB hardware =

== USB Card Readers ==

Standalone card readers only, please; see below for multifunction devices.

{| class="wikitable sortable"
!Type || Make/Model || Hardware IDs || Result || Notes
|-
|USB-2 SDHC reader || Sandisk MobileMate+ || 0781:b2b3 || good ||
|-
|USB-3 SDHC/CF reader || Transcend TS-RDF8K || 8564:4000 || good ||
|}

== USB Networking ==

Standalone network devices only, please; see below for multifunction devices

{| class="wikitable sortable"
!Type || Make/Model || Hardware IDs || Result || Notes
|-
|USB-2 Fast Ethernet adapter || Realtek RTL8152 || 0bda:8152 || good ||
|-
|USB-2 Ethernet adapter || ASIX AX77882 || 0b95:7720 || good ||
|-
|USB Wifi Dongle || TP-Link TL-WN725N || 0bda:8179 || good || RTL8188EUS, Driver=rtl8188eu from MrFixit stock Debian, works better than internal Broadcom, but signal still not great, https://www.amazon.com/gp/product/B008IFXQFU/
|-
|USB Wifi Dongle || Shenzhen Dudes Tech #8541553244 || 0bda:c811 || mixed || plug/play on stock Armbian Buster with driver rtl8821cu; could not get operating driver built on MrFixit Debian or Manjaro KDE Plasma. Works 2x+ better than internal Broadcom on Armbian. https://www.amazon.com/gp/product/B07F595V22/
|-
|USB 3 to Gigabit Ethernet Adapter || Pluggable USB 3.0 to Ethernet Gigabit (ASIX AX88179 chipset) || 0b95:1790 || good ||
|}

== USB Multifunction Devices ==

{| class="wikitable sortable"
!Type || Make/Model || Hardware IDs || Result || Notes
|-
|USB-C Hub || Samsung EE-P5000 || || Power is passed through from hub to Pinebook Pro; Ethernet, HDMI, and USB-A do not work ||
|-
|USB-C Hub || Insignia NS-PU378CHM || || Power is passed through from hub to Pinebook Pro; USB-A works; HDMI does not work ||
|-
|USB-C Hub || Dell WD19TB || || Power is passed through from hub to Pinebook Pro; Ethernet and USB-A work; Neither Display Port nor HDMI work; audio not tested ||
|-
|USB-C Hub || Totu 8-in-1 || 058f:8468, 2109:0817 USB3, 1a40:0801, 2109:2817 USB2, bda:8153 RTL8153 Gigabit Ethernet || Network, USB, Card Reader, Power Good, HDMI Not Working || Amazon Smile [https://smile.amazon.com/gp/product/B07FX2LW35/]
|-
|USB-C Hub || Delock 87721 || || Network Works, USB Works, Card Reader not tested, Power Good, HDMI Works but does not show as an extra output in X. It just mirrors the default display || Delock 87721 [https://www.delock.de/produkte/G_87721/merkmale.html?setLanguage=en]
|-
|USB-3 combo hub (network, card slots, usb ports) || generic || 05e3:0610 hub, 0bda:8153 gigE, 05e3:0743 card reader || Network good, usb ports good, card reader good ||
|-
|USB-C combo hub (network, card slots, usb ports) || generic || 05e3:0612 hub, 0bda:8153 realtek gigE || Network good, usb ports fail, card reader fail ||
|-
|5-1 USB-C hub || [https://www.aliexpress.com/item/32954358411.html from aliexpress] || 05e3:0626 hub || HDMI, Network, USB-3, USB-C PD [http://www.sympato.ch/~dryak/files/usbc-dock.jpg good] || Might need changing orientation or USB-C cable
|-
|4 Port USB 3 NIC || Delock 62966 || || good || 4 individually controllable Gigabit Ethernet Ports. Consider using it with own power supply
|-
|USB-C combo hub || [https://www.amazon.com/gp/product/B07XKRGQQ2/ from Amazon] || 0c76:161f 0c45:6321 2109:0813 1a40:0101 || good || Everything works: AltMode DP, Ethernet, SD card, USB-A and C, and charging using the stock Debian, and Ubuntu.
|-
|USB-C dock || i-Tec USB-C Metal Nano Dock 4K HDMI w/ LAN || 0bda:0411 hub, 0bda:8153 ethernet || mixed || plug & play with Manjaro, HDMI tested w/ fullHD only, works but only in one polarity. Sound output works, USB hub works. HDMI output may not be recognized by Plasma if dock is connected with HDMI port disconnected. NIC recognized by kernel, but untested if link actually works. USB power delivery works only in one polarity. Unfortunately HDMI works with opposite polarity than USB PD.
|-
|USB-C dock || Planet Computers Gemini USB-C hub || 0bda:0411 hub, 0bda:8153 ethernet || good || USB works, NIC recognized by kernel, but untested if link actually works. Interestingly, dmesg shows unconnected alternate mode DP, but no connector is present. It seems as if PlanetCom actually made custom version of above i-Tec device.
|-
|USB-C dock || DELL USB-C to HDMI/VGA/Ethernet/USB 3.0 DA200g || idVendor=05e3, idProduct=0610, bcdDevice=49.70 || mixed || USB works, detected as u port usb hub, the rest is not working
|-
|USB-C dock || Lenovo ThinkPad 40A9 || 17ef:3063 17ef:1021 17ef:1026 17ef:3060 17ef:3062 17ef:1025 || mixed || USB hub works, audio device works, ethernet device works, display does NOT despite plug's orientation
|}

== USB C alternate mode DP ==
Note that only USB C alternate mode Display Port will pass video. Any HDMI, DVI or VGA port must be converted internally by the device from Display Port - or the device won't work for video.
{| class="wikitable sortable"
!Type || Make/Model || Hardware IDs || Result || Notes
|-
|USB-C to HDMI adapter 201018 || Cable Matters || || good || Tested up to 1080p30, audio works
|-
|USB-C to HDMI adapter || Choetech HUB-H06 || || good || Advertises support for 4K@60Hz, tested up to 1080p@60Hz, worked in both Debian and Manjaro 2020-04-04
|-
|USB-C to HDMI adapter || generic || || good || Tested up to 4k60
|-
|USB-C to DP Adapter || OrxnQ || 04b4:5210 || good || Advertises support for 4K@60Hz, tested up to 1080p. Only FullHD resolutions available on Debian.
|-
|USB-C HDMI adapter (DP-alt mode) || QGeeM || || good || Manjaro 2020-01-25
|-
|USB C Hub to HDMI VGA SD TF Card Reader 3USB 3.0 and USB C Power Pass-Through Port || MOKiN|| || good || tested to 1080p, sdcards can read from one write to another --Manjaro 2020-11-11 https://smile.amazon.com/gp/product/B07MP9P6B7/
|-
|USB-C combo hub (HDMI, network, card slots, USB ports) || generic || || fail ||
|-
|USB-C combo hub (HDMI, VGA, Ethernet, card slots, USB 2 & 3 || Powlaken || 05e3:0610 0bda:8153 || USB, Power, Ethernet and SD good, HDMI and VGA fail
|-
|USB-C Dock (HDMI, VGA, Ethernet, microSD/SD card slots, 2 USB 3 Ports, 1 USB-C Port, USB-Power Passthru || Digitus DA-70865 || || USB, Ethernet and MicroSD/SD good, video crashes System (fail). || Tested on Manjaro w/ Kernel 5.5. You have to turn the USB-C connector upside down for it to work. Video seems to be a driver issue.
|-
|USB-C Dock (HDMI, VGA, Ethernet, microSD/SD card slots, 2 USB 3 Ports, 1 USB-C Port, USB-Power pass-through) || generic || || Ethernet and MicroSD/SD good, USB fail, video up to 1080p. || https://forum.pine64.org/showthread.php?tid=8728
|-
|USB-C Dock (DP, HDMI, 1Gbps Ethernet, SD card slot, 2 USB 3 Ports, USB-C power in port || goFanco || || DP, Ethernet & USB good, (HDMI & SD card untested). Video tested good to 1080p || Tested on default Debian
|-
|USB-C Dock (HDMI, USB 3.0 x 2, USB-C PD Pass Thru Power Port Up to 100W, SD/TF Card Reader || Hiearcool 7-in-1 || || HDMI, USB, Power Port good, SD/TF Reader fail || Default Debian
|-
|USB-C 3.0 Multi-Port Hub (HDMI, USB 3.0 x 1, USB-C charge only) || Linden LITCAD17 || || HDMI and USB good, Power Port fail || Default Debian & ayufan Ubuntu
|-
|USB-C to DP adapter || Nekteck || 04b4:5210 || good || Shows up as "Cypress Semiconductor Corp. Billboard Device" in lsusb and dmesg output. Works in latest Manjaro (as of January 26, 2020) with no issues. Only FullHD resolutions available on Debian.
|-
|USB-C to HDMI adapter || MHL TH002 || || good || Tested at 1080p@60
|-
|USB-C combo hub (USB-C power, HDMI, 2xUSB, 1xUSB-C(no power)) || Baseus || || good
|-
|USB-C Travel Dock with DP ALT-MODE || Targus DOCK411-A || 0835:2a01 (BILLBOARD DEVICE) 0bda:8153 (RTL8153 GbE Adapter) || GbE: works, HDMI: works, USB3.0 port: works, VGA: unknown || HDMI@1080p@60Hz: works OK, HDMI@4K@30Hz: works but buggy. GbE is only picked up when the USB C is plugged in with one certain side facing upwards. It is not detected the other way around. (Sounds weird, but reproduced it multiple times.)
|-
|USB-C to DP adapter || MediaGearPro AC0011 || 2109:0100 (USB 2.0 BILLBOARD) || DP: works || Only 1080p@60Hz is available, 4K resolutions not possible in contrast to what the manufacturer claims.
|-
|USB-C to DP cable || Generic on ebay || || good but with issues || Had some wonky framerates when tested on a 144hz monitor, 60hz mode was actually sent as ~48hz, 120hz mode was actually sent at ~112hz and 144hz mode was actually sent at ~120hz
|-
|UGREEN Hub USB C 9 in 1 HDMI and VGA || UGREEN || || good || VGA and HDMI works but not at the same time. HDMI audio not tested. Switching between HDMI and VGA need to replug the hub.
|-
|USB-C Dock 6-in-1 HDMI || Ugreen 50771 || || HDMI: works, Ethernet: works, 3x USB: works, USB-PD: works || Tested on Manjaro 2020/03/18 Works USB-C PD Chargers provided they can do 5V3A, works with 5V3A USB-C Raspberry Pi 4 power supply (Doesn't work with 5V2A USB-C). No HDMI Audio.
|-
|USB-C to DP cable || [https://www.amazon.es/gp/product/B01N5RFAI4/ CHOETECH V-XCP-0012BK] || || good
|-
| [https://www.apple.com/ca/shop/product/MQ4H2AM/A/thunderbolt-3-usb%E2%80%91c-cable-08-m Thunderbolt 3 (USB‑C) Cable (0.8 m)] || Apple || || Display Port Alternate Mode: Fails, USB-PD: works || Tested on Manjaro 2020/05/29 - Charges but no video
|-
|USB-C to HDMI cable || Planet Computers USB-C to HDMI cable || || fail || does not work regardless of orientation in USB slot
|-
|USB-C combo hub || Moreslan 11in1 (https://www.amazon.fr/gp/product/B08397B66G) || || good || GbE: OK, HDMI: OK, 4 usb ports: OK, Power via USB-C: OK, microSD: OK, TFT: OK, Jack: OK, VGA: Not tested; UPDATE: HDMI Display not working anymore since Manjaro release 20.08
|-
|USB-C Multiport Adapter || [https://www.wentronic.com/en/usb-ctm-multiport-adapter-hdmi-ethernet-pd-white-62105 Goobay 62105] || || Fail || GbE: OK, UBS port: OK, Power via USB-C: OK, HDMI: Does generate an image, but it jumps X pixels right from time to time (4K@30 and FHD)
|-
| USB Type-C to HDMI Adapter || Insignia NS-PU369CH-WH || 0bda:5400|| good || tested on kernel 5.5.0, video out works, audio not tested
|}

== USB other ==
{| class="wikitable sortable"
!Type || Make/Model || Hardware IDs || Result || Notes
|-
|Wireless Mouse || Logitech M705 Marathon || || good || Uses Logitech receiver. Battery level detected in power settings.
|-
|Wireless Mouse || Logitech G305 || || good || Uses Logitech receiver
|-
|Gamepad || Sertronics SNES Style Controller || || good || Tested in retroarch, Sertronics is also known as Berrybase
|-
|Drawing tablet || XP Pen G430s || 28bd:0913 || good || Hardware works, official software not used, tablet was configured using udev rules which are more functional than official software anyway
|-
|Yubikey original || Yubico || 1050:0010 || good ||
|-
|}

----

= Bluetooth hardware =
{| class="wikitable sortable"
!Type || Make/Model || Hardware IDs || Result || Notes
|-
|Bluetooth Mouse || HP Z5000 || E5C13AA || good ||
|-
|Bluetooth Mouse || Logitech M557 || || good ||
|-
|Bluetooth Mouse || Kensington Expert Wireless Trackball || || good ||
|-
|Bluetooth Mouse || Logitech MX Vertical || || good || Battery level is not detected over bluetooth, detected when using the logitech receiver
|-
|Bluetooth Mouse || Logitech Triathlon M720 || || good ||
|-
|Bluetooth Mouse || Logitech Ultra-Thin Touch Mouse || || good || Detects battery level as "keyboard"
|-
|Bluetooth Mouse || Logitech MX Anywhere 2 || || good ||
|-
|Bluetooth Mouse || Logitech M535 || 910-004432 || good ||
|-
|Bluetooth Mouse || Microsoft Bluetooth Mouse || RJN-00002 || good ||
|-
|Bluetooth Mouse || Fenifox low profile || MX106-Black || good ||
|-
|Bluetooth Mouse || Technet || MGS479 || good ||
|-
|Bluetooth Keyboard || Logitech MX Keys || || good || Battery level is not detected over bluetooth, detected when using the logitech receiver
|-
|Bluetooth Speaker || Ivation Acoustix || || good || Use audio sink profile
|-
|Bluetooth Headphones || Sony WH-1000XM2 || || good* || Needs pulseaudio-module-bluetooth. *Recording untested.
|-
|Bluetooth Headphones || COWIN SE7 Noise Cancelling Headphones || || good || Pairs and plays audio with stock Debian OS. More detail [https://forum.pine64.org/showthread.php?tid=8192&pid=60682#pid60682 here].
|-
|USB Audio & Bluetooth Headset || Sony SBH90C || || good || Works well connected via USB Type-C and Bluetooth.
|-
|Bluetooth Headset || BlueAnt Ribbon || 7252A-RB || good || a2dp mode works, headset mode seems to work, out of box with manjaro
|-
|Bluetooth Headphones || DO-SV-BTIES03 || || good || Tested on Manjaro ARM - kde
|-
|Bluetooth Headset || TaoTronics TT-BH090 || || good || Microphone not tested but should work as expected of a normal Linux machine
|-
|Bluetooth Mouse || Logitech MX Ergo || || good || Works flawlessly both on Manjaro and Armbian.
|}

----

= Other hardware =

{| class="wikitable sortable"
!Type || Make/Model || Hardware IDs || Result || Notes
|-
|[https://www.aliexpress.com/item/32831647303.html USB charging cable] || - || - || good || Got the cable a while back so may not be identical to current product
|-
|Printer || HP DeskJet Ink Advantage 3775 || || good* || Using hplip-gui: via USB and WiFi. *Only print function tested.
|-
|}

[[Category:PineBook Pro]]

Pinebook Pro Hardware Accessory Compatibility

2021-05-20T01:14:02Z

BenTheTechGuy: Fix space on table

Please test as many things as you can find with your [[Pinebook Pro]] and share the results here. Some devices which should work don't!

= Storage =

== NVMe SSD drives ==
Only PCI Express M.2 drives can work, due to the available connectivity of the Pinebook Pro. Consequently, SATA or USB M.2 cards will not work.

You need to buy and install the M.2 adaptor in order to fit one, please see [[Pinebook_Pro#Using_the_optional_NVMe_adapter]]

Please see [[Pinebook Pro Troubleshooting Guide#NVMe SSD issues|a separate section]] that describes reported issues with the NVMe drives in PineBook Pro.

{| class="wikitable sortable"
!Type || Make/Model || Size || Hardware IDs || Result || Notes || Power options Active only || Save power setting?
|-
| 2280 || Crucial P1 || 1 TB || CT1000P1SSD8 || good || With PS 2 and APST impact on battery life seems to be minimal. Running powerstat seems to confirm little additional power draw. || PS 0: 9.00W PS 1: 4.60W PS 2: 3.80W PS 3: 0.0300W PS 4: 0.0030W APSTE: enabled by default || Yes
|-
| 2280 || Kingston A2000 || 250 GB || SA2000M8250G || good || || PS 0: 9.00W PS 1: 4.60W PS 2: 3.80W PS 3: 0.045W PS 4: 0.004W APSTE: enabled by default || Yes
|-
| 2280 || Kingston A2000 || 1 TB || SA2000M81000G || good || || same as 250 GB || Yes
|-
| 2242 || Toshiba OCZ RC 100 || 240 GB || RC100-M22242-240G || good || || ||
|-
| 2242 || Lexar NM520 || 256 GB || LNM520-256RBNA || good ||For some data on power use and performance, see [https://forum.pine64.org/showthread.php?tid=9029 here.] || PS 0: 3.05W PS 1: 2.44W PS 2: 2.02W || No. See [https://forum.pine64.org/showthread.php?tid=8737&pid=56481#pid56481 workaround].
|-
| 2280 || XPS SX8200 || 512 GB || ASX8200PNP-512GT-C || good || Performed [https://forum.pine64.org/showthread.php?tid=8322 these] steps for physical installation. Currently rooting from drive. || ||
|-
| 2280 || Intel 660p M.2 || 512 GB || SSDPEKNW512G8X1 || good || PS 1 (2.70W) will work without issues, even under heavy load. Recommended over PS 2, as PS 2 will incur an additional 80% performance penalty. APSTE shows enabled but drive does not support it. || PS 0: 3.50W PS 1: 2.70W PS 2: 2.00W || No
|-
| 2280 || Intel 660p M.2 || 1 TB || SSDPEKNW010T8X1 || good || || PS 0: 4.00W PS 1: 3.00W PS 2: 2.20W APSTE Disabled by default || No
|-
| 2280 || Intel 660p M.2 || 2 TB || SSDPEKNW020T8 || good || [https://forum.pine64.org/showthread.php?tid=7524&pid=49300#pid49300 Performance tests results] || PS 0: 5.50W PS 1: 3.60W PS 2: 2.60W PS 3: 0.0300W PS 4: 0.0040W || No
|-
| 2280 || Intel 760p M.2 || 128 GB || SSDPEKKW128G8 || good || Firmware Revision 004C || PS 0: 9.00W PS 1: 4.60W PS 2: 3.80W PS 3: 0.045W PS 4: 0.004W APSTE: disabled by default with 4.4 kernel (mrfixit Debian), enabled by default with 5.6 kernel (Manjaro KDE) || Yes
|-
| 2280 || Intel 760p M.2 || 256 GB || SSDPEKKW256G8 || good || Firmware Revision 004C || PS 0: 9.00W PS 1: 4.60W PS 2: 3.80W PS 3: 0.045W PS 4: 0.004W Need to use lower power. ||
|-
| 2280 || integral 256GB SSD M.2 2280 NVME || 256 GB || INSSD256GM280NM1 || usable || || PS 0: 9.00W || No
|-
| 2280 || Samsung 970 EVO Plus || 250 GB || MZ-V7S250BW || fail || Tested on Manjaro-ARM as root drive. Limited to PS 2 and Volatile Write Cache off gives the most stable results, but it will still hang on a hdparm test. || ||
|-
| 2280 || Samsung 970 EVO Plus || 500 GB || MZ-V7S500 || fail || Too power hungry? || PS 0: 6.2W PS 1: 4.3W PS 2: 2.1W ||
|-
| 2280 || Samsung 970 EVO || 1 TB || MZ-V7E1T0BW || fail || Too power hungry? || ||
|-
| 2280 || Samsung 970 PRO || 1 TB || MZ-V7P1T0BW || good || || PS 0: 6.20W PS 1: 4.30W PS 2: 2.10W PS 3: 0.04W PS 4: 0.005W APSTE: enabled by default || Yes
|-
| 2280 || Corsair MP300 || 120 GB || CSSD-F120GBMP300 || good || || PS 0: 3.00W PS 1: 2.00W PS 2: 2.00W PS 3: 0.1W PS 4: 0.005W APSTE Disabled by default ||
|-
| 2280 || Silicon Power P34A60 || 1TB || SP001TBP34A60M28 || Usable || Power eager, but doesn't seem to use all 9W all the time, only under heavy I/O || PS 0: 9W || N/A
|-
| 2280 || Silicon Power P34A60 || 256 GB || SPCC M.2 PCIe SSD || detected || ASIN B07ZH6QR8Q "Silicon Power PCIe M.2 NVMe SSD 256GB Gen3x4" / PCIe A60 || PS 0: 6.77W PS 1: 5.71W PS 2: 5.19W APSTE Enabled by default || No
|-
| 2280 || Silicon Power P34A60 || 256 GB || ??? || fail || Isn't detected || ||
|-
| 2280 || Sabrent Rocket || 256 GB || SB-ROCKET-256 || good || || || No
|-
| 2242 || Sabrent Rocket Nano || 512 GB || SB-1342-512 || good* || No touchpad issues, didn't trim NVME adapter board. (*Might be too power hungry. More testing needed.) || ||
|-
| 2242 || Sabrent Rocket || 1 TB || SB-RKTQ-1TB || good || || PS 0: 5.55W PS 1: 4.49W PS 2: 3.97W PS 3: 0.049W PS 4: 0.0018W APSTE: available || Yes
|-
| 2280 || MyDigitalSSD SBXe || 960 GB || || good || || APST enabled Power states N/A || N/A
|-
| 2280 || HP SSD EX900 || 250GB || || good || No low-power modes available || ||
|-
| 2280 || HP SSD EX950 || 512GB || || good || Unsure about low-power modes || ||
|-
| 2280 || WD BLUE SN550 || 1TB || WDC WDS100T2B0C-00PXH0 || WARNING good || WARNING mine was SATA and does NOT work! Booted successfully from NVMe (Bionic MATE) || PS 0: 3.50W PS 1: 2.70W PS 2: 1.90W APSTE Disabled by default || N/A
|-
| 2280 || WD Blue SN550 || 500GB || WDC WDS500G2B0C-00PXH0 || good || || PS 0: 3.50W PS 1: 2.40W PS 2: 1.90W APSTE enabled by default with 5.9 kernel (Manjaro XFCE) || No ||
|-
| 2280 || WD Blue SN500 || 500GB || WDS500G1B0C || fail || Works OK on power state 2 (2.5W), but hangs the system whenever there is intense IO (peak draw) on the drive || ||
|-

| 2242 || WD PC SN520 || 256GB || - || fail || Power LED Flashes. Nothing else happens. || ||
|-
| 2280 || WD PC SN730 || 512GB || SDBPNTY-512G-1032 || good || No touchpad issues. Works after latest updates. ||APST enabled by default PS 0: 5.50W PS 1: 3.50W PS 2: 3.00W PS 3: 0.0700W PS 4: 0.0025W || No ||
|-
| 2280 || WD BLACK SN750 || 250GB || WDS250G3X0C-00SJG0 || good || No touchpad issues, didn't trim NVME adapter board. || APSTE disabled by default PS 0: 5.00W PS 1: 3.50W PS 2: 3.00W||
|-
| 2280 || WD BLACK SN750 || 500GB || WDS500G3X0C-00SJG0 || good || No tp issues. had to charge battery for 20% initially. || APSTE disabled by default PS 0: 5.50W PS 1: 3.50W PS 2: 3.00W PS 3: 0.07W PS 4: 0.0025W||
|-
| 2280 || WD BLACK SN750 || 1TB || WDS100T3X0C-00SJG0 || mixed || Drive works as expected (so far) though with 50% reduction in battery life. Unable to set power mode (due to APST being enabled?). Also unable to suspend PineBook Pro with NVMe drive attached. From dmesg: rockchip-pcie f8000000.pcie: PCIe link enter L2 timeout! PM: dpm_run_callback(): rockchip_pcie_suspend_noirq+0x0/0x100 returns -110 PM: Devvice f8000000.pcie failed to suspend noirq: error -110 PM: no irq suspend of devices failed || APST enabled by default PS 0: 6.00W PS 1: 3.50W PS 2: 3.00W PS 3: 0.1000W PS 4: 0.0025W || No
|-
| 2242 || KingSpec NE-512 || 512 GB || NE512 || good || || APST enabled Power states N/A || N/A
|-
| 2230 || Kioxia BG4 256GBTB|| 256 GB || KBG40ZNS256G || good || || APST enabled by default Power states PS 0: 3.60W PS 1: 2.60W PS 2: 2.20W PS 3: 0.005W PS 4: 0.005W ||
|-
| 2280 || Patriot P300 || 256 GB || P300P256GM28US || good || Booted successfully with / on NVMe and /boot on eMMC (Armbian Buster) || APSTE disabled by default PS 0: 4.50W PS 1: 2.70W PS 2: 2.16W PS 3: 0.07W PS 4: 0.002W||
|-
| 2280 || Team Group MP33 || 128 GB || TM8FP6128G0C101 || good || || ||
|-
| 2280 || Team Group MP34 || 512 GB || TM8FP6512G0C101 || fail ||APST enabled by default and scripts do not change the power mode. Higher power consumption modes cause the PBP to crash || PS 0 5.55W PS 1 4.49W PS 2 3.97W PS 3 0.0490W PS 4 0.0018W ||No
|-
| 2280 || Digifast Ace || 256 GB || DGFA256M2L01 || good ||No touchpad issues. Board not trimmed. || PS 0 6.77W PS 1 5.71W PS 2 5.19W PS 3 0.0490W PS 4 0.0018W ||Yes
|-
| 2280 || Toshiba XG6 || 256 GB || KXG60ZNV256G || good || || PS 0: 6.00W PS 1: 2.70W PS 2: 1.30W PS 3: 0.0500W PS 4: 0.0050W PS 5: 0.0030W APSTE: enabled by default || No

|}

== microSD Cards ==
{| class="wikitable sortable"
!Type || Make/Model || Hardware IDs || Result || Notes
|-
|SD Card || Samsung Evo Select 512GB || MB-ME512GA/AM || good ||
|-
|SD Card || Samsung Evo Plus 64GB || || good || Hdparm tested 44MBps read speeds
|-
|SD Card || Sandisk Ultra 400GB || || good || Works fine as a storage extension. Mounted for pictures, etc.
|-
|SD Card || Sandisk Ultra 16GB || || fail || Works for a short period of time but locks up completely after a certain amount of written data
|-
|SD Card || Sandisk Ultra 64GB (Old from 2015) || || fail || ^
|-
|SD Card || Sandisk Extreme 64GB || || good || Speeds seem a little slow (67MB/s read compared to 160MB/s rating) but response time and reliability is good
|-
|SD Card || Sandisk Extreme Pro 64GB || || good ||
|}

= USB hardware =

== USB Card Readers ==

Standalone card readers only, please; see below for multifunction devices.

{| class="wikitable sortable"
!Type || Make/Model || Hardware IDs || Result || Notes
|-
|USB-2 SDHC reader || Sandisk MobileMate+ || 0781:b2b3 || good ||
|-
|USB-3 SDHC/CF reader || Transcend TS-RDF8K || 8564:4000 || good ||
|}

== USB Networking ==

Standalone network devices only, please; see below for multifunction devices

{| class="wikitable sortable"
!Type || Make/Model || Hardware IDs || Result || Notes
|-
|USB-2 Fast Ethernet adapter || Realtek RTL8152 || 0bda:8152 || good ||
|-
|USB-2 Ethernet adapter || ASIX AX77882 || 0b95:7720 || good ||
|-
|USB Wifi Dongle || TP-Link TL-WN725N || 0bda:8179 || good || RTL8188EUS, Driver=rtl8188eu from MrFixit stock Debian, works better than internal Broadcom, but signal still not great, https://www.amazon.com/gp/product/B008IFXQFU/
|-
|USB Wifi Dongle || Shenzhen Dudes Tech #8541553244 || 0bda:c811 || mixed || plug/play on stock Armbian Buster with driver rtl8821cu; could not get operating driver built on MrFixit Debian or Manjaro KDE Plasma. Works 2x+ better than internal Broadcom on Armbian. https://www.amazon.com/gp/product/B07F595V22/
|-
|USB 3 to Gigabit Ethernet Adapter || Pluggable USB 3.0 to Ethernet Gigabit (ASIX AX88179 chipset) || 0b95:1790 || good ||
|}

== USB Multifunction Devices ==

{| class="wikitable sortable"
!Type || Make/Model || Hardware IDs || Result || Notes
|-
|USB-C Hub || Samsung EE-P5000 || || Power is passed through from hub to Pinebook Pro; Ethernet, HDMI, and USB-A do not work ||
|-
|USB-C Hub || Insignia NS-PU378CHM || || Power is passed through from hub to Pinebook Pro; USB-A works; HDMI does not work ||
|-
|USB-C Hub || Dell WD19TB || || Power is passed through from hub to Pinebook Pro; Ethernet and USB-A work; Neither Display Port nor HDMI work; audio not tested ||
|-
|USB-C Hub || Totu 8-in-1 || 058f:8468, 2109:0817 USB3, 1a40:0801, 2109:2817 USB2, bda:8153 RTL8153 Gigabit Ethernet || Network, USB, Card Reader, Power Good, HDMI Not Working || Amazon Smile [https://smile.amazon.com/gp/product/B07FX2LW35/]
|-
|USB-C Hub || Delock 87721 || || Network Works, USB Works, Card Reader not tested, Power Good, HDMI Works but does not show as an extra output in X. It just mirrors the default display || Delock 87721 [https://www.delock.de/produkte/G_87721/merkmale.html?setLanguage=en]
|-
|USB-3 combo hub (network, card slots, usb ports) || generic || 05e3:0610 hub, 0bda:8153 gigE, 05e3:0743 card reader || Network good, usb ports good, card reader good ||
|-
|USB-C combo hub (network, card slots, usb ports) || generic || 05e3:0612 hub, 0bda:8153 realtek gigE || Network good, usb ports fail, card reader fail ||
|-
|5-1 USB-C hub || [https://www.aliexpress.com/item/32954358411.html from aliexpress] || 05e3:0626 hub || HDMI, Network, USB-3, USB-C PD [http://www.sympato.ch/~dryak/files/usbc-dock.jpg good] || Might need changing orientation or USB-C cable
|-
|4 Port USB 3 NIC || Delock 62966 || || good || 4 individually controllable Gigabit Ethernet Ports. Consider using it with own power supply
|-
|USB-C combo hub || [https://www.amazon.com/gp/product/B07XKRGQQ2/ from Amazon] || 0c76:161f 0c45:6321 2109:0813 1a40:0101 || good || Everything works: AltMode DP, Ethernet, SD card, USB-A and C, and charging using the stock Debian, and Ubuntu.
|-
|USB-C dock || i-Tec USB-C Metal Nano Dock 4K HDMI w/ LAN || 0bda:0411 hub, 0bda:8153 ethernet || mixed || plug & play with Manjaro, HDMI tested w/ fullHD only, works but only in one polarity. Sound output works, USB hub works. HDMI output may not be recognized by Plasma if dock is connected with HDMI port disconnected. NIC recognized by kernel, but untested if link actually works. USB power delivery works only in one polarity. Unfortunately HDMI works with opposite polarity than USB PD.
|-
|USB-C dock || Planet Computers Gemini USB-C hub || 0bda:0411 hub, 0bda:8153 ethernet || good || USB works, NIC recognized by kernel, but untested if link actually works. Interestingly, dmesg shows unconnected alternate mode DP, but no connector is present. It seems as if PlanetCom actually made custom version of above i-Tec device.
|-
|USB-C dock || DELL USB-C to HDMI/VGA/Ethernet/USB 3.0 DA200g || idVendor=05e3, idProduct=0610, bcdDevice=49.70 || mixed || USB works, detected as u port usb hub, the rest is not working
|-
|USB-C dock || Lenovo ThinkPad 40A9 || TBD || mixed || USB hub works, audio device works, ethernet device works, display does NOT despite plug's orientation
|}

== USB C alternate mode DP ==
Note that only USB C alternate mode Display Port will pass video. Any HDMI, DVI or VGA port must be converted internally by the device from Display Port - or the device won't work for video.
{| class="wikitable sortable"
!Type || Make/Model || Hardware IDs || Result || Notes
|-
|USB-C to HDMI adapter 201018 || Cable Matters || || good || Tested up to 1080p30, audio works
|-
|USB-C to HDMI adapter || Choetech HUB-H06 || || good || Advertises support for 4K@60Hz, tested up to 1080p@60Hz, worked in both Debian and Manjaro 2020-04-04
|-
|USB-C to HDMI adapter || generic || || good || Tested up to 4k60
|-
|USB-C to DP Adapter || OrxnQ || 04b4:5210 || good || Advertises support for 4K@60Hz, tested up to 1080p. Only FullHD resolutions available on Debian.
|-
|USB-C HDMI adapter (DP-alt mode) || QGeeM || || good || Manjaro 2020-01-25
|-
|USB C Hub to HDMI VGA SD TF Card Reader 3USB 3.0 and USB C Power Pass-Through Port || MOKiN|| || good || tested to 1080p, sdcards can read from one write to another --Manjaro 2020-11-11 https://smile.amazon.com/gp/product/B07MP9P6B7/
|-
|USB-C combo hub (HDMI, network, card slots, USB ports) || generic || || fail ||
|-
|USB-C combo hub (HDMI, VGA, Ethernet, card slots, USB 2 & 3 || Powlaken || 05e3:0610 0bda:8153 || USB, Power, Ethernet and SD good, HDMI and VGA fail
|-
|USB-C Dock (HDMI, VGA, Ethernet, microSD/SD card slots, 2 USB 3 Ports, 1 USB-C Port, USB-Power Passthru || Digitus DA-70865 || || USB, Ethernet and MicroSD/SD good, video crashes System (fail). || Tested on Manjaro w/ Kernel 5.5. You have to turn the USB-C connector upside down for it to work. Video seems to be a driver issue.
|-
|USB-C Dock (HDMI, VGA, Ethernet, microSD/SD card slots, 2 USB 3 Ports, 1 USB-C Port, USB-Power pass-through) || generic || || Ethernet and MicroSD/SD good, USB fail, video up to 1080p. || https://forum.pine64.org/showthread.php?tid=8728
|-
|USB-C Dock (DP, HDMI, 1Gbps Ethernet, SD card slot, 2 USB 3 Ports, USB-C power in port || goFanco || || DP, Ethernet & USB good, (HDMI & SD card untested). Video tested good to 1080p || Tested on default Debian
|-
|USB-C Dock (HDMI, USB 3.0 x 2, USB-C PD Pass Thru Power Port Up to 100W, SD/TF Card Reader || Hiearcool 7-in-1 || || HDMI, USB, Power Port good, SD/TF Reader fail || Default Debian
|-
|USB-C 3.0 Multi-Port Hub (HDMI, USB 3.0 x 1, USB-C charge only) || Linden LITCAD17 || || HDMI and USB good, Power Port fail || Default Debian & ayufan Ubuntu
|-
|USB-C to DP adapter || Nekteck || 04b4:5210 || good || Shows up as "Cypress Semiconductor Corp. Billboard Device" in lsusb and dmesg output. Works in latest Manjaro (as of January 26, 2020) with no issues. Only FullHD resolutions available on Debian.
|-
|USB-C to HDMI adapter || MHL TH002 || || good || Tested at 1080p@60
|-
|USB-C combo hub (USB-C power, HDMI, 2xUSB, 1xUSB-C(no power)) || Baseus || || good
|-
|USB-C Travel Dock with DP ALT-MODE || Targus DOCK411-A || 0835:2a01 (BILLBOARD DEVICE) 0bda:8153 (RTL8153 GbE Adapter) || GbE: works, HDMI: works, USB3.0 port: works, VGA: unknown || HDMI@1080p@60Hz: works OK, HDMI@4K@30Hz: works but buggy. GbE is only picked up when the USB C is plugged in with one certain side facing upwards. It is not detected the other way around. (Sounds weird, but reproduced it multiple times.)
|-
|USB-C to DP adapter || MediaGearPro AC0011 || 2109:0100 (USB 2.0 BILLBOARD) || DP: works || Only 1080p@60Hz is available, 4K resolutions not possible in contrast to what the manufacturer claims.
|-
|USB-C to DP cable || Generic on ebay || || good but with issues || Had some wonky framerates when tested on a 144hz monitor, 60hz mode was actually sent as ~48hz, 120hz mode was actually sent at ~112hz and 144hz mode was actually sent at ~120hz
|-
|UGREEN Hub USB C 9 in 1 HDMI and VGA || UGREEN || || good || VGA and HDMI works but not at the same time. HDMI audio not tested. Switching between HDMI and VGA need to replug the hub.
|-
|USB-C Dock 6-in-1 HDMI || Ugreen 50771 || || HDMI: works, Ethernet: works, 3x USB: works, USB-PD: works || Tested on Manjaro 2020/03/18 Works USB-C PD Chargers provided they can do 5V3A, works with 5V3A USB-C Raspberry Pi 4 power supply (Doesn't work with 5V2A USB-C). No HDMI Audio.
|-
|USB-C to DP cable || [https://www.amazon.es/gp/product/B01N5RFAI4/ CHOETECH V-XCP-0012BK] || || good
|-
| [https://www.apple.com/ca/shop/product/MQ4H2AM/A/thunderbolt-3-usb%E2%80%91c-cable-08-m Thunderbolt 3 (USB‑C) Cable (0.8 m)] || Apple || || Display Port Alternate Mode: Fails, USB-PD: works || Tested on Manjaro 2020/05/29 - Charges but no video
|-
|USB-C to HDMI cable || Planet Computers USB-C to HDMI cable || || fail || does not work regardless of orientation in USB slot
|-
|USB-C combo hub || Moreslan 11in1 (https://www.amazon.fr/gp/product/B08397B66G) || || good || GbE: OK, HDMI: OK, 4 usb ports: OK, Power via USB-C: OK, microSD: OK, TFT: OK, Jack: OK, VGA: Not tested; UPDATE: HDMI Display not working anymore since Manjaro release 20.08
|-
|USB-C Multiport Adapter || [https://www.wentronic.com/en/usb-ctm-multiport-adapter-hdmi-ethernet-pd-white-62105 Goobay 62105] || || Fail || GbE: OK, UBS port: OK, Power via USB-C: OK, HDMI: Does generate an image, but it jumps X pixels right from time to time (4K@30 and FHD)
|-
| USB Type-C to HDMI Adapter || Insignia NS-PU369CH-WH || 0bda:5400|| good || tested on kernel 5.5.0, video out works, audio not tested
|}

== USB other ==
{| class="wikitable sortable"
!Type || Make/Model || Hardware IDs || Result || Notes
|-
|Wireless Mouse || Logitech M705 Marathon || || good || Uses Logitech receiver. Battery level detected in power settings.
|-
|Wireless Mouse || Logitech G305 || || good || Uses Logitech receiver
|-
|Gamepad || Sertronics SNES Style Controller || || good || Tested in retroarch, Sertronics is also known as Berrybase
|-
|Drawing tablet || XP Pen G430s || 28bd:0913 || good || Hardware works, official software not used, tablet was configured using udev rules which are more functional than official software anyway
|-
|Yubikey original || Yubico || 1050:0010 || good ||
|-
|}

----

= Bluetooth hardware =
{| class="wikitable sortable"
!Type || Make/Model || Hardware IDs || Result || Notes
|-
|Bluetooth Mouse || HP Z5000 || E5C13AA || good ||
|-
|Bluetooth Mouse || Logitech M557 || || good ||
|-
|Bluetooth Mouse || Kensington Expert Wireless Trackball || || good ||
|-
|Bluetooth Mouse || Logitech MX Vertical || || good || Battery level is not detected over bluetooth, detected when using the logitech receiver
|-
|Bluetooth Mouse || Logitech Triathlon M720 || || good ||
|-
|Bluetooth Mouse || Logitech Ultra-Thin Touch Mouse || || good || Detects battery level as "keyboard"
|-
|Bluetooth Mouse || Logitech MX Anywhere 2 || || good ||
|-
|Bluetooth Mouse || Logitech M535 || 910-004432 || good ||
|-
|Bluetooth Mouse || Microsoft Bluetooth Mouse || RJN-00002 || good ||
|-
|Bluetooth Mouse || Fenifox low profile || MX106-Black || good ||
|-
|Bluetooth Mouse || Technet || MGS479 || good ||
|-
|Bluetooth Keyboard || Logitech MX Keys || || good || Battery level is not detected over bluetooth, detected when using the logitech receiver
|-
|Bluetooth Speaker || Ivation Acoustix || || good || Use audio sink profile
|-
|Bluetooth Headphones || Sony WH-1000XM2 || || good* || Needs pulseaudio-module-bluetooth. *Recording untested.
|-
|Bluetooth Headphones || COWIN SE7 Noise Cancelling Headphones || || good || Pairs and plays audio with stock Debian OS. More detail [https://forum.pine64.org/showthread.php?tid=8192&pid=60682#pid60682 here].
|-
|USB Audio & Bluetooth Headset || Sony SBH90C || || good || Works well connected via USB Type-C and Bluetooth.
|-
|Bluetooth Headset || BlueAnt Ribbon || 7252A-RB || good || a2dp mode works, headset mode seems to work, out of box with manjaro
|-
|Bluetooth Headphones || DO-SV-BTIES03 || || good || Tested on Manjaro ARM - kde
|-
|Bluetooth Headset || TaoTronics TT-BH090 || || good || Microphone not tested but should work as expected of a normal Linux machine
|-
|Bluetooth Mouse || Logitech MX Ergo || || good || Works flawlessly both on Manjaro and Armbian.
|}

----

= Other hardware =

{| class="wikitable sortable"
!Type || Make/Model || Hardware IDs || Result || Notes
|-
|[https://www.aliexpress.com/item/32831647303.html USB charging cable] || - || - || good || Got the cable a while back so may not be identical to current product
|-
|Printer || HP DeskJet Ink Advantage 3775 || || good* || Using hplip-gui: via USB and WiFi. *Only print function tested.
|-
|}

[[Category:PineBook Pro]]

Pinebook Pro Hardware Accessory Compatibility

2021-05-20T01:12:31Z

BenTheTechGuy: Add Toshiba KXG60ZNV256G

Please test as many things as you can find with your [[Pinebook Pro]] and share the results here. Some devices which should work don't!

= Storage =

== NVMe SSD drives ==
Only PCI Express M.2 drives can work, due to the available connectivity of the Pinebook Pro. Consequently, SATA or USB M.2 cards will not work.

You need to buy and install the M.2 adaptor in order to fit one, please see [[Pinebook_Pro#Using_the_optional_NVMe_adapter]]

Please see [[Pinebook Pro Troubleshooting Guide#NVMe SSD issues|a separate section]] that describes reported issues with the NVMe drives in PineBook Pro.

{| class="wikitable sortable"
!Type || Make/Model || Size || Hardware IDs || Result || Notes || Power options Active only || Save power setting?
|-
| 2280 || Crucial P1 || 1 TB || CT1000P1SSD8 || good || With PS 2 and APST impact on battery life seems to be minimal. Running powerstat seems to confirm little additional power draw. || PS 0: 9.00W PS 1: 4.60W PS 2: 3.80W PS 3: 0.0300W PS 4: 0.0030W APSTE: enabled by default || Yes
|-
| 2280 || Kingston A2000 || 250 GB || SA2000M8250G || good || || PS 0: 9.00W PS 1: 4.60W PS 2: 3.80W PS 3: 0.045W PS 4: 0.004W APSTE: enabled by default || Yes
|-
| 2280 || Kingston A2000 || 1 TB || SA2000M81000G || good || || same as 250 GB || Yes
|-
| 2242 || Toshiba OCZ RC 100 || 240 GB || RC100-M22242-240G || good || || ||
|-
| 2242 || Lexar NM520 || 256 GB || LNM520-256RBNA || good ||For some data on power use and performance, see [https://forum.pine64.org/showthread.php?tid=9029 here.] || PS 0: 3.05W PS 1: 2.44W PS 2: 2.02W || No. See [https://forum.pine64.org/showthread.php?tid=8737&pid=56481#pid56481 workaround].
|-
| 2280 || XPS SX8200 || 512 GB || ASX8200PNP-512GT-C || good || Performed [https://forum.pine64.org/showthread.php?tid=8322 these] steps for physical installation. Currently rooting from drive. || ||
|-
| 2280 || Intel 660p M.2 || 512 GB || SSDPEKNW512G8X1 || good || PS 1 (2.70W) will work without issues, even under heavy load. Recommended over PS 2, as PS 2 will incur an additional 80% performance penalty. APSTE shows enabled but drive does not support it. || PS 0: 3.50W PS 1: 2.70W PS 2: 2.00W || No
|-
| 2280 || Intel 660p M.2 || 1 TB || SSDPEKNW010T8X1 || good || || PS 0: 4.00W PS 1: 3.00W PS 2: 2.20W APSTE Disabled by default || No
|-
| 2280 || Intel 660p M.2 || 2 TB || SSDPEKNW020T8 || good || [https://forum.pine64.org/showthread.php?tid=7524&pid=49300#pid49300 Performance tests results] || PS 0: 5.50W PS 1: 3.60W PS 2: 2.60W PS 3: 0.0300W PS 4: 0.0040W || No
|-
| 2280 || Intel 760p M.2 || 128 GB || SSDPEKKW128G8 || good || Firmware Revision 004C || PS 0: 9.00W PS 1: 4.60W PS 2: 3.80W PS 3: 0.045W PS 4: 0.004W APSTE: disabled by default with 4.4 kernel (mrfixit Debian), enabled by default with 5.6 kernel (Manjaro KDE) || Yes
|-
| 2280 || Intel 760p M.2 || 256 GB || SSDPEKKW256G8 || good || Firmware Revision 004C || PS 0: 9.00W PS 1: 4.60W PS 2: 3.80W PS 3: 0.045W PS 4: 0.004W Need to use lower power. ||
|-
| 2280 || integral 256GB SSD M.2 2280 NVME || 256 GB || INSSD256GM280NM1 || usable || || PS 0: 9.00W || No
|-
| 2280 || Samsung 970 EVO Plus || 250 GB || MZ-V7S250BW || fail || Tested on Manjaro-ARM as root drive. Limited to PS 2 and Volatile Write Cache off gives the most stable results, but it will still hang on a hdparm test. || ||
|-
| 2280 || Samsung 970 EVO Plus || 500 GB || MZ-V7S500 || fail || Too power hungry? || PS 0: 6.2W PS 1: 4.3W PS 2: 2.1W ||
|-
| 2280 || Samsung 970 EVO || 1 TB || MZ-V7E1T0BW || fail || Too power hungry? || ||
|-
| 2280 || Samsung 970 PRO || 1 TB || MZ-V7P1T0BW || good || || PS 0: 6.20W PS 1: 4.30W PS 2: 2.10W PS 3: 0.04W PS 4: 0.005W APSTE: enabled by default || Yes
|-
| 2280 || Corsair MP300 || 120 GB || CSSD-F120GBMP300 || good || || PS 0: 3.00W PS 1: 2.00W PS 2: 2.00W PS 3: 0.1W PS 4: 0.005W APSTE Disabled by default ||
|-
| 2280 || Silicon Power P34A60 || 1TB || SP001TBP34A60M28 || Usable || Power eager, but doesn't seem to use all 9W all the time, only under heavy I/O || PS 0: 9W || N/A
|-
| 2280 || Silicon Power P34A60 || 256 GB || SPCC M.2 PCIe SSD || detected || ASIN B07ZH6QR8Q "Silicon Power PCIe M.2 NVMe SSD 256GB Gen3x4" / PCIe A60 || PS 0: 6.77W PS 1: 5.71W PS 2: 5.19W APSTE Enabled by default || No
|-
| 2280 || Silicon Power P34A60 || 256 GB || ??? || fail || Isn't detected || ||
|-
| 2280 || Sabrent Rocket || 256 GB || SB-ROCKET-256 || good || || || No
|-
| 2242 || Sabrent Rocket Nano || 512 GB || SB-1342-512 || good* || No touchpad issues, didn't trim NVME adapter board. (*Might be too power hungry. More testing needed.) || ||
|-
| 2242 || Sabrent Rocket || 1 TB || SB-RKTQ-1TB || good || || PS 0: 5.55W PS 1: 4.49W PS 2: 3.97W PS 3: 0.049W PS 4: 0.0018W APSTE: available || Yes
|-
| 2280 || MyDigitalSSD SBXe || 960 GB || || good || || APST enabled Power states N/A || N/A
|-
| 2280 || HP SSD EX900 || 250GB || || good || No low-power modes available || ||
|-
| 2280 || HP SSD EX950 || 512GB || || good || Unsure about low-power modes || ||
|-
| 2280 || WD BLUE SN550 || 1TB || WDC WDS100T2B0C-00PXH0 || WARNING good || WARNING mine was SATA and does NOT work! Booted successfully from NVMe (Bionic MATE) || PS 0: 3.50W PS 1: 2.70W PS 2: 1.90W APSTE Disabled by default || N/A
|-
| 2280 || WD Blue SN550 || 500GB || WDC WDS500G2B0C-00PXH0 || good || || PS 0: 3.50W PS 1: 2.40W PS 2: 1.90W APSTE enabled by default with 5.9 kernel (Manjaro XFCE) || No ||
|-
| 2280 || WD Blue SN500 || 500GB || WDS500G1B0C || fail || Works OK on power state 2 (2.5W), but hangs the system whenever there is intense IO (peak draw) on the drive || ||
|-

| 2242 || WD PC SN520 || 256GB || - || fail || Power LED Flashes. Nothing else happens. || ||
|-
| 2280 || WD PC SN730 || 512GB || SDBPNTY-512G-1032 || good || No touchpad issues. Works after latest updates. ||APST enabled by default PS 0: 5.50W PS 1: 3.50W PS 2: 3.00W PS 3: 0.0700W PS 4: 0.0025W || No ||
|-
| 2280 || WD BLACK SN750 || 250GB || WDS250G3X0C-00SJG0 || good || No touchpad issues, didn't trim NVME adapter board. || APSTE disabled by default PS 0: 5.00W PS 1: 3.50W PS 2: 3.00W||
|-
| 2280 || WD BLACK SN750 || 500GB || WDS500G3X0C-00SJG0 || good || No tp issues. had to charge battery for 20% initially. || APSTE disabled by default PS 0: 5.50W PS 1: 3.50W PS 2: 3.00W PS 3: 0.07W PS 4: 0.0025W||
|-
| 2280 || WD BLACK SN750 || 1TB || WDS100T3X0C-00SJG0 || mixed || Drive works as expected (so far) though with 50% reduction in battery life. Unable to set power mode (due to APST being enabled?). Also unable to suspend PineBook Pro with NVMe drive attached. From dmesg: rockchip-pcie f8000000.pcie: PCIe link enter L2 timeout! PM: dpm_run_callback(): rockchip_pcie_suspend_noirq+0x0/0x100 returns -110 PM: Devvice f8000000.pcie failed to suspend noirq: error -110 PM: no irq suspend of devices failed || APST enabled by default PS 0: 6.00W PS 1: 3.50W PS 2: 3.00W PS 3: 0.1000W PS 4: 0.0025W || No
|-
| 2242 || KingSpec NE-512 || 512 GB || NE512 || good || || APST enabled Power states N/A || N/A
|-
| 2230 || Kioxia BG4 256GBTB|| 256 GB || KBG40ZNS256G || good || || APST enabled by default Power states PS 0: 3.60W PS 1: 2.60W PS 2: 2.20W PS 3: 0.005W PS 4: 0.005W ||
|-
| 2280 || Patriot P300 || 256 GB || P300P256GM28US || good || Booted successfully with / on NVMe and /boot on eMMC (Armbian Buster) || APSTE disabled by default PS 0: 4.50W PS 1: 2.70W PS 2: 2.16W PS 3: 0.07W PS 4: 0.002W||
|-
| 2280 || Team Group MP33 || 128 GB || TM8FP6128G0C101 || good || || ||
|-
| 2280 || Team Group MP34 || 512 GB || TM8FP6512G0C101 || fail ||APST enabled by default and scripts do not change the power mode. Higher power consumption modes cause the PBP to crash || PS 0 5.55W PS 1 4.49W PS 2 3.97W PS 3 0.0490W PS 4 0.0018W ||No
|-
| 2280 || Digifast Ace || 256 GB || DGFA256M2L01 || good ||No touchpad issues. Board not trimmed. || PS 0 6.77W PS 1 5.71W PS 2 5.19W PS 3 0.0490W PS 4 0.0018W ||Yes
| 2280 || Toshiba XG6 || 256 GB || KXG60ZNV256G || good || || PS 0: 6.00W PS 1: 2.70W PS 2: 1.30W PS 3: 0.0500W PS 4: 0.0050W PS 5: 0.0030W APSTE: enabled by default || No

|}

== microSD Cards ==
{| class="wikitable sortable"
!Type || Make/Model || Hardware IDs || Result || Notes
|-
|SD Card || Samsung Evo Select 512GB || MB-ME512GA/AM || good ||
|-
|SD Card || Samsung Evo Plus 64GB || || good || Hdparm tested 44MBps read speeds
|-
|SD Card || Sandisk Ultra 400GB || || good || Works fine as a storage extension. Mounted for pictures, etc.
|-
|SD Card || Sandisk Ultra 16GB || || fail || Works for a short period of time but locks up completely after a certain amount of written data
|-
|SD Card || Sandisk Ultra 64GB (Old from 2015) || || fail || ^
|-
|SD Card || Sandisk Extreme 64GB || || good || Speeds seem a little slow (67MB/s read compared to 160MB/s rating) but response time and reliability is good
|-
|SD Card || Sandisk Extreme Pro 64GB || || good ||
|}

= USB hardware =

== USB Card Readers ==

Standalone card readers only, please; see below for multifunction devices.

{| class="wikitable sortable"
!Type || Make/Model || Hardware IDs || Result || Notes
|-
|USB-2 SDHC reader || Sandisk MobileMate+ || 0781:b2b3 || good ||
|-
|USB-3 SDHC/CF reader || Transcend TS-RDF8K || 8564:4000 || good ||
|}

== USB Networking ==

Standalone network devices only, please; see below for multifunction devices

{| class="wikitable sortable"
!Type || Make/Model || Hardware IDs || Result || Notes
|-
|USB-2 Fast Ethernet adapter || Realtek RTL8152 || 0bda:8152 || good ||
|-
|USB-2 Ethernet adapter || ASIX AX77882 || 0b95:7720 || good ||
|-
|USB Wifi Dongle || TP-Link TL-WN725N || 0bda:8179 || good || RTL8188EUS, Driver=rtl8188eu from MrFixit stock Debian, works better than internal Broadcom, but signal still not great, https://www.amazon.com/gp/product/B008IFXQFU/
|-
|USB Wifi Dongle || Shenzhen Dudes Tech #8541553244 || 0bda:c811 || mixed || plug/play on stock Armbian Buster with driver rtl8821cu; could not get operating driver built on MrFixit Debian or Manjaro KDE Plasma. Works 2x+ better than internal Broadcom on Armbian. https://www.amazon.com/gp/product/B07F595V22/
|-
|USB 3 to Gigabit Ethernet Adapter || Pluggable USB 3.0 to Ethernet Gigabit (ASIX AX88179 chipset) || 0b95:1790 || good ||
|}

== USB Multifunction Devices ==

{| class="wikitable sortable"
!Type || Make/Model || Hardware IDs || Result || Notes
|-
|USB-C Hub || Samsung EE-P5000 || || Power is passed through from hub to Pinebook Pro; Ethernet, HDMI, and USB-A do not work ||
|-
|USB-C Hub || Insignia NS-PU378CHM || || Power is passed through from hub to Pinebook Pro; USB-A works; HDMI does not work ||
|-
|USB-C Hub || Dell WD19TB || || Power is passed through from hub to Pinebook Pro; Ethernet and USB-A work; Neither Display Port nor HDMI work; audio not tested ||
|-
|USB-C Hub || Totu 8-in-1 || 058f:8468, 2109:0817 USB3, 1a40:0801, 2109:2817 USB2, bda:8153 RTL8153 Gigabit Ethernet || Network, USB, Card Reader, Power Good, HDMI Not Working || Amazon Smile [https://smile.amazon.com/gp/product/B07FX2LW35/]
|-
|USB-C Hub || Delock 87721 || || Network Works, USB Works, Card Reader not tested, Power Good, HDMI Works but does not show as an extra output in X. It just mirrors the default display || Delock 87721 [https://www.delock.de/produkte/G_87721/merkmale.html?setLanguage=en]
|-
|USB-3 combo hub (network, card slots, usb ports) || generic || 05e3:0610 hub, 0bda:8153 gigE, 05e3:0743 card reader || Network good, usb ports good, card reader good ||
|-
|USB-C combo hub (network, card slots, usb ports) || generic || 05e3:0612 hub, 0bda:8153 realtek gigE || Network good, usb ports fail, card reader fail ||
|-
|5-1 USB-C hub || [https://www.aliexpress.com/item/32954358411.html from aliexpress] || 05e3:0626 hub || HDMI, Network, USB-3, USB-C PD [http://www.sympato.ch/~dryak/files/usbc-dock.jpg good] || Might need changing orientation or USB-C cable
|-
|4 Port USB 3 NIC || Delock 62966 || || good || 4 individually controllable Gigabit Ethernet Ports. Consider using it with own power supply
|-
|USB-C combo hub || [https://www.amazon.com/gp/product/B07XKRGQQ2/ from Amazon] || 0c76:161f 0c45:6321 2109:0813 1a40:0101 || good || Everything works: AltMode DP, Ethernet, SD card, USB-A and C, and charging using the stock Debian, and Ubuntu.
|-
|USB-C dock || i-Tec USB-C Metal Nano Dock 4K HDMI w/ LAN || 0bda:0411 hub, 0bda:8153 ethernet || mixed || plug & play with Manjaro, HDMI tested w/ fullHD only, works but only in one polarity. Sound output works, USB hub works. HDMI output may not be recognized by Plasma if dock is connected with HDMI port disconnected. NIC recognized by kernel, but untested if link actually works. USB power delivery works only in one polarity. Unfortunately HDMI works with opposite polarity than USB PD.
|-
|USB-C dock || Planet Computers Gemini USB-C hub || 0bda:0411 hub, 0bda:8153 ethernet || good || USB works, NIC recognized by kernel, but untested if link actually works. Interestingly, dmesg shows unconnected alternate mode DP, but no connector is present. It seems as if PlanetCom actually made custom version of above i-Tec device.
|-
|USB-C dock || DELL USB-C to HDMI/VGA/Ethernet/USB 3.0 DA200g || idVendor=05e3, idProduct=0610, bcdDevice=49.70 || mixed || USB works, detected as u port usb hub, the rest is not working
|-
|USB-C dock || Lenovo ThinkPad 40A9 || TBD || mixed || USB hub works, audio device works, ethernet device works, display does NOT despite plug's orientation
|}

== USB C alternate mode DP ==
Note that only USB C alternate mode Display Port will pass video. Any HDMI, DVI or VGA port must be converted internally by the device from Display Port - or the device won't work for video.
{| class="wikitable sortable"
!Type || Make/Model || Hardware IDs || Result || Notes
|-
|USB-C to HDMI adapter 201018 || Cable Matters || || good || Tested up to 1080p30, audio works
|-
|USB-C to HDMI adapter || Choetech HUB-H06 || || good || Advertises support for 4K@60Hz, tested up to 1080p@60Hz, worked in both Debian and Manjaro 2020-04-04
|-
|USB-C to HDMI adapter || generic || || good || Tested up to 4k60
|-
|USB-C to DP Adapter || OrxnQ || 04b4:5210 || good || Advertises support for 4K@60Hz, tested up to 1080p. Only FullHD resolutions available on Debian.
|-
|USB-C HDMI adapter (DP-alt mode) || QGeeM || || good || Manjaro 2020-01-25
|-
|USB C Hub to HDMI VGA SD TF Card Reader 3USB 3.0 and USB C Power Pass-Through Port || MOKiN|| || good || tested to 1080p, sdcards can read from one write to another --Manjaro 2020-11-11 https://smile.amazon.com/gp/product/B07MP9P6B7/
|-
|USB-C combo hub (HDMI, network, card slots, USB ports) || generic || || fail ||
|-
|USB-C combo hub (HDMI, VGA, Ethernet, card slots, USB 2 & 3 || Powlaken || 05e3:0610 0bda:8153 || USB, Power, Ethernet and SD good, HDMI and VGA fail
|-
|USB-C Dock (HDMI, VGA, Ethernet, microSD/SD card slots, 2 USB 3 Ports, 1 USB-C Port, USB-Power Passthru || Digitus DA-70865 || || USB, Ethernet and MicroSD/SD good, video crashes System (fail). || Tested on Manjaro w/ Kernel 5.5. You have to turn the USB-C connector upside down for it to work. Video seems to be a driver issue.
|-
|USB-C Dock (HDMI, VGA, Ethernet, microSD/SD card slots, 2 USB 3 Ports, 1 USB-C Port, USB-Power pass-through) || generic || || Ethernet and MicroSD/SD good, USB fail, video up to 1080p. || https://forum.pine64.org/showthread.php?tid=8728
|-
|USB-C Dock (DP, HDMI, 1Gbps Ethernet, SD card slot, 2 USB 3 Ports, USB-C power in port || goFanco || || DP, Ethernet & USB good, (HDMI & SD card untested). Video tested good to 1080p || Tested on default Debian
|-
|USB-C Dock (HDMI, USB 3.0 x 2, USB-C PD Pass Thru Power Port Up to 100W, SD/TF Card Reader || Hiearcool 7-in-1 || || HDMI, USB, Power Port good, SD/TF Reader fail || Default Debian
|-
|USB-C 3.0 Multi-Port Hub (HDMI, USB 3.0 x 1, USB-C charge only) || Linden LITCAD17 || || HDMI and USB good, Power Port fail || Default Debian & ayufan Ubuntu
|-
|USB-C to DP adapter || Nekteck || 04b4:5210 || good || Shows up as "Cypress Semiconductor Corp. Billboard Device" in lsusb and dmesg output. Works in latest Manjaro (as of January 26, 2020) with no issues. Only FullHD resolutions available on Debian.
|-
|USB-C to HDMI adapter || MHL TH002 || || good || Tested at 1080p@60
|-
|USB-C combo hub (USB-C power, HDMI, 2xUSB, 1xUSB-C(no power)) || Baseus || || good
|-
|USB-C Travel Dock with DP ALT-MODE || Targus DOCK411-A || 0835:2a01 (BILLBOARD DEVICE) 0bda:8153 (RTL8153 GbE Adapter) || GbE: works, HDMI: works, USB3.0 port: works, VGA: unknown || HDMI@1080p@60Hz: works OK, HDMI@4K@30Hz: works but buggy. GbE is only picked up when the USB C is plugged in with one certain side facing upwards. It is not detected the other way around. (Sounds weird, but reproduced it multiple times.)
|-
|USB-C to DP adapter || MediaGearPro AC0011 || 2109:0100 (USB 2.0 BILLBOARD) || DP: works || Only 1080p@60Hz is available, 4K resolutions not possible in contrast to what the manufacturer claims.
|-
|USB-C to DP cable || Generic on ebay || || good but with issues || Had some wonky framerates when tested on a 144hz monitor, 60hz mode was actually sent as ~48hz, 120hz mode was actually sent at ~112hz and 144hz mode was actually sent at ~120hz
|-
|UGREEN Hub USB C 9 in 1 HDMI and VGA || UGREEN || || good || VGA and HDMI works but not at the same time. HDMI audio not tested. Switching between HDMI and VGA need to replug the hub.
|-
|USB-C Dock 6-in-1 HDMI || Ugreen 50771 || || HDMI: works, Ethernet: works, 3x USB: works, USB-PD: works || Tested on Manjaro 2020/03/18 Works USB-C PD Chargers provided they can do 5V3A, works with 5V3A USB-C Raspberry Pi 4 power supply (Doesn't work with 5V2A USB-C). No HDMI Audio.
|-
|USB-C to DP cable || [https://www.amazon.es/gp/product/B01N5RFAI4/ CHOETECH V-XCP-0012BK] || || good
|-
| [https://www.apple.com/ca/shop/product/MQ4H2AM/A/thunderbolt-3-usb%E2%80%91c-cable-08-m Thunderbolt 3 (USB‑C) Cable (0.8 m)] || Apple || || Display Port Alternate Mode: Fails, USB-PD: works || Tested on Manjaro 2020/05/29 - Charges but no video
|-
|USB-C to HDMI cable || Planet Computers USB-C to HDMI cable || || fail || does not work regardless of orientation in USB slot
|-
|USB-C combo hub || Moreslan 11in1 (https://www.amazon.fr/gp/product/B08397B66G) || || good || GbE: OK, HDMI: OK, 4 usb ports: OK, Power via USB-C: OK, microSD: OK, TFT: OK, Jack: OK, VGA: Not tested; UPDATE: HDMI Display not working anymore since Manjaro release 20.08
|-
|USB-C Multiport Adapter || [https://www.wentronic.com/en/usb-ctm-multiport-adapter-hdmi-ethernet-pd-white-62105 Goobay 62105] || || Fail || GbE: OK, UBS port: OK, Power via USB-C: OK, HDMI: Does generate an image, but it jumps X pixels right from time to time (4K@30 and FHD)
|-
| USB Type-C to HDMI Adapter || Insignia NS-PU369CH-WH || 0bda:5400|| good || tested on kernel 5.5.0, video out works, audio not tested
|}

== USB other ==
{| class="wikitable sortable"
!Type || Make/Model || Hardware IDs || Result || Notes
|-
|Wireless Mouse || Logitech M705 Marathon || || good || Uses Logitech receiver. Battery level detected in power settings.
|-
|Wireless Mouse || Logitech G305 || || good || Uses Logitech receiver
|-
|Gamepad || Sertronics SNES Style Controller || || good || Tested in retroarch, Sertronics is also known as Berrybase
|-
|Drawing tablet || XP Pen G430s || 28bd:0913 || good || Hardware works, official software not used, tablet was configured using udev rules which are more functional than official software anyway
|-
|Yubikey original || Yubico || 1050:0010 || good ||
|-
|}

----

= Bluetooth hardware =
{| class="wikitable sortable"
!Type || Make/Model || Hardware IDs || Result || Notes
|-
|Bluetooth Mouse || HP Z5000 || E5C13AA || good ||
|-
|Bluetooth Mouse || Logitech M557 || || good ||
|-
|Bluetooth Mouse || Kensington Expert Wireless Trackball || || good ||
|-
|Bluetooth Mouse || Logitech MX Vertical || || good || Battery level is not detected over bluetooth, detected when using the logitech receiver
|-
|Bluetooth Mouse || Logitech Triathlon M720 || || good ||
|-
|Bluetooth Mouse || Logitech Ultra-Thin Touch Mouse || || good || Detects battery level as "keyboard"
|-
|Bluetooth Mouse || Logitech MX Anywhere 2 || || good ||
|-
|Bluetooth Mouse || Logitech M535 || 910-004432 || good ||
|-
|Bluetooth Mouse || Microsoft Bluetooth Mouse || RJN-00002 || good ||
|-
|Bluetooth Mouse || Fenifox low profile || MX106-Black || good ||
|-
|Bluetooth Mouse || Technet || MGS479 || good ||
|-
|Bluetooth Keyboard || Logitech MX Keys || || good || Battery level is not detected over bluetooth, detected when using the logitech receiver
|-
|Bluetooth Speaker || Ivation Acoustix || || good || Use audio sink profile
|-
|Bluetooth Headphones || Sony WH-1000XM2 || || good* || Needs pulseaudio-module-bluetooth. *Recording untested.
|-
|Bluetooth Headphones || COWIN SE7 Noise Cancelling Headphones || || good || Pairs and plays audio with stock Debian OS. More detail [https://forum.pine64.org/showthread.php?tid=8192&pid=60682#pid60682 here].
|-
|USB Audio & Bluetooth Headset || Sony SBH90C || || good || Works well connected via USB Type-C and Bluetooth.
|-
|Bluetooth Headset || BlueAnt Ribbon || 7252A-RB || good || a2dp mode works, headset mode seems to work, out of box with manjaro
|-
|Bluetooth Headphones || DO-SV-BTIES03 || || good || Tested on Manjaro ARM - kde
|-
|Bluetooth Headset || TaoTronics TT-BH090 || || good || Microphone not tested but should work as expected of a normal Linux machine
|-
|Bluetooth Mouse || Logitech MX Ergo || || good || Works flawlessly both on Manjaro and Armbian.
|}

----

= Other hardware =

{| class="wikitable sortable"
!Type || Make/Model || Hardware IDs || Result || Notes
|-
|[https://www.aliexpress.com/item/32831647303.html USB charging cable] || - || - || good || Got the cable a while back so may not be identical to current product
|-
|Printer || HP DeskJet Ink Advantage 3775 || || good* || Using hplip-gui: via USB and WiFi. *Only print function tested.
|-
|}

[[Category:PineBook Pro]]

Pinebook Pro Troubleshooting Guide

2021-05-20T00:55:52Z

BenTheTechGuy: Add note that NVMe speed issue is fixed in 5.12

=Useful Links=

[[Pinebook_Pro|Back to the main Pinebook Pro page]]

[[Pinebook_Pro_Hardware_Accessory_Compatibility|Hardware Compatibility page]]

[[Pinebook Pro Software Release]]

=Tips, tricks and other information for troubleshooting your Pinebook Pro=

If something has gone wrong, the key thing is remain calm and not do anything hasty and make things worse, particularly when flashing the eMMC or firmware. Try and make a record of all the things you did in the run-up to the problem (even to the point of using a camera to take a note of errors on the screen, this record can be vital later).

=Manjaro Updates Fail With 404=
If you have an old Manjaro installation then it will have the wrong repositories/mirrors set up and they won't work. Set up new repositories by following these instructions:
https://forum.manjaro.org/t/another-mirror-transition-manual-intervention-required/132302

=Power And Boot=

== New from the factory - Pinebook Pro won't boot / power on ==
* Some Pinebook Pros came from the factory with the eMMC switch in the disabled position. It should be switched towards the back / hinge to enable the eMMC.
* The eMMC may have come loose during shipment. [[Pinebook Pro#Accessing the Internals - Disassembly and Reassembly|Open the back]] and verify that the eMMC is firmly seated.
* You may want to try unplugging the SD card daughterboard ribbon cable and see if it powers on (remove the battery and peel off a bit of the tape before unplugging it to avoid damage). If it does, try reseating it on both sides. It might have come loose during shipping.
* It's possible that your eMMC is empty from the factory. Simply [[NOOB|create]] a bootable [[Pinebook_Pro#Pinebook_Pro_images|SD card]] and see if your Pinebook Pro [[Pinebook_Pro#Boot_sequence_details|boots]]. If so, you can then [[NOOB|write]] an OS image to the eMMC.

== Pinebook Pro will not power on after toggling the eMMC enable/disable switch ==
* This may happen if you meant to toggle the UART/Headphone switch (9) towards touchpad for headphone use and instead you toggled the eMMC enable/disable switch (24).
* After reenabling eMMC by toggling switch (24) towards hinge, if Pinebook Pro does not turn on then press the RESET button (28). It is clearly marked 'reset' on the PCB board.

== Pinebook Pro will not power on after removing and replacing EMI shielding ==
* Closely inspect that the shielding is firmly seated in the clips on all sides. You can be seated in the clips on one axis, and have missed on an another axis.

== Pinebook Pro won't boot when using UART console cable ==
* If you're using the [[Pinebook_Pro#Using_the_UART|UART]] cable sold on the [https://pine64.com/product-category/pinebook-pro/ Pine Store], you may want to see if it boots after you disconnect it. Some users report that custom-made cables based on FTDI UART adapters do not cause this issue.
* Make sure your USB to serial UART device is 3.3v. Many are 5v and some even +-12v. Pinebook Pro's only support 3.3v and may act eratically when using higher voltage. Further, higher voltage could permananetly damage the Pinebook Pro's SoC.

== Pinebook Pro will not sleep with lid closed ==
A problem with the positioning of the lid magnet has been identified by several forum users in mid-2020 models of the Pinebook Pro. The magnetic field from the lid magnet operates a hall effect sensor located on the daughterboard (smallboard), which causes the Pinebook Pro to sleep when the lid is closed. If the magnet is not positioned correctly, the Pinebook Pro will not sleep when the lid is fully closed, but may sleep if the lid is open about an inch. If you experience this problem, repositioning of the magnet may be necessary.
=== Lid Magnet Repositioning Step-by-Step ===
*Read these steps thoroughly before starting. This is a somewhat laborious process involving fragile parts!
# Remove bottom cover.
# Disconnect LCD and webcam ribbon cable from main board. Flip the small black strip on the connector upward and the ribbon cable can be easily removed. Do not pull the cable out without first raising the black retaining mechanism.
# Remove the small black plastic standoffs on each hinge and set aside.
# Remove the three screws from each hinge on the display assembly.
# Move the hinges upward to a 90 degree angle independently from the main body. Then lift the main body to the same 90 degree angle and you should be able to separate the display assembly from the main body. Set the main body aside.
# Remove the plastic hinge cover on the display assembly. There's not really an easy way to do this, just work slowly and deliberately so as not to damage the sensitive cable inside. Start from either end and work your way inward. Use a small flathead screwdriver or similar tool to get started.
# Remove the hinges from the display assembly.
# Remove the rubber bumpers at the top corners of the display assembly to expose two screws. Remove the screws.
# Starting at the corners, separate the bezel from the lid. The clips that hold it in place are similar to those found on the hinge cover. Again, slow deliberate work will get it done. Work from the top down. Take care not to damage the cables in the bottom.
# With the bezel separated from the lid, feed the cable through the slot and set the bezel aside.
# Without removing the LCD panel completely, lift and move the panel slightly to the left, taking care not to damage the cable running underneath up to the webcam. This will give you room to remove the magnet without risking damage to the panel.
# The magnet is a silver colored bar near the bottom right side of the lid. Pry the magnet out with a small flathead or similar tool and set it aside. There is some adhesive but it's not very strong.
# Put the LCD panel back where it belongs. Note the foam pads on either side of the panel. The magnet is the same width as the foam pad that keeps the panel in place, and should fit perfectly in the same channel.
# The magnet should be placed about 1 to 1.5cm lower than where it was originally. There should be no need for adhesive, as the magnet will stick to the LCD panel. For reference, the hall effect sensor that the magnet interacts with is in between the USB port and audio jack.
# Reassemble using these steps in reverse order.

Your PineBook Pro should now sleep properly when the lid is closed.

=WiFi And Bluetooth=

== WiFi issues ==
* First, check the privacy switches to make sure your WiFi is enabled. They are persistant. See [[Pinebook_Pro#Privacy_Switches|Privacy Switches]]
* Next, you may have to modify the <code>/etc/NetworkManager/NetworkManager.conf</code> as root user, and replace <code>managed=false</code> with <code>managed=true</code>. Then reboot.
* For connections that drop and resume too often, it might be due to WiFi power management from earlier OS releases. Later OS releases either removed WiFi power management, or default to full power. (Power management can be turned off via command line with <code>iw dev wlan0 set power_save off</code> or <code>iwconfig wlan0 power off</code>, although it is not persistent through re-boot.)
* For connections that drop under load on the default Debian, remove <code>iwconfig wlan0 power off</code> in the file <code>/etc/rc.local</code>.
* If WiFi is un-usable or often crashes when using an alternate OS, then it might because its WiFi firmware is not appropriate for the WiFi chip in the Pinebook Pro. Try the latest firmware patch from [https://gitlab.manjaro.org/tsys/pinebook-firmware/tree/master/brcm https://gitlab.manjaro.org/tsys/pinebook-firmware/tree/master/brcm]
* After re-enabling WiFi via the privacy switch, you have to reboot to restore function. There is a work around for the default Debian, (and may work with others);
        <code>sudo tee /sys/bus/platform/drivers/dwmmc_rockchip/{un,}bind <<< 'fe310000.dwmmc'</code>
* On extremely rare occasions, the WiFi antenna connection is loose. To fix, simply open up the bottom, re-connect the WiFi antenna cable. This may show up as any of the following symptoms:
** Can't connect to any network, but the network manager software sees the WiFi device, (so it has not been disabled by the Privacy Switch)
** Very limited range, meaning you can make a connection if the Pinebook Pro is next to the WiFi router. But not the next room.
** Unreliable connections, that are also limited by range.

== Bluetooth issues ==

* When connecting a Bluetooth device, such as a Bluetooth mouse, it does not automatically re-connect on re-boot. In the Bluetooth connection GUI, there is a yellow star for re-connect on boot. Use that button to enable a persistent connection. It can be changed back later.
* Bluetooth-attached speakers or headset require the pulseaudio-module-bluetooth package. If not already installed, it can be installed with a package manager or using the following:
<pre>sudo apt-get install pulseaudio-module-bluetooth</pre>
* When using Bluetooth-attached speakers or headset and 2.4Ghz WiFi at the same time, you may experience stuttering of the audio. One solution is to use 5Ghz WiFi if you can. Or you may try using a different 2.4Ghz channel, perhaps channel 1 or the top channel, (11 in the USA, or 13/14 in some other countries).

= Sound issues =

* Many reports of no sound are due to the OS, incorrect settings, or other software problems (eg. PulseAudio). So first test to see if it is a software or hardware problem, by trying another OS via SD card. (For example, if Debian is installed on the eMMC, try Ubuntu on SD.)
* If you cannot get sound from the headphone jack, but can get sound from the speakers, then the headphone / UART console switch may be set to the UART mode. You can open the back and check the position of the switch. If set to UART mode, switch it to headphone mode. See the parts layout for the location and correct position of the switch.
* When using the USB C alternate DisplayPort mode, it is possible that the audio has been re-directed through this path. If your monitor has speakers, see if they work.
* See [https://gitlab.manjaro.org/manjaro-arm/packages/community/pinebookpro-post-install/blob/master/asound.state manjaro-arm/pinebookpro-post-install /var/lib/alsa/asound.state] for some ALSA tweaks.
* See [https://gitlab.manjaro.org/manjaro-arm/packages/community/pinebookpro-audio manjaro-arm/pinebookpro-audio] for how to handle 3.5mm jack plug/unplug events with ACPID.
* Serveral users have reported that one internal speaker had reversed polarity. Thus, sound from the speakers is like an echo effect.
** Their is a software fix using alsamixer and then enable either "R invert" or "L invert", however, now the headphones have incorrect audio.
** The permanent fix is to re-wire one speaker, though this requires soldering small wires.
* Sound playback may be affected by the "mirroring" between the right and left channels, which results in distorted sound image. The root cause is the [https://linux.die.net/man/1/alsamixer ALSA mixer] setting named "DAC Stereo Enhancement", which needs to be changed to 0% to fix this issue. Please see [https://forum.pine64.org/showthread.php?tid=12631&pid=87372#pid87372 this forum post] for further information.

= NVMe SSD issues =

Many PineBook Pro users have reported issues with NVMe SSD drives, including random Linux lockups and crashes. Some of these issues are related to the [https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=712fa1777207 RK3399's errata] that disables Gen2 (5 GT/s) speed for the PCI Express link used by the NVMe SSD, reducing it down to Gen1 speed (2.5 GT/s). However, as of December 17, 2020, Linux distributions that use mainline Linux kernel still configure the PCI Express link to run at Gen2 speed, which requires [https://forum.pine64.org/showthread.php?tid=11683 manual reconfiguration] to Gen1 speed in case system instability is experienced. See also this [https://patchwork.kernel.org/project/linux-rockchip/patch/20200423150510.6216-1-pgwipeout@gmail.com/ related discussion]. NOTE: This issue seems to have been [https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=642fb2795290 fixed] in mainline 5.12. It has been tested on Manjaro ARM and seems to work with no modifications.

Some PineBook Pro users have reported issues with the default settings for the APST (Autonomous Powe State Transition) power saving, which cause an NVMe drive to disappear from the system or lock up after a certain period of time. Please see [https://forum.pine64.org/showthread.php?tid=11337&pid=87711#pid87711 this forum thread] for further information.

= Keyboard and trackpad =

== Keys not registering / missing keys when typing ==
This issue occurs when your thumb or edge of the palm makes contact with left or right tip of the trackpad when you type. This is due to the palm rejection firmware being too forceful. Instead of only disabling the trackpad, so your cursor does not move all over the screen, it disables both the trackpad and the keyboard.

Using Fn+F7 to disable the touchpad will keep it from also disabling the keyboard.

A [[Pinebook_Pro#Trackpad|firmware update]] has been released to address this.

== Key mapping ==
* See this [https://gitlab.manjaro.org/manjaro-arm/packages/community/pinebookpro-post-install/blob/master/10-usb-kbd.hwdb /etc/udev/hwdb.d/10-usb-kbd.hwdb] for some key mapping tweaks

== Pinebook Pro gets stuck after first reboot in Trackpad Firmware Update ==
This refers to the firmware update shown here:
https://github.com/ayufan-rock64/pinebook-pro-keyboard-updater#update-all-firmwares
* If the system is not responding after the 1st reboot, it might be easiest to do a system restore or boot an sdcard-only OS, and follow up by running the second step of the trackpad firmware update with a USB keyboard and mouse plugged in
* System restore https://forum.pine64.org/showthread.php?tid=8229
* Firmware update https://github.com/ayufan-rock64/pinebook-pro-keyboard-updater#update-all-firmwares

== ANSI Fn + F keys wrong for F9, F10, F11 and F12 ==

There appears to be a minor firmware issue for ANSI keyboard models of the Pinebook Pro. Some discussion and fixes have been proposed;
* Discussion thread [https://forum.pine64.org/showthread.php?tid=8744&pid=57678#pid57678 Fn + F keys screwy for F9, F10, F11 and F12]
* Proposed fix [https://github.com/ayufan-rock64/pinebook-pro-keyboard-updater/issues/14#issuecomment-576825396 (ANSI) Fn + F(9-12) has wrong assignment after firmware update #14]

= USB docks & USB C alternate mode video =

The Pinebook Pro uses the RK3399 SoC (System on a Chip). It supports a video pass through mode on the USB C port using DisplayPort alternate mode. This DisplayPort output comes from the same GPU used to display the built-in LCD.

Here are some selection criteria for successfully using the USB C alternate mode for video:
* The device must use USB C alternate mode DisplayPort. Not USB C alternate mode HDMI, or other.
* The device can have a HDMI, DVI, or VGA connector, if it uses an active translater.
* If USB 3 is also desired from a USB dock, the maximum resolution, frame rate and pixel depth is reduced to half the bandwidth. For example, 4K @ 30hz instead of 60hz.
* USB docks that also use USB C alternate mode DisplayPort will always have USB 2 available, (480Mbps, half-duplex).

=Screen=

Also see above about external screen using USB-C adaptor

== After changing builtin LCD resolution, blank screen ==
Some people find that the text or icons are too small, so they attempt to change the resolution of the built-in display. Afterwards, the display is blank.
Use the following to fix when logged into a text console as yourself, pressing Control-Alt-F1 through F6. After listing the resolutions, select the native resolution, (1920x1080 aka 1080p).

<pre>export DISPLAY=:0.0
xrandr -q
xrandr -s [resolution]</pre>

Once the screen resolution is restored, try using the software settings to configure the desired screen scaling.

If the above fix did not work, you can try this:
* Using a text console, (Control-Alt-F1), login with your normal user ID
* Edit the file <code>nano ~/.config/monitors.xml</code>
* Change the "width" value to "1920"
* Change the "height" value to "1080"
* If there is more than one monitor configuration listed, edit that one too. Be careful to make no other changes. If needed, exit without saving and re-edit.
* Save the file and exit.
* Login using the GUI and test
* If you are still loggied in via the GUI, you will have to reboot using <code>sudo shutdown -r now</code>. After the reboot, you should be able to login to the GUI login and have the resolution back to normal.

After restoring the usability of your Pinebook Pro's graphical screen, also see [[Pinebook Pro#Improving readability|this section]] on improving readability and usability.

=Outer Shell=

== Cracks in the plastic ==
There have been multiple reports of cracks in the plastic keyboard and trackpad part of the case. These are generally near:
* Hinges
* USB ports
* Top side, around the corners

This seems to apply to the first batches in 2019. Later versions of the keyboard and trackpad have used better plastic. With replacements now in the Pine64 Store, it's possible to simply order a replacement.

There have been a few reports of cracks in the plastic around the LCD display, but these appear to be less common. There are replacement LCDs with top cases available in the Pine64 Store.

[[Category:PineBook Pro]]