PINE64 - User contributions [en]

Overclocking

2023-11-29T08:37:49Z

TuxThePenguin: Add new RK3399 GPU overclocking info

{{warning|1= There is the possibility of damaging your equipment by overclocking. Do so at your own risk!}}
{{hint|This page is incomplete, you're welcome to improve it.}}
{{hint|All information regarding clock speeds, voltages and more are stored in the DTB (Device Tree Blob). You can learn more about it [https://elinux.org/Device_Tree_Reference here].}}

Overclocking is a way to get more performance out of the system by running it at higher clock speeds than the factory default, usually while putting out more heat and using more power (You can also downclock to possibly reduce power consumption and thermals at the cost of performance). It is highly recommended that you avoid overvolting the device, as that has a high risk of damaging the hardware, hence the warning at the beginning of this page. However, just some slight overclocks without the added voltage can not only improve performance, but not carry as much risk (Still: Do at your own risk!). It should be noted however that overclocking can cause instability, so you will need to test and see what values work best with your device (There is a silicon lottery for the Pinephone's hardware).

== A64-based devices ==

{{note|These instructions are targeting the PinePhone to simplify the explanation, however they can be used to also overclock other devices such as the Pinetab if you modify the proper DTB files.}}

=== Editing the PinePhone DTS ===

In order to overclock the PinePhone you will have to first convert the DTB file in <code>/boot/dtbs/allwinner/</code> to a DTS file. You will see <code>sun50i-a64-pinephone-1.2.dtb</code>, and also two other files with different PinePhone mainboard revisions (1.1 and 1.0). You will want to select the correct file for your PinePhone (Only choose 1.1 if you have a Braveheart, As all other consumer PinePhones use the 1.2 DTS).

Once you've found the file, you can run the following command to convert the DTB to DTS:

dtc -I dtb -O dts /boot/dtbs/allwinner/sun50i-a64-pinephone-1.2.dtb -o /boot/dtbs/allwinner/sun50i-a64-pinephone-1.2.dts

Finally, modify the newly converted .dts file and change the clockspeeds you wish to modify. You can simply use a text editor to do so.

To convert back to DTB:

dtc -I dts -O dtb /boot/dtbs/allwinner/sun50i-a64-pinephone-1.2.dts -o /boot/dtbs/allwinner/sun50i-a64-pinephone-1.2.dtb

Afterwards you can simply reboot and check with <code>sudo cat /sys/kernel/debug/clk/clk_summary</code> to see if the changes have correctly applied.

{{note|In the future it is possible that someone may make a driver to adjust clockspeeds of the A64 from userspace (using a config file) without the need to recompile. However, currently the only way to overclock is to either compile your own kernel, or modify just the DTB (instructions above).}}

=== GPU ===

Open <code>/boot/dtbs/allwinner/sun50i-a64-pinephone-1.2.dts</code> (You will have to find the source of the kernel used by your distribution. There is the Pine64 kernel, and Megi's) in a text editor following these instructions: https://wiki.pine64.org/wiki/Overclocking#Edit_Pinephone_DTS

Look for <code>mali: gpu@1c4000 {</code> and within that block search for <code>assigned-clock-rates = <432000000>;</code>

The <code>assigned-clock-rates</code> line should be set to <code>432000000</code>, this means that the GPU is clocked at 432MHz by default. So if you want 500MHz, set the value to <code>500000000</code>.

Save the DTS file, and recompile the DTB. In order to check if the overclock was successfully applied you can run: <code>sudo cat /sys/kernel/debug/clk/clk_summary</code>.

{{note|The file may be slightly different and you may need to enter the values as hexadecimals}}
{{hint|The GPU appears to run stable overclocked to 540 Mhz, however more testing with a wider group of devices is needed.}}
{{hint|Remember to run a benchmark tool (such as glmark2-es2) to help check stability.}}

=== CPU ===

The stock speed of the A64 is 1.152 GHz. The A64 can be overclocked significantly, it is highly advisable not to do this unless you can also drop the voltage at the same time.

If the CPU is undervolted and overclocked at the same time, it is possible to reach similar thermals and power consumption to the stock configuration but with better performance.

{| class=wikitable
|+ Power consumption at different voltages and frequencies
! Configuration
! Frequency
! Voltage
! Power (Screen 50%)
|-
! Stock
| 1.152GHz || 1.30v || ~4.35w
|-
! Stock + Undervolt
| 1.152GHz || 1.18v || ~3.65w
|-
! Overclock + Undervolt
| 1.344Ghz || 1.28v || ~4.60w
|}
The table above contains measurements created in postmarketOS (SWMO/SXMO - postmarketOS 21.12 SP1) with the screen on (set to 50% brightness) under a threaded load.

{| class=wikitable
|+ AXP803 PMIC voltage steps on DCDC2.
! Voltage range
! Step size
|-
! 0.50V-1.20V
| 10mV
|-
! 1.22V-1.30V
| 20mV
|-
|}
The table above shows the valid voltages provided by the AXP803 PMIC on DCDC2 (used to power the cores). For example, setting the voltage to 0.60V is valid, but setting it to 1.23V is not. When overclocking, ensure that you only use valid voltages at each operation point (otherwise it will simply be dropped and ignored). You can use (after installing) cpupower to display all valid frequencies after boot.

{{note|The user ''somefoo'' was able to undervolt the PinePhone at each frequency operation point by at least -100mv. The A64 set to 1.152Ghz runs at 1.18v instead of the standard 1.3v, dropping the power usage by ~0.7w under full single threaded load! The silicon lottery will dictate how well you can undervolt.}}
{{hint|The exact voltages and frequencies that you can achieve will depend on your device. Make sure to run stress tests (such as ''stress-ng'') to ensure stability.}}

=== DRAM ===

{{warning|1=It is not recommended to exceed 667 MHz clockspeed on the DRAM. 648MHz is likely the upper limit.}}
{{hint|Make sure to set your DRAM to a multiple of 24.}}
{{hint|The current frequency your DRAM is running at can be found using this command: <code>cat /proc/device-tree/memory/ram_freq</code>}}

When overclocking the GPU, it is a good idea to also overclock the DRAM, as the main bottleneck of the A64 SOC is the memory. The A64's maximum ram clockspeed falls just short of 667MHz. This may be unstable on your device however.

Around 600 MHz (PC-1200) should work fine, however some people have reported instability at lower clockspeeds. Arch Linux Arm uses a default clockspeed of 552MHz, with U-Boot builds available to easily switch out for a higher (624) or lower (492) DRAM clockspeed.

It is possible that by reverse engineering the DRAM driver from Allwinner that auto tuning can be accomplished to get the best performance.

Setting the DRAM clock is accomplished by modifying pinephone_defconfig in U-Boot (https://gitlab.com/pine64-org/u-boot/-/blob/crust/configs/pinephone_defconfig)

You can find simple instructions on doing so here: [[U-Boot]]

=== VPU ===

In order to allocate more VRAM for the GPU you can add <code>cma=256</code> to your kernel (or use kconfig with CONFIG_CMA_SIZE_MBYTES=256) cmdline in boot.scr which you will have to compile using mkimage. By default the kernel allocates only 64MB, and the maximum value is 256MB.

In order to compile boot.scr you can run <code>mkimage -C none -A arm64 -T script -d boot.cmd boot.scr</code>

{{note|You may not have a boot.cmd file in your boot directory and instead you may instead have a boot.txt}}

=== Cedrus ===

Overclocking cedrus is achieved by modifying the kernel source code: https://elixir.bootlin.com/linux/latest/source/drivers/staging/media/sunxi/cedrus/cedrus.c#L507

{{note|User ''33yn2'' is not particularly sure if this makes any difference, or if it might in fact have a negative impact. Probably not worth messing with.}}

== RK3399-based devices ==
The RK3399 clocks are found in [https://github.com/torvalds/linux/blob/master/arch/arm64/boot/dts/rockchip/rk3399-opp.dtsi arch/arm64/boot/dts/rockchip/rk3399-opp.dtsi]

More optimised voltages and clocks can be found in [https://github.com/torvalds/linux/blob/master/arch/arm64/boot/dts/rockchip/rk3399-op1-opp.dtsi arch/arm64/boot/dts/rockchip/rk3399-op1-opp.dtsi]
These include a slight overclock and undervolt, they are intended for the OP1 CPU found in many Chromebooks but have worked fine in all recorded cases on regular RK3399 SoCs in other devices.

===GPU===
Available clock speeds for the GPU can be found and modified in <code>gpu_opp_table</code>.

The highest recommended voltage for the GPU is 1.2V as specified in the RK3399 schematic from Rockchip.

The GPU does not have its own PLL like the CPU clusters and memory so adding new clock speed options depends on the speed of other PLLs in the system, however depending on the device these often can't be changed without breaking some functionality.

Without changing the PLLs the next step up from 800MHz is 1GHz, which is not known to be stable on any units.

In general overclocking the GPU in the RK3399 seems to be a bad idea, it usually ends up reducing performance or crashing the system entirely, possibly due to some kind of silent errors. Generally even with higher voltages there are no meaningful performance gains past 800MHz.

===CPU===
A set of available clock speeds that can be added to the CPU clusters can be found in <code>drivers/clk/rockchip/clk-rk3399.c</code> under <code>rk3399_cpuclkl_rates</code> for the little cores and <code>rk3399_cpuclkb_rates</code> for the big cores.

These clock speeds can be added to <code>cluster0_opp</code> for the small cores and <code>cluster1_opp</code> for the big cores respectively.

The maximum limit is 1.8GHz on the little cores and 2.2GHz on the big cores.

The highest recommended voltage for the little cores is 1.2V and for the big cores is 1.25V.

Segfault has found that the RK3399 in his Pinebook Pro can reach 1.7GHz on the little cores and 2.08GHz on the big ones.

The stock speed for the little cores is 1.4GHz and on the big cores it is 1.8GHz, the OP1 speeds default to 1.5GHz and 2.0GHz instead.

== ROCK64 ==

DTB is in <code>/boot/dtbs/rockchip/rk3328-rock64.dtb</code>. CPU clock rates are inside <code>opp_table0</code> as hexadecimal numbers in the <code>opp-hz</code> field.

Check the achieved clock speed with <code>sudo cat /sys/kernel/debug/clk/clk_summary | grep armclk</code>.

Thanks to [https://github.com/ayufan-rock64 Ayufan]'s work (with their [https://github.com/ayufan-rock64/linux-build/blob/master/recipes/overclocking.md overclocking recipe]), we know we can add a 1.392GHz operating point, and a 1.512GHz operating point (you should ensure you have a large heatsink for this last one). You can do so by adding the following in the <code>opp_table0</code> object, after the <code>opp-1296000000</code> operating point:

opp-1392000000 {
opp-hz = <0x00 0x52f83c00>;
opp-microvolt = <0x149970>;
clock-latency-ns = <0x9c40>;
};

opp-1512000000 {
opp-hz = <0x00 0x5a1f4a00>;
opp-microvolt = <0x162010>;
clock-latency-ns = <0x9c40>;
};

GPU needs investigating, but current mainline device tree does not try to clock up the GPU at all.

[[Category:SOPINE]] [[Category:PINE A64]] [[Category:PINE H64]] [[Category:PINE A64-LTS]] [[Category:Pinebook]] [[Category:PinePhone]] [[Category:PineTab]] [[Category:ROCK64]] [[Category:Pinebook Pro]] [[Category:ROCKPro64]] [[Category:Allwinner A64]] [[Category:Allwinner H6]] [[Category:Rockchip RK3399]]

Quartz64 Development

2023-05-26T14:15:25Z

TuxThePenguin: Update wifi status

This page documents the current status of software support for the [[Quartz64]] single-board computer, and provides links to resources to help prospective contributors get started. Information is kept current on a best-effort basis as various patches get accepted into the kernel.

== Overview ==

=== Upstreaming Status ===

{| class="wikitable plainrowheaders" border="1"
! scope="col" | Function
! scope="col" colspan="2" | Status
! scope="col" | Component
! scope="col" | Notes
! scope="col" | Applies To
|-
! scope="row" rowspan="3" | Video Output
| colspan="2" style="background:PaleGreen; text-align:center;"|Linux Mainline
| <code>rockchipdrm/VOP2</code>
|
As of 5.19-rc1[https://git.kernel.org/linus/604be85547ce4d61b89292d2f9a78c721b778c16], Also featured in Phoronix Article[https://www.phoronix.com/scan.php?page=news_item&px=Rockchip-VOP2-Linux-5.19]
|-
| colspan="2" style="background:#F99; text-align:center;"|Needs porting
| <code>rockchip-edpphy-naneng</code>
| Downstream: [https://gitlab.com/pine64-org/quartz-bsp/rockchip-linux/-/blob/quartz64/drivers/phy/rockchip/phy-rockchip-naneng-edp.c] and [https://gitlab.com/pine64-org/quartz-bsp/rockchip-linux/-/commit/d7ad116fb30d11d110aeb880754cf27f34c45c40#7e8e2ef87e479c54539dc519c0b92d6b31727f8d_671_681] Coordinate any porting with Rockchip first
|
|-
| colspan="2" style="background:PaleGreen; text-align:center;"|Linux Mainline
| <code>dw-mipi-dsi-rockchip</code>
| As of 6.1[https://git.kernel.org/linus/e18d9b093006d8abd53e1ce13c0d5a8d0fcd5f64]
|
|-
! scope="row" | 3D Acceleration
| style="background:PaleGreen; text-align:center;"|Linux Mainline
| style="background:PaleGreen; text-align:center;"|Upstream Mesa
| <code>panfrost</code>
| As of 5.18[https://git.kernel.org/linus/810028668c6d9da25664195d6b906c98a8169f72]
|-
! scope="row" rowspan="3" | Video Decode
| style="background:PaleGreen; text-align:center;"|Linux Mainline
| style="background:LightYellow; text-align:center;" rowspan="3"|GStreamer only, no ffmpeg[https://patchwork.ffmpeg.org/project/ffmpeg/list/?series=2898]
| <code>hantro</code> using <code>v4l2-requests</code>
| VDPU121 handling 1080p H.263, MPEG-1, MPEG-2, VP8 and H.264. Mainline as of 5.19[https://git.kernel.org/linus/5f6bfab6da6531238e899fdf29efd6d0185adc3e]
|
|-
| style="background:#F99; text-align:center;"|Needs writing
| <code>rkvdec2</code> using <code>v4l2-requests</code>
| VDPU346 handling 4K H.265, H.264 and VP9
|
|-
| style="background:#F99; text-align:center;"|Needs writing
| <code>rkdjpeg</code> using <code>v4l2-requests</code>
| VDPU720 handling JPEG, [[User:CounterPillow]] is working on this
|-
! scope="row" rowspan="5" | [[Mainline Hardware Encoding|Video Encode]]
| style="background:PaleGreen; text-align:center;"|Linux Mainline
| style="text-align:center; background:LightYellow;"|GStreamer only
| JPEG on VEPU121
| Hantro-based. Mainline as of 6.1[https://git.kernel.org/linus/6f1ae821a6c4aa9d5b8f437b27ec86fb569219fd]
|
|-
| style="background:#F99; text-align:center;"|Needs writing
| style="text-align:center;"|?
| H.264 on VEPU121
| Hantro-based
|
|-
| style="background:#F99; text-align:center;"|Needs writing
| style="text-align:center;"|?
| VP8 on VEPU121
| Hantro-based
|
|-
| style="background:#F99; text-align:center;"|Needs writing
| style="text-align:center;"|?
| H.264 on VEPU540
| rkvenc-based
|
|-
| style="background:#F99; text-align:center;"|Needs writing
| style="text-align:center;"|?
| H.265 on VEPU540
| rkvenc-based
|
|-
! scope="row" rowspan="3" | Audio
| colspan="2" style="background:PaleGreen; text-align:center;"|Linux Mainline
| <code>rockchip-i2s-tdm</code>
| As of 5.16[https://git.kernel.org/linus/43b058698f723e3c2087af7069c0da082a3ecbe1]
|-
| colspan="2" style="background:PaleGreen; text-align:center;"|Linux Mainline
| <code>rockchip-spdif</code>
| As of 5.15[https://git.kernel.org/linus/dac825b6a6bdca41347e25f07354ad94fdc97445]
|-
| colspan="2" style="background:PaleGreen; text-align:center;"|Linux Mainline
| <code>rk817-codec</code>
| As of 5.14[https://git.kernel.org/linus/0d6a04da9b25b9a7cf2cac5f5079e3296d3bee0f].
| Quartz64 Model A/B
|-
! scope="row" rowspan="3" | Bootloader
| colspan="2" style="background:LightYellow; text-align:center;"|In review[https://review.trustedfirmware.org/c/TF-A/trusted-firmware-a/+/16952]
| <code>TF-A</code>
|
|-
| colspan="2" style="background:LightYellow; text-align:center;"|In progress
| <code>U-Boot</code>
| [[Quartz64_Development#Mainline_U-Boot_Work|See below]]
|
|-
| colspan="2" style="background:LightYellow; text-align:center;"|In progress[https://github.com/jaredmcneill/quartz64_uefi]
| <code>Tianocore EDK II</code>
|
|-
! scope="row" rowspan="4" | Device Tree
| colspan="2" style="background:PaleGreen; text-align:center;"|Linux Mainline
| Quartz64 Model A
| As of 5.16[https://git.kernel.org/linus/b33a22a1e7c4248608e533fc4fa524258b3fae84]
| Quartz64 Model A
|-
| colspan="2" style="background:PaleGreen; text-align:center;"|Linux Mainline
| Quartz64 Model B
| As of 5.19[https://git.kernel.org/linus/c37415f55bdadffe5b4c0e7981e9fc7e8b96beea]
| Quartz64 Model B
|-
| colspan="2" style="background:PaleGreen; text-align:center;"|Linux Mainline
| SOQuartz
| As of 5.19[https://git.kernel.org/linus/c466828fb3ba8cb7f5c3bf28766da9b70bf9745e]
| SOQuartz
|-
| colspan="2" style="background:PaleGreen; text-align:center;"|Linux Mainline
| PineNote
| As of 5.18[https://git.kernel.org/linus/d449121e5e8addcee654250cec298c887ecafb32]
| PineNote
|-
! scope="row" rowspan="2"| Gigabit Ethernet
| colspan="2" style="background:PaleGreen; text-align:center;"|Linux Mainline
| <code>rk3566-gmac</code>
| As of 5.14[https://git.kernel.org/linus/3bb3d6b1c1957e88bfc5e77a4557f7e6ba761fe3]
|-
| colspan="2" style="background:PaleGreen; text-align:center;"|Linux Mainline
| <code>yt8511-phy</code>
| As of 5.14[https://git.kernel.org/linus/48e8c6f1612b3d2dccaea2285231def830cc5b8e]
|-
! scope="row" | IOMMU
| colspan="2" style="background:PaleGreen; text-align:center;"|Linux Mainline
| <code>rockchip-iommu</code>
| As of 5.14[https://git.kernel.org/linus/c55356c534aa651ccc3053ef2d5d8d810adacf5f]
|-
! scope="row" | GPIO
| colspan="2" style="background:PaleGreen; text-align:center;"|Linux Mainline
| <code>gpio-rockchip</code>
| As of 5.15[https://git.kernel.org/linus/936ee2675eee1faca0dcdfa79165c7990422e0fc]
|-
! scope="row" | pinctrl
| colspan="2" style="background:PaleGreen; text-align:center;"|Linux Mainline
|
|
|-
! scope="row" | Thermal Regulation
| colspan="2" style="background:PaleGreen; text-align:center;"|Linux Mainline
| <code>rockchip-thermal</code>
| As of 5.14[https://git.kernel.org/linus/4b14c055a6f644cbeb1156ba24647e92fe51ec69]
|-
! scope="row" | PCIe
| colspan="2" style="background:PaleGreen; text-align:center;"|Linux Mainline
| <code>pcie-dw-rockchip</code>
| As of 5.15[https://git.kernel.org/linus/0e898eb8df4e34c7b129452444eb7cef68a11f43]
|-
! scope="row" | Power Management
| colspan="2" style="background:PaleGreen; text-align:center;"|Linux Mainline
| <code>rockchip-pm-domains</code>
| As of 5.14[https://git.kernel.org/linus/1782c87b44a0b1a527f01a6a184677c58ccbf9c7]
|-
! scope="row" | Voltage Control
| colspan="2" style="background:PaleGreen; text-align:center;"|Linux Mainline
| <code>rk3568-pmu-io-voltage-domain</code>
| As of 5.15[https://git.kernel.org/linus/28b05a64e47cbceebb8a5f3f643033148d5c06c3]
|-
! scope="row" | SPI
| colspan="2" style="background:PaleGreen; text-align:center;"|Linux Mainline
| <code>spi-rockchip</code>
| As of 5.14[https://git.kernel.org/linus/d74d99229f4d48f42d674f7a8a1137179efd67ac]. Necessary device tree changes [https://patchwork.kernel.org/project/linux-rockchip/list/?series=586691 in review].
|-
! scope="row" | Battery
| colspan="2" style="background:PaleGreen; text-align:center;"|Linux Mainline
| <code>rk817-charger</code>
| As of 6.1[https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/power/supply/rk817_charger.c?id=11cb8da0189b417392e2334ae967b0ba1f0d1be8]
| Quartz64 Model A, Pinenote
|-
! scope="row" | Microphone
| colspan="2" style="background:PaleGreen; text-align:center;"|Linux Mainline
| <code>rockchip-saradc</code>
| As of 5.15[https://git.kernel.org/linus/7786da3b5ae167c17f35e22ba35e06006338c2f6]. Headphone jack mic seems to connect to <code>SARADC_VIN2_HP_HOOK</code>, so I'm pretty sure that the dtsi and driver changes are needed for that mic to work
|-
! scope="row" | USB 2.0
| colspan="2" style="background:PaleGreen; text-align:center;"|Linux Mainline
| <code>rockchip-usb2phy</code>
| As of 5.17[https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/phy/rockchip?h=v5.17-rc1&id=42b559727a45d79c811f493515eb9b7e56016421]
|-
! scope="row" | e-Ink
| colspan="2" style="background:LightYellow; text-align:center;"|In review (RFC)[https://lore.kernel.org/linux-rockchip/20220413221916.50995-1-samuel@sholland.org/T/]
| <code>rockchip-ebc</code>
| A DRM driver is available [https://github.com/smaeul/linux/commits/rk35/ebc-drm-v5 here]; also see [[RK3566 EBC Reverse-Engineering]]
|-
! scope="row" | Combo PHY
| colspan="2" style="background:PaleGreen; text-align:center;"|Linux Mainline
| <code>naneng-combphy</code>
| As of 5.18[https://git.kernel.org/linus/7160820d742a16313f7802e33c2956c19548e488]. Still requires DTS changes
|-
! scope="row" | RGA
| colspan="2" style="background:#F99; text-align:center;"|Needs fixing
| <code>rockchip-rga</code>
| [[User:CounterPillow]] experimentally enabled it[https://gist.github.com/CounterPillow/6bea809f15ada7ddd3a3d7a4994fdc4e] in the device tree and ran gstreamer's v4l2convert through it to test, resulting in a completely garbled output.
|-
! scope="row" | Fan Controller
| colspan="2" style="background:#F99; text-align:center;"|Needs writing
| <code>gp7101</code>
| Someone should write a pwm driver for it so we can then use pwm-fan
| SOQuartz Blade
|-
! scope="row" rowspan="2" | CSI Camera
| colspan="2" style="background:#F99; text-align:center;"|Needs porting
| <code>rkisp</code>
| Downstream: [https://gitlab.com/pine64-org/quartz-bsp/rockchip-linux/-/tree/quartz64/drivers/media/platform/rockchip/isp]
|
|-
| colspan="2" style="background:PaleGreen; text-align:center;"|Linux Mainline
| <code>rockchip-inno-csidphy</code>
| As of 6.1[https://git.kernel.org/linus/29c99fb085ad53e6d5504d1f8d32e6673b9b3a2c]
|
|-
! scope="row" | NPU
| colspan="2" style="background:#F99; text-align:center;"|Needs writing
|
| Downstream version is a closed source SDK. Major undertaking to reimplement this as Linux does not (yet) appear to have a generic architecture for neural accelerators.
|
|-
! scope="row" | Crypto
| colspan="2" style="background:#F99; text-align:center;"|Needs porting
| <code>rk-crypto</code> v2
| Downstream driver [https://gitlab.com/pine64-org/quartz-bsp/rockchip-linux/-/tree/quartz64/drivers/crypto/rockchip] doesn't include a rk3568 compatible either, but the TRM shows that it seemingly matches.
|
|-
! scope="row" | TRNG
| colspan="2" style="background:LightYellow; text-align:center;"|In review[https://patchwork.kernel.org/project/linux-rockchip/list/?series=699813]
| <code>rockchip-rng</code>
|
|
|-
! scope="row" rowspan="2" | Wi-Fi
| colspan="2" style="background:#F99; text-align:center;"|Needs porting
| <code>bes2600</code>
| A downstream driver is available but it makes use of some custom Rockchip interfaces and is designed for older kernels, plans are being made to port it to DKMS.
| PineTab 2
|-
| colspan="2" style="background:PaleGreen; text-align:center;"|Linux Mainline
| <code>brcmfmac</code>
|
| Quartz64 Model B
|}

== Current Status ==

The following sections give an overview over the current status of different parts of the board. Some parts are waiting on a driver to be written or ported, others only need various adjustments.

According to pgwipeout, I/O device performance is within expected ranges now.

=== Working ===

* eMMC
* SDMMC0 (SD cards)
* GMAC (Gigabit Ethernet)
* USB 2.0
* SATA 2
* SATA 3
* UART
** UART 0 (Pi-bus)
** UART 1 (Bluetooth)
** UART 2 (Pi-bus, debug)
* Video Decode
** VP8
** H.264
* Video Encode
** JPEG (it's pretty bad)
* Battery
* GPU
* Audio
** Analog audio works
** SPDIF works
** HDMI works
* SPI — works, user needs to modify device tree to add devices
* I2C — works, user needs to modify device tree to add devices

=== Partially Working ===

* PCI-Express Controller — everything but devices that need cache coherency (e.g. dGPUs) should work
** [[User:CounterPillow]] noticed some weirdness with NVMe devices disconnecting during heavy write operations, likely down due to power draw on one of the rails as the same sustained bandwidth could be achieved with a different PCIe device with no issue.
* SDMMC1 (Wi-Fi) — AP6256 working, BL602 needs some work to make it flash firmware
* [https://developer.arm.com/architectures/system-architectures/system-components/arm-generic-interrupt-controller GIC] — needs errata published by Rockchip to get upstream to add device-specific workarounds[https://lore.kernel.org/linux-rockchip/CAMdYzYrQ5f-mv_VmTq_CRf9tR=j3mwRpKHNLmPFgCF9whsGFRw@mail.gmail.com/]
* Video Output — only at 1920x1080p60 and nothing else, very buggy and rough around more than just the edges

=== Confirmed Broken ===

* USB 3.0 (applies to Model A only) — only works with very short cables and depends on the device. This is due to a hardware design issue relating to the coupling capacitors needed for SATA, which shares the same lines as USB 3.0.
** Hardware design changes have been suggested to engineers, it's in their hands now.
* RGA — only works with memory ≤ 4 GiB, because Rockchip didn't make the address registers larger. Oopsie.

=== Needs Testing ===

* E-Paper
* Microphone Input
* CSI — needs CIF driver
* eDP — needs PHY driver and controller driver
* DSI

== TODO ==

=== ebc-dev Reverse Engineering and Development ===

The [https://gitlab.com/pine64-org/quartz-bsp/linux-next/-/tree/rk356x-ebc-dev driver for the eInk panel] needs to both be reverse engineered and then rewritten as C. In its current form, it is mostly an assembly dump produced by gcc with debug symbols. See [[RK3566 EBC Reverse-Engineering]] for details.

=== Investigate MCU ===

The RK3566 comes with an integrated RISC-V microcontroller (MCU). It communicates with the A55 host through the Mailbox system driven by the rockchip-mailbox driver. Since this MCU would be quite useful for things such as low power standby mode, investigating how it can be turned on and have firmware flashed to it should greatly enhance the power saving features of the PineNote.

=== Mainline U-Boot Work ===

Currently, mainline U-Boot does not have support for the RK3566 SoC used on the Quartz64. That's why we currently use the "downstream" Rockchip U-Boot, which is based on an old version of U-Boot and contains vendor specific patches that have not undergone the same level of code review as they'd have done had they been submitted upstream.

While the lack of ATF sources means that using mainline U-Boot would still require the use of Rockchip provided binaries for the firmware, the mainline U-Boot works needs to be done eventually anyway, and even with Rockchip blobs, a more modern version of U-Boot will be much nicer to use.

Someone needs to get on the task of investigating what minimally needs to be ported to get the board booting with mainline U-Boot, port those changes, and submit them for review.

==== Things that need to be done ====

This list is non-exhaustive as we don't exactly know how much is missing

* Bring the kernel's Quartz64 DTSes into the tree (CounterPillow did this [https://github.com/CounterPillow/u-boot-quartz64/commits/mainline-ish-2 in his tree])
* Write <code>defconfig</code>s based on <code>evb-rk3568_defconfig</code> (CounterPillow did this [https://github.com/CounterPillow/u-boot-quartz64/commits/mainline-ish-2 in his tree])
* Write a mainline-able patch for the [https://github.com/CounterPillow/u-boot-quartz64/commit/ba33172a36f298641f51a5e6b855c3e89e3f5d3e DWMCI_PWREN hack]

Stretch Goals:

* Port the Naneng Combo PHY driver to u-boot so we can SATA, USB 3 and PCIe boot
* Look into SPI
* Port the Motorcomm PHY driver to u-boot for networking?
** Only needed for Model A, RTL8211 on Model B is already supported in mainline u-boot
* Port a basic VOP2 driver to get a framebuffer from u-boot

==== List of Useful Resources for this Task ====
* Downstream Rockchip U-Boot repository with Quartz64 specific patches: https://gitlab.com/pgwipeout/u-boot-rockchip/-/tree/quartz64
* Mainline Rockchip custodian U-Boot repository: https://source.denx.de/u-boot/custodians/u-boot-rockchip
* U-Boot Mailing List: https://lists.denx.de/listinfo/u-boot

=== eDP Driver Porting ===

The eDP PHY driver and controller driver needs to be ported, brought into shape and submitted with proper commit attribution to the Rockchip authors.

[[User:CounterPillow]] has experimentally ported stuff, but it's currently not working.

== Linux Kernel Config Options ==

* <code>CONFIG_SND_SOC_ROCKCHIP_I2S_TDM</code>
** for Analog and HDMI audio
* <code>CONFIG_SND_SOC_RK817</code>
** for Analog audio on the Model A
* <code>CONFIG_STMMAC_ETH</code>
** Ethernet
* <code>CONFIG_DWMAC_ROCKCHIP</code>
** Ethernet
* <code>CONFIG_MOTORCOMM_PHY</code>
** Ethernet PHY for Model A, set this one to Y, m won't work out of the box if the generic PHY driver is y and binds first. Alternatively tell users in board-specific setup instructions to force including the <code>motorcomm</code> module in initramfs if you set it to m.
* <code>CONFIG_REALTEK_PHY</code>
** Ethernet PHY for Model B
* <code>CONFIG_MMC_DW</code>
** MMC/SD
* <code>CONFIG_MMC_DW_ROCKCHIP</code>
** MMC/SD
* <code>CONFIG_MMC_SDHCI_OF_DWCMSHC</code>
** MMC/SD
* <code>CONFIG_PCIE_ROCKCHIP_DW_HOST</code>
** PCIe
* <code>CONFIG_PHY_ROCKCHIP_NANENG_COMBO_PHY</code>
** PHY for PCIe/SATA/USB3
* <code>CONFIG_DRM_PANFROST</code>
** GPU
* <code>CONFIG_SND_SOC_ROCKCHIP_SPDIF</code>
** SPDIF audio
* <code>CONFIG_ROCKCHIP_DW_HDMI</code>
** HDMI PHY
* <code>CONFIG_PHY_ROCKCHIP_INNO_DSIDPHY</code>
** MIPI DSI DPHY (note: requires in-review patches linked in status table)
* <code>CONFIG_ROCKCHIP_VOP2</code>
** Video output
* <code>CONFIG_ARCH_ROCKCHIP</code>
** General SoC support
* <code>CONFIG_ROCKCHIP_PHY</code>
** General SoC support
* <code>CONFIG_PHY_ROCKCHIP_INNO_USB2</code>
** USB 2
* <code>CONFIG_RTC_DRV_RK808</code>
** Real-time Clock
* <code>CONFIG_COMMON_CLK_RK808</code>
** Real-time Clock
* <code>CONFIG_MFD_RK808</code>
** Various things relating to the RK817 chip
* <code>CONFIG_CHARGER_RK817</code>
** RK817 charger (note: requires in-review patches linked in status table)
* <code>CONFIG_REGULATOR_RK808</code>
** Voltage regulators
* <code>CONFIG_ROCKCHIP_PM_DOMAINS</code>
** Power management domains
* <code>CONFIG_GPIO_ROCKCHIP</code>
** GPIO support
* <code>CONFIG_PINCTRL_ROCKCHIP</code>
** GPIO and general SoC support
* <code>CONFIG_PWM_ROCKCHIP</code>
** PWM support
* <code>CONFIG_ROCKCHIP_IOMMU</code>
** IOMMU support
* <code>CONFIG_ROCKCHIP_MBOX</code>
** Mailbox support (for communication with MCU)
* <code>CONFIG_ROCKCHIP_SARADC</code>
** Analog-to-digital conversion support, for e.g. microphones
* <code>CONFIG_ROCKCHIP_THERMAL</code>
** Temperature sensor and thermal throttling support
* <code>CONFIG_SPI_ROCKCHIP</code>
** SPI support
* <code>CONFIG_VIDEO_HANTRO_ROCKCHIP</code>
** Hardware video decoder support
* <code>CONFIG_ROCKCHIP_IODOMAIN</code>
** General SoC support so your I/O pins have the right voltage
* <code>CONFIG_COMMON_CLK_ROCKCHIP</code>
** Common clock support
* <code>CONFIG_PHY_ROCKCHIP_INNO_CSIDPHY</code>
** MIPI CSI DPHY
* <code>CONFIG_I2C_RK3X</code>
** I2C support

== Resources ==
=== Repositories ===

* pgwipeout's kernel tree
** https://gitlab.com/pgwipeout/linux-next/-/tree/quartz64-v5.15-rc1
* BSP based development effort for SPL/U-Boot and Linux
** https://gitlab.com/pine64-org/quartz-bsp
* Image CI pipeline aimed at developers
** https://gitlab.com/pgwipeout/quartz64_ci/
* Rockchip U-Boot
** https://github.com/rockchip-linux/u-boot
* Downstream rockchip-linux kernel tree
** https://gitlab.com/pine64-org/quartz-bsp/rockchip-linux
* Tianocore EDK II port for UEFI on Quartz64
** https://github.com/jaredmcneill/quartz64_uefi
* Mainline U-Boot Port by pgwipeout
** https://gitlab.com/pgwipeout/u-boot-quartz64

=== Other ===

* Rockchip-SoC Patchwork Page
** https://patchwork.kernel.org/project/linux-rockchip/list/
* Rockchip Kernel Mailing List Archive
** https://lore.kernel.org/linux-rockchip/

== Board/SoC Documentation ==
=== Booting ===
==== Boot Order ====
The RK3566 boot ROM will search for a valid ID BLOCK in the following order on the support boot media:

* SPI NOR flash
* SPI NAND flash
* SD-Card
* eMMC

... if this fails, the boot ROM will initialize the USB0 port and wait for a connection from the Rockchip
flash/boot tools.

==== Bootloader Flashing ====

As per pgwipeout's [https://gitlab.com/pine64-org/quartz-bsp/u-boot/-/commit/12d102b86813378af08b086f3b9c13ed8010754c commit message]:
* Make a partition named <code>uboot</code> as partition number 1 at 8 MiB to 16 MiB
* <code>dd if=idblock.bin of=/dev/''<mmc/sd>'' seek=64</code>
* <code>dd if=uboot.img of=/dev/''<mmc/sd>''1</code>

==== BSP Image Layout ====

[[Category:Quartz64]][[Category:Rockchip RK3566]]

PineTab2

2023-03-10T14:09:14Z

TuxThePenguin: oops

[[File:PineTab2 Front.jpg|250px|thumb|right|The PineTab 2 with the detachable keyboard attached]]

The '''PineTab 2''' is PINE64's successor to the original [[PineTab]] Linux tablet computer, featuring a faster processor and better availability. The tablet is available in two configurations, 4GB of RAM and 64GB of internal storage or 8GB of RAM and 128GB of internal storage. The tablet ships with a detachable keyboard that doubles as a protective cover.

The tablet is designed around the Rockchip RK3566 processor, which features 4 energy-efficient Cortex-A55 64-bit ARM cores and enjoys good mainline Linux support.

It is expected to be available in April of 2023, with pricing starting at USD 159 for the 4GB/64GB version and USD 209 for the 8GB/128GB version.

== Specifications ==

[[File:RK3566_icon.png|right]]
* '''SoC:''' Rockchip RK3566
* '''CPU:''' 4x ARM Cortex-A55 @ 1.8 GHz
** 32KB L1 Instruction Cache and 32KB L1 Data Cache per core
** 512KB unified system L3 cache
** ARMv8 Cryptography Extensions
* '''GPU:''' Mali-G52 MP2 @ 800 MHz
** Supported by the open source 'Panfrost' driver in Linux and Mesa, supports OpenGL 3.1 and OpenGL ES 3.1 with many newer extensions
* '''NPU:''' 0.8 TOPS Neural Processing Unit
* '''RAM:''' 4GB or 8GB LPDDR4
* '''Storage:'''
** 64GB or 128GB internal eMMC
** 1x MicroSD slot
* '''Display:''' 10.1" IPS LCD Resolution 1280x800
* '''Cameras:''' 2Mpx front, 5Mpx rear
* '''Battery:''' 6000 mAh (22.2Wh)
* '''Buttons:''' Power, volume up, volume down
* '''Network:'''
** Wi-Fi
** Bluetooth
* '''I/O:'''
** 1x USB-C 3.0
** 1x USB-C 2.0
** 1x MicroHDMI
** 1x 3.5mm audio jack
** 1x 5 pin Pogo connector for keyboard
** (PCIe on PCB as a flat flex ribbon connector, no room for M.2 NVMe drives in case)
* '''Multimedia:'''
** rkdjpeg: 1080p120 JPEG decode
*** no driver in mainline yet
** hantro: JPEG/VP8/H.264 encode, 1080p MPEG-2/H.263/VP8/H.264 AVC decode
*** mainline driver does not yet support all codecs/functions, see [[Mainline Hardware Decoding]] and [[Mainline Hardware Encoding]]
** rkvdec2: 4K H.264 AVC Main10 L5.1/H.265 HEVC Main10 L5.1/VP9 Profile 0 and 2 L5.1 decode
*** no driver in mainline yet
** rkvenc2: 4K H.264 AVC/H.265 HEVC encode
*** no driver in mainline yet
* '''Build:''' Metal and Plastic
* '''Dimensions:''' 242x161x9mm
* '''Misc:'''
** Protective cover with keyboard

== Development efforts ==

{{SeeMainArticle|Quartz64 Development}}

Linux mainline is already quite far along for the device, as the SoC is the same as is used in the Quartz64 line of devices.

Notable features currently missing are the display panel driver (needs submitting), Wi-Fi driver (needs porting/major cleanup) and camera driver (needs writing).

== Datasheets for Components and Peripherals ==

Rockchip RK3566 SoC information:
* [https://files.pine64.org/doc/quartz64/Rockchip%20RK3566%20Datasheet%20V1.0-20201210.pdf Rockchip RK3566 ver 1.0 datasheet]
* [https://opensource.rock-chips.com/images/2/26/Rockchip_RK3568_TRM_Part1_V1.3-20220930P.PDF Rockchip RK3566 and RK3568 TRM (Technical Reference Manual)]

== External Links ==

* [https://www.pine64.org/2022/12/15/december-update-merry-christmas-and-happy-new-pinetab/ December 2022 Community Update]
* [https://www.pine64.org/2023/03/01/february-update-things-are-taking-shape/ February 2023 Community Update]

[[Category:Rockchip RK3566]]

PineTab2

2023-03-10T14:07:50Z

TuxThePenguin:

[[File:PineTab2 Front.jpg|250px|thumb|right|The PineTab 2 with the detachable keyboard attached]]

The '''PineTab 2''' is PINE64's successor to the original [[PineTab]] Linux tablet computer, featuring a faster processor and better availability. The tablet is available in two configurations, 4GB of RAM and 64GB of internal storage or 8GB of RAM and 128GB of internal storage. The tablet ships with a detachable keyboard that doubles as a protective cover.

The tablet is designed around the Rockchip RK3566 processor, which features 4 energy-efficient Cortex-A55 64-bit ARM cores and enjoys good mainline Linux support.

It is expected to be available in April of 2023, with pricing starting at USD 159 for the 4GB/64GB version and USD 209 for the 8GB/128GB version.

== Specifications ==

[[File:RK3566_icon.png|right]]
* '''SoC:''' Rockchip RK3566
* '''CPU:''' 4x ARM Cortex-A55 @ 1.8 GHz
** 32KB L1 Instruction Cache and 32KB L1 Data Cache per core
** 512KB unified system L3 cache
** ARMv8 Cryptography Extensions
* '''GPU:''' Mali-G52 MP2 @ 800 MHz
** Supported by the open source 'Panfrost' driver in Linux and Mesa, supports OpenGL 3.1 and OpenGL ES 3.1 with many newer extensions
* '''NPU:''' 0.8 TOPS Neural Processing Unit
* '''RAM:''' 4GB or 8GB LPDDR4
* '''Storage:'''
** 64GB or 128GB internal eMMC
** 1x MicroSD slot
* '''Display:''' 10.1" IPS LCD Resolution 1280x800
* '''Cameras:''' 2Mpx front, 5Mpx rear
* '''Battery:''' 6000 mAh (22.2Wh)
* '''Buttons:''' Power, volume up, volume down
* '''Network:'''
** Wi-Fi
** Bluetooth
* '''I/O:'''
** 1x USB-C 3.0
** 1x USB-C 2.0
** 1x MicroHDMI
** 1x 3.5mm audio jack
** 1x 5 pin Pogo connector for keyboard
** (PCIe on PCB as a flat flex ribbon connector, no room for M.2 NVMe drives in case)
* '''Multimedia:'''
** rkdjpeg: 1080p120 JPEG decode
*** no driver in mainline yet
** hantro: JPEG/VP8/H.264 encode, 1080p MPEG-2/H.263/VP8/H.264 AVC decode
*** mainline driver does not yet support all codecs/functions, see [[Mainline Hardware Decoding]] and [[Mainline Hardware Encoding]]
** rkvdec2: 4K H.264 AVC Main10 L5.1/H.265 HEVC Main10 L5.1/VP9 Profile 0 and 2 L5.1 decode
*** no driver in mainline yet
** rkvenc2: 4K H.264 AVC/H.265 HEVC encode
*** no driver in mainline yet
* '''Build:''' Metal and Plastic
* '''Dimensions:''' 242x160x9mm
* '''Misc:'''
** Protective cover with keyboard

== Development efforts ==

{{SeeMainArticle|Quartz64 Development}}

Linux mainline is already quite far along for the device, as the SoC is the same as is used in the Quartz64 line of devices.

Notable features currently missing are the display panel driver (needs submitting), Wi-Fi driver (needs porting/major cleanup) and camera driver (needs writing).

== Datasheets for Components and Peripherals ==

Rockchip RK3566 SoC information:
* [https://files.pine64.org/doc/quartz64/Rockchip%20RK3566%20Datasheet%20V1.0-20201210.pdf Rockchip RK3566 ver 1.0 datasheet]
* [https://opensource.rock-chips.com/images/2/26/Rockchip_RK3568_TRM_Part1_V1.3-20220930P.PDF Rockchip RK3566 and RK3568 TRM (Technical Reference Manual)]

== External Links ==

* [https://www.pine64.org/2022/12/15/december-update-merry-christmas-and-happy-new-pinetab/ December 2022 Community Update]
* [https://www.pine64.org/2023/03/01/february-update-things-are-taking-shape/ February 2023 Community Update]

[[Category:Rockchip RK3566]]

User:TuxThePenguin

2023-02-25T02:24:50Z

TuxThePenguin: Update my page

Pine64 community insider. 
I don't touch the wiki much but I do some kernel development and help to moderate the chats.

'''Discord:''' Segfault#0127 
'''Telegram:''' @segfault_11 
'''Gitlab:''' [https://gitlab.com/TuxThePenguin0 TuxThePenguin0] 
'''Github:''' [https://github.com/TuxThePenguin0 TuxThePenguin0] 

'''Notable devices I own:'''
: PineTab2 pre-production unit
: Pinebook Pro
: Pinephone
: Quartz64 Model A
: Pinetime
: Various SBCs including Raspberry Pis and NVIDIA Jetsons

Main Page

2023-02-25T02:12:59Z

TuxThePenguin: Correct #quartz-dev IRC channel name

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 [[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 devices manufactured by PINE64:

* Phones: '''[[PinePhone]]''' and '''[[PinePhone Pro]]'''
* Phone accessories: '''[[PinePhone (Pro) Add-ons]]''' and '''[[PinePhone (Pro) Keyboard]]'''
* Tablets: '''[[PineTab]]''' and '''[[PineNote]]'''
* Wearable: '''[[PineBuds Pro]]''', '''[[PineTime]]'''
* Laptops: '''[[Pinebook]]''' and '''[[Pinebook Pro]]'''
* Laptop accessories: '''[[Pinebook Pro Dock|Pinebook Pro Docking station]]'''
* Single-board computers: '''[[Ox64]]''', '''[[STAR64]]''', '''[[Quartz64]]''', '''[[QuartzPro64_Development|QuartzPro64]]''', '''[[ROCKPro64]]''', '''[[ROCK64]]''', '''[[PINE A64]]''', '''[[PINE A64-LTS]]''' and '''[[PINE H64]]'''
* Set-top box: '''[[RockBox]]'''
* Clusters and modules: '''[[Clusterboard]]''', '''[[SOPINE]]''', '''[[SOPINE Baseboard]]''', '''[[SOEDGE]]''', '''[[SOEDGE Baseboard]]''', and '''[[SOQuartz]]'''
* IP camera: '''[[PineCube]]'''
* Power adapter: '''[[PinePower]]'''
* Soldering iron: '''[[Pinecil]]'''
* Makerspace: '''[[PineCone]]''' and '''[[Pinedio]]'''

== Community and Support ==

Community collaboration and support is focused around the chat platforms and forums described below. 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.

{{hint|PINE64 community is not some always responding, restless commercial customer service, or some sort of almighty existence that can resolve all your problems. When participating in community discussions, please be patient and do not expect questions to be answered immediately, certainly, or currently.
* The activity of community members varies depending on the time of day and the number of active users.
* Whether your questions will be answered & whether the answers are right and definitive, depends on the information you provide, and, after all, difficulty of your questions & community members' ability.
* Read [http://www.catb.org/~esr/faqs/smart-questions.html How To Ask Questions The Smart Way] to learn more.
* Please read [[PINE64 Community Rules and Code of Conduct]].

'''Note:'''
* PINE64 uses a bridge bot (''[https://github.com/42wim/matterbridge matterbridge]'' with some modifications), which allows Discord, IRC, Matrix, and Telegram users to see and participate in the community chat.
* The bot name is "Pine64 Protocol Droid" and if you see this, look in the message to see the actual author of the message.
* When the bot relays messages it will show the platform the user is using: ''[D]'' for ''Discord'', ''[I]'' for ''IRC'', ''[M]'' for ''Matrix'' and ''[T]'' for ''Telegram''.
}}

The community chat platforms are the following:

* '''Discord''': use this '''[https://discord.gg/pine64 Invite Link]'''. All Pine64 discord channels are immediately viewable, do not need to join separate channels like the Telegram/Matrix table below.
* '''IRC''': the server is irc.pine64.org. 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://matrix.to/#/#pine64-announcements:matrix.org #pine64-announcements:matrix.org]
| [https://t.me/PINE64_News @PINE64_News]
| Unavailable
|-
| General PINE64 chat
| [https://matrix.to/#/#pine64:matrix.org #pine64:matrix.org]
| [https://t.me/mtrx_pine64 @mtrx_pine64]
| #pine64
|-
| PINE A64(+), A64-LTS & SOPine
| [https://matrix.to/#/#pine64sopine:matrix.org #pine64sopine:matrix.org]
| [https://t.me/pine64sopine @pine64sopine]
| #lts-sopine
|-
| ROCK64 / ROCKPro64
| [https://matrix.to/#/#rock64:matrix.org #rock64:matrix.org]
| [https://t.me/mtrx_rock64 @mtrx_rock64]
| #rock64
|-
| Quartz64
| [https://matrix.to/#/#quartz64:matrix.org #quartz64:matrix.org]
| [https://t.me/joinchat/Vq50DXkH31e0_i-f Quartz64]
| #quartz64
|-
| Quartz64 Development
| [https://matrix.to/#/#quartz64-dev:matrix.org #quartz64-dev:matrix.org]
| [https://t.me/q64dev @q64dev]
| #quartz-dev
|-
| Star64
| [https://matrix.to/#/#star64:matrix.org #star64:matrix.org]
| [https://t.me/star64_sbc @star64-sbc]
| Unavailable
|-
| Pinebook and Pinebook Pro
| [https://matrix.to/#/#pinebook:matrix.org #pinebook:matrix.org]
| [https://t.me/mtx_pinebook @mtx_pinebook]
| #pinebook
|-
| PinePhone
| [https://matrix.to/#/#pinephone:matrix.org #pinephone:matrix.org]
| [https://t.me/pinephone @pinephone]
| #pinephone
|-
| PineNote
| [https://matrix.to/#/#pinenote:matrix.org #pinenote:matrix.org]
| [https://t.me/pinenote @PineNote]
| #pinenote
|-
| PineTab
| [https://matrix.to/#/#pinetab64:matrix.org #pinetab64:matrix.org]
| [https://t.me/PineTab @PineTab]
| #pinetab
|-
| PineTime
| [https://matrix.to/#/#pinetime:matrix.org #pinetime:matrix.org]
| [https://t.me/pinetime @pinetime]
| #Pinetime
|-
| PineTime Development
| [https://matrix.to/#/#pinetime-dev:matrix.org #pinetime-dev:matrix.org]
| [https://t.me/pinetime_dev @pinetime_dev]
| #pinetime-dev
|-
| PineBuds Pro
| [https://matrix.to/#/#pinebuds:matrix.org #pinebuds:matrix.org]
| [https://t.me/+nJVhM0mZ9KhlYmZl @pinebuds]
| Unavailable
|-
| Pinecil
| [https://matrix.to/#/#pinecil:matrix.org #pinecil:matrix.org]
| [https://t.me/joinchat/Kmi2S1iej-_4DgrVf3jjnQ Pinecil]
| #pinecil
|-
| Pinecil Development
| [https://matrix.to/#/#pinecil-dev:matrix.org #pinecil-dev:matrix.org]
| [https://t.me/+8_pdKqXrVuQ4OTk1 Pinecil-dev]
| Unavailable
|-
| Pinetalk Podcast || Unavailable || Unavailable || Unavailable
|-
| PineCube
| [https://matrix.to/#/#cube64:matrix.org #cube64:matrix.org]
| [https://t.me/pinecube @pinecube]
| #cube
|-
| Nutcracker, Ox64
| [https://matrix.to/#/#pine64-nutcracker:matrix.org #pine64-nutcracker:matrix.org]
| [https://t.me/joinchat/Kmi2S0nOsT240emHk-aO6g Nutcracker]
| #nutcracker
|-
| LoRa
| [https://matrix.to/#/#pinelora:matrix.org #pinelora:matrix.org]
| [https://t.me/pine64lora @pine64lora]
| #lora
|-
| Off-topic
| [https://matrix.to/#/#offtopic64:matrix.org #offtopic64:matrix.org]
| [https://t.me/pine64offtopic @pine64offtopic]
| #Offtopic
|}

There is also an unofficial Matrix Space at [https://matrix.to/#/#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 ==

* '''[[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
* '''[[How to Contribute]]''': Information about how to contribute to different partner projects
* '''[[Where to Report Bugs]]''': Information about how to report bugs
* '''[[Project]]''': A variety of well documented PINE64 projects to serve as inspiration
* '''[[:Category:Guide]]''': Lists other guide pages than those two above, some are dedicated to specific devices

Overclocking

2021-10-22T09:54:09Z

TuxThePenguin: Clarification and rewording

{{warning|1= There is the possibility of damaging your equipment by overclocking. Do so at your own risk!}}
{{hint|This page is incomplete, you're welcome to improve it.}}
{{hint|All information regarding clock speeds, voltages and more are stored in the DTB (Device Tree Blob). You can learn more about it [https://elinux.org/Device_Tree_Reference here].}}

Overclocking is a way to get more performance out of the system by running it at higher clock speeds than the factory default, usually while putting out more heat and using more power (You can also downclock to possibly reduce power consumption and thermals at the cost of performance). It is highly recommended that you avoid overvolting the device, as that has a high risk of damaging the hardware, hence the warning at the beginning of this page. However, just some slight overclocks without the added voltage can not only improve performance, but not carry as much risk (Still: Do at your own risk!). It should be noted however that overclocking can cause instability, so you will need to test and see what values work best with your device (There is a silicon lottery for the Pinephone's hardware).

= A64-based devices =

{{note|These instructions are targeting the Pinephone to simplify the explanation, however they can be used to also overclock other devices such as the Pinetab if you modify the proper DTB files.}}

== Editing the Pinephone DTS ==

In order to overclock the Pinephone you will have to first convert the DTB file in <code>/boot/dtbs/allwinner/</code> to a DTS file. You will see <code>sun50i-a64-pinephone-1.2.dtb</code>, and also two other files with different pinephone mainboard revisions (1.1 and 1.0). You will want to select the correct file for your pinephone (Only choose 1.1 if you have a braveheart, As all other consumer pinephones use the 1.2 DTS).

Once you've found the file, you can run the following command to convert the DTB to DTS:
<code>dtc -I dtb -O dts /boot/dtbs/allwinner/sun50i-a64-pinephone-1.2.dtb -o /boot/dtbs/allwinner/sun50i-a64-pinephone-1.2.dts</code>

Finally, modify the newly converted .dts file and change the clockspeeds you wish to modify. You can simply use a text editor to do so.

To convert back to DTB:
<code>dtc -I dts -O dtb /boot/dtbs/allwinner/sun50i-a64-pinephone-1.2.dts -o /boot/dtbs/allwinner/sun50i-a64-pinephone-1.2.dtb</code>

Afterwards you can simply reboot and check with <code>sudo cat /sys/kernel/debug/clk/clk_summary</code> to see if the changes have correctly applied.

{{note|In the future it is possible that someone may make a driver to adjust clockspeeds of the A64 from userspace (using a config file) without the need to recompile. However, currently the only way to overclock is to either compile your own kernel, or modify just the DTB (instructions above).}}

== GPU ==

Open <code>/boot/dtbs/allwinner/sun50i-a64-pinephone-1.2.dts</code> (You will have to find the source of the kernel used by your distribution. There is the Pine64 kernel, and Megi's) in a text editor following these instructions: https://wiki.pine64.org/wiki/Overclocking#Edit_Pinephone_DTS

Look for <code>mali: gpu@1c4000 {</code> and within that block search for <code>assigned-clock-rates = <432000000>;</code>

The <code>assigned-clock-rates</code> line should be set to <code>432000000</code>, this means that the GPU is clocked at 432MHz by default. So if you want 500MHz, set the value to <code>500000000</code>.

Save the dts file, and recompile the DTB. In order to check if the overclock was successfully applied you can run: <code>sudo cat /sys/kernel/debug/clk/clk_summary</code>.

{{note|The file may be slightly different and you may need to enter the values as hexidecimals}}
{{hint|The GPU appears to run stable overclocked to 560 Mhz, however more testing with a wider group of devices is needed.}}
{{hint|Remember to run a benchmark tool (such as glmark2-es2) to help check stability.}}

== CPU ==

The stock speed of the A64 is 1.152 GHz. It is not recommended to the overclock the CPU because doing so greatly increases power and thermals and will overheat the device for little to no gain.

== DRAM ==

{{warning|1=It is not recommended to exceed 667 MHz clockspeed on the DRAM. 624MHz is likely the upper limit.}}
{{hint|Make sure to set your DRAM to a multiple of 24.}}

When overclocking the GPU, it is a good idea to also overclock the DRAM, as the main bottleneck of the A64 SOC is the memory. The A64's maximum ram clockspeed falls just short of 667MHz. This may be unstable on your device however.

Around 600 MHz (PC-1200) should work fine, however some people have reported instability at lower clockspeeds. Arch Linux Arm uses a default clockspeed of 552MHz, with uboot builds available to easily switch out for a higher (624) or lower (492) DRAM clockspeed.

It is possible that by reverse engineering the DRAM driver from allwinner that auto tuning can be accomplished to get the best performance.

Setting the DRAM clock is accomplished by modifying pinephone_defconfig in uboot (https://gitlab.com/pine64-org/u-boot/-/blob/crust/configs/pinephone_defconfig)

You can find simple instructions on doing so here: [[Uboot]]

== VPU ==

In order to allocate more VRAM for the GPU you can add <code>cma=256</code> to your kernel (or use kconfig with CONFIG_CMA_SIZE_MBYTES=256) cmdline in boot.scr which you will have to compile using mkimage. By default the kernel allocates only 64MB, and the maximum value is 256MB.

In order to compile boot.scr you can run <code>mkimage -C none -A arm64 -T script -d boot.cmd boot.scr</code>

{{note|You may not have a boot.cmd file in your boot directory and instead you may instead have a boot.txt}}

== Cedrus ==

Overclocking cedrus is achieved by modifying the kernel source code: https://elixir.bootlin.com/linux/latest/source/drivers/staging/media/sunxi/cedrus/cedrus.c#L507

{{note|I'm (33yn2) not particularly sure if this makes any difference, or if it might infact have a negative impact. Probably not worth messing with.}}

= RK3399-based devices =
The RK3399 clocks are found in [https://github.com/torvalds/linux/blob/master/arch/arm64/boot/dts/rockchip/rk3399-opp.dtsi arch/arm64/boot/dts/rockchip/rk3399-opp.dtsi]

More optimised voltages and clocks can be found in [https://github.com/torvalds/linux/blob/master/arch/arm64/boot/dts/rockchip/rk3399-op1-opp.dtsi arch/arm64/boot/dts/rockchip/rk3399-op1-opp.dtsi]
These include a slight overclock and undervolt, they are intended for the OP1 CPU found in many chromebooks but have worked fine in all recorded cases on regular RK3399 SOCs in other devices.

==GPU==
Any clock speeds can be added for the GPU in <code>gpu_opp_table</code>

The highest recommended voltage for the GPU is 1.2V as specified in the RK3399 schematic from Rockchip.

Segfault has found that the RK3399 in his Pinebook Pro can reach 950MHz on the GPU while being stable.

The stock speed for the GPU is 800Mhz.

Note that the GPU in the RK3399 is already bottlenecked by the memory bandwidth available to it, so overclocking generally yields no improvements.

==CPU==
A set of available clock speeds that can be added to the CPU clusters can be found in <code>drivers/clk/rockchip/clk-rk3399.c</code> under <code>rk3399_cpuclkl_rates</code> for the little cores and <code>rk3399_cpuclkb_rates</code> for the big cores.

These clock speeds can be added to <code>cluster0_opp</code> for the small cores and <code>cluster1_opp</code> for the big cores respectively.

The maximum limit is 1.8GHz on the little cores and 2.2GHz on the big cores.

The highest recommended voltage for the little cores is 1.2V and for the big cores is 1.25V.

Segfault has found that the RK3399 in his Pinebook Pro can reach 1.7GHz on the little cores and 2.08GHz on the big ones.

The stock speed for the little cores is 1.4GHz and on the big cores it is 1.8GHz, the OP1 speeds default to 1.5GHz and 2.0GHz instead.

= ROCK64 =

DTB is in <code>/boot/dtbs/rockchip/rk3328-rock64.dtb</code>. CPU clock rates are inside <code>opp_table0</code> as hexadecimal numbers in the <code>opp-hz</code> field.

Check the achieved clock speed with <code>sudo cat /sys/kernel/debug/clk/clk_summary | grep armclk</code>. Does not seem to overclock at stock voltages at all, defaults to 408 MHz if it fails to set a clock rate. Stock voltage is 1.30V, just shy of the 1.35V maximum outlined in [https://www.rockchip.fr/RK3328%20datasheet%20V1.1.pdf the datasheet]. Overvolting to 1.325V just left the device in an unbootable state for CounterPillow, would not recommend.

GPU needs investigating, but is seemingly tied to the bus speed.

[[Category:SOPine]] [[Category:Pine A64]] [[Category:Pine H64]] [[Category:A64-LTS]] [[Category:PineBook]] [[Category:PinePhone]] [[Category:PineTab]] [[Category:Rock64]] [[Category:PineBook Pro]] [[Category:ROCKPro64]] [[Category:Allwinner A64]] [[Category:Allwinner H6]] [[Category:Rockchip RK3399]]

Pinebook Pro Keyboard Assembly

2021-09-10T11:04:07Z

TuxThePenguin: Better wording and add a clarification

{{hint|This page is incomplete, tell me how I can improve it! Segfault#0127 on the PINE64 Discord server}}

The Pinebook Pro keyboard comes as a pre-assembled unit built into the main shell of the device, a damaged shell had the keyboard removed from it to be studied.
Note that removing the keyboard from the shell is technically irreversible since it's held in with melted plastic rivets. If these ever happen to break then you could likely hold the keyboard in with adhesives or drill small holes and use screws instead.

The keyboard is sandwiched between a thick (likely 0.7mm) steel plate and the plastic shell, this steel plate serves as a mounting point for some of the components inside the laptop as well as adding a significant amount of structural rigidity to the device. The actual keyboard is made of a very thin metal backplate, a clear flexible plastic PCB, and a black flexible plastic layer that appears to be removable but more research will need to be done.

The key mechanism is a relatively modern style of scissor switch, the upside to this mechanism is that the keys have a very nice feel to them and don't fall apart easily, the downside is that if the plastic scissor mechanism gets damaged the whole key assembly will start to fall off due to slipping out from under the metal arms in the keyboard backplate. The only known fix is to replace the key assembly, or more likely the entire keyboard mechanism, more research should be done into this.

Older style scissor switches allowed you to just pull the keycap straight off the mechanism and snap it back into place by pressing down on it. Do not do this for newer mechanisms like the Pinebook Pro keyboard, all that will do is damage the mechanism.

== Removing Keys ==
{{warning|1=Do not attempt this unless you know what you're doing, there will be very few cases where this works}}
Keys can be relatively safely removed (however the mechanism can easily be damaged by someone who doesn't know what they're doing) when the keyboard assembly has been removed from the shell, however with the shell in place it blocks movement of the keys that is required to unhook the mechanism from the metal backplate.
{{hint|The keys *might* be removable without taking the keyboard out of the frame, this needs more research}}
To remove a key, first push it all the way in, slide it upwards slightly, and lift the top half of the key, this should dislodge the upper half of the scissor mechanism, this step can be tricky, the keys were designed to be assembled once and never removed again.
[[file:pinebookpro_keyboard_key-half-removed.jpg|400px|none]]
Next you can just slide the key down slightly, this will dislodge the lower half of the scissor mechanism and the key should come completely off the keyboard.
[[file:pinebookpro_keyboard_key-removed.jpg|400px|none]]
Re-attaching a key can be quite fiddly since the mechanism stays attached to the key rather than the keyboard like older scissor designs. 
The assembly process is the same as disassembly, just reversed, but you have to be careful with horizontal alignment, otherwise the lower half of the mechanism won't lodge in place. 
Note that if a key mechanism is damaged, pressing in the upper corners of the key will cause it to dislodge and fall off the keyboard.
[[file:pinebookpro_keyboard_key.jpg|400px|none]]
Damaged keys might look like this, note that the pin on the lower right side of the mechanism is slightly deformed and the latch on the upper half of the mechanism is bowed out slightly and cracked. 
This is enough damage to cause the key to pop out when pressed in the upper corners.

Pinebook Pro Keyboard Assembly

2021-09-10T10:46:51Z

TuxThePenguin: Add example of a broken key

{{hint|This page is incomplete, tell me how I can improve it! Segfault#0127 on the PINE64 Discord server}}

The Pinebook Pro keyboard comes as a pre-assembled unit built into the main shell of the device, a damaged shell had the keyboard removed from it to be studied.
Note that removing the keyboard from the shell is technically irreversible since it's held in with melted plastic rivets. If these ever happen to break then you could likely hold the keyboard in with adhesives or drill small holes and use screws instead.

The keyboard is sandwiched between a thick (likely 0.7mm) steel plate and the plastic shell, this steel plate serves as a mounting point for some of the components inside the laptop as well as adding a significant amount of structural rigidity to the device. The actual keyboard is made of a very thin metal backplate, a clear flexible plastic PCB, and a black flexible plastic layer that appears to be removable but more research will need to be done.

The key mechanism is a relatively modern style of scissor switch, the upside to this mechanism is that the keys have a very nice feel to them and don't fall apart easily, the downside is that if the plastic scissor mechanism gets damaged the whole key assembly will start to fall off due to slipping out from under the metal arms in the keyboard backplate. The only known fix is to replace the key assembly, or more likely the entire keyboard mechanism, more research should be done into this.

== Removing Keys ==
{{warning|1=Do not attempt this unless you know what you're doing, there will be very few cases where this works}}
Keys can be relatively safely removed (however the mechanism can easily be damaged by someone who doesn't know what they're doing) when the keyboard assembly has been removed from the shell, however with the shell in place it blocks movement of the keys that is required to unhook the mechanism from the metal backplate.
{{hint|The keys *might* be removable without taking the keyboard out of the frame, this needs more research}}
To remove a key, first push it all the way in, then slide it upwards slightly, this should dislodge the upper half of the scissor mechanism, this step can be tricky, the keys were designed to be assembled once and never removed again.
[[file:pinebookpro_keyboard_key-half-removed.jpg|400px|none]]
Next you can just slide the key down slightly, this will dislodge the lower half of the scissor mechanism and the key should come completely off the keyboard.
[[file:pinebookpro_keyboard_key-removed.jpg|400px|none]]
Re-attaching a key can be quite fiddly since the mechanism stays attached to the key rather than the keyboard like older scissor designs. 
The assembly process is the same as disassembly, just reversed, but you have to be careful with horizontal alignment, otherwise the lower half of the mechanism won't lodge in place. 
Note that if a key mechanism is damaged, pressing in the upper corners of the key will cause it to dislodge and fall off the keyboard.
[[file:pinebookpro_keyboard_key.jpg|400px|none]]
Damaged keys might look like this, note that the pin on the lower right side of the mechanism is slightly deformed and the latch on the upper half of the mechanism is bowed out slightly and cracked. 
This is enough damage to cause the key to pop out when pressed in the upper corners.

File:Pinebookpro keyboard key.jpg

2021-09-10T10:41:23Z

TuxThePenguin: Underside of a key from a Pinebook Pro keyboard

== Summary ==
Underside of a key from a Pinebook Pro keyboard

Pinebook Pro Keyboard Assembly

2021-09-10T09:57:58Z

TuxThePenguin: Reword some bits

{{hint|This page is incomplete, tell me how I can improve it! Segfault#0127 on the PINE64 Discord server}}

The Pinebook Pro keyboard comes as a pre-assembled unit built into the main shell of the device, a damaged shell had the keyboard removed from it to be studied.
Note that removing the keyboard from the shell is technically irreversible since it's held in with melted plastic rivets. If these ever happen to break then you could likely hold the keyboard in with adhesives or drill small holes and use screws instead.

The keyboard is sandwiched between a thick (likely 0.7mm) steel plate and the plastic shell, this steel plate serves as a mounting point for some of the components inside the laptop as well as adding a significant amount of structural rigidity to the device. The actual keyboard is made of a very thin metal backplate, a clear flexible plastic PCB, and a black flexible plastic layer that appears to be removable but more research will need to be done.

The key mechanism is a relatively modern style of scissor switch, the upside to this mechanism is that the keys have a very nice feel to them and don't fall apart easily, the downside is that if the plastic scissor mechanism gets damaged the whole key assembly will start to fall off due to slipping out from under the metal arms in the keyboard backplate. The only known fix is to replace the key assembly, or more likely the entire keyboard mechanism, more research should be done into this.

== Removing Keys ==
{{warning|1=Do not attempt this unless you know what you're doing, there will be very few cases where this works}}
Keys can be relatively safely removed (however the mechanism can easily be damaged by someone who doesn't know what they're doing) when the keyboard assembly has been removed from the shell, however with the shell in place it blocks movement of the keys that is required to unhook the mechanism from the metal backplate.
To remove a key, first push it all the way in, then slide it upwards slightly, this should dislodge the upper half of the scissor mechanism, this step can be tricky, the keys were designed to be assembled once and never removed again.
[[file:pinebookpro_keyboard_key-half-removed.jpg|400px|none]]
Next you can just slide the key down slightly, this will dislodge the lower half of the scissor mechanism and the key should come completely off the keyboard.
[[file:pinebookpro_keyboard_key-removed.jpg|400px|none]]
Re-attaching a key can be quite fiddly since the mechanism stays attached to the key rather than the keyboard like older scissor designs. 
The assembly process is the same as disassembly, just reversed, but you have to be careful with horizontal alignment, otherwise the lower half of the mechanism won't lodge in place. 
Note that if a key mechanism is damaged, pressing in the upper corners of the key will cause it to dislodge and fall off the keyboard.

Pinebook Pro Keyboard Assembly

2021-09-10T09:51:54Z

TuxThePenguin: Add some info about my borked keyboard

{{hint|This page is incomplete, tell me how I can improve it! Segfault#0127 on the PINE64 Discord server}}

The Pinebook Pro keyboard comes as a pre-assembled unit built into the main shell of the device, a damaged shell had the keyboard removed from it to be studied.
Note that removing the keyboard from the shell is technically irreversible since it's held in with melted plastic rivets. If these ever happen to break then you could likely hold the keyboard in with adhesives or drill small holes and use screws instead.

The keyboard is sandwiched between a thick (likely 0.7mm) steel plate and the plastic shell, this steel plate serves as a mounting point for some of the components inside the laptop as well as adding a significant amount of structural rigidity to the device. The actual keyboard is made of a very thin metal backplate, a clear flexible plastic PCB, and a black flexible plastic layer that appears to be removable but more research will need to be done.

The key mechanism is a relatively modern style of scissor switch, the upside to this mechanism is that the keys have a very nice feel to them and don't fall apart easily, the downside is that if the plastic scissor mechanism gets damaged the whole key assembly will start to fall off due to slipping out from under the metal arms in the keyboard backplate. The only known fix is to replace the key assembly, or more likely the entire keyboard mechanism, more research should be done into this.

== Removing Keys ==
{{warning|1=Do not attempt this unless you know what you're doing, there will be very few cases where this works}}
Keys can be relatively safely removed (however the mechanism can easily be damaged by someone who doesn't know what they're doing) when the keyboard assembly has been removed from the shell, however with the shell in place it blocks movement of the keys that is required to unhook the mechanism from the metal backplate.
To remove a key, first push it all the way in, then slide it upwards slightly, this should dislodge the upper half of the scissor mechanism, this step can be tricky, the keys were designed to be assembled once and never removed again.
[[file:pinebookpro_keyboard_key-half-removed.jpg|400px|none]]
Next you can just slide the key down slightly, this will dislodge the lower half of the scissor mechanism and the key should come completely off the keyboard.
[[file:pinebookpro_keyboard_key-removed.jpg|400px|none]]
Re-attaching a key can be quite fiddly since the mechanism stays attached to the key rather than the keyboard like older scissor designs. The process is the same, just reversed but you have to be careful with horizontal alignment, otherwise the lower half of the mechanism won't lodge in place. 
Note that if a key mechanism is damaged it's most likely that pressing in the upper corners of the key will cause it to dislodge, which makes typing quite difficult. This is why it's not recommended to remove keys from this keyboard.

File:Pinebookpro keyboard key-removed.jpg

2021-09-10T09:44:56Z

TuxThePenguin: Removed key from a disassembled Pinebook Pro keyboard assembly

== Summary ==
Removed key from a disassembled Pinebook Pro keyboard assembly

File:Pinebookpro keyboard key-half-removed.jpg

2021-09-10T09:41:02Z

TuxThePenguin: Half-removed key from a disassembled Pinebook Pro keyboard assembly

== Summary ==
Half-removed key from a disassembled Pinebook Pro keyboard assembly

User:TuxThePenguin

2021-05-22T01:05:13Z

TuxThePenguin: Update details

Just another community member, I guess I moderate the Pine community servers which is kinda neat.

'''Discord:''' Segfault#0127 
'''Telegram:''' @segfault_11 
'''Github:''' TuxThePenguin0 

'''Notable devices I own:'''
: Thinkpad W540
: Pinebook Pro
: Pinetime
: Nexus 9
: '''3''' 2012 Nexus 7's
: Switch Lite
: Google Pixel 4a
: HTC 10
: Samsung Galaxy S5
: Samsung Galaxy Ace 3
: LG G Watch
: Some Raspberry Pi's

I can probably help with details about Rockchip SOCs, like why eGPUs won't work with the RK3399 or how to overclock just about any of them.

Overclocking

2021-05-12T06:37:44Z

TuxThePenguin: Reword and update RK3399 CPU overclock details + Update TuxThePenguin name to Segfault

Pinebook Pro Hardware Accessory Compatibility

2021-01-16T05:30:10Z

TuxThePenguin: /* Bluetooth hardware */

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.

Please note that many 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].

{| class="wikitable sortable"
!Type || Make/Model || Size || Hardware IDs || Result || Notes || Power options Active only || Save power setting?
|-
| 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 || investigating || No touchpad issues. ||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
|}

== 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
|}

= 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 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.
|-
|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
|}

----

= 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

2020-11-04T09:44:29Z

TuxThePenguin: Add new 16GB Sandisk Ultra

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 ==
Note that only PCIe type M.2 drives will work. Any SATA or USB type M.2 card will NOT work.
{| class="wikitable sortable"
!Type || Make/Model || Size || Hardware IDs || Result || Notes || Power options Active only || Save power setting?
|-
| 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
|-
| 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] || ||
|-
| 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 || 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 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 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
|}

== 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
|}

= USB hardware =

== USB Card Readers ==

Stand-alone card readers only please, see below for combination 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 ==

Stand-alone network devices only please, see below for combination 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 Combination Devices ==
{| class="wikitable sortable"
!Type || Make/Model || Hardware IDs || Result || Notes
|-
|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 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 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
|-
|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 || 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
|-
|}

----

= 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

2020-11-04T04:03:40Z

TuxThePenguin: Fix weird issue with 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 ==
Note that only PCIe type M.2 drives will work. Any SATA or USB type M.2 card will NOT work.
{| class="wikitable sortable"
!Type || Make/Model || Size || Hardware IDs || Result || Notes || Power options Active only || Save power setting?
|-
| 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
|-
| 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] || ||
|-
| 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 || 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 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 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
|}

== 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 64GB (Old model from 2015) || || good but with issues || Works fine but sometimes stops working and needs to be connected to another device to fix it
|-
|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
|}

= USB hardware =

== USB Card Readers ==

Stand-alone card readers only please, see below for combination 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 ==

Stand-alone network devices only please, see below for combination 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 Combination Devices ==
{| class="wikitable sortable"
!Type || Make/Model || Hardware IDs || Result || Notes
|-
|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 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 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
|-
|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 || 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
|-
|}

----

= 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

2020-11-04T03:59:02Z

TuxThePenguin: Fix weird issue with 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 ==
Note that only PCIe type M.2 drives will work. Any SATA or USB type M.2 card will NOT work.
{| class="wikitable sortable"
!Type || Make/Model || Size || Hardware IDs || Result || Notes || Power options Active only || Save power setting?
|-
| 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
|-
| 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] || ||
|-
| 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 || 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 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 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
|}

== 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 64GB (Old model from 2015) || || good but with issues || Works fine but sometimes stops working and needs to be connected to another device to fix it
|-
|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
|}

= USB hardware =

== USB Card Readers ==

Stand-alone card readers only please, see below for combination 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 ==

Stand-alone network devices only please, see below for combination 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 Combination Devices ==
{| class="wikitable sortable"
!Type || Make/Model || Hardware IDs || Result || Notes
|-
|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 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 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
|-
|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 || 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
|-
|}

----

= 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]]

User:TuxThePenguin

2020-11-03T10:56:05Z

TuxThePenguin: Personal info update

Just another community member

'''Discord:''' Segfault#0127 
'''Telegram:''' @sigsegv_11 
'''Github:''' TuxThePenguin0 

'''Notable devices I own:'''
: Thinkpad W540 running Arch
: Pinebook Pro ANSI running Arch
: '''3''' 2012 Nexus 7's running various OSes
: Switch Lite (yet to be hacked)
: Samsung Galaxy S5 running Ubuntu Touch
: Samsung Galaxy Ace 3 running Ubuntu Touch
: ZTE Axon 7 running LineageOS
: Some Raspberry Pi's

Ask me about why an eGPU won't work with the RK3399 
Or about how to overclock the RK3399 I guess :)

PineTab

2020-11-03T10:44:55Z

TuxThePenguin: More detailed display specs

{{warning|1=IMPORTANT INFORMATION for '''Early Adopters''' - please [[PineTab/Early-Adopter|'''CLICK HERE''']] - some '''known issues''' are listed there}}

The PineTab is a 10" tablet created by Pine64.

== Specifications ==
* '''Dimensions:''' 11mm x 175mm x 260mm (Thickness, Width, Height)
* '''Weight:''' 575g (Tablet alone)
* '''Build:''' Plastic
* '''Storage:'''
** 64GB of internal eMMC storage
** MicroSD slot, bootable
** M.2 SSD slot, supports SATA and USB devices only, not NVME (optional)
* '''Cameras:''' 2Mpx Front, 5Mpx Rear
* '''SOC:''' Allwinner A64 Quad Core
* '''CPU:''' 4x ARM A53 1.152GHz
* '''GPU:''' Mali 400 MP2
* '''RAM:''' 2GB LPDDR3
* '''I/O:''' HD Video Out (Mini HDMI), Micro USB 2.0 OTG, USB 2.0 A host, 3.5mm Headphone/Mic combo,
* '''Network:'''
** WiFi (802.11b/g/n, 2.4GHz only)
** Bluetooth 2.1
** M.2 LTE / Cell MODEM card, (optional, and takes place of optional M.2 SSD)
* '''Display:'''
** '''Size:''' 10.1 inches (257mm) diagonal
** '''Type:''' HD IPS capacitive touchscreen, 16M colors
** '''Resolution:''' 1280x800, 16:10 ratio 
* '''Attachments/Accessories:''' Magnetically attached keyboard (optional)
* '''Battery:''' 6000MAh (6Ah)
* '''Misc. features:'''
** Volume rocker and home button
** Speakers and Microphone
** 2.5mm OD 0.7mm ID DC Jack Power (5V 2A) Port

== Keyboard ==
'''Overview:''' The PineTab detachable keyboard features a full function row, FN key functionality, meta key (where the Windows key would be) and all of the keys you need for daily use.

'''FN keys:''': Pause/play (F2), Stop (F3), Previous(F4), Next(F5), Music (F6), Mail (F7), Home (F8), Mute (F9), Vol- (F10), Vol+ (F11), Disable touchpad (F12), NumLock (Insert), Scroll Lock (Delete), PgUp (Up Arrow), PgDn (Down Arrow), Home (Left Arrow), End (Right Arrow), Digital Numpad (7,8,9,0,U,I,O,P,J,K,L,;,M,.,/)

==Versions==
* "pinetab-dev": development version sent to ~100 developers. This one is like the Early Adopter version, but has a different display panel.
* [[PineTab/Early-Adopter|Early Adopter]]: the first hardware revision of the PineTab, which shipped to customers.

[[File:PineTabBoard.jpeg|400px|thumb|right|The insides of the PineTab]]

== PineTab board information, schematics and certifications ==
* PineTab mainboard schematic:
** [https://files.pine64.org/doc/PineTab/PineTab%20Schematic%20v1.2-20191125.pdf PineTab mainboard Released Schematic ver 1.2]
** [https://files.pine64.org/doc/PineTab/PineTab%20Board%20View%20v1.2-20191201-top.pdf PineTab mainboard component placement ver 1.2 - Top View]
** [https://files.pine64.org/doc/PineTab/PineTab%20Board%20View%20v1.2-20191201-bottom.pdf PineTab mainboard component placement ver 1.2 - Bottom View]
* PineTab keyboard schematic:
** PineTab keyboard and Pinebook (Pro) keyboard using same controller and from same engineering source
** [https://files.pine64.org/doc/PineTab/Pinetab%20HB092A%20Keyboard%20Schematic.pdf PineTab Keyboard Schematic]
** [https://files.pine64.org/doc/PineTab/HB092_0884232458_Hynitron_PTP_20200514_662905_Linux_US_BackLight_CRC_175057F5.hex PineTab keyboard firmware code]
** [https://files.pine64.org/doc/PineTab/SH68F83V2.0.pdf PineTab Keyboard Controller Datasheet]

* PineTab certifications:
** [https://files.pine64.org/doc/cert/PineTab%20FCC-SDOC%20Certificate-S20060600404001.pdf PineTab FCC Certificate]
** [https://files.pine64.org/doc/cert/PineTab%20CE-RED%20Certificate-S20060600403.pdf PineTab CE RED Certificate]
** [https://files.pine64.org/doc/cert/PINETAB%20ROHS%20TEST%20REPORT.pdf PineTab ROHS Test Report]

== Datasheets for components and peripherals ==
* Allwinner A64 SoC information:
** [https://files.pine64.org/doc/datasheet/pine64/A64%20brief%20v1.0%2020150323.pdf Allwinner A64 SoC brief introduction]
** [https://files.pine64.org/doc/datasheet/pine64/A64_Datasheet_V1.1.pdf Allwinner A64 SoC Data Sheet V1.1 (Official Released Version)]
** [https://files.pine64.org/doc/datasheet/pine64/Allwinner_A64_User_Manual_V1.0.pdf Allwinner A64 SoC User Manual V1.0 (Official Release Version)]

* X-Powers AXP803 PMU (Power Management Unit) information:
** [https://files.pine64.org/doc/datasheet/pine64/AXP803_Datasheet_V1.0.pdf AXP803 PMIC datasheet]

* LPDDR3 (178 Balls) SDRAM:
** [https://files.pine64.org/doc/datasheet/pinephone/ATL3A1632H12A_mobile_lpddr3_11x11.5_v1.0_1600.pdf Artmem LPDDR3 datasheet]

* eMMC information:
** [https://files.pine64.org/doc/rock64/PINE64_eMMC_Module_20170719.pdf PINE64 eMMC module schematic]
** [https://files.pine64.org/doc/rock64/usb%20emmc%20module%20adapter%20v2.pdf PINE64 USB adapter for eMMC module V2 schematic]
** [https://files.pine64.org/doc/rock64/USB%20adapter%20for%20eMMC%20module%20PCB.tar PINE64 USB adapter for eMMC module PCB in JPEG]
** [https://files.pine64.org/doc/datasheet/pine64/SDINADF4-16-128GB-H%20data%20sheet%20v1.13.pdf 64GB SanDisk eMMC Datasheet]

* CMOS camera module information:
** [https://files.pine64.org/doc/datasheet/pinephone/OV5640_datasheet.pdf OV5640 5MP CMOS Image Sensor SoC for Rear Module datasheet]
** [https://files.pine64.org/doc/datasheet/pinephone/GC2145%20CSP%20DataSheet%20release%20V1.0_20131201.pdf GC2145 2MP CMOS Image Sensor SoC for Front Module datasheet]

* LCD touch screen panel information:
** [https://files.pine64.org/doc/datasheet/pinetab/GT9271.pdf GOODiX GT9271 Capacitive Touch Controller datasheet]
** [https://files.pine64.org/doc/datasheet/pinetab/GT9271_Config_20200818_142030_V66.cfg PineTab GT9271 Capacitive Touch Controller configuration file]

* Lithium battery information:

* WiFi/BT module information:
** [https://files.pine64.org/doc/datasheet/pine64/RTL8723BS.pdf RTL8723BS/RTL8723CS specification]

== Operating Systems ==
The PineTab will automatically boot from microSD if a bootable card is inserted. Although it is technically possible to use any ARM distro (because the PineTab uses the mainline kernel), only few of them will actually be usable on Early Adopters PineTab, due to specifics of working with LCD panel. Among those listed all except for postmarketOS have working builds.

=== UBPorts ===
[[File:Ubports-logo.png|100px]]
The UBPorts Ubuntu Touch is what preinstalled on PineTab Early Adopters batch.

It can update itself, and also jenkins daily build can be downloaded [https://ci.ubports.com/job/rootfs/job/rootfs-pinetab/ here]

In the event that WiFi fails to connect, the USB port can be used with an appropriate dongle to connect for internet using ethernet cable.

=== postmarketOS ===
[[File:PostmarketOS-logo.png|100px]]
postmarketOS is a preconfigured version of [https://www.alpinelinux.org/ Alpine Linux] for mobile devices.

It offers various user interfaces (Phosh, Plasma Mobile, Sxmo, Plasma Desktop, Gnome 3, Kodi, XFCE4, ...), and allows to encrypt your installation.

As of writing, postmarketOS supports the "pinetab-dev" and the Early Adopters versions of the PineTab.

Refer to the [https://wiki.postmarketos.org/wiki/PINE64_PineTab_(pine64-pinetab) PineTab wiki page] for installation instructions.

=== Arch Linux ARM ===
[[File:Archlinux-logo.png|100px]]
Arch Linux ARM with Phosh as the UI selection, maintained by the DanctNIX community.

The latest image can be downloaded [https://github.com/dreemurrs-embedded/Pine64-Arch/releases here]

=== Manjaro ARM ===
[[File:Manjaro-logo.svg|100px]]
The first Manjaro ARM image confirmed to be working on Early Adopters PineTab can be downloaded [https://next.manjaro.org/index.php/s/aeXDtbWnnBNEM2Q here], ref [https://forum.manjaro.org/t/manjaro-arm-alpha2-with-phosh-pinetab/150/12 forum thread].

Older Manjaro images with several different environments, including Phosh and Plasma, but '''not working on Early Adopters PineTab''' can be downloaded [https://osdn.net/projects/manjaro-arm/storage/pinetab/ here]

=== Mobian ===
[[File:Debian-logo.png|100px]]
Mobian is a project providing Debian images for mobile devices.

PineTab images can be downloaded [https://images.mobian-project.org/pinetab/ here]. Password is '''1234'''

== Installation instructions ==
For instructions on how to install the operating systems to the eMMC or microSD card see [[PinePhone Installation Instructions]]. The information is almost the same for the PineTab, as it is a very similar device. Do not try to use the PinePhone images though, use the PineTab images linked above.

=== Testing ===
To test an OS, just flash its image onto an microSD card, plug it into PineTab, and reboot.
Note that USB stick won't work.
Also note that you need to "flash", not just copy the file onto the card.
Also remember that you need to unpack image file if it's packed!

You can do it using Ubuntu Touch installed on the PineTab! For now, only Mobian is supported by the guide below.

* First, make sure you have enough free disk space and empty Downloads directory on the PineTab (while not strictly necessary, empty Downloads dir will simplify your typing. You can just move all files from there to another directory).
* Turn off Sleep when idle in the settings. Settings > Battery > Sleep when idle: Never
* Go to the Mobian link above and download compressed image (the one ending with .img.gz) - usual recommendation is to download latest, i.e. lowest one.
* Open terminal and type this in it:
cd Downloads
ls
* It should show you the name of the file you've just downloaded
* This file is compressed, so first you need to uncompress it. Type this into terminal:
gunzip *.gz && echo done
* This command will take some time (you won't see any progress until it's done). It either will succeed (and print "done") and fail (and print why).
* Now, let's have a look at disks. Type this into terminal:
lsblk
* It should show you a tree of disks and their partitions. If you don't have microSD card inserted yet, all of them begin with mmcblk2. Also, some of them have something in the "MOUNTPOINT" column
* Insert microSD card into PineTab. Note that all information on it will be deleted, so don't insert one with valuable information on it!
* type `lsblk` into terminal again.
* Note that now tree of disks has one or more new entries - starting with mmcblk0 - that's partitions of your microSD card.
* Confirm that size of mmcblk0 is close to size of the microSD card, and all lines starting with mmcblk0 have empty "MOUNTPOINT" column.
* now type this:
sudo dd if=`ls` of=/dev/mmcblk0 bs=1M status=progress
* It will take some time, depending on speed of your microSD card and size of image file
* Now, reboot your PineTab - type this into terminal:
sudo reboot
* PineTab should boot from the microSD you've just flashed

== Tips and tricks ==

=== Reset ===

If your PineTab is in unknown state or doesn't want to start.
Press power button for 7-8s. It makes a sound and you know it's totally off. 3 seconds after, power button again for 2-3s and it will start to boot. - thanks
@Aperricio on IRC for this hint

=== Display rotated 90° on Arch ARM ===
With the following command you can turn the display to landscape:

* echo 1 | sudo tee /sys/class/graphics/fbcon/rotate

This command does not persist a reboot.

[[Category:PineTab]] [[Category:Allwinner A64]]

Pinebook Pro Hardware Accessory Compatibility

2020-10-07T06:06:37Z

TuxThePenguin: New SD 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 ==
Note that only PCIe type M.2 drives will work. Any SATA or USB type M.2 card will NOT work.
{| class="wikitable sortable"
!Type || Make/Model || Size || Hardware IDs || Result || Notes || Power options Active only || Save power setting?
|-
| 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
|-
| 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] || ||
|-
| 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 || 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 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 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
|}

== 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 64GB (Old model from 2015) || || good but with issues || Works fine but sometimes stops working and needs to be connected to another device to fix it
|-
|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
|}

= USB hardware =

== USB Card Readers ==

Stand-alone card readers only please, see below for combination 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 ==

Stand-alone network devices only please, see below for combination 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/ref=ppx_yo_dt_b_asin_title_o01_s00?ie=UTF8&psc=1
|-
|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/ref=ppx_yo_dt_b_asin_title_o02_s00?ie=UTF8&psc=1
|-
|USB 3 to Gigabit Ethernet Adapter || Pluggable USB 3.0 to Ethernet Gigabit (ASIX AX88179 chipset) || 0b95:1790 || good ||
|-
|}

== USB Combination Devices ==
{| class="wikitable sortable"
!Type || Make/Model || Hardware IDs || Result || Notes
|-
|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/ref=ppx_yo_dt_b_search_asin_title?ie=UTF8&psc=1]
|-
|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/ref=ppx_yo_dt_b_asin_title_o00_s00?ie=UTF8&psc=1 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 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 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/ref=ppx_yo_dt_b_asin_title_o00_s00?ie=UTF8&psc=1 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
|-
|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 || 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
|-
|}

----

= 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.
|-
|}

Pinebook Pro Hardware Accessory Compatibility

2020-09-14T01:30:39Z

TuxThePenguin: Add SD 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 ==
Note that only PCIe type M.2 drives will work. Any SATA or USB type M.2 card will NOT work.
{| class="wikitable sortable"
!Type || Make/Model || Size || Hardware IDs || Result || Notes || Power options Active only || Save power setting?
|-
| 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
|-
| 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] || ||
|-
| 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 || 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.) || ||
|-
| 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 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 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||
|-
| 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
|}

== 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 64GB (Old model from 2015) || || good but with issues || Works fine but sometimes stops working and needs to be connected to another device to fix it
|}

= USB hardware =

== USB Card Readers ==

Stand-alone card readers only please, see below for combination 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 ==

Stand-alone network devices only please, see below for combination 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/ref=ppx_yo_dt_b_asin_title_o01_s00?ie=UTF8&psc=1
|-
|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/ref=ppx_yo_dt_b_asin_title_o02_s00?ie=UTF8&psc=1
|-
|USB 3 to Gigabit Ethernet Adapter || Pluggable USB 3.0 to Ethernet Gigabit (ASIX AX88179 chipset) || 0b95:1790 || good ||
|-
|}

== USB Combination Devices ==
{| class="wikitable sortable"
!Type || Make/Model || Hardware IDs || Result || Notes
|-
|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/ref=ppx_yo_dt_b_search_asin_title?ie=UTF8&psc=1]
|-
|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/ref=ppx_yo_dt_b_asin_title_o00_s00?ie=UTF8&psc=1 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 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 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/ref=ppx_yo_dt_b_asin_title_o00_s00?ie=UTF8&psc=1 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
|-
|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 || 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
|-
|}

----

= 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.
|-
|}

Pinebook Pro Hardware Accessory Compatibility

2020-09-14T01:25:54Z

TuxThePenguin: Update XP Pen G430s notes

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 ==
Note that only PCIe type M.2 drives will work. Any SATA or USB type M.2 card will NOT work.
{| class="wikitable sortable"
!Type || Make/Model || Size || Hardware IDs || Result || Notes || Power options Active only || Save power setting?
|-
| 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
|-
| 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] || ||
|-
| 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 || 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.) || ||
|-
| 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 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 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||
|-
| 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
|}

== 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.
|-
|}

= USB hardware =

== USB Card Readers ==

Stand-alone card readers only please, see below for combination 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 ==

Stand-alone network devices only please, see below for combination 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/ref=ppx_yo_dt_b_asin_title_o01_s00?ie=UTF8&psc=1
|-
|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/ref=ppx_yo_dt_b_asin_title_o02_s00?ie=UTF8&psc=1
|-
|USB 3 to Gigabit Ethernet Adapter || Pluggable USB 3.0 to Ethernet Gigabit (ASIX AX88179 chipset) || 0b95:1790 || good ||
|-
|}

== USB Combination Devices ==
{| class="wikitable sortable"
!Type || Make/Model || Hardware IDs || Result || Notes
|-
|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/ref=ppx_yo_dt_b_search_asin_title?ie=UTF8&psc=1]
|-
|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/ref=ppx_yo_dt_b_asin_title_o00_s00?ie=UTF8&psc=1 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 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 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/ref=ppx_yo_dt_b_asin_title_o00_s00?ie=UTF8&psc=1 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
|-
|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 || 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
|-
|}

----

= 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.
|-
|}

PineTab

2020-09-14T00:55:47Z

TuxThePenguin: Minor details

PAGE UNDER CONSTRUCTION, INFO SUBJECT TO CHANGE

{{warning|1=IMPORTANT INFORMATION for '''Early Adopters''' - please [[PineTab/Early-Adopter|'''CLICK HERE''']] - some '''known issues''' are listed there}}

The PineTab is a 10" tablet created by Pine64.

== Specifications ==
* '''Dimensions:''' 11mm x 175mm x 260mm (Thickness, Width, Height)
* '''Weight:''' 575g (Tablet alone)
* '''Build:''' Plastic
* '''Storage:'''
** 64GB of internal eMMC storage
** MicroSD slot, bootable
** M.2 SSD slot, supports SATA and USB devices only, not NVME (optional)
* '''Cameras:''' 2Mpx Front, 5Mpx Rear
* '''SOC:''' Allwinner A64 Quad Core
* '''CPU:''' 4x ARM A53 1.152GHz
* '''GPU:''' Mali 400 MP2
* '''RAM:''' 2GB LPDDR3
* '''I/O:''' HD Video Out (Mini HDMI), Micro USB 2.0 OTG, USB 2.0 A host, 3.5mm Headphone/Mic combo,
* '''Network'''
** WiFi (802.11b/g/n, 2.4GHz only)
** Bluetooth 2.1
** M.2 LTE / Cell MODEM card, (optional, and takes place of optional M.2 SSD)
* '''Screen:''' 10.1" IPS 800x1280 Capacitive LCD
* '''Attachments/Accessories:''' Magnetically attached keyboard (optional)
* '''Battery:''' 6000MAh (6Ah)
* '''Misc. features:'''
** Volume rocker and home button
** Speakers and Microphone
** 2.5mm OD 0.7mm ID DC Jack Power (5V 2A) Port

== Keyboard ==
'''Overview:''' The PineTab detachable keyboard features a full function row, FN key functionality, meta key (where the Windows key would be) and all of the keys you need for daily use.

'''FN keys:''': Pause/play (F2), Stop (F3), Previous(F4), Next(F5), Music (F6), Mail (F7), Home (F8), Mute (F9), Vol- (F10), Vol+ (F11), Disable touchpad (F12), NumLock (Insert), Scroll Lock (Delete), PgUp (Up Arrow), PgDn (Down Arrow), Home (Left Arrow), End (Right Arrow), Digital Numpad (7,8,9,0,U,I,O,P,J,K,L,;,M,.,/)

==Versions==
For now there is only one version, also mentioned in the manual leaflet in the box.
* [[PineTab/Early-Adopter]]

== PineTab board information, schematics and certifications ==
* PineTab mainboard schematic:
** [http://files.pine64.org/doc/PineTab/PineTab%20Schematic%20v1.2-20191125.pdf PineTab mainboard Released Schematic ver 1.2]
** [http://files.pine64.org/doc/PineTab/PineTab%20Board%20View%20v1.2-20191201-top.pdf PineTab mainboard component placement ver 1.2 - Top View]
** [http://files.pine64.org/doc/PineTab/PineTab%20Board%20View%20v1.2-20191201-bottom.pdf PineTab mainboard component placement ver 1.2 - Bottom View]
* PineTab certifications:
** [http://files.pine64.org/doc/cert/PineTab%20FCC-SDOC%20Certificate-S20060600404001.pdf PineTab FCC Certificate]
** [http://files.pine64.org/doc/cert/PineTab%20CE-RED%20Certificate-S20060600403.pdf PineTab CE RED Certificate]

== Datasheets for components and peripherals ==
* Allwinner A64 SoC information:
** [http://files.pine64.org/doc/datasheet/pine64/A64%20brief%20v1.0%2020150323.pdf Allwinner A64 SoC brief introduction]
** [http://files.pine64.org/doc/datasheet/pine64/A64_Datasheet_V1.1.pdf Allwinner A64 SoC Data Sheet V1.1 (Official Released Version)]
** [http://files.pine64.org/doc/datasheet/pine64/Allwinner_A64_User_Manual_V1.0.pdf Allwinner A64 SoC User Manual V1.0 (Official Release Version)]

* X-Powers AXP803 PMU (Power Management Unit) information:
** [http://files.pine64.org/doc/datasheet/pine64/AXP803_Datasheet_V1.0.pdf AXP803 PMIC datasheet]

* LPDDR3 (178 Balls) SDRAM:
** [http://files.pine64.org/doc/datasheet/pinephone/ATL3A1632H12A_mobile_lpddr3_11x11.5_v1.0_1600.pdf Artmem LPDDR3 datasheet]

* eMMC information:
** [http://files.pine64.org/doc/rock64/PINE64_eMMC_Module_20170719.pdf PINE64 eMMC module schematic]
** [http://files.pine64.org/doc/rock64/usb%20emmc%20module%20adapter%20v2.pdf PINE64 USB adapter for eMMC module V2 schematic]
** [http://files.pine64.org/doc/rock64/USB%20adapter%20for%20eMMC%20module%20PCB.tar PINE64 USB adapter for eMMC module PCB in JPEG]
** [http://files.pine64.org/doc/datasheet/pine64/SDINADF4-16-128GB-H%20data%20sheet%20v1.13.pdf SanDisk eMMC Datasheet]

* CMOS camera module information:
** [http://files.pine64.org/doc/datasheet/pinephone/OV5640_datasheet.pdf OV5640 5MP CMOS Image Sensor SoC for Rear Module datasheet]
** [http://files.pine64.org/doc/datasheet/pinephone/GC2145%20CSP%20DataSheet%20release%20V1.0_20131201.pdf GC2145 2MP CMOS Image Sensor SoC for Front Module datasheet]

* LCD touch screen panel information:
** [http://files.pine64.org/doc/datasheet/pinetab/GT9271.pdf GOODiX GT9271 Capacitive Touch Controller datasheet]
** [http://files.pine64.org/doc/datasheet/pinetab/GT9271_Config_20200818_142030_V66.cfg PineTab GT9271 Capacitive Touch Controller configuration file]

* Lithium battery information:

* WiFi/BT module information:
** [http://files.pine64.org/doc/datasheet/pine64/RTL8723BS.pdf RTL8723BS/RTL8723CS specification]

== Operating Systems ==
The PineTab will automatically boot from microSD if a bootable card is inserted. Although it is technically possible to use any ARM distro (because the PineTab uses the mainline kernel), only few of them will actually be usable on Early Adopters PineTab, due to specifics of working with LCD panel. Among those listed below only [[#UBPorts|UBPorts]], [[#Mobian|Mobian]], and [[#Arch Linux ARM|Arch Linux ARM]] are confirmed to be working.

* [[#UBPorts|UBPorts]]
* [[#postmarketOS|postmarketOS]]
* [[#Arch Linux ARM|Arch Linux ARM]]
* [[#Manjaro ARM|Manjaro ARM]]
* [[#Mobian|Mobian]]

=== UBPorts ===
The UBPorts Ubuntu Touch is what preinstalled on PineTab Early Adopters batch. It can update itself, and also jenkins daily build can be downloaded [https://ci.ubports.com/job/rootfs/job/rootfs-pinetab/ here]

=== postmarketOS ===
postmarketOS is a preconfigured version of [https://www.alpinelinux.org/ Alpine Linux] for mobile devices. The latest builds can be downloaded from the [https://images.postmarketos.org/pinetab/ images page] to be flashed to the PineTab.

More information is available at [https://postmarketos.org postmarketos.org] and on their [https://wiki.postmarketos.org/wiki/PINE64_PineTab_(pine64-pinetab) dedicated PineTab wiki page].

=== Arch Linux ARM ===
Arch Linux ARM with Phosh as the UI selection, maintained by the DanctNIX community.

The latest test image can be downloaded [https://github.com/dreemurrs-embedded/Pine64-Arch/releases/tag/20200910pre here]

=== Manjaro ARM ===
Manjaro ARM with several different environments, including Phosh and Plasma, can be downloaded [https://osdn.net/projects/manjaro-arm/storage/pinetab/ here]

=== Mobian ===
Mobian is a project providing Debian images for mobile devices. PineTab images can be downloaded [https://images.mobian-project.org/pinetab/ here]. Password is '''1234'''

=== Testing ===
To test an OS, just flash its image onto an microSD card, plug it into PineTab, and reboot.
Note that USB stick won't work.
Also note that you need to "flash", not just copy the file onto the card.
Also remember that you need to unpack image file if it's packed!

You can do it using Ubuntu Touch installed on the PineTab! For now, only Mobian is supported by the guide below.

* First, make sure you have enough free disk space and empty Downloads directory on the PineTab (while not strictly necessary, empty Downloads dir will simplify your typing. You can just move all files from there to another directory).
* go to the Mobian link above and download compressed image (the one ending with .img.gz) - usual recommendation is to download latest, i.e. lowest one.
* Open terminal and type this in it:
cd Downloads
ls
* It should show you the name of the file you've just downloaded
* This file is compressed, so first you need to uncompress it. Type this into terminal:
gunzip *.gz && echo done
* This command will take some time (you won't see any progress until it's done). It either will succeed (and print "done") and fail (and print why).
* Now, let's have a look at disks. Type this into terminal:
lsblk
* It should show you a tree of disks and their partitions. If you don't have microCD card inserted yet, all of them begin with mmcblk2. Also, some of them have something in the "MOUNTPOINT" column
* Insert microSD card into PineTab. Note that all information on it will be deleted, so don't insert one with valuable information on it!
* type `lsblk` into terminal again.
* Note that now tree of disks has one or more new entries - starting with mmcblk0 - that's partitions of your microSD card.
* Confirm that size of mmcblk0 is close to size of the microSD card, and all lines starting with mmcblk0 have empty "MOUNTPOINT" column.
* now type this:
sudo dd if=`ls` of=/dev/mmcblk0 bs=1M status=progress
* It will take some time, depending on speed of your microSD card and size of image file
* Now, reboot your PineTab - type this into terminal:
sudo reboot
* PineTab should boot from the microSD you've just flashed

== Tips and tricks ==

=== Reset ===

If your PineTab is in unknown state or doesn't want to start.
Press power button for 7-8s. It makes a sound and you know it's totally off. 3 seconds after, power button again for 2-3s and it will start to boot. - thanks
@Aperricio on IRC for this hint

PineTab

2020-09-14T00:43:44Z

TuxThePenguin: Minor details

PAGE UNDER CONSTRUCTION, INFO SUBJECT TO CHANGE

{{warning|1=IMPORTANT INFORMATION for '''Early Adopters''' - please [[PineTab/Early-Adopter|'''CLICK HERE''']] - some '''known issues''' are listed there}}

The PineTab is a 10" tablet created by Pine64.

== Specifications ==
* '''Dimensions:''' 11mm x 175mm x 260mm (Thickness, Width, Height)
* '''Weight:''' 575g (Tablet alone)
* '''Build:''' Plastic
* '''Storage:'''
** 64GB of internal eMMC storage
** MicroSD slot, bootable
** M.2 SSD slot, supports SATA and USB devices only, not NVME (optional)
* '''Cameras:''' 2Mpx Front, 5Mpx Rear
* '''CPU:''' Allwinner A64 Quad Core
* '''GPU:''' Mali 400 MP2
* '''RAM:''' 2GB LPDDR3
* '''I/O:''' HD Video Out (Mini HDMI), Micro USB 2.0 OTG, USB 2.0 A host, 3.5mm Headphone/Mic combo,
* '''Network'''
** WiFi (802.11b/g/n, 2.4GHz only)
** M.2 LTE / Cell MODEM card, (optional, and takes place of optional M.2 SSD)
* '''Screen:''' 10.1" IPS 800x1280 Capacitive LCD
* '''Attachments/Accessories:''' Magnetically attached keyboard (optional)
* '''Battery:''' 6000MAh (6Ah)
* '''Misc. features:'''
** Volume rocker and home button
** Speakers and Microphone
** 2.5mm OD 0.7mm ID DC Jack Power (5V 2A) Port

== Keyboard ==
'''Overview:''' The PineTab detachable keyboard features a full function row, FN key functionality, meta key (where the Windows key would be) and all of the keys you need for daily use.

'''FN keys:''': Pause/play (F2), Stop (F3), Previous(F4), Next(F5), Music (F6), Mail (F7), Home (F8), Mute (F9), Vol- (F10), Vol+ (F11), Disable touchpad (F12), NumLock (Insert), Scroll Lock (Delete), PgUp (Up Arrow), PgDn (Down Arrow), Home (Left Arrow), End (Right Arrow), Digital Numpad (7,8,9,0,U,I,O,P,J,K,L,;,M,.,/)

==Versions==
For now there is only one version, also mentioned in the manual leaflet in the box.
* [[PineTab/Early-Adopter]]

== PineTab board information, schematics and certifications ==
* PineTab mainboard schematic:
** [http://files.pine64.org/doc/PineTab/PineTab%20Schematic%20v1.2-20191125.pdf PineTab mainboard Released Schematic ver 1.2]
** [http://files.pine64.org/doc/PineTab/PineTab%20Board%20View%20v1.2-20191201-top.pdf PineTab mainboard component placement ver 1.2 - Top View]
** [http://files.pine64.org/doc/PineTab/PineTab%20Board%20View%20v1.2-20191201-bottom.pdf PineTab mainboard component placement ver 1.2 - Bottom View]
* PineTab certifications:
** [http://files.pine64.org/doc/cert/PineTab%20FCC-SDOC%20Certificate-S20060600404001.pdf PineTab FCC Certificate]
** [http://files.pine64.org/doc/cert/PineTab%20CE-RED%20Certificate-S20060600403.pdf PineTab CE RED Certificate]

== Datasheets for components and peripherals ==
* Allwinner A64 SoC information:
** [http://files.pine64.org/doc/datasheet/pine64/A64%20brief%20v1.0%2020150323.pdf Allwinner A64 SoC brief introduction]
** [http://files.pine64.org/doc/datasheet/pine64/A64_Datasheet_V1.1.pdf Allwinner A64 SoC Data Sheet V1.1 (Official Released Version)]
** [http://files.pine64.org/doc/datasheet/pine64/Allwinner_A64_User_Manual_V1.0.pdf Allwinner A64 SoC User Manual V1.0 (Official Release Version)]

* X-Powers AXP803 PMU (Power Management Unit) information:
** [http://files.pine64.org/doc/datasheet/pine64/AXP803_Datasheet_V1.0.pdf AXP803 PMIC datasheet]

* LPDDR3 (178 Balls) SDRAM:
** [http://files.pine64.org/doc/datasheet/pinephone/ATL3A1632H12A_mobile_lpddr3_11x11.5_v1.0_1600.pdf Artmem LPDDR3 datasheet]

* eMMC information:
** [http://files.pine64.org/doc/rock64/PINE64_eMMC_Module_20170719.pdf PINE64 eMMC module schematic]
** [http://files.pine64.org/doc/rock64/usb%20emmc%20module%20adapter%20v2.pdf PINE64 USB adapter for eMMC module V2 schematic]
** [http://files.pine64.org/doc/rock64/USB%20adapter%20for%20eMMC%20module%20PCB.tar PINE64 USB adapter for eMMC module PCB in JPEG]
** [http://files.pine64.org/doc/datasheet/pine64/SDINADF4-16-128GB-H%20data%20sheet%20v1.13.pdf SanDisk eMMC Datasheet]

* CMOS camera module information:
** [http://files.pine64.org/doc/datasheet/pinephone/OV5640_datasheet.pdf OV5640 5MP CMOS Image Sensor SoC for Rear Module datasheet]
** [http://files.pine64.org/doc/datasheet/pinephone/GC2145%20CSP%20DataSheet%20release%20V1.0_20131201.pdf GC2145 2MP CMOS Image Sensor SoC for Front Module datasheet]

* LCD touch screen panel information:
** [http://files.pine64.org/doc/datasheet/pinetab/GT9271.pdf GOODiX GT9271 Capacitive Touch Controller datasheet]
** [http://files.pine64.org/doc/datasheet/pinetab/GT9271_Config_20200818_142030_V66.cfg PineTab GT9271 Capacitive Touch Controller configuration file]

* Lithium battery information:

* WiFi/BT module information:
** [http://files.pine64.org/doc/datasheet/pine64/RTL8723BS.pdf RTL8723BS/RTL8723CS specification]

== Operating Systems ==
The PineTab will automatically boot from microSD if a bootable card is inserted. Although it is technically possible to use any ARM distro (because the PineTab uses the mainline kernel), only few of them will actually be usable on Early Adopters PineTab, due to specifics of working with LCD panel. Among those listed below only [[#UBPorts|UBPorts]], [[#Mobian|Mobian]], and [[#Arch Linux ARM|Arch Linux ARM]] are confirmed to be working.

* [[#UBPorts|UBPorts]]
* [[#postmarketOS|postmarketOS]]
* [[#Arch Linux ARM|Arch Linux ARM]]
* [[#Manjaro ARM|Manjaro ARM]]
* [[#Mobian|Mobian]]

=== UBPorts ===
The UBPorts Ubuntu Touch is what preinstalled on PineTab Early Adopters batch. It can update itself, and also jenkins daily build can be downloaded [https://ci.ubports.com/job/rootfs/job/rootfs-pinetab/ here]

=== postmarketOS ===
postmarketOS is a preconfigured version of [https://www.alpinelinux.org/ Alpine Linux] for mobile devices. The latest builds can be downloaded from the [https://images.postmarketos.org/pinetab/ images page] to be flashed to the PineTab.

More information is available at [https://postmarketos.org postmarketos.org] and on their [https://wiki.postmarketos.org/wiki/PINE64_PineTab_(pine64-pinetab) dedicated PineTab wiki page].

=== Arch Linux ARM ===
Arch Linux ARM with Phosh as the UI selection, maintained by the DanctNIX community.

The latest test image can be downloaded [https://github.com/dreemurrs-embedded/Pine64-Arch/releases/tag/20200910pre here]

=== Manjaro ARM ===
Manjaro ARM with several different environments, including Phosh and Plasma, can be downloaded [https://osdn.net/projects/manjaro-arm/storage/pinetab/ here]

=== Mobian ===
Mobian is a project providing Debian images for mobile devices. PineTab images can be downloaded [https://images.mobian-project.org/pinetab/ here]. Password is '''1234'''

=== Testing ===
To test an OS, just flash its image onto an microSD card, plug it into PineTab, and reboot.
Note that USB stick won't work.
Also note that you need to "flash", not just copy the file onto the card.
Also remember that you need to unpack image file if it's packed!

You can do it using Ubuntu Touch installed on the PineTab! For now, only Mobian is supported by the guide below.

* First, make sure you have enough free disk space and empty Downloads directory on the PineTab (while not strictly necessary, empty Downloads dir will simplify your typing. You can just move all files from there to another directory).
* go to the Mobian link above and download compressed image (the one ending with .img.gz) - usual recommendation is to download latest, i.e. lowest one.
* Open terminal and type this in it:
cd Downloads
ls
* It should show you the name of the file you've just downloaded
* This file is compressed, so first you need to uncompress it. Type this into terminal:
gunzip *.gz && echo done
* This command will take some time (you won't see any progress until it's done). It either will succeed (and print "done") and fail (and print why).
* Now, let's have a look at disks. Type this into terminal:
lsblk
* It should show you a tree of disks and their partitions. If you don't have microCD card inserted yet, all of them begin with mmcblk2. Also, some of them have something in the "MOUNTPOINT" column
* Insert microSD card into PineTab. Note that all information on it will be deleted, so don't insert one with valuable information on it!
* type `lsblk` into terminal again.
* Note that now tree of disks has one or more new entries - starting with mmcblk0 - that's partitions of your microSD card.
* Confirm that size of mmcblk0 is close to size of the microSD card, and all lines starting with mmcblk0 have empty "MOUNTPOINT" column.
* now type this:
sudo dd if=`ls` of=/dev/mmcblk0 bs=1M status=progress
* It will take some time, depending on speed of your microSD card and size of image file
* Now, reboot your PineTab - type this into terminal:
sudo reboot
* PineTab should boot from the microSD you've just flashed

== Tips and tricks ==

=== Reset ===

If your PineTab is in unknown state or doesn't want to start.
Press power button for 7-8s. It makes a sound and you know it's totally off. 3 seconds after, power button again for 2-3s and it will start to boot. - thanks
@Aperricio on IRC for this hint

Overclocking

2020-07-14T08:09:38Z

TuxThePenguin: Adjustments for ease of reading

{{warning|1=This might damage your equipment or may result in a unstable system, so do this at your own risk!}}
{{hint|This page is incomplete, you're welcome to improve it.}}
{{hint|All information regarding clock speeds, voltages and more are stored in the DTB (Device Tree Blob). You can learn more about it [https://elinux.org/Device_Tree_Reference here].}}

Overclocking is a way to get more performance out of the system by running it at higher clock speeds than the factory default.

= Preparation =
TODO, requires a compatible cross compiler (usually aarch64-linux-gnu), and clone the pine64 kernel repository.

Then after that just setup the variables for make.

In the future there will likely be a driver to adjust clockspeeds from userspace without the need to recompile.

= A64-based boards =
== GPU ==
Open <code>arch/arm64/boot/dts/allwinner/sun50i-a64.dtsi</code> in a text editor.

Look for

<nowiki>
mali: gpu@1c40000 {
compatible = "allwinner,sun50i-a64-mali", "arm,mali-400";
reg = <0x01c40000 0x10000>;
interrupts = <GIC_SPI 97 IRQ_TYPE_LEVEL_HIGH>,
<GIC_SPI 98 IRQ_TYPE_LEVEL_HIGH>,
<GIC_SPI 99 IRQ_TYPE_LEVEL_HIGH>,
<GIC_SPI 100 IRQ_TYPE_LEVEL_HIGH>,
<GIC_SPI 102 IRQ_TYPE_LEVEL_HIGH>,
<GIC_SPI 103 IRQ_TYPE_LEVEL_HIGH>,
<GIC_SPI 101 IRQ_TYPE_LEVEL_HIGH>;
interrupt-names = "gp",
"gpmmu",
"pp0",
"ppmmu0",
"pp1",
"ppmmu1",
"pmu";
clocks = <&ccu CLK_BUS_GPU>, <&ccu CLK_GPU>;
clock-names = "bus", "core";
resets = <&ccu RST_BUS_GPU>;

assigned-clocks = <&ccu CLK_GPU>;
assigned-clock-rates = <432000000>;
};
</nowiki>

The <code>assigned-clock-rates</code> line is set to <code>432000000</code>, this means that the GPU is clocked at 432MHz. So if you want 500MHz, set the value to <code>500000000</code>.

Save the dtsi file, and recompile the DTB.

The GPU appears to run stable overclocked to 560 Mhz, however more testing with a wider group of devices is needed.

{{note|Remember to run a benchmark tool (such as glmark2-es2) to help check stability.}}

== CPU ==

Stock speed: 1.152GHz CPU

== DRAM ==

{{warning|1=It is not recommended to exceed 667 MHz clockspeed on the DRAM.}}

When overclocking the GPU, it is a good idea to also overclock the DRAM, as the main bottleneck of the A64 SOC is the memory.

The A64's maximum ram clockspeed falls just short of 667MHz. This may be unstable on your device however. Around 600 MHz (PC-1200) should work fine. (Some people have reported instability at lower clockspeeds, however it's not clear if the overclock was at fault)

= Rockchip RK3399 based boards =
The RK3399 clocks are found in <code>arch/arm64/boot/dts/rockchip/rk3399-opp.dtsi</code>

More optimised voltages and clocks can be found in <code>arch/arm64/boot/dts/rockchip/rk3399-op1-opp.dtsi</code>
These include a slight overclock and undervolt, they are intended for the OP1 CPU found in many chromebooks but have worked fine in all recorded cases on regular RK3399s in other devices.

Specific to the Pinebook Pro DTS in tsys' kernels is an extra clock speed entry for the big cores in <code>arch/arm64/boot/dts/rockchip/rk3399-pinebook-pro.dts</code> 
It overrides the <code>opp08</code> entry for the big core cluster with one that runs 2GHz at 1.3V. 
It is up to you how to deal with this, either by just skipping opp08 in the main dtsi to keep using that entry or by removing that entry from the Pinebook Pro dts and adding your own to the regular dtsi.

==GPU==
Any clock speeds can be added for the GPU in <code>gpu_opp_table</code>

The highest safe voltage for the GPU is 1.2V as specified in the RK3399 schematic from Rockchip.

TuxThePenguin has found that the RK3399 in his Pinebook Pro can reach 950MHz on the GPU while being stable.

The stock speed for the GPU is 800Mhz

==CPU==
A set of available clock speeds that can be added to the CPU clusters can be found in <code>drivers/clk/rockchip/clk-rk3399.c</code> under <code>rk3399_cpuclkl_rates</code> for the little cores and <code>rk3399_cpuclkb_rates</code> for the big cores.

These clock speeds can be added to <code>cluster0_opp</code> for the small cores and <code>cluster1_opp</code> for the big cores respectively.

There is a hard limit of 1.8GHz on the little cores and 2.2GHz on the big cores.

The highest safe voltage for the little cores is 1.2V and for the big cores is 1.25V.

TuxThePenguin has found that the little cores on his RK3399 can run at 1.6GHz, and 2.08GHz on the big cores.

==DRAM==
TODO

= Rockchip RK3328 based boards =
TODO

User:TuxThePenguin

2020-07-14T08:04:39Z

TuxThePenguin: Update my device list

Just another community member

I have:
* Thinkpad W540 running Arch
* Pinebook Pro ANSI running Arch
* 3 2012 Nexus 7s running various OSes
* Switch Lite (yet to be hacked)
* Samsung Galaxy S5 running Ubuntu Touch
* Samsung Galaxy Ace 3 running Ubuntu Touch
* ZTE Axon 7 running LineageOS
* And some other non-Linux devices that are really boring

Ask me about why an eGPU won't work with the RK3399 :)

Or about how to overclock the RK3399 I guess

Overclocking

2020-06-05T06:45:33Z

TuxThePenguin: Add information about preexisting Pinebook Pro override

{{note|This might damage your equipment or may result in a unstable system, so do this at your own risk!}}
{{hint|This page is incomplete, you're welcome to improve it.}}
{{hint|All information regarding clock speeds, voltages and more are stored in the DTB (Device Tree Blob). You can learn more about it [https://elinux.org/Device_Tree_Reference here].}}

Overclocking is a way to get more performance out of the system by running it at higher clock speeds than the factory default.

= Preparation =
TODO, requires a compatible cross compiler (usually aarch64-linux-gnu), and clone the pine64 kernel repository.

Then after that just setup the variables for make.

In the future there will likely be a driver to adjust clockspeeds from userspace without the need to recompile.

= A64-based boards =
== GPU ==
Open <code>arch/arm64/boot/dts/allwinner/sun50i-a64.dtsi</code> in a text editor.

Look for

<nowiki>
mali: gpu@1c40000 {
compatible = "allwinner,sun50i-a64-mali", "arm,mali-400";
reg = <0x01c40000 0x10000>;
interrupts = <GIC_SPI 97 IRQ_TYPE_LEVEL_HIGH>,
<GIC_SPI 98 IRQ_TYPE_LEVEL_HIGH>,
<GIC_SPI 99 IRQ_TYPE_LEVEL_HIGH>,
<GIC_SPI 100 IRQ_TYPE_LEVEL_HIGH>,
<GIC_SPI 102 IRQ_TYPE_LEVEL_HIGH>,
<GIC_SPI 103 IRQ_TYPE_LEVEL_HIGH>,
<GIC_SPI 101 IRQ_TYPE_LEVEL_HIGH>;
interrupt-names = "gp",
"gpmmu",
"pp0",
"ppmmu0",
"pp1",
"ppmmu1",
"pmu";
clocks = <&ccu CLK_BUS_GPU>, <&ccu CLK_GPU>;
clock-names = "bus", "core";
resets = <&ccu RST_BUS_GPU>;

assigned-clocks = <&ccu CLK_GPU>;
assigned-clock-rates = <432000000>;
};
</nowiki>

The <code>assigned-clock-rates</code> line is set to <code>432000000</code>, this means that the GPU is clocked at 432MHz. So if you want 500MHz, set the value to <code>500000000</code>.

Save the dtsi file, and recompile the DTB.

The GPU appears to run stable overclocked to 560 Mhz, however more testing with a wider group of devices is needed.

{{note|Remember to run a benchmark tool (such as glmark2-es2) to help check stability.}}

== CPU ==

Stock speed: 1.152GHz CPU

== DRAM ==

{{note|It is not recommended to exceed 672 MHz clockspeed on the DRAM.}}

When overclocking the GPU, it is a good idea to also overclock the DRAM, as the main bottleneck of the A64 SOC is the memory.

Ideal overclock is 666 Mhz. This may be unstable on your device however. (Some people have reported instability at lower clockspeeds, however it's not clear if the overclock was at fault)

= Rockchip RK3399 based boards =
The RK3399 clocks are found in <code>arch/arm64/boot/dts/rockchip/rk3399-opp.dtsi</code>

More optimised voltages and clocks can be found in <code>arch/arm64/boot/dts/rockchip/rk3399-op1-opp.dtsi</code>
These include a slight overclock and undervolt, they are intended for the OP1 CPU found in many chromebooks but have worked fine in all recorded cases on regular RK3399s in other devices.

Specific to the Pinebook Pro DTS in some kernels is an extra clock speed entry for the big cores in <code>arch/arm64/boot/dts/rockchip/rk3399-pinebook-pro.dts</code>
It overrides the <code>opp08</code> entry for the big core cluster with one that runs 2GHz at 1.3V, it is up to you how to deal with this, either by just skipping opp08 in the main dtsi to keep using that entry or by removing that entry from the Pinebook Pro dts and adding your own to the regular dtsi.

==GPU==
Any clock speeds can be added for the GPU in <code>gpu_opp_table</code>

The highest safe voltage for the GPU is 1.2V as specified in the RK3399 schematic from Rockchip.

TuxThePenguin has found that the RK3399 in his Pinebook Pro can reach 950MHz on the GPU while being stable.

The stock speed for the GPU is 800Mhz

==CPU==
A set of available clock speeds that can be added to the CPU clusters can be found in <code>drivers/clk/rockchip/clk-rk3399.c</code> under <code>rk3399_cpuclkl_rates</code> for the little cores and <code>rk3399_cpuclkb_rates</code> for the big cores.

These clock speeds can be added to <code>cluster0_opp</code> for the small cores and <code>cluster1_opp</code> for the big cores respectively.

There is a hard limit of 1.8GHz on the little cores and 2.2GHz on the big cores.

The highest safe voltage for the little cores is 1.2V and for the big cores is 1.25V.

TuxThePenguin has found that the little cores on his RK3399 can run at 1.6GHz, and 2.08GHz on the big cores.

==DRAM==
TODO

= Rockchip RK3328 based boards =
TODO

Overclocking

2020-05-28T00:02:17Z

TuxThePenguin: Some known overclocks

{{note|This might damage your equipment or may result in a unstable system, so do this at your own risk!}}
{{note|This page is incomplete, you're welcome to improve it.}}
{{note|Overclocked devices may seem stable but crash occasionally and be hard to debug. A good test suite needs to be found to properly test the entire functionality of overclocked devices to properly ensure stability}}
{{note|Keep a backup bootable OS which is known to be stable, if an overclock fails you may not be able to boot the system without another OS }}
{{hint|All information regarding clock speeds, voltages and more are stored in the DTB (Device Tree Blob). You can learn more about it [https://elinux.org/Device_Tree_Reference here].}}

Overclocking is a way to get more and better performance out of the system by running it at higher clock speeds than the factory default.

= Preparation =
TODO, requires a compatible cross compiler (usually aarch64-linux-gnu), and clone the pine64 kernel repository.

Then after that just setup the variables for make.

= A64-based boards =
== GPU ==
Open <code>arch/arm64/boot/dts/allwinner/sun50i-a64.dtsi</code> in a text editor.

Look for

<nowiki>
mali: gpu@1c40000 {
compatible = "allwinner,sun50i-a64-mali", "arm,mali-400";
reg = <0x01c40000 0x10000>;
interrupts = <GIC_SPI 97 IRQ_TYPE_LEVEL_HIGH>,
<GIC_SPI 98 IRQ_TYPE_LEVEL_HIGH>,
<GIC_SPI 99 IRQ_TYPE_LEVEL_HIGH>,
<GIC_SPI 100 IRQ_TYPE_LEVEL_HIGH>,
<GIC_SPI 102 IRQ_TYPE_LEVEL_HIGH>,
<GIC_SPI 103 IRQ_TYPE_LEVEL_HIGH>,
<GIC_SPI 101 IRQ_TYPE_LEVEL_HIGH>;
interrupt-names = "gp",
"gpmmu",
"pp0",
"ppmmu0",
"pp1",
"ppmmu1",
"pmu";
clocks = <&ccu CLK_BUS_GPU>, <&ccu CLK_GPU>;
clock-names = "bus", "core";
resets = <&ccu RST_BUS_GPU>;

assigned-clocks = <&ccu CLK_GPU>;
assigned-clock-rates = <432000000>;
};
</nowiki>

The <code>assigned-clock-rates</code> line is set to <code>432000000</code>, this means that the GPU is clocked at 432MHz. So if you want 500MHz, set the value to <code>500000000</code>.

Save the dtsi file, and recompile the DTB.

{{note|Danct12 has found on his Pinetab that 562 MHz is the limit for stable operation.}}
{{note|Remember to run a benchmark tool (such as glmark2-es2) to make sure that it's stable! If it's not, then lower the clock speed until you can get a stable clock speed.}}

== CPU ==
TODO

== DRAM ==

{{note|It is not recommended to exceed 672 MHz clockspeed on the DRAM.}}

When overclocking the GPU, it is a good idea to also overclock the DRAM, as the main bottleneck of the A64 SOC is the memory.

= Rockchip RK3399 based boards =
The RK3399 clocks are found in <code>arch/arm64/boot/dts/rockchip/rk3399-opp.dtsi</code>

More optimised voltages and clocks can be found in <code>arch/arm64/boot/dts/rockchip/rk3399-op1-opp.dtsi</code>
These include a slight overclock and undervolt, they are intended for the OP1 CPU found in many chromebooks but have worked fine in all recorded cases on regular RK3399s in other devices.

==GPU==
Any clock speeds can be added for the GPU in <code>gpu_opp_table</code>

The highest safe voltage for the GPU is 1.2V as specified in the RK3399 schematic from Rockchip.
{{note|TuxThePenguin has found that the RK3399 in his Pinebook Pro can reach 950MHz on the GPU while being stable, 1GHz was tried but crashed instantly.}}

==CPU==
A set of available clock speeds that can be added to the CPU clusters can be found in <code>drivers/clk/rockchip/clk-rk3399.c</code> under <code>rk3399_cpuclkl_rates</code> for the little cores and <code>rk3399_cpuclkb_rates</code> for the big cores.

These clock speeds can be added to <code>cluster0_opp</code> for the small cores and <code>cluster1_opp</code> for the big cores respectively.

Any of the clock speeds listed in this file can be added but no others will work, this means there is a hard limit of 1.8GHz on the little cores and 2.2GHz on the big cores.

The highest safe voltage for the little cores is 1.2V and for the big cores is 1.25V.
{{note|TuxThePenguin has found that the little cores on his RK3399 would run at 1.7GHz and the big cores would run at 2.1GHz, however a crash was encountered at this frequency so speeds were stepped back to 1.6GHz on the little cores and 2.08GHz on the big cores, make sure to thoroughly check for stability!}}

==DRAM==
TODO

= Rockchip RK3328 based boards =
TODO

= Recorded Overclocks =
==A64==
Stock: 1.152GHz CPU, 432MHz GPU

Danct12: 562MHz GPU

==RK3399==
Stock: 1.4GHz little CPU, 1.8GHz big CPU, 800MHz GPU

TuxThePenguin: 1.6GHz little CPU, 2.08GHz big CPU, 950MHz GPU

User:TuxThePenguin

2020-05-27T23:57:24Z

TuxThePenguin:

Just another community member

I have:
* Thinkpad W540 running Arch
* Pinebook Pro ANSI running Arch
* 3 2012 Nexus 7s running Ubuntu, pmOS and Android
* Switch Lite (yet to be hacked)
* Samsung Galaxy S5 running LineageOS
* ZTE Axon 7 running Ubuntu Touch
* And some other non-Linux devices that are really boring

Ask me about why an eGPU won't work with the RK3399 :)

Or about how to overclock the RK3399 I guess

Overclocking

2020-05-27T23:55:28Z

TuxThePenguin:

Overclocking

2020-05-27T23:50:44Z

TuxThePenguin: Fixed layout

{{note|This might damage your equipment or may result in a unstable system, so do this at your own risk!}}
{{note|This page is incomplete, you're welcome to improve it.}}
{{note|Overclocked devices may seem stable but crash occasionally and be hard to debug. A good test suite needs to be found to properly test the entire functionality of overclocked devices to properly ensure stability}}
{{note|Keep a backup bootable OS which is known to be stable, if an overclock fails you may not be able to boot the system without another OS }}
{{hint|All information regarding clock speeds, voltages and more are stored in the DTB (Device Tree Blob). You can learn more about it [https://elinux.org/Device_Tree_Reference here].}}

Overclocking is a way to get more and better performance out of the system by running it at higher clock speeds than the factory default.

= Preparation =
TODO, requires a compatible cross compiler (usually aarch64-linux-gnu), and clone the pine64 kernel repository.

Then after that just setup the variables for make.

= A64-based boards =
== GPU ==
Open <code>arch/arm64/boot/dts/allwinner/sun50i-a64.dtsi</code> in a text editor.

Look for

<nowiki>
mali: gpu@1c40000 {
compatible = "allwinner,sun50i-a64-mali", "arm,mali-400";
reg = <0x01c40000 0x10000>;
interrupts = <GIC_SPI 97 IRQ_TYPE_LEVEL_HIGH>,
<GIC_SPI 98 IRQ_TYPE_LEVEL_HIGH>,
<GIC_SPI 99 IRQ_TYPE_LEVEL_HIGH>,
<GIC_SPI 100 IRQ_TYPE_LEVEL_HIGH>,
<GIC_SPI 102 IRQ_TYPE_LEVEL_HIGH>,
<GIC_SPI 103 IRQ_TYPE_LEVEL_HIGH>,
<GIC_SPI 101 IRQ_TYPE_LEVEL_HIGH>;
interrupt-names = "gp",
"gpmmu",
"pp0",
"ppmmu0",
"pp1",
"ppmmu1",
"pmu";
clocks = <&ccu CLK_BUS_GPU>, <&ccu CLK_GPU>;
clock-names = "bus", "core";
resets = <&ccu RST_BUS_GPU>;

assigned-clocks = <&ccu CLK_GPU>;
assigned-clock-rates = <432000000>;
};
</nowiki>

The <code>assigned-clock-rates</code> line is set to <code>432000000</code>, this means that the GPU is clocked at 432MHz. So if you want 500MHz, set the value to <code>500000000</code>.

Save the dtsi file, and recompile the DTB.

{{note|Danct12 has found on his Pinetab that 562 MHz is the limit for stable operation.}}
{{note|Remember to run a benchmark tool (such as glmark2-es2) to make sure that it's stable! If it's not, then lower the clock speed until you can get a stable clock speed.}}

== CPU ==
TODO

== DRAM ==

{{note|It is not recommended to exceed 672 MHz clockspeed on the DRAM.}}

When overclocking the GPU, it is a good idea to also overclock the DRAM, as the main bottleneck of the A64 SOC is the memory.

= Rockchip RK3399 based boards =
The RK3399 clocks are found in <code>arch/arm64/boot/dts/rockchip/rk3399-opp.dtsi</code>

More optimised voltages and clocks can be found in <code>arch/arm64/boot/dts/rockchip/rk3399-op1-opp.dtsi</code>
These include a slight overclock and undervolt, they are intended for the OP1 CPU found in many chromebooks but have worked fine in all recorded cases on regular RK3399s in other devices.

==GPU==
Any clock speeds can be added for the GPU in <code>gpu_opp_table</code>

The highest safe voltage for the GPU is 1.2V as specified in the RK3399 schematic from Rockchip.
{{note|TuxThePenguin has found that the RK3399 in his Pinebook Pro can reach 950MHz on the GPU while being stable, 1GHz was tried but crashed instantly.}}

==CPU==
A set of available clock speeds that can be added to the CPU clusters can be found in [need to find file], these clock speeds can be added to <code>cluster0_opp</code> for the small cores and <code>cluster1_opp</code> for the big cores respectively.

Any of the clock speeds listed in this file can be added but no others will work, this means there is a hard limit of 1.8GHz on the little cores and 2.2GHz on the big cores.

The highest safe voltage for the little cores is 1.2V and for the big cores is 1.25V.
{{note|TuxThePenguin has found that the little cores on his RK3399 would run at 1.7GHz and the big cores would run at 2.1GHz, however a crash was encountered at this frequency so speeds were stepped back to 1.6GHz on the little cores and 2.08GHz on the big cores, make sure to thoroughly check for stability!}}

==DRAM==
TODO

= Rockchip RK3328 based boards =
TODO

Overclocking

2020-05-27T23:42:22Z

TuxThePenguin: Add RK3399 info

{{note|This might damage your equipment or may result in a unstable system, so do this at your own risk!}}
{{note|This page is incomplete, you're welcome to improve it.}}
{{note|Overclocked devices may seem stable but crash occasionally and be hard to debug. A good test suite needs to be found to properly test the entire functionality of overclocked devices to properly ensure stability}}
{{note|Keep a backup bootable OS which is known to be stable, if an overclock fails you may not be able to boot the system without another OS }}
{{hint|All information regarding clock speeds, voltages and more are stored in the DTB (Device Tree Blob). You can learn more about it [https://elinux.org/Device_Tree_Reference here].}}

Overclocking is a way to get more and better performance out of the system by running it at higher clock speeds than the factory default.

= Preparation =
TODO, requires a compatible cross compiler (usually aarch64-linux-gnu), and clone the pine64 kernel repository.

Then after that just setup the variables for make.

= A64-based boards =
== GPU ==
Open <code>arch/arm64/boot/dts/allwinner/sun50i-a64.dtsi</code> in a text editor.

Look for

<nowiki>
mali: gpu@1c40000 {
compatible = "allwinner,sun50i-a64-mali", "arm,mali-400";
reg = <0x01c40000 0x10000>;
interrupts = <GIC_SPI 97 IRQ_TYPE_LEVEL_HIGH>,
<GIC_SPI 98 IRQ_TYPE_LEVEL_HIGH>,
<GIC_SPI 99 IRQ_TYPE_LEVEL_HIGH>,
<GIC_SPI 100 IRQ_TYPE_LEVEL_HIGH>,
<GIC_SPI 102 IRQ_TYPE_LEVEL_HIGH>,
<GIC_SPI 103 IRQ_TYPE_LEVEL_HIGH>,
<GIC_SPI 101 IRQ_TYPE_LEVEL_HIGH>;
interrupt-names = "gp",
"gpmmu",
"pp0",
"ppmmu0",
"pp1",
"ppmmu1",
"pmu";
clocks = <&ccu CLK_BUS_GPU>, <&ccu CLK_GPU>;
clock-names = "bus", "core";
resets = <&ccu RST_BUS_GPU>;

assigned-clocks = <&ccu CLK_GPU>;
assigned-clock-rates = <432000000>;
};
</nowiki>

The <code>assigned-clock-rates</code> line is set to <code>432000000</code>, this means that the GPU is clocked at 432MHz. So if you want 500MHz, set the value to <code>500000000</code>.

Save the dtsi file, and recompile the DTB.

{{note|Danct12 has found on his Pinetab that 562 MHz is the limit for stable operation.}}
{{note|Remember to run a benchmark tool (such as glmark2-es2) to make sure that it's stable! If it's not, then lower the clock speed until you can get a stable clock speed.}}

== CPU ==
TODO

== DRAM ==

{{note|It is not recommended to exceed 672 MHz clockspeed on the DRAM.}}

When overclocking the GPU, it is a good idea to also overclock the DRAM, as the main bottleneck of the A64 SOC is the memory.

= Rockchip RK3399 based boards =
The RK3399 clocks are found in <code>arch/arm64/boot/dts/rockchip/rk3399-opp.dtsi</code>

More optimised voltages and clocks can be found in <code>arch/arm64/boot/dts/rockchip/rk3399-op1-opp.dtsi</code>
These include a slight overclock and undervolt, they are intended for the OP1 CPU found in many chromebooks but have worked fine in all recorded cases on regular RK3399s in other devices.

Any clock speeds can be added for the GPU in <code>gpu_opp_table</code>
A set of available clock speeds that can be added to the CPU clusters can be found in [need to fine file], these clock speeds can be added to <code>cluster0_opp</code> for the small cores and <code>cluster1_opp</code> for the big cores respectively

Safe voltages for the GPU and small CPU core clusters are up to 1.2V.

Safe voltages for the big CPU core cluster is up to 1.25V.

These are specified in the RK3399 schematic provided by Rockchip as being the maximum recommended operating voltage.

{{note|TuxThePenguin has found that the RK3399 in his Pinebook Pro can reach 950MHz on the GPU while being stable, 1GHz was tried but crashed instantly.}}

= Rockchip RK3328 based boards =
TODO

Overclocking

2020-05-27T23:32:36Z

TuxThePenguin:

Pinebook Pro

2020-05-24T13:35:39Z

TuxThePenguin: Update RK3399 schematic version

= User Guide =
== Introducing PineBook Pro ==
[[File:PBP.jpg|400px|thumb|right|Pinebook Pro running stock Debian with MATE]]

The Pinebook Pro is a Linux and *BSD ARM laptop from [https://www.pine64.org/ PINE64]

It is built to be a compelling alternative to mid-ranged Chromebooks that people convert into Linux laptops. It features an IPS 1080p 14″ LCD panel, a premium magnesium alloy shell, high capacity eMMC storage, a 10,000 mAh capacity battery, and the modularity that only an open source project can deliver.

Key features include: the RK3399 SOC; USB-C for data, video-out and power-in (3A 5V); privacy switches for the microphone, BT/WiFi module, and camera; and expandable storage via NVMe (PCIe 4x) with an optional adapter.

The Pinebook Pro is equipped with 4GB LPDDR4 system memory, high capacity eMMC flash storage, and 128Mb SPI boot Flash. The I/O includes: 1x micro SD card reader (bootable), 1x USB 2.0, 1x USB 3.0, 1x USB type C Host with DP 1.2 and power-in, PCIe 4x for an NVMe SSD drive (requires an optional adapter), and UART (via the headphone jack by setting an internal switch).

The keyboard and trackpad both use the USB 2.0 protocol. The LCD panel uses eDP MiPi display protocol.

Many different Operating Systems (OS) are freely available from the open source community and partner projects. These include various flavors of Linux (Ubuntu, Debian, Manjaro, etc.) and *BSD.

== Software and OS Image Downloads ==

=== Default Debian MATE Desktop Quick Start ===

The default Operating system that ships with the Pinebook Pro is Debian 9 with MATE desktop. It has been built by a community developer called MrFixIt2001, who can be reached on the PINE64 forum or in the chats.
The newest release of the build can downloaded directly from [https://github.com/mrfixit2001/debian_desktop/releases MrFixIt2001's GitHub].

'''The default username and password is:'''
* Username: rock
* Password: rock

You can change the default ''rock'' username and ''rock'' home directory by logging into root (credentials root/root) instead of the default 'rock' user and running the following in root terminal and substituting desired username for NewUser:
[[File:UpdateScript.png|350px|thumb|right|Location of update script applet icon on stock Debian with MATE]]
<pre>
usermod -l NewUser -d /home/NewUser -m rock
</pre>

Once you log back into your new user, Bluetooth will complain about no transfer folder location. To fix this open terminal and type:
<pre>
blueman-services
</pre>

From here, select incoming folder under the 'transfer' tab.

The build includes a custom updater capable of updating uboot, the Linux kernel and numerous packages. The update script can be ran from both the userspace and the commandline. You will find a small 'Update Script' applet icon in the bottom panel, next to time and date applet.

You can run the script from the terminal using:
<pre>
sudo /usr/bin/mrfixit_update.sh
</pre>

More information about the default OS build and version history can be found on the [https://forum.pine64.org/showthread.php?tid=7830 Default OS update log] PINE64 forum thread.

=== [[Pinebook Pro_Software_Release|Pinebook Pro images]] ===
Under [[Pinebook Pro Software Release|'Pinebook Pro Software and OS Image Download Section']] you will find a complete list of currently supported Operating System images that work with the Pinebook as well as other related software.

The list includes OS images and descriptions of:

[{{fullurl:PinebookPro_Software_Release#Debian_Desktop}} http://files.pine64.org/sw/pine64_installer/json/debian.png] [[PinebookPro_Software_Release#Debian Desktop|'''Debian Desktop (microSD and eMMC Boot)''']]

[{{fullurl:PinebookPro_Software_Release#Bionic_LXDE}} http://files.pine64.org/sw/pine64_installer/json/lxde.png] [[PinebookPro_Software_Release#Bionic LXDE|'''Bionic LXDE (microSD and eMMC Boot)''']]

[{{fullurl:PinebookPro_Software_Release#Bionic_Mate}} http://files.pine64.org/sw/pine64_installer/json/mate.png] [[PinebookPro_Software_Release#Bionic Mate|'''Bionic Mate (microSD and eMMC Boot)''']]

[{{fullurl:PinebookPro_Software_Release#Manjaro_ARM}} http://files.pine64.org/sw/pine64_installer/json/fedora.png] [[PinebookPro_Software_Release#Fedora|'''Fedora (microSD and eMMC Boot)''']]

[{{fullurl:PinebookPro_Software_Release#Manjaro_ARM}} http://files.pine64.org/sw/pine64_installer/json/manjaro.png] [[PinebookPro_Software_Release#Manjaro ARM|'''Manjaro ARM (microSD and eMMC Boot)''']]

note: When upgrading from a prior release of Manjaro to version 20.1, you may need to increase the backlight as the number of steps for the backlight exposed by the kernel was changed from 256 to 4096

[{{fullurl:PinebookPro_Software_Release#Manjaro_ARM}} http://files.pine64.org/sw/pine64_installer/json/opensuse.png] [[PinebookPro_Software_Release#OpenSUSE|'''OpenSUSE (microSD and eMMC Boot)''']]

[{{fullurl:PinebookPro_Software_Release#Q4OS}} http://files.pine64.org/sw/pine64_installer/json/q4os.png] [[PinebookPro_Software_Release#Q4OS|'''Q4OS (microSD and eMMC Boot)''']]

[{{fullurl:PinebookPro_Software_Release#Armbian}} http://files.pine64.org/sw/pine64_installer/json/armbian.png] [[PinebookPro_Software_Release#Armbian|'''Armbian (microSD and eMMC Boot)''']]

[{{fullurl:PinebookPro_Software_Release#NetBSD}} http://files.pine64.org/sw/pine64_installer/json/netbsd.png] [[PinebookPro_Software_Release#NetBSD|'''NetBSD (microSD and eMMC Boot)''']]

[{{fullurl:Pinebook_Pro_Software_Release#OpenBSD}} [[File:Puffy_mascot_openbsd.png|125px]]] [[Pinebook_Pro_Software_Release#OpenBSD|'''OpenBSD release for ARM64''']]

[{{fullurl:PinebookPro_Software_Release#Chropmium}} http://files.pine64.org/sw/pine64_installer/json/chromium.jpg] [[PinebookPro_Software_Release#Chromium|'''Chromium (microSD and eMMC Boot)''']]

[{{fullurl:PinebookPro_Software_Release#Android_7.1_microSD}} http://files.pine64.org/sw/pine64_installer/json/android_7.png] [[PinebookPro_Software_Release#Android_7.1_microSD|'''Android 7.1 (microSD Boot)''']]           [{{fullurl:PinebookPro_Software_Release#Android_7.1_eMMC}} http://files.pine64.org/sw/pine64_installer/json/android_7.png] [[PinebookPro_Software_Release#Android_7.1_eMMC|'''Android 7.1 (eMMC)''']]

[{{fullurl:PinebookPro_Software_Release#Debian_Installer_for_Pinebook_Pro}} http://files.pine64.org/sw/pine64_installer/json/debian.png] [[PinebookPro_Software_Release#Debian_Installer_for_Pinebook_Pro|'''Debian Installer for Pinebook Pro''']]

[{{fullurl:Pinebook_Pro_Software_Release#Gentoo_Script_for_Pinebook_Pro}} http://files.pine64.org/sw/pine64_installer/json/gentoo.png]
[[Pinebook_Pro_Software_Release#Gentoo_Script_for_Pinebook_Pro|'''Gentoo Script for Pinebook Pro''']]

[{{fullurl:PinebookPro_Software_Release#Kali}} [[File:Kali.jpeg|125px]]] [[PinebookPro_Software_Release#Kali|'''Kali Script for Pinebook Pro (microSD and eMMC Boot)''']]

=== Quick Links to OS Images Build Sources===
'''Some of the provided OS images are still in beta or nightly build and only fit for testing purposes. These images ought to be avoided for normal usage - use them at your own risk'''
* [https://github.com/ayufan-rock64/linux-build/releases/ ayufan's Linux build repo]
* [https://github.com/ayufan-rock64/chromiumos-build/releases ayufan's Chromium OS build repo]
* [https://github.com/mrfixit2001/debian_desktop/releases mrfixit2001's Linux debian desktop build repo]

== Keyboard ==
The Pinebook Pro is available in two keyboard configurations: ISO and ANSI. Both the keyboard and trackpad in the Pinebook Pro use the USB 2.0 protocol and show up as such in xinput. The keyboard features function (Fn) keys in the F-key row, which include display brightness controls, sound volume, trackpad lock, and other functionality. There is also a custom PINE64 logo key that functions as Menu/Super key. It has also a secondary functionality for setting the privacy switches.

The keyboard firmware binary can be flashed from userspace using the provided open source utility.

Documentation for the keyboard can be found in [[#Datasheets for Components and Peripherals|Datasheets for Components and Peripherals]].

=== Typing special characters ===
The [[Wikipedia:British_and_American_keyboards#Other_keyboard_layouts|UK ISO Layout]] does not have dedicated keys for characters like the German umlauts (Ä,Ö,Ü, etc). Certain characters can still be generated by means of either key combinations or key sequences.
{| class="wikitable"
!Character
!Key combination/sequence
|-
|Ä, Ö, Ü, ä, ö, ü
|[[Wikipedia:AltGr_key|[AltGr]]]+'[' followed by [A], [O], [U], [a], [o] or [u]
|-
|µ
|[AltGr]+[m]
|-
|Ø, ø
|[AltGr]+[O], [AltGr]+[o]
|-
|@
|[AltGr]+[q] (as on the German layout)
|-
|ß
|[AltGr]+[s]
|-
|§
|[AltGr]+[S]
|-
|°
|[AltGr]+[)]
|}

=== Privacy Switches ===
There are three privacy switches mapped to the F10, F11 and F12 keys on the Pinebook Pro keyboard. They de/activate the following:

{| class="wikitable"
|+ Privacy switch function and description
! Combination
! Effect
! Description
! Notes
|-
! scope=row | PINE64 logo key+F10
| Microphone Privacy switch || CAPs lock LED blinks. 2 blinks = enabled, 3 blinks = disabled
|-
! scope=row | PINE64 logo key+F11
| WiFi Privacy switch || NUM lock LED blinks. 2 blinks = enabled, 3 blinks = disabled.
| '''Re-enabling requires reboot''' (or a [//forum.pine64.org/showthread.php?tid=8313&pid=52645#pid52645 command line hack to bind/unbind]).
|-
! scope=row | PINE64 logo key+F12
| Camera privacy switch || CAPs lock and NUM lock LEDs blink together. 2 blinks = enabled, 3 blinks = disabled
|}

'''(Press the PINE64 logo key plus Fn (10/11/12) for 3 seconds)'''

The keyboard uses special firmware that operates separately of the operating system. It detects if either the F10, F11 or F12 key, and the Pine key were pressed for 3 seconds. This disables the peripherals as listed above by cutting off their power. Which has the same result as cutting off the power to each peripheral with a physical switch. This implementation is very secure since the firmware that determines whether a peripheral gets power is not a part of the Pinebook Pro’s operating system. So the power state value for each peripheral cannot be overridden or accessed from the operating system. The power state setting for each peripheral is stored across reboots.

== Trackpad ==
The trackpad is a reasonable size, has a matte finish that that your finger can slide along easily, and two actuating buttons. It is the only component of the Pinebook Pro held in place with strong adhesive tape. It supports multi-touch functionality.
Documentation for the trackpad can be found in [[#Datasheets for Components and Peripherals|Datasheets for Components and Peripherals]].
The trackpad firmware binary can be flashed from userspace using the provided open source utility (https://github.com/ayufan-rock64/pinebook-pro-keyboard-updater).

'''Everyone with a Pinebook Pro produced in 2019 should update their keyboard and trackpad firmware.'''

Before you start:

Please refer to original documentation for details.

Your Pinebook Pro should be either fully charged or, preferably, running of mains. This utility will be writing chips on the keyboard and trackpad, so a loss of power during any stage of the update can result in irrecoverable damage to your trackpad or keyboard.

The scripts ought to work on all OSs available for the Pinebook Pro. Some OSs may, however, require installation of relevant dependencies.

There are two keyboard versions of the Pinebook Pro, ISO and ANSI. You need to know which model you have prior to running the updater.
FW update steps for both models are listed below.

What you will need:

*Your Pinebook Pro fully charged or running off of mains power
*Connection to WiFi
*An external USB keyboard & mouse. Or access to the Pinebebook Pro via SSH

'''ISO Model'''

From the terminal command line:

<pre>
git clone https://github.com/ayufan-rock64/pinebook-pro-keyboard-updater
cd pinebook-pro-keyboard-updater
sudo apt-get install build-essential libusb-1.0-0-dev xxd
make
</pre>

Step 1
<pre>
cd pinebook-pro-keyboard-updater
sudo ./updater step-1 iso
sudo reboot
</pre>

Step 2 (after reboot)
<pre>
cd pinebook-pro-keyboard-updater
sudo ./updater step-2 iso
sudo reboot
</pre>

----

'''ANSI Model'''

*NOTE: Running step-1 on the ansi keyboard model will make the keyboard and trackpad inaccessible until step-2 is run, so an external keyboard must be connected to complete the update on this model!

From the terminal command line:

<pre>
git clone https://github.com/ayufan-rock64/pinebook-pro-keyboard-updater
cd pinebook-pro-keyboard-updater
sudo apt-get install build-essential libusb-1.0-0-dev xxd
make
</pre>

Step 1
<pre>
cd pinebook-pro-keyboard-updater
sudo ./updater step-1 ansi
sudo reboot
</pre>

Step 2 (after reboot)
<pre>
cd pinebook-pro-keyboard-updater
sudo ./updater step-2 ansi
sudo reboot
</pre>
When done, if some of the keys produce in-correct characters, please check your OSes' language settings. For ANSI users, the default OS shipped with English UK as the default language. You can change it to English US if desired.

=== X-Windows & trackpad settings ===
Some forum members have found that an adjustment to X-Windows will allow finer motion in the trackpad. If you use the '''Synaptic''' mouse/trackpad driver use this command to make the change live;
<pre>synclient MinSpeed=0.25</pre>
You may experiment with different settings, but 0.25 was tested as helping noticably. 
 
To make the change persist across reboots, change the file <code>/etc/X11/xorg.conf</code> similar to below;
<pre> Section "InputClass"
Identifier "touchpad catchall"
Driver "synaptics"
MatchIsTouchpad "on"
MatchDevicePath "/dev/input/event*"
Option "MinSpeed" "0.25"
EndSection</pre>
The line <code>Option "MinSpeed" "0.25"</code> is the change. 
 
Another forum user built on the above settings a little, and have found these to be very good:
<pre>synclient MinSpeed=0.25
synclient FingerLow=30
synclient PalmDetect=1
synclient VertScrollDelta=64
synclient HorizScrollDelta=64</pre>

<code>FingerLow</code> has the same value as 'FingerHigh' in one config (30). It is believed to help reduce mouse movement as you lift your finger, but it's not sure if synaptic works like this.
You may find this config to be comfortable for daily use.
 

The <code>right mouse click</code> is emulated by tapping with two fingers on the trackpad. If you feel that this is not very responsive you can try this value:
<pre> synclient MaxTapTime=250 </pre>.
 

== Power Supply ==
* Input Power: 5V DC @ 3A
* Mechanical: 3.5mm OD / 1.35mm ID, Barrel jack
* USB-C 15W PD quickcharge
* Only use one power input at a time, barrel jack OR USB-C

== LEDs ==
In total there are four LEDs on the Pinebook Pro, three of which are placed in the top left side of the keyboard, and one near the barrel-port:

:1. The red LED next to the barrel-port indicates charging. It will illuminate when mains power is supplied to the Pinebook Pro from either the standard power supply unit or a USB-C smartphone charger.

:2. The power indicator LED on the Pinebook Pro supports three different colours: green, amber and red. It is also capable of flashing/blinking to indicate activity. In the default Debian with MATE build, green LED means power and red means suspend (amber is unused).

:3. The Num lock, green LED.

:4. The Caps lock, green LED.

(The Num and Caps lock LEDs have a secondary function. When the privacy switches get activated they blink to confirm that switch has been activated.)

== Webcam ==
* Streaming video resolutions supported, (un-compressed):
** 320 x 240
** 640 x 480
** 800 x 600
** 1280 x 720
** 1600 x 1200
* Still frame resolutions supported:
** 160 x 120
** 176 x 144
** 320 x 240
** 352 x 288
** 640 x 480
** 800 x 600
** 1280 x 720
** 1600 x 1200
* Some people test with the application Cheese
WIP

== Microphones ==
While it has been said that some Pinebook Pro units contain only one microphone despite having two labeled microphone holes on the outer casing, other units do indeed contain two microphones. It is presently unclear which batches have either configuration; units from the initial community batch of 1000 units (following the initial 100) are believed to contain two, populating both labeled holes.

The wires leading to both microphones connect to the mainboard withd a small white plastic connector, located directly adjacent to the ribbon cable attachment point for the keyboard interface.

'''Microphones not working?'''

If pavucontrol input doesn't show microphone activity try the [[Pinebook_Pro#Privacy_Switches]]; once that is set to on do the below; if that still hasn't fixed it you may want to check that the microphone connector is plugged in (see the [[Pinebook_Pro#Technical_Reference]]).

<pre>
run alsamixer from the command line > hit F6 and select the es8316 > hit F4 to get to the capture screen > select the bar labeled ADC >
> increase the gain to 0dB > change the audio profile in pavucontrol to another with input

Additionally:
you may want to modify ADC PGA to get the levels to where you want them
</pre>

== Bluetooth and WiFi ==
[[File:PinebookPro_WirelessIC_Location.jpg|400px|thumb|right|The Pinebook Pro's AP6256 wireless module]]
===Hardware Overview===
The Pinebook Pro contains an AMPAK AP6256 wireless module to provide Wi-Fi (compliant to IEEE 802.11ac) and Bluetooth (compliant to Bluetooth SIG revision 5.0). The module contains a Broadcom transceiver IC, believed to be the BCM43456, as well as the support electronics needed to allow the Wi-Fi and Bluetooth modes to share a single antenna.

The wireless module interfaces with the Pinebook Pro’s system-on-chip using a combination of three interfaces: Bluetooth functionality is operated by serial UART and PCM, while the Wi-Fi component uses SDIO. It is unknown if the module’s Bluetooth capabilites are usable under operating systems that do not support SDIO.

The module’s RF antenna pin is exposed on the mainboard via a standard Hirose U.FL connector, where a coaxial feedline links it to a flexible adhesive antenna situated near the upper right corner of the Pinebook Pro’s battery. As the RF connector is fragile and easily damaged, it should be handled carefully during connection and disconnection, and should not be reconnected frequently.

===Issues===
Problems have been reported with the Wi-Fi transceiver’s reliability during extended periods of high throughput, especially on the 2.4 GHz band. While the cause of this has yet to be determined, switching to the 5 GHz band may improve stability.

Since the Bluetooth transceiver shares both its spectrum and antenna with 2.4 GHz Wi-Fi, simultaneous use of these modes may cause interference, especially when listening to audio over Bluetooth. If Bluetooth audio cuts out frequently, switching to the 5 GHz band – or deactivating Wi-Fi – may help.

===Wi-Fi Capabilities===
Wi-Fi on the Pinebook Pro is capable of reaching a maximum data transfer rate of approximately 433 megabits per second, using one spatial stream. The transceiver does not support multiple spatial streams or 160-MHz channel bandwidths.

The Wi-Fi transceiver supports the lower thirteen standard channels on the 2.4 GHz band, using a bandwidth of 20 MHz. At least twenty-four channels are supported on the 5 GHz band, spanning frequencies from 5180 to 5320 MHz, 5500 to 5720 MHz, and 5745 to 5825 MHz, with bandwidths of 20, 40, or 80 MHz.

Maximum reception sensitivity for both bands is approximately -92 dBm. The receiver can tolerate input intensities of no more than -20 dBm on the 2.4 GHz band, and no more than -30 dBm on the 5 GHz band. Maximum transmission power is approximately +15 dBm for either band, falling further to approximately +10 dBm at higher data transfer rates on the 5 GHz band.

With current available drivers and firmware, the Wi-Fi interface supports infrastructure, ad-hoc, and access-point modes with satisfactory reliability. Monitor mode is not presently supported. Wi-Fi Direct features may be available, but it is unclear how to make use of them under Linux.

Be aware that Linux userspace utilities, such as <code>iw</code>, may report inaccurate information about the capabilities of wireless devices. Parameter values derived from vendor datasheets, or direct testing, should be preferred to the outputs of hardware-querying tools.

===Bluetooth Capabilities===
Bluetooth data transfer speeds have an indicated maximum of 3 megabits per second, but it is unclear what practical data rates can be expected. Audio streaming over Bluetooth is functioning normally, as is networking. Bluetooth Low-Energy functions, such as interacting with Bluetooth beacons, have not yet been tested conclusively.

The Bluetooth transceiver supports all 79 channel allocations, spanning frequencies from 2402 MHz to 2480 MHz. Reception sensitivity is approximately -85 dBm, with a maximum tolerable reception intensity of -20 dBm. Bluetooth transmission power is limited to +10 dBm.

===Disabling Bluetooth===
<pre>
#disable bluetooth once
sudo rfkill block bluetooth &&

#confirm
rfkill
</pre>

<pre>
#disable bluetooth on boot**
sudo systemctl enable rfkill-block@bluetooth
</pre>

<nowiki>**This does not do what one might want on certain distros, Manjaro XFCE for example. Try the below.</nowiki>

<pre>
right click on the bluetooth panel icon > select 'plugins' > PowerManager > configuration > deselect the auto power on option
</pre>

== LCD Panel ==
* Model: BOE NV140FHM-N49
* 14.0" (35.56cm) diagonal size
* 1920x1080 resolution
* 60hz refresh rate
* IPS
* 1000:1 contrast
* 250nt brightness
* 63% sRGB coverage
* 6 bit colour
* 30 pin eDP connection

Some people have tested hardware video decode using the following;
<pre>ffmpeg -benchmark -c:v h264_rkmpp -i file.mp4 -f null -</pre>

== External ports list ==
Here are a list of the external ports. See [[Pinebook_Pro#Expansion_Ports|Technical Reference - Expansion Ports]] for port specifications.
* Left side
** Barrel jack for power, (with LED)
** USB 3, Type A
** USB 3, Type C
* Right side
** USB 2, Type A
** Standard headset jack
** MicroSD card slot

== Using the UART ==
[[File:PBPUART.jpeg|400px|thumb|right|Headphone jack UART wiring reference.
 Swapping the tx and rx around from this also works and is more traditional.
 See [http://files.pine64.org/doc/pinebook/guide/Pinebook_Earphone_Serial_Console_Developer_Guide.pdf this] official Pine64 .pdf.]]

UART output is enabled by flipping the UART switch to the ON position (item 9). To do so you need to remove the Pinebook Pro's bottom cover - please follow [https://wiki.pine64.org/index.php/Pinebook_Pro_Main_Page#Accessing_the_Internals_-_Disassembly_and_Reassembly proper disassembly and reassembly protocol]. The OFF position is towards the touchpad, the ON position is towards the display hinges.

With the UART switch in the ON position, console is relayed via the audiojack and the laptop's sound is turned OFF. Please ensure that you are using a 3.3v interface (such as the CH340, FTDI-232R, or PL2303, which are sold in both 3.3v and 5v variants) to avoid damage to the CPU.

Insert the USB plug of the cable into an open USB port on the machine which will monitor. Run the following in a terminal:

<code>
$ lsusb
</code>

you should find a line similar to this:

<code>
Bus 001 Device 058: ID 1a86:7523 QinHeng Electronics HL-340 USB-Serial adapter
</code>

You may have to clean the USB contacts of the Serial cable to get a good connection if you do not find that line.

The audio jack of the Serial cable should be fully inserted into the Pinebook Pro audio port.

Serial output should now be accessible using screen, picocom or minicom (and others).
Examples:

<code>
screen /dev/ttyUSB0 1500000

picocom /dev/ttyUSB0 -b 1500000

minicom -D /dev/ttyUSB0 -b 1500000</code>

Old versions of U-Boot do not use the UART for console output. <strike>The console function is activated by the Linux kernel. Thus, if you use a non-Pinebook Pro Linux distro and want the UART as a console, you have to manually enable it.</strike>

== Using the optional NVMe adapter ==
The optional NVMe adapter allows the use of M.2 cards that support the NVMe standard, (but not SATA standard). The optional NVMe M.2 adapter supports '''M''' & '''M'''+'''B''' keyed devices, in both 2242 & 2280 physical sizes, the most common ones available. In addition, 2230 & 2260 are also supported, though NVMe devices that use those sizes are rare.

Once you have fitted and tested your NVMe drive, please add a note to this page [[Pinebook_Pro_Hardware_Accessory_Compatibility]] to help build a list of tried and tested devices.

=== Installing the adapter ===
The V2.1-2019-0809 SSD adapter that shipped with the initial Pinebook Pro batches had significant issues. A repair kit will be shipped to address those issues.
(If necessary, it can be modified to work. There is [https://forum.pine64.org/showthread.php?tid=8322&pid=52700#pid52700 an unofficial tutorial on the forums] describing these modifications.)

The updated SSD adapter, labeled V2-2019-1107, takes into account the prior problems with trackpad interference. New orders as of Feb. 22nd, 2020 will be the updated adapter.

Actual installation instructions are a work in progress.

=== Post NVMe install power limiting ===
Some NVMe SSDs allow reducing the maximum amount of power. Doing so may reduce the speed, but it may be needed in the Pinebook Pro to both improve reliability at lower battery levels. And to reduce power used, to maintain battery life.
Here are the commands to obtain and change the power settings. The package 'nvme-cli' is required to run these commands. The example shows how to find the available power states, and then sets it to the lowest, non-standby setting, (which is 3.8 watts for the device shown);
<pre>$ sudo nvme id-ctrl /dev/nvme0
NVME Identify Controller:
...
ps 0 : mp:9.00W operational enlat:0 exlat:0 rrt:0 rrl:0
rwt:0 rwl:0 idle_power:- active_power:-
ps 1 : mp:4.60W operational enlat:0 exlat:0 rrt:1 rrl:1
rwt:1 rwl:1 idle_power:- active_power:-
ps 2 : mp:3.80W operational enlat:0 exlat:0 rrt:2 rrl:2
rwt:2 rwl:2 idle_power:- active_power:-
ps 3 : mp:0.0450W non-operational enlat:2000 exlat:2000 rrt:3 rrl:3
rwt:3 rwl:3 idle_power:- active_power:-
ps 4 : mp:0.0040W non-operational enlat:6000 exlat:8000 rrt:4 rrl:4
rwt:4 rwl:4 idle_power:- active_power:-

$ sudo nvme get-feature /dev/nvme0 -f 2
get-feature:0x2 (Power Management), Current value:00000000
$ sudo nvme set-feature /dev/nvme0 -f 2 -v 2 -s
set-feature:02 (Power Management), value:0x000002</pre>
Some NVMe SSDs don't appear to allow saving the setting with "-s" option. In those cases, leave off the "-s" and use a startup script to set the non-default power state at boot. 
If you want to test performance without saving the new power setting semi-permanantly, then leave off the "-s" option. 
 
There is another power saving feature for NVMes, APST, (Autonomous Power State Transitions). This performs the power saving & transitions based on usage. To check if you have a NVMe SSD with this feature;
<pre>$ sudo nvme get-feature -f 0x0c -H /dev/nvme0</pre>
Information for this feature, (on a Pinebook Pro), is a work in progress.

=== Using as data drive ===
As long as the kernel in use has both the PCIe and NVMe drivers, you should be able to use a NVMe drive as a data drive. It can automatically mount when booting from either the eMMC or an SD card. This applies to Linux, FreeBSD, and Chromium, using the normal partitioning and file system creation tools. Android requires testing.

=== Using as OS root drive ===
The SoC does not include the NVMe boot code, so the NVMe is not in the SoC's boot order. However, using the [https://github.com/mrfixit2001/updates_repo/blob/v1.1/pinebook/filesystem/mrfixit_update.sh U-Boot update script] from the mrfixit2001 Debian or [https://pastebin.com/raw/EeK074XB Arglebargle's modified script], and [https://github.com/pcm720/rockchip-u-boot/releases the modified u-boot images] provided by forum user pcm720, you can now add support to boot from an NVMe drive. Binary images are useable with SD, eMMC, and [[Pinebook_Pro_SPI|SPI flash]]. For OS images using the mainline kernel, there are a few variants of U-Boot available that also support NVMe as the OS drive. Though these may require writing the U-Boot to the SPI flash for proper use of the NVMe as the OS drive.

The current boot order, per last testing, for this modified U-Boot is:
*MicroSD
*eMMC
*NVMe

For more information, please refer to [https://forum.pine64.org/showthread.php?tid=8439&pid=53764#pid53764 the forum post.]

It is also possible to initially boot off an eMMC or SD card, then transfer to a root file system on the NVMe. Currently, it is necessary to have the U-Boot code on an eMMC or SD card. (A forum member [https://forum.pine64.org/showthread.php?tid=8439 posted here] about using a modified version of U-Boot with NVMe drivers, that uses <code>/boot</code> and <code>/</code> off the NVMe drive. So this may change in the future.)

Please see [[Pinebook_Pro#Bootable Storage|Bootable Storage]].

== Caring for the PineBook Pro ==
=== Bypass Cables ===
The mainboard features two (disconnected by default) bypass cables that are only to be used with the battery disconnected. The female (10) male (6) ends of the bypass cables can be connected to provide power to the mainboard if you need to run the laptop without a battery. Please refer to this [http://files.pine64.org/doc/PinebookPro/PinebookPro_Engineering_Notice.pdf engineering notice].

WARNING: Do not connect the bypass cables with the battery connected. Using the bypass cables with the battery connected can permanently damage the computer.

=== [[Pinebook_Service_Step_by_Step_Guides|Pinebook Service Step-by-Step Guides]] ===
Placeholder for Pinebook Pro specific guides

Under [[Pinebook_Service_Step_by_Step_Guides|'Service Guides for Pinebook']] you can find instructions guides concerning disassembly of:

'''Note: The installation process on Pinebook Pro similar to 14" Pinebook'''

'''Note: The installation process is the reverse order of removal guide'''

* 14″ Pinebook Lithium Battery Pack Removal Guide
* 14″ Pinebook LCD Panel Screen Removal Guide
* 14″ Pinebook eMMC Module Removal Guide

== Using the SPI flash device ==
The Pinebook Pro comes with a 128Mbit, (16MByte), flash device suitable for initial boot target, to store the bootloader. The SoC used on the Pinebook Pro boots from this SPI flash device first, before eMMC or SD card. At present, April 19, 2020, the Pinebook Pros ship without anything programmed in the SPI flash device. So the SoC moves on to the next potential boot device, the eMMC. ARM/ARM64 computers do not have a standardized BIOS, yet.

Here is some information on using the SPI flash device:

* You need the kernel built with SPI flash device support, which will supply a device similar to: <code>/dev/mtd0</code> 
* The Linux package below, will need to be available: <code>mtd-utils</code> 
* You can then use this program from the package to write the SPI device: <code>flashcp <filename> /dev/mtd0</code> 

Even if you need to recover from a defective bootloader written to the SPI flash, you can simply short pin 6 of the SPI flash to GND and boot. This will render the SoC bootrom unable to read from the SPI flash and have it fall back to reading the bootloader from other boot media like the eMMC or Micro SD card.

The procedures described above are a lot less risky than attaching an external SPI flasher and do not require any additional hardware. 
 
At present, April 19th, 2020, there is no good bootloader image to flash into the SPI flash device. This is expected to change, as there are people working on issue.

== FAQ ==
What cool software works out of the box? [[Pinebook Pro OTB Experience]]

= Software tuning guide =
Details on how to get the most out of a Pinebook Pro & its RK3399 SoC.

== Customizing Pinebook Pro's factory OS ==
Here are some hints on what you can do to customize the Pinebook Pro's factory image (aka [https://github.com/mrfixit2001/debian_desktop mrfixit2001 debian build])

=== Initial user changes, password, name, etc ===
When you first get your Pinebook Pro, you should consider setting strong passwords and making the default account your own.

* Reboot (this is just to ensure all background processes belong to the user are not running... there are other ways to achieve this but this way is easy)
* Once the machine reboots press Alt-Ctrl-F1 to bring up a text terminal
* Login as root (login: root, password: root)
* Set a strong password for the root user using the following command and it's prompts:
<pre># passwd (and follow prompts)</pre>
* Rename the rock user to your prefered username (replace myself with whatever you like):
<pre># usermod -l myself -d /home/myself -m rock</pre>
* Rename the rock group to match your preferred username:
<pre># groupmod -n myself rock</pre>
* Put your name in the account, (replace "John A Doe" with your name):
<pre># chfn -f "John A Doe" myself</pre>
* Set a strong password for the normal user:
<pre># passwd myself</pre>
* Log out of the text terminal:
<pre># logout</pre>
* Press Alt-Ctrl-F7 to go back to the login screen and then login as the normal user
* Open text terminal to fix login error: "Configured directory for incoming files does not exist";
<pre>$ blueman-services</pre>
Select "Transfer" tab and set "Incoming Folder" to myself
OR
If adduser is in distro, this is MUCH easier
sudo adduser $USER ,, fill out requested data
Then,, sudo adduser $USER $GROUP,,, 1 group at a time
To see which groups to add,,, id $USER, id rock

=== Changing the default hostname ===
Debian 9 has a command to allow you to change the hostname. You can see the current settings using;
<pre>> sudo hostnamectl
Static hostname: Debian-Desktop
Icon name: computer
Machine ID: dccbddccbdccbdccbdccbdccbdccbccb
Boot ID: ea99ea99ea99ea99ea99ea99ea99ea99
Operating System: Debian GNU/Linux 9 (stretch)
Kernel: Linux 4.4.210
Architecture: arm64</pre>
To change, use this, (with "My_Hostname" used as the example);
<pre>> sudo hostnamectl set-hostname My_Hostname</pre>
Whence done, you can re-verify using the first example.

Then you should backup and edit your <code>/etc/hosts</code> entry's name;
<pre>> sudo cp -p /etc/hosts /etc/hosts.`date +%Y%m%d`
> sudo vi /etc/hosts
127.0.0.1 localhost
127.0.0.1 My_Hostname
::1 localhost ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
127.0.1.1 linaro-alip</pre>

=== Disable Chromium browser's prompt for passphrase & password storage ===

Perform the following steps:

* On the tool bar, hover over the Chromium icon
* Using the right mouse button, select '''Properties'''
* In the '''Command:''' line section, add <code>--password-store=basic</code> before the <code>%U</code>
* Use the '''x Close''' button to save the change
This will of course, use basic password storage, meaning any saved passwords are not encrypted. Perfectly fine if you never use password storage.

=== Changing the boot splash picture ===

The default boot splash picture can be replaced using the following instructions:

* Install '''ImageMagick''' which will do the conversion
<pre>$ sudo apt-get install imagemagick</pre>
* Create a 1920 x 1080 picture. For the best results, use a PNG image (It supports lossless compression).
* From the directory in which your new image is stored run the following commands
* Convert your image to the bootsplash raw format using imagemagick convert.
<pre>$ convert yoursplashimage.png -separate +channel -swap 0,2 -combine -colorspace sRGB RGBO:splash.fb</pre>
* Create a backup copy of your current splash screen
<pre>$ sudo cp /usr/share/backgrounds/splash.fb /usr/share/backgrounds/splash_original.fb</pre>
* Copy your new splash screen into place
<pre>$ sudo cp splash.fb /usr/share/backgrounds/splash.fb</pre>
* Set the correct permissions on the splash.fb file
<pre>$ sudo chmod 644 /usr/share/backgrounds/splash.fb</pre>
* If you do not want to see kernel console text messages, make sure you don't have '''Plymouth''' installed

=== Enabling text boot time messages ===

By default most Linux distros have a boot screen with a picture. To see all the messages, use the following;

* Backup and edit the U-Boot configuration file:
<pre>cp -p /etc/default/u-boot /etc/default/u-boot.`date +%Y%m%d`
chmod a-w /etc/default/u-boot.`date +%Y%m%d`
vi /etc/default/u-boot</pre>
Remove the '''quiet''' and '''splash''' parameters. Leave everything else alone.
* Update the U-Boot configuration:
<pre>u-boot-update</pre>
* Test and verify you get what you think you should be seeing.

== Chromium tweaks ==

=== Flags ===

From the [https://github.com/mrfixit2001/updates_repo/blob/v1.8/pinebook/filesystem/default official Debian image]:

<pre>
--disable-low-res-tiling \
--num-raster-threads=6 \
--profiler-timing=0 \
--disable-composited-antialiasing \
--test-type \
--show-component-extension-options \
--ignore-gpu-blacklist \
--use-gl=egl \
--ppapi-flash-path=/usr/lib/chromium-browser/pepper/libpepflashplayer.so \
--ppapi-flash-version=32.0.0.255 \
--enable-pinch \
--flag-switches-begin \
--enable-gpu-rasterization \
--enable-oop-rasterization \
--flag-switches-end
</pre>

== GVIM has performance issue ==
It appears that using GTK3 can cause very slow scolling, while VIM in a terminal window works fine. 
Simply revert back to using GTK2, (how to do so, is somewhat Linux distro specific).

== Kernel options ==
Here are some Pinebook Pro & its RK3399 SoC Linux specific options. If kernel version, (or version range specific), it should list that information in the description.

To see if a specific feature is enabled in the current kernel, you can use something like this;

<pre>
$ zgrep -i rockchip_pcie /proc/config.gz
# CONFIG_ROCKCHIP_PCIE_DMA_OBJ is not set
CONFIG_PHY_ROCKCHIP_PCIE=m
</pre>
If it's listed as <code>=m</code>, then it's a module. You can see if the module is loaded with;
<pre>
$ lsmod | grep -i rockchip_pcie
phy_rockchip_pcie 16384 0
</pre>
Note modules are not loaded until needed. Thus, we sometimes check the kernel configuration instead to see if a feature is configured first, then see if it's a module.

=== Hardware video decoding ===
Here is a method to check for hardware video decoding by the VPU. There are special Linux kernel modules that perform this function. 
The default Debian uses Rockchip supplied kernel module <code>rk-vcodec</code>. To check, something like this can be used;
<pre>
$ lsmod | grep rk-vcodec
or
$ zgrep RK_VCODEC /proc/config.gz
CONFIG_RK_VCODEC=y
</pre>
Note that in the above example, the Rockchip video CODEC is not built as a module, but included into the kernel. Thus, it does not show up in the list modules check. 
 
Later kernels may use a different option in the configuration as below;
<pre>
$ zgrep HANTRO /proc/config.gz
CONFIG_VIDEO_HANTRO=m
CONFIG_VIDEO_HANTRO_ROCKCHIP=y
</pre>
  

= Troubleshooting guide =
Tips, tricks and other information for troubleshooting your Pinebook Pro
=== 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. [https://wiki.pine64.org/index.php/Pinebook_Pro_Main_Page#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 create a bootable SD card and see if your Pinebook Pro boots. If so, you can then 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 UART cable sold on the 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.

=== WiFi issues ===
* First, check the privacy switches to make sure your WiFi is enabled. They are persistant. See [[Pinebook_Pro_Main_Page#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>

=== 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 with: 
<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.

=== 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).

=== 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's might be easiest to do a system restore, and follow up by running the second step of the trackpad firmware update.
* 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]
  

=== 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, (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 your resolution is restored, try using the Tweak app to set scaling, instead. 
 
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.

= [[Pinebook_Pro_Hardware_Accessory_Compatibility|PineBookPro Hardware Compatibility]] =

Please contribute to the hardware compatibility page, which lists hardware which has been tested with the PBP, whether successful or not!

* [[Pinebook_Pro_Hardware_Accessory_Compatibility#NVMe_SSD_drives|NVMe SSD drives]]
* [[Pinebook_Pro_Hardware_Accessory_Compatibility#USB_hardware|USB hardware]]
* [[Pinebook_Pro_Hardware_Accessory_Compatibility#USB_C_alternate_mode_DP|USB C alternate mode DP]]
* [[Pinebook_Pro_Hardware_Accessory_Compatibility#Other_hardware|Other hardware]]
  
 

= Technical Reference =
== Accessing the Internals - Disassembly and Reassembly ==
[[File:Standoffs.png|400px|thumb|right|Pinebook Screw stand-offs correct placement and location]]

'''WARNING:''' Do not open the laptop by lifting the lid while the Pinebook Pro bottom cover is removed - this can cause structural damage to the hinges and/or other plastic components of the chassis such as the IO port cut-outs.

'''WARNING:''' When removing the back cover plate, use care if sliding fingertips between back cover plate and palm rest assembly. The back cover plate edges are sharp.

When disassembling the laptop make sure that it is powered off and folded closed. To remove the bottom cover of the Pinebook Pro, first remove the ten (10) Phillips head screws that hold the bottom section of the laptop in place. Remove the cover from the back where the hinges are situated by lifting it up and away from the rest of the chassis.

During reassembly, make sure that the back-screw standoffs are in place and seated correctly. To reassemble the Pinebook Pro, slide the bottom section into place so it meets the front lip of the keyboard section. Secure the front section (where the trackpad is located) in place using the short screws in the front left and right corners. Then proceed to pop in the bottom panel into place. Secure the bottom section (where hinges are located) by screwing in the left and right corners. Then screw in the remaining screws and run your finger though the rim on the chassis to make sure its fitted correctly. Note that the front uses the remaining 2 short screws.

NOTE: The screws are small and should only be finger tight. Too much force will strip the threads. If after installing screws the back cover plate has not seated properly on one side, open the display and hold the base on either side of the keyboard and gently flex the base with both hands in opposing directions. Once the side pops further in, then recheck the screws on that side. If it does not pop back in, just let it be.

NOTE: a basic 3d model to print replacement back-screw standoffs is available on Thingiverse [https://www.thingiverse.com/thing:4226648] pending release of something more definitive

== Pinebook Pro Internal Layout ==
=== Main chips ===
* RK3399 system-on-chip (1)
* LPDDR4 SDRAM (21)
* SPI NOR flash memory (29)
* eMMC flash memory (26)
* WiFi/BT module (27)

=== Mainboard Switches and Buttons ===
There are two switches on the main board: disabling the eMMC (24), and enabling UART (9) via headphone jack.

The Reset and Recovery buttons (28): the reset button performs an immediate reset of the laptop. The Recovery button is used to place the device in maskrom mode; this mode allows flashing eMMC using Rockchip tools (e.g. rkflashtools).

[[File:PBPL_S.jpg]]

=== Key Internal Parts ===
{| class="wikitable"
|+ Numbered parts classification and description
! Number
! Type
! Descriptor
|-
! scope=row | 1
| Component || RK3399 System-On-Chip
|-
! scope=row | 2
| Socket || PCIe 4X socket for optional NVMe adapter
|-
! scope=row | 3
| Socket || Speakers socket
|-
! scope=row | 4
| Socket || Trackpad socket
|-
! scope=row | 5
| Component || Left speaker
|-
! scope=row | 6
| Connector || Male power bridge connector
|-
! scope=row | 7
| Socket || Keyboard Socket
|-
! scope=row | 8
| Component || Optional NVMe SSD adapter
|-
! scope=row | 9
| Switch || UART/Audio switch - outputs UART via headphone jack
|-
! scope=row | 10
| Socket || Female power bridge socket
|-
! scope=row | 11
| Socket || Battery socket
|-
! scope=row | 12
| Component || Trackpad
|-
! scope=row | 13
| Component || Battery
|-
! scope=row | 14
| Component || Right speaker
|-
! scope=row | 15
| Socket || MicroSD card slot
|-
! scope=row | 16
| Socket || Headphone / UART jack
|-
! scope=row | 17
| Socket || USB 2.0 Type A
|-
! scope=row | 18
| Socket || Daughterboard-to-mainboard ribbon cable socket
|-
! scope=row | 19
| Cable || Daughterboard-to-mainboard ribbon cable
|-
! scope=row | 20
| Component || microphone
|-
! scope=row | 21
| Component || LPDDR4 RAM
|-
! scope=row | 22
| Socket || Mainboard-to-daughterboard ribbon cable socket
|-
! scope=row | 23
| Socket || Microphone socket
|-
! scope=row | 24
| Switch || Switch to hardware disable eMMC
|-
! scope=row | 25
| Antenna || BT/WiFI antenna
|-
! scope=row | 26
| Component || eMMC flash memory module
|-
! scope=row | 27
| Component ||BT/WiFi module chip
|-
! scope=row | 28
| Buttons || Reset and recovery buttons
|-
! scope=row | 29
| Component || SPI flash storage
|-
! scope=row | 30
| Socket || eDP LCD socket
|-
! scope=row | 31
| Socket || Power in barrel socket
|-
! scope=row | 32
| Socket || USB 3.0 Type A
|-
! scope=row | 33
| Socket || USB 3.0 Type C
|}

=== Smallboard detailed picture ===

[[File:Pinebook_pro_smallboard.jpg]]

== Bootable Storage ==
The Pinebook Pro is capable of booting from eMMC, USB 2.0, USB 3.0, or an SD card. It cannot boot from USB-C. The boot order of the hard-coded ROM of its RK3399 SoC is: SPI NOR, eMMC, SD, USB OTG.

At this time, the Pinebook Pro ships with a Debian + MATE build with [https://www.denx.de/wiki/U-Boot/ uboot] on the eMMC. Its boot order is: SD, then eMMC. Booting off USB storage is not currently available, but will be in the future.

(An update has been pushed for the default Debian + MATE build that improves compatibility with booting other OSs from an SD card. In order to update, fully charge the battery, establish an internet connection, click the update icon in the toolbar, and then reboot your Pinebook Pro. Please see [https://forum.pine64.org/showthread.php?tid=7830 this log] for details.)

Please note that PCIe, the interface used for NVMe SSD on the Pinebook Pro, is not bootable on the RK3399 and therefore is not a part of the boot hierarchy. It is possible to run the desired OS from NVMe by pointing extlinux on the eMMC to rootfs on the SSD. This requires uboot, the Kernel image, DTB, and extlinux.conf
in a /boot partition on the eMMC.

=== eMMC information ===
The eMMC appears to be hot-pluggable. This can be useful if trying to recover data or a broken install. Best practice is probably to turn the eMMC switch to off position before changing modules.

The eMMC storage will show up as multiple block devices:
*mmcblk1boot0 - eMMC standard boot0 partition, may be 4MB
*mmcblk1boot1 - eMMC standard boot1 partition, may be 4MB
*mmcblk1rpmb - eMMC standard secure data partition, may be 16MB
*mmcblk1 - This block contains the user areas

Only the last is usable as regular storage device in the Pinebook Pro.
The device number of "1" shown above may vary, depending on kernel.

If the eMMC module is enabled after boot from an SD card, you can detect this change with the following command:
<pre>
echo 'fe330000.sdhci' | tee /sys/bus/platform/drivers/sdhci-arasan/unbind
echo 'fe330000.sdhci' | tee /sys/bus/platform/drivers/sdhci-arasan/bind
</pre>

=== Boot sequence details ===
The RK3399's mask 32KB ROM boot code looks for the next stage of code at byte off-set 32768, (sector 64 if using 512 byte sectors). This is where U-Boot code would reside on any media that is bootable.

== Pinebook Pro Dimensions ==
* Dimensions: 329mm x 220mm x 12mm (WxDxH)
* Weight: 1.26Kg
* Screws
** Philips head type screws
** M2 flat head machine screws (measurements in mm)
** 4 x Small screws (used along the front edge): Head - 3.44, Thread Diameter - 1.97, Thread Length - 2.1, Overall length - 3.05
** 6 x Large screws: Head - 3.44, Thread Diameter - 1.97, Thread Length - 4.41, Overall Length - 5.85
* Rubber Feet
** 18mm diameter
** 3mm height
** Dome shaped

== SoC and Memory Specification ==
[[File:Rockchip_RK3399.png|right]]
* Based on Rockchip RK3399

=== CPU Architecture ===
* big.LITTLE architecture: Dual Cortex-A72 + Quad Cortex-A53, 64-bit CPU
** Full implementation of the ARM architecture v8-A instruction set (both AArch64 and AArch32)
** ARM Neon Advanced SIMD (single instruction, multiple data) support for accelerated media and signal processing computation
** ARMv8 Cryptography Extensions
** VFPv4 floating point unit supporting single and double-precision operations
** Hardware virtualization support
** TrustZone technology support
** Full CoreSight debug solution
** One isolated voltage domain to support DVFS
* Cortex-A72 (big cluster):
** [https://developer.arm.com/products/processors/cortex-a/cortex-a72 Dual-core Cortex-A72 up to 2.0GHz CPU]
** Superscalar, variable-length, out-of-order pipeline
** L1 cache 48KB Icache and 32KB Dcache for each A72
** L2 cache 1024KB for big cluster
* Cortex-A53 (little cluster):
** [https://developer.arm.com/products/processors/cortex-a/cortex-a53 Quad-core Cortex-A53 up to 1.5GHz CPU]
** In-order pipeline with symmetric dual-issue of most instructions
** L1 cache 32KB Icache and 32KB Dcache for each A53
** L2 cache 512KB for little cluster
* Cortex-M0 (control processors):
** [https://developer.arm.com/ip-products/processors/cortex-m/cortex-m0 Cortex-M0 CPU]
** Two Cortex-M0 cooperate with the central processors
** Architecture: Armv6-M
** Thumb/Thumb2 instruction set
** 32 bit only

=== GPU Architecture ===
* [https://developer.arm.com/products/graphics-and-multimedia/mali-gpus/mali-t860-and-mali-t880-gpus ARM Mali-T860MP4 Quad-core GPU]
* The highest performance GPUs built on Arm Mali’s famous Midgard architecture, the Mali-T860 GPU is designed for complex graphics use cases and provide stunning visuals for UHD content.
* Frequency 650MHz
* Throughput 1300Mtri/s, 10.4Gpix/s
* OpenGL® ES 1.1, 1.2, 2.0, 3.1, 3.2., Vulkan 1.0*., OpenCL™ 1.1, 1.2., DirectX® 11 FL11_1., RenderScript™.

=== System Memory ===
* RAM Memory:
** LPDDR4
** Dual memory channels on the CPU, each 32 bits wide
** Quad memory channels on the RAM chip, each 16 bits wide, 2 bonded together for each CPU channel
** 4GB as a single 366 pin mobile RAM chip
* Storage Memory:
** 64GB eMMC module, can be upgraded to a 128GB eMMC module. (The initial PINE64 community build version shipped with a 128GB eMMC.)
** eMMC version 5.1, HS400, 8 bit on RK3399 side

=== Video out ===
* USB-C Alt mode DP
* Up to 3840x2160 p60, dependant on adapter, (2 lanes verses 4 lanes)

=== Expansion Ports ===
* MicroSD card:
** Bootable
** Supports SD, SDHC and SDXC cards, up to 512GB tested. SDXC standard says 2TB is the maximum.
** Version SD3.0, (MMC 4.5), up to 50MB/s
** SD card Application Performance Class 1 (A1), (or better), recommended by some users, for better IOPS
* USB ports:
** 1 x USB 2.0 Type-A Host Port, bootable
** 1 x USB 3.0 Type-A Host Port, 5Gbps, is not bootable
** 1 x USB 3.0 Type-C OTG Port, 5Gbps, (includes laptop charging function), is not bootable
** Note that high power USB devices may not work reliably on a PBP. Or they may draw enough power to drain the battery even when the PBP is plugged into A.C. One alternative is externally powered USB devices.
* Headphone jack switchable to UART console mux circuit

== Additional hardware ==
Hardware that is not part of the SoC.

=== Battery ===
* Lithium Polymer Battery (10,000 mAH)

=== Display ===
* 14.0" 1920x1080 IPS LCD panel

=== Audio ===
* 3.5mm stereo earphone/microphone plug
* Built-in stereo speakers:
** Oval in design
** 3 mm high x 20 mm x 30 mm

=== Network ===
* WiFi:
** 802.11 b/g/n/ac
** Dual band: 2.4Ghz & 5Ghz
** Single antenna
* Bluetooth 5.0

=== Optional NVMe adapter ===
* PCIe 2.x, 5GT/s per lane
* 4 PCIe lanes, can not be bifurcated, (however, can be used with 1 or 2 lane NVMe cards)
* '''M''' keyed, though '''M'''+'''B''' keyed devices will work too
* Maximum length for M.2 card is 80mm (M.2 2280). The following sizes will also work: 2230, 2242, 2260
* Power: 2.5W continuous, 8.25W peak momentary
* Does not support SATA M.2 cards
* Does not support USB M.2 cards

== Pinebook Pro Schematics and Certifications ==
* Pinebook Pro Main Board Schematic And Silkscreen:
** [http://files.pine64.org/doc/PinebookPro/pinebookpro_v2.1_mainboard_schematic.pdf Pinebook Pro Main Board ver 2.1 Schematic]
** [https://wiki.pine64.org/images/3/30/Pinebookpro-v2.1-top-ref.pdf Pinebook Pro ver 2.1 Top Layer Silkscreen]
** [https://wiki.pine64.org/images/b/b7/Pinebookpro-v2.1-bottom-ref.pdf Pinebook Pro ver 2.1 Bottom Layer Silkscreen]
* Pinebook Pro Daughter Board Schematic:
** [http://files.pine64.org/doc/PinebookPro/pinebookpro_v2.1_daughterboard_schematic.pdf Pinebook Pro Daughter Board ver 2.1 Schematic]
* Optional Pinebook Pro NVMe Adapter Schematic:
** [http://files.pine64.org/doc/PinebookPro/pinebookpro_v2.1_NVMe-adapter_schematic.pdf Pinebook Pro NVMe Adapter Board ver 2.1 Schematic]
* Serial Console Earphone Jack Pinout:
** [http://files.pine64.org/doc/pinebook/guide/Pinebook_Earphone_Serial_Console_Developer_Guide.pdf Pinkbook Serial Console Earphone Jack Pinout]
* Pinebook Pro Case:
** [https://send.firefox.com/download/b34c14f3e0a3d66d/#15Cx1vBaGKmJr57y85U2qQ AutoCAD DWG File]
* Pinebook Pro Certifications:
** [http://files.pine64.org/doc/cert/Pinebook%20Pro%20FCC%20Certificate-S19071103501001.pdf Pinebook Pro FCC Certificate]
** [http://files.pine64.org/doc/cert/Pinebook%20Pro%20CE%20RED%20Certificate-S19051404304.pdf Pinebook Pro CE Certificate]
** [http://files.pine64.org/doc/cert/Pinebook%20Pro%20ROHS%20Compliance%20Certificate.pdf Pinebook Pro RoHS Certificate]

== Datasheets for Components and Peripherals ==
* Rockchip RK3399 SoC information:
** [http://www.rock-chips.com/a/en/products/RK33_Series/2016/0419/758.html Rockchip RK3399 SoC Brief]
** [http://opensource.rock-chips.com/images/d/d7/Rockchip_RK3399_Datasheet_V2.1-20200323.pdf Rockchip RK3399 Datasheet V2.1]
** [http://opensource.rock-chips.com/images/e/ee/Rockchip_RK3399TRM_V1.4_Part1-20170408.pdf Rockchip RK3399 Technical Reference Manual part 1]
** [http://files.pine64.org/doc/datasheet/rockpro64/RK808%20datasheet%20V0.8.pdf Rockchip RK808 Datasheet V0.8]
* LPDDR4 (366 Balls) SDRAM:
** [http://files.pine64.org/doc/datasheet/PinebookPro/micron%20SM512M64Z01MD4BNK-053FT%20LPDDR4%20(366Ball).pdf Micron 366 balls Mobile LPDDR4 Datasheet]
* eMMC information:
** [http://files.pine64.org/doc/rock64/PINE64_eMMC_Module_20170719.pdf PINE64 eMMC module schematic]
** [http://files.pine64.org/doc/rock64/usb%20emmc%20module%20adapter%20v2.pdf PINE64 USB adapter for eMMC module V2 schematic]
** [http://files.pine64.org/doc/rock64/USB%20adapter%20for%20eMMC%20module%20PCB.tar PINE64 USB adapter for eMMC module PCB in JPEG]
** [http://files.pine64.org/doc/datasheet/pine64/SDINADF4-16-128GB-H%20data%20sheet%20v1.13.pdf SanDisk eMMC Datasheet]
* SPI NOR Flash information:
** [http://files.pine64.org/doc/datasheet/pine64/w25q128jv%20spi%20revc%2011162016.pdf WinBond 128Mb SPI Flash Datasheet]
** [https://wiki.pine64.org/images/b/b9/Ds-00220-gd25q127c-rev1-df2f4.pdf GigaDevice 128Mb SPI Flash Datasheet (UPDATED)]
* Wireless related info:
** [http://files.pine64.org/doc/datasheet/PinebookPro/AP6256%20datasheet_V1.7_12282018.pdf AMPAK AP6256 11AC Wi-Fi + Bluetooth5 Datasheet]
* Audio Codec (ES8316)
** [http://everest-semi.com/pdf/ES8316%20PB.pdf Everest ES8316 Audio Codec]
* LCD Panel:
** [http://files.pine64.org/doc/datasheet/PinebookPro/NV140FHM-N49_Rev.P0_20160804_201710235838.pdf 14" 1920x1080 IPS LCD Panel datasheet]
* Internal USB 2 hub:
** [https://wiki.pine64.org/images/3/39/GL850G_USB_Hub_1.07.pdf GL850G USB Hub 1.07.pdf]
* Touchpad information:
** [http://files.pine64.org/doc/datasheet/PinebookPro/YX%20HK-9562%20HID%20I2C%20Specification.pdf Touchpad Specification for Pinebook Pro model]
* Keyboard information:
** [http://www.sinowealth.com/ftp/ph/SH68F83/SH68F83V2.0.pdf Sinowealth SH68F83 Datasheet]
** US ANSI: XK-HS002 MB27716023
* Full HD Camera sensor:
** [http://files.pine64.org/doc/datasheet/PinebookPro/HK-2145-263.pdf Full HD Camera module specification in Chinese]
** [http://files.pine64.org/doc/datasheet/PinebookPro/GC2145%20CSP%20DataSheet%20release%20V1.0_20131201.pdf GalaxyCore GC2145 Full HD Camera Sensor Data Sheet]
* Lithium Battery information:
** [http://files.pine64.org/doc/datasheet/pinebook/40110175P%203.8V%2010000mAh规格书-14.pdf 10000mAH Lithium Battery Specification for 14" model]
* NVMe adapter:
** [https://datasheet.octopart.com/FH26W-35S-0.3SHW%2860%29-Hirose-datasheet-26676825.pdf Compatible, not OEM! Use FH26-35S-0.3SHW flat flex connector]

== Versions ==
Pinebook Pro v1 and v2 were prototype models that did not make it to the public. The "first batch" (First 100 forum preorders) onward are v2.1. [https://forum.pine64.org/showthread.php?tid=8111]

=Skinning and Case Customization=
* Template files for creating custom skins. Each includes template layers for art placement, and CUT lines.
**[https://drive.google.com/open?id=1UKFlC53DO0GJm3Hz1E_669n_HhI45e4n Case Lid Template]
**[https://drive.google.com/open?id=1Q6bKGarMDhvWz3HdGvhL5qDhyHb546ve Case Bottom Template]
**[https://drive.google.com/open?id=1ugI74ygNJ3EN5jXks5jKvdpEAoxIzHo4 Case Palmrest Template]

= Other Resources =
* [https://forum.pine64.org/forumdisplay.php?fid=111 Pinebook Pro Forum]
* [https://forum.pine64.org/forumdisplay.php?fid=98 ROCKPro64 Forum]
* [[RockPro64 Guides]]
* [https://riot.im/app/#/room/#pinebook:matrix.org Matrix Channel] (No login required to read)
* [http://www.pine64.xyz:9090/?channels=ROCK64 ROCK64/ROCKPro64 IRC Channel]
* [https://discordapp.com/channels/463237927984693259/622348681538043924 Discord Channel]
* [https://github.com/rockchip-linux Rockchip Linux GitHub Repo]
* [http://opensource.rock-chips.com/ Rockchip Open Source Wiki]

Pinebook Pro Hardware Accessory Compatibility

2020-03-08T23:53:20Z

TuxThePenguin: /* USB C alternate mode DP */

= Pinebook Pro accessories - by type =

This page was started in the early days when not all accessories/peripherals were working.

== NVMe SSD drives ==
Note that only PCIe type M.2 drives will work. Any SATA or USB type M.2 card will NOT work.
{| class="wikitable sortable"
!Type || Make/Model || Size || Hardware IDs || Result || Notes || Power options Active only || Save power setting?
|-
| 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. || || 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 || 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 || 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 || 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.) || ||
|-
| 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 || 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 APSTE Disabled by default || N/A
|-
| 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 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||
|-
| 2242 || KingSpec NE-512 || 512 GB || NE512 || good || || APST enabled Power states N/A || N/A
|-
| 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||
|
|}

== USB hardware ==
{| 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-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/ref=ppx_yo_dt_b_search_asin_title?ie=UTF8&psc=1]
|-
|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
|-
|Yubikey original || Yubico || 1050:0010 || good ||
|-
|4 Port USB 3 NIC || Delock 62966 || || good || 4 individually controllable Gigabit Ethernet Ports. Consider using it with own power supply
|-
|USB-2 Fast Ethernet adapter || Realtek RTL8152 || 0bda:8152 || good ||
|-
|USB 3 to Gigabit Ethernet Adapter || Pluggable USB 3.0 to Ethernet Gigabit (ASIX AX88179 chipset) || 0b95:1790 || good ||
|-
|USB-C combo hub || [https://www.amazon.com/gp/product/B07XKRGQQ2/ref=ppx_yo_dt_b_asin_title_o00_s00?ie=UTF8&psc=1 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 Drawing tablet || XP Pen G430s || 28bd:0913 || good || Hardware works, with qemu usermode and some hacks it should be possible to use the official configuration software (runs but does not work on my setup for unrelated reasons) but it may also be able to be configured using more standard methods
|}

== 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 || 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 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
|}

== Other hardware ==
{| class="wikitable sortable"
!Type || Make/Model || Hardware IDs || Result || Notes
|-
|Bluetooth Mouse || HP Z5000 || E5C13AA || good ||
|-
|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 Speaker || Ivation Acoustix || || good || Use audio sink profile
|-
|Headphone || Sony WH-1000XM2 || || good* || Needs pulseaudio-module-bluetooth. *Recording untested.
|-
|Bluetooth Headphone || 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].
|-
|[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
|-
|USB Audio & Bluetooth Headset || Sony SBH90C || || good || Works well connected via USB Type-C and Bluetooth.
|-
|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.
|-
|Printer || HP DeskJet Ink Advantage 3775 || || good* || Using hplip-gui: via USB and WiFi. *Only print function tested.
|-
|}

Pinebook Pro Hardware Accessory Compatibility

2020-02-18T08:57:00Z

TuxThePenguin: Add newly tested USB device

= Pinebook Pro accessories - by type =

This page was started in the early days when not all accessories/peripherals were working.

== NVMe SSD drives ==
Note that only PCIe type M.2 drives will work. Any SATA or USB type M.2 card will NOT work.
{| class="wikitable sortable"
!Type || Make/Model || Size || Hardware IDs || Result || Notes || Power options Active only || Save power setting?
|-
| 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. || || 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 || 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 || 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 || 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.) || ||
|-
| 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 || 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 APSTE Disabled by default || N/A
|-
| 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 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||
|-
| 2242 || KingSpec NE-512 || 512 GB || NE512 || good || || APST enabled Power states N/A || N/A
|-
| 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||
|
|}

== USB hardware ==
{| 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-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/ref=ppx_yo_dt_b_search_asin_title?ie=UTF8&psc=1]
|-
|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
|-
|Yubikey original || Yubico || 1050:0010 || good ||
|-
|4 Port USB 3 NIC || Delock 62966 || || good || 4 individually controllable Gigabit Ethernet Ports. Consider using it with own power supply
|-
|USB-2 Fast Ethernet adapter || Realtek RTL8152 || 0bda:8152 || good ||
|-
|USB 3 to Gigabit Ethernet Adapter || Pluggable USB 3.0 to Ethernet Gigabit (ASIX AX88179 chipset) || 0b95:1790 || good ||
|-
|USB-C combo hub || [https://www.amazon.com/gp/product/B07XKRGQQ2/ref=ppx_yo_dt_b_asin_title_o00_s00?ie=UTF8&psc=1 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 Drawing tablet || XP Pen G430s || 28bd:0913 || good || Hardware works, with qemu usermode and some hacks it should be possible to use the official configuration software (runs but does not work on my setup for unrelated reasons) but it may also be able to be configured using more standard methods
|}

== 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 || generic || || good || Tested up to 4k60
|-
|USB-C to DP Adapter || OrxnQ || || good || Advertises support for 4K@60Hz, tested up to 1080p
|-
|USB-C HDMI adapter (DP-alt mode) || QGeeM || || good || Manjaro 2020-01-25
|-
|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.
|-
|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 || || GbE: works, HDMI: works, USB3.0 port: works, VGA: unknown || I could only test the HDMI connector with an 1080p display, so no information about 4K. ||
|}

== Other hardware ==
{| class="wikitable sortable"
!Type || Make/Model || Hardware IDs || Result || Notes
|-
|Bluetooth Mouse || HP Z5000 || E5C13AA || good ||
|-
|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 Speaker || Ivation Acoustix || || good || Use audio sink profile
|-
|Headphone || Sony WH-1000XM2 || || good* || Needs pulseaudio-module-bluetooth. *Recording untested.
|-
|[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
|-
|USB Audio & Bluetooth Headset || Sony SBH90C || || good || Works well connected via USB Type-C and Bluetooth.
|-
|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.
|-
|Printer || HP DeskJet Ink Advantage 3775 || || good* || Using hplip-gui: via USB and WiFi. *Only print function tested.
|-
|}

User:TuxThePenguin

2020-01-31T05:34:40Z

TuxThePenguin: Just some more information about me

Just another community member

I have:
* Thinkpad W540 running Arch
* Pinebook Pro ANSI running Arch
* 3 2012 Nexus 7s running Ubuntu, pmOS and Android
* Switch Lite (yet to be hacked)
* ZTE Axon 7 running LineageOS
* And some other non-Linux devices that are really boring

Ask me about why an eGPU won't work with the RK3399 :)

Pinebook Pro

2020-01-07T02:26:46Z

TuxThePenguin: Fix minor mistake in display section

Pinebook Pro

2020-01-07T02:22:27Z

TuxThePenguin: /* LCD Panel */

User:TuxThePenguin

2020-01-05T12:43:37Z

TuxThePenguin: I'm just a person, nothing special

Just another community member

I have:
* Pinebook Pro ANSI
* 3 2012 Nexus 7s
* Switch Lite (yet to be hacked)
* ZTE Axon 7
* And some other non-Linux devices that are really boring

Pinebook Pro

2020-01-04T23:10:24Z

TuxThePenguin: Extra information for LCD panel section

PineTab

2020-01-04T23:03:06Z

TuxThePenguin: General fixes for inconsistent information

PAGE UNDER CONSTRUCTION, INFO SUBJECT TO CHANGE

The PineTab is a 10" tablet created by Pine64.

== Specifications ==
* '''Dimensions:''' 11mm x 17.5mm x 26mm (Thickness, Width, Height)
* '''Weight:''' ~600-700g
* '''Build:''' Plastic
* '''Storage:'''
** 64GB of internal eMMC storage
** MicroSD slot, bootable
** M.2 SSD slot, (optional)
* '''Cameras:''' 2Mpx Front, 5Mpx Rear
* '''CPU:''' Allwinner A64 Quad Core
* '''GPU:''' Mali 400 MP2
* '''RAM:''' 2GB LPDDR3
* '''I/O:''' HD Video Out (Mini HDMI), Micro USB 2.0 OTG, USB 2.0 A host, 3.5mm Headphone/Mic combo,
* '''Network'''
** WiFi
** M.2 LTE / Cell MODEM card, (optional, and takes place of optional M.2 SSD)
* '''Screen:''' 10.1" IPS 800x1280 Capacitive LCD
* '''Attachments/Accessories:''' Magnetically attached keyboard (optional)
* '''Battery:''' 6000MAh (6Ah)
* '''Misc. features:'''
** Volume rocker and home button
** Speakers and Microphone
** 2.5mm OD Power (5V 3A) Port

== Keyboard ==
'''Overview:''' The PineTab detachable keyboard features a full function row, FN key functionality, meta key (where the Windows key would be) and all of the keys you need for daily use.

'''FN keys:''': Pause/play (F2), Stop (F3), Previous(F4), Next(F5), Music (F6), Mail (F7), Home (F8), Mute (F9), Vol- (F10), Vol+ (F11), Disable touchpad (F12), NumLock (Insert), Scroll Lock (Delete), PgUp (Up Arrow), PgDn (Down Arrow), Home (Left Arrow), End (Right Arrow), Digital Numpad (7,8,9,0,U,I,O,P,J,K,L,;,M,.,/)

== Operating Systems ==
The PineTab will automatically boot from microSD if a bootable card is inserted. Although it is technically possible to use any ARM distro (because the PineTab uses the mainline kernel), there are a few that are designed specifically for phones and tablets:
* [[#postmarketOS|postmarketOS]]
* [[#Arch Linux ARM|Arch Linux ARM]]

=== postmarketOS ===
postmarketOS is a preconfigured version of [https://www.alpinelinux.org/ Alpine Linux] for mobile devices. The latest builds can be downloaded from the [https://images.postmarketos.org/pinetab/ images page] to be flashed to the PineTab.

More information is available at [https://postmarketos.org postmarketos.org] and on their [https://wiki.postmarketos.org/wiki/PINE64_PineTab_(pine64-pinetab) dedicated PineTab wiki page].

=== Arch Linux ARM ===
Arch Linux ARM with LXQt built by Danct12 can be downloaded [https://github.com/Danct12/Pine64-Arch/releases/tag/20191207 here]