https://wiki.pine64.org/api.php?action=feedcontributions&user=Ura2&feedformat=atomPINE64 - User contributions [en]2024-03-28T10:55:29ZUser contributionsMediaWiki 1.37.1https://wiki.pine64.org/index.php?title=Pinebook_Pro_Hardware_Accessory_Compatibility&diff=10381Pinebook Pro Hardware Accessory Compatibility2021-05-16T00:32:33Z<p>Ura2: /* USB other */</p>
<hr />
<div><br />
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!<br />
<br />
= Storage =<br />
<br />
== NVMe SSD drives ==<br />
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.<br />
<br />
You need to buy and install the M.2 adaptor in order to fit one, please see [[Pinebook_Pro#Using_the_optional_NVMe_adapter]]<br />
<br />
Please see [[Pinebook Pro Troubleshooting Guide#NVMe SSD issues|a separate section]] that describes reported issues with the NVMe drives in PineBook Pro.<br />
<br />
{| class="wikitable sortable"<br />
!Type || Make/Model || Size || Hardware IDs || Result || Notes || Power options<br/>Active only || Save<br/>power<br/>setting?<br />
|-<br />
| 2280 || Kingston A2000 || 250 GB || SA2000M8250G || good || || PS 0: 9.00W<br/>PS 1: 4.60W<br/>PS 2: 3.80W<br/>PS 3: 0.045W<br/>PS 4: 0.004W<br/>APSTE: enabled by default || Yes<br />
|-<br />
| 2280 || Kingston A2000 || 1 TB || SA2000M81000G || good || || same as 250 GB || Yes<br />
|-<br />
| 2242 || Toshiba OCZ RC 100 || 240 GB || RC100-M22242-240G || good || || ||<br />
|-<br />
| 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<br/>PS 1: 2.44W<br/>PS 2: 2.02W || No. See [https://forum.pine64.org/showthread.php?tid=8737&pid=56481#pid56481 workaround].<br />
|-<br />
| 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. || ||<br />
|-<br />
| 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<br/>PS 1: 2.70W<br/>PS 2: 2.00W || No <br />
|-<br />
| 2280 || Intel 660p M.2 || 1 TB || SSDPEKNW010T8X1 || good || || PS 0: 4.00W<br/>PS 1: 3.00W<br/>PS 2: 2.20W<br/>APSTE Disabled by default || No<br />
|-<br />
| 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<br/>PS 1: 3.60W<br/>PS 2: 2.60W<br/>PS 3: 0.0300W<br/>PS 4: 0.0040W || No<br />
|-<br />
| 2280 || Intel 760p M.2 || 128 GB || SSDPEKKW128G8 || good || Firmware Revision 004C || PS 0: 9.00W<br/>PS 1: 4.60W<br/>PS 2: 3.80W<br/>PS 3: 0.045W<br/>PS 4: 0.004W<br/>APSTE: disabled by default with 4.4 kernel (mrfixit Debian), enabled by default with 5.6 kernel (Manjaro KDE) || Yes<br />
|-<br />
| 2280 || Intel 760p M.2 || 256 GB || SSDPEKKW256G8 || good || Firmware Revision 004C || PS 0: 9.00W<br/>PS 1: 4.60W<br/>PS 2: 3.80W<br/>PS 3: 0.045W<br/>PS 4: 0.004W<br/>Need to use lower power. || <br />
|-<br />
| 2280 || integral 256GB SSD M.2 2280 NVME || 256 GB || INSSD256GM280NM1 || usable || || PS 0: 9.00W || No<br />
|-<br />
| 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. || ||<br />
|-<br />
| 2280 || Samsung 970 EVO Plus || 500 GB || MZ-V7S500 || fail || Too power hungry? || PS 0: 6.2W<br/>PS 1: 4.3W<br/>PS 2: 2.1W ||<br />
|-<br />
| 2280 || Samsung 970 EVO || 1 TB || MZ-V7E1T0BW || fail || Too power hungry? || ||<br />
|-<br />
| 2280 || Samsung 970 PRO || 1 TB || MZ-V7P1T0BW || good || || PS 0: 6.20W<br/>PS 1: 4.30W<br/>PS 2: 2.10W<br/>PS 3: 0.04W<br/>PS 4: 0.005W<br/>APSTE: enabled by default || Yes<br />
|-<br />
| 2280 || Corsair MP300 || 120 GB || CSSD-F120GBMP300 || good || || PS 0: 3.00W<br/>PS 1: 2.00W<br/>PS 2: 2.00W<br/>PS 3: 0.1W<br/>PS 4: 0.005W<br/>APSTE Disabled by default ||<br />
|-<br />
| 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<br />
|-<br />
| 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<br/> PS 1: 5.71W<br/> PS 2: 5.19W<br/>APSTE Enabled by default || No<br />
|-<br />
| 2280 || Silicon Power P34A60 || 256 GB || ??? || fail || Isn't detected || ||<br />
|-<br />
| 2280 || Sabrent Rocket || 256 GB || SB-ROCKET-256 || good || || || No<br />
|-<br />
| 2242 || Sabrent Rocket Nano || 512 GB || SB-1342-512 || good* || No touchpad issues, didn't trim NVME adapter board.<br/>(*Might be too power hungry. More testing needed.) || ||<br />
|-<br />
| 2242 || Sabrent Rocket || 1 TB || SB-RKTQ-1TB || good || || PS 0: 5.55W<br/>PS 1: 4.49W<br/>PS 2: 3.97W<br/>PS 3: 0.049W<br/>PS 4: 0.0018W<br/>APSTE: available || Yes<br />
|-<br />
| 2280 || MyDigitalSSD SBXe || 960 GB || || good || || APST enabled<br/>Power states N/A || N/A <br />
|-<br />
| 2280 || HP SSD EX900 || 250GB || || good || No low-power modes available || || <br />
|-<br />
| 2280 || HP SSD EX950 || 512GB || || good || Unsure about low-power modes || || <br />
|-<br />
| 2280 || WD BLUE SN550 || 1TB || WDC WDS100T2B0C-00PXH0 || WARNING <br />good || WARNING mine was SATA and does NOT work!<br /> Booted successfully from NVMe (Bionic MATE) || PS 0: 3.50W<br/>PS 1: 2.70W<br/>PS 2: 1.90W<br/>APSTE Disabled by default || N/A <br />
|-<br />
| 2280 || WD Blue SN550 || 500GB || WDC WDS500G2B0C-00PXH0 || good || || PS 0: 3.50W<br/>PS 1: 2.40W<br/>PS 2: 1.90W<br/>APSTE enabled by default with 5.9 kernel (Manjaro XFCE) || No ||<br />
|-<br />
| 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 || ||<br />
|-<br />
<br />
| 2242 || WD PC SN520 || 256GB || - || fail || Power LED Flashes. Nothing else happens. || ||<br />
|-<br />
| 2280 || WD PC SN730 || 512GB || SDBPNTY-512G-1032 || fail || No touchpad issues. Could not bring SSD out of PS 3. ||APST enabled by default<br/>PS 0: 5.50W<br/>PS 1: 3.50W<br/>PS 2: 3.00W<br/>PS 3: 0.0700W<br/>PS 4: 0.0025W || No ||<br />
|-<br />
| 2280 || WD BLACK SN750 || 250GB || WDS250G3X0C-00SJG0 || good || No touchpad issues, didn't trim NVME adapter board. || APSTE disabled by default<br/> PS 0: 5.00W<br/>PS 1: 3.50W<br/>PS 2: 3.00W||<br />
|-<br />
| 2280 || WD BLACK SN750 || 500GB || WDS500G3X0C-00SJG0 || good || No tp issues. had to charge battery for 20% initially. || APSTE disabled by default<br/> PS 0: 5.50W<br/>PS 1: 3.50W<br/>PS 2: 3.00W<br/>PS 3: 0.07W<br/>PS 4: 0.0025W||<br />
|-<br />
| 2280 || WD BLACK SN750 || 1TB || WDS100T3X0C-00SJG0 || mixed || Drive works as expected (so far) though with 50% reduction in battery life.<br/><br/>Unable to set power mode (due to APST being enabled?).<br/><br/>Also unable to suspend PineBook Pro with NVMe drive attached. From dmesg:<br/>rockchip-pcie f8000000.pcie: PCIe link enter L2 timeout!<br/>PM: dpm_run_callback(): rockchip_pcie_suspend_noirq+0x0/0x100 returns -110<br/>PM: Devvice f8000000.pcie failed to suspend noirq: error -110<br/>PM: no irq suspend of devices failed<br/> || APST enabled by default<br/> PS 0: 6.00W<br/>PS 1: 3.50W<br/>PS 2: 3.00W<br/>PS 3: 0.1000W<br/>PS 4: 0.0025W || No<br />
|-<br />
| 2242 || KingSpec NE-512 || 512 GB || NE512 || good || || APST enabled<br/>Power states N/A || N/A <br />
|-<br />
| 2230 || Kioxia BG4 256GBTB|| 256 GB || KBG40ZNS256G || good || || APST enabled by default<br/>Power states PS 0: 3.60W<br/>PS 1: 2.60W<br/>PS 2: 2.20W<br/>PS 3: 0.005W<br/>PS 4: 0.005W ||<br />
|-<br />
| 2280 || Patriot P300 || 256 GB || P300P256GM28US || good || Booted successfully with / on NVMe and /boot on eMMC (Armbian Buster) || APSTE disabled by default<br/> PS 0: 4.50W<br/> PS 1: 2.70W<br/> PS 2: 2.16W<br/>PS 3: 0.07W<br/>PS 4: 0.002W||<br />
|-<br />
| 2280 || Team Group MP33 || 128 GB || TM8FP6128G0C101 || good || || ||<br />
|-<br />
| 2280 || Team Group MP34 || 512 GB || TM8FP6512G0C101 || fail ||APST enabled by default and scripts do not change the power mode. <br>Higher power consumption modes cause the PBP to crash<br/> || PS 0 5.55W <br/>PS 1 4.49W<br/>PS 2 3.97W <br/>PS 3 0.0490W <br/>PS 4 0.0018W ||No<br />
|-<br />
| 2280 || Digifast Ace || 256 GB || DGFA256M2L01 || good ||No touchpad issues. Board not trimmed. || PS 0 6.77W <br/>PS 1 5.71W<br/>PS 2 5.19W <br/>PS 3 0.0490W <br/>PS 4 0.0018W ||Yes<br />
<br />
|}<br />
<br />
== microSD Cards ==<br />
{| class="wikitable sortable"<br />
!Type || Make/Model || Hardware IDs || Result || Notes<br />
|-<br />
|SD Card || Samsung Evo Select 512GB || MB-ME512GA/AM || good ||<br />
|-<br />
|SD Card || Samsung Evo Plus 64GB || || good || Hdparm tested 44MBps read speeds<br />
|-<br />
|SD Card || Sandisk Ultra 400GB || || good || Works fine as a storage extension. Mounted for pictures, etc.<br />
|-<br />
|SD Card || Sandisk Ultra 16GB || || fail || Works for a short period of time but locks up completely after a certain amount of written data<br />
|-<br />
|SD Card || Sandisk Ultra 64GB (Old from 2015) || || fail || ^<br />
|-<br />
|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<br />
|-<br />
|SD Card || Sandisk Extreme Pro 64GB || || good || <br />
|}<br />
<br />
= USB hardware =<br />
<br />
== USB Card Readers ==<br />
<br />
Standalone card readers only, please; see below for multifunction devices.<br />
<br />
{| class="wikitable sortable"<br />
!Type || Make/Model || Hardware IDs || Result || Notes<br />
|-<br />
|USB-2 SDHC reader || Sandisk MobileMate+ || 0781:b2b3 || good ||<br />
|-<br />
|USB-3 SDHC/CF reader || Transcend TS-RDF8K || 8564:4000 || good ||<br />
|}<br />
<br />
== USB Networking ==<br />
<br />
Standalone network devices only, please; see below for multifunction devices<br />
<br />
{| class="wikitable sortable"<br />
!Type || Make/Model || Hardware IDs || Result || Notes<br />
|-<br />
|USB-2 Fast Ethernet adapter || Realtek RTL8152 || 0bda:8152 || good || <br />
|-<br />
|USB-2 Ethernet adapter || ASIX AX77882 || 0b95:7720 || good || <br />
|-<br />
|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/<br />
|-<br />
|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/<br />
|-<br />
|USB 3 to Gigabit Ethernet Adapter || Pluggable USB 3.0 to Ethernet Gigabit (ASIX AX88179 chipset) || 0b95:1790 || good ||<br />
|}<br />
<br />
== USB Multifunction Devices ==<br />
<br />
{| class="wikitable sortable"<br />
!Type || Make/Model || Hardware IDs || Result || Notes<br />
|-<br />
|USB-C Hub || Samsung EE-P5000 || || Power is passed through from hub to Pinebook Pro; Ethernet, HDMI, and USB-A do not work || <br />
|-<br />
|USB-C Hub || Insignia NS-PU378CHM || || Power is passed through from hub to Pinebook Pro; USB-A works; HDMI does not work || <br />
|-<br />
|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 || <br />
|-<br />
|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/]<br />
|-<br />
|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]<br />
|-<br />
|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 ||<br />
|-<br />
|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 ||<br />
|-<br />
|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 <br />
|- <br />
|4 Port USB 3 NIC || Delock 62966 || || good || 4 individually controllable Gigabit Ethernet Ports. Consider using it with own power supply<br />
|-<br />
|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.<br />
|-<br />
|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.<br />
|-<br />
|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.<br />
|-<br />
|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<br />
|-<br />
|USB-C dock || Lenovo ThinkPad 40A9 || TBD || mixed || USB hub works, audio device works, ethernet device works, display does NOT despite plug's orientation<br />
|}<br />
<br />
== USB C alternate mode DP ==<br />
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.<br />
{| class="wikitable sortable"<br />
!Type || Make/Model || Hardware IDs || Result || Notes<br />
|-<br />
|USB-C to HDMI adapter 201018 || Cable Matters || || good || Tested up to 1080p30, audio works<br />
|-<br />
|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<br />
|-<br />
|USB-C to HDMI adapter || generic || || good || Tested up to 4k60<br />
|-<br />
|USB-C to DP Adapter || OrxnQ || 04b4:5210 || good || Advertises support for 4K@60Hz, tested up to 1080p. Only FullHD resolutions available on Debian.<br />
|-<br />
|USB-C HDMI adapter (DP-alt mode) || QGeeM || || good || Manjaro 2020-01-25<br />
|-<br />
|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/<br />
|-<br />
|USB-C combo hub (HDMI, network, card slots, USB ports) || generic || || fail ||<br />
|-<br />
|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<br />
|-<br />
|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.<br />
|-<br />
|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<br />
|- <br />
|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<br />
|-<br />
|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 <br />
|-<br />
|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<br />
|-<br />
|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.<br />
|-<br />
|USB-C to HDMI adapter || MHL TH002 || || good || Tested at 1080p@60<br />
|-<br />
|USB-C combo hub (USB-C power, HDMI, 2xUSB, 1xUSB-C(no power)) || Baseus || || good<br />
|-<br />
|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.) <br />
|-<br />
|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. <br />
|-<br />
|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<br />
|-<br />
|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.<br />
|-<br />
|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.<br />
|-<br />
|USB-C to DP cable || [https://www.amazon.es/gp/product/B01N5RFAI4/ CHOETECH V-XCP-0012BK] || || good <br />
|-<br />
| [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<br />
|-<br />
|USB-C to HDMI cable || Planet Computers USB-C to HDMI cable || || fail || does not work regardless of orientation in USB slot<br />
|-<br />
|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<br />
|-<br />
|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)<br />
|-<br />
| 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<br />
|}<br />
<br />
== USB other ==<br />
{| class="wikitable sortable"<br />
!Type || Make/Model || Hardware IDs || Result || Notes<br />
|-<br />
|Wireless Mouse || Logitech M705 Marathon || || good || Uses Logitech receiver. Battery level detected in power settings.<br />
|-<br />
|Wireless Mouse || Logitech G305 || || good || Uses Logitech receiver<br />
|-<br />
|Gamepad || Sertronics SNES Style Controller || || good || Tested in retroarch, Sertronics is also known as Berrybase<br />
|-<br />
|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<br />
|-<br />
|Yubikey original || Yubico || 1050:0010 || good ||<br />
|-<br />
|}<br />
<br />
----<br />
<br />
= Bluetooth hardware =<br />
{| class="wikitable sortable"<br />
!Type || Make/Model || Hardware IDs || Result || Notes <br />
|-<br />
|Bluetooth Mouse || HP Z5000 || E5C13AA || good || <br />
|-<br />
|Bluetooth Mouse || Logitech M557 || || good || <br />
|-<br />
|Bluetooth Mouse || Kensington Expert Wireless Trackball || || good ||<br />
|-<br />
|Bluetooth Mouse || Logitech MX Vertical || || good || Battery level is not detected over bluetooth, detected when using the logitech receiver<br />
|-<br />
|Bluetooth Mouse || Logitech Triathlon M720 || || good ||<br />
|-<br />
|Bluetooth Mouse || Logitech Ultra-Thin Touch Mouse || || good || Detects battery level as "keyboard"<br />
|-<br />
|Bluetooth Mouse || Logitech MX Anywhere 2 || || good ||<br />
|-<br />
|Bluetooth Mouse || Logitech M535 || 910-004432 || good ||<br />
|-<br />
|Bluetooth Mouse || Microsoft Bluetooth Mouse || RJN-00002 || good ||<br />
|-<br />
|Bluetooth Mouse || Fenifox low profile || MX106-Black || good ||<br />
|-<br />
|Bluetooth Mouse || Technet || MGS479 || good ||<br />
|-<br />
|Bluetooth Keyboard || Logitech MX Keys || || good || Battery level is not detected over bluetooth, detected when using the logitech receiver<br />
|-<br />
|Bluetooth Speaker || Ivation Acoustix || || good || Use audio sink profile<br />
|-<br />
|Bluetooth Headphones || Sony WH-1000XM2 || || good* || Needs pulseaudio-module-bluetooth. *Recording untested.<br />
|-<br />
|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].<br />
|-<br />
|USB Audio & Bluetooth Headset || Sony SBH90C || || good || Works well connected via USB Type-C and Bluetooth.<br />
|-<br />
|Bluetooth Headset || BlueAnt Ribbon || 7252A-RB || good || a2dp mode works, headset mode seems to work, out of box with manjaro<br />
|-<br />
|Bluetooth Headphones || DO-SV-BTIES03 || || good || Tested on Manjaro ARM - kde<br />
|-<br />
|Bluetooth Headset || TaoTronics TT-BH090 || || good || Microphone not tested but should work as expected of a normal Linux machine<br />
|-<br />
|Bluetooth Mouse || Logitech MX Ergo || || good || Works flawlessly both on Manjaro and Armbian.<br />
|}<br />
<br />
----<br />
<br />
= Other hardware =<br />
<br />
{| class="wikitable sortable"<br />
!Type || Make/Model || Hardware IDs || Result || Notes<br />
|-<br />
|[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<br />
|-<br />
|Printer || HP DeskJet Ink Advantage 3775 || || good* || Using hplip-gui: via USB and WiFi. *Only print function tested.<br />
|-<br />
|}<br />
<br />
[[Category:PineBook Pro]]</div>Ura2https://wiki.pine64.org/index.php?title=Pinebook_Pro_Hardware_Accessory_Compatibility&diff=10380Pinebook Pro Hardware Accessory Compatibility2021-05-16T00:31:51Z<p>Ura2: /* USB other */</p>
<hr />
<div><br />
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!<br />
<br />
= Storage =<br />
<br />
== NVMe SSD drives ==<br />
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.<br />
<br />
You need to buy and install the M.2 adaptor in order to fit one, please see [[Pinebook_Pro#Using_the_optional_NVMe_adapter]]<br />
<br />
Please see [[Pinebook Pro Troubleshooting Guide#NVMe SSD issues|a separate section]] that describes reported issues with the NVMe drives in PineBook Pro.<br />
<br />
{| class="wikitable sortable"<br />
!Type || Make/Model || Size || Hardware IDs || Result || Notes || Power options<br/>Active only || Save<br/>power<br/>setting?<br />
|-<br />
| 2280 || Kingston A2000 || 250 GB || SA2000M8250G || good || || PS 0: 9.00W<br/>PS 1: 4.60W<br/>PS 2: 3.80W<br/>PS 3: 0.045W<br/>PS 4: 0.004W<br/>APSTE: enabled by default || Yes<br />
|-<br />
| 2280 || Kingston A2000 || 1 TB || SA2000M81000G || good || || same as 250 GB || Yes<br />
|-<br />
| 2242 || Toshiba OCZ RC 100 || 240 GB || RC100-M22242-240G || good || || ||<br />
|-<br />
| 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<br/>PS 1: 2.44W<br/>PS 2: 2.02W || No. See [https://forum.pine64.org/showthread.php?tid=8737&pid=56481#pid56481 workaround].<br />
|-<br />
| 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. || ||<br />
|-<br />
| 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<br/>PS 1: 2.70W<br/>PS 2: 2.00W || No <br />
|-<br />
| 2280 || Intel 660p M.2 || 1 TB || SSDPEKNW010T8X1 || good || || PS 0: 4.00W<br/>PS 1: 3.00W<br/>PS 2: 2.20W<br/>APSTE Disabled by default || No<br />
|-<br />
| 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<br/>PS 1: 3.60W<br/>PS 2: 2.60W<br/>PS 3: 0.0300W<br/>PS 4: 0.0040W || No<br />
|-<br />
| 2280 || Intel 760p M.2 || 128 GB || SSDPEKKW128G8 || good || Firmware Revision 004C || PS 0: 9.00W<br/>PS 1: 4.60W<br/>PS 2: 3.80W<br/>PS 3: 0.045W<br/>PS 4: 0.004W<br/>APSTE: disabled by default with 4.4 kernel (mrfixit Debian), enabled by default with 5.6 kernel (Manjaro KDE) || Yes<br />
|-<br />
| 2280 || Intel 760p M.2 || 256 GB || SSDPEKKW256G8 || good || Firmware Revision 004C || PS 0: 9.00W<br/>PS 1: 4.60W<br/>PS 2: 3.80W<br/>PS 3: 0.045W<br/>PS 4: 0.004W<br/>Need to use lower power. || <br />
|-<br />
| 2280 || integral 256GB SSD M.2 2280 NVME || 256 GB || INSSD256GM280NM1 || usable || || PS 0: 9.00W || No<br />
|-<br />
| 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. || ||<br />
|-<br />
| 2280 || Samsung 970 EVO Plus || 500 GB || MZ-V7S500 || fail || Too power hungry? || PS 0: 6.2W<br/>PS 1: 4.3W<br/>PS 2: 2.1W ||<br />
|-<br />
| 2280 || Samsung 970 EVO || 1 TB || MZ-V7E1T0BW || fail || Too power hungry? || ||<br />
|-<br />
| 2280 || Samsung 970 PRO || 1 TB || MZ-V7P1T0BW || good || || PS 0: 6.20W<br/>PS 1: 4.30W<br/>PS 2: 2.10W<br/>PS 3: 0.04W<br/>PS 4: 0.005W<br/>APSTE: enabled by default || Yes<br />
|-<br />
| 2280 || Corsair MP300 || 120 GB || CSSD-F120GBMP300 || good || || PS 0: 3.00W<br/>PS 1: 2.00W<br/>PS 2: 2.00W<br/>PS 3: 0.1W<br/>PS 4: 0.005W<br/>APSTE Disabled by default ||<br />
|-<br />
| 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<br />
|-<br />
| 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<br/> PS 1: 5.71W<br/> PS 2: 5.19W<br/>APSTE Enabled by default || No<br />
|-<br />
| 2280 || Silicon Power P34A60 || 256 GB || ??? || fail || Isn't detected || ||<br />
|-<br />
| 2280 || Sabrent Rocket || 256 GB || SB-ROCKET-256 || good || || || No<br />
|-<br />
| 2242 || Sabrent Rocket Nano || 512 GB || SB-1342-512 || good* || No touchpad issues, didn't trim NVME adapter board.<br/>(*Might be too power hungry. More testing needed.) || ||<br />
|-<br />
| 2242 || Sabrent Rocket || 1 TB || SB-RKTQ-1TB || good || || PS 0: 5.55W<br/>PS 1: 4.49W<br/>PS 2: 3.97W<br/>PS 3: 0.049W<br/>PS 4: 0.0018W<br/>APSTE: available || Yes<br />
|-<br />
| 2280 || MyDigitalSSD SBXe || 960 GB || || good || || APST enabled<br/>Power states N/A || N/A <br />
|-<br />
| 2280 || HP SSD EX900 || 250GB || || good || No low-power modes available || || <br />
|-<br />
| 2280 || HP SSD EX950 || 512GB || || good || Unsure about low-power modes || || <br />
|-<br />
| 2280 || WD BLUE SN550 || 1TB || WDC WDS100T2B0C-00PXH0 || WARNING <br />good || WARNING mine was SATA and does NOT work!<br /> Booted successfully from NVMe (Bionic MATE) || PS 0: 3.50W<br/>PS 1: 2.70W<br/>PS 2: 1.90W<br/>APSTE Disabled by default || N/A <br />
|-<br />
| 2280 || WD Blue SN550 || 500GB || WDC WDS500G2B0C-00PXH0 || good || || PS 0: 3.50W<br/>PS 1: 2.40W<br/>PS 2: 1.90W<br/>APSTE enabled by default with 5.9 kernel (Manjaro XFCE) || No ||<br />
|-<br />
| 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 || ||<br />
|-<br />
<br />
| 2242 || WD PC SN520 || 256GB || - || fail || Power LED Flashes. Nothing else happens. || ||<br />
|-<br />
| 2280 || WD PC SN730 || 512GB || SDBPNTY-512G-1032 || fail || No touchpad issues. Could not bring SSD out of PS 3. ||APST enabled by default<br/>PS 0: 5.50W<br/>PS 1: 3.50W<br/>PS 2: 3.00W<br/>PS 3: 0.0700W<br/>PS 4: 0.0025W || No ||<br />
|-<br />
| 2280 || WD BLACK SN750 || 250GB || WDS250G3X0C-00SJG0 || good || No touchpad issues, didn't trim NVME adapter board. || APSTE disabled by default<br/> PS 0: 5.00W<br/>PS 1: 3.50W<br/>PS 2: 3.00W||<br />
|-<br />
| 2280 || WD BLACK SN750 || 500GB || WDS500G3X0C-00SJG0 || good || No tp issues. had to charge battery for 20% initially. || APSTE disabled by default<br/> PS 0: 5.50W<br/>PS 1: 3.50W<br/>PS 2: 3.00W<br/>PS 3: 0.07W<br/>PS 4: 0.0025W||<br />
|-<br />
| 2280 || WD BLACK SN750 || 1TB || WDS100T3X0C-00SJG0 || mixed || Drive works as expected (so far) though with 50% reduction in battery life.<br/><br/>Unable to set power mode (due to APST being enabled?).<br/><br/>Also unable to suspend PineBook Pro with NVMe drive attached. From dmesg:<br/>rockchip-pcie f8000000.pcie: PCIe link enter L2 timeout!<br/>PM: dpm_run_callback(): rockchip_pcie_suspend_noirq+0x0/0x100 returns -110<br/>PM: Devvice f8000000.pcie failed to suspend noirq: error -110<br/>PM: no irq suspend of devices failed<br/> || APST enabled by default<br/> PS 0: 6.00W<br/>PS 1: 3.50W<br/>PS 2: 3.00W<br/>PS 3: 0.1000W<br/>PS 4: 0.0025W || No<br />
|-<br />
| 2242 || KingSpec NE-512 || 512 GB || NE512 || good || || APST enabled<br/>Power states N/A || N/A <br />
|-<br />
| 2230 || Kioxia BG4 256GBTB|| 256 GB || KBG40ZNS256G || good || || APST enabled by default<br/>Power states PS 0: 3.60W<br/>PS 1: 2.60W<br/>PS 2: 2.20W<br/>PS 3: 0.005W<br/>PS 4: 0.005W ||<br />
|-<br />
| 2280 || Patriot P300 || 256 GB || P300P256GM28US || good || Booted successfully with / on NVMe and /boot on eMMC (Armbian Buster) || APSTE disabled by default<br/> PS 0: 4.50W<br/> PS 1: 2.70W<br/> PS 2: 2.16W<br/>PS 3: 0.07W<br/>PS 4: 0.002W||<br />
|-<br />
| 2280 || Team Group MP33 || 128 GB || TM8FP6128G0C101 || good || || ||<br />
|-<br />
| 2280 || Team Group MP34 || 512 GB || TM8FP6512G0C101 || fail ||APST enabled by default and scripts do not change the power mode. <br>Higher power consumption modes cause the PBP to crash<br/> || PS 0 5.55W <br/>PS 1 4.49W<br/>PS 2 3.97W <br/>PS 3 0.0490W <br/>PS 4 0.0018W ||No<br />
|-<br />
| 2280 || Digifast Ace || 256 GB || DGFA256M2L01 || good ||No touchpad issues. Board not trimmed. || PS 0 6.77W <br/>PS 1 5.71W<br/>PS 2 5.19W <br/>PS 3 0.0490W <br/>PS 4 0.0018W ||Yes<br />
<br />
|}<br />
<br />
== microSD Cards ==<br />
{| class="wikitable sortable"<br />
!Type || Make/Model || Hardware IDs || Result || Notes<br />
|-<br />
|SD Card || Samsung Evo Select 512GB || MB-ME512GA/AM || good ||<br />
|-<br />
|SD Card || Samsung Evo Plus 64GB || || good || Hdparm tested 44MBps read speeds<br />
|-<br />
|SD Card || Sandisk Ultra 400GB || || good || Works fine as a storage extension. Mounted for pictures, etc.<br />
|-<br />
|SD Card || Sandisk Ultra 16GB || || fail || Works for a short period of time but locks up completely after a certain amount of written data<br />
|-<br />
|SD Card || Sandisk Ultra 64GB (Old from 2015) || || fail || ^<br />
|-<br />
|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<br />
|-<br />
|SD Card || Sandisk Extreme Pro 64GB || || good || <br />
|}<br />
<br />
= USB hardware =<br />
<br />
== USB Card Readers ==<br />
<br />
Standalone card readers only, please; see below for multifunction devices.<br />
<br />
{| class="wikitable sortable"<br />
!Type || Make/Model || Hardware IDs || Result || Notes<br />
|-<br />
|USB-2 SDHC reader || Sandisk MobileMate+ || 0781:b2b3 || good ||<br />
|-<br />
|USB-3 SDHC/CF reader || Transcend TS-RDF8K || 8564:4000 || good ||<br />
|}<br />
<br />
== USB Networking ==<br />
<br />
Standalone network devices only, please; see below for multifunction devices<br />
<br />
{| class="wikitable sortable"<br />
!Type || Make/Model || Hardware IDs || Result || Notes<br />
|-<br />
|USB-2 Fast Ethernet adapter || Realtek RTL8152 || 0bda:8152 || good || <br />
|-<br />
|USB-2 Ethernet adapter || ASIX AX77882 || 0b95:7720 || good || <br />
|-<br />
|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/<br />
|-<br />
|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/<br />
|-<br />
|USB 3 to Gigabit Ethernet Adapter || Pluggable USB 3.0 to Ethernet Gigabit (ASIX AX88179 chipset) || 0b95:1790 || good ||<br />
|}<br />
<br />
== USB Multifunction Devices ==<br />
<br />
{| class="wikitable sortable"<br />
!Type || Make/Model || Hardware IDs || Result || Notes<br />
|-<br />
|USB-C Hub || Samsung EE-P5000 || || Power is passed through from hub to Pinebook Pro; Ethernet, HDMI, and USB-A do not work || <br />
|-<br />
|USB-C Hub || Insignia NS-PU378CHM || || Power is passed through from hub to Pinebook Pro; USB-A works; HDMI does not work || <br />
|-<br />
|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 || <br />
|-<br />
|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/]<br />
|-<br />
|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]<br />
|-<br />
|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 ||<br />
|-<br />
|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 ||<br />
|-<br />
|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 <br />
|- <br />
|4 Port USB 3 NIC || Delock 62966 || || good || 4 individually controllable Gigabit Ethernet Ports. Consider using it with own power supply<br />
|-<br />
|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.<br />
|-<br />
|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.<br />
|-<br />
|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.<br />
|-<br />
|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<br />
|-<br />
|USB-C dock || Lenovo ThinkPad 40A9 || TBD || mixed || USB hub works, audio device works, ethernet device works, display does NOT despite plug's orientation<br />
|}<br />
<br />
== USB C alternate mode DP ==<br />
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.<br />
{| class="wikitable sortable"<br />
!Type || Make/Model || Hardware IDs || Result || Notes<br />
|-<br />
|USB-C to HDMI adapter 201018 || Cable Matters || || good || Tested up to 1080p30, audio works<br />
|-<br />
|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<br />
|-<br />
|USB-C to HDMI adapter || generic || || good || Tested up to 4k60<br />
|-<br />
|USB-C to DP Adapter || OrxnQ || 04b4:5210 || good || Advertises support for 4K@60Hz, tested up to 1080p. Only FullHD resolutions available on Debian.<br />
|-<br />
|USB-C HDMI adapter (DP-alt mode) || QGeeM || || good || Manjaro 2020-01-25<br />
|-<br />
|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/<br />
|-<br />
|USB-C combo hub (HDMI, network, card slots, USB ports) || generic || || fail ||<br />
|-<br />
|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<br />
|-<br />
|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.<br />
|-<br />
|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<br />
|- <br />
|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<br />
|-<br />
|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 <br />
|-<br />
|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<br />
|-<br />
|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.<br />
|-<br />
|USB-C to HDMI adapter || MHL TH002 || || good || Tested at 1080p@60<br />
|-<br />
|USB-C combo hub (USB-C power, HDMI, 2xUSB, 1xUSB-C(no power)) || Baseus || || good<br />
|-<br />
|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.) <br />
|-<br />
|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. <br />
|-<br />
|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<br />
|-<br />
|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.<br />
|-<br />
|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.<br />
|-<br />
|USB-C to DP cable || [https://www.amazon.es/gp/product/B01N5RFAI4/ CHOETECH V-XCP-0012BK] || || good <br />
|-<br />
| [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<br />
|-<br />
|USB-C to HDMI cable || Planet Computers USB-C to HDMI cable || || fail || does not work regardless of orientation in USB slot<br />
|-<br />
|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<br />
|-<br />
|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)<br />
|-<br />
| 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<br />
|}<br />
<br />
== USB other ==<br />
{| class="wikitable sortable"<br />
!Type || Make/Model || Hardware IDs || Result || Notes<br />
|-<br />
|Wireless Mouse || Logitech M705 Marathon || || good || Uses Logitech receiver. Battery level detected in power settings.<br />
|-<br />
|Wireless Mouse || Logitech G305 || || good || Uses Logitech receiver<br />
|-<br />
|Gamepad || sertronics SNES Style Controller || || good || tested in retroarch, the controller from berrybase<br />
|-<br />
|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<br />
|-<br />
|Yubikey original || Yubico || 1050:0010 || good ||<br />
|-<br />
|}<br />
<br />
----<br />
<br />
= Bluetooth hardware =<br />
{| class="wikitable sortable"<br />
!Type || Make/Model || Hardware IDs || Result || Notes <br />
|-<br />
|Bluetooth Mouse || HP Z5000 || E5C13AA || good || <br />
|-<br />
|Bluetooth Mouse || Logitech M557 || || good || <br />
|-<br />
|Bluetooth Mouse || Kensington Expert Wireless Trackball || || good ||<br />
|-<br />
|Bluetooth Mouse || Logitech MX Vertical || || good || Battery level is not detected over bluetooth, detected when using the logitech receiver<br />
|-<br />
|Bluetooth Mouse || Logitech Triathlon M720 || || good ||<br />
|-<br />
|Bluetooth Mouse || Logitech Ultra-Thin Touch Mouse || || good || Detects battery level as "keyboard"<br />
|-<br />
|Bluetooth Mouse || Logitech MX Anywhere 2 || || good ||<br />
|-<br />
|Bluetooth Mouse || Logitech M535 || 910-004432 || good ||<br />
|-<br />
|Bluetooth Mouse || Microsoft Bluetooth Mouse || RJN-00002 || good ||<br />
|-<br />
|Bluetooth Mouse || Fenifox low profile || MX106-Black || good ||<br />
|-<br />
|Bluetooth Mouse || Technet || MGS479 || good ||<br />
|-<br />
|Bluetooth Keyboard || Logitech MX Keys || || good || Battery level is not detected over bluetooth, detected when using the logitech receiver<br />
|-<br />
|Bluetooth Speaker || Ivation Acoustix || || good || Use audio sink profile<br />
|-<br />
|Bluetooth Headphones || Sony WH-1000XM2 || || good* || Needs pulseaudio-module-bluetooth. *Recording untested.<br />
|-<br />
|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].<br />
|-<br />
|USB Audio & Bluetooth Headset || Sony SBH90C || || good || Works well connected via USB Type-C and Bluetooth.<br />
|-<br />
|Bluetooth Headset || BlueAnt Ribbon || 7252A-RB || good || a2dp mode works, headset mode seems to work, out of box with manjaro<br />
|-<br />
|Bluetooth Headphones || DO-SV-BTIES03 || || good || Tested on Manjaro ARM - kde<br />
|-<br />
|Bluetooth Headset || TaoTronics TT-BH090 || || good || Microphone not tested but should work as expected of a normal Linux machine<br />
|-<br />
|Bluetooth Mouse || Logitech MX Ergo || || good || Works flawlessly both on Manjaro and Armbian.<br />
|}<br />
<br />
----<br />
<br />
= Other hardware =<br />
<br />
{| class="wikitable sortable"<br />
!Type || Make/Model || Hardware IDs || Result || Notes<br />
|-<br />
|[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<br />
|-<br />
|Printer || HP DeskJet Ink Advantage 3775 || || good* || Using hplip-gui: via USB and WiFi. *Only print function tested.<br />
|-<br />
|}<br />
<br />
[[Category:PineBook Pro]]</div>Ura2https://wiki.pine64.org/index.php?title=Pinebook_Pro_Hardware_Accessory_Compatibility&diff=10379Pinebook Pro Hardware Accessory Compatibility2021-05-16T00:31:30Z<p>Ura2: added my mouse and gamepad</p>
<hr />
<div><br />
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!<br />
<br />
= Storage =<br />
<br />
== NVMe SSD drives ==<br />
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.<br />
<br />
You need to buy and install the M.2 adaptor in order to fit one, please see [[Pinebook_Pro#Using_the_optional_NVMe_adapter]]<br />
<br />
Please see [[Pinebook Pro Troubleshooting Guide#NVMe SSD issues|a separate section]] that describes reported issues with the NVMe drives in PineBook Pro.<br />
<br />
{| class="wikitable sortable"<br />
!Type || Make/Model || Size || Hardware IDs || Result || Notes || Power options<br/>Active only || Save<br/>power<br/>setting?<br />
|-<br />
| 2280 || Kingston A2000 || 250 GB || SA2000M8250G || good || || PS 0: 9.00W<br/>PS 1: 4.60W<br/>PS 2: 3.80W<br/>PS 3: 0.045W<br/>PS 4: 0.004W<br/>APSTE: enabled by default || Yes<br />
|-<br />
| 2280 || Kingston A2000 || 1 TB || SA2000M81000G || good || || same as 250 GB || Yes<br />
|-<br />
| 2242 || Toshiba OCZ RC 100 || 240 GB || RC100-M22242-240G || good || || ||<br />
|-<br />
| 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<br/>PS 1: 2.44W<br/>PS 2: 2.02W || No. See [https://forum.pine64.org/showthread.php?tid=8737&pid=56481#pid56481 workaround].<br />
|-<br />
| 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. || ||<br />
|-<br />
| 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<br/>PS 1: 2.70W<br/>PS 2: 2.00W || No <br />
|-<br />
| 2280 || Intel 660p M.2 || 1 TB || SSDPEKNW010T8X1 || good || || PS 0: 4.00W<br/>PS 1: 3.00W<br/>PS 2: 2.20W<br/>APSTE Disabled by default || No<br />
|-<br />
| 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<br/>PS 1: 3.60W<br/>PS 2: 2.60W<br/>PS 3: 0.0300W<br/>PS 4: 0.0040W || No<br />
|-<br />
| 2280 || Intel 760p M.2 || 128 GB || SSDPEKKW128G8 || good || Firmware Revision 004C || PS 0: 9.00W<br/>PS 1: 4.60W<br/>PS 2: 3.80W<br/>PS 3: 0.045W<br/>PS 4: 0.004W<br/>APSTE: disabled by default with 4.4 kernel (mrfixit Debian), enabled by default with 5.6 kernel (Manjaro KDE) || Yes<br />
|-<br />
| 2280 || Intel 760p M.2 || 256 GB || SSDPEKKW256G8 || good || Firmware Revision 004C || PS 0: 9.00W<br/>PS 1: 4.60W<br/>PS 2: 3.80W<br/>PS 3: 0.045W<br/>PS 4: 0.004W<br/>Need to use lower power. || <br />
|-<br />
| 2280 || integral 256GB SSD M.2 2280 NVME || 256 GB || INSSD256GM280NM1 || usable || || PS 0: 9.00W || No<br />
|-<br />
| 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. || ||<br />
|-<br />
| 2280 || Samsung 970 EVO Plus || 500 GB || MZ-V7S500 || fail || Too power hungry? || PS 0: 6.2W<br/>PS 1: 4.3W<br/>PS 2: 2.1W ||<br />
|-<br />
| 2280 || Samsung 970 EVO || 1 TB || MZ-V7E1T0BW || fail || Too power hungry? || ||<br />
|-<br />
| 2280 || Samsung 970 PRO || 1 TB || MZ-V7P1T0BW || good || || PS 0: 6.20W<br/>PS 1: 4.30W<br/>PS 2: 2.10W<br/>PS 3: 0.04W<br/>PS 4: 0.005W<br/>APSTE: enabled by default || Yes<br />
|-<br />
| 2280 || Corsair MP300 || 120 GB || CSSD-F120GBMP300 || good || || PS 0: 3.00W<br/>PS 1: 2.00W<br/>PS 2: 2.00W<br/>PS 3: 0.1W<br/>PS 4: 0.005W<br/>APSTE Disabled by default ||<br />
|-<br />
| 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<br />
|-<br />
| 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<br/> PS 1: 5.71W<br/> PS 2: 5.19W<br/>APSTE Enabled by default || No<br />
|-<br />
| 2280 || Silicon Power P34A60 || 256 GB || ??? || fail || Isn't detected || ||<br />
|-<br />
| 2280 || Sabrent Rocket || 256 GB || SB-ROCKET-256 || good || || || No<br />
|-<br />
| 2242 || Sabrent Rocket Nano || 512 GB || SB-1342-512 || good* || No touchpad issues, didn't trim NVME adapter board.<br/>(*Might be too power hungry. More testing needed.) || ||<br />
|-<br />
| 2242 || Sabrent Rocket || 1 TB || SB-RKTQ-1TB || good || || PS 0: 5.55W<br/>PS 1: 4.49W<br/>PS 2: 3.97W<br/>PS 3: 0.049W<br/>PS 4: 0.0018W<br/>APSTE: available || Yes<br />
|-<br />
| 2280 || MyDigitalSSD SBXe || 960 GB || || good || || APST enabled<br/>Power states N/A || N/A <br />
|-<br />
| 2280 || HP SSD EX900 || 250GB || || good || No low-power modes available || || <br />
|-<br />
| 2280 || HP SSD EX950 || 512GB || || good || Unsure about low-power modes || || <br />
|-<br />
| 2280 || WD BLUE SN550 || 1TB || WDC WDS100T2B0C-00PXH0 || WARNING <br />good || WARNING mine was SATA and does NOT work!<br /> Booted successfully from NVMe (Bionic MATE) || PS 0: 3.50W<br/>PS 1: 2.70W<br/>PS 2: 1.90W<br/>APSTE Disabled by default || N/A <br />
|-<br />
| 2280 || WD Blue SN550 || 500GB || WDC WDS500G2B0C-00PXH0 || good || || PS 0: 3.50W<br/>PS 1: 2.40W<br/>PS 2: 1.90W<br/>APSTE enabled by default with 5.9 kernel (Manjaro XFCE) || No ||<br />
|-<br />
| 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 || ||<br />
|-<br />
<br />
| 2242 || WD PC SN520 || 256GB || - || fail || Power LED Flashes. Nothing else happens. || ||<br />
|-<br />
| 2280 || WD PC SN730 || 512GB || SDBPNTY-512G-1032 || fail || No touchpad issues. Could not bring SSD out of PS 3. ||APST enabled by default<br/>PS 0: 5.50W<br/>PS 1: 3.50W<br/>PS 2: 3.00W<br/>PS 3: 0.0700W<br/>PS 4: 0.0025W || No ||<br />
|-<br />
| 2280 || WD BLACK SN750 || 250GB || WDS250G3X0C-00SJG0 || good || No touchpad issues, didn't trim NVME adapter board. || APSTE disabled by default<br/> PS 0: 5.00W<br/>PS 1: 3.50W<br/>PS 2: 3.00W||<br />
|-<br />
| 2280 || WD BLACK SN750 || 500GB || WDS500G3X0C-00SJG0 || good || No tp issues. had to charge battery for 20% initially. || APSTE disabled by default<br/> PS 0: 5.50W<br/>PS 1: 3.50W<br/>PS 2: 3.00W<br/>PS 3: 0.07W<br/>PS 4: 0.0025W||<br />
|-<br />
| 2280 || WD BLACK SN750 || 1TB || WDS100T3X0C-00SJG0 || mixed || Drive works as expected (so far) though with 50% reduction in battery life.<br/><br/>Unable to set power mode (due to APST being enabled?).<br/><br/>Also unable to suspend PineBook Pro with NVMe drive attached. From dmesg:<br/>rockchip-pcie f8000000.pcie: PCIe link enter L2 timeout!<br/>PM: dpm_run_callback(): rockchip_pcie_suspend_noirq+0x0/0x100 returns -110<br/>PM: Devvice f8000000.pcie failed to suspend noirq: error -110<br/>PM: no irq suspend of devices failed<br/> || APST enabled by default<br/> PS 0: 6.00W<br/>PS 1: 3.50W<br/>PS 2: 3.00W<br/>PS 3: 0.1000W<br/>PS 4: 0.0025W || No<br />
|-<br />
| 2242 || KingSpec NE-512 || 512 GB || NE512 || good || || APST enabled<br/>Power states N/A || N/A <br />
|-<br />
| 2230 || Kioxia BG4 256GBTB|| 256 GB || KBG40ZNS256G || good || || APST enabled by default<br/>Power states PS 0: 3.60W<br/>PS 1: 2.60W<br/>PS 2: 2.20W<br/>PS 3: 0.005W<br/>PS 4: 0.005W ||<br />
|-<br />
| 2280 || Patriot P300 || 256 GB || P300P256GM28US || good || Booted successfully with / on NVMe and /boot on eMMC (Armbian Buster) || APSTE disabled by default<br/> PS 0: 4.50W<br/> PS 1: 2.70W<br/> PS 2: 2.16W<br/>PS 3: 0.07W<br/>PS 4: 0.002W||<br />
|-<br />
| 2280 || Team Group MP33 || 128 GB || TM8FP6128G0C101 || good || || ||<br />
|-<br />
| 2280 || Team Group MP34 || 512 GB || TM8FP6512G0C101 || fail ||APST enabled by default and scripts do not change the power mode. <br>Higher power consumption modes cause the PBP to crash<br/> || PS 0 5.55W <br/>PS 1 4.49W<br/>PS 2 3.97W <br/>PS 3 0.0490W <br/>PS 4 0.0018W ||No<br />
|-<br />
| 2280 || Digifast Ace || 256 GB || DGFA256M2L01 || good ||No touchpad issues. Board not trimmed. || PS 0 6.77W <br/>PS 1 5.71W<br/>PS 2 5.19W <br/>PS 3 0.0490W <br/>PS 4 0.0018W ||Yes<br />
<br />
|}<br />
<br />
== microSD Cards ==<br />
{| class="wikitable sortable"<br />
!Type || Make/Model || Hardware IDs || Result || Notes<br />
|-<br />
|SD Card || Samsung Evo Select 512GB || MB-ME512GA/AM || good ||<br />
|-<br />
|SD Card || Samsung Evo Plus 64GB || || good || Hdparm tested 44MBps read speeds<br />
|-<br />
|SD Card || Sandisk Ultra 400GB || || good || Works fine as a storage extension. Mounted for pictures, etc.<br />
|-<br />
|SD Card || Sandisk Ultra 16GB || || fail || Works for a short period of time but locks up completely after a certain amount of written data<br />
|-<br />
|SD Card || Sandisk Ultra 64GB (Old from 2015) || || fail || ^<br />
|-<br />
|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<br />
|-<br />
|SD Card || Sandisk Extreme Pro 64GB || || good || <br />
|}<br />
<br />
= USB hardware =<br />
<br />
== USB Card Readers ==<br />
<br />
Standalone card readers only, please; see below for multifunction devices.<br />
<br />
{| class="wikitable sortable"<br />
!Type || Make/Model || Hardware IDs || Result || Notes<br />
|-<br />
|USB-2 SDHC reader || Sandisk MobileMate+ || 0781:b2b3 || good ||<br />
|-<br />
|USB-3 SDHC/CF reader || Transcend TS-RDF8K || 8564:4000 || good ||<br />
|}<br />
<br />
== USB Networking ==<br />
<br />
Standalone network devices only, please; see below for multifunction devices<br />
<br />
{| class="wikitable sortable"<br />
!Type || Make/Model || Hardware IDs || Result || Notes<br />
|-<br />
|USB-2 Fast Ethernet adapter || Realtek RTL8152 || 0bda:8152 || good || <br />
|-<br />
|USB-2 Ethernet adapter || ASIX AX77882 || 0b95:7720 || good || <br />
|-<br />
|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/<br />
|-<br />
|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/<br />
|-<br />
|USB 3 to Gigabit Ethernet Adapter || Pluggable USB 3.0 to Ethernet Gigabit (ASIX AX88179 chipset) || 0b95:1790 || good ||<br />
|}<br />
<br />
== USB Multifunction Devices ==<br />
<br />
{| class="wikitable sortable"<br />
!Type || Make/Model || Hardware IDs || Result || Notes<br />
|-<br />
|USB-C Hub || Samsung EE-P5000 || || Power is passed through from hub to Pinebook Pro; Ethernet, HDMI, and USB-A do not work || <br />
|-<br />
|USB-C Hub || Insignia NS-PU378CHM || || Power is passed through from hub to Pinebook Pro; USB-A works; HDMI does not work || <br />
|-<br />
|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 || <br />
|-<br />
|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/]<br />
|-<br />
|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]<br />
|-<br />
|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 ||<br />
|-<br />
|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 ||<br />
|-<br />
|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 <br />
|- <br />
|4 Port USB 3 NIC || Delock 62966 || || good || 4 individually controllable Gigabit Ethernet Ports. Consider using it with own power supply<br />
|-<br />
|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.<br />
|-<br />
|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.<br />
|-<br />
|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.<br />
|-<br />
|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<br />
|-<br />
|USB-C dock || Lenovo ThinkPad 40A9 || TBD || mixed || USB hub works, audio device works, ethernet device works, display does NOT despite plug's orientation<br />
|}<br />
<br />
== USB C alternate mode DP ==<br />
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.<br />
{| class="wikitable sortable"<br />
!Type || Make/Model || Hardware IDs || Result || Notes<br />
|-<br />
|USB-C to HDMI adapter 201018 || Cable Matters || || good || Tested up to 1080p30, audio works<br />
|-<br />
|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<br />
|-<br />
|USB-C to HDMI adapter || generic || || good || Tested up to 4k60<br />
|-<br />
|USB-C to DP Adapter || OrxnQ || 04b4:5210 || good || Advertises support for 4K@60Hz, tested up to 1080p. Only FullHD resolutions available on Debian.<br />
|-<br />
|USB-C HDMI adapter (DP-alt mode) || QGeeM || || good || Manjaro 2020-01-25<br />
|-<br />
|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/<br />
|-<br />
|USB-C combo hub (HDMI, network, card slots, USB ports) || generic || || fail ||<br />
|-<br />
|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<br />
|-<br />
|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.<br />
|-<br />
|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<br />
|- <br />
|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<br />
|-<br />
|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 <br />
|-<br />
|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<br />
|-<br />
|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.<br />
|-<br />
|USB-C to HDMI adapter || MHL TH002 || || good || Tested at 1080p@60<br />
|-<br />
|USB-C combo hub (USB-C power, HDMI, 2xUSB, 1xUSB-C(no power)) || Baseus || || good<br />
|-<br />
|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.) <br />
|-<br />
|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. <br />
|-<br />
|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<br />
|-<br />
|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.<br />
|-<br />
|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.<br />
|-<br />
|USB-C to DP cable || [https://www.amazon.es/gp/product/B01N5RFAI4/ CHOETECH V-XCP-0012BK] || || good <br />
|-<br />
| [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<br />
|-<br />
|USB-C to HDMI cable || Planet Computers USB-C to HDMI cable || || fail || does not work regardless of orientation in USB slot<br />
|-<br />
|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<br />
|-<br />
|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)<br />
|-<br />
| 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<br />
|}<br />
<br />
== USB other ==<br />
{| class="wikitable sortable"<br />
!Type || Make/Model || Hardware IDs || Result || Notes<br />
|-<br />
|Wireless Mouse || Logitech M705 Marathon || || good || Uses Logitech receiver. Battery level detected in power settings.<br />
|-<br />
|Wireless Mouse || Logitech G305 || || good || Uses Logitech receiver<br />
|-<br />
|Gamepad || sertronics SNES Style Controller || || good || tested in retroarch, the controller from berrybase<br />
|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<br />
|-<br />
|Yubikey original || Yubico || 1050:0010 || good ||<br />
|-<br />
|}<br />
<br />
----<br />
<br />
= Bluetooth hardware =<br />
{| class="wikitable sortable"<br />
!Type || Make/Model || Hardware IDs || Result || Notes <br />
|-<br />
|Bluetooth Mouse || HP Z5000 || E5C13AA || good || <br />
|-<br />
|Bluetooth Mouse || Logitech M557 || || good || <br />
|-<br />
|Bluetooth Mouse || Kensington Expert Wireless Trackball || || good ||<br />
|-<br />
|Bluetooth Mouse || Logitech MX Vertical || || good || Battery level is not detected over bluetooth, detected when using the logitech receiver<br />
|-<br />
|Bluetooth Mouse || Logitech Triathlon M720 || || good ||<br />
|-<br />
|Bluetooth Mouse || Logitech Ultra-Thin Touch Mouse || || good || Detects battery level as "keyboard"<br />
|-<br />
|Bluetooth Mouse || Logitech MX Anywhere 2 || || good ||<br />
|-<br />
|Bluetooth Mouse || Logitech M535 || 910-004432 || good ||<br />
|-<br />
|Bluetooth Mouse || Microsoft Bluetooth Mouse || RJN-00002 || good ||<br />
|-<br />
|Bluetooth Mouse || Fenifox low profile || MX106-Black || good ||<br />
|-<br />
|Bluetooth Mouse || Technet || MGS479 || good ||<br />
|-<br />
|Bluetooth Keyboard || Logitech MX Keys || || good || Battery level is not detected over bluetooth, detected when using the logitech receiver<br />
|-<br />
|Bluetooth Speaker || Ivation Acoustix || || good || Use audio sink profile<br />
|-<br />
|Bluetooth Headphones || Sony WH-1000XM2 || || good* || Needs pulseaudio-module-bluetooth. *Recording untested.<br />
|-<br />
|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].<br />
|-<br />
|USB Audio & Bluetooth Headset || Sony SBH90C || || good || Works well connected via USB Type-C and Bluetooth.<br />
|-<br />
|Bluetooth Headset || BlueAnt Ribbon || 7252A-RB || good || a2dp mode works, headset mode seems to work, out of box with manjaro<br />
|-<br />
|Bluetooth Headphones || DO-SV-BTIES03 || || good || Tested on Manjaro ARM - kde<br />
|-<br />
|Bluetooth Headset || TaoTronics TT-BH090 || || good || Microphone not tested but should work as expected of a normal Linux machine<br />
|-<br />
|Bluetooth Mouse || Logitech MX Ergo || || good || Works flawlessly both on Manjaro and Armbian.<br />
|}<br />
<br />
----<br />
<br />
= Other hardware =<br />
<br />
{| class="wikitable sortable"<br />
!Type || Make/Model || Hardware IDs || Result || Notes<br />
|-<br />
|[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<br />
|-<br />
|Printer || HP DeskJet Ink Advantage 3775 || || good* || Using hplip-gui: via USB and WiFi. *Only print function tested.<br />
|-<br />
|}<br />
<br />
[[Category:PineBook Pro]]</div>Ura2https://wiki.pine64.org/index.php?title=Pinebook_Pro_Hardware_Accessory_Compatibility&diff=10378Pinebook Pro Hardware Accessory Compatibility2021-05-16T00:28:43Z<p>Ura2: /* USB other */</p>
<hr />
<div><br />
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!<br />
<br />
= Storage =<br />
<br />
== NVMe SSD drives ==<br />
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.<br />
<br />
You need to buy and install the M.2 adaptor in order to fit one, please see [[Pinebook_Pro#Using_the_optional_NVMe_adapter]]<br />
<br />
Please see [[Pinebook Pro Troubleshooting Guide#NVMe SSD issues|a separate section]] that describes reported issues with the NVMe drives in PineBook Pro.<br />
<br />
{| class="wikitable sortable"<br />
!Type || Make/Model || Size || Hardware IDs || Result || Notes || Power options<br/>Active only || Save<br/>power<br/>setting?<br />
|-<br />
| 2280 || Kingston A2000 || 250 GB || SA2000M8250G || good || || PS 0: 9.00W<br/>PS 1: 4.60W<br/>PS 2: 3.80W<br/>PS 3: 0.045W<br/>PS 4: 0.004W<br/>APSTE: enabled by default || Yes<br />
|-<br />
| 2280 || Kingston A2000 || 1 TB || SA2000M81000G || good || || same as 250 GB || Yes<br />
|-<br />
| 2242 || Toshiba OCZ RC 100 || 240 GB || RC100-M22242-240G || good || || ||<br />
|-<br />
| 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<br/>PS 1: 2.44W<br/>PS 2: 2.02W || No. See [https://forum.pine64.org/showthread.php?tid=8737&pid=56481#pid56481 workaround].<br />
|-<br />
| 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. || ||<br />
|-<br />
| 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<br/>PS 1: 2.70W<br/>PS 2: 2.00W || No <br />
|-<br />
| 2280 || Intel 660p M.2 || 1 TB || SSDPEKNW010T8X1 || good || || PS 0: 4.00W<br/>PS 1: 3.00W<br/>PS 2: 2.20W<br/>APSTE Disabled by default || No<br />
|-<br />
| 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<br/>PS 1: 3.60W<br/>PS 2: 2.60W<br/>PS 3: 0.0300W<br/>PS 4: 0.0040W || No<br />
|-<br />
| 2280 || Intel 760p M.2 || 128 GB || SSDPEKKW128G8 || good || Firmware Revision 004C || PS 0: 9.00W<br/>PS 1: 4.60W<br/>PS 2: 3.80W<br/>PS 3: 0.045W<br/>PS 4: 0.004W<br/>APSTE: disabled by default with 4.4 kernel (mrfixit Debian), enabled by default with 5.6 kernel (Manjaro KDE) || Yes<br />
|-<br />
| 2280 || Intel 760p M.2 || 256 GB || SSDPEKKW256G8 || good || Firmware Revision 004C || PS 0: 9.00W<br/>PS 1: 4.60W<br/>PS 2: 3.80W<br/>PS 3: 0.045W<br/>PS 4: 0.004W<br/>Need to use lower power. || <br />
|-<br />
| 2280 || integral 256GB SSD M.2 2280 NVME || 256 GB || INSSD256GM280NM1 || usable || || PS 0: 9.00W || No<br />
|-<br />
| 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. || ||<br />
|-<br />
| 2280 || Samsung 970 EVO Plus || 500 GB || MZ-V7S500 || fail || Too power hungry? || PS 0: 6.2W<br/>PS 1: 4.3W<br/>PS 2: 2.1W ||<br />
|-<br />
| 2280 || Samsung 970 EVO || 1 TB || MZ-V7E1T0BW || fail || Too power hungry? || ||<br />
|-<br />
| 2280 || Samsung 970 PRO || 1 TB || MZ-V7P1T0BW || good || || PS 0: 6.20W<br/>PS 1: 4.30W<br/>PS 2: 2.10W<br/>PS 3: 0.04W<br/>PS 4: 0.005W<br/>APSTE: enabled by default || Yes<br />
|-<br />
| 2280 || Corsair MP300 || 120 GB || CSSD-F120GBMP300 || good || || PS 0: 3.00W<br/>PS 1: 2.00W<br/>PS 2: 2.00W<br/>PS 3: 0.1W<br/>PS 4: 0.005W<br/>APSTE Disabled by default ||<br />
|-<br />
| 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<br />
|-<br />
| 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<br/> PS 1: 5.71W<br/> PS 2: 5.19W<br/>APSTE Enabled by default || No<br />
|-<br />
| 2280 || Silicon Power P34A60 || 256 GB || ??? || fail || Isn't detected || ||<br />
|-<br />
| 2280 || Sabrent Rocket || 256 GB || SB-ROCKET-256 || good || || || No<br />
|-<br />
| 2242 || Sabrent Rocket Nano || 512 GB || SB-1342-512 || good* || No touchpad issues, didn't trim NVME adapter board.<br/>(*Might be too power hungry. More testing needed.) || ||<br />
|-<br />
| 2242 || Sabrent Rocket || 1 TB || SB-RKTQ-1TB || good || || PS 0: 5.55W<br/>PS 1: 4.49W<br/>PS 2: 3.97W<br/>PS 3: 0.049W<br/>PS 4: 0.0018W<br/>APSTE: available || Yes<br />
|-<br />
| 2280 || MyDigitalSSD SBXe || 960 GB || || good || || APST enabled<br/>Power states N/A || N/A <br />
|-<br />
| 2280 || HP SSD EX900 || 250GB || || good || No low-power modes available || || <br />
|-<br />
| 2280 || HP SSD EX950 || 512GB || || good || Unsure about low-power modes || || <br />
|-<br />
| 2280 || WD BLUE SN550 || 1TB || WDC WDS100T2B0C-00PXH0 || WARNING <br />good || WARNING mine was SATA and does NOT work!<br /> Booted successfully from NVMe (Bionic MATE) || PS 0: 3.50W<br/>PS 1: 2.70W<br/>PS 2: 1.90W<br/>APSTE Disabled by default || N/A <br />
|-<br />
| 2280 || WD Blue SN550 || 500GB || WDC WDS500G2B0C-00PXH0 || good || || PS 0: 3.50W<br/>PS 1: 2.40W<br/>PS 2: 1.90W<br/>APSTE enabled by default with 5.9 kernel (Manjaro XFCE) || No ||<br />
|-<br />
| 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 || ||<br />
|-<br />
<br />
| 2242 || WD PC SN520 || 256GB || - || fail || Power LED Flashes. Nothing else happens. || ||<br />
|-<br />
| 2280 || WD PC SN730 || 512GB || SDBPNTY-512G-1032 || fail || No touchpad issues. Could not bring SSD out of PS 3. ||APST enabled by default<br/>PS 0: 5.50W<br/>PS 1: 3.50W<br/>PS 2: 3.00W<br/>PS 3: 0.0700W<br/>PS 4: 0.0025W || No ||<br />
|-<br />
| 2280 || WD BLACK SN750 || 250GB || WDS250G3X0C-00SJG0 || good || No touchpad issues, didn't trim NVME adapter board. || APSTE disabled by default<br/> PS 0: 5.00W<br/>PS 1: 3.50W<br/>PS 2: 3.00W||<br />
|-<br />
| 2280 || WD BLACK SN750 || 500GB || WDS500G3X0C-00SJG0 || good || No tp issues. had to charge battery for 20% initially. || APSTE disabled by default<br/> PS 0: 5.50W<br/>PS 1: 3.50W<br/>PS 2: 3.00W<br/>PS 3: 0.07W<br/>PS 4: 0.0025W||<br />
|-<br />
| 2280 || WD BLACK SN750 || 1TB || WDS100T3X0C-00SJG0 || mixed || Drive works as expected (so far) though with 50% reduction in battery life.<br/><br/>Unable to set power mode (due to APST being enabled?).<br/><br/>Also unable to suspend PineBook Pro with NVMe drive attached. From dmesg:<br/>rockchip-pcie f8000000.pcie: PCIe link enter L2 timeout!<br/>PM: dpm_run_callback(): rockchip_pcie_suspend_noirq+0x0/0x100 returns -110<br/>PM: Devvice f8000000.pcie failed to suspend noirq: error -110<br/>PM: no irq suspend of devices failed<br/> || APST enabled by default<br/> PS 0: 6.00W<br/>PS 1: 3.50W<br/>PS 2: 3.00W<br/>PS 3: 0.1000W<br/>PS 4: 0.0025W || No<br />
|-<br />
| 2242 || KingSpec NE-512 || 512 GB || NE512 || good || || APST enabled<br/>Power states N/A || N/A <br />
|-<br />
| 2230 || Kioxia BG4 256GBTB|| 256 GB || KBG40ZNS256G || good || || APST enabled by default<br/>Power states PS 0: 3.60W<br/>PS 1: 2.60W<br/>PS 2: 2.20W<br/>PS 3: 0.005W<br/>PS 4: 0.005W ||<br />
|-<br />
| 2280 || Patriot P300 || 256 GB || P300P256GM28US || good || Booted successfully with / on NVMe and /boot on eMMC (Armbian Buster) || APSTE disabled by default<br/> PS 0: 4.50W<br/> PS 1: 2.70W<br/> PS 2: 2.16W<br/>PS 3: 0.07W<br/>PS 4: 0.002W||<br />
|-<br />
| 2280 || Team Group MP33 || 128 GB || TM8FP6128G0C101 || good || || ||<br />
|-<br />
| 2280 || Team Group MP34 || 512 GB || TM8FP6512G0C101 || fail ||APST enabled by default and scripts do not change the power mode. <br>Higher power consumption modes cause the PBP to crash<br/> || PS 0 5.55W <br/>PS 1 4.49W<br/>PS 2 3.97W <br/>PS 3 0.0490W <br/>PS 4 0.0018W ||No<br />
|-<br />
| 2280 || Digifast Ace || 256 GB || DGFA256M2L01 || good ||No touchpad issues. Board not trimmed. || PS 0 6.77W <br/>PS 1 5.71W<br/>PS 2 5.19W <br/>PS 3 0.0490W <br/>PS 4 0.0018W ||Yes<br />
<br />
|}<br />
<br />
== microSD Cards ==<br />
{| class="wikitable sortable"<br />
!Type || Make/Model || Hardware IDs || Result || Notes<br />
|-<br />
|SD Card || Samsung Evo Select 512GB || MB-ME512GA/AM || good ||<br />
|-<br />
|SD Card || Samsung Evo Plus 64GB || || good || Hdparm tested 44MBps read speeds<br />
|-<br />
|SD Card || Sandisk Ultra 400GB || || good || Works fine as a storage extension. Mounted for pictures, etc.<br />
|-<br />
|SD Card || Sandisk Ultra 16GB || || fail || Works for a short period of time but locks up completely after a certain amount of written data<br />
|-<br />
|SD Card || Sandisk Ultra 64GB (Old from 2015) || || fail || ^<br />
|-<br />
|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<br />
|-<br />
|SD Card || Sandisk Extreme Pro 64GB || || good || <br />
|}<br />
<br />
= USB hardware =<br />
<br />
== USB Card Readers ==<br />
<br />
Standalone card readers only, please; see below for multifunction devices.<br />
<br />
{| class="wikitable sortable"<br />
!Type || Make/Model || Hardware IDs || Result || Notes<br />
|-<br />
|USB-2 SDHC reader || Sandisk MobileMate+ || 0781:b2b3 || good ||<br />
|-<br />
|USB-3 SDHC/CF reader || Transcend TS-RDF8K || 8564:4000 || good ||<br />
|}<br />
<br />
== USB Networking ==<br />
<br />
Standalone network devices only, please; see below for multifunction devices<br />
<br />
{| class="wikitable sortable"<br />
!Type || Make/Model || Hardware IDs || Result || Notes<br />
|-<br />
|USB-2 Fast Ethernet adapter || Realtek RTL8152 || 0bda:8152 || good || <br />
|-<br />
|USB-2 Ethernet adapter || ASIX AX77882 || 0b95:7720 || good || <br />
|-<br />
|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/<br />
|-<br />
|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/<br />
|-<br />
|USB 3 to Gigabit Ethernet Adapter || Pluggable USB 3.0 to Ethernet Gigabit (ASIX AX88179 chipset) || 0b95:1790 || good ||<br />
|}<br />
<br />
== USB Multifunction Devices ==<br />
<br />
{| class="wikitable sortable"<br />
!Type || Make/Model || Hardware IDs || Result || Notes<br />
|-<br />
|USB-C Hub || Samsung EE-P5000 || || Power is passed through from hub to Pinebook Pro; Ethernet, HDMI, and USB-A do not work || <br />
|-<br />
|USB-C Hub || Insignia NS-PU378CHM || || Power is passed through from hub to Pinebook Pro; USB-A works; HDMI does not work || <br />
|-<br />
|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 || <br />
|-<br />
|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/]<br />
|-<br />
|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]<br />
|-<br />
|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 ||<br />
|-<br />
|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 ||<br />
|-<br />
|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 <br />
|- <br />
|4 Port USB 3 NIC || Delock 62966 || || good || 4 individually controllable Gigabit Ethernet Ports. Consider using it with own power supply<br />
|-<br />
|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.<br />
|-<br />
|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.<br />
|-<br />
|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.<br />
|-<br />
|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<br />
|-<br />
|USB-C dock || Lenovo ThinkPad 40A9 || TBD || mixed || USB hub works, audio device works, ethernet device works, display does NOT despite plug's orientation<br />
|}<br />
<br />
== USB C alternate mode DP ==<br />
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.<br />
{| class="wikitable sortable"<br />
!Type || Make/Model || Hardware IDs || Result || Notes<br />
|-<br />
|USB-C to HDMI adapter 201018 || Cable Matters || || good || Tested up to 1080p30, audio works<br />
|-<br />
|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<br />
|-<br />
|USB-C to HDMI adapter || generic || || good || Tested up to 4k60<br />
|-<br />
|USB-C to DP Adapter || OrxnQ || 04b4:5210 || good || Advertises support for 4K@60Hz, tested up to 1080p. Only FullHD resolutions available on Debian.<br />
|-<br />
|USB-C HDMI adapter (DP-alt mode) || QGeeM || || good || Manjaro 2020-01-25<br />
|-<br />
|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/<br />
|-<br />
|USB-C combo hub (HDMI, network, card slots, USB ports) || generic || || fail ||<br />
|-<br />
|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<br />
|-<br />
|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.<br />
|-<br />
|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<br />
|- <br />
|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<br />
|-<br />
|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 <br />
|-<br />
|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<br />
|-<br />
|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.<br />
|-<br />
|USB-C to HDMI adapter || MHL TH002 || || good || Tested at 1080p@60<br />
|-<br />
|USB-C combo hub (USB-C power, HDMI, 2xUSB, 1xUSB-C(no power)) || Baseus || || good<br />
|-<br />
|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.) <br />
|-<br />
|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. <br />
|-<br />
|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<br />
|-<br />
|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.<br />
|-<br />
|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.<br />
|-<br />
|USB-C to DP cable || [https://www.amazon.es/gp/product/B01N5RFAI4/ CHOETECH V-XCP-0012BK] || || good <br />
|-<br />
| [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<br />
|-<br />
|USB-C to HDMI cable || Planet Computers USB-C to HDMI cable || || fail || does not work regardless of orientation in USB slot<br />
|-<br />
|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<br />
|-<br />
|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)<br />
|-<br />
| 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<br />
|}<br />
<br />
== USB other ==<br />
{| class="wikitable sortable"<br />
!Type || Make/Model || Hardware IDs || Result || Notes<br />
|-<br />
|Wireless Mouse || Logitech M705 Marathon || || good || Uses Logitech receiver. Battery level detected in power settings.<br />
|-<br />
|Wireless Mouse || Logitech G305 || || good || Uses Logitech receiver<br />
|-<br />
|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<br />
|-<br />
|Yubikey original || Yubico || 1050:0010 || good ||<br />
|-<br />
|}<br />
<br />
----<br />
<br />
= Bluetooth hardware =<br />
{| class="wikitable sortable"<br />
!Type || Make/Model || Hardware IDs || Result || Notes <br />
|-<br />
|Bluetooth Mouse || HP Z5000 || E5C13AA || good || <br />
|-<br />
|Bluetooth Mouse || Logitech M557 || || good || <br />
|-<br />
|Bluetooth Mouse || Kensington Expert Wireless Trackball || || good ||<br />
|-<br />
|Bluetooth Mouse || Logitech MX Vertical || || good || Battery level is not detected over bluetooth, detected when using the logitech receiver<br />
|-<br />
|Bluetooth Mouse || Logitech Triathlon M720 || || good ||<br />
|-<br />
|Bluetooth Mouse || Logitech Ultra-Thin Touch Mouse || || good || Detects battery level as "keyboard"<br />
|-<br />
|Bluetooth Mouse || Logitech MX Anywhere 2 || || good ||<br />
|-<br />
|Bluetooth Mouse || Logitech M535 || 910-004432 || good ||<br />
|-<br />
|Bluetooth Mouse || Microsoft Bluetooth Mouse || RJN-00002 || good ||<br />
|-<br />
|Bluetooth Mouse || Fenifox low profile || MX106-Black || good ||<br />
|-<br />
|Bluetooth Mouse || Technet || MGS479 || good ||<br />
|-<br />
|Bluetooth Keyboard || Logitech MX Keys || || good || Battery level is not detected over bluetooth, detected when using the logitech receiver<br />
|-<br />
|Bluetooth Speaker || Ivation Acoustix || || good || Use audio sink profile<br />
|-<br />
|Bluetooth Headphones || Sony WH-1000XM2 || || good* || Needs pulseaudio-module-bluetooth. *Recording untested.<br />
|-<br />
|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].<br />
|-<br />
|USB Audio & Bluetooth Headset || Sony SBH90C || || good || Works well connected via USB Type-C and Bluetooth.<br />
|-<br />
|Bluetooth Headset || BlueAnt Ribbon || 7252A-RB || good || a2dp mode works, headset mode seems to work, out of box with manjaro<br />
|-<br />
|Bluetooth Headphones || DO-SV-BTIES03 || || good || Tested on Manjaro ARM - kde<br />
|-<br />
|Bluetooth Headset || TaoTronics TT-BH090 || || good || Microphone not tested but should work as expected of a normal Linux machine<br />
|-<br />
|Bluetooth Mouse || Logitech MX Ergo || || good || Works flawlessly both on Manjaro and Armbian.<br />
|}<br />
<br />
----<br />
<br />
= Other hardware =<br />
<br />
{| class="wikitable sortable"<br />
!Type || Make/Model || Hardware IDs || Result || Notes<br />
|-<br />
|[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<br />
|-<br />
|Printer || HP DeskJet Ink Advantage 3775 || || good* || Using hplip-gui: via USB and WiFi. *Only print function tested.<br />
|-<br />
|}<br />
<br />
[[Category:PineBook Pro]]</div>Ura2https://wiki.pine64.org/index.php?title=Pinebook_Pro_Hardware_Accessory_Compatibility&diff=10377Pinebook Pro Hardware Accessory Compatibility2021-05-16T00:27:49Z<p>Ura2: /* microSD Cards */</p>
<hr />
<div><br />
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!<br />
<br />
= Storage =<br />
<br />
== NVMe SSD drives ==<br />
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.<br />
<br />
You need to buy and install the M.2 adaptor in order to fit one, please see [[Pinebook_Pro#Using_the_optional_NVMe_adapter]]<br />
<br />
Please see [[Pinebook Pro Troubleshooting Guide#NVMe SSD issues|a separate section]] that describes reported issues with the NVMe drives in PineBook Pro.<br />
<br />
{| class="wikitable sortable"<br />
!Type || Make/Model || Size || Hardware IDs || Result || Notes || Power options<br/>Active only || Save<br/>power<br/>setting?<br />
|-<br />
| 2280 || Kingston A2000 || 250 GB || SA2000M8250G || good || || PS 0: 9.00W<br/>PS 1: 4.60W<br/>PS 2: 3.80W<br/>PS 3: 0.045W<br/>PS 4: 0.004W<br/>APSTE: enabled by default || Yes<br />
|-<br />
| 2280 || Kingston A2000 || 1 TB || SA2000M81000G || good || || same as 250 GB || Yes<br />
|-<br />
| 2242 || Toshiba OCZ RC 100 || 240 GB || RC100-M22242-240G || good || || ||<br />
|-<br />
| 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<br/>PS 1: 2.44W<br/>PS 2: 2.02W || No. See [https://forum.pine64.org/showthread.php?tid=8737&pid=56481#pid56481 workaround].<br />
|-<br />
| 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. || ||<br />
|-<br />
| 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<br/>PS 1: 2.70W<br/>PS 2: 2.00W || No <br />
|-<br />
| 2280 || Intel 660p M.2 || 1 TB || SSDPEKNW010T8X1 || good || || PS 0: 4.00W<br/>PS 1: 3.00W<br/>PS 2: 2.20W<br/>APSTE Disabled by default || No<br />
|-<br />
| 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<br/>PS 1: 3.60W<br/>PS 2: 2.60W<br/>PS 3: 0.0300W<br/>PS 4: 0.0040W || No<br />
|-<br />
| 2280 || Intel 760p M.2 || 128 GB || SSDPEKKW128G8 || good || Firmware Revision 004C || PS 0: 9.00W<br/>PS 1: 4.60W<br/>PS 2: 3.80W<br/>PS 3: 0.045W<br/>PS 4: 0.004W<br/>APSTE: disabled by default with 4.4 kernel (mrfixit Debian), enabled by default with 5.6 kernel (Manjaro KDE) || Yes<br />
|-<br />
| 2280 || Intel 760p M.2 || 256 GB || SSDPEKKW256G8 || good || Firmware Revision 004C || PS 0: 9.00W<br/>PS 1: 4.60W<br/>PS 2: 3.80W<br/>PS 3: 0.045W<br/>PS 4: 0.004W<br/>Need to use lower power. || <br />
|-<br />
| 2280 || integral 256GB SSD M.2 2280 NVME || 256 GB || INSSD256GM280NM1 || usable || || PS 0: 9.00W || No<br />
|-<br />
| 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. || ||<br />
|-<br />
| 2280 || Samsung 970 EVO Plus || 500 GB || MZ-V7S500 || fail || Too power hungry? || PS 0: 6.2W<br/>PS 1: 4.3W<br/>PS 2: 2.1W ||<br />
|-<br />
| 2280 || Samsung 970 EVO || 1 TB || MZ-V7E1T0BW || fail || Too power hungry? || ||<br />
|-<br />
| 2280 || Samsung 970 PRO || 1 TB || MZ-V7P1T0BW || good || || PS 0: 6.20W<br/>PS 1: 4.30W<br/>PS 2: 2.10W<br/>PS 3: 0.04W<br/>PS 4: 0.005W<br/>APSTE: enabled by default || Yes<br />
|-<br />
| 2280 || Corsair MP300 || 120 GB || CSSD-F120GBMP300 || good || || PS 0: 3.00W<br/>PS 1: 2.00W<br/>PS 2: 2.00W<br/>PS 3: 0.1W<br/>PS 4: 0.005W<br/>APSTE Disabled by default ||<br />
|-<br />
| 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<br />
|-<br />
| 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<br/> PS 1: 5.71W<br/> PS 2: 5.19W<br/>APSTE Enabled by default || No<br />
|-<br />
| 2280 || Silicon Power P34A60 || 256 GB || ??? || fail || Isn't detected || ||<br />
|-<br />
| 2280 || Sabrent Rocket || 256 GB || SB-ROCKET-256 || good || || || No<br />
|-<br />
| 2242 || Sabrent Rocket Nano || 512 GB || SB-1342-512 || good* || No touchpad issues, didn't trim NVME adapter board.<br/>(*Might be too power hungry. More testing needed.) || ||<br />
|-<br />
| 2242 || Sabrent Rocket || 1 TB || SB-RKTQ-1TB || good || || PS 0: 5.55W<br/>PS 1: 4.49W<br/>PS 2: 3.97W<br/>PS 3: 0.049W<br/>PS 4: 0.0018W<br/>APSTE: available || Yes<br />
|-<br />
| 2280 || MyDigitalSSD SBXe || 960 GB || || good || || APST enabled<br/>Power states N/A || N/A <br />
|-<br />
| 2280 || HP SSD EX900 || 250GB || || good || No low-power modes available || || <br />
|-<br />
| 2280 || HP SSD EX950 || 512GB || || good || Unsure about low-power modes || || <br />
|-<br />
| 2280 || WD BLUE SN550 || 1TB || WDC WDS100T2B0C-00PXH0 || WARNING <br />good || WARNING mine was SATA and does NOT work!<br /> Booted successfully from NVMe (Bionic MATE) || PS 0: 3.50W<br/>PS 1: 2.70W<br/>PS 2: 1.90W<br/>APSTE Disabled by default || N/A <br />
|-<br />
| 2280 || WD Blue SN550 || 500GB || WDC WDS500G2B0C-00PXH0 || good || || PS 0: 3.50W<br/>PS 1: 2.40W<br/>PS 2: 1.90W<br/>APSTE enabled by default with 5.9 kernel (Manjaro XFCE) || No ||<br />
|-<br />
| 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 || ||<br />
|-<br />
<br />
| 2242 || WD PC SN520 || 256GB || - || fail || Power LED Flashes. Nothing else happens. || ||<br />
|-<br />
| 2280 || WD PC SN730 || 512GB || SDBPNTY-512G-1032 || fail || No touchpad issues. Could not bring SSD out of PS 3. ||APST enabled by default<br/>PS 0: 5.50W<br/>PS 1: 3.50W<br/>PS 2: 3.00W<br/>PS 3: 0.0700W<br/>PS 4: 0.0025W || No ||<br />
|-<br />
| 2280 || WD BLACK SN750 || 250GB || WDS250G3X0C-00SJG0 || good || No touchpad issues, didn't trim NVME adapter board. || APSTE disabled by default<br/> PS 0: 5.00W<br/>PS 1: 3.50W<br/>PS 2: 3.00W||<br />
|-<br />
| 2280 || WD BLACK SN750 || 500GB || WDS500G3X0C-00SJG0 || good || No tp issues. had to charge battery for 20% initially. || APSTE disabled by default<br/> PS 0: 5.50W<br/>PS 1: 3.50W<br/>PS 2: 3.00W<br/>PS 3: 0.07W<br/>PS 4: 0.0025W||<br />
|-<br />
| 2280 || WD BLACK SN750 || 1TB || WDS100T3X0C-00SJG0 || mixed || Drive works as expected (so far) though with 50% reduction in battery life.<br/><br/>Unable to set power mode (due to APST being enabled?).<br/><br/>Also unable to suspend PineBook Pro with NVMe drive attached. From dmesg:<br/>rockchip-pcie f8000000.pcie: PCIe link enter L2 timeout!<br/>PM: dpm_run_callback(): rockchip_pcie_suspend_noirq+0x0/0x100 returns -110<br/>PM: Devvice f8000000.pcie failed to suspend noirq: error -110<br/>PM: no irq suspend of devices failed<br/> || APST enabled by default<br/> PS 0: 6.00W<br/>PS 1: 3.50W<br/>PS 2: 3.00W<br/>PS 3: 0.1000W<br/>PS 4: 0.0025W || No<br />
|-<br />
| 2242 || KingSpec NE-512 || 512 GB || NE512 || good || || APST enabled<br/>Power states N/A || N/A <br />
|-<br />
| 2230 || Kioxia BG4 256GBTB|| 256 GB || KBG40ZNS256G || good || || APST enabled by default<br/>Power states PS 0: 3.60W<br/>PS 1: 2.60W<br/>PS 2: 2.20W<br/>PS 3: 0.005W<br/>PS 4: 0.005W ||<br />
|-<br />
| 2280 || Patriot P300 || 256 GB || P300P256GM28US || good || Booted successfully with / on NVMe and /boot on eMMC (Armbian Buster) || APSTE disabled by default<br/> PS 0: 4.50W<br/> PS 1: 2.70W<br/> PS 2: 2.16W<br/>PS 3: 0.07W<br/>PS 4: 0.002W||<br />
|-<br />
| 2280 || Team Group MP33 || 128 GB || TM8FP6128G0C101 || good || || ||<br />
|-<br />
| 2280 || Team Group MP34 || 512 GB || TM8FP6512G0C101 || fail ||APST enabled by default and scripts do not change the power mode. <br>Higher power consumption modes cause the PBP to crash<br/> || PS 0 5.55W <br/>PS 1 4.49W<br/>PS 2 3.97W <br/>PS 3 0.0490W <br/>PS 4 0.0018W ||No<br />
|-<br />
| 2280 || Digifast Ace || 256 GB || DGFA256M2L01 || good ||No touchpad issues. Board not trimmed. || PS 0 6.77W <br/>PS 1 5.71W<br/>PS 2 5.19W <br/>PS 3 0.0490W <br/>PS 4 0.0018W ||Yes<br />
<br />
|}<br />
<br />
== microSD Cards ==<br />
{| class="wikitable sortable"<br />
!Type || Make/Model || Hardware IDs || Result || Notes<br />
|-<br />
|SD Card || Samsung Evo Select 512GB || MB-ME512GA/AM || good ||<br />
|-<br />
|SD Card || Samsung Evo Plus 64GB || || good || Hdparm tested 44MBps read speeds<br />
|-<br />
|SD Card || Sandisk Ultra 400GB || || good || Works fine as a storage extension. Mounted for pictures, etc.<br />
|-<br />
|SD Card || Sandisk Ultra 16GB || || fail || Works for a short period of time but locks up completely after a certain amount of written data<br />
|-<br />
|SD Card || Sandisk Ultra 64GB (Old from 2015) || || fail || ^<br />
|-<br />
|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<br />
|-<br />
|SD Card || Sandisk Extreme Pro 64GB || || good || <br />
|}<br />
<br />
= USB hardware =<br />
<br />
== USB Card Readers ==<br />
<br />
Standalone card readers only, please; see below for multifunction devices.<br />
<br />
{| class="wikitable sortable"<br />
!Type || Make/Model || Hardware IDs || Result || Notes<br />
|-<br />
|USB-2 SDHC reader || Sandisk MobileMate+ || 0781:b2b3 || good ||<br />
|-<br />
|USB-3 SDHC/CF reader || Transcend TS-RDF8K || 8564:4000 || good ||<br />
|}<br />
<br />
== USB Networking ==<br />
<br />
Standalone network devices only, please; see below for multifunction devices<br />
<br />
{| class="wikitable sortable"<br />
!Type || Make/Model || Hardware IDs || Result || Notes<br />
|-<br />
|USB-2 Fast Ethernet adapter || Realtek RTL8152 || 0bda:8152 || good || <br />
|-<br />
|USB-2 Ethernet adapter || ASIX AX77882 || 0b95:7720 || good || <br />
|-<br />
|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/<br />
|-<br />
|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/<br />
|-<br />
|USB 3 to Gigabit Ethernet Adapter || Pluggable USB 3.0 to Ethernet Gigabit (ASIX AX88179 chipset) || 0b95:1790 || good ||<br />
|}<br />
<br />
== USB Multifunction Devices ==<br />
<br />
{| class="wikitable sortable"<br />
!Type || Make/Model || Hardware IDs || Result || Notes<br />
|-<br />
|USB-C Hub || Samsung EE-P5000 || || Power is passed through from hub to Pinebook Pro; Ethernet, HDMI, and USB-A do not work || <br />
|-<br />
|USB-C Hub || Insignia NS-PU378CHM || || Power is passed through from hub to Pinebook Pro; USB-A works; HDMI does not work || <br />
|-<br />
|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 || <br />
|-<br />
|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/]<br />
|-<br />
|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]<br />
|-<br />
|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 ||<br />
|-<br />
|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 ||<br />
|-<br />
|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 <br />
|- <br />
|4 Port USB 3 NIC || Delock 62966 || || good || 4 individually controllable Gigabit Ethernet Ports. Consider using it with own power supply<br />
|-<br />
|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.<br />
|-<br />
|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.<br />
|-<br />
|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.<br />
|-<br />
|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<br />
|-<br />
|USB-C dock || Lenovo ThinkPad 40A9 || TBD || mixed || USB hub works, audio device works, ethernet device works, display does NOT despite plug's orientation<br />
|}<br />
<br />
== USB C alternate mode DP ==<br />
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.<br />
{| class="wikitable sortable"<br />
!Type || Make/Model || Hardware IDs || Result || Notes<br />
|-<br />
|USB-C to HDMI adapter 201018 || Cable Matters || || good || Tested up to 1080p30, audio works<br />
|-<br />
|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<br />
|-<br />
|USB-C to HDMI adapter || generic || || good || Tested up to 4k60<br />
|-<br />
|USB-C to DP Adapter || OrxnQ || 04b4:5210 || good || Advertises support for 4K@60Hz, tested up to 1080p. Only FullHD resolutions available on Debian.<br />
|-<br />
|USB-C HDMI adapter (DP-alt mode) || QGeeM || || good || Manjaro 2020-01-25<br />
|-<br />
|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/<br />
|-<br />
|USB-C combo hub (HDMI, network, card slots, USB ports) || generic || || fail ||<br />
|-<br />
|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<br />
|-<br />
|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.<br />
|-<br />
|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<br />
|- <br />
|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<br />
|-<br />
|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 <br />
|-<br />
|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<br />
|-<br />
|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.<br />
|-<br />
|USB-C to HDMI adapter || MHL TH002 || || good || Tested at 1080p@60<br />
|-<br />
|USB-C combo hub (USB-C power, HDMI, 2xUSB, 1xUSB-C(no power)) || Baseus || || good<br />
|-<br />
|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.) <br />
|-<br />
|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. <br />
|-<br />
|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<br />
|-<br />
|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.<br />
|-<br />
|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.<br />
|-<br />
|USB-C to DP cable || [https://www.amazon.es/gp/product/B01N5RFAI4/ CHOETECH V-XCP-0012BK] || || good <br />
|-<br />
| [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<br />
|-<br />
|USB-C to HDMI cable || Planet Computers USB-C to HDMI cable || || fail || does not work regardless of orientation in USB slot<br />
|-<br />
|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<br />
|-<br />
|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)<br />
|-<br />
| 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<br />
|}<br />
<br />
== USB other ==<br />
{| class="wikitable sortable"<br />
!Type || Make/Model || Hardware IDs || Result || Notes<br />
|-<br />
|Wireless Mouse || Logitech M705 Marathon || || good || Uses Logitech receiver. Battery level detected in power settings.<br />
|-<br />
|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<br />
|-<br />
|Yubikey original || Yubico || 1050:0010 || good ||<br />
|-<br />
|}<br />
<br />
----<br />
<br />
= Bluetooth hardware =<br />
{| class="wikitable sortable"<br />
!Type || Make/Model || Hardware IDs || Result || Notes <br />
|-<br />
|Bluetooth Mouse || HP Z5000 || E5C13AA || good || <br />
|-<br />
|Bluetooth Mouse || Logitech M557 || || good || <br />
|-<br />
|Bluetooth Mouse || Kensington Expert Wireless Trackball || || good ||<br />
|-<br />
|Bluetooth Mouse || Logitech MX Vertical || || good || Battery level is not detected over bluetooth, detected when using the logitech receiver<br />
|-<br />
|Bluetooth Mouse || Logitech Triathlon M720 || || good ||<br />
|-<br />
|Bluetooth Mouse || Logitech Ultra-Thin Touch Mouse || || good || Detects battery level as "keyboard"<br />
|-<br />
|Bluetooth Mouse || Logitech MX Anywhere 2 || || good ||<br />
|-<br />
|Bluetooth Mouse || Logitech M535 || 910-004432 || good ||<br />
|-<br />
|Bluetooth Mouse || Microsoft Bluetooth Mouse || RJN-00002 || good ||<br />
|-<br />
|Bluetooth Mouse || Fenifox low profile || MX106-Black || good ||<br />
|-<br />
|Bluetooth Mouse || Technet || MGS479 || good ||<br />
|-<br />
|Bluetooth Keyboard || Logitech MX Keys || || good || Battery level is not detected over bluetooth, detected when using the logitech receiver<br />
|-<br />
|Bluetooth Speaker || Ivation Acoustix || || good || Use audio sink profile<br />
|-<br />
|Bluetooth Headphones || Sony WH-1000XM2 || || good* || Needs pulseaudio-module-bluetooth. *Recording untested.<br />
|-<br />
|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].<br />
|-<br />
|USB Audio & Bluetooth Headset || Sony SBH90C || || good || Works well connected via USB Type-C and Bluetooth.<br />
|-<br />
|Bluetooth Headset || BlueAnt Ribbon || 7252A-RB || good || a2dp mode works, headset mode seems to work, out of box with manjaro<br />
|-<br />
|Bluetooth Headphones || DO-SV-BTIES03 || || good || Tested on Manjaro ARM - kde<br />
|-<br />
|Bluetooth Headset || TaoTronics TT-BH090 || || good || Microphone not tested but should work as expected of a normal Linux machine<br />
|-<br />
|Bluetooth Mouse || Logitech MX Ergo || || good || Works flawlessly both on Manjaro and Armbian.<br />
|}<br />
<br />
----<br />
<br />
= Other hardware =<br />
<br />
{| class="wikitable sortable"<br />
!Type || Make/Model || Hardware IDs || Result || Notes<br />
|-<br />
|[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<br />
|-<br />
|Printer || HP DeskJet Ink Advantage 3775 || || good* || Using hplip-gui: via USB and WiFi. *Only print function tested.<br />
|-<br />
|}<br />
<br />
[[Category:PineBook Pro]]</div>Ura2https://wiki.pine64.org/index.php?title=Pinebook_Pro_Software_Releases&diff=10354Pinebook Pro Software Releases2021-05-14T19:24:09Z<p>Ura2: Compressed installers section. Removed "Daniel Thompson's Debian Installer" as the official debian installer is very actively developed now</p>
<hr />
<div>= Linux OS Image Releases =<br />
For information on how to install these images onto your device, please see the [[NOOB]] Page, which includes information on writing images to the device eMMC or an SD card<br />
<br />
== Manjaro ARM ==<br />
[[File:Manjaro.png|right|100px]]<br />
<br />
* The Manjaro project offers a mainline kernel with patches and modules to support PBPro hardware in two flavors. Both provide DD images and installer images (DD to SD card which will then install to eMMC when booted).<br />
* To learn more about Manjaro please visit [https://forum.manjaro.org/tags/manjaroarm Manjaro Forum]<br />
* You can follow the ongoing discussion about Twister OS on the PINE64 forum (https://forum.pine64.org/showthread.php?tid=8207)<br />
<br />
=== Manjaro ARM with KDE (X11) desktop [microSD / eMMC Boot] ===<br />
<br />
* [https://manjaro.org/downloads/arm/pinebook-pro/arm8-pinebook-pro-kde-plasma/ Direct download from Manjaro] (microSD image only)<br />
* [https://osdn.net/projects/manjaro-arm/storage/pbpro/kde-plasma/ Direct download from osdn.net] (both microSD and emmc-installer images)<br />
<br />
=== Manjaro ARM with XFCE desktop [microSD / eMMC Boot] ===<br />
<br />
* [https://manjaro.org/downloads/arm/pinebook-pro/arm8-pinebook-pro-xfce/ Direct download from Manjaro]<br />
* [https://osdn.net/projects/manjaro-arm/storage/pbpro/xfce/ Direct download from osdn.net]<br />
<br />
=== Manjaro ARM with i3 desktop [microSD / eMMC Boot] ===<br />
<br />
* [https://manjaro.org/downloads/arm/pinebook-pro/arm8-pinebook-pro-i3/ Direct download from Manjaro]<br />
* [https://osdn.net/projects/manjaro-arm/storage/pbpro/i3/ Direct download from osdn.net]<br />
<br />
=== Manjaro ARM with Sway desktop [microSD / eMMC Boot] ===<br />
<br />
* [https://osdn.net/projects/manjaro-arm/storage/pbpro/sway/ Direct download from osdn.net]<br />
<br />
== Armbian ==<br />
[[File:armbian.png|right|100px]]<br />
<br />
* To find out more about Armbian and available options please visit their [https://www.armbian.com/pinebook-pro/ site]<br />
* DD image to microSD card or eMMC module and boot. Highly recommend using [https://etcher.io/ Etcher]<br />
<br />
=== Armbian Ubuntu Focal XFCE Desktop mainline kernel [microSD / eMMC Boot] ===<br />
* Armbian provides a mainline kernel build images for Ubuntu Focal with XFCE Desktop<br />
* DD image (for 8GB micoSD card or eMMC Module and above)<br />
** [https://dl.armbian.com/pinebook-pro/Focal_current_desktop Armbian's Pinebook Pro Ubuntu Focal XFCE Desktop download site]<br />
<br />
=== Armbian Ubuntu Focal XFCE Desktop legacy kernel [microSD / eMMC Boot] ===<br />
* Armbian provides a legacy kernel 4.4 build images for Ubuntu Focal with XFCE Desktop<br />
* DD image (for 8GB microSD card or eMMC Module and above)<br />
** [https://dl.armbian.com/pinebook-pro/Focal_legacy_desktop Armbian's Pinebook Pro Ubuntu Focal XFCE Desktop download site]<br />
<br />
=== Armbian Debian Buster XFCE Desktop legacy kernel [microSD / eMMC Boot] ===<br />
* Armbian provides a legacy kernel 4.4 build images for Debian Buster with XFCE Desktop<br />
* DD image (for 8GB micoSD card or eMMC Module and above)<br />
** [https://dl.armbian.com/pinebook-pro/Buster_legacy_desktop Armbian's Pinebook Pro Debian Buster XFCE Desktop download site]<br />
<br />
=== Armbian Ubuntu Bionic XFCE Desktop legacy kernel [microSD / eMMC Boot] ===<br />
* Armbian provides a legacy kernel 4.4 build images for Ubuntu Bionic with XFCE Desktop<br />
* DD image (for 8GB micoSD card or eMMC Module and above)<br />
** [https://dl.armbian.com/pinebook-pro/Bionic_legacy_desktop Armbian's Pinebook Pro Ubuntu Bionic XFCE Desktop download site]<br />
<br />
== Twister OS ==<br />
[[File:Twister_OS.png|right|100px]]<br />
<br />
=== Twister OS Armbian-Reforged XFCE Dsktop [microSD boot]===<br />
* For more infomation on Twister OS, please visit this {https://twisteros.com/ official site]<br />
* You can follow the ongoing discussion about Twister OS on the PINE64 forum (https://forum.pine64.org/showthread.php?tid=12192)<br />
* After flashing image with Etcher, edit /boot/armbianEnv.txt, replace the dtb name with rk3399-pinebook-pro.dtb.<br />
* DD image (for 16GB microSD card /16GB eMMC module and above):<br />
** [https://twisteros.com/twisterarmbian.html Direct download latest images from Twister OS's website]<br />
** size: 2.8GB<br />
* Login with<br />
** password: asdasd<br />
<br />
== Fedora ==<br />
[[File:fedora1.png|right|100px]]<br />
<br />
=== Fedora 34/33/32 Gnome/KDE/Minimal Images [microSD / eMMC Boot] ===<br />
* Unofficial images based on Fedora, and a [https://copr.fedorainfracloud.org/coprs/aptupdate/pinebook-pro/ copr] repository for kernel and tweaks.<br />
* To learn more about how they are build [https://github.com/bengtfredh/pinebook-pro-fedora-installer Install script].<br />
* DD image (for 12GB microSD card / eMMC module and above) [https://github.com/bengtfredh/pinebook-pro-fedora-installer/wiki/How-to-Resize---Expand-a-Btrfs-Volume---Filesystem How to expand btrfs]<br />
** [https://s3.fredhs.net/minio/pinebook-pro-image/ Fedora Pinebook Pro Images]<br />
<br />
=== Fedora 32 Cinnamon Desktop OS Image [microSD / eMMC Boot] ===<br />
* This image contains an install of Fedora with [https://cinnamon-spices.linuxmint.com/ Cinnamon] desktop environment. <br />
* To learn more about Fedora please visit the [https://getfedora.org/ official website].<br />
* DD image (for 12GB microSD card / eMMC module and above)<br />
** [https://builds.armdevelopers.com/pinebook-pro/releases/dev/Fedora32-Cinnamon-Desktop-202009.0.pinebook-pro.img.xz Fedora 32 Pinebook Pro Image]<br />
* login with:<br />
** username: root<br />
** password: fedora<br />
<br />
=== Fedora 32 KDE Desktop OS Image [microSD / eMMC Boot] ===<br />
* This image contains an install of Fedora with [https://kde.org/ KDE aka Plasma] desktop environment. <br />
* To learn more about Fedora please visit the [https://getfedora.org/ official website].<br />
* DD image (for 12GB microSD card / eMMC module and above)<br />
** [https://builds.armdevelopers.com/pinebook-pro/releases/dev/Fedora32-KDE-Desktop-202009.0.pinebook-pro.img.xz Fedora 32 Pinebook Pro Image]<br />
* login with:<br />
** username: root<br />
** password: fedora<br />
<br />
=== Fedora 32 Xfce Desktop OS Image [microSD / eMMC Boot] ===<br />
* This image contains an install of Fedora with [https://xfce.org/ xfce] desktop environment. <br />
* To learn more about Fedora please visit the [https://getfedora.org/ official website].<br />
* DD image (for 12GB microSD card / eMMC module and above)<br />
** [https://builds.armdevelopers.com/pinebook-pro/releases/dev/Fedora32-Xfce-Desktop-202009.0.pinebook-pro.img.xz Fedora 32 Pinebook Pro Image]<br />
* login with:<br />
** username: root<br />
** password: fedora<br />
<br />
=== Fedora 32 Gnome OS Image [microSD / eMMC Boot] ===<br />
* This image contains an install of Fedora with [https://www.gnome.org/gnome-3/ GNOME 3] desktop environment. <br />
* To learn more about Fedora please visit the [https://getfedora.org/ official website].<br />
* DD image (for 12GB microSD card / eMMC module and above)<br />
** [https://builds.armdevelopers.com/pinebook-pro/releases/dev/Fedora32-Workstation-202009.0.pinebook-pro.img.xz Fedora 32 Pinebook Pro Image]<br />
* login with:<br />
** username: root<br />
** password: fedora<br />
<br />
== Arch Linux ==<br />
[[File:Archlinux-logo.png|right|100px]]<br />
<br />
=== Arch Linux ARM install image [microSD/USB Boot] ===<br />
* archiso image customized for Arch Linux ARM on the Pinebook Pro<br />
* DD image (for 1GB or larger microSD card/USB stick):<br />
** [https://github.com/nadiaholmquist/archiso-pbp/releases Direct download for latest releases from GitHub]<br />
** size: 579MB<br />
* Automatic login as root<br />
* Make sure to thoroughly read the [https://github.com/nadiaholmquist/archiso-pbp/blob/master/README.md readme] and [https://github.com/nadiaholmquist/archiso-pbp/blob/master/FAQ.md FAQ], otherwise follow the normal Arch installation guide.<br />
<br />
== postmarketOS ==<br />
[[File:PostmarketOS logo.png|right|100px]]<br />
<br />
===Official postmarketOS build [microSD/ eMMC Boot] ===<br />
* Official postmarketOS build with the GNOME desktop for the Pinebook Pro. <br />
* DD image (for 8GB microSD card /16GB eMMC module and above):<br />
** [http://images.postmarketos.org/pinebookpro/ Direct download latest images from postmarketOS]<br />
** size: 400MB<br />
* Login with<br />
** username: demo<br />
** password: demo OR 147147<br />
<br />
==Kali Linux==<br />
[[File:Kali.jpeg|right|100px]]<br />
<br />
=== Kali Linux prebuilt OS images for Pinebook Pro [SD/eMMC boot]===<br />
* Official pre-built OS images of Kali Linux for the Pinebook Pro featuring all tools you'd expect from the distribution. <br />
* DD image (for 8GB microSD card /16GB eMMC module and above):<br />
** [https://www.offensive-security.com/kali-linux-arm-images/ Direct download latest images from Offensive Security's website]<br />
** size: 2.0GB<br />
* Login with<br />
** username: kali<br />
** password: kali<br />
<br />
== Q4OS ==<br />
[[File:q4os.png|right|100px]]<br />
<br />
=== Q4OS Test Build Image [microSD / eMMC Boot] ===<br />
* Q4OS is advertised as a 'fast and powerful operating system based on the latest technologies while offering highly productive desktop environment'<br />
* To learn more please visit the [https://forum.pine64.org/showthread.php?tid=8385 PINE64 forum] or official [https://q4os.org/index.html Q4OS website]<br />
* DD image (for 8GB microSD card / eMMC module and above)<br />
** [https://sourceforge.net/projects/q4os/files/testing/ Direct download latest release build from SourceForge]<br />
* User account and password are created on first run<br />
<br />
= BSD OS Image Release =<br />
<br />
==NetBSD==<br />
[[File:netbsd.png|right|100px]]<br />
<br />
=== NetBSD [microSD /eMMC Boot] ===<br />
* To learn more about NetBSD please visit [https://www.netbsd.org/ NetBSD main page] <br />
* DD image to microSD card or eMMC module. Highly recommend using [https://etcher.io/ Etcher]<br />
** [http://www.armbsd.org/arm/ Direct download from NetBSD]<br />
* Console and SSH default login:<br />
** username: root<br />
** password: [none]<br />
* Instructions concerning enabling SSH can be found [https://www.netbsd.org/docs/guide/en/chap-boot.html#chap-boot-ssh here]<br />
<br />
==OpenBSD==<br />
[[File:Puffy_mascot_openbsd.png|right|100px]]<br />
<br />
=== OpenBSD ===<br />
* To learn more about OpenBSD, please visit [https://www.openbsd.org/ OpenBSD main page]<br />
* ARM64 images, (including support for Pinebook Pro), can be found here [https://www.openbsd.org/arm64.html OpenBSD arm64]<br />
<br />
= Linux Installer Releases =<br />
<br />
<br />
=== Manjaro ARM ===<br />
[[File:Manjaro.png|right|100px]]<br />
<br />
The [https://gitlab.manjaro.org/manjaro-arm/applications/manjaro-arm-installer manjaro-arm-installer] script is intended to install Manjaro ARM directly to SD/eMMC cards without the need for images (including LXQT, Mate & CuboCore editions, as well as full disk encryption). Running on a Linux x86 computer, it can install Manjaro ARM directly to an empty eMMC using an eMMC to USB adapter. The script can also be run from SD to install an image to the eMMC.<br />
<br />
=== Debian ===<br />
[[File:debian.png|right|100px]]<br />
* Uses only the upstream kernel and firmware without special patches<br />
* No graphical display yet, works only through serial console<br />
* Requires adding the non-free component to your /etc/apt/sources.list file and installing the "firmware-linux" package for Wi-Fi and Bluetooth support<br />
* Installer is loaded into RAM, can install onto the same media from which it’s booted<br />
* Supports automatic partitioning and full disk encryption through LVM<br />
* Installer currently doesn't install the bootloader, leaving the installed system in an unbootable state until it's manually added<br />
<br />
[https://d-i.debian.org/daily-images/arm64/daily/netboot/SD-card-images/ The relevant files are built daily here] and may sometimes be unavailable if the build system is having issues. The "README.concatenateable_images" file provides instructions on how to combine the partition.img.gz file with the firmware.pinebook-pro.rk3399.img.gz file in order to create a DD-able image.<br />
<br />
The official images are '''not''' recommended yet until the display begins working and the installer properly installs the bootloader. Most users will want to see [[Pinebook Pro Debian Installer|Daniel Thompson's Debian Installer]] instead.<br />
<br />
=== Gentoo ===<br />
[[File:GentooLogo.png|right|100px]]<br />
<br />
* This is a script that prepares a Gentoo arm64 stage 3 tarball for the Pinebook Pro<br />
** The script takes care of device specifics like an optimized make.conf, an overlay that provides kernel and firmware amongst others, and other miscellaneous fixes<br />
* The usual tarball setup as per [https://wiki.gentoo.org/wiki/Handbook:AMD64 Gentoo Handbook] is left to the user.<br />
* Forum thread with instructions at https://forum.pine64.org/showthread.php?tid=8765<br />
<br />
=== Kali Linux ===<br />
[[File:Kali.jpeg|right|100px]]<br />
<br />
* This is a script to create official Kali Linux OS images for the Pinebook Pro<br />
** The script carries out the build process in entirety and is Pinebook Pro specific<br />
* Please pull the latest [https://gitlab.com/kalilinux/build-scripts/kali-arm/blob/master/pinebook-pro.sh Kali Linux install script] from the project's GitLab.<br />
* For more information regarding building the OS image please read the README instruction at https://gitlab.com/kalilinux/build-scripts/kali-arm/blob/master/README.md<br />
<br />
=== K1ss OS ===<br />
[[File:K1ss.png|right|100px]]<br />
<br />
* This is a repository containing an unofficial port of KISS Linux to aarch64. The tarball is built for generic aarch64, currently being tested on the Pinebook Pro.<br />
* Please pull the latest [https://github.com/jedavies-dev/kiss-aarch64 K1ss Linux install script] from the project's GitHub.<br />
* * You can follow the ongoing discussion about K1ss Linux on the PINE64 forum (https://forum.pine64.org/showthread.php?tid=9304)<br />
<br />
=== NixOS ===<br />
[[File:nixos.png|right|100px]]<br />
<br />
* This is instructions to install NixOS on the Pinebook Pro: https://nixos.wiki/wiki/NixOS_on_ARM/PINE64_Pinebook_Pro<br />
* Please pull the latest [https://github.com/samueldr/wip-pinebook-pro samueldr's repository ] from the project's GitHub.<br />
* * There is a good chance we will see Tier 1 support for aarch64, including the Pinebook Pro, in 2021 (https://github.com/NixOS/rfcs/pull/87)<br />
* * You can follow the ongoing discussion about NixOS on the PINE64 forum (https://forum.pine64.org/showthread.php?tid=10524)<br />
<br />
=== SkiffOS ===<br />
[[File:SkiffOS-Icon-1.png|right|100px]]<br />
<br />
* Instructions to build/install on the Pinebook Pro: https://github.com/skiffos/SkiffOS/tree/master/configs/pine64/book<br />
* Please pull the latest version from the project's GitHub.<br />
* Compiling the boot image takes approximately 30 minutes.<br />
* Easily configure the kernel, compiler, etc with Buildroot.<br />
* Pre-built ISOs will be available with the upcoming 2021.02 <br />
release.<br />
<br />
<br />
[[Category:PineBook Pro]]</div>Ura2https://wiki.pine64.org/index.php?title=Pinebook_Pro_Software_Releases&diff=10353Pinebook Pro Software Releases2021-05-14T19:16:38Z<p>Ura2: added manjaro logo to the right of the installer</p>
<hr />
<div>= Linux OS Image Releases =<br />
For information on how to install these images onto your device, please see the [[NOOB]] Page, which includes information on writing images to the device eMMC or an SD card<br />
<br />
== Manjaro ARM ==<br />
[[File:Manjaro.png|right|100px]]<br />
<br />
* The Manjaro project offers a mainline kernel with patches and modules to support PBPro hardware in two flavors. Both provide DD images and installer images (DD to SD card which will then install to eMMC when booted).<br />
* To learn more about Manjaro please visit [https://forum.manjaro.org/tags/manjaroarm Manjaro Forum]<br />
* You can follow the ongoing discussion about Twister OS on the PINE64 forum (https://forum.pine64.org/showthread.php?tid=8207)<br />
<br />
=== Manjaro ARM with KDE (X11) desktop [microSD / eMMC Boot] ===<br />
<br />
* [https://manjaro.org/downloads/arm/pinebook-pro/arm8-pinebook-pro-kde-plasma/ Direct download from Manjaro] (microSD image only)<br />
* [https://osdn.net/projects/manjaro-arm/storage/pbpro/kde-plasma/ Direct download from osdn.net] (both microSD and emmc-installer images)<br />
<br />
=== Manjaro ARM with XFCE desktop [microSD / eMMC Boot] ===<br />
<br />
* [https://manjaro.org/downloads/arm/pinebook-pro/arm8-pinebook-pro-xfce/ Direct download from Manjaro]<br />
* [https://osdn.net/projects/manjaro-arm/storage/pbpro/xfce/ Direct download from osdn.net]<br />
<br />
=== Manjaro ARM with i3 desktop [microSD / eMMC Boot] ===<br />
<br />
* [https://manjaro.org/downloads/arm/pinebook-pro/arm8-pinebook-pro-i3/ Direct download from Manjaro]<br />
* [https://osdn.net/projects/manjaro-arm/storage/pbpro/i3/ Direct download from osdn.net]<br />
<br />
=== Manjaro ARM with Sway desktop [microSD / eMMC Boot] ===<br />
<br />
* [https://osdn.net/projects/manjaro-arm/storage/pbpro/sway/ Direct download from osdn.net]<br />
<br />
== Armbian ==<br />
[[File:armbian.png|right|100px]]<br />
<br />
* To find out more about Armbian and available options please visit their [https://www.armbian.com/pinebook-pro/ site]<br />
* DD image to microSD card or eMMC module and boot. Highly recommend using [https://etcher.io/ Etcher]<br />
<br />
=== Armbian Ubuntu Focal XFCE Desktop mainline kernel [microSD / eMMC Boot] ===<br />
* Armbian provides a mainline kernel build images for Ubuntu Focal with XFCE Desktop<br />
* DD image (for 8GB micoSD card or eMMC Module and above)<br />
** [https://dl.armbian.com/pinebook-pro/Focal_current_desktop Armbian's Pinebook Pro Ubuntu Focal XFCE Desktop download site]<br />
<br />
=== Armbian Ubuntu Focal XFCE Desktop legacy kernel [microSD / eMMC Boot] ===<br />
* Armbian provides a legacy kernel 4.4 build images for Ubuntu Focal with XFCE Desktop<br />
* DD image (for 8GB microSD card or eMMC Module and above)<br />
** [https://dl.armbian.com/pinebook-pro/Focal_legacy_desktop Armbian's Pinebook Pro Ubuntu Focal XFCE Desktop download site]<br />
<br />
=== Armbian Debian Buster XFCE Desktop legacy kernel [microSD / eMMC Boot] ===<br />
* Armbian provides a legacy kernel 4.4 build images for Debian Buster with XFCE Desktop<br />
* DD image (for 8GB micoSD card or eMMC Module and above)<br />
** [https://dl.armbian.com/pinebook-pro/Buster_legacy_desktop Armbian's Pinebook Pro Debian Buster XFCE Desktop download site]<br />
<br />
=== Armbian Ubuntu Bionic XFCE Desktop legacy kernel [microSD / eMMC Boot] ===<br />
* Armbian provides a legacy kernel 4.4 build images for Ubuntu Bionic with XFCE Desktop<br />
* DD image (for 8GB micoSD card or eMMC Module and above)<br />
** [https://dl.armbian.com/pinebook-pro/Bionic_legacy_desktop Armbian's Pinebook Pro Ubuntu Bionic XFCE Desktop download site]<br />
<br />
== Twister OS ==<br />
[[File:Twister_OS.png|right|100px]]<br />
<br />
=== Twister OS Armbian-Reforged XFCE Dsktop [microSD boot]===<br />
* For more infomation on Twister OS, please visit this {https://twisteros.com/ official site]<br />
* You can follow the ongoing discussion about Twister OS on the PINE64 forum (https://forum.pine64.org/showthread.php?tid=12192)<br />
* After flashing image with Etcher, edit /boot/armbianEnv.txt, replace the dtb name with rk3399-pinebook-pro.dtb.<br />
* DD image (for 16GB microSD card /16GB eMMC module and above):<br />
** [https://twisteros.com/twisterarmbian.html Direct download latest images from Twister OS's website]<br />
** size: 2.8GB<br />
* Login with<br />
** password: asdasd<br />
<br />
== Fedora ==<br />
[[File:fedora1.png|right|100px]]<br />
<br />
=== Fedora 34/33/32 Gnome/KDE/Minimal Images [microSD / eMMC Boot] ===<br />
* Unofficial images based on Fedora, and a [https://copr.fedorainfracloud.org/coprs/aptupdate/pinebook-pro/ copr] repository for kernel and tweaks.<br />
* To learn more about how they are build [https://github.com/bengtfredh/pinebook-pro-fedora-installer Install script].<br />
* DD image (for 12GB microSD card / eMMC module and above) [https://github.com/bengtfredh/pinebook-pro-fedora-installer/wiki/How-to-Resize---Expand-a-Btrfs-Volume---Filesystem How to expand btrfs]<br />
** [https://s3.fredhs.net/minio/pinebook-pro-image/ Fedora Pinebook Pro Images]<br />
<br />
=== Fedora 32 Cinnamon Desktop OS Image [microSD / eMMC Boot] ===<br />
* This image contains an install of Fedora with [https://cinnamon-spices.linuxmint.com/ Cinnamon] desktop environment. <br />
* To learn more about Fedora please visit the [https://getfedora.org/ official website].<br />
* DD image (for 12GB microSD card / eMMC module and above)<br />
** [https://builds.armdevelopers.com/pinebook-pro/releases/dev/Fedora32-Cinnamon-Desktop-202009.0.pinebook-pro.img.xz Fedora 32 Pinebook Pro Image]<br />
* login with:<br />
** username: root<br />
** password: fedora<br />
<br />
=== Fedora 32 KDE Desktop OS Image [microSD / eMMC Boot] ===<br />
* This image contains an install of Fedora with [https://kde.org/ KDE aka Plasma] desktop environment. <br />
* To learn more about Fedora please visit the [https://getfedora.org/ official website].<br />
* DD image (for 12GB microSD card / eMMC module and above)<br />
** [https://builds.armdevelopers.com/pinebook-pro/releases/dev/Fedora32-KDE-Desktop-202009.0.pinebook-pro.img.xz Fedora 32 Pinebook Pro Image]<br />
* login with:<br />
** username: root<br />
** password: fedora<br />
<br />
=== Fedora 32 Xfce Desktop OS Image [microSD / eMMC Boot] ===<br />
* This image contains an install of Fedora with [https://xfce.org/ xfce] desktop environment. <br />
* To learn more about Fedora please visit the [https://getfedora.org/ official website].<br />
* DD image (for 12GB microSD card / eMMC module and above)<br />
** [https://builds.armdevelopers.com/pinebook-pro/releases/dev/Fedora32-Xfce-Desktop-202009.0.pinebook-pro.img.xz Fedora 32 Pinebook Pro Image]<br />
* login with:<br />
** username: root<br />
** password: fedora<br />
<br />
=== Fedora 32 Gnome OS Image [microSD / eMMC Boot] ===<br />
* This image contains an install of Fedora with [https://www.gnome.org/gnome-3/ GNOME 3] desktop environment. <br />
* To learn more about Fedora please visit the [https://getfedora.org/ official website].<br />
* DD image (for 12GB microSD card / eMMC module and above)<br />
** [https://builds.armdevelopers.com/pinebook-pro/releases/dev/Fedora32-Workstation-202009.0.pinebook-pro.img.xz Fedora 32 Pinebook Pro Image]<br />
* login with:<br />
** username: root<br />
** password: fedora<br />
<br />
== Arch Linux ==<br />
[[File:Archlinux-logo.png|right|100px]]<br />
<br />
=== Arch Linux ARM install image [microSD/USB Boot] ===<br />
* archiso image customized for Arch Linux ARM on the Pinebook Pro<br />
* DD image (for 1GB or larger microSD card/USB stick):<br />
** [https://github.com/nadiaholmquist/archiso-pbp/releases Direct download for latest releases from GitHub]<br />
** size: 579MB<br />
* Automatic login as root<br />
* Make sure to thoroughly read the [https://github.com/nadiaholmquist/archiso-pbp/blob/master/README.md readme] and [https://github.com/nadiaholmquist/archiso-pbp/blob/master/FAQ.md FAQ], otherwise follow the normal Arch installation guide.<br />
<br />
== postmarketOS ==<br />
[[File:PostmarketOS logo.png|right|100px]]<br />
<br />
===Official postmarketOS build [microSD/ eMMC Boot] ===<br />
* Official postmarketOS build with the GNOME desktop for the Pinebook Pro. <br />
* DD image (for 8GB microSD card /16GB eMMC module and above):<br />
** [http://images.postmarketos.org/pinebookpro/ Direct download latest images from postmarketOS]<br />
** size: 400MB<br />
* Login with<br />
** username: demo<br />
** password: demo OR 147147<br />
<br />
==Kali Linux==<br />
[[File:Kali.jpeg|right|100px]]<br />
<br />
=== Kali Linux prebuilt OS images for Pinebook Pro [SD/eMMC boot]===<br />
* Official pre-built OS images of Kali Linux for the Pinebook Pro featuring all tools you'd expect from the distribution. <br />
* DD image (for 8GB microSD card /16GB eMMC module and above):<br />
** [https://www.offensive-security.com/kali-linux-arm-images/ Direct download latest images from Offensive Security's website]<br />
** size: 2.0GB<br />
* Login with<br />
** username: kali<br />
** password: kali<br />
<br />
== Q4OS ==<br />
[[File:q4os.png|right|100px]]<br />
<br />
=== Q4OS Test Build Image [microSD / eMMC Boot] ===<br />
* Q4OS is advertised as a 'fast and powerful operating system based on the latest technologies while offering highly productive desktop environment'<br />
* To learn more please visit the [https://forum.pine64.org/showthread.php?tid=8385 PINE64 forum] or official [https://q4os.org/index.html Q4OS website]<br />
* DD image (for 8GB microSD card / eMMC module and above)<br />
** [https://sourceforge.net/projects/q4os/files/testing/ Direct download latest release build from SourceForge]<br />
* User account and password are created on first run<br />
<br />
= BSD OS Image Release =<br />
<br />
==NetBSD==<br />
[[File:netbsd.png|right|100px]]<br />
<br />
=== NetBSD [microSD /eMMC Boot] ===<br />
* To learn more about NetBSD please visit [https://www.netbsd.org/ NetBSD main page] <br />
* DD image to microSD card or eMMC module. Highly recommend using [https://etcher.io/ Etcher]<br />
** [http://www.armbsd.org/arm/ Direct download from NetBSD]<br />
* Console and SSH default login:<br />
** username: root<br />
** password: [none]<br />
* Instructions concerning enabling SSH can be found [https://www.netbsd.org/docs/guide/en/chap-boot.html#chap-boot-ssh here]<br />
<br />
==OpenBSD==<br />
[[File:Puffy_mascot_openbsd.png|right|100px]]<br />
<br />
=== OpenBSD ===<br />
* To learn more about OpenBSD, please visit [https://www.openbsd.org/ OpenBSD main page]<br />
* ARM64 images, (including support for Pinebook Pro), can be found here [https://www.openbsd.org/arm64.html OpenBSD arm64]<br />
<br />
= Linux Installer Releases =<br />
<br />
<br />
=== Manjaro ARM installer ===<br />
[[File:Manjaro.png|right|100px]]<br />
<br />
The [https://gitlab.manjaro.org/manjaro-arm/applications/manjaro-arm-installer manjaro-arm-installer] script is intended to install Manjaro ARM directly to SD/eMMC cards without the need for images (including LXQT, Mate & CuboCore editions, as well as full disk encryption). Running on a Linux x86 computer, it can install Manjaro ARM directly to an empty eMMC using an eMMC to USB adapter. The script can also be run from SD to install an image to the eMMC.<br />
<br />
== Debian Installer ==<br />
[[File:debian.png|right|100px]]<br />
<br />
=== Daniel Thompson's Debian Installer for the Pinebook Pro ===<br />
* This is an image creator and Debian installer that runs from an existing Linux OS and installs Debian Bullseye<br />
** Installer can configure an encrypted rootfs and provides a choice of desktops, including the default Debian desktop based on Gnome 3<br />
** Strict adoption of upstream Debian packages (with exception of kernel and bootloaders) in order to provide a clean upgrade path as Bullseye matures<br />
* Download at: https://github.com/daniel-thompson/pinebook-pro-debian-installer/<br />
* Pull requests welcome but for discussion and support please use [https://forum.pine64.org/showthread.php?tid=8487 the forum topic].<br />
<br />
For more information, see the [[Pinebook_Pro_Debian_Installer]] wiki page<br />
<br />
=== Official Debian Installer Images ===<br />
* Uses only the upstream kernel and firmware without special patches<br />
* No graphical display yet, works only through serial console<br />
* Requires adding the non-free component to your /etc/apt/sources.list file and installing the "firmware-linux" package for Wi-Fi and Bluetooth support<br />
* Installer is loaded into RAM, can install onto the same media from which it’s booted<br />
* Supports automatic partitioning and full disk encryption through LVM<br />
* Installer currently doesn't install the bootloader, leaving the installed system in an unbootable state until it's manually added<br />
<br />
[https://d-i.debian.org/daily-images/arm64/daily/netboot/SD-card-images/ The relevant files are built daily here] and may sometimes be unavailable if the build system is having issues. The "README.concatenateable_images" file provides instructions on how to combine the partition.img.gz file with the firmware.pinebook-pro.rk3399.img.gz file in order to create a DD-able image.<br />
<br />
The official images are '''not''' recommended yet until the display begins working and the installer properly installs the bootloader. Most users will want to see [[Pinebook Pro Debian Installer|Daniel Thompson's Debian Installer]] instead.<br />
<br />
<br />
== Gentoo Script ==<br />
[[File:GentooLogo.png|right|100px]]<br />
<br />
=== Gentoo Script for Pinebook Pro ===<br />
* This is a script that prepares a Gentoo arm64 stage 3 tarball for the Pinebook Pro<br />
** The script takes care of device specifics like an optimized make.conf, an overlay that provides kernel and firmware amongst others, and other miscellaneous fixes<br />
* The usual tarball setup as per [https://wiki.gentoo.org/wiki/Handbook:AMD64 Gentoo Handbook] is left to the user.<br />
* Forum thread with instructions at https://forum.pine64.org/showthread.php?tid=8765<br />
<br />
<br />
==Kali Script==<br />
[[File:Kali.jpeg|right|100px]]<br />
<br />
=== Kali Linux for Pinebook Pro ===<br />
* This is a script to create official Kali Linux OS images for the Pinebook Pro<br />
** The script carries out the build process in entirety and is Pinebook Pro specific<br />
* Please pull the latest [https://gitlab.com/kalilinux/build-scripts/kali-arm/blob/master/pinebook-pro.sh Kali Linux install script] from the project's GitLab.<br />
* For more information regarding building the OS image please read the README instruction at https://gitlab.com/kalilinux/build-scripts/kali-arm/blob/master/README.md<br />
<br />
<br />
==K1ss OS Script==<br />
[[File:K1ss.png|right|100px]]<br />
<br />
=== K1ss Linux for Pinebook Pro ===<br />
* This is a repository containing an unofficial port of KISS Linux to aarch64. The tarball is built for generic aarch64, currently being tested on the Pinebook Pro.<br />
* Please pull the latest [https://github.com/jedavies-dev/kiss-aarch64 K1ss Linux install script] from the project's GitHub.<br />
* * You can follow the ongoing discussion about K1ss Linux on the PINE64 forum (https://forum.pine64.org/showthread.php?tid=9304)<br />
<br />
<br />
==NixOS Script==<br />
[[File:nixos.png|right|100px]]<br />
<br />
=== NixOS for Pinebook Pro ===<br />
* This is instructions to install NixOS on the Pinebook Pro: https://nixos.wiki/wiki/NixOS_on_ARM/PINE64_Pinebook_Pro<br />
* Please pull the latest [https://github.com/samueldr/wip-pinebook-pro samueldr's repository ] from the project's GitHub.<br />
* * There is a good chance we will see Tier 1 support for aarch64, including the Pinebook Pro, in 2021 (https://github.com/NixOS/rfcs/pull/87)<br />
* * You can follow the ongoing discussion about NixOS on the PINE64 forum (https://forum.pine64.org/showthread.php?tid=10524)<br />
<br />
==SkiffOS for Pinebook Pro ==<br />
[[File:SkiffOS-Icon-1.png|right|100px]]<br />
<br />
=== SkiffOS Boot Image for Pinebook Pro ===<br />
* Instructions to build/install on the Pinebook Pro: https://github.com/skiffos/SkiffOS/tree/master/configs/pine64/book<br />
* Please pull the latest version from the project's GitHub.<br />
* Compiling the boot image takes approximately 30 minutes.<br />
* Easily configure the kernel, compiler, etc with Buildroot.<br />
* Pre-built ISOs will be available with the upcoming 2021.02 <br />
release.<br />
<br />
=== Skiff Core ===<br />
* Supports multiple distros running simultaneously.<br />
* Optionally build from scratch on device on first boot.<br />
* Pre-built multi-arch core container images are available.<br />
<br />
=== GentooLTO with KDE Apps ===<br />
<br />
* GentooLTO with O3 optimized KDE Desktop configuration.<br />
* Use <tt>SKIFF_CONFIG=pine64/book,core/pinebook_gentoo</tt><br />
* Default sign-in is username "core" w/ empty password.<br />
<br />
<br />
[[Category:PineBook Pro]]</div>Ura2https://wiki.pine64.org/index.php?title=Pinebook_Pro_Software_Releases&diff=10352Pinebook Pro Software Releases2021-05-14T19:00:12Z<p>Ura2: Removed Twiser OS Monka Manjaro because no-longer maintained. Fixed some consistency problems.</p>
<hr />
<div>= Linux OS Image Releases =<br />
For information on how to install these images onto your device, please see the [[NOOB]] Page, which includes information on writing images to the device eMMC or an SD card<br />
<br />
== Manjaro ARM ==<br />
[[File:Manjaro.png|right|100px]]<br />
<br />
* The Manjaro project offers a mainline kernel with patches and modules to support PBPro hardware in two flavors. Both provide DD images and installer images (DD to SD card which will then install to eMMC when booted).<br />
* To learn more about Manjaro please visit [https://forum.manjaro.org/tags/manjaroarm Manjaro Forum]<br />
* You can follow the ongoing discussion about Twister OS on the PINE64 forum (https://forum.pine64.org/showthread.php?tid=8207)<br />
<br />
=== Manjaro ARM with KDE (X11) desktop [microSD / eMMC Boot] ===<br />
<br />
* [https://manjaro.org/downloads/arm/pinebook-pro/arm8-pinebook-pro-kde-plasma/ Direct download from Manjaro] (microSD image only)<br />
* [https://osdn.net/projects/manjaro-arm/storage/pbpro/kde-plasma/ Direct download from osdn.net] (both microSD and emmc-installer images)<br />
<br />
=== Manjaro ARM with XFCE desktop [microSD / eMMC Boot] ===<br />
<br />
* [https://manjaro.org/downloads/arm/pinebook-pro/arm8-pinebook-pro-xfce/ Direct download from Manjaro]<br />
* [https://osdn.net/projects/manjaro-arm/storage/pbpro/xfce/ Direct download from osdn.net]<br />
<br />
=== Manjaro ARM with i3 desktop [microSD / eMMC Boot] ===<br />
<br />
* [https://manjaro.org/downloads/arm/pinebook-pro/arm8-pinebook-pro-i3/ Direct download from Manjaro]<br />
* [https://osdn.net/projects/manjaro-arm/storage/pbpro/i3/ Direct download from osdn.net]<br />
<br />
=== Manjaro ARM with Sway desktop [microSD / eMMC Boot] ===<br />
<br />
* [https://osdn.net/projects/manjaro-arm/storage/pbpro/sway/ Direct download from osdn.net]<br />
<br />
== Armbian ==<br />
[[File:armbian.png|right|100px]]<br />
<br />
* To find out more about Armbian and available options please visit their [https://www.armbian.com/pinebook-pro/ site]<br />
* DD image to microSD card or eMMC module and boot. Highly recommend using [https://etcher.io/ Etcher]<br />
<br />
=== Armbian Ubuntu Focal XFCE Desktop mainline kernel [microSD / eMMC Boot] ===<br />
* Armbian provides a mainline kernel build images for Ubuntu Focal with XFCE Desktop<br />
* DD image (for 8GB micoSD card or eMMC Module and above)<br />
** [https://dl.armbian.com/pinebook-pro/Focal_current_desktop Armbian's Pinebook Pro Ubuntu Focal XFCE Desktop download site]<br />
<br />
=== Armbian Ubuntu Focal XFCE Desktop legacy kernel [microSD / eMMC Boot] ===<br />
* Armbian provides a legacy kernel 4.4 build images for Ubuntu Focal with XFCE Desktop<br />
* DD image (for 8GB microSD card or eMMC Module and above)<br />
** [https://dl.armbian.com/pinebook-pro/Focal_legacy_desktop Armbian's Pinebook Pro Ubuntu Focal XFCE Desktop download site]<br />
<br />
=== Armbian Debian Buster XFCE Desktop legacy kernel [microSD / eMMC Boot] ===<br />
* Armbian provides a legacy kernel 4.4 build images for Debian Buster with XFCE Desktop<br />
* DD image (for 8GB micoSD card or eMMC Module and above)<br />
** [https://dl.armbian.com/pinebook-pro/Buster_legacy_desktop Armbian's Pinebook Pro Debian Buster XFCE Desktop download site]<br />
<br />
=== Armbian Ubuntu Bionic XFCE Desktop legacy kernel [microSD / eMMC Boot] ===<br />
* Armbian provides a legacy kernel 4.4 build images for Ubuntu Bionic with XFCE Desktop<br />
* DD image (for 8GB micoSD card or eMMC Module and above)<br />
** [https://dl.armbian.com/pinebook-pro/Bionic_legacy_desktop Armbian's Pinebook Pro Ubuntu Bionic XFCE Desktop download site]<br />
<br />
== Twister OS ==<br />
[[File:Twister_OS.png|right|100px]]<br />
<br />
=== Twister OS Armbian-Reforged XFCE Dsktop [microSD boot]===<br />
* For more infomation on Twister OS, please visit this {https://twisteros.com/ official site]<br />
* You can follow the ongoing discussion about Twister OS on the PINE64 forum (https://forum.pine64.org/showthread.php?tid=12192)<br />
* After flashing image with Etcher, edit /boot/armbianEnv.txt, replace the dtb name with rk3399-pinebook-pro.dtb.<br />
* DD image (for 16GB microSD card /16GB eMMC module and above):<br />
** [https://twisteros.com/twisterarmbian.html Direct download latest images from Twister OS's website]<br />
** size: 2.8GB<br />
* Login with<br />
** password: asdasd<br />
<br />
== Fedora ==<br />
[[File:fedora1.png|right|100px]]<br />
<br />
=== Fedora 34/33/32 Gnome/KDE/Minimal Images [microSD / eMMC Boot] ===<br />
* Unofficial images based on Fedora, and a [https://copr.fedorainfracloud.org/coprs/aptupdate/pinebook-pro/ copr] repository for kernel and tweaks.<br />
* To learn more about how they are build [https://github.com/bengtfredh/pinebook-pro-fedora-installer Install script].<br />
* DD image (for 12GB microSD card / eMMC module and above) [https://github.com/bengtfredh/pinebook-pro-fedora-installer/wiki/How-to-Resize---Expand-a-Btrfs-Volume---Filesystem How to expand btrfs]<br />
** [https://s3.fredhs.net/minio/pinebook-pro-image/ Fedora Pinebook Pro Images]<br />
<br />
=== Fedora 32 Cinnamon Desktop OS Image [microSD / eMMC Boot] ===<br />
* This image contains an install of Fedora with [https://cinnamon-spices.linuxmint.com/ Cinnamon] desktop environment. <br />
* To learn more about Fedora please visit the [https://getfedora.org/ official website].<br />
* DD image (for 12GB microSD card / eMMC module and above)<br />
** [https://builds.armdevelopers.com/pinebook-pro/releases/dev/Fedora32-Cinnamon-Desktop-202009.0.pinebook-pro.img.xz Fedora 32 Pinebook Pro Image]<br />
* login with:<br />
** username: root<br />
** password: fedora<br />
<br />
=== Fedora 32 KDE Desktop OS Image [microSD / eMMC Boot] ===<br />
* This image contains an install of Fedora with [https://kde.org/ KDE aka Plasma] desktop environment. <br />
* To learn more about Fedora please visit the [https://getfedora.org/ official website].<br />
* DD image (for 12GB microSD card / eMMC module and above)<br />
** [https://builds.armdevelopers.com/pinebook-pro/releases/dev/Fedora32-KDE-Desktop-202009.0.pinebook-pro.img.xz Fedora 32 Pinebook Pro Image]<br />
* login with:<br />
** username: root<br />
** password: fedora<br />
<br />
=== Fedora 32 Xfce Desktop OS Image [microSD / eMMC Boot] ===<br />
* This image contains an install of Fedora with [https://xfce.org/ xfce] desktop environment. <br />
* To learn more about Fedora please visit the [https://getfedora.org/ official website].<br />
* DD image (for 12GB microSD card / eMMC module and above)<br />
** [https://builds.armdevelopers.com/pinebook-pro/releases/dev/Fedora32-Xfce-Desktop-202009.0.pinebook-pro.img.xz Fedora 32 Pinebook Pro Image]<br />
* login with:<br />
** username: root<br />
** password: fedora<br />
<br />
=== Fedora 32 Gnome OS Image [microSD / eMMC Boot] ===<br />
* This image contains an install of Fedora with [https://www.gnome.org/gnome-3/ GNOME 3] desktop environment. <br />
* To learn more about Fedora please visit the [https://getfedora.org/ official website].<br />
* DD image (for 12GB microSD card / eMMC module and above)<br />
** [https://builds.armdevelopers.com/pinebook-pro/releases/dev/Fedora32-Workstation-202009.0.pinebook-pro.img.xz Fedora 32 Pinebook Pro Image]<br />
* login with:<br />
** username: root<br />
** password: fedora<br />
<br />
== Arch Linux ==<br />
[[File:Archlinux-logo.png|right|100px]]<br />
<br />
=== Arch Linux ARM install image [microSD/USB Boot] ===<br />
* archiso image customized for Arch Linux ARM on the Pinebook Pro<br />
* DD image (for 1GB or larger microSD card/USB stick):<br />
** [https://github.com/nadiaholmquist/archiso-pbp/releases Direct download for latest releases from GitHub]<br />
** size: 579MB<br />
* Automatic login as root<br />
* Make sure to thoroughly read the [https://github.com/nadiaholmquist/archiso-pbp/blob/master/README.md readme] and [https://github.com/nadiaholmquist/archiso-pbp/blob/master/FAQ.md FAQ], otherwise follow the normal Arch installation guide.<br />
<br />
== postmarketOS ==<br />
[[File:PostmarketOS logo.png|right|100px]]<br />
<br />
===Official postmarketOS build [microSD/ eMMC Boot] ===<br />
* Official postmarketOS build with the GNOME desktop for the Pinebook Pro. <br />
* DD image (for 8GB microSD card /16GB eMMC module and above):<br />
** [http://images.postmarketos.org/pinebookpro/ Direct download latest images from postmarketOS]<br />
** size: 400MB<br />
* Login with<br />
** username: demo<br />
** password: demo OR 147147<br />
<br />
==Kali Linux==<br />
[[File:Kali.jpeg|right|100px]]<br />
<br />
=== Kali Linux prebuilt OS images for Pinebook Pro [SD/eMMC boot]===<br />
* Official pre-built OS images of Kali Linux for the Pinebook Pro featuring all tools you'd expect from the distribution. <br />
* DD image (for 8GB microSD card /16GB eMMC module and above):<br />
** [https://www.offensive-security.com/kali-linux-arm-images/ Direct download latest images from Offensive Security's website]<br />
** size: 2.0GB<br />
* Login with<br />
** username: kali<br />
** password: kali<br />
<br />
== Q4OS ==<br />
[[File:q4os.png|right|100px]]<br />
<br />
=== Q4OS Test Build Image [microSD / eMMC Boot] ===<br />
* Q4OS is advertised as a 'fast and powerful operating system based on the latest technologies while offering highly productive desktop environment'<br />
* To learn more please visit the [https://forum.pine64.org/showthread.php?tid=8385 PINE64 forum] or official [https://q4os.org/index.html Q4OS website]<br />
* DD image (for 8GB microSD card / eMMC module and above)<br />
** [https://sourceforge.net/projects/q4os/files/testing/ Direct download latest release build from SourceForge]<br />
* User account and password are created on first run<br />
<br />
= BSD OS Image Release =<br />
<br />
==NetBSD==<br />
[[File:netbsd.png|right|100px]]<br />
<br />
=== NetBSD [microSD /eMMC Boot] ===<br />
* To learn more about NetBSD please visit [https://www.netbsd.org/ NetBSD main page] <br />
* DD image to microSD card or eMMC module. Highly recommend using [https://etcher.io/ Etcher]<br />
** [http://www.armbsd.org/arm/ Direct download from NetBSD]<br />
* Console and SSH default login:<br />
** username: root<br />
** password: [none]<br />
* Instructions concerning enabling SSH can be found [https://www.netbsd.org/docs/guide/en/chap-boot.html#chap-boot-ssh here]<br />
<br />
==OpenBSD==<br />
[[File:Puffy_mascot_openbsd.png|right|100px]]<br />
<br />
=== OpenBSD ===<br />
* To learn more about OpenBSD, please visit [https://www.openbsd.org/ OpenBSD main page]<br />
* ARM64 images, (including support for Pinebook Pro), can be found here [https://www.openbsd.org/arm64.html OpenBSD arm64]<br />
<br />
= Linux Installer Releases =<br />
<br />
<br />
=== Manjaro ARM installer ===<br />
<br />
The [https://gitlab.manjaro.org/manjaro-arm/applications/manjaro-arm-installer manjaro-arm-installer] script is intended to install Manjaro ARM directly to SD/eMMC cards without the need for images (including LXQT, Mate & CuboCore editions, as well as full disk encryption). Running on a Linux x86 computer, it can install Manjaro ARM directly to an empty eMMC using an eMMC to USB adapter. The script can also be run from SD to install an image to the eMMC.<br />
<br />
== Debian Installer ==<br />
[[File:debian.png|right|100px]]<br />
<br />
=== Daniel Thompson's Debian Installer for the Pinebook Pro ===<br />
* This is an image creator and Debian installer that runs from an existing Linux OS and installs Debian Bullseye<br />
** Installer can configure an encrypted rootfs and provides a choice of desktops, including the default Debian desktop based on Gnome 3<br />
** Strict adoption of upstream Debian packages (with exception of kernel and bootloaders) in order to provide a clean upgrade path as Bullseye matures<br />
* Download at: https://github.com/daniel-thompson/pinebook-pro-debian-installer/<br />
* Pull requests welcome but for discussion and support please use [https://forum.pine64.org/showthread.php?tid=8487 the forum topic].<br />
<br />
For more information, see the [[Pinebook_Pro_Debian_Installer]] wiki page<br />
<br />
=== Official Debian Installer Images ===<br />
* Uses only the upstream kernel and firmware without special patches<br />
* No graphical display yet, works only through serial console<br />
* Requires adding the non-free component to your /etc/apt/sources.list file and installing the "firmware-linux" package for Wi-Fi and Bluetooth support<br />
* Installer is loaded into RAM, can install onto the same media from which it’s booted<br />
* Supports automatic partitioning and full disk encryption through LVM<br />
* Installer currently doesn't install the bootloader, leaving the installed system in an unbootable state until it's manually added<br />
<br />
[https://d-i.debian.org/daily-images/arm64/daily/netboot/SD-card-images/ The relevant files are built daily here] and may sometimes be unavailable if the build system is having issues. The "README.concatenateable_images" file provides instructions on how to combine the partition.img.gz file with the firmware.pinebook-pro.rk3399.img.gz file in order to create a DD-able image.<br />
<br />
The official images are '''not''' recommended yet until the display begins working and the installer properly installs the bootloader. Most users will want to see [[Pinebook Pro Debian Installer|Daniel Thompson's Debian Installer]] instead.<br />
<br />
<br />
== Gentoo Script ==<br />
[[File:GentooLogo.png|right|100px]]<br />
<br />
=== Gentoo Script for Pinebook Pro ===<br />
* This is a script that prepares a Gentoo arm64 stage 3 tarball for the Pinebook Pro<br />
** The script takes care of device specifics like an optimized make.conf, an overlay that provides kernel and firmware amongst others, and other miscellaneous fixes<br />
* The usual tarball setup as per [https://wiki.gentoo.org/wiki/Handbook:AMD64 Gentoo Handbook] is left to the user.<br />
* Forum thread with instructions at https://forum.pine64.org/showthread.php?tid=8765<br />
<br />
<br />
==Kali Script==<br />
[[File:Kali.jpeg|right|100px]]<br />
<br />
=== Kali Linux for Pinebook Pro ===<br />
* This is a script to create official Kali Linux OS images for the Pinebook Pro<br />
** The script carries out the build process in entirety and is Pinebook Pro specific<br />
* Please pull the latest [https://gitlab.com/kalilinux/build-scripts/kali-arm/blob/master/pinebook-pro.sh Kali Linux install script] from the project's GitLab.<br />
* For more information regarding building the OS image please read the README instruction at https://gitlab.com/kalilinux/build-scripts/kali-arm/blob/master/README.md<br />
<br />
<br />
==K1ss OS Script==<br />
[[File:K1ss.png|right|100px]]<br />
<br />
=== K1ss Linux for Pinebook Pro ===<br />
* This is a repository containing an unofficial port of KISS Linux to aarch64. The tarball is built for generic aarch64, currently being tested on the Pinebook Pro.<br />
* Please pull the latest [https://github.com/jedavies-dev/kiss-aarch64 K1ss Linux install script] from the project's GitHub.<br />
* * You can follow the ongoing discussion about K1ss Linux on the PINE64 forum (https://forum.pine64.org/showthread.php?tid=9304)<br />
<br />
<br />
==NixOS Script==<br />
[[File:nixos.png|right|100px]]<br />
<br />
=== NixOS for Pinebook Pro ===<br />
* This is instructions to install NixOS on the Pinebook Pro: https://nixos.wiki/wiki/NixOS_on_ARM/PINE64_Pinebook_Pro<br />
* Please pull the latest [https://github.com/samueldr/wip-pinebook-pro samueldr's repository ] from the project's GitHub.<br />
* * There is a good chance we will see Tier 1 support for aarch64, including the Pinebook Pro, in 2021 (https://github.com/NixOS/rfcs/pull/87)<br />
* * You can follow the ongoing discussion about NixOS on the PINE64 forum (https://forum.pine64.org/showthread.php?tid=10524)<br />
<br />
==SkiffOS for Pinebook Pro ==<br />
[[File:SkiffOS-Icon-1.png|right|100px]]<br />
<br />
=== SkiffOS Boot Image for Pinebook Pro ===<br />
* Instructions to build/install on the Pinebook Pro: https://github.com/skiffos/SkiffOS/tree/master/configs/pine64/book<br />
* Please pull the latest version from the project's GitHub.<br />
* Compiling the boot image takes approximately 30 minutes.<br />
* Easily configure the kernel, compiler, etc with Buildroot.<br />
* Pre-built ISOs will be available with the upcoming 2021.02 <br />
release.<br />
<br />
=== Skiff Core ===<br />
* Supports multiple distros running simultaneously.<br />
* Optionally build from scratch on device on first boot.<br />
* Pre-built multi-arch core container images are available.<br />
<br />
=== GentooLTO with KDE Apps ===<br />
<br />
* GentooLTO with O3 optimized KDE Desktop configuration.<br />
* Use <tt>SKIFF_CONFIG=pine64/book,core/pinebook_gentoo</tt><br />
* Default sign-in is username "core" w/ empty password.<br />
<br />
<br />
[[Category:PineBook Pro]]</div>Ura2https://wiki.pine64.org/index.php?title=Pinebook_Pro_Software_Releases&diff=10351Pinebook Pro Software Releases2021-05-14T18:56:34Z<p>Ura2: Moved "Manjaro ARM Installer" down to "Linux Installer Releases" Section, where it belongs</p>
<hr />
<div>= Linux OS Image Releases =<br />
For information on how to install these images onto your device, please see the [[NOOB]] Page, which includes information on writing images to the device eMMC or an SD card<br />
<br />
== Manjaro ARM ==<br />
[[File:Manjaro.png|right|100px]]<br />
<br />
* The Manjaro project offers a mainline kernel with patches and modules to support PBPro hardware in two flavors. Both provide DD images and installer images (DD to SD card which will then install to eMMC when booted).<br />
* To learn more about Manjaro please visit [https://forum.manjaro.org/tags/manjaroarm Manjaro Forum]<br />
* You can follow the ongoing discussion about Twister OS on the PINE64 forum (https://forum.pine64.org/showthread.php?tid=8207)<br />
<br />
=== Manjaro ARM with KDE (Plasma) desktop [microSD / eMMC Boot] ===<br />
<br />
* [https://manjaro.org/downloads/arm/pinebook-pro/arm8-pinebook-pro-kde-plasma/ Direct download from Manjaro] (microSD image only)<br />
* [https://osdn.net/projects/manjaro-arm/storage/pbpro/kde-plasma/ Direct download from osdn.net] (both microSD and emmc-installer images)<br />
<br />
=== Manjaro ARM with GTK (XFCE) desktop [microSD / eMMC Boot] ===<br />
<br />
* [https://manjaro.org/downloads/arm/pinebook-pro/arm8-pinebook-pro-xfce/ Direct download from Manjaro]<br />
* [https://osdn.net/projects/manjaro-arm/storage/pbpro/xfce/ Direct download from osdn.net]<br />
<br />
=== Manjaro ARM with i3 tiling window manager [microSD / eMMC Boot] ===<br />
<br />
* [https://manjaro.org/downloads/arm/pinebook-pro/arm8-pinebook-pro-i3/ Direct download from Manjaro]<br />
* [https://osdn.net/projects/manjaro-arm/storage/pbpro/i3/ Direct download from osdn.net]<br />
<br />
=== Manjaro ARM with Sway tiling window manager [microSD / eMMC Boot] ===<br />
<br />
* [https://osdn.net/projects/manjaro-arm/storage/pbpro/sway/ Direct download from osdn.net]<br />
<br />
== Armbian ==<br />
[[File:armbian.png|right|100px]]<br />
<br />
* To find out more about Armbian and available options please visit their [https://www.armbian.com/pinebook-pro/ site]<br />
* DD image to microSD card or eMMC module and boot. Highly recommend using [https://etcher.io/ Etcher]<br />
<br />
=== Armbian Ubuntu Focal XFCE Desktop mainline kernel [microSD / eMMC Boot] ===<br />
* Armbian provides a mainline kernel build images for Ubuntu Focal with XFCE Desktop<br />
* DD image (for 8GB micoSD card or eMMC Module and above)<br />
** [https://dl.armbian.com/pinebook-pro/Focal_current_desktop Armbian's Pinebook Pro Ubuntu Focal XFCE Desktop download site]<br />
<br />
=== Armbian Ubuntu Focal XFCE Desktop legacy kernel [microSD / eMMC Boot] ===<br />
* Armbian provides a legacy kernel 4.4 build images for Ubuntu Focal with XFCE Desktop<br />
* DD image (for 8GB microSD card or eMMC Module and above)<br />
** [https://dl.armbian.com/pinebook-pro/Focal_legacy_desktop Armbian's Pinebook Pro Ubuntu Focal XFCE Desktop download site]<br />
<br />
=== Armbian Debian Buster XFCE Desktop legacy kernel [microSD / eMMC Boot] ===<br />
* Armbian provides a legacy kernel 4.4 build images for Debian Buster with XFCE Desktop<br />
* DD image (for 8GB micoSD card or eMMC Module and above)<br />
** [https://dl.armbian.com/pinebook-pro/Buster_legacy_desktop Armbian's Pinebook Pro Debian Buster XFCE Desktop download site]<br />
<br />
=== Armbian Ubuntu Bionic XFCE Desktop legacy kernel [microSD / eMMC Boot] ===<br />
* Armbian provides a legacy kernel 4.4 build images for Ubuntu Bionic with XFCE Desktop<br />
* DD image (for 8GB micoSD card or eMMC Module and above)<br />
** [https://dl.armbian.com/pinebook-pro/Bionic_legacy_desktop Armbian's Pinebook Pro Ubuntu Bionic XFCE Desktop download site]<br />
<br />
== Twister OS ==<br />
[[File:Twister_OS.png|right|100px]]<br />
<br />
=== Twister OS Armbian-Reforged XFCE Dsktop beta images [SD boot]===<br />
* For more infomation on Twister OS, please visit this {https://twisteros.com/ official site]<br />
* You can follow the ongoing discussion about Twister OS on the PINE64 forum (https://forum.pine64.org/showthread.php?tid=12192)<br />
* After flashing image with Etcher, edit /boot/armbianEnv.txt, replace the dtb name with rk3399-pinebook-pro.dtb.<br />
* DD image (for 16GB microSD card /16GB eMMC module and above):<br />
** [https://twisteros.com/twisterarmbian.html Direct download latest images from Twister OS's website]<br />
** size: 2.8GB<br />
* Login with<br />
** password: asdasd<br />
<br />
=== Twister OS Monka-Manjaro XFCE Dsktop beta images [SD boot]===<br />
* For more infomation on Twister OS, please visit this {https://twisteros.com/ official site]<br />
* You can follow the ongoing discussion about Twister OS on the PINE64 forum (https://forum.pine64.org/showthread.php?tid=12192)<br />
* After flashing image with Etcher, edit /boot/armbianEnv.txt, replace the dtb name with rk3399-pinebook-pro.dtb.<br />
* DD image (for 16GB microSD card /16GB eMMC module and above):<br />
** [https://drive.google.com/file/d/1I0yHIDfezqnz1jdphJ4gooWbGtNw0ArW/view?usp=sharing Direct download latest images from Google Drive]<br />
** size: 8.9GB<br />
* Login with<br />
** username: pi<br />
** password: root<br />
<br />
== Fedora ==<br />
[[File:fedora1.png|right|100px]]<br />
<br />
=== Fedora 34/33/32 Gnome/KDE/Minimal Images [microSD / eMMC Boot] ===<br />
* Unofficial images based on Fedora, and a [https://copr.fedorainfracloud.org/coprs/aptupdate/pinebook-pro/ copr] repository for kernel and tweaks.<br />
* To learn more about how they are build [https://github.com/bengtfredh/pinebook-pro-fedora-installer Install script].<br />
* DD image (for 12GB microSD card / eMMC module and above) [https://github.com/bengtfredh/pinebook-pro-fedora-installer/wiki/How-to-Resize---Expand-a-Btrfs-Volume---Filesystem How to expand btrfs]<br />
** [https://s3.fredhs.net/minio/pinebook-pro-image/ Fedora Pinebook Pro Images]<br />
<br />
=== Fedora 32 Cinnamon Desktop OS Image [microSD / eMMC Boot] ===<br />
* This image contains an install of Fedora with [https://cinnamon-spices.linuxmint.com/ Cinnamon] desktop environment. <br />
* To learn more about Fedora please visit the [https://getfedora.org/ official website].<br />
* DD image (for 12GB microSD card / eMMC module and above)<br />
** [https://builds.armdevelopers.com/pinebook-pro/releases/dev/Fedora32-Cinnamon-Desktop-202009.0.pinebook-pro.img.xz Fedora 32 Pinebook Pro Image]<br />
* login with:<br />
** username: root<br />
** password: fedora<br />
<br />
=== Fedora 32 KDE Desktop OS Image [microSD / eMMC Boot] ===<br />
* This image contains an install of Fedora with [https://kde.org/ KDE aka Plasma] desktop environment. <br />
* To learn more about Fedora please visit the [https://getfedora.org/ official website].<br />
* DD image (for 12GB microSD card / eMMC module and above)<br />
** [https://builds.armdevelopers.com/pinebook-pro/releases/dev/Fedora32-KDE-Desktop-202009.0.pinebook-pro.img.xz Fedora 32 Pinebook Pro Image]<br />
* login with:<br />
** username: root<br />
** password: fedora<br />
<br />
=== Fedora 32 Xfce Desktop OS Image [microSD / eMMC Boot] ===<br />
* This image contains an install of Fedora with [https://xfce.org/ xfce] desktop environment. <br />
* To learn more about Fedora please visit the [https://getfedora.org/ official website].<br />
* DD image (for 12GB microSD card / eMMC module and above)<br />
** [https://builds.armdevelopers.com/pinebook-pro/releases/dev/Fedora32-Xfce-Desktop-202009.0.pinebook-pro.img.xz Fedora 32 Pinebook Pro Image]<br />
* login with:<br />
** username: root<br />
** password: fedora<br />
<br />
=== Fedora 32 Workstation OS Image [microSD / eMMC Boot] ===<br />
* This image contains an install of Fedora with [https://www.gnome.org/gnome-3/ GNOME 3] desktop environment. <br />
* To learn more about Fedora please visit the [https://getfedora.org/ official website].<br />
* DD image (for 12GB microSD card / eMMC module and above)<br />
** [https://builds.armdevelopers.com/pinebook-pro/releases/dev/Fedora32-Workstation-202009.0.pinebook-pro.img.xz Fedora 32 Pinebook Pro Image]<br />
* login with:<br />
** username: root<br />
** password: fedora<br />
<br />
== Arch Linux ==<br />
[[File:Archlinux-logo.png|right|100px]]<br />
<br />
=== Arch Linux ARM install image [microSD/USB Boot] ===<br />
* archiso image customized for Arch Linux ARM on the Pinebook Pro<br />
* DD image (for 1GB or larger microSD card/USB stick):<br />
** [https://github.com/nadiaholmquist/archiso-pbp/releases Direct download for latest releases from GitHub]<br />
** size: 579MB<br />
* Automatic login as root<br />
* Make sure to thoroughly read the [https://github.com/nadiaholmquist/archiso-pbp/blob/master/README.md readme] and [https://github.com/nadiaholmquist/archiso-pbp/blob/master/FAQ.md FAQ], otherwise follow the normal Arch installation guide.<br />
<br />
== postmarketOS ==<br />
[[File:PostmarketOS logo.png|right|100px]]<br />
<br />
===Official postmarketOS build [microSD/ eMMC Boot] ===<br />
* Official postmarketOS build with the GNOME desktop for the Pinebook Pro. <br />
* DD image (for 8GB microSD card /16GB eMMC module and above):<br />
** [http://images.postmarketos.org/pinebookpro/ Direct download latest images from postmarketOS]<br />
** size: 400MB<br />
* Login with<br />
** username: demo<br />
** password: demo OR 147147<br />
<br />
==Kali Linux==<br />
[[File:Kali.jpeg|right|100px]]<br />
<br />
=== Kali Linux prebuilt OS images for Pinebook Pro [SD/eMMC boot]===<br />
* Official pre-built OS images of Kali Linux for the Pinebook Pro featuring all tools you'd expect from the distribution. <br />
* DD image (for 8GB microSD card /16GB eMMC module and above):<br />
** [https://www.offensive-security.com/kali-linux-arm-images/ Direct download latest images from Offensive Security's website]<br />
** size: 2.0GB<br />
* Login with<br />
** username: kali<br />
** password: kali<br />
<br />
== Q4OS ==<br />
[[File:q4os.png|right|100px]]<br />
<br />
=== Q4OS Test Build Image [microSD / eMMC Boot] ===<br />
* Q4OS is advertised as a 'fast and powerful operating system based on the latest technologies while offering highly productive desktop environment'<br />
* To learn more please visit the [https://forum.pine64.org/showthread.php?tid=8385 PINE64 forum] or official [https://q4os.org/index.html Q4OS website]<br />
* DD image (for 8GB microSD card / eMMC module and above)<br />
** [https://sourceforge.net/projects/q4os/files/testing/ Direct download latest release build from SourceForge]<br />
* User account and password are created on first run<br />
<br />
= BSD OS Image Release =<br />
<br />
==NetBSD==<br />
[[File:netbsd.png|right|100px]]<br />
<br />
=== NetBSD [microSD /eMMC Boot] ===<br />
* To learn more about NetBSD please visit [https://www.netbsd.org/ NetBSD main page] <br />
* DD image to microSD card or eMMC module. Highly recommend using [https://etcher.io/ Etcher]<br />
** [http://www.armbsd.org/arm/ Direct download from NetBSD]<br />
* Console and SSH default login:<br />
** username: root<br />
** password: [none]<br />
* Instructions concerning enabling SSH can be found [https://www.netbsd.org/docs/guide/en/chap-boot.html#chap-boot-ssh here]<br />
<br />
==OpenBSD==<br />
[[File:Puffy_mascot_openbsd.png|right|100px]]<br />
<br />
=== OpenBSD ===<br />
* To learn more about OpenBSD, please visit [https://www.openbsd.org/ OpenBSD main page]<br />
* ARM64 images, (including support for Pinebook Pro), can be found here [https://www.openbsd.org/arm64.html OpenBSD arm64]<br />
<br />
= Linux Installer Releases =<br />
<br />
<br />
=== Manjaro ARM installer ===<br />
<br />
The [https://gitlab.manjaro.org/manjaro-arm/applications/manjaro-arm-installer manjaro-arm-installer] script is intended to install Manjaro ARM directly to SD/eMMC cards without the need for images (including LXQT, Mate & CuboCore editions, as well as full disk encryption). Running on a Linux x86 computer, it can install Manjaro ARM directly to an empty eMMC using an eMMC to USB adapter. The script can also be run from SD to install an image to the eMMC.<br />
<br />
== Debian Installer ==<br />
[[File:debian.png|right|100px]]<br />
<br />
=== Daniel Thompson's Debian Installer for the Pinebook Pro ===<br />
* This is an image creator and Debian installer that runs from an existing Linux OS and installs Debian Bullseye<br />
** Installer can configure an encrypted rootfs and provides a choice of desktops, including the default Debian desktop based on Gnome 3<br />
** Strict adoption of upstream Debian packages (with exception of kernel and bootloaders) in order to provide a clean upgrade path as Bullseye matures<br />
* Download at: https://github.com/daniel-thompson/pinebook-pro-debian-installer/<br />
* Pull requests welcome but for discussion and support please use [https://forum.pine64.org/showthread.php?tid=8487 the forum topic].<br />
<br />
For more information, see the [[Pinebook_Pro_Debian_Installer]] wiki page<br />
<br />
=== Official Debian Installer Images ===<br />
* Uses only the upstream kernel and firmware without special patches<br />
* No graphical display yet, works only through serial console<br />
* Requires adding the non-free component to your /etc/apt/sources.list file and installing the "firmware-linux" package for Wi-Fi and Bluetooth support<br />
* Installer is loaded into RAM, can install onto the same media from which it’s booted<br />
* Supports automatic partitioning and full disk encryption through LVM<br />
* Installer currently doesn't install the bootloader, leaving the installed system in an unbootable state until it's manually added<br />
<br />
[https://d-i.debian.org/daily-images/arm64/daily/netboot/SD-card-images/ The relevant files are built daily here] and may sometimes be unavailable if the build system is having issues. The "README.concatenateable_images" file provides instructions on how to combine the partition.img.gz file with the firmware.pinebook-pro.rk3399.img.gz file in order to create a DD-able image.<br />
<br />
The official images are '''not''' recommended yet until the display begins working and the installer properly installs the bootloader. Most users will want to see [[Pinebook Pro Debian Installer|Daniel Thompson's Debian Installer]] instead.<br />
<br />
<br />
== Gentoo Script ==<br />
[[File:GentooLogo.png|right|100px]]<br />
<br />
=== Gentoo Script for Pinebook Pro ===<br />
* This is a script that prepares a Gentoo arm64 stage 3 tarball for the Pinebook Pro<br />
** The script takes care of device specifics like an optimized make.conf, an overlay that provides kernel and firmware amongst others, and other miscellaneous fixes<br />
* The usual tarball setup as per [https://wiki.gentoo.org/wiki/Handbook:AMD64 Gentoo Handbook] is left to the user.<br />
* Forum thread with instructions at https://forum.pine64.org/showthread.php?tid=8765<br />
<br />
<br />
==Kali Script==<br />
[[File:Kali.jpeg|right|100px]]<br />
<br />
=== Kali Linux for Pinebook Pro ===<br />
* This is a script to create official Kali Linux OS images for the Pinebook Pro<br />
** The script carries out the build process in entirety and is Pinebook Pro specific<br />
* Please pull the latest [https://gitlab.com/kalilinux/build-scripts/kali-arm/blob/master/pinebook-pro.sh Kali Linux install script] from the project's GitLab.<br />
* For more information regarding building the OS image please read the README instruction at https://gitlab.com/kalilinux/build-scripts/kali-arm/blob/master/README.md<br />
<br />
<br />
==K1ss OS Script==<br />
[[File:K1ss.png|right|100px]]<br />
<br />
=== K1ss Linux for Pinebook Pro ===<br />
* This is a repository containing an unofficial port of KISS Linux to aarch64. The tarball is built for generic aarch64, currently being tested on the Pinebook Pro.<br />
* Please pull the latest [https://github.com/jedavies-dev/kiss-aarch64 K1ss Linux install script] from the project's GitHub.<br />
* * You can follow the ongoing discussion about K1ss Linux on the PINE64 forum (https://forum.pine64.org/showthread.php?tid=9304)<br />
<br />
<br />
==NixOS Script==<br />
[[File:nixos.png|right|100px]]<br />
<br />
=== NixOS for Pinebook Pro ===<br />
* This is instructions to install NixOS on the Pinebook Pro: https://nixos.wiki/wiki/NixOS_on_ARM/PINE64_Pinebook_Pro<br />
* Please pull the latest [https://github.com/samueldr/wip-pinebook-pro samueldr's repository ] from the project's GitHub.<br />
* * There is a good chance we will see Tier 1 support for aarch64, including the Pinebook Pro, in 2021 (https://github.com/NixOS/rfcs/pull/87)<br />
* * You can follow the ongoing discussion about NixOS on the PINE64 forum (https://forum.pine64.org/showthread.php?tid=10524)<br />
<br />
==SkiffOS for Pinebook Pro ==<br />
[[File:SkiffOS-Icon-1.png|right|100px]]<br />
<br />
=== SkiffOS Boot Image for Pinebook Pro ===<br />
* Instructions to build/install on the Pinebook Pro: https://github.com/skiffos/SkiffOS/tree/master/configs/pine64/book<br />
* Please pull the latest version from the project's GitHub.<br />
* Compiling the boot image takes approximately 30 minutes.<br />
* Easily configure the kernel, compiler, etc with Buildroot.<br />
* Pre-built ISOs will be available with the upcoming 2021.02 <br />
release.<br />
<br />
=== Skiff Core ===<br />
* Supports multiple distros running simultaneously.<br />
* Optionally build from scratch on device on first boot.<br />
* Pre-built multi-arch core container images are available.<br />
<br />
=== GentooLTO with KDE Apps ===<br />
<br />
* GentooLTO with O3 optimized KDE Desktop configuration.<br />
* Use <tt>SKIFF_CONFIG=pine64/book,core/pinebook_gentoo</tt><br />
* Default sign-in is username "core" w/ empty password.<br />
<br />
<br />
[[Category:PineBook Pro]]</div>Ura2https://wiki.pine64.org/index.php?title=Pinebook_Pro&diff=10348Pinebook Pro2021-05-14T18:23:34Z<p>Ura2: Removed "Quick Links to OS Images Build Sources", as it really only linked to outdated and unusable repos</p>
<hr />
<div>= User Guide =<br />
== Introducing PineBook Pro == <br />
[[File:PBP.jpg|400px|thumb|right|Pinebook Pro running Debian with MATE]]<br />
<br />
The Pinebook Pro is a Linux and *BSD ARM laptop from [https://www.pine64.org/ PINE64]<br />
<br />
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. <br />
<br />
It's compact and slim dimensions are 329mm x 220mm x 12mm (WxDxH).<br />
<br />
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 x4) with an optional adapter. <br />
<br />
The Pinebook Pro is equipped with 4GB LPDDR4 system memory, high capacity eMMC flash storage, and 128Mb SPI boot Flash. The I/O includes: 1 x micro SD card reader (bootable), 1 x USB 2.0, 1 x USB 3.0, 1 x USB type C Host with DP 1.2 and power-in, PCIe x4 for an NVMe SSD drive (requires an optional adapter), and UART (via the headphone jack by setting an internal switch). <br />
<br />
The keyboard and trackpad both use the USB 2.0 protocol. The LCD panel uses eDP MiPi display protocol.<br />
<br />
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.<br />
<br />
== Software and OS Image Downloads ==<br />
<br />
=== Default Manjaro KDE Desktop Quick Start ===<br />
<br />
When you first get your Pinebook Pro and boot it up for the first time, it'll come with Manjaro using the KDE desktop. The Pinebook Pro is officially supported by the Manjaro ARM project, and support can be found on the [https://forum.manjaro.org/c/manjaro-arm/78 Manjaro ARM forums.]<br />
<br />
On first boot, it will ask for certain information such as your timezone location, keyboard layout, username, password, and hostname. Most of these should be self-explanatory. Note that the hostname it asks for should be thought of as the "codename" of your machine, and if you don't know what it's about, you can make something up (use a single word, all lower case, no punctuation; e.g. "pbpro").<br />
<br />
After you're on the desktop, be sure to update it as soon as possible and reboot after updates are finished installing. If nothing appears when you click on the Networking icon in your system tray to connect to your Wi-Fi, ensure the Wi-Fi [https://wiki.pine64.org/index.php/Pinebook_Pro#ANSI_Fn_.2B_F_keys_wrong_for_F9.2C_F10.2C_F11_and_F12 privacy switch] is not disabled.<br />
<br />
=== [[Pinebook Pro_Software_Release|Pinebook Pro images]] ===<br />
Under [[Pinebook Pro Software Release|'Pinebook Pro Software Release/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. <br />
<br />
The list includes OS images and descriptions of:<br />
<br />
[[PinebookPro_Software_Release#Manjaro ARM|'''Manjaro ARM (microSD and eMMC Boot)''']]<br />
<br />
[[PinebookPro_Software_Release#Armbian|'''Armbian (microSD and eMMC Boot)''']]<br />
<br />
[[PinebookPro_Software_Release#Twister OS|'''Twister OS (microSD Boot)''']]<br />
<br />
[[PinebookPro_Software_Release#Fedora|'''Fedora (microSD and eMMC Boot)''']]<br />
<br />
[[PinebookPro_Software_Release#Arch Linux|'''Arch Linux (microSD and USB boot)''']]<br />
<br />
[[PinebookPro_Software_Release#Postmarket OS|'''Postmarket OS (microSD and USB boot)''']]<br />
<br />
[[PinebookPro_Software_Release#Kali Linux|'''Kali Linux (microSD and USB boot)''']]<br />
<br />
[[PinebookPro_Software_Release#Q4OS|'''Q4OS (microSD and eMMC Boot)''']]<br />
<br />
[[PinebookPro_Software_Release#NetBSD|'''NetBSD (microSD and eMMC Boot)''']]<br />
<br />
[[Pinebook_Pro_Software_Release#OpenBSD|'''OpenBSD release for ARM64''']]<br />
<br />
[[Pinebook_Pro_Software_Release#Gentoo_Script_for_Pinebook_Pro|'''Gentoo Script for Pinebook Pro''']]<br />
<br />
== Keyboard ==<br />
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. <br />
<br />
The keyboard firmware binary can be flashed from userspace using the provided open source utility. <b style="color: red">WARNING: DO NOT update the keyboard firmware before checking which keyboard IC your Pinebook Pro has.</b> Some Pinebook Pro were delivered with a '''SH61F83''' instead of a '''SH68F83'''. The SH61F83 can only be written 8 times, this will render the keyboard and trackpad unusable if this limit is reached when <code>step-1</code> is flashed. See [//old.reddit.com/r/PINE64official/comments/loq4db/very_disappointed/ Reddit SH61F83 thread].<br />
<br />
Documentation for the keyboard can be found in [[#Datasheets for Components and Peripherals|Datasheets for Components and Peripherals]]. <br />
<br />
=== Typing special characters ===<br />
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. <br />
{| class="wikitable"<br />
!Character<br />
!Key combination/sequence<br />
|-<br />
|Ä, Ö, Ü, ä, ö, ü<br />
|[[Wikipedia:AltGr_key|[AltGr]]]+'[' followed by [A], [O], [U], [a], [o] or [u]<br />
|-<br />
|µ<br />
|[AltGr]+[m]<br />
|-<br />
|Ø, ø<br />
|[AltGr]+[O], [AltGr]+[o]<br />
|-<br />
|@<br />
|[AltGr]+[q] (as on the German layout)<br />
|-<br />
|ß<br />
|[AltGr]+[s]<br />
|-<br />
|§<br />
|[AltGr]+[S]<br />
|-<br />
|°<br />
|[AltGr]+[)]<br />
|}<br />
<br />
=== Privacy Switches ===<br />
There are three privacy switches mapped to the F10, F11 and F12 keys on the Pinebook Pro keyboard. They de/activate the following:<br />
<br />
{| class="wikitable"<br />
|+ Privacy switch function and description<br />
! Combination<br />
! Effect<br />
! Description<br />
! Notes<br />
|-<br />
! scope=row | PINE64 logo key+F10<br />
| Microphone Privacy switch<br />
| CAPs lock LED blinks. 2 blinks = enabled, 3 blinks = disabled<br />
|-<br />
! scope=row | PINE64 logo key+F11<br />
| WiFi Privacy switch<br />
| NUM lock LED blinks. 2 blinks = WiFi enabled / killswitch disabled, 3 blinks = WiFi disabled / killswitch enabled.<br />
| '''Re-enabling requires reboot''' (or a [//forum.pine64.org/showthread.php?tid=8313&pid=52645#pid52645 command line hack to bind/unbind]).<br />
|-<br />
! scope=row | PINE64 logo key+F12<br />
| Camera privacy switch<br />
| CAPs lock and NUM lock LEDs blink together. 2 blinks = enabled, 3 blinks = disabled<br />
| Can use tools like '''<code>lsusb</code>''' to detect camera's presence. If not detected, check privacy switch.<br />
|}<br />
<br />
'''(Press the PINE64 logo key plus F10/F11/F12) for 3 seconds)'''<br />
<br />
The keyboard operates on firmware independant of the operating system. It detects if one of the F10, F11 or F12 keys is pressed in combination with the Pine key for 3 seconds. Doing so disables power to the appropriate peripheral, thereby disabling it. This has the same effect 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 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 inside the keyboard's firmware flash memory.<br />
<br />
== Trackpad ==<br />
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. <br />
Documentation for the trackpad can be found in [[#Datasheets for Components and Peripherals|Datasheets for Components and Peripherals]].<br />
The trackpad firmware binary can be flashed from userspace using the provided open source utility (https://github.com/ayufan-rock64/pinebook-pro-keyboard-updater). A fork with more recent changes is also available (https://github.com/jackhumbert/pinebook-pro-keyboard-updater) and may want to be considered instead while feature parity is different.<br />
<br />
The trackpad controller is connected to the keyboard controller. All trackpad events go through the keyboard controller and it's software, then to the keyboard controller's USB port. Note that the trackpad does have separate firmware, (which has to be written through the keyboard controller).<br />
<br />
<br />
'''Everyone with a Pinebook Pro produced in 2019 should update their keyboard and trackpad firmware.''' <br />
<br />
Before you start:<br />
<br />
<b style="color: red">WARNING: DO NOT update the trackpad firmware before checking which keyboard IC your Pinebook Pro has.</b> Some Pinebook Pro were delivered with a '''SH61F83''' instead of a '''SH68F83'''. The SH61F83 can only be written 8 times, this will render the keyboard and trackpad unusable if this limit is reached when <code>step-1</code> is flashed. See [//old.reddit.com/r/PINE64official/comments/loq4db/very_disappointed/ Reddit SH61F83 thread].<br />
<br />
Please refer to original documentation for details.<br />
<br />
Your Pinebook Pro should be either fully charged or, preferably, running off 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.<br />
<br />
The scripts ought to work on all OSs available for the Pinebook Pro. Some OSs may, however, require installation of relevant dependencies. The instructions below assume a Debian desktop. Newer Pinebook Pro models that come with Manjaro will require a different command to install the proper dependencies.<br />
<br />
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. <br />
Firmware update steps for both models are listed below. <br />
<br />
What you will need:<br />
<br />
*Your Pinebook Pro fully charged or running off of mains power<br />
*Connection to WiFi<br />
*An external USB keyboard & mouse (or access to the Pinebook Pro via SSH)<br />
<br />
'''ISO Model''' <br />
<br />
From the terminal command line: <br />
<br />
<pre><br />
git clone https://github.com/ayufan-rock64/pinebook-pro-keyboard-updater<br />
cd pinebook-pro-keyboard-updater<br />
sudo apt-get install build-essential libusb-1.0-0-dev xxd<br />
make<br />
</pre><br />
<br />
Step 1<br />
<pre><br />
cd pinebook-pro-keyboard-updater<br />
sudo ./updater step-1 iso<br />
sudo reboot<br />
</pre><br />
<br />
Step 2 (after reboot)<br />
<pre><br />
cd pinebook-pro-keyboard-updater<br />
sudo ./updater step-2 iso<br />
sudo reboot<br />
</pre><br />
<br />
----<br />
<br />
'''ANSI Model''' <br />
<br />
*<b>NOTE:</b> Running step 1 on the ANSI keyboard model will make the keyboard and trackpad inaccessible until step 2 is ran, so an external keyboard must be connected to complete the update on this model!<br />
<br />
From the terminal command line: <br />
<br />
<pre><br />
git clone https://github.com/ayufan-rock64/pinebook-pro-keyboard-updater<br />
cd pinebook-pro-keyboard-updater<br />
sudo apt-get install build-essential libusb-1.0-0-dev xxd<br />
make<br />
</pre><br />
<br />
Step 1<br />
<pre><br />
cd pinebook-pro-keyboard-updater<br />
sudo ./updater step-1 ansi<br />
sudo reboot<br />
</pre><br />
<br />
Step 2 (after reboot)<br />
<pre><br />
cd pinebook-pro-keyboard-updater<br />
sudo ./updater step-2 ansi<br />
sudo reboot<br />
</pre><br />
When done, if some of the keys produce incorrect characters, please check your OS’s 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.<br />
<br />
=== X-Windows & trackpad settings ===<br />
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:<br />
<pre>synclient MinSpeed=0.25</pre><br />
You may experiment with different settings, but 0.25 was tested as helping noticeably.<br><br />
<br><br />
To make the change persist across reboots, change the file <code>/etc/X11/xorg.conf</code> similar to below:<br />
<pre> Section "InputClass"<br />
Identifier "touchpad catchall"<br />
Driver "synaptics"<br />
MatchIsTouchpad "on"<br />
MatchDevicePath "/dev/input/event*"<br />
Option "MinSpeed" "0.25"<br />
EndSection</pre><br />
The line <code>Option "MinSpeed" "0.25"</code> is the change.<br><br />
<br><br />
Another forum user built on the above settings a little, and have found these to be very good:<br />
<pre>synclient MinSpeed=0.25<br />
synclient TapButton1=1<br />
synclient TapButton2=3<br />
synclient TapButton3=2<br />
synclient FingerLow=30<br />
synclient PalmDetect=1<br />
synclient VertScrollDelta=64<br />
synclient HorizScrollDelta=64</pre><br />
<br />
<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 unknown whether synaptic works like this.<br />
You may find this config to be comfortable for daily use.<br />
<br><br />
<br />
<code>TabButton</code> allows to just tab the touchpad instead of physically pressing it down (to get this click noise).<br />
<br />
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:<br />
<pre> synclient MaxTapTime=250 </pre><br />
<br />
== Power Supply ==<br />
* Input Power: 5V DC @ 3A<br />
* Mechanical: 3.5mm OD / 1.35mm ID, Barrel jack<br />
* USB-C 5V, 15W PD quickcharge<br />
* Only use one power input at a time, barrel jack OR USB-C<br />
<br />
== LEDs ==<br />
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: <br />
<br />
# The red LED next to the barrel port indicates charging, in three ways. First, it will illuminate steadily when either the factory power supply or a USB Type-C charger is connected to the Pinebook Pro, and the battery is getting charged. Second, if the battery is at 100%, the LED will remain turned off regardless of the connected power input; however, this is [https://forum.pine64.org/showthread.php?tid=10899 rather rarely achieved]. Third, this LED will flash at 0.5&nbsp;Hz if there are any problems that prevent charging, such as the battery becoming too hot.<br />
# The power indicator LED, above the keyboard, supports three different colours: green, amber and red. It is also capable of flashing to indicate eMMC activity. In the default Debian with MATE build, green LED means power and red means suspend (amber is unused). <br />
# The green NumLock LED, above the keyboard.<br />
# The green CapsLock LED, above the keyboard.<br />
<br />
The NumLock and CapsLock LEDs serve their usual purposes on a keyboard, but they also have a secondary function. When the privacy switches get activated they blink to confirm that the switch has been activated.<br />
<br />
== Webcam ==<br />
* Streaming video resolutions supported, (un-compressed):<br />
** 320 x 240 <br />
** 640 x 480<br />
** 800 x 600<br />
** 1280 x 720<br />
** 1600 x 1200<br />
* Still frame resolutions supported:<br />
** 160 x 120<br />
** 176 x 144<br />
** 320 x 240<br />
** 352 x 288 <br />
** 640 x 480<br />
** 800 x 600<br />
** 1280 x 720<br />
** 1600 x 1200<br />
* Some people test with the application Cheese<br />
WIP<br />
<br />
== Microphones ==<br />
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.<br />
<br />
The wires leading to both microphones connect to the mainboard with a small white plastic connector, located directly adjacent to the ribbon cable attachment point for the keyboard interface.<br />
<br />
<br />
'''Microphones not working?'''<br />
<br />
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]]).<br />
<br />
<pre><br />
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 ><br />
> increase the gain to 0dB > change the audio profile in pavucontrol to another with input<br />
<br />
Additionally:<br />
you may want to modify ADC PGA to get the levels to where you want them<br />
</pre><br />
<br />
== Bluetooth and WiFi ==<br />
[[File:PinebookPro_WirelessIC_Location.jpg|400px|thumb|right|The Pinebook Pro's AP6256 wireless module]]<br />
===Hardware Overview===<br />
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. <br />
<br />
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.<br />
<br />
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.<br />
<br />
===Issues===<br />
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.<br />
<br />
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.<br />
<br />
===Wi-Fi Capabilities===<br />
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.<br />
<br />
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.<br />
<br />
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.<br />
<br />
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.<br />
<br />
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.<br />
<br />
===Bluetooth Capabilities===<br />
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.<br />
<br />
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.<br />
<br />
===Disabling Bluetooth===<br />
<pre><br />
#disable bluetooth once<br />
sudo rfkill block bluetooth && <br />
<br />
#confirm<br />
rfkill<br />
</pre><br />
<br />
<pre><br />
#disable bluetooth on boot**<br />
sudo systemctl enable rfkill-block@bluetooth<br />
</pre><br />
<br />
<nowiki>**This does not do what one might want on certain distros, Manjaro XFCE for example. Try the below.</nowiki><br />
<br />
<pre><br />
right click on the bluetooth panel icon > select 'plugins' > PowerManager > configuration > deselect the auto power on option<br />
</pre><br />
<br />
== LCD Panel ==<br />
* Model: BOE NV140FHM-N49<br />
* 14.0" (35.56&nbsp;cm) diagonal size<br />
* 1920x1080 resolution<br />
* 60&nbsp;Hz refresh rate<br />
* IPS technology<br />
* 1000:1 contrast<br />
* 250&nbsp;nit brightness<br />
* 63% sRGB coverage<br />
* 6-bit color<br />
* 30-pin eDP connection<br />
<br />
Some people have tested hardware video decode using the following;<br />
<br />
<pre>ffmpeg -benchmark -c:v h264_rkmpp -i file.mp4 -f null -</pre><br />
<br />
== External ports list ==<br />
Here are a list of the external ports. See [[Pinebook_Pro#Expansion_Ports|Technical Reference - Expansion Ports]] for port specifications.<br />
* Left side<br />
** Barrel jack for power, (with LED)<br />
** USB 3, Type A<br />
** USB 3, Type C<br />
* Right side<br />
** USB 2, Type A<br />
** Standard headset jack<br />
** MicroSD card slot<br />
<br />
== Using the UART ==<br />
[[File:PBPUART.jpeg|400px|thumb|right|Headphone jack UART wiring reference.<br />
<br> Swapping the tx and rx around from this also works and is more traditional.<br />
<br> See [https://files.pine64.org/doc/pinebook/guide/Pinebook_Earphone_Serial_Console_Developer_Guide.pdf this] official Pine64 .pdf.]]<br />
<br />
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.<br />
<br />
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.3&nbsp;V interface (such as the CH340, FTDI-232R, or PL2303, which are sold in both 3.3&nbsp;V and 5&nbsp;V variants) to avoid damage to the CPU. Older version of the serial console cable sold by Pine64 uses wrong voltage level and should not be used; see [https://forum.pine64.org/showthread.php?tid=9367 this forum thread] for further information. Recent version of the same cable uses the right voltage level.<br />
<br />
Insert the USB plug of the cable into an open USB port on the machine which will monitor, ensuring that the audio jack of the serial cable is be fully inserted into the Pinebook Pro audio port. Run the following in a terminal:<br />
<br />
<code><br />
$ lsusb<br />
</code><br />
<br />
you should find a line similar to this:<br />
<br />
<code><br />
Bus 001 Device 058: ID 1a86:7523 QinHeng Electronics HL-340 USB-Serial adapter<br />
</code><br />
<br />
Serial output should now be accessible using screen, picocom or minicom (and others).<br />
Examples:<br />
<br />
<code><br />
screen /dev/ttyUSB0 1500000<br />
<br />
picocom /dev/ttyUSB0 -b 1500000<br />
<br />
minicom -D /dev/ttyUSB0 -b 1500000</code><br />
<br />
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><br />
<br />
== Using the optional NVMe adapter ==<br />
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.<br />
<br />
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.<br />
<br />
Please see [[Pinebook Pro Troubleshooting Guide#NVMe SSD issues|a separate section]] that describes reported issues with the NVMe drives in PineBook Pro.<br />
<br />
=== Installing the adapter ===<br />
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.<br />
(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.)<br />
<br />
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.<br />
<br />
This is the link to the PBPro accessories in the store: [[https://pine64.com/?v=0446c16e2e66]]<br />
<br />
Actual installation instructions are a work in progress. Unofficial instructions for installing V2-2019-1107 can be found [https://eli.gladman.cc/blog/2020/06/23/pine-book-pro-nvme.html here].<br />
<br />
=== Post NVMe install power limiting ===<br />
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.<br />
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);<br />
<pre>$ sudo nvme id-ctrl /dev/nvme0<br />
NVME Identify Controller:<br />
...<br />
ps 0 : mp:9.00W operational enlat:0 exlat:0 rrt:0 rrl:0<br />
rwt:0 rwl:0 idle_power:- active_power:-<br />
ps 1 : mp:4.60W operational enlat:0 exlat:0 rrt:1 rrl:1<br />
rwt:1 rwl:1 idle_power:- active_power:-<br />
ps 2 : mp:3.80W operational enlat:0 exlat:0 rrt:2 rrl:2<br />
rwt:2 rwl:2 idle_power:- active_power:-<br />
ps 3 : mp:0.0450W non-operational enlat:2000 exlat:2000 rrt:3 rrl:3<br />
rwt:3 rwl:3 idle_power:- active_power:-<br />
ps 4 : mp:0.0040W non-operational enlat:6000 exlat:8000 rrt:4 rrl:4<br />
rwt:4 rwl:4 idle_power:- active_power:-<br />
<br />
$ sudo nvme get-feature /dev/nvme0 -f 2<br />
get-feature:0x2 (Power Management), Current value:00000000<br />
$ sudo nvme set-feature /dev/nvme0 -f 2 -v 2 -s<br />
set-feature:02 (Power Management), value:0x000002</pre><br />
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.<br><br />
If you want to test performance without saving the new power setting semi-permanantly, then leave off the "-s" option.<br/><br />
<br/><br />
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;<br />
<pre>$ sudo nvme get-feature -f 0x0c -H /dev/nvme0</pre><br />
Information for this feature, (on a Pinebook Pro), is a work in progress.<br />
<br />
=== Using as data drive ===<br />
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.<br />
<br />
=== Using as OS root drive ===<br />
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.<br />
<br />
The current boot order, per last testing, for this modified U-Boot is:<br />
*MicroSD<br />
*eMMC<br />
*NVMe<br />
<br />
For more information, please refer to [https://forum.pine64.org/showthread.php?tid=8439&pid=53764#pid53764 the forum post.]<br />
<br />
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.)<br />
<br />
Please see [[Pinebook_Pro#Bootable Storage|Bootable Storage]].<br />
<br />
== Caring for the PineBook Pro ==<br />
=== Bypass Cables ===<br />
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 [https://files.pine64.org/doc/PinebookPro/PinebookPro_Engineering_Notice.pdf engineering notice]. <br />
<br />
'''Note that despite the bypass cable being a two conductor cable, it is only used as one. Both wires being soldered together on either side is normal!'''<br />
<br />
WARNING: Do not connect the bypass cables with the battery connected. Using the bypass cables with the battery connected can permanently damage the computer.<br />
<br />
=== [[Pinebook_Service_Step_by_Step_Guides|Pinebook Service Step-by-Step Guides]] ===<br />
<span style="color:#FF0000">Placeholder for Pinebook Pro specific guides</span><br />
<br />
Under [[Pinebook_Service_Step_by_Step_Guides|'Service Guides for Pinebook']] you can find instructions guides concerning disassembly of:<br />
<br />
'''Note: The installation process on Pinebook Pro similar to 14" Pinebook'''<br />
<br />
'''Note: The installation process is the reverse order of removal guide'''<br />
<br />
* 14″ Pinebook Lithium Battery Pack Removal Guide<br />
* 14″ Pinebook LCD Panel Screen Removal Guide<br />
* 14″ Pinebook eMMC Module Removal Guide<br />
<br />
== Using the SPI flash device ==<br />
<br />
See [[Pinebook_Pro_SPI]]<br />
<br />
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.<br />
<br />
Here is some information on using the SPI flash device:<br />
<br />
* You need the kernel built with SPI flash device support, which will supply a device similar to:<br><br><code>/dev/mtd0</code><br><br><br />
* The Linux package below, will need to be available:<br><br><code>mtd-utils</code><br><br><br />
* You can then use this program from the package to write the SPI device:<br><br><code>flashcp &lt;filename&gt; /dev/mtd0</code><br><br><br />
<br />
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.<br />
<br />
The procedures described above are a lot less risky than attaching an external SPI flasher and do not require any additional hardware.<br><br />
<br><br />
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.<br />
<br />
== FAQ ==<br />
What cool software works out of the box? [[Pinebook Pro OTB Experience]]<br />
<br />
= Software tuning guide =<br />
Details on how to get the most out of a Pinebook Pro & its RK3399 SoC.<br />
<br />
== Customizing the Pinebook Pro's default Manjaro KDE system ==<br />
=== Watching DRM content (Netflix, etc.) ===<br />
Most paid online streaming services use Widevine DRM to make their content more difficult to pirate. Widevine is not directly supported on Manjaro KDE, however it is still possible to watch DRM content via the "chromium-docker" package which downloads a 32-bit ARM container and installs Chromium with Widevine inside of that. While not space-efficient, or efficient in general, it's the recommended solution for watching this content on your Pinebook Pro. You can install this package with:<br />
<pre>sudo pacman -Sy chromium-docker</pre><br />
=== Checking GPU capabilities ===<br />
To see what versions of OpenGL and OpenGL ES are supported by the Pinebook Pro, what driver is in use, and what version of the driver is loaded, install the "mesa-demos" package with:<br />
<pre>sudo pacman -Sy mesa-demos</pre><br />
And then run:<br />
<pre>glxinfo | grep OpenGL</pre><br />
This will give detailed information about your graphics card and driver, useful for debugging.<br />
<br />
=== Better GPU compatibility and performance ===<br />
For better graphics performance, you may install the "mesa-git" package, built and supplied in the Manjaro ARM repos. This lets you bring in the latest features, optimizations, and bugfixes for the graphics driver used by the Pinebook Pro. Installation is as simple as:<br />
<pre>pacman -Sy mesa-git</pre><br />
Then you may reboot to load the newer driver.<br />
<br />
With Mesa 20.2 there is no longer much reason to use this over the standard mesa package, and applications may occasionally break with mesa-git.<br />
<br />
[https://docs.mesa3d.org/bugs.html Reporting bugs] to the Mesa project will help make sure any problems are quickly fixed.<br />
<br />
=== OpenGL 3.3 support ===<br />
By default, with the current state of the Panfrost GPU driver, the Pinebook Pro supports OpenGL 2.1 and OpenGL ES 3.0. If you want to use OpenGL 3.3, you need to set the system-wide environment variable, open the '''/etc/environment''' file with:<br />
<pre>kate /etc/environment</pre><br />
And then at the bottom of the file, on a new line, add:<br />
<pre>PAN_MESA_DEBUG="gl3"</pre><br />
Then save the file, entering your password when prompted, and reboot the system. When you check your GPU capabilities, it should report OpenGL 3.3 and applications that rely on it should function properly. Note that GL 3.3 support is incomplete and some rendering features do not work yet, notably geometry shaders.<br />
<br />
=== Install Anbox on Pinebook Pro Manjaro 20.10 ===<br />
[https://www.youtube.com/watch?v=EU8_Q11dATs Youtube video on installing Anbox on Pienbook Pro Manjaro Build 20.10 by LivingLinux]<br />
<br />
== Customizing the Pinebook Pro's previously-default Debian system ==<br />
Here are some hints on what you can do to customize the Pinebook Pro's previous factory image (aka [https://github.com/mrfixit2001/debian_desktop mrfixit2001 debian build])<br />
<br />
=== Initial user changes, password, name, etc ===<br />
When you first get your Pinebook Pro, you should consider setting strong passwords and making the default account your own.<br />
<br />
* 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)<br />
* Once the machine reboots press Alt-Ctrl-F1 to bring up a text terminal<br />
* Login as root (login: root, password: root)<br />
* Set a strong password for the root user using the following command and it's prompts:<br />
<pre># passwd (and follow prompts)</pre><br />
* Rename the rock user to your prefered username (replace myself with whatever you like):<br />
<pre># usermod -l myself -d /home/myself -m rock</pre><br />
* Rename the rock group to match your preferred username:<br />
<pre># groupmod -n myself rock</pre><br />
* Put your name in the account, (replace "John A Doe" with your name):<br />
<pre># chfn -f "John A Doe" myself</pre><br />
* Set a strong password for the normal user:<br />
<pre># passwd myself</pre><br />
* Log out of the text terminal:<br />
<pre># logout</pre><br />
* Press Alt-Ctrl-F7 to go back to the login screen and then login as the normal user<br />
* Open text terminal to fix login error: "Configured directory for incoming files does not exist";<br />
<pre>$ blueman-services</pre><br />
Select "Transfer" tab and set "Incoming Folder" to myself<br />
OR<br />
If adduser is in distro, this is MUCH easier<br />
sudo adduser $USER ,, fill out requested data<br />
Then,, sudo adduser $USER $GROUP,,, 1 group at a time<br />
To see which groups to add,,, id $USER, id rock<br />
<br />
=== Changing the default hostname ===<br />
Debian 9 has a command to allow you to change the hostname. You can see the current settings using;<br />
<pre>> sudo hostnamectl<br />
Static hostname: Debian-Desktop<br />
Icon name: computer<br />
Machine ID: dccbddccbdccbdccbdccbdccbdccbccb<br />
Boot ID: ea99ea99ea99ea99ea99ea99ea99ea99<br />
Operating System: Debian GNU/Linux 9 (stretch)<br />
Kernel: Linux 4.4.210<br />
Architecture: arm64</pre><br />
To change, use this, (with "My_Hostname" used as the example);<br />
<pre>> sudo hostnamectl set-hostname My_Hostname</pre><br />
Whence done, you can re-verify using the first example.<br />
<br />
Then you should backup and edit your <code>/etc/hosts</code> entry's name;<br />
<pre>> sudo cp -p /etc/hosts /etc/hosts.`date +%Y%m%d`<br />
> sudo vi /etc/hosts<br />
127.0.0.1 localhost<br />
127.0.0.1 My_Hostname<br />
::1 localhost ip6-localhost ip6-loopback<br />
fe00::0 ip6-localnet<br />
ff00::0 ip6-mcastprefix<br />
ff02::1 ip6-allnodes<br />
ff02::2 ip6-allrouters<br />
127.0.1.1 linaro-alip</pre><br />
<br />
=== Disable Chromium browser's prompt for passphrase & password storage ===<br />
<br />
Perform the following steps:<br />
<br />
* On the tool bar, hover over the Chromium icon<br />
* Using the right mouse button, select '''Properties'''<br />
* In the '''Command:''' line section, add <code>--password-store=basic</code> before the <code>%U</code><br />
* Use the '''x Close''' button to save the change<br />
This will of course, use basic password storage, meaning any saved passwords are not encrypted. Perfectly fine if you never use password storage.<br />
<br />
=== Changing the boot splash picture ===<br />
<br />
The default boot splash picture can be replaced using the following instructions:<br />
<br />
* Install '''ImageMagick''' which will do the conversion<br />
<pre>$ sudo apt-get install imagemagick</pre><br />
* Create a 1920 x 1080 picture. For the best results, use a PNG image (It supports lossless compression).<br />
* From the directory in which your new image is stored run the following commands<br />
* Convert your image to the bootsplash raw format using imagemagick convert.<br />
<pre>$ convert yoursplashimage.png -separate +channel -swap 0,2 -combine -colorspace sRGB RGBO:splash.fb</pre><br />
* Create a backup copy of your current splash screen<br />
<pre>$ sudo cp /usr/share/backgrounds/splash.fb /usr/share/backgrounds/splash_original.fb</pre><br />
* Copy your new splash screen into place<br />
<pre>$ sudo cp splash.fb /usr/share/backgrounds/splash.fb</pre><br />
* Set the correct permissions on the splash.fb file<br />
<pre>$ sudo chmod 644 /usr/share/backgrounds/splash.fb</pre><br />
* If you do not want to see kernel console text messages, make sure you don't have '''Plymouth''' installed<br />
<br />
=== Watching Amazon Prime videos with Chromium ===<br />
When you create a new user, it will be necessary to launch the Chromium browswer with a specific user agent like below;<br />
<pre>chromium-browser --user-agent="Mozilla/5.0 (X11; CrOS armv7l 6946.63.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/72.0.3626.121 Safari/537.36"</pre><br />
There may be more tweaks needed.<br />
<br />
=== Enabling text boot time messages ===<br />
<br />
By default, most Linux distros have a boot screen with a picture. To see all the boot time messages, use one of the following;<br />
<br />
<b><u>Default Debian</u></b><br />
* Backup and edit the U-Boot configuration file:<br />
<pre>cp -p /etc/default/u-boot /etc/default/u-boot.`date +%Y%m%d`<br />
chmod a-w /etc/default/u-boot.`date +%Y%m%d`<br />
vi /etc/default/u-boot</pre><br />
Remove the '''quiet''' and '''splash''' parameters. Leave everything else alone.<br />
* Update the U-Boot configuration:<br />
<pre>u-boot-update</pre><br />
* Test and verify you get what you think you should be seeing.<br />
<br><br />
<b><u>Manjaro</u></b><br />
* Backup and edit the U-Boot configuration file:<br />
<pre>cp -p /boot/extlinux/extlinux.conf /boot/extlinux/extlinux.conf.`date +%Y%m%d`<br />
chmod a-w /boot/extlinux/extlinux.conf.`date +%Y%m%d`<br />
vi /boot/extlinux/extlinux.conf</pre><br />
Change '''console=ttyS2,1500000''' to '''console=tty1'''<br> <br />
Remove the '''bootsplash.bootfile''' option and it's parameter.<br><br />
You can add verbose logging by appending '''ignore_loglevel''' to the line where boot splash was.<br><br />
Leave everything else alone.<br><br />
* Test and verify you get what you think you should be seeing.<br />
<br />
== Improving readability ==<br />
<br />
Some people find that a 14" LCD screen with 1080p, (1920 x 1080), has text and icons a bit too small. There are things you can do to make the screen easier to use and read.<br><br />
* Increase the font size<br />
* Use a font with more pronounced features<br />
* Increase the various window manager sizes (e.g. increase the height of the tool bar)<br />
* Change the color scheme to be easier on the eyes. Higher contrast can help usability.<br />
* Change the window manager's decorations (e.g. use larger icons)<br />
* Use a workspace manager, with one application per workspace<br />
* When at home or office, use an external monitor<br />
* Change the X-Windows DPI<br />
<br><br />
However, do not change the resolution of the LCD screen, otherwise you may end up with a blank / black screen. If that happens, see this troubleshooting section for the fix:<br><br />
[[Pinebook_Pro#After_changing_builtin_LCD_resolution.2C_blank_screen|Blank screen after changing builtin LCD resolution]]<br />
<br />
== Chromium tweaks ==<br />
<br />
=== Flags ===<br />
<br />
From the [https://github.com/mrfixit2001/updates_repo/blob/v1.8/pinebook/filesystem/default official Debian image]:<br />
<br />
<pre><br />
--disable-low-res-tiling \<br />
--num-raster-threads=6 \<br />
--profiler-timing=0 \<br />
--disable-composited-antialiasing \<br />
--test-type \<br />
--show-component-extension-options \<br />
--ignore-gpu-blacklist \<br />
--use-gl=egl \<br />
--ppapi-flash-path=/usr/lib/chromium-browser/pepper/libpepflashplayer.so \<br />
--ppapi-flash-version=32.0.0.255 \<br />
--enable-pinch \<br />
--flag-switches-begin \<br />
--enable-gpu-rasterization \<br />
--enable-oop-rasterization \<br />
--flag-switches-end<br />
</pre><br />
<br />
Note that in some cases, this may also decrease performance substantially, as observed when using these flags on the Manjaro KDE desktop. Feel free to experiment to find what is smoothest for you personally.<br />
<br />
== gVim has performance issue ==<br />
It appears that using GTK3 can cause very slow scrolling, while Vim in a terminal window works fine.<br/><br />
Simply revert back to using GTK2, (how to do so is somewhat Linux distro-specific).<br />
<br />
Another solution may be to run gVim with <br />
<br />
GDK_RENDERING=image<br />
<br />
environment variable set. It seems that this improves the performance by reverting back to software-only rendering.<br />
<br />
== Kernel options ==<br />
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.<br />
<br />
To see if a specific feature is enabled in the current kernel, you can use something like this;<br />
<br />
<pre><br />
$ zgrep -i rockchip_pcie /proc/config.gz<br />
# CONFIG_ROCKCHIP_PCIE_DMA_OBJ is not set<br />
CONFIG_PHY_ROCKCHIP_PCIE=m<br />
</pre><br />
If it's listed as <code>=m</code>, then it's a module. You can see if the module is loaded with;<br />
<pre><br />
$ lsmod | grep -i rockchip_pcie<br />
phy_rockchip_pcie 16384 0<br />
</pre><br />
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.<br />
<br />
=== Hardware video decoding ===<br />
Here is a method to check for hardware video decoding by the VPU. There are special Linux kernel modules that perform this function.<br><br />
Older systems, such as the previously-default Debian desktop, use the Rockchip-supplied kernel module <code>rk-vcodec</code>. To check, something like this can be used:<br />
<pre><br />
$ lsmod | grep rk-vcodec<br />
or<br />
$ zgrep RK_VCODEC /proc/config.gz<br />
CONFIG_RK_VCODEC=y<br />
</pre><br />
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.<br><br />
<br><br />
<br />
Newer systems may use a different option as in the configuration below:<br />
<pre><br />
$ zgrep HANTRO /proc/config.gz<br />
CONFIG_VIDEO_HANTRO=m<br />
CONFIG_VIDEO_HANTRO_ROCKCHIP=y<br />
</pre><br />
<br />
= Troubleshooting guide =<br />
<br />
Do not to panic if something goes wrong or in an unexpected way. Instead, stop and consider carefully how to undo something, or how to redo it. This particularly applies when flashing a new operating system, or flashing new firmware to the keyboard or touchpad. If everything fails, consider reporting the issue on the forums, with as many relevant details as available.<br />
<br />
Please, have a look at the [[Pinebook Pro Troubleshooting Guide]], which details a number of issues you may encounter.<br />
<br />
= Hardware/Accessory Compatibility =<br />
Please contribute to the [[Pinebook Pro Hardware Accessory Compatibility|hardware/accessory compatibility page]], which lists the status of hardware tested with the Pinebook Pro. Available hardware categories include the following:<br />
<br />
* [[Pinebook Pro Hardware Accessory Compatibility#NVMe SSD drives|NVMe SSD drives]]<br />
* [[Pinebook Pro Hardware Accessory Compatibility#USB hardware|USB hardware]]<br />
* [[Pinebook Pro Hardware Accessory Compatibility#USB C alternate mode DP|USB-C alternate mode DP]]<br />
* [[Pinebook Pro Hardware Accessory Compatibility#Other hardware|Other hardware]]<br />
<br />
= Technical Reference =<br />
== Disassembly and Reassembly == <br />
[[File:Standoffs.png|400px|thumb|right|Pinebook Screw stand-offs correct placement and location]]<br />
<br />
There are a few '''mandatory''' precautions to be taken:<br />
<br />
* 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.<br />
* When removing the back cover plate, *do not, under any circumstances, slide your fingertips between the metal shell and the plastic frame!* The back cover plate edges are sharp, and when combined with the pressure and movement generated from, specifically, attempting to slide the tips of your fingers along the bottom edge of the plate along the lid-hinge, they *will* slice open the tips of your fingers like a knife.<br />
* When removing the back cover plate, use care to avoid damaging the speakers. They are stuck to the back cover with double-sided tape, and the thin wires are very delicate.<br />
<br />
[[File:PinebookProScrewGuide.png|400px|thumb|right|PinebookPro external screws (this particular unit has suffered damage on screw (4)L)]]<br />
<br />
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. There are four (4) short screws along the front edge, and six (6) long screws along the 3 remaining sides. Remove the cover from the back where the hinges are situated by lifting it up and away from the rest of the chassis. The aluminum case is held on only by screws. There are no plastic snaps, and the shell should pull away without any effort. If you experience any resistance at all stop and ensure all ten (10) screws are accounted for.<br />
<br />
During reassembly, make sure that the back-screw standoffs are in place and seated correctly. Before replacing the aluminum back-plate, ensure that the speakers are properly seated by pressing gently on the hard plastic edge of the speaker module. 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 4 short screws.<br />
<br />
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 (which may be caused by the aforementioned misseating of the speakers), 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, re-open the machine and check for misseated components.<br />
<br />
A basic 3D model to print replacement standoffs for the back cover screws is [https://www.thingiverse.com/thing:4226648 available on Thingiverse], until the official drawings or 3D models are made available.<br />
<br />
== Internal Layout ==<br />
<br />
=== Main chips ===<br />
* RK3399 system-on-chip (1)<br />
* LPDDR4 SDRAM (21)<br />
* SPI NOR flash memory (29)<br />
* eMMC flash memory (26)<br />
* WiFi/BT module (27)<br />
<br />
=== Mainboard Switches and Buttons ===<br />
There are two switches on the main board: disabling the eMMC (24), and enabling UART (9) via headphone jack. <br />
<br />
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). <br />
<br />
[[File:PBPL_S.jpg]]<br />
<br />
=== Key Internal Parts ===<br />
{| class="wikitable"<br />
|+ Numbered parts classification and description<br />
! Number<br />
! Type<br />
! Descriptor<br />
|-<br />
! scope=row | 1<br />
| Component || RK3399 System-On-Chip<br />
|-<br />
! scope=row | 2<br />
| Socket || PCIe x4 slot for optional NVMe adapter<br />
|-<br />
! scope=row | 3<br />
| Socket || Speakers socket<br />
|-<br />
! scope=row | 4<br />
| Socket || Trackpad socket<br />
|-<br />
! scope=row | 5<br />
| Component || Left speaker <br />
|-<br />
! scope=row | 6<br />
| Connector || Power bridge connector <br />
|-<br />
! scope=row | 7<br />
| Socket || Keyboard Socket<br />
|-<br />
! scope=row | 8<br />
| Component || Optional NVMe SSD adapter<br />
|-<br />
! scope=row | 9<br />
| Switch || UART/Audio switch - outputs UART via headphone jack<br />
|-<br />
! scope=row | 10<br />
| Socket || Power bridge socket<br />
|-<br />
! scope=row | 11<br />
| Socket || Battery socket<br />
|-<br />
! scope=row | 12<br />
| Component || Trackpad<br />
|-<br />
! scope=row | 13<br />
| Component || Battery<br />
|-<br />
! scope=row | 14<br />
| Component || Right speaker<br />
|-<br />
! scope=row | 15<br />
| Socket || MicroSD card slot<br />
|-<br />
! scope=row | 16<br />
| Socket || Headphone / UART jack<br />
|-<br />
! scope=row | 17<br />
| Socket || USB 2.0 Type A<br />
|-<br />
! scope=row | 18<br />
| Socket || Daughterboard-to-mainboard ribbon cable socket<br />
|-<br />
! scope=row | 19<br />
| Cable || Daughterboard-to-mainboard ribbon cable<br />
|-<br />
! scope=row | 20<br />
| Component || microphone<br />
|-<br />
! scope=row | 21<br />
| Component || LPDDR4 RAM<br />
|-<br />
! scope=row | 22<br />
| Socket || Mainboard-to-daughterboard ribbon cable socket<br />
|-<br />
! scope=row | 23<br />
| Socket || Microphone socket<br />
|-<br />
! scope=row | 24<br />
| Switch || Switch to hardware disable eMMC<br />
|-<br />
! scope=row | 25<br />
| Antenna || BT/WiFI antenna<br />
|-<br />
! scope=row | 26<br />
| Component || eMMC flash memory module <br />
|-<br />
! scope=row | 27<br />
| Component ||BT/WiFi module chip<br />
|-<br />
! scope=row | 28<br />
| Buttons || Reset and recovery buttons<br />
|-<br />
! scope=row | 29<br />
| Component || SPI flash storage<br />
|-<br />
! scope=row | 30<br />
| Socket || eDP LCD socket<br />
|-<br />
! scope=row | 31<br />
| Socket || Power in barrel socket<br />
|-<br />
! scope=row | 32<br />
| Socket || USB 3.0 Type A<br />
|-<br />
! scope=row | 33<br />
| Socket || USB 3.0 Type C <br />
|}<br />
<br />
=== Smallboard detailed picture ===<br />
<br />
[[File:Pinebook_pro_smallboard.jpg]]<br />
<br />
== Bootable Storage ==<br />
<br />
=== Boot sequence details ===<br />
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.<br><br />
[[RK3399_boot_sequence|RK3399 boot sequence]]<br />
<br />
=== Boot devices ===<br />
<br />
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. <br />
<br />
At this time, the Pinebook Pro ships with a Manjaro + KDE build with [https://www.denx.de/wiki/U-Boot/ uboot] on the eMMC. Its boot order is: SD, USB, then eMMC.<br />
<br />
(An update has been pushed for the older 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.)<br />
<br />
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<br />
in a /boot partition on the eMMC.<br />
<br />
=== eMMC information ===<br />
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.<br />
<br />
The eMMC storage will show up as multiple block devices:<br />
*mmcblk1boot0 - eMMC standard boot0 partition, may be 4MB<br />
*mmcblk1boot1 - eMMC standard boot1 partition, may be 4MB<br />
*mmcblk1rpmb - eMMC standard secure data partition, may be 16MB<br />
*mmcblk1 - This block contains the user areas<br />
<br />
Only the last is usable as regular storage device in the Pinebook Pro.<br />
The device number of "1" shown above may vary, depending on kernel.<br />
<br />
If the eMMC module is enabled after boot from an SD card, you can detect this change with the following commands as user "root";<br />
<pre><br />
echo fe330000.sdhci >/sys/bus/platform/drivers/sdhci-arasan/unbind<br />
echo fe330000.sdhci >/sys/bus/platform/drivers/sdhci-arasan/bind<br />
</pre><br />
<br />
== Case Dimensions and Data ==<br />
* Dimensions: 329mm x 220mm x 12mm (WxDxH)<br />
* Weight: 1.26Kg<br />
* Screws<br />
** Philips head type screws<br />
** M2 flat head machine screws (measurements in mm)<br />
** 4 x Small screws (used along the front edge): Head - 3.44, Thread Diameter - 1.97, Thread Length - 2.1, Overall length - 3.05<br />
** 6 x Large screws: Head - 3.44, Thread Diameter - 1.97, Thread Length - 4.41, Overall Length - 5.85<br />
* Rubber Feet<br />
** 18mm diameter<br />
** 3mm height<br />
** Dome shaped<br />
<br />
== SoC and Memory Specification ==<br />
[[File:Rockchip_RK3399.png|right]]<br />
* Based on Rockchip RK3399<br />
<br />
=== CPU Architecture ===<br />
* big.LITTLE architecture: Dual Cortex-A72 + Quad Cortex-A53, 64-bit CPU<br />
** Full implementation of the ARM architecture v8-A instruction set (both AArch64 and AArch32)<br />
** ARM Neon Advanced SIMD (single instruction, multiple data) support for accelerated media and signal processing computation<br />
** ARMv8 Cryptography Extensions<br />
** VFPv4 floating point unit supporting single and double-precision operations<br />
** Hardware virtualization support<br />
** TrustZone technology support<br />
** Full CoreSight debug solution<br />
** One isolated voltage domain to support DVFS<br />
* Cortex-A72 (big cluster):<br />
** [https://developer.arm.com/products/processors/cortex-a/cortex-a72 Dual-core Cortex-A72 up to 2.0GHz CPU]<br />
** Superscalar, variable-length, out-of-order pipeline<br />
** L1 cache 48KB Icache and 32KB Dcache for each A72 <br />
** L2 cache 1024KB for big cluster <br />
* Cortex-A53 (little cluster):<br />
** [https://developer.arm.com/products/processors/cortex-a/cortex-a53 Quad-core Cortex-A53 up to 1.5GHz CPU]<br />
** In-order pipeline with symmetric dual-issue of most instructions <br />
** L1 cache 32KB Icache and 32KB Dcache for each A53<br />
** L2 cache 512KB for little cluster<br />
* Cortex-M0 (control processors):<br />
** [https://developer.arm.com/ip-products/processors/cortex-m/cortex-m0 Cortex-M0 CPU]<br />
** Two Cortex-M0 cooperate with the central processors<br />
** Architecture: Armv6-M<br />
** Thumb/Thumb2 instruction set<br />
** 32 bit only<br />
<br />
=== GPU Architecture ===<br />
* [https://developer.arm.com/products/graphics-and-multimedia/mali-gpus/mali-t860-and-mali-t880-gpus ARM Mali-T860MP4 Quad-core GPU]<br />
* 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.<br />
* Frequency 650MHz <br />
* Throughput 1300Mtri/s, 10.4Gpix/s<br />
* Graphic interface standards:<br />
** OpenGL® ES 1.1, 1.2, 2.0, 3.0, 3.1, 3.2. (Panfrost has initial support of 3.0 beginning 2020/02/27)<br />
** Vulkan 1.0, using the Mali binary blob. (Panfrost does not support Vulkan as of 2020/06/24)<br />
** OpenCL™ 1.1, 1.2<br />
** DirectX® 11 FL11_1<br />
** RenderScript™<br />
<br />
=== System Memory ===<br />
* RAM Memory:<br />
** LPDDR4<br />
** 800MHz, (limited by RK3399)<br />
** Dual memory channels on the CPU, each 32 bits wide<br />
** Quad memory channels on the RAM chip, each 16 bits wide, 2 bonded together for each CPU channel<br />
** 4GB as a single 366 pin mobile RAM chip<br />
* Storage Memory: <br />
** 64GB eMMC module, can be upgraded to an 128GB eMMC module. (The initial PINE64 community build version shipped with a 128GB eMMC.)<br />
** eMMC version 5.1, HS400, 8 bit on RK3399 side<br />
** Bootable<br />
* SPI flash:<br />
** [[Pinebook Pro SPI]]<br />
** 128Mbit / 16MByte<br />
** 1 bit interface<br />
** Bootable, (first boot device, ahead of eMMC & SD card)<br />
** U-Boot images can be made to work, but as of 2020/06/24 there is no standardized image available.<br />
<br />
=== Video out ===<br />
* USB-C Alt mode DP<br />
* Up to 3840x2160 p60, dependant on adapter, (2 lanes verses 4 lanes)<br />
<br />
=== Expansion Ports ===<br />
* MicroSD card:<br />
** Bootable<br />
** Supports SD, SDHC and SDXC cards, up to 512GB tested. SDXC standard says 2TB is the maximum.<br />
** Version SD3.0, (MMC 4.5), up to 50MB/s<br />
** SD card Application Performance Class 1 (A1), (or better), recommended by some users, for better IOPS<br />
* USB ports:<br />
** 1 x USB 2.0 Type-A Host Port, bootable<br />
** 1 x USB 3.0 Type-A Host Port, 5Gbps, is not bootable<br />
** 1 x USB 3.0 Type-C OTG Port, 5Gbps, (includes laptop charging function), is not bootable<br />
** 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.<br />
* Headphone jack switchable to UART console mux circuit<br />
<br />
== Additional hardware ==<br />
Hardware that is not part of the SoC.<br />
<br />
=== Battery ===<br />
* Lithium Polymer Battery (10,000 mAH)<br />
<br />
=== Display ===<br />
* 14.0" 1920x1080 IPS LCD panel<br />
=== Lid closed magnet ===<br />
There is a magnet to detect when the laptop lid is closed, so action can be taken like sleep. This meets up with the Hall sensor on the daughter / small board to detect lid closed.<br />
* The magnet is located on the LCD panel right side, around 1.5 inches up measure from bottom edge.<br />
<br />
=== Webcam ===<br />
* Internal USB attached Webcam<br />
<br />
=== Audio ===<br />
* 3.5mm stereo earphone/microphone plug<br />
* Built-in microphone<br />
* Built-in stereo speakers:<br />
** Oval in design<br />
** 3 mm high x 20 mm x 30 mm<br />
<br />
=== Network ===<br />
* WiFi:<br />
** 802.11 b/g/n/ac<br />
** Dual band: 2.4Ghz & 5Ghz<br />
** Single antenna<br />
* Bluetooth 5.0<br />
<br />
=== Optional NVMe adapter ===<br />
* PCIe 2.0, 5&nbsp;GT/s per lane<br />
* Four PCIe lanes, which can not be bifurcated, but can be used with one- or two-lane NVMe cards<br />
* '''M''' keyed, though '''M'''+'''B''' keyed devices will work too<br />
* Maximum length for M.2 card is 80mm (M.2 2280). The following sizes will also work: 2230, 2242, 2260<br />
* Power: 2.5&nbsp;W continuous, 8.25&nbsp;W peak momentary<br />
* Does not support SATA M.2 cards<br />
* Does not support USB M.2 cards<br />
<br />
== Pinebook Pro Schematics and Certifications ==<br />
* Pinebook Pro Main Board Schematic And Silkscreen:<br />
** [https://files.pine64.org/doc/PinebookPro/pinebookpro_v2.1_mainboard_schematic.pdf Pinebook Pro Main Board ver 2.1 Schematic]<br />
** [https://wiki.pine64.org/images/3/30/Pinebookpro-v2.1-top-ref.pdf Pinebook Pro ver 2.1 Top Layer Silkscreen]<br />
** [https://wiki.pine64.org/images/b/b7/Pinebookpro-v2.1-bottom-ref.pdf Pinebook Pro ver 2.1 Bottom Layer Silkscreen]<br />
* Pinebook Pro Daughter Board Schematic:<br />
** [https://files.pine64.org/doc/PinebookPro/pinebookpro_v2.1_daughterboard_schematic.pdf Pinebook Pro Daughter Board ver 2.1 Schematic]<br />
* Optional Pinebook Pro NVMe Adapter Schematic:<br />
** [https://files.pine64.org/doc/PinebookPro/pinebookpro_v2.1_NVMe-adapter_schematic.pdf Pinebook Pro NVMe Adapter Board ver 2.1 Schematic]<br />
* Serial Console Earphone Jack Pinout:<br />
** [https://files.pine64.org/doc/pinebook/guide/Pinebook_Earphone_Serial_Console_Developer_Guide.pdf Pinkbook Serial Console Earphone Jack Pinout]<br />
* Pinebook Pro Case:<br />
** [https://files.pine64.org/doc/PinebookPro/drawings/Pinebook%20Pro%20Principle%20Views.pdf AutoCAD PDF File ]<br />
** [https://files.pine64.org/doc/PinebookPro/drawings/Pinebook%20Pro%20Principle%20Views.ai AutoCAD AI File ]<br />
** [https://files.pine64.org/doc/PinebookPro/drawings/Pinebook%20Pro%20Principle%20Views.dwg AutoCAD DWG File ]<br />
* Pinebook Pro Certifications:<br />
** [https://files.pine64.org/doc/cert/Pinebook%20Pro%20FCC%20Certificate-S19071103501001.pdf Pinebook Pro FCC Certificate]<br />
** [https://files.pine64.org/doc/cert/Pinebook%20Pro%20CE%20RED%20Certificate-S19051404304.pdf Pinebook Pro CE Certificate]<br />
** [https://files.pine64.org/doc/cert/Pinebook%20Pro%20ROHS%20Compliance%20Certificate.pdf Pinebook Pro RoHS Certificate]<br />
<br />
== Datasheets for Components and Peripherals ==<br />
* Rockchip RK3399 SoC information:<br />
** [https://www.rock-chips.com/a/en/products/RK33_Series/2016/0419/758.html Rockchip RK3399 SoC Brief]<br />
** [https://opensource.rock-chips.com/images/d/d7/Rockchip_RK3399_Datasheet_V2.1-20200323.pdf Rockchip RK3399 Datasheet v2.1]<br />
** [https://www.rockchip.fr/Rockchip%20RK3399%20TRM%20V1.4%20Part1.pdf Rockchip RK3399 Technical Reference Manual v1.4, part 1]<br />
** [https://www.rockchip.fr/Rockchip%20RK3399%20TRM%20V1.3%20Part1.pdf Rockchip RK3399 Technical Reference Manual v1.3, part 1] and [https://www.rockchip.fr/Rockchip%20RK3399%20TRM%20V1.3%20Part2.pdf part 2]<br />
** [https://files.pine64.org/doc/datasheet/rockpro64/RK808%20datasheet%20V0.8.pdf Rockchip RK808 Datasheet v0.8]<br />
* LPDDR4 SDRAM (366-pin BGA):<br />
** [https://files.pine64.org/doc/datasheet/PinebookPro/micron%20SM512M64Z01MD4BNK-053FT%20LPDDR4%20(366Ball).pdf Micron 366 balls Mobile LPDDR4 Datasheet]<br />
* eMMC information:<br />
** [https://files.pine64.org/doc/rock64/PINE64_eMMC_Module_20170719.pdf PINE64 eMMC module schematic]<br />
** [https://files.pine64.org/doc/rock64/usb%20emmc%20module%20adapter%20v2.pdf PINE64 USB adapter for eMMC module V2 schematic]<br />
** [https://files.pine64.org/doc/rock64/USB%20adapter%20for%20eMMC%20module%20PCB.tar PINE64 USB adapter for eMMC module PCB in JPEG]<br />
** [https://files.pine64.org/doc/datasheet/pine64/SDINADF4-16-128GB-H%20data%20sheet%20v1.13.pdf 64GB/128GB SanDisk eMMC Datasheet]<br />
* SPI NOR Flash information:<br />
** [https://files.pine64.org/doc/datasheet/pine64/w25q128jv%20spi%20revc%2011162016.pdf WinBond 128Mb SPI Flash Datasheet]<br />
** [https://wiki.pine64.org/images/b/b9/Ds-00220-gd25q127c-rev1-df2f4.pdf GigaDevice 128Mb SPI Flash Datasheet (updated)]<br />
* Wireless and Bluetooth information:<br />
** [https://files.pine64.org/doc/datasheet/PinebookPro/AP6256%20datasheet_V1.7_12282018.pdf AMPAK AP6256 11AC Wi-Fi + Bluetooth5 Datasheet]<br />
* Audio codec:<br />
** [http://www.everest-semi.com/pdf/ES8316%20PB.pdf Everest ES8316 Audio Codec Datasheet]<br />
* LCD panel:<br />
** [https://files.pine64.org/doc/datasheet/PinebookPro/NV140FHM-N49_Rev.P0_20160804_201710235838.pdf 14" 1920x1080 IPS LCD Panel datasheet]<br />
* USB-related information:<br />
** Internal USB 2.0 hub: [https://wiki.pine64.org/images/3/39/GL850G_USB_Hub_1.07.pdf GL850G USB Hub Datasheet]<br />
** USB Type-C Controller: [https://www.onsemi.com/pub/Collateral/FUSB302-D.PDF ON Semiconductor FUSB302 Datasheet]<br />
* Touchpad information:<br />
** [https://files.pine64.org/doc/datasheet/PinebookPro/YX%20HK-9562%20HID%20I2C%20Specification.pdf PineBook Pro Touchpad Specification]<br />
* Keyboard information:<br />
** [https://wiki.pine64.org/images/b/b0/SH68F83V2.0.pdf Sinowealth SH68F83 Datasheet]<br />
** US ANSI: XK-HS002 MB27716023<br />
* Full HD camera sensor:<br />
** [https://files.pine64.org/doc/datasheet/PinebookPro/HK-2145-263.pdf Full HD Camera module specification (in Chinese)]<br />
** [https://files.pine64.org/doc/datasheet/PinebookPro/GC2145%20CSP%20DataSheet%20release%20V1.0_20131201.pdf GalaxyCore GC2145 Full HD Camera Sensor Datasheet]<br />
* Battery-related information:<br />
** Battery charging IC: [https://www.ti.com/lit/ds/symlink/bq24171.pdf?ts=1607068456825&ref_url=https%253A%252F%252Fwww.ti.com%252Fproduct%252FBQ24171 Texas Instruments BQ24171 Datasheet]<br />
** Battery monitoring IC: [https://cdn.datasheetspdf.com/pdf-down/C/W/2/CW2015-Cellwise.pdf Cellwise CW2015 Datasheet]<br />
** [https://files.pine64.org/doc/datasheet/pinebook/40110175P%203.8V%2010000mAh规格书-14.pdf 10000mAH Lithium Battery Specification]<br />
* Power path device:<br />
** [https://wiki.pine64.org/images/9/99/Sis412dn.pdf N-MOS / MOSFET]<br />
* NVMe adapter:<br />
** [https://wiki.pine64.org/images/d/d0/Hirose-FH26W-35S-0.3SHW%2860%29-datasheet.pdf FH26-35S-0.3SHW flat flex connector (compatible, not OEM)]<br />
<br />
== Versions ==<br />
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] <br />
<br />
=Skinning and Case Customization=<br />
* Template files for creating custom skins. Each includes template layers for art placement, and CUT lines.<br />
**[https://drive.google.com/open?id=1UKFlC53DO0GJm3Hz1E_669n_HhI45e4n Case Lid Template]<br />
**[https://drive.google.com/open?id=1Q6bKGarMDhvWz3HdGvhL5qDhyHb546ve Case Bottom Template]<br />
**[https://drive.google.com/open?id=1ugI74ygNJ3EN5jXks5jKvdpEAoxIzHo4 Case Palmrest Template]<br />
<br />
= Other Resources =<br />
* [https://forum.pine64.org/forumdisplay.php?fid=111 Pinebook Pro Forum]<br />
* [https://forum.pine64.org/forumdisplay.php?fid=98 ROCKPro64 Forum]<br />
* [https://riot.im/app/#/room/#pinebook:matrix.org Matrix Channel] (no login required to read)<br />
* IRC Server: irc.pine64.org Channel: PineBook<br />
* [https://discordapp.com/channels/463237927984693259/622348681538043924 Discord Channel]<br />
* [https://github.com/rockchip-linux Rockchip Linux GitHub Repo]<br />
* [https://opensource.rock-chips.com/ Rockchip Open Source Wiki]<br />
* [[Pinebook Pro/Freepascal and Lazarus IDE on Manjaro|Freepascal and Lazarus IDE on Pinebook Pro]]<br />
<br />
[[Category:PineBook Pro]]<br />
[[Category:Rockchip RK3399]]</div>Ura2https://wiki.pine64.org/index.php?title=Pinebook_Pro&diff=10347Pinebook Pro2021-05-14T18:20:46Z<p>Ura2: /* Pinebook Pro images */</p>
<hr />
<div>= User Guide =<br />
== Introducing PineBook Pro == <br />
[[File:PBP.jpg|400px|thumb|right|Pinebook Pro running Debian with MATE]]<br />
<br />
The Pinebook Pro is a Linux and *BSD ARM laptop from [https://www.pine64.org/ PINE64]<br />
<br />
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. <br />
<br />
It's compact and slim dimensions are 329mm x 220mm x 12mm (WxDxH).<br />
<br />
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 x4) with an optional adapter. <br />
<br />
The Pinebook Pro is equipped with 4GB LPDDR4 system memory, high capacity eMMC flash storage, and 128Mb SPI boot Flash. The I/O includes: 1 x micro SD card reader (bootable), 1 x USB 2.0, 1 x USB 3.0, 1 x USB type C Host with DP 1.2 and power-in, PCIe x4 for an NVMe SSD drive (requires an optional adapter), and UART (via the headphone jack by setting an internal switch). <br />
<br />
The keyboard and trackpad both use the USB 2.0 protocol. The LCD panel uses eDP MiPi display protocol.<br />
<br />
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.<br />
<br />
== Software and OS Image Downloads ==<br />
<br />
=== Default Manjaro KDE Desktop Quick Start ===<br />
<br />
When you first get your Pinebook Pro and boot it up for the first time, it'll come with Manjaro using the KDE desktop. The Pinebook Pro is officially supported by the Manjaro ARM project, and support can be found on the [https://forum.manjaro.org/c/manjaro-arm/78 Manjaro ARM forums.]<br />
<br />
On first boot, it will ask for certain information such as your timezone location, keyboard layout, username, password, and hostname. Most of these should be self-explanatory. Note that the hostname it asks for should be thought of as the "codename" of your machine, and if you don't know what it's about, you can make something up (use a single word, all lower case, no punctuation; e.g. "pbpro").<br />
<br />
After you're on the desktop, be sure to update it as soon as possible and reboot after updates are finished installing. If nothing appears when you click on the Networking icon in your system tray to connect to your Wi-Fi, ensure the Wi-Fi [https://wiki.pine64.org/index.php/Pinebook_Pro#ANSI_Fn_.2B_F_keys_wrong_for_F9.2C_F10.2C_F11_and_F12 privacy switch] is not disabled.<br />
<br />
=== [[Pinebook Pro_Software_Release|Pinebook Pro images]] ===<br />
Under [[Pinebook Pro Software Release|'Pinebook Pro Software Release/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. <br />
<br />
The list includes OS images and descriptions of:<br />
<br />
[[PinebookPro_Software_Release#Manjaro ARM|'''Manjaro ARM (microSD and eMMC Boot)''']]<br />
<br />
[[PinebookPro_Software_Release#Armbian|'''Armbian (microSD and eMMC Boot)''']]<br />
<br />
[[PinebookPro_Software_Release#Twister OS|'''Twister OS (microSD Boot)''']]<br />
<br />
[[PinebookPro_Software_Release#Fedora|'''Fedora (microSD and eMMC Boot)''']]<br />
<br />
[[PinebookPro_Software_Release#Arch Linux|'''Arch Linux (microSD and USB boot)''']]<br />
<br />
[[PinebookPro_Software_Release#Postmarket OS|'''Postmarket OS (microSD and USB boot)''']]<br />
<br />
[[PinebookPro_Software_Release#Kali Linux|'''Kali Linux (microSD and USB boot)''']]<br />
<br />
[[PinebookPro_Software_Release#Q4OS|'''Q4OS (microSD and eMMC Boot)''']]<br />
<br />
[[PinebookPro_Software_Release#NetBSD|'''NetBSD (microSD and eMMC Boot)''']]<br />
<br />
[[Pinebook_Pro_Software_Release#OpenBSD|'''OpenBSD release for ARM64''']]<br />
<br />
[[Pinebook_Pro_Software_Release#Gentoo_Script_for_Pinebook_Pro|'''Gentoo Script for Pinebook Pro''']]<br />
<br />
=== Quick Links to OS Images Build Sources===<br />
'''Some of the provided OS images are still in <span style="color:#FF0000">beta or nightly build</span> and only fit for testing purposes. These images ought to be avoided for normal usage - use them at <span style="color:#FF0000">your own risk</span>'''<br />
* [https://github.com/ayufan-rock64/linux-build/releases/ ayufan's Linux build repo] (Includes Ubuntu 20.04 Focal Fossa and Debian Buster images. Click 'Assets' at the end of the releases text to view images) <br />
* [https://github.com/ayufan-rock64/chromiumos-build/releases ayufan's Chromium OS build repo]<br />
* [https://github.com/mrfixit2001/debian_desktop/releases mrfixit2001's Linux debian desktop build repo]<br />
* [https://github.com/skiffos/skiffos/releases SkiffOS/Buildroot build repo]<br />
<br />
== Keyboard ==<br />
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. <br />
<br />
The keyboard firmware binary can be flashed from userspace using the provided open source utility. <b style="color: red">WARNING: DO NOT update the keyboard firmware before checking which keyboard IC your Pinebook Pro has.</b> Some Pinebook Pro were delivered with a '''SH61F83''' instead of a '''SH68F83'''. The SH61F83 can only be written 8 times, this will render the keyboard and trackpad unusable if this limit is reached when <code>step-1</code> is flashed. See [//old.reddit.com/r/PINE64official/comments/loq4db/very_disappointed/ Reddit SH61F83 thread].<br />
<br />
Documentation for the keyboard can be found in [[#Datasheets for Components and Peripherals|Datasheets for Components and Peripherals]]. <br />
<br />
=== Typing special characters ===<br />
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. <br />
{| class="wikitable"<br />
!Character<br />
!Key combination/sequence<br />
|-<br />
|Ä, Ö, Ü, ä, ö, ü<br />
|[[Wikipedia:AltGr_key|[AltGr]]]+'[' followed by [A], [O], [U], [a], [o] or [u]<br />
|-<br />
|µ<br />
|[AltGr]+[m]<br />
|-<br />
|Ø, ø<br />
|[AltGr]+[O], [AltGr]+[o]<br />
|-<br />
|@<br />
|[AltGr]+[q] (as on the German layout)<br />
|-<br />
|ß<br />
|[AltGr]+[s]<br />
|-<br />
|§<br />
|[AltGr]+[S]<br />
|-<br />
|°<br />
|[AltGr]+[)]<br />
|}<br />
<br />
=== Privacy Switches ===<br />
There are three privacy switches mapped to the F10, F11 and F12 keys on the Pinebook Pro keyboard. They de/activate the following:<br />
<br />
{| class="wikitable"<br />
|+ Privacy switch function and description<br />
! Combination<br />
! Effect<br />
! Description<br />
! Notes<br />
|-<br />
! scope=row | PINE64 logo key+F10<br />
| Microphone Privacy switch<br />
| CAPs lock LED blinks. 2 blinks = enabled, 3 blinks = disabled<br />
|-<br />
! scope=row | PINE64 logo key+F11<br />
| WiFi Privacy switch<br />
| NUM lock LED blinks. 2 blinks = WiFi enabled / killswitch disabled, 3 blinks = WiFi disabled / killswitch enabled.<br />
| '''Re-enabling requires reboot''' (or a [//forum.pine64.org/showthread.php?tid=8313&pid=52645#pid52645 command line hack to bind/unbind]).<br />
|-<br />
! scope=row | PINE64 logo key+F12<br />
| Camera privacy switch<br />
| CAPs lock and NUM lock LEDs blink together. 2 blinks = enabled, 3 blinks = disabled<br />
| Can use tools like '''<code>lsusb</code>''' to detect camera's presence. If not detected, check privacy switch.<br />
|}<br />
<br />
'''(Press the PINE64 logo key plus F10/F11/F12) for 3 seconds)'''<br />
<br />
The keyboard operates on firmware independant of the operating system. It detects if one of the F10, F11 or F12 keys is pressed in combination with the Pine key for 3 seconds. Doing so disables power to the appropriate peripheral, thereby disabling it. This has the same effect 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 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 inside the keyboard's firmware flash memory.<br />
<br />
== Trackpad ==<br />
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. <br />
Documentation for the trackpad can be found in [[#Datasheets for Components and Peripherals|Datasheets for Components and Peripherals]].<br />
The trackpad firmware binary can be flashed from userspace using the provided open source utility (https://github.com/ayufan-rock64/pinebook-pro-keyboard-updater). A fork with more recent changes is also available (https://github.com/jackhumbert/pinebook-pro-keyboard-updater) and may want to be considered instead while feature parity is different.<br />
<br />
The trackpad controller is connected to the keyboard controller. All trackpad events go through the keyboard controller and it's software, then to the keyboard controller's USB port. Note that the trackpad does have separate firmware, (which has to be written through the keyboard controller).<br />
<br />
<br />
'''Everyone with a Pinebook Pro produced in 2019 should update their keyboard and trackpad firmware.''' <br />
<br />
Before you start:<br />
<br />
<b style="color: red">WARNING: DO NOT update the trackpad firmware before checking which keyboard IC your Pinebook Pro has.</b> Some Pinebook Pro were delivered with a '''SH61F83''' instead of a '''SH68F83'''. The SH61F83 can only be written 8 times, this will render the keyboard and trackpad unusable if this limit is reached when <code>step-1</code> is flashed. See [//old.reddit.com/r/PINE64official/comments/loq4db/very_disappointed/ Reddit SH61F83 thread].<br />
<br />
Please refer to original documentation for details.<br />
<br />
Your Pinebook Pro should be either fully charged or, preferably, running off 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.<br />
<br />
The scripts ought to work on all OSs available for the Pinebook Pro. Some OSs may, however, require installation of relevant dependencies. The instructions below assume a Debian desktop. Newer Pinebook Pro models that come with Manjaro will require a different command to install the proper dependencies.<br />
<br />
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. <br />
Firmware update steps for both models are listed below. <br />
<br />
What you will need:<br />
<br />
*Your Pinebook Pro fully charged or running off of mains power<br />
*Connection to WiFi<br />
*An external USB keyboard & mouse (or access to the Pinebook Pro via SSH)<br />
<br />
'''ISO Model''' <br />
<br />
From the terminal command line: <br />
<br />
<pre><br />
git clone https://github.com/ayufan-rock64/pinebook-pro-keyboard-updater<br />
cd pinebook-pro-keyboard-updater<br />
sudo apt-get install build-essential libusb-1.0-0-dev xxd<br />
make<br />
</pre><br />
<br />
Step 1<br />
<pre><br />
cd pinebook-pro-keyboard-updater<br />
sudo ./updater step-1 iso<br />
sudo reboot<br />
</pre><br />
<br />
Step 2 (after reboot)<br />
<pre><br />
cd pinebook-pro-keyboard-updater<br />
sudo ./updater step-2 iso<br />
sudo reboot<br />
</pre><br />
<br />
----<br />
<br />
'''ANSI Model''' <br />
<br />
*<b>NOTE:</b> Running step 1 on the ANSI keyboard model will make the keyboard and trackpad inaccessible until step 2 is ran, so an external keyboard must be connected to complete the update on this model!<br />
<br />
From the terminal command line: <br />
<br />
<pre><br />
git clone https://github.com/ayufan-rock64/pinebook-pro-keyboard-updater<br />
cd pinebook-pro-keyboard-updater<br />
sudo apt-get install build-essential libusb-1.0-0-dev xxd<br />
make<br />
</pre><br />
<br />
Step 1<br />
<pre><br />
cd pinebook-pro-keyboard-updater<br />
sudo ./updater step-1 ansi<br />
sudo reboot<br />
</pre><br />
<br />
Step 2 (after reboot)<br />
<pre><br />
cd pinebook-pro-keyboard-updater<br />
sudo ./updater step-2 ansi<br />
sudo reboot<br />
</pre><br />
When done, if some of the keys produce incorrect characters, please check your OS’s 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.<br />
<br />
=== X-Windows & trackpad settings ===<br />
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:<br />
<pre>synclient MinSpeed=0.25</pre><br />
You may experiment with different settings, but 0.25 was tested as helping noticeably.<br><br />
<br><br />
To make the change persist across reboots, change the file <code>/etc/X11/xorg.conf</code> similar to below:<br />
<pre> Section "InputClass"<br />
Identifier "touchpad catchall"<br />
Driver "synaptics"<br />
MatchIsTouchpad "on"<br />
MatchDevicePath "/dev/input/event*"<br />
Option "MinSpeed" "0.25"<br />
EndSection</pre><br />
The line <code>Option "MinSpeed" "0.25"</code> is the change.<br><br />
<br><br />
Another forum user built on the above settings a little, and have found these to be very good:<br />
<pre>synclient MinSpeed=0.25<br />
synclient TapButton1=1<br />
synclient TapButton2=3<br />
synclient TapButton3=2<br />
synclient FingerLow=30<br />
synclient PalmDetect=1<br />
synclient VertScrollDelta=64<br />
synclient HorizScrollDelta=64</pre><br />
<br />
<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 unknown whether synaptic works like this.<br />
You may find this config to be comfortable for daily use.<br />
<br><br />
<br />
<code>TabButton</code> allows to just tab the touchpad instead of physically pressing it down (to get this click noise).<br />
<br />
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:<br />
<pre> synclient MaxTapTime=250 </pre><br />
<br />
== Power Supply ==<br />
* Input Power: 5V DC @ 3A<br />
* Mechanical: 3.5mm OD / 1.35mm ID, Barrel jack<br />
* USB-C 5V, 15W PD quickcharge<br />
* Only use one power input at a time, barrel jack OR USB-C<br />
<br />
== LEDs ==<br />
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: <br />
<br />
# The red LED next to the barrel port indicates charging, in three ways. First, it will illuminate steadily when either the factory power supply or a USB Type-C charger is connected to the Pinebook Pro, and the battery is getting charged. Second, if the battery is at 100%, the LED will remain turned off regardless of the connected power input; however, this is [https://forum.pine64.org/showthread.php?tid=10899 rather rarely achieved]. Third, this LED will flash at 0.5&nbsp;Hz if there are any problems that prevent charging, such as the battery becoming too hot.<br />
# The power indicator LED, above the keyboard, supports three different colours: green, amber and red. It is also capable of flashing to indicate eMMC activity. In the default Debian with MATE build, green LED means power and red means suspend (amber is unused). <br />
# The green NumLock LED, above the keyboard.<br />
# The green CapsLock LED, above the keyboard.<br />
<br />
The NumLock and CapsLock LEDs serve their usual purposes on a keyboard, but they also have a secondary function. When the privacy switches get activated they blink to confirm that the switch has been activated.<br />
<br />
== Webcam ==<br />
* Streaming video resolutions supported, (un-compressed):<br />
** 320 x 240 <br />
** 640 x 480<br />
** 800 x 600<br />
** 1280 x 720<br />
** 1600 x 1200<br />
* Still frame resolutions supported:<br />
** 160 x 120<br />
** 176 x 144<br />
** 320 x 240<br />
** 352 x 288 <br />
** 640 x 480<br />
** 800 x 600<br />
** 1280 x 720<br />
** 1600 x 1200<br />
* Some people test with the application Cheese<br />
WIP<br />
<br />
== Microphones ==<br />
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.<br />
<br />
The wires leading to both microphones connect to the mainboard with a small white plastic connector, located directly adjacent to the ribbon cable attachment point for the keyboard interface.<br />
<br />
<br />
'''Microphones not working?'''<br />
<br />
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]]).<br />
<br />
<pre><br />
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 ><br />
> increase the gain to 0dB > change the audio profile in pavucontrol to another with input<br />
<br />
Additionally:<br />
you may want to modify ADC PGA to get the levels to where you want them<br />
</pre><br />
<br />
== Bluetooth and WiFi ==<br />
[[File:PinebookPro_WirelessIC_Location.jpg|400px|thumb|right|The Pinebook Pro's AP6256 wireless module]]<br />
===Hardware Overview===<br />
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. <br />
<br />
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.<br />
<br />
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.<br />
<br />
===Issues===<br />
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.<br />
<br />
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.<br />
<br />
===Wi-Fi Capabilities===<br />
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.<br />
<br />
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.<br />
<br />
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.<br />
<br />
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.<br />
<br />
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.<br />
<br />
===Bluetooth Capabilities===<br />
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.<br />
<br />
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.<br />
<br />
===Disabling Bluetooth===<br />
<pre><br />
#disable bluetooth once<br />
sudo rfkill block bluetooth && <br />
<br />
#confirm<br />
rfkill<br />
</pre><br />
<br />
<pre><br />
#disable bluetooth on boot**<br />
sudo systemctl enable rfkill-block@bluetooth<br />
</pre><br />
<br />
<nowiki>**This does not do what one might want on certain distros, Manjaro XFCE for example. Try the below.</nowiki><br />
<br />
<pre><br />
right click on the bluetooth panel icon > select 'plugins' > PowerManager > configuration > deselect the auto power on option<br />
</pre><br />
<br />
== LCD Panel ==<br />
* Model: BOE NV140FHM-N49<br />
* 14.0" (35.56&nbsp;cm) diagonal size<br />
* 1920x1080 resolution<br />
* 60&nbsp;Hz refresh rate<br />
* IPS technology<br />
* 1000:1 contrast<br />
* 250&nbsp;nit brightness<br />
* 63% sRGB coverage<br />
* 6-bit color<br />
* 30-pin eDP connection<br />
<br />
Some people have tested hardware video decode using the following;<br />
<br />
<pre>ffmpeg -benchmark -c:v h264_rkmpp -i file.mp4 -f null -</pre><br />
<br />
== External ports list ==<br />
Here are a list of the external ports. See [[Pinebook_Pro#Expansion_Ports|Technical Reference - Expansion Ports]] for port specifications.<br />
* Left side<br />
** Barrel jack for power, (with LED)<br />
** USB 3, Type A<br />
** USB 3, Type C<br />
* Right side<br />
** USB 2, Type A<br />
** Standard headset jack<br />
** MicroSD card slot<br />
<br />
== Using the UART ==<br />
[[File:PBPUART.jpeg|400px|thumb|right|Headphone jack UART wiring reference.<br />
<br> Swapping the tx and rx around from this also works and is more traditional.<br />
<br> See [https://files.pine64.org/doc/pinebook/guide/Pinebook_Earphone_Serial_Console_Developer_Guide.pdf this] official Pine64 .pdf.]]<br />
<br />
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.<br />
<br />
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.3&nbsp;V interface (such as the CH340, FTDI-232R, or PL2303, which are sold in both 3.3&nbsp;V and 5&nbsp;V variants) to avoid damage to the CPU. Older version of the serial console cable sold by Pine64 uses wrong voltage level and should not be used; see [https://forum.pine64.org/showthread.php?tid=9367 this forum thread] for further information. Recent version of the same cable uses the right voltage level.<br />
<br />
Insert the USB plug of the cable into an open USB port on the machine which will monitor, ensuring that the audio jack of the serial cable is be fully inserted into the Pinebook Pro audio port. Run the following in a terminal:<br />
<br />
<code><br />
$ lsusb<br />
</code><br />
<br />
you should find a line similar to this:<br />
<br />
<code><br />
Bus 001 Device 058: ID 1a86:7523 QinHeng Electronics HL-340 USB-Serial adapter<br />
</code><br />
<br />
Serial output should now be accessible using screen, picocom or minicom (and others).<br />
Examples:<br />
<br />
<code><br />
screen /dev/ttyUSB0 1500000<br />
<br />
picocom /dev/ttyUSB0 -b 1500000<br />
<br />
minicom -D /dev/ttyUSB0 -b 1500000</code><br />
<br />
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><br />
<br />
== Using the optional NVMe adapter ==<br />
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.<br />
<br />
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.<br />
<br />
Please see [[Pinebook Pro Troubleshooting Guide#NVMe SSD issues|a separate section]] that describes reported issues with the NVMe drives in PineBook Pro.<br />
<br />
=== Installing the adapter ===<br />
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.<br />
(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.)<br />
<br />
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.<br />
<br />
This is the link to the PBPro accessories in the store: [[https://pine64.com/?v=0446c16e2e66]]<br />
<br />
Actual installation instructions are a work in progress. Unofficial instructions for installing V2-2019-1107 can be found [https://eli.gladman.cc/blog/2020/06/23/pine-book-pro-nvme.html here].<br />
<br />
=== Post NVMe install power limiting ===<br />
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.<br />
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);<br />
<pre>$ sudo nvme id-ctrl /dev/nvme0<br />
NVME Identify Controller:<br />
...<br />
ps 0 : mp:9.00W operational enlat:0 exlat:0 rrt:0 rrl:0<br />
rwt:0 rwl:0 idle_power:- active_power:-<br />
ps 1 : mp:4.60W operational enlat:0 exlat:0 rrt:1 rrl:1<br />
rwt:1 rwl:1 idle_power:- active_power:-<br />
ps 2 : mp:3.80W operational enlat:0 exlat:0 rrt:2 rrl:2<br />
rwt:2 rwl:2 idle_power:- active_power:-<br />
ps 3 : mp:0.0450W non-operational enlat:2000 exlat:2000 rrt:3 rrl:3<br />
rwt:3 rwl:3 idle_power:- active_power:-<br />
ps 4 : mp:0.0040W non-operational enlat:6000 exlat:8000 rrt:4 rrl:4<br />
rwt:4 rwl:4 idle_power:- active_power:-<br />
<br />
$ sudo nvme get-feature /dev/nvme0 -f 2<br />
get-feature:0x2 (Power Management), Current value:00000000<br />
$ sudo nvme set-feature /dev/nvme0 -f 2 -v 2 -s<br />
set-feature:02 (Power Management), value:0x000002</pre><br />
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.<br><br />
If you want to test performance without saving the new power setting semi-permanantly, then leave off the "-s" option.<br/><br />
<br/><br />
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;<br />
<pre>$ sudo nvme get-feature -f 0x0c -H /dev/nvme0</pre><br />
Information for this feature, (on a Pinebook Pro), is a work in progress.<br />
<br />
=== Using as data drive ===<br />
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.<br />
<br />
=== Using as OS root drive ===<br />
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.<br />
<br />
The current boot order, per last testing, for this modified U-Boot is:<br />
*MicroSD<br />
*eMMC<br />
*NVMe<br />
<br />
For more information, please refer to [https://forum.pine64.org/showthread.php?tid=8439&pid=53764#pid53764 the forum post.]<br />
<br />
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.)<br />
<br />
Please see [[Pinebook_Pro#Bootable Storage|Bootable Storage]].<br />
<br />
== Caring for the PineBook Pro ==<br />
=== Bypass Cables ===<br />
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 [https://files.pine64.org/doc/PinebookPro/PinebookPro_Engineering_Notice.pdf engineering notice]. <br />
<br />
'''Note that despite the bypass cable being a two conductor cable, it is only used as one. Both wires being soldered together on either side is normal!'''<br />
<br />
WARNING: Do not connect the bypass cables with the battery connected. Using the bypass cables with the battery connected can permanently damage the computer.<br />
<br />
=== [[Pinebook_Service_Step_by_Step_Guides|Pinebook Service Step-by-Step Guides]] ===<br />
<span style="color:#FF0000">Placeholder for Pinebook Pro specific guides</span><br />
<br />
Under [[Pinebook_Service_Step_by_Step_Guides|'Service Guides for Pinebook']] you can find instructions guides concerning disassembly of:<br />
<br />
'''Note: The installation process on Pinebook Pro similar to 14" Pinebook'''<br />
<br />
'''Note: The installation process is the reverse order of removal guide'''<br />
<br />
* 14″ Pinebook Lithium Battery Pack Removal Guide<br />
* 14″ Pinebook LCD Panel Screen Removal Guide<br />
* 14″ Pinebook eMMC Module Removal Guide<br />
<br />
== Using the SPI flash device ==<br />
<br />
See [[Pinebook_Pro_SPI]]<br />
<br />
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.<br />
<br />
Here is some information on using the SPI flash device:<br />
<br />
* You need the kernel built with SPI flash device support, which will supply a device similar to:<br><br><code>/dev/mtd0</code><br><br><br />
* The Linux package below, will need to be available:<br><br><code>mtd-utils</code><br><br><br />
* You can then use this program from the package to write the SPI device:<br><br><code>flashcp &lt;filename&gt; /dev/mtd0</code><br><br><br />
<br />
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.<br />
<br />
The procedures described above are a lot less risky than attaching an external SPI flasher and do not require any additional hardware.<br><br />
<br><br />
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.<br />
<br />
== FAQ ==<br />
What cool software works out of the box? [[Pinebook Pro OTB Experience]]<br />
<br />
= Software tuning guide =<br />
Details on how to get the most out of a Pinebook Pro & its RK3399 SoC.<br />
<br />
== Customizing the Pinebook Pro's default Manjaro KDE system ==<br />
=== Watching DRM content (Netflix, etc.) ===<br />
Most paid online streaming services use Widevine DRM to make their content more difficult to pirate. Widevine is not directly supported on Manjaro KDE, however it is still possible to watch DRM content via the "chromium-docker" package which downloads a 32-bit ARM container and installs Chromium with Widevine inside of that. While not space-efficient, or efficient in general, it's the recommended solution for watching this content on your Pinebook Pro. You can install this package with:<br />
<pre>sudo pacman -Sy chromium-docker</pre><br />
=== Checking GPU capabilities ===<br />
To see what versions of OpenGL and OpenGL ES are supported by the Pinebook Pro, what driver is in use, and what version of the driver is loaded, install the "mesa-demos" package with:<br />
<pre>sudo pacman -Sy mesa-demos</pre><br />
And then run:<br />
<pre>glxinfo | grep OpenGL</pre><br />
This will give detailed information about your graphics card and driver, useful for debugging.<br />
<br />
=== Better GPU compatibility and performance ===<br />
For better graphics performance, you may install the "mesa-git" package, built and supplied in the Manjaro ARM repos. This lets you bring in the latest features, optimizations, and bugfixes for the graphics driver used by the Pinebook Pro. Installation is as simple as:<br />
<pre>pacman -Sy mesa-git</pre><br />
Then you may reboot to load the newer driver.<br />
<br />
With Mesa 20.2 there is no longer much reason to use this over the standard mesa package, and applications may occasionally break with mesa-git.<br />
<br />
[https://docs.mesa3d.org/bugs.html Reporting bugs] to the Mesa project will help make sure any problems are quickly fixed.<br />
<br />
=== OpenGL 3.3 support ===<br />
By default, with the current state of the Panfrost GPU driver, the Pinebook Pro supports OpenGL 2.1 and OpenGL ES 3.0. If you want to use OpenGL 3.3, you need to set the system-wide environment variable, open the '''/etc/environment''' file with:<br />
<pre>kate /etc/environment</pre><br />
And then at the bottom of the file, on a new line, add:<br />
<pre>PAN_MESA_DEBUG="gl3"</pre><br />
Then save the file, entering your password when prompted, and reboot the system. When you check your GPU capabilities, it should report OpenGL 3.3 and applications that rely on it should function properly. Note that GL 3.3 support is incomplete and some rendering features do not work yet, notably geometry shaders.<br />
<br />
=== Install Anbox on Pinebook Pro Manjaro 20.10 ===<br />
[https://www.youtube.com/watch?v=EU8_Q11dATs Youtube video on installing Anbox on Pienbook Pro Manjaro Build 20.10 by LivingLinux]<br />
<br />
== Customizing the Pinebook Pro's previously-default Debian system ==<br />
Here are some hints on what you can do to customize the Pinebook Pro's previous factory image (aka [https://github.com/mrfixit2001/debian_desktop mrfixit2001 debian build])<br />
<br />
=== Initial user changes, password, name, etc ===<br />
When you first get your Pinebook Pro, you should consider setting strong passwords and making the default account your own.<br />
<br />
* 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)<br />
* Once the machine reboots press Alt-Ctrl-F1 to bring up a text terminal<br />
* Login as root (login: root, password: root)<br />
* Set a strong password for the root user using the following command and it's prompts:<br />
<pre># passwd (and follow prompts)</pre><br />
* Rename the rock user to your prefered username (replace myself with whatever you like):<br />
<pre># usermod -l myself -d /home/myself -m rock</pre><br />
* Rename the rock group to match your preferred username:<br />
<pre># groupmod -n myself rock</pre><br />
* Put your name in the account, (replace "John A Doe" with your name):<br />
<pre># chfn -f "John A Doe" myself</pre><br />
* Set a strong password for the normal user:<br />
<pre># passwd myself</pre><br />
* Log out of the text terminal:<br />
<pre># logout</pre><br />
* Press Alt-Ctrl-F7 to go back to the login screen and then login as the normal user<br />
* Open text terminal to fix login error: "Configured directory for incoming files does not exist";<br />
<pre>$ blueman-services</pre><br />
Select "Transfer" tab and set "Incoming Folder" to myself<br />
OR<br />
If adduser is in distro, this is MUCH easier<br />
sudo adduser $USER ,, fill out requested data<br />
Then,, sudo adduser $USER $GROUP,,, 1 group at a time<br />
To see which groups to add,,, id $USER, id rock<br />
<br />
=== Changing the default hostname ===<br />
Debian 9 has a command to allow you to change the hostname. You can see the current settings using;<br />
<pre>> sudo hostnamectl<br />
Static hostname: Debian-Desktop<br />
Icon name: computer<br />
Machine ID: dccbddccbdccbdccbdccbdccbdccbccb<br />
Boot ID: ea99ea99ea99ea99ea99ea99ea99ea99<br />
Operating System: Debian GNU/Linux 9 (stretch)<br />
Kernel: Linux 4.4.210<br />
Architecture: arm64</pre><br />
To change, use this, (with "My_Hostname" used as the example);<br />
<pre>> sudo hostnamectl set-hostname My_Hostname</pre><br />
Whence done, you can re-verify using the first example.<br />
<br />
Then you should backup and edit your <code>/etc/hosts</code> entry's name;<br />
<pre>> sudo cp -p /etc/hosts /etc/hosts.`date +%Y%m%d`<br />
> sudo vi /etc/hosts<br />
127.0.0.1 localhost<br />
127.0.0.1 My_Hostname<br />
::1 localhost ip6-localhost ip6-loopback<br />
fe00::0 ip6-localnet<br />
ff00::0 ip6-mcastprefix<br />
ff02::1 ip6-allnodes<br />
ff02::2 ip6-allrouters<br />
127.0.1.1 linaro-alip</pre><br />
<br />
=== Disable Chromium browser's prompt for passphrase & password storage ===<br />
<br />
Perform the following steps:<br />
<br />
* On the tool bar, hover over the Chromium icon<br />
* Using the right mouse button, select '''Properties'''<br />
* In the '''Command:''' line section, add <code>--password-store=basic</code> before the <code>%U</code><br />
* Use the '''x Close''' button to save the change<br />
This will of course, use basic password storage, meaning any saved passwords are not encrypted. Perfectly fine if you never use password storage.<br />
<br />
=== Changing the boot splash picture ===<br />
<br />
The default boot splash picture can be replaced using the following instructions:<br />
<br />
* Install '''ImageMagick''' which will do the conversion<br />
<pre>$ sudo apt-get install imagemagick</pre><br />
* Create a 1920 x 1080 picture. For the best results, use a PNG image (It supports lossless compression).<br />
* From the directory in which your new image is stored run the following commands<br />
* Convert your image to the bootsplash raw format using imagemagick convert.<br />
<pre>$ convert yoursplashimage.png -separate +channel -swap 0,2 -combine -colorspace sRGB RGBO:splash.fb</pre><br />
* Create a backup copy of your current splash screen<br />
<pre>$ sudo cp /usr/share/backgrounds/splash.fb /usr/share/backgrounds/splash_original.fb</pre><br />
* Copy your new splash screen into place<br />
<pre>$ sudo cp splash.fb /usr/share/backgrounds/splash.fb</pre><br />
* Set the correct permissions on the splash.fb file<br />
<pre>$ sudo chmod 644 /usr/share/backgrounds/splash.fb</pre><br />
* If you do not want to see kernel console text messages, make sure you don't have '''Plymouth''' installed<br />
<br />
=== Watching Amazon Prime videos with Chromium ===<br />
When you create a new user, it will be necessary to launch the Chromium browswer with a specific user agent like below;<br />
<pre>chromium-browser --user-agent="Mozilla/5.0 (X11; CrOS armv7l 6946.63.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/72.0.3626.121 Safari/537.36"</pre><br />
There may be more tweaks needed.<br />
<br />
=== Enabling text boot time messages ===<br />
<br />
By default, most Linux distros have a boot screen with a picture. To see all the boot time messages, use one of the following;<br />
<br />
<b><u>Default Debian</u></b><br />
* Backup and edit the U-Boot configuration file:<br />
<pre>cp -p /etc/default/u-boot /etc/default/u-boot.`date +%Y%m%d`<br />
chmod a-w /etc/default/u-boot.`date +%Y%m%d`<br />
vi /etc/default/u-boot</pre><br />
Remove the '''quiet''' and '''splash''' parameters. Leave everything else alone.<br />
* Update the U-Boot configuration:<br />
<pre>u-boot-update</pre><br />
* Test and verify you get what you think you should be seeing.<br />
<br><br />
<b><u>Manjaro</u></b><br />
* Backup and edit the U-Boot configuration file:<br />
<pre>cp -p /boot/extlinux/extlinux.conf /boot/extlinux/extlinux.conf.`date +%Y%m%d`<br />
chmod a-w /boot/extlinux/extlinux.conf.`date +%Y%m%d`<br />
vi /boot/extlinux/extlinux.conf</pre><br />
Change '''console=ttyS2,1500000''' to '''console=tty1'''<br> <br />
Remove the '''bootsplash.bootfile''' option and it's parameter.<br><br />
You can add verbose logging by appending '''ignore_loglevel''' to the line where boot splash was.<br><br />
Leave everything else alone.<br><br />
* Test and verify you get what you think you should be seeing.<br />
<br />
== Improving readability ==<br />
<br />
Some people find that a 14" LCD screen with 1080p, (1920 x 1080), has text and icons a bit too small. There are things you can do to make the screen easier to use and read.<br><br />
* Increase the font size<br />
* Use a font with more pronounced features<br />
* Increase the various window manager sizes (e.g. increase the height of the tool bar)<br />
* Change the color scheme to be easier on the eyes. Higher contrast can help usability.<br />
* Change the window manager's decorations (e.g. use larger icons)<br />
* Use a workspace manager, with one application per workspace<br />
* When at home or office, use an external monitor<br />
* Change the X-Windows DPI<br />
<br><br />
However, do not change the resolution of the LCD screen, otherwise you may end up with a blank / black screen. If that happens, see this troubleshooting section for the fix:<br><br />
[[Pinebook_Pro#After_changing_builtin_LCD_resolution.2C_blank_screen|Blank screen after changing builtin LCD resolution]]<br />
<br />
== Chromium tweaks ==<br />
<br />
=== Flags ===<br />
<br />
From the [https://github.com/mrfixit2001/updates_repo/blob/v1.8/pinebook/filesystem/default official Debian image]:<br />
<br />
<pre><br />
--disable-low-res-tiling \<br />
--num-raster-threads=6 \<br />
--profiler-timing=0 \<br />
--disable-composited-antialiasing \<br />
--test-type \<br />
--show-component-extension-options \<br />
--ignore-gpu-blacklist \<br />
--use-gl=egl \<br />
--ppapi-flash-path=/usr/lib/chromium-browser/pepper/libpepflashplayer.so \<br />
--ppapi-flash-version=32.0.0.255 \<br />
--enable-pinch \<br />
--flag-switches-begin \<br />
--enable-gpu-rasterization \<br />
--enable-oop-rasterization \<br />
--flag-switches-end<br />
</pre><br />
<br />
Note that in some cases, this may also decrease performance substantially, as observed when using these flags on the Manjaro KDE desktop. Feel free to experiment to find what is smoothest for you personally.<br />
<br />
== gVim has performance issue ==<br />
It appears that using GTK3 can cause very slow scrolling, while Vim in a terminal window works fine.<br/><br />
Simply revert back to using GTK2, (how to do so is somewhat Linux distro-specific).<br />
<br />
Another solution may be to run gVim with <br />
<br />
GDK_RENDERING=image<br />
<br />
environment variable set. It seems that this improves the performance by reverting back to software-only rendering.<br />
<br />
== Kernel options ==<br />
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.<br />
<br />
To see if a specific feature is enabled in the current kernel, you can use something like this;<br />
<br />
<pre><br />
$ zgrep -i rockchip_pcie /proc/config.gz<br />
# CONFIG_ROCKCHIP_PCIE_DMA_OBJ is not set<br />
CONFIG_PHY_ROCKCHIP_PCIE=m<br />
</pre><br />
If it's listed as <code>=m</code>, then it's a module. You can see if the module is loaded with;<br />
<pre><br />
$ lsmod | grep -i rockchip_pcie<br />
phy_rockchip_pcie 16384 0<br />
</pre><br />
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.<br />
<br />
=== Hardware video decoding ===<br />
Here is a method to check for hardware video decoding by the VPU. There are special Linux kernel modules that perform this function.<br><br />
Older systems, such as the previously-default Debian desktop, use the Rockchip-supplied kernel module <code>rk-vcodec</code>. To check, something like this can be used:<br />
<pre><br />
$ lsmod | grep rk-vcodec<br />
or<br />
$ zgrep RK_VCODEC /proc/config.gz<br />
CONFIG_RK_VCODEC=y<br />
</pre><br />
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.<br><br />
<br><br />
<br />
Newer systems may use a different option as in the configuration below:<br />
<pre><br />
$ zgrep HANTRO /proc/config.gz<br />
CONFIG_VIDEO_HANTRO=m<br />
CONFIG_VIDEO_HANTRO_ROCKCHIP=y<br />
</pre><br />
<br />
= Troubleshooting guide =<br />
<br />
Do not to panic if something goes wrong or in an unexpected way. Instead, stop and consider carefully how to undo something, or how to redo it. This particularly applies when flashing a new operating system, or flashing new firmware to the keyboard or touchpad. If everything fails, consider reporting the issue on the forums, with as many relevant details as available.<br />
<br />
Please, have a look at the [[Pinebook Pro Troubleshooting Guide]], which details a number of issues you may encounter.<br />
<br />
= Hardware/Accessory Compatibility =<br />
Please contribute to the [[Pinebook Pro Hardware Accessory Compatibility|hardware/accessory compatibility page]], which lists the status of hardware tested with the Pinebook Pro. Available hardware categories include the following:<br />
<br />
* [[Pinebook Pro Hardware Accessory Compatibility#NVMe SSD drives|NVMe SSD drives]]<br />
* [[Pinebook Pro Hardware Accessory Compatibility#USB hardware|USB hardware]]<br />
* [[Pinebook Pro Hardware Accessory Compatibility#USB C alternate mode DP|USB-C alternate mode DP]]<br />
* [[Pinebook Pro Hardware Accessory Compatibility#Other hardware|Other hardware]]<br />
<br />
= Technical Reference =<br />
== Disassembly and Reassembly == <br />
[[File:Standoffs.png|400px|thumb|right|Pinebook Screw stand-offs correct placement and location]]<br />
<br />
There are a few '''mandatory''' precautions to be taken:<br />
<br />
* 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.<br />
* When removing the back cover plate, *do not, under any circumstances, slide your fingertips between the metal shell and the plastic frame!* The back cover plate edges are sharp, and when combined with the pressure and movement generated from, specifically, attempting to slide the tips of your fingers along the bottom edge of the plate along the lid-hinge, they *will* slice open the tips of your fingers like a knife.<br />
* When removing the back cover plate, use care to avoid damaging the speakers. They are stuck to the back cover with double-sided tape, and the thin wires are very delicate.<br />
<br />
[[File:PinebookProScrewGuide.png|400px|thumb|right|PinebookPro external screws (this particular unit has suffered damage on screw (4)L)]]<br />
<br />
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. There are four (4) short screws along the front edge, and six (6) long screws along the 3 remaining sides. Remove the cover from the back where the hinges are situated by lifting it up and away from the rest of the chassis. The aluminum case is held on only by screws. There are no plastic snaps, and the shell should pull away without any effort. If you experience any resistance at all stop and ensure all ten (10) screws are accounted for.<br />
<br />
During reassembly, make sure that the back-screw standoffs are in place and seated correctly. Before replacing the aluminum back-plate, ensure that the speakers are properly seated by pressing gently on the hard plastic edge of the speaker module. 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 4 short screws.<br />
<br />
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 (which may be caused by the aforementioned misseating of the speakers), 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, re-open the machine and check for misseated components.<br />
<br />
A basic 3D model to print replacement standoffs for the back cover screws is [https://www.thingiverse.com/thing:4226648 available on Thingiverse], until the official drawings or 3D models are made available.<br />
<br />
== Internal Layout ==<br />
<br />
=== Main chips ===<br />
* RK3399 system-on-chip (1)<br />
* LPDDR4 SDRAM (21)<br />
* SPI NOR flash memory (29)<br />
* eMMC flash memory (26)<br />
* WiFi/BT module (27)<br />
<br />
=== Mainboard Switches and Buttons ===<br />
There are two switches on the main board: disabling the eMMC (24), and enabling UART (9) via headphone jack. <br />
<br />
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). <br />
<br />
[[File:PBPL_S.jpg]]<br />
<br />
=== Key Internal Parts ===<br />
{| class="wikitable"<br />
|+ Numbered parts classification and description<br />
! Number<br />
! Type<br />
! Descriptor<br />
|-<br />
! scope=row | 1<br />
| Component || RK3399 System-On-Chip<br />
|-<br />
! scope=row | 2<br />
| Socket || PCIe x4 slot for optional NVMe adapter<br />
|-<br />
! scope=row | 3<br />
| Socket || Speakers socket<br />
|-<br />
! scope=row | 4<br />
| Socket || Trackpad socket<br />
|-<br />
! scope=row | 5<br />
| Component || Left speaker <br />
|-<br />
! scope=row | 6<br />
| Connector || Power bridge connector <br />
|-<br />
! scope=row | 7<br />
| Socket || Keyboard Socket<br />
|-<br />
! scope=row | 8<br />
| Component || Optional NVMe SSD adapter<br />
|-<br />
! scope=row | 9<br />
| Switch || UART/Audio switch - outputs UART via headphone jack<br />
|-<br />
! scope=row | 10<br />
| Socket || Power bridge socket<br />
|-<br />
! scope=row | 11<br />
| Socket || Battery socket<br />
|-<br />
! scope=row | 12<br />
| Component || Trackpad<br />
|-<br />
! scope=row | 13<br />
| Component || Battery<br />
|-<br />
! scope=row | 14<br />
| Component || Right speaker<br />
|-<br />
! scope=row | 15<br />
| Socket || MicroSD card slot<br />
|-<br />
! scope=row | 16<br />
| Socket || Headphone / UART jack<br />
|-<br />
! scope=row | 17<br />
| Socket || USB 2.0 Type A<br />
|-<br />
! scope=row | 18<br />
| Socket || Daughterboard-to-mainboard ribbon cable socket<br />
|-<br />
! scope=row | 19<br />
| Cable || Daughterboard-to-mainboard ribbon cable<br />
|-<br />
! scope=row | 20<br />
| Component || microphone<br />
|-<br />
! scope=row | 21<br />
| Component || LPDDR4 RAM<br />
|-<br />
! scope=row | 22<br />
| Socket || Mainboard-to-daughterboard ribbon cable socket<br />
|-<br />
! scope=row | 23<br />
| Socket || Microphone socket<br />
|-<br />
! scope=row | 24<br />
| Switch || Switch to hardware disable eMMC<br />
|-<br />
! scope=row | 25<br />
| Antenna || BT/WiFI antenna<br />
|-<br />
! scope=row | 26<br />
| Component || eMMC flash memory module <br />
|-<br />
! scope=row | 27<br />
| Component ||BT/WiFi module chip<br />
|-<br />
! scope=row | 28<br />
| Buttons || Reset and recovery buttons<br />
|-<br />
! scope=row | 29<br />
| Component || SPI flash storage<br />
|-<br />
! scope=row | 30<br />
| Socket || eDP LCD socket<br />
|-<br />
! scope=row | 31<br />
| Socket || Power in barrel socket<br />
|-<br />
! scope=row | 32<br />
| Socket || USB 3.0 Type A<br />
|-<br />
! scope=row | 33<br />
| Socket || USB 3.0 Type C <br />
|}<br />
<br />
=== Smallboard detailed picture ===<br />
<br />
[[File:Pinebook_pro_smallboard.jpg]]<br />
<br />
== Bootable Storage ==<br />
<br />
=== Boot sequence details ===<br />
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.<br><br />
[[RK3399_boot_sequence|RK3399 boot sequence]]<br />
<br />
=== Boot devices ===<br />
<br />
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. <br />
<br />
At this time, the Pinebook Pro ships with a Manjaro + KDE build with [https://www.denx.de/wiki/U-Boot/ uboot] on the eMMC. Its boot order is: SD, USB, then eMMC.<br />
<br />
(An update has been pushed for the older 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.)<br />
<br />
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<br />
in a /boot partition on the eMMC.<br />
<br />
=== eMMC information ===<br />
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.<br />
<br />
The eMMC storage will show up as multiple block devices:<br />
*mmcblk1boot0 - eMMC standard boot0 partition, may be 4MB<br />
*mmcblk1boot1 - eMMC standard boot1 partition, may be 4MB<br />
*mmcblk1rpmb - eMMC standard secure data partition, may be 16MB<br />
*mmcblk1 - This block contains the user areas<br />
<br />
Only the last is usable as regular storage device in the Pinebook Pro.<br />
The device number of "1" shown above may vary, depending on kernel.<br />
<br />
If the eMMC module is enabled after boot from an SD card, you can detect this change with the following commands as user "root";<br />
<pre><br />
echo fe330000.sdhci >/sys/bus/platform/drivers/sdhci-arasan/unbind<br />
echo fe330000.sdhci >/sys/bus/platform/drivers/sdhci-arasan/bind<br />
</pre><br />
<br />
== Case Dimensions and Data ==<br />
* Dimensions: 329mm x 220mm x 12mm (WxDxH)<br />
* Weight: 1.26Kg<br />
* Screws<br />
** Philips head type screws<br />
** M2 flat head machine screws (measurements in mm)<br />
** 4 x Small screws (used along the front edge): Head - 3.44, Thread Diameter - 1.97, Thread Length - 2.1, Overall length - 3.05<br />
** 6 x Large screws: Head - 3.44, Thread Diameter - 1.97, Thread Length - 4.41, Overall Length - 5.85<br />
* Rubber Feet<br />
** 18mm diameter<br />
** 3mm height<br />
** Dome shaped<br />
<br />
== SoC and Memory Specification ==<br />
[[File:Rockchip_RK3399.png|right]]<br />
* Based on Rockchip RK3399<br />
<br />
=== CPU Architecture ===<br />
* big.LITTLE architecture: Dual Cortex-A72 + Quad Cortex-A53, 64-bit CPU<br />
** Full implementation of the ARM architecture v8-A instruction set (both AArch64 and AArch32)<br />
** ARM Neon Advanced SIMD (single instruction, multiple data) support for accelerated media and signal processing computation<br />
** ARMv8 Cryptography Extensions<br />
** VFPv4 floating point unit supporting single and double-precision operations<br />
** Hardware virtualization support<br />
** TrustZone technology support<br />
** Full CoreSight debug solution<br />
** One isolated voltage domain to support DVFS<br />
* Cortex-A72 (big cluster):<br />
** [https://developer.arm.com/products/processors/cortex-a/cortex-a72 Dual-core Cortex-A72 up to 2.0GHz CPU]<br />
** Superscalar, variable-length, out-of-order pipeline<br />
** L1 cache 48KB Icache and 32KB Dcache for each A72 <br />
** L2 cache 1024KB for big cluster <br />
* Cortex-A53 (little cluster):<br />
** [https://developer.arm.com/products/processors/cortex-a/cortex-a53 Quad-core Cortex-A53 up to 1.5GHz CPU]<br />
** In-order pipeline with symmetric dual-issue of most instructions <br />
** L1 cache 32KB Icache and 32KB Dcache for each A53<br />
** L2 cache 512KB for little cluster<br />
* Cortex-M0 (control processors):<br />
** [https://developer.arm.com/ip-products/processors/cortex-m/cortex-m0 Cortex-M0 CPU]<br />
** Two Cortex-M0 cooperate with the central processors<br />
** Architecture: Armv6-M<br />
** Thumb/Thumb2 instruction set<br />
** 32 bit only<br />
<br />
=== GPU Architecture ===<br />
* [https://developer.arm.com/products/graphics-and-multimedia/mali-gpus/mali-t860-and-mali-t880-gpus ARM Mali-T860MP4 Quad-core GPU]<br />
* 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.<br />
* Frequency 650MHz <br />
* Throughput 1300Mtri/s, 10.4Gpix/s<br />
* Graphic interface standards:<br />
** OpenGL® ES 1.1, 1.2, 2.0, 3.0, 3.1, 3.2. (Panfrost has initial support of 3.0 beginning 2020/02/27)<br />
** Vulkan 1.0, using the Mali binary blob. (Panfrost does not support Vulkan as of 2020/06/24)<br />
** OpenCL™ 1.1, 1.2<br />
** DirectX® 11 FL11_1<br />
** RenderScript™<br />
<br />
=== System Memory ===<br />
* RAM Memory:<br />
** LPDDR4<br />
** 800MHz, (limited by RK3399)<br />
** Dual memory channels on the CPU, each 32 bits wide<br />
** Quad memory channels on the RAM chip, each 16 bits wide, 2 bonded together for each CPU channel<br />
** 4GB as a single 366 pin mobile RAM chip<br />
* Storage Memory: <br />
** 64GB eMMC module, can be upgraded to an 128GB eMMC module. (The initial PINE64 community build version shipped with a 128GB eMMC.)<br />
** eMMC version 5.1, HS400, 8 bit on RK3399 side<br />
** Bootable<br />
* SPI flash:<br />
** [[Pinebook Pro SPI]]<br />
** 128Mbit / 16MByte<br />
** 1 bit interface<br />
** Bootable, (first boot device, ahead of eMMC & SD card)<br />
** U-Boot images can be made to work, but as of 2020/06/24 there is no standardized image available.<br />
<br />
=== Video out ===<br />
* USB-C Alt mode DP<br />
* Up to 3840x2160 p60, dependant on adapter, (2 lanes verses 4 lanes)<br />
<br />
=== Expansion Ports ===<br />
* MicroSD card:<br />
** Bootable<br />
** Supports SD, SDHC and SDXC cards, up to 512GB tested. SDXC standard says 2TB is the maximum.<br />
** Version SD3.0, (MMC 4.5), up to 50MB/s<br />
** SD card Application Performance Class 1 (A1), (or better), recommended by some users, for better IOPS<br />
* USB ports:<br />
** 1 x USB 2.0 Type-A Host Port, bootable<br />
** 1 x USB 3.0 Type-A Host Port, 5Gbps, is not bootable<br />
** 1 x USB 3.0 Type-C OTG Port, 5Gbps, (includes laptop charging function), is not bootable<br />
** 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.<br />
* Headphone jack switchable to UART console mux circuit<br />
<br />
== Additional hardware ==<br />
Hardware that is not part of the SoC.<br />
<br />
=== Battery ===<br />
* Lithium Polymer Battery (10,000 mAH)<br />
<br />
=== Display ===<br />
* 14.0" 1920x1080 IPS LCD panel<br />
=== Lid closed magnet ===<br />
There is a magnet to detect when the laptop lid is closed, so action can be taken like sleep. This meets up with the Hall sensor on the daughter / small board to detect lid closed.<br />
* The magnet is located on the LCD panel right side, around 1.5 inches up measure from bottom edge.<br />
<br />
=== Webcam ===<br />
* Internal USB attached Webcam<br />
<br />
=== Audio ===<br />
* 3.5mm stereo earphone/microphone plug<br />
* Built-in microphone<br />
* Built-in stereo speakers:<br />
** Oval in design<br />
** 3 mm high x 20 mm x 30 mm<br />
<br />
=== Network ===<br />
* WiFi:<br />
** 802.11 b/g/n/ac<br />
** Dual band: 2.4Ghz & 5Ghz<br />
** Single antenna<br />
* Bluetooth 5.0<br />
<br />
=== Optional NVMe adapter ===<br />
* PCIe 2.0, 5&nbsp;GT/s per lane<br />
* Four PCIe lanes, which can not be bifurcated, but can be used with one- or two-lane NVMe cards<br />
* '''M''' keyed, though '''M'''+'''B''' keyed devices will work too<br />
* Maximum length for M.2 card is 80mm (M.2 2280). The following sizes will also work: 2230, 2242, 2260<br />
* Power: 2.5&nbsp;W continuous, 8.25&nbsp;W peak momentary<br />
* Does not support SATA M.2 cards<br />
* Does not support USB M.2 cards<br />
<br />
== Pinebook Pro Schematics and Certifications ==<br />
* Pinebook Pro Main Board Schematic And Silkscreen:<br />
** [https://files.pine64.org/doc/PinebookPro/pinebookpro_v2.1_mainboard_schematic.pdf Pinebook Pro Main Board ver 2.1 Schematic]<br />
** [https://wiki.pine64.org/images/3/30/Pinebookpro-v2.1-top-ref.pdf Pinebook Pro ver 2.1 Top Layer Silkscreen]<br />
** [https://wiki.pine64.org/images/b/b7/Pinebookpro-v2.1-bottom-ref.pdf Pinebook Pro ver 2.1 Bottom Layer Silkscreen]<br />
* Pinebook Pro Daughter Board Schematic:<br />
** [https://files.pine64.org/doc/PinebookPro/pinebookpro_v2.1_daughterboard_schematic.pdf Pinebook Pro Daughter Board ver 2.1 Schematic]<br />
* Optional Pinebook Pro NVMe Adapter Schematic:<br />
** [https://files.pine64.org/doc/PinebookPro/pinebookpro_v2.1_NVMe-adapter_schematic.pdf Pinebook Pro NVMe Adapter Board ver 2.1 Schematic]<br />
* Serial Console Earphone Jack Pinout:<br />
** [https://files.pine64.org/doc/pinebook/guide/Pinebook_Earphone_Serial_Console_Developer_Guide.pdf Pinkbook Serial Console Earphone Jack Pinout]<br />
* Pinebook Pro Case:<br />
** [https://files.pine64.org/doc/PinebookPro/drawings/Pinebook%20Pro%20Principle%20Views.pdf AutoCAD PDF File ]<br />
** [https://files.pine64.org/doc/PinebookPro/drawings/Pinebook%20Pro%20Principle%20Views.ai AutoCAD AI File ]<br />
** [https://files.pine64.org/doc/PinebookPro/drawings/Pinebook%20Pro%20Principle%20Views.dwg AutoCAD DWG File ]<br />
* Pinebook Pro Certifications:<br />
** [https://files.pine64.org/doc/cert/Pinebook%20Pro%20FCC%20Certificate-S19071103501001.pdf Pinebook Pro FCC Certificate]<br />
** [https://files.pine64.org/doc/cert/Pinebook%20Pro%20CE%20RED%20Certificate-S19051404304.pdf Pinebook Pro CE Certificate]<br />
** [https://files.pine64.org/doc/cert/Pinebook%20Pro%20ROHS%20Compliance%20Certificate.pdf Pinebook Pro RoHS Certificate]<br />
<br />
== Datasheets for Components and Peripherals ==<br />
* Rockchip RK3399 SoC information:<br />
** [https://www.rock-chips.com/a/en/products/RK33_Series/2016/0419/758.html Rockchip RK3399 SoC Brief]<br />
** [https://opensource.rock-chips.com/images/d/d7/Rockchip_RK3399_Datasheet_V2.1-20200323.pdf Rockchip RK3399 Datasheet v2.1]<br />
** [https://www.rockchip.fr/Rockchip%20RK3399%20TRM%20V1.4%20Part1.pdf Rockchip RK3399 Technical Reference Manual v1.4, part 1]<br />
** [https://www.rockchip.fr/Rockchip%20RK3399%20TRM%20V1.3%20Part1.pdf Rockchip RK3399 Technical Reference Manual v1.3, part 1] and [https://www.rockchip.fr/Rockchip%20RK3399%20TRM%20V1.3%20Part2.pdf part 2]<br />
** [https://files.pine64.org/doc/datasheet/rockpro64/RK808%20datasheet%20V0.8.pdf Rockchip RK808 Datasheet v0.8]<br />
* LPDDR4 SDRAM (366-pin BGA):<br />
** [https://files.pine64.org/doc/datasheet/PinebookPro/micron%20SM512M64Z01MD4BNK-053FT%20LPDDR4%20(366Ball).pdf Micron 366 balls Mobile LPDDR4 Datasheet]<br />
* eMMC information:<br />
** [https://files.pine64.org/doc/rock64/PINE64_eMMC_Module_20170719.pdf PINE64 eMMC module schematic]<br />
** [https://files.pine64.org/doc/rock64/usb%20emmc%20module%20adapter%20v2.pdf PINE64 USB adapter for eMMC module V2 schematic]<br />
** [https://files.pine64.org/doc/rock64/USB%20adapter%20for%20eMMC%20module%20PCB.tar PINE64 USB adapter for eMMC module PCB in JPEG]<br />
** [https://files.pine64.org/doc/datasheet/pine64/SDINADF4-16-128GB-H%20data%20sheet%20v1.13.pdf 64GB/128GB SanDisk eMMC Datasheet]<br />
* SPI NOR Flash information:<br />
** [https://files.pine64.org/doc/datasheet/pine64/w25q128jv%20spi%20revc%2011162016.pdf WinBond 128Mb SPI Flash Datasheet]<br />
** [https://wiki.pine64.org/images/b/b9/Ds-00220-gd25q127c-rev1-df2f4.pdf GigaDevice 128Mb SPI Flash Datasheet (updated)]<br />
* Wireless and Bluetooth information:<br />
** [https://files.pine64.org/doc/datasheet/PinebookPro/AP6256%20datasheet_V1.7_12282018.pdf AMPAK AP6256 11AC Wi-Fi + Bluetooth5 Datasheet]<br />
* Audio codec:<br />
** [http://www.everest-semi.com/pdf/ES8316%20PB.pdf Everest ES8316 Audio Codec Datasheet]<br />
* LCD panel:<br />
** [https://files.pine64.org/doc/datasheet/PinebookPro/NV140FHM-N49_Rev.P0_20160804_201710235838.pdf 14" 1920x1080 IPS LCD Panel datasheet]<br />
* USB-related information:<br />
** Internal USB 2.0 hub: [https://wiki.pine64.org/images/3/39/GL850G_USB_Hub_1.07.pdf GL850G USB Hub Datasheet]<br />
** USB Type-C Controller: [https://www.onsemi.com/pub/Collateral/FUSB302-D.PDF ON Semiconductor FUSB302 Datasheet]<br />
* Touchpad information:<br />
** [https://files.pine64.org/doc/datasheet/PinebookPro/YX%20HK-9562%20HID%20I2C%20Specification.pdf PineBook Pro Touchpad Specification]<br />
* Keyboard information:<br />
** [https://wiki.pine64.org/images/b/b0/SH68F83V2.0.pdf Sinowealth SH68F83 Datasheet]<br />
** US ANSI: XK-HS002 MB27716023<br />
* Full HD camera sensor:<br />
** [https://files.pine64.org/doc/datasheet/PinebookPro/HK-2145-263.pdf Full HD Camera module specification (in Chinese)]<br />
** [https://files.pine64.org/doc/datasheet/PinebookPro/GC2145%20CSP%20DataSheet%20release%20V1.0_20131201.pdf GalaxyCore GC2145 Full HD Camera Sensor Datasheet]<br />
* Battery-related information:<br />
** Battery charging IC: [https://www.ti.com/lit/ds/symlink/bq24171.pdf?ts=1607068456825&ref_url=https%253A%252F%252Fwww.ti.com%252Fproduct%252FBQ24171 Texas Instruments BQ24171 Datasheet]<br />
** Battery monitoring IC: [https://cdn.datasheetspdf.com/pdf-down/C/W/2/CW2015-Cellwise.pdf Cellwise CW2015 Datasheet]<br />
** [https://files.pine64.org/doc/datasheet/pinebook/40110175P%203.8V%2010000mAh规格书-14.pdf 10000mAH Lithium Battery Specification]<br />
* Power path device:<br />
** [https://wiki.pine64.org/images/9/99/Sis412dn.pdf N-MOS / MOSFET]<br />
* NVMe adapter:<br />
** [https://wiki.pine64.org/images/d/d0/Hirose-FH26W-35S-0.3SHW%2860%29-datasheet.pdf FH26-35S-0.3SHW flat flex connector (compatible, not OEM)]<br />
<br />
== Versions ==<br />
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] <br />
<br />
=Skinning and Case Customization=<br />
* Template files for creating custom skins. Each includes template layers for art placement, and CUT lines.<br />
**[https://drive.google.com/open?id=1UKFlC53DO0GJm3Hz1E_669n_HhI45e4n Case Lid Template]<br />
**[https://drive.google.com/open?id=1Q6bKGarMDhvWz3HdGvhL5qDhyHb546ve Case Bottom Template]<br />
**[https://drive.google.com/open?id=1ugI74ygNJ3EN5jXks5jKvdpEAoxIzHo4 Case Palmrest Template]<br />
<br />
= Other Resources =<br />
* [https://forum.pine64.org/forumdisplay.php?fid=111 Pinebook Pro Forum]<br />
* [https://forum.pine64.org/forumdisplay.php?fid=98 ROCKPro64 Forum]<br />
* [https://riot.im/app/#/room/#pinebook:matrix.org Matrix Channel] (no login required to read)<br />
* IRC Server: irc.pine64.org Channel: PineBook<br />
* [https://discordapp.com/channels/463237927984693259/622348681538043924 Discord Channel]<br />
* [https://github.com/rockchip-linux Rockchip Linux GitHub Repo]<br />
* [https://opensource.rock-chips.com/ Rockchip Open Source Wiki]<br />
* [[Pinebook Pro/Freepascal and Lazarus IDE on Manjaro|Freepascal and Lazarus IDE on Pinebook Pro]]<br />
<br />
[[Category:PineBook Pro]]<br />
[[Category:Rockchip RK3399]]</div>Ura2https://wiki.pine64.org/index.php?title=Pinebook_Pro_Software_Releases&diff=10346Pinebook Pro Software Releases2021-05-14T18:07:54Z<p>Ura2: Rearranged Linux releases in order of importance (Subjective in nature, but conservatively ranked). Got rid of ayufans Ubuntu because its not even ubuntu but rather an experimental kernel project by the looks of it</p>
<hr />
<div>= Linux OS Image Releases =<br />
For information on how to install these images onto your device, please see the [[NOOB]] Page, which includes information on writing images to the device eMMC or an SD card<br />
<br />
== Manjaro ARM ==<br />
[[File:Manjaro.png|right|100px]]<br />
<br />
* The Manjaro project offers a mainline kernel with patches and modules to support PBPro hardware in two flavors. Both provide DD images and installer images (DD to SD card which will then install to eMMC when booted).<br />
* To learn more about Manjaro please visit [https://forum.manjaro.org/tags/manjaroarm Manjaro Forum]<br />
* You can follow the ongoing discussion about Twister OS on the PINE64 forum (https://forum.pine64.org/showthread.php?tid=8207)<br />
<br />
=== Manjaro ARM with KDE (Plasma) desktop [microSD / eMMC Boot] ===<br />
<br />
* [https://manjaro.org/downloads/arm/pinebook-pro/arm8-pinebook-pro-kde-plasma/ Direct download from Manjaro] (microSD image only)<br />
* [https://osdn.net/projects/manjaro-arm/storage/pbpro/kde-plasma/ Direct download from osdn.net] (both microSD and emmc-installer images)<br />
<br />
=== Manjaro ARM with GTK (XFCE) desktop [microSD / eMMC Boot] ===<br />
<br />
* [https://manjaro.org/downloads/arm/pinebook-pro/arm8-pinebook-pro-xfce/ Direct download from Manjaro]<br />
* [https://osdn.net/projects/manjaro-arm/storage/pbpro/xfce/ Direct download from osdn.net]<br />
<br />
=== Manjaro ARM with i3 tiling window manager [microSD / eMMC Boot] ===<br />
<br />
* [https://manjaro.org/downloads/arm/pinebook-pro/arm8-pinebook-pro-i3/ Direct download from Manjaro]<br />
* [https://osdn.net/projects/manjaro-arm/storage/pbpro/i3/ Direct download from osdn.net]<br />
<br />
=== Manjaro ARM with Sway tiling window manager [microSD / eMMC Boot] ===<br />
<br />
* [https://osdn.net/projects/manjaro-arm/storage/pbpro/sway/ Direct download from osdn.net]<br />
<br />
=== Manjaro ARM installer ===<br />
<br />
The [https://gitlab.manjaro.org/manjaro-arm/applications/manjaro-arm-installer manjaro-arm-installer] script is intended to install Manjaro ARM directly to SD/eMMC cards without the need for images (including LXQT, Mate & CuboCore editions, as well as full disk encryption). Running on a Linux x86 computer, it can install Manjaro ARM directly to an empty eMMC using an eMMC to USB adapter. The script can also be run from SD to install an image to the eMMC.<br />
<br />
== Armbian ==<br />
[[File:armbian.png|right|100px]]<br />
<br />
* To find out more about Armbian and available options please visit their [https://www.armbian.com/pinebook-pro/ site]<br />
* DD image to microSD card or eMMC module and boot. Highly recommend using [https://etcher.io/ Etcher]<br />
<br />
=== Armbian Ubuntu Focal XFCE Desktop mainline kernel [microSD / eMMC Boot] ===<br />
* Armbian provides a mainline kernel build images for Ubuntu Focal with XFCE Desktop<br />
* DD image (for 8GB micoSD card or eMMC Module and above)<br />
** [https://dl.armbian.com/pinebook-pro/Focal_current_desktop Armbian's Pinebook Pro Ubuntu Focal XFCE Desktop download site]<br />
<br />
=== Armbian Ubuntu Focal XFCE Desktop legacy kernel [microSD / eMMC Boot] ===<br />
* Armbian provides a legacy kernel 4.4 build images for Ubuntu Focal with XFCE Desktop<br />
* DD image (for 8GB microSD card or eMMC Module and above)<br />
** [https://dl.armbian.com/pinebook-pro/Focal_legacy_desktop Armbian's Pinebook Pro Ubuntu Focal XFCE Desktop download site]<br />
<br />
=== Armbian Debian Buster XFCE Desktop legacy kernel [microSD / eMMC Boot] ===<br />
* Armbian provides a legacy kernel 4.4 build images for Debian Buster with XFCE Desktop<br />
* DD image (for 8GB micoSD card or eMMC Module and above)<br />
** [https://dl.armbian.com/pinebook-pro/Buster_legacy_desktop Armbian's Pinebook Pro Debian Buster XFCE Desktop download site]<br />
<br />
=== Armbian Ubuntu Bionic XFCE Desktop legacy kernel [microSD / eMMC Boot] ===<br />
* Armbian provides a legacy kernel 4.4 build images for Ubuntu Bionic with XFCE Desktop<br />
* DD image (for 8GB micoSD card or eMMC Module and above)<br />
** [https://dl.armbian.com/pinebook-pro/Bionic_legacy_desktop Armbian's Pinebook Pro Ubuntu Bionic XFCE Desktop download site]<br />
<br />
== Twister OS ==<br />
[[File:Twister_OS.png|right|100px]]<br />
<br />
=== Twister OS Armbian-Reforged XFCE Dsktop beta images [SD boot]===<br />
* For more infomation on Twister OS, please visit this {https://twisteros.com/ official site]<br />
* You can follow the ongoing discussion about Twister OS on the PINE64 forum (https://forum.pine64.org/showthread.php?tid=12192)<br />
* After flashing image with Etcher, edit /boot/armbianEnv.txt, replace the dtb name with rk3399-pinebook-pro.dtb.<br />
* DD image (for 16GB microSD card /16GB eMMC module and above):<br />
** [https://twisteros.com/twisterarmbian.html Direct download latest images from Twister OS's website]<br />
** size: 2.8GB<br />
* Login with<br />
** password: asdasd<br />
<br />
=== Twister OS Monka-Manjaro XFCE Dsktop beta images [SD boot]===<br />
* For more infomation on Twister OS, please visit this {https://twisteros.com/ official site]<br />
* You can follow the ongoing discussion about Twister OS on the PINE64 forum (https://forum.pine64.org/showthread.php?tid=12192)<br />
* After flashing image with Etcher, edit /boot/armbianEnv.txt, replace the dtb name with rk3399-pinebook-pro.dtb.<br />
* DD image (for 16GB microSD card /16GB eMMC module and above):<br />
** [https://drive.google.com/file/d/1I0yHIDfezqnz1jdphJ4gooWbGtNw0ArW/view?usp=sharing Direct download latest images from Google Drive]<br />
** size: 8.9GB<br />
* Login with<br />
** username: pi<br />
** password: root<br />
<br />
== Fedora ==<br />
[[File:fedora1.png|right|100px]]<br />
<br />
=== Fedora 34/33/32 Gnome/KDE/Minimal Images [microSD / eMMC Boot] ===<br />
* Unofficial images based on Fedora, and a [https://copr.fedorainfracloud.org/coprs/aptupdate/pinebook-pro/ copr] repository for kernel and tweaks.<br />
* To learn more about how they are build [https://github.com/bengtfredh/pinebook-pro-fedora-installer Install script].<br />
* DD image (for 12GB microSD card / eMMC module and above) [https://github.com/bengtfredh/pinebook-pro-fedora-installer/wiki/How-to-Resize---Expand-a-Btrfs-Volume---Filesystem How to expand btrfs]<br />
** [https://s3.fredhs.net/minio/pinebook-pro-image/ Fedora Pinebook Pro Images]<br />
<br />
=== Fedora 32 Cinnamon Desktop OS Image [microSD / eMMC Boot] ===<br />
* This image contains an install of Fedora with [https://cinnamon-spices.linuxmint.com/ Cinnamon] desktop environment. <br />
* To learn more about Fedora please visit the [https://getfedora.org/ official website].<br />
* DD image (for 12GB microSD card / eMMC module and above)<br />
** [https://builds.armdevelopers.com/pinebook-pro/releases/dev/Fedora32-Cinnamon-Desktop-202009.0.pinebook-pro.img.xz Fedora 32 Pinebook Pro Image]<br />
* login with:<br />
** username: root<br />
** password: fedora<br />
<br />
=== Fedora 32 KDE Desktop OS Image [microSD / eMMC Boot] ===<br />
* This image contains an install of Fedora with [https://kde.org/ KDE aka Plasma] desktop environment. <br />
* To learn more about Fedora please visit the [https://getfedora.org/ official website].<br />
* DD image (for 12GB microSD card / eMMC module and above)<br />
** [https://builds.armdevelopers.com/pinebook-pro/releases/dev/Fedora32-KDE-Desktop-202009.0.pinebook-pro.img.xz Fedora 32 Pinebook Pro Image]<br />
* login with:<br />
** username: root<br />
** password: fedora<br />
<br />
=== Fedora 32 Xfce Desktop OS Image [microSD / eMMC Boot] ===<br />
* This image contains an install of Fedora with [https://xfce.org/ xfce] desktop environment. <br />
* To learn more about Fedora please visit the [https://getfedora.org/ official website].<br />
* DD image (for 12GB microSD card / eMMC module and above)<br />
** [https://builds.armdevelopers.com/pinebook-pro/releases/dev/Fedora32-Xfce-Desktop-202009.0.pinebook-pro.img.xz Fedora 32 Pinebook Pro Image]<br />
* login with:<br />
** username: root<br />
** password: fedora<br />
<br />
=== Fedora 32 Workstation OS Image [microSD / eMMC Boot] ===<br />
* This image contains an install of Fedora with [https://www.gnome.org/gnome-3/ GNOME 3] desktop environment. <br />
* To learn more about Fedora please visit the [https://getfedora.org/ official website].<br />
* DD image (for 12GB microSD card / eMMC module and above)<br />
** [https://builds.armdevelopers.com/pinebook-pro/releases/dev/Fedora32-Workstation-202009.0.pinebook-pro.img.xz Fedora 32 Pinebook Pro Image]<br />
* login with:<br />
** username: root<br />
** password: fedora<br />
<br />
== Arch Linux ==<br />
[[File:Archlinux-logo.png|right|100px]]<br />
<br />
=== Arch Linux ARM install image [microSD/USB Boot] ===<br />
* archiso image customized for Arch Linux ARM on the Pinebook Pro<br />
* DD image (for 1GB or larger microSD card/USB stick):<br />
** [https://github.com/nadiaholmquist/archiso-pbp/releases Direct download for latest releases from GitHub]<br />
** size: 579MB<br />
* Automatic login as root<br />
* Make sure to thoroughly read the [https://github.com/nadiaholmquist/archiso-pbp/blob/master/README.md readme] and [https://github.com/nadiaholmquist/archiso-pbp/blob/master/FAQ.md FAQ], otherwise follow the normal Arch installation guide.<br />
<br />
== postmarketOS ==<br />
[[File:PostmarketOS logo.png|right|100px]]<br />
<br />
===Official postmarketOS build [microSD/ eMMC Boot] ===<br />
* Official postmarketOS build with the GNOME desktop for the Pinebook Pro. <br />
* DD image (for 8GB microSD card /16GB eMMC module and above):<br />
** [http://images.postmarketos.org/pinebookpro/ Direct download latest images from postmarketOS]<br />
** size: 400MB<br />
* Login with<br />
** username: demo<br />
** password: demo OR 147147<br />
<br />
==Kali Linux==<br />
[[File:Kali.jpeg|right|100px]]<br />
<br />
=== Kali Linux prebuilt OS images for Pinebook Pro [SD/eMMC boot]===<br />
* Official pre-built OS images of Kali Linux for the Pinebook Pro featuring all tools you'd expect from the distribution. <br />
* DD image (for 8GB microSD card /16GB eMMC module and above):<br />
** [https://www.offensive-security.com/kali-linux-arm-images/ Direct download latest images from Offensive Security's website]<br />
** size: 2.0GB<br />
* Login with<br />
** username: kali<br />
** password: kali<br />
<br />
== Q4OS ==<br />
[[File:q4os.png|right|100px]]<br />
<br />
=== Q4OS Test Build Image [microSD / eMMC Boot] ===<br />
* Q4OS is advertised as a 'fast and powerful operating system based on the latest technologies while offering highly productive desktop environment'<br />
* To learn more please visit the [https://forum.pine64.org/showthread.php?tid=8385 PINE64 forum] or official [https://q4os.org/index.html Q4OS website]<br />
* DD image (for 8GB microSD card / eMMC module and above)<br />
** [https://sourceforge.net/projects/q4os/files/testing/ Direct download latest release build from SourceForge]<br />
* User account and password are created on first run<br />
<br />
= BSD OS Image Release =<br />
<br />
==NetBSD==<br />
[[File:netbsd.png|right|100px]]<br />
<br />
=== NetBSD [microSD /eMMC Boot] ===<br />
* To learn more about NetBSD please visit [https://www.netbsd.org/ NetBSD main page] <br />
* DD image to microSD card or eMMC module. Highly recommend using [https://etcher.io/ Etcher]<br />
** [http://www.armbsd.org/arm/ Direct download from NetBSD]<br />
* Console and SSH default login:<br />
** username: root<br />
** password: [none]<br />
* Instructions concerning enabling SSH can be found [https://www.netbsd.org/docs/guide/en/chap-boot.html#chap-boot-ssh here]<br />
<br />
==OpenBSD==<br />
[[File:Puffy_mascot_openbsd.png|right|100px]]<br />
<br />
=== OpenBSD ===<br />
* To learn more about OpenBSD, please visit [https://www.openbsd.org/ OpenBSD main page]<br />
* ARM64 images, (including support for Pinebook Pro), can be found here [https://www.openbsd.org/arm64.html OpenBSD arm64]<br />
<br />
= Linux Installer Releases =<br />
== Debian Installer ==<br />
[[File:debian.png|right|100px]]<br />
<br />
=== Daniel Thompson's Debian Installer for the Pinebook Pro ===<br />
* This is an image creator and Debian installer that runs from an existing Linux OS and installs Debian Bullseye<br />
** Installer can configure an encrypted rootfs and provides a choice of desktops, including the default Debian desktop based on Gnome 3<br />
** Strict adoption of upstream Debian packages (with exception of kernel and bootloaders) in order to provide a clean upgrade path as Bullseye matures<br />
* Download at: https://github.com/daniel-thompson/pinebook-pro-debian-installer/<br />
* Pull requests welcome but for discussion and support please use [https://forum.pine64.org/showthread.php?tid=8487 the forum topic].<br />
<br />
For more information, see the [[Pinebook_Pro_Debian_Installer]] wiki page<br />
<br />
=== Official Debian Installer Images ===<br />
* Uses only the upstream kernel and firmware without special patches<br />
* No graphical display yet, works only through serial console<br />
* Requires adding the non-free component to your /etc/apt/sources.list file and installing the "firmware-linux" package for Wi-Fi and Bluetooth support<br />
* Installer is loaded into RAM, can install onto the same media from which it’s booted<br />
* Supports automatic partitioning and full disk encryption through LVM<br />
* Installer currently doesn't install the bootloader, leaving the installed system in an unbootable state until it's manually added<br />
<br />
[https://d-i.debian.org/daily-images/arm64/daily/netboot/SD-card-images/ The relevant files are built daily here] and may sometimes be unavailable if the build system is having issues. The "README.concatenateable_images" file provides instructions on how to combine the partition.img.gz file with the firmware.pinebook-pro.rk3399.img.gz file in order to create a DD-able image.<br />
<br />
The official images are '''not''' recommended yet until the display begins working and the installer properly installs the bootloader. Most users will want to see [[Pinebook Pro Debian Installer|Daniel Thompson's Debian Installer]] instead.<br />
<br />
<br />
== Gentoo Script ==<br />
[[File:GentooLogo.png|right|100px]]<br />
<br />
=== Gentoo Script for Pinebook Pro ===<br />
* This is a script that prepares a Gentoo arm64 stage 3 tarball for the Pinebook Pro<br />
** The script takes care of device specifics like an optimized make.conf, an overlay that provides kernel and firmware amongst others, and other miscellaneous fixes<br />
* The usual tarball setup as per [https://wiki.gentoo.org/wiki/Handbook:AMD64 Gentoo Handbook] is left to the user.<br />
* Forum thread with instructions at https://forum.pine64.org/showthread.php?tid=8765<br />
<br />
<br />
==Kali Script==<br />
[[File:Kali.jpeg|right|100px]]<br />
<br />
=== Kali Linux for Pinebook Pro ===<br />
* This is a script to create official Kali Linux OS images for the Pinebook Pro<br />
** The script carries out the build process in entirety and is Pinebook Pro specific<br />
* Please pull the latest [https://gitlab.com/kalilinux/build-scripts/kali-arm/blob/master/pinebook-pro.sh Kali Linux install script] from the project's GitLab.<br />
* For more information regarding building the OS image please read the README instruction at https://gitlab.com/kalilinux/build-scripts/kali-arm/blob/master/README.md<br />
<br />
<br />
==K1ss OS Script==<br />
[[File:K1ss.png|right|100px]]<br />
<br />
=== K1ss Linux for Pinebook Pro ===<br />
* This is a repository containing an unofficial port of KISS Linux to aarch64. The tarball is built for generic aarch64, currently being tested on the Pinebook Pro.<br />
* Please pull the latest [https://github.com/jedavies-dev/kiss-aarch64 K1ss Linux install script] from the project's GitHub.<br />
* * You can follow the ongoing discussion about K1ss Linux on the PINE64 forum (https://forum.pine64.org/showthread.php?tid=9304)<br />
<br />
<br />
==NixOS Script==<br />
[[File:nixos.png|right|100px]]<br />
<br />
=== NixOS for Pinebook Pro ===<br />
* This is instructions to install NixOS on the Pinebook Pro: https://nixos.wiki/wiki/NixOS_on_ARM/PINE64_Pinebook_Pro<br />
* Please pull the latest [https://github.com/samueldr/wip-pinebook-pro samueldr's repository ] from the project's GitHub.<br />
* * There is a good chance we will see Tier 1 support for aarch64, including the Pinebook Pro, in 2021 (https://github.com/NixOS/rfcs/pull/87)<br />
* * You can follow the ongoing discussion about NixOS on the PINE64 forum (https://forum.pine64.org/showthread.php?tid=10524)<br />
<br />
==SkiffOS for Pinebook Pro ==<br />
[[File:SkiffOS-Icon-1.png|right|100px]]<br />
<br />
=== SkiffOS Boot Image for Pinebook Pro ===<br />
* Instructions to build/install on the Pinebook Pro: https://github.com/skiffos/SkiffOS/tree/master/configs/pine64/book<br />
* Please pull the latest version from the project's GitHub.<br />
* Compiling the boot image takes approximately 30 minutes.<br />
* Easily configure the kernel, compiler, etc with Buildroot.<br />
* Pre-built ISOs will be available with the upcoming 2021.02 <br />
release.<br />
<br />
=== Skiff Core ===<br />
* Supports multiple distros running simultaneously.<br />
* Optionally build from scratch on device on first boot.<br />
* Pre-built multi-arch core container images are available.<br />
<br />
=== GentooLTO with KDE Apps ===<br />
<br />
* GentooLTO with O3 optimized KDE Desktop configuration.<br />
* Use <tt>SKIFF_CONFIG=pine64/book,core/pinebook_gentoo</tt><br />
* Default sign-in is username "core" w/ empty password.<br />
<br />
<br />
[[Category:PineBook Pro]]</div>Ura2https://wiki.pine64.org/index.php?title=Pinebook_Pro_Software_Releases&diff=10345Pinebook Pro Software Releases2021-05-14T18:03:11Z<p>Ura2: Removed unsupported Distros, meaning no release in > 6 months</p>
<hr />
<div>= Linux OS Image Releases =<br />
For information on how to install these images onto your device, please see the [[NOOB]] Page, which includes information on writing images to the device eMMC or an SD card<br />
<br />
==Kali Linux==<br />
[[File:Kali.jpeg|right|100px]]<br />
<br />
=== Kali Linux prebuilt OS images for Pinebook Pro [SD/eMMC boot]===<br />
* Official pre-built OS images of Kali Linux for the Pinebook Pro featuring all tools you'd expect from the distribution. <br />
* DD image (for 8GB microSD card /16GB eMMC module and above):<br />
** [https://www.offensive-security.com/kali-linux-arm-images/ Direct download latest images from Offensive Security's website]<br />
** size: 2.0GB<br />
* Login with<br />
** username: kali<br />
** password: kali<br />
<br />
<br />
== Arch Linux ==<br />
[[File:Archlinux-logo.png|right|100px]]<br />
<br />
=== Arch Linux ARM install image [microSD/USB Boot] ===<br />
* archiso image customized for Arch Linux ARM on the Pinebook Pro<br />
* DD image (for 1GB or larger microSD card/USB stick):<br />
** [https://github.com/nadiaholmquist/archiso-pbp/releases Direct download for latest releases from GitHub]<br />
** size: 579MB<br />
* Automatic login as root<br />
* Make sure to thoroughly read the [https://github.com/nadiaholmquist/archiso-pbp/blob/master/README.md readme] and [https://github.com/nadiaholmquist/archiso-pbp/blob/master/FAQ.md FAQ], otherwise follow the normal Arch installation guide.<br />
<br />
<br />
== Manjaro ARM ==<br />
[[File:Manjaro.png|right|100px]]<br />
<br />
* The Manjaro project offers a mainline kernel with patches and modules to support PBPro hardware in two flavors. Both provide DD images and installer images (DD to SD card which will then install to eMMC when booted).<br />
* To learn more about Manjaro please visit [https://forum.manjaro.org/tags/manjaroarm Manjaro Forum]<br />
* You can follow the ongoing discussion about Twister OS on the PINE64 forum (https://forum.pine64.org/showthread.php?tid=8207)<br />
<br />
=== Manjaro ARM with KDE (Plasma) desktop [microSD / eMMC Boot] ===<br />
<br />
* [https://manjaro.org/downloads/arm/pinebook-pro/arm8-pinebook-pro-kde-plasma/ Direct download from Manjaro] (microSD image only)<br />
* [https://osdn.net/projects/manjaro-arm/storage/pbpro/kde-plasma/ Direct download from osdn.net] (both microSD and emmc-installer images)<br />
<br />
=== Manjaro ARM with GTK (XFCE) desktop [microSD / eMMC Boot] ===<br />
<br />
* [https://manjaro.org/downloads/arm/pinebook-pro/arm8-pinebook-pro-xfce/ Direct download from Manjaro]<br />
* [https://osdn.net/projects/manjaro-arm/storage/pbpro/xfce/ Direct download from osdn.net]<br />
<br />
=== Manjaro ARM with i3 tiling window manager [microSD / eMMC Boot] ===<br />
<br />
* [https://manjaro.org/downloads/arm/pinebook-pro/arm8-pinebook-pro-i3/ Direct download from Manjaro]<br />
* [https://osdn.net/projects/manjaro-arm/storage/pbpro/i3/ Direct download from osdn.net]<br />
<br />
=== Manjaro ARM with Sway tiling window manager [microSD / eMMC Boot] ===<br />
<br />
* [https://osdn.net/projects/manjaro-arm/storage/pbpro/sway/ Direct download from osdn.net]<br />
<br />
=== Manjaro ARM installer ===<br />
<br />
The [https://gitlab.manjaro.org/manjaro-arm/applications/manjaro-arm-installer manjaro-arm-installer] script is intended to install Manjaro ARM directly to SD/eMMC cards without the need for images (including LXQT, Mate & CuboCore editions, as well as full disk encryption). Running on a Linux x86 computer, it can install Manjaro ARM directly to an empty eMMC using an eMMC to USB adapter. The script can also be run from SD to install an image to the eMMC.<br />
<br />
== Fedora ==<br />
[[File:fedora1.png|right|100px]]<br />
<br />
=== Fedora 34/33/32 Gnome/KDE/Minimal Images [microSD / eMMC Boot] ===<br />
* Unofficial images based on Fedora, and a [https://copr.fedorainfracloud.org/coprs/aptupdate/pinebook-pro/ copr] repository for kernel and tweaks.<br />
* To learn more about how they are build [https://github.com/bengtfredh/pinebook-pro-fedora-installer Install script].<br />
* DD image (for 12GB microSD card / eMMC module and above) [https://github.com/bengtfredh/pinebook-pro-fedora-installer/wiki/How-to-Resize---Expand-a-Btrfs-Volume---Filesystem How to expand btrfs]<br />
** [https://s3.fredhs.net/minio/pinebook-pro-image/ Fedora Pinebook Pro Images]<br />
<br />
=== Fedora 32 Cinnamon Desktop OS Image [microSD / eMMC Boot] ===<br />
* This image contains an install of Fedora with [https://cinnamon-spices.linuxmint.com/ Cinnamon] desktop environment. <br />
* To learn more about Fedora please visit the [https://getfedora.org/ official website].<br />
* DD image (for 12GB microSD card / eMMC module and above)<br />
** [https://builds.armdevelopers.com/pinebook-pro/releases/dev/Fedora32-Cinnamon-Desktop-202009.0.pinebook-pro.img.xz Fedora 32 Pinebook Pro Image]<br />
* login with:<br />
** username: root<br />
** password: fedora<br />
<br />
=== Fedora 32 KDE Desktop OS Image [microSD / eMMC Boot] ===<br />
* This image contains an install of Fedora with [https://kde.org/ KDE aka Plasma] desktop environment. <br />
* To learn more about Fedora please visit the [https://getfedora.org/ official website].<br />
* DD image (for 12GB microSD card / eMMC module and above)<br />
** [https://builds.armdevelopers.com/pinebook-pro/releases/dev/Fedora32-KDE-Desktop-202009.0.pinebook-pro.img.xz Fedora 32 Pinebook Pro Image]<br />
* login with:<br />
** username: root<br />
** password: fedora<br />
<br />
=== Fedora 32 Xfce Desktop OS Image [microSD / eMMC Boot] ===<br />
* This image contains an install of Fedora with [https://xfce.org/ xfce] desktop environment. <br />
* To learn more about Fedora please visit the [https://getfedora.org/ official website].<br />
* DD image (for 12GB microSD card / eMMC module and above)<br />
** [https://builds.armdevelopers.com/pinebook-pro/releases/dev/Fedora32-Xfce-Desktop-202009.0.pinebook-pro.img.xz Fedora 32 Pinebook Pro Image]<br />
* login with:<br />
** username: root<br />
** password: fedora<br />
<br />
=== Fedora 32 Workstation OS Image [microSD / eMMC Boot] ===<br />
* This image contains an install of Fedora with [https://www.gnome.org/gnome-3/ GNOME 3] desktop environment. <br />
* To learn more about Fedora please visit the [https://getfedora.org/ official website].<br />
* DD image (for 12GB microSD card / eMMC module and above)<br />
** [https://builds.armdevelopers.com/pinebook-pro/releases/dev/Fedora32-Workstation-202009.0.pinebook-pro.img.xz Fedora 32 Pinebook Pro Image]<br />
* login with:<br />
** username: root<br />
** password: fedora<br />
<br />
== Armbian ==<br />
[[File:armbian.png|right|100px]]<br />
<br />
* To find out more about Armbian and available options please visit their [https://www.armbian.com/pinebook-pro/ site]<br />
* DD image to microSD card or eMMC module and boot. Highly recommend using [https://etcher.io/ Etcher]<br />
<br />
=== Armbian Ubuntu Focal XFCE Desktop mainline kernel [microSD / eMMC Boot] ===<br />
* Armbian provides a mainline kernel build images for Ubuntu Focal with XFCE Desktop<br />
* DD image (for 8GB micoSD card or eMMC Module and above)<br />
** [https://dl.armbian.com/pinebook-pro/Focal_current_desktop Armbian's Pinebook Pro Ubuntu Focal XFCE Desktop download site]<br />
<br />
=== Armbian Ubuntu Focal XFCE Desktop legacy kernel [microSD / eMMC Boot] ===<br />
* Armbian provides a legacy kernel 4.4 build images for Ubuntu Focal with XFCE Desktop<br />
* DD image (for 8GB microSD card or eMMC Module and above)<br />
** [https://dl.armbian.com/pinebook-pro/Focal_legacy_desktop Armbian's Pinebook Pro Ubuntu Focal XFCE Desktop download site]<br />
<br />
=== Armbian Debian Buster XFCE Desktop legacy kernel [microSD / eMMC Boot] ===<br />
* Armbian provides a legacy kernel 4.4 build images for Debian Buster with XFCE Desktop<br />
* DD image (for 8GB micoSD card or eMMC Module and above)<br />
** [https://dl.armbian.com/pinebook-pro/Buster_legacy_desktop Armbian's Pinebook Pro Debian Buster XFCE Desktop download site]<br />
<br />
=== Armbian Ubuntu Bionic XFCE Desktop legacy kernel [microSD / eMMC Boot] ===<br />
* Armbian provides a legacy kernel 4.4 build images for Ubuntu Bionic with XFCE Desktop<br />
* DD image (for 8GB micoSD card or eMMC Module and above)<br />
** [https://dl.armbian.com/pinebook-pro/Bionic_legacy_desktop Armbian's Pinebook Pro Ubuntu Bionic XFCE Desktop download site]<br />
<br />
== Twister OS ==<br />
[[File:Twister_OS.png|right|100px]]<br />
<br />
=== Twister OS Armbian-Reforged XFCE Dsktop beta images [SD boot]===<br />
* For more infomation on Twister OS, please visit this {https://twisteros.com/ official site]<br />
* You can follow the ongoing discussion about Twister OS on the PINE64 forum (https://forum.pine64.org/showthread.php?tid=12192)<br />
* After flashing image with Etcher, edit /boot/armbianEnv.txt, replace the dtb name with rk3399-pinebook-pro.dtb.<br />
* DD image (for 16GB microSD card /16GB eMMC module and above):<br />
** [https://twisteros.com/twisterarmbian.html Direct download latest images from Twister OS's website]<br />
** size: 2.8GB<br />
* Login with<br />
** password: asdasd<br />
<br />
=== Twister OS Monka-Manjaro XFCE Dsktop beta images [SD boot]===<br />
* For more infomation on Twister OS, please visit this {https://twisteros.com/ official site]<br />
* You can follow the ongoing discussion about Twister OS on the PINE64 forum (https://forum.pine64.org/showthread.php?tid=12192)<br />
* After flashing image with Etcher, edit /boot/armbianEnv.txt, replace the dtb name with rk3399-pinebook-pro.dtb.<br />
* DD image (for 16GB microSD card /16GB eMMC module and above):<br />
** [https://drive.google.com/file/d/1I0yHIDfezqnz1jdphJ4gooWbGtNw0ArW/view?usp=sharing Direct download latest images from Google Drive]<br />
** size: 8.9GB<br />
* Login with<br />
** username: pi<br />
** password: root<br />
<br />
== Ubuntu 20.04 Focal Fossa MATE / GNOME ==<br />
[[File:UbuntuLogo.png|right|100px]]<br />
<br />
=== Ubuntu 20.04 Focal Fossa MATE and GNOME Community Builds [microSD/ eMMC Boot] by ayufan ===<br />
* Desktop Images featurng a standard Ubuntu suite of software to get you started. <br />
* DD image (for 8GB microSD card /16GB eMMC module and above):<br />
** [https://github.com/ayufan-rock64/linux-build/releases Direct download for latests releases and pre-releases on ayufan's github]<br />
** size: 1.06GB<br />
* Login with<br />
** username: rock64<br />
** password: rock64 (must be changed on initial boot)<br />
<br />
== postmarketOS ==<br />
[[File:PostmarketOS logo.png|right|100px]]<br />
<br />
===Official postmarketOS build [microSD/ eMMC Boot] ===<br />
* Official postmarketOS build with the GNOME desktop for the Pinebook Pro. <br />
* DD image (for 8GB microSD card /16GB eMMC module and above):<br />
** [http://images.postmarketos.org/pinebookpro/ Direct download latest images from postmarketOS]<br />
** size: 400MB<br />
* Login with<br />
** username: demo<br />
** password: demo OR 147147<br />
<br />
<br />
== Q4OS ==<br />
[[File:q4os.png|right|100px]]<br />
<br />
=== Q4OS Test Build Image [microSD / eMMC Boot] ===<br />
* Q4OS is advertised as a 'fast and powerful operating system based on the latest technologies while offering highly productive desktop environment'<br />
* To learn more please visit the [https://forum.pine64.org/showthread.php?tid=8385 PINE64 forum] or official [https://q4os.org/index.html Q4OS website]<br />
* DD image (for 8GB microSD card / eMMC module and above)<br />
** [https://sourceforge.net/projects/q4os/files/testing/ Direct download latest release build from SourceForge]<br />
* User account and password are created on first run<br />
<br />
= BSD OS Image Release =<br />
<br />
==NetBSD==<br />
[[File:netbsd.png|right|100px]]<br />
<br />
=== NetBSD [microSD /eMMC Boot] ===<br />
* To learn more about NetBSD please visit [https://www.netbsd.org/ NetBSD main page] <br />
* DD image to microSD card or eMMC module. Highly recommend using [https://etcher.io/ Etcher]<br />
** [http://www.armbsd.org/arm/ Direct download from NetBSD]<br />
* Console and SSH default login:<br />
** username: root<br />
** password: [none]<br />
* Instructions concerning enabling SSH can be found [https://www.netbsd.org/docs/guide/en/chap-boot.html#chap-boot-ssh here]<br />
<br />
==OpenBSD==<br />
[[File:Puffy_mascot_openbsd.png|right|100px]]<br />
<br />
=== OpenBSD ===<br />
* To learn more about OpenBSD, please visit [https://www.openbsd.org/ OpenBSD main page]<br />
* ARM64 images, (including support for Pinebook Pro), can be found here [https://www.openbsd.org/arm64.html OpenBSD arm64]<br />
<br />
= Linux Installer Releases =<br />
== Debian Installer ==<br />
[[File:debian.png|right|100px]]<br />
<br />
=== Daniel Thompson's Debian Installer for the Pinebook Pro ===<br />
* This is an image creator and Debian installer that runs from an existing Linux OS and installs Debian Bullseye<br />
** Installer can configure an encrypted rootfs and provides a choice of desktops, including the default Debian desktop based on Gnome 3<br />
** Strict adoption of upstream Debian packages (with exception of kernel and bootloaders) in order to provide a clean upgrade path as Bullseye matures<br />
* Download at: https://github.com/daniel-thompson/pinebook-pro-debian-installer/<br />
* Pull requests welcome but for discussion and support please use [https://forum.pine64.org/showthread.php?tid=8487 the forum topic].<br />
<br />
For more information, see the [[Pinebook_Pro_Debian_Installer]] wiki page<br />
<br />
=== Official Debian Installer Images ===<br />
* Uses only the upstream kernel and firmware without special patches<br />
* No graphical display yet, works only through serial console<br />
* Requires adding the non-free component to your /etc/apt/sources.list file and installing the "firmware-linux" package for Wi-Fi and Bluetooth support<br />
* Installer is loaded into RAM, can install onto the same media from which it’s booted<br />
* Supports automatic partitioning and full disk encryption through LVM<br />
* Installer currently doesn't install the bootloader, leaving the installed system in an unbootable state until it's manually added<br />
<br />
[https://d-i.debian.org/daily-images/arm64/daily/netboot/SD-card-images/ The relevant files are built daily here] and may sometimes be unavailable if the build system is having issues. The "README.concatenateable_images" file provides instructions on how to combine the partition.img.gz file with the firmware.pinebook-pro.rk3399.img.gz file in order to create a DD-able image.<br />
<br />
The official images are '''not''' recommended yet until the display begins working and the installer properly installs the bootloader. Most users will want to see [[Pinebook Pro Debian Installer|Daniel Thompson's Debian Installer]] instead.<br />
<br />
<br />
== Gentoo Script ==<br />
[[File:GentooLogo.png|right|100px]]<br />
<br />
=== Gentoo Script for Pinebook Pro ===<br />
* This is a script that prepares a Gentoo arm64 stage 3 tarball for the Pinebook Pro<br />
** The script takes care of device specifics like an optimized make.conf, an overlay that provides kernel and firmware amongst others, and other miscellaneous fixes<br />
* The usual tarball setup as per [https://wiki.gentoo.org/wiki/Handbook:AMD64 Gentoo Handbook] is left to the user.<br />
* Forum thread with instructions at https://forum.pine64.org/showthread.php?tid=8765<br />
<br />
<br />
==Kali Script==<br />
[[File:Kali.jpeg|right|100px]]<br />
<br />
=== Kali Linux for Pinebook Pro ===<br />
* This is a script to create official Kali Linux OS images for the Pinebook Pro<br />
** The script carries out the build process in entirety and is Pinebook Pro specific<br />
* Please pull the latest [https://gitlab.com/kalilinux/build-scripts/kali-arm/blob/master/pinebook-pro.sh Kali Linux install script] from the project's GitLab.<br />
* For more information regarding building the OS image please read the README instruction at https://gitlab.com/kalilinux/build-scripts/kali-arm/blob/master/README.md<br />
<br />
<br />
==K1ss OS Script==<br />
[[File:K1ss.png|right|100px]]<br />
<br />
=== K1ss Linux for Pinebook Pro ===<br />
* This is a repository containing an unofficial port of KISS Linux to aarch64. The tarball is built for generic aarch64, currently being tested on the Pinebook Pro.<br />
* Please pull the latest [https://github.com/jedavies-dev/kiss-aarch64 K1ss Linux install script] from the project's GitHub.<br />
* * You can follow the ongoing discussion about K1ss Linux on the PINE64 forum (https://forum.pine64.org/showthread.php?tid=9304)<br />
<br />
<br />
==NixOS Script==<br />
[[File:nixos.png|right|100px]]<br />
<br />
=== NixOS for Pinebook Pro ===<br />
* This is instructions to install NixOS on the Pinebook Pro: https://nixos.wiki/wiki/NixOS_on_ARM/PINE64_Pinebook_Pro<br />
* Please pull the latest [https://github.com/samueldr/wip-pinebook-pro samueldr's repository ] from the project's GitHub.<br />
* * There is a good chance we will see Tier 1 support for aarch64, including the Pinebook Pro, in 2021 (https://github.com/NixOS/rfcs/pull/87)<br />
* * You can follow the ongoing discussion about NixOS on the PINE64 forum (https://forum.pine64.org/showthread.php?tid=10524)<br />
<br />
==SkiffOS for Pinebook Pro ==<br />
[[File:SkiffOS-Icon-1.png|right|100px]]<br />
<br />
=== SkiffOS Boot Image for Pinebook Pro ===<br />
* Instructions to build/install on the Pinebook Pro: https://github.com/skiffos/SkiffOS/tree/master/configs/pine64/book<br />
* Please pull the latest version from the project's GitHub.<br />
* Compiling the boot image takes approximately 30 minutes.<br />
* Easily configure the kernel, compiler, etc with Buildroot.<br />
* Pre-built ISOs will be available with the upcoming 2021.02 <br />
release.<br />
<br />
=== Skiff Core ===<br />
* Supports multiple distros running simultaneously.<br />
* Optionally build from scratch on device on first boot.<br />
* Pre-built multi-arch core container images are available.<br />
<br />
=== GentooLTO with KDE Apps ===<br />
<br />
* GentooLTO with O3 optimized KDE Desktop configuration.<br />
* Use <tt>SKIFF_CONFIG=pine64/book,core/pinebook_gentoo</tt><br />
* Default sign-in is username "core" w/ empty password.<br />
<br />
<br />
[[Category:PineBook Pro]]</div>Ura2