Pinebook Pro Troubleshooting Guide - Revision history

Dsimic: /* NVMe SSD issues */ Describe the 3.3 V regulator issues

2023-10-15T14:29:35Z

NVMe SSD issues: Describe the 3.3 V regulator issues

← Older revision		Revision as of 14:29, 15 October 2023
Line 114:		Line 114:
	== NVMe SSD issues ==		== NVMe SSD issues ==

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

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

			The output of the 3.3 V regulator inside the Pinebook Pro, which powers the M.2 SSD, becomes very noisy when the battery voltage drops below 3.9 V or so. This is a hardware issue of the Pinebook Pro that cannot be corrected without extensive hardware modifications, and it causes many M.2 SSDs to lock up under load and cause operating system crashes. The real trouble is that for some M.2 SSDs it takes a couple of hours of heavy I/O to lock up under these conditions, which may make them appear to be working reliably, while they eventually fail.

	== Keyboard and trackpad ==		== Keyboard and trackpad ==

The duck imagines: /* WiFi issues */

2023-07-03T20:36:00Z

WiFi issues

← Older revision		Revision as of 20:36, 3 July 2023
Line 92:		Line 92:
	** Very limited range, meaning you can make a connection if the Pinebook Pro is next to the WiFi router. But not the next room.		** Very limited range, meaning you can make a connection if the Pinebook Pro is next to the WiFi router. But not the next room.
	** Unreliable connections, that are also limited by range.		** Unreliable connections, that are also limited by range.
			* Every once in a great while, the kernel will just fail to detect the wifi hardware. (symptom: <code>ip link</code> shows no wlan0.) Only solution found so far is to hard-reset the machine. (Complete power-off then on again.)

	=== Bluetooth issues ===		=== Bluetooth issues ===

Fxc: Fixes

2023-04-02T21:24:08Z

Fixes

Show changes

Fxc at 15:32, 20 February 2023

2023-02-20T15:32:52Z

← Older revision		Revision as of 15:32, 20 February 2023
Line 198:		Line 198:
	Be extra careful if you open the PBP, the plastic parts of the shell, around the back corners or the hinges are really tiny and break easily.		Be extra careful if you open the PBP, the plastic parts of the shell, around the back corners or the hinges are really tiny and break easily.

	[[Category:~~PineBook~~ Pro]][[Category:Guide]]		[[Category:Pinebook Pro]][[Category:Guide]]

Fxc: style, page moved

2023-02-04T21:45:13Z

style, page moved

← Older revision		Revision as of 21:45, 4 February 2023
Line 1:		Line 1:

	=Useful Links=		= Useful Links =

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

	[[~~Pinebook_Pro_Hardware_Accessory_Compatibility~~\|Hardware Compatibility page]]		[[Pinebook Pro Hardware Accessory Compatibility\|Hardware Compatibility page]]

	[[Pinebook Pro Software ~~Release~~]]		[[Pinebook Pro Software Releases]]

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

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

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

	=Power And Boot=		= Power And Boot =

	== New from the factory - Pinebook Pro won't boot / power on ==		== New from the factory - Pinebook Pro won't boot / power on ==
Line 130:		Line 130:
	Using Fn+F7 to disable the touchpad will keep it from also disabling the keyboard.		Using Fn+F7 to disable the touchpad will keep it from also disabling the keyboard.

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

	== Key mapping ==		== Key mapping ==

Fxc: Moved, style

2023-02-02T14:01:43Z

Moved, style

← Older revision		Revision as of 14:01, 2 February 2023
Line 22:		Line 22:
	* The eMMC may have come loose during shipment. [[Pinebook Pro#Accessing the Internals - Disassembly and Reassembly\|Open the back]] and verify that the eMMC is firmly seated.		* The eMMC may have come loose during shipment. [[Pinebook Pro#Accessing the Internals - Disassembly and Reassembly\|Open the back]] and verify that the eMMC is firmly seated.
	* You may want to try unplugging the SD card daughterboard ribbon cable and see if it powers on (remove the battery and peel off a bit of the tape before unplugging it to avoid damage). If it does, try reseating it on both sides. It might have come loose during shipping.		* You may want to try unplugging the SD card daughterboard ribbon cable and see if it powers on (remove the battery and peel off a bit of the tape before unplugging it to avoid damage). If it does, try reseating it on both sides. It might have come loose during shipping.
	* It's possible that your eMMC is empty from the factory. Simply ~~[[NOOB\|~~create]] a bootable [[Pinebook_Pro#Pinebook_Pro_images\|SD card]] and see if your Pinebook Pro [[Pinebook_Pro#Boot_sequence_details\|boots]]. If so, you can then ~~[[NOOB\|~~write]] an OS image to the eMMC.		* It's possible that your eMMC is empty from the factory. Simply create a bootable [[Pinebook_Pro#Pinebook_Pro_images\|SD card]] and see if your Pinebook Pro [[Pinebook_Pro#Boot_sequence_details\|boots]]. If so, you can then write an OS image to the eMMC, see [[Getting started]].

	== Pinebook Pro will not power on after toggling the eMMC enable/disable switch ==		== Pinebook Pro will not power on after toggling the eMMC enable/disable switch ==

Fxc: fix

2023-01-15T10:46:19Z

fix

← Older revision		Revision as of 10:46, 15 January 2023
Line 7:		Line 7:

	[[Pinebook Pro Software Release]]		[[Pinebook Pro Software Release]]


	=Tips, tricks and other information for troubleshooting your Pinebook Pro=		=Tips, tricks and other information for troubleshooting your Pinebook Pro=
Line 106:		Line 105:
	= NVMe SSD issues =		= NVMe SSD issues =

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

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

Vincele: /* Cracks in the plastic */ Add more caution

2022-11-15T17:38:12Z

Cracks in the plastic: Add more caution

← Older revision		Revision as of 17:38, 15 November 2022
Line 196:		Line 196:

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

			Be extra careful if you open the PBP, the plastic parts of the shell, around the back corners or the hinges are really tiny and break easily.

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

Artcfox: Added Alternative Non-Invasive Lid Magnet Repositioning Method

2022-09-24T14:58:48Z

Added Alternative Non-Invasive Lid Magnet Repositioning Method

← Older revision		Revision as of 14:58, 24 September 2022
Line 56:		Line 56:
	# Reassemble using these steps in reverse order.		# Reassemble using these steps in reverse order.

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

			===Alternative Non-Invasive Lid Magnet Repositioning Method===
			*This method only takes a few seconds, and doesn't require disassembling your Pinebook Pro:
			# Turn on your Pinebook Pro so you can easily test when the internal magnet is in the correct position.
			# Open the lid.
			# Take a tiny 1/8" neodymium magnet, and place it along the right edge of the front bezel (LCD side) to locate the internal positioning magnet and discover the correct polarity. There should be one spot where it has the most attraction. Mark that spot.
			# Using a very strong neodymium magnet(s) oriented with the same polarity you discovered using the tiny magnet, carefully place it on the spot you marked, and slowly slide it down the bezel until the internal magnet is pulled into the proper position. I successfully used four 1/2" cube neodymium magnets stacked on top of each other each having 20lbs of pull force to accomplish this.
			# The internal magnet should be placed about 1 to 1.5cm lower than where it was originally. There should be no need for adhesive, as the magnet will stick to the LCD panel. For reference, the hall effect sensor that the magnet interacts with is in between the USB port and audio jack.
			# Remove all external magnets, and test that the internal magnet is positioned correctly by slowly closing the lid while watching the LCD screen to make sure it stays suspended when closed, and wakes up when opened.

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

	=WiFi And Bluetooth=		=WiFi And Bluetooth=

Mothenjoyer69: Wifi Issues: added note about changed networking hardware in the 2022 batch, and the new firmware required.

2022-08-23T03:31:59Z

Wifi Issues: added note about changed networking hardware in the 2022 batch, and the new firmware required.

← Older revision		Revision as of 03:31, 23 August 2022
Line 63:		Line 63:
	* First, check the privacy switches to make sure your WiFi is enabled. They are persistant. See [[Pinebook_Pro#Privacy_Switches\|Privacy Switches]]		* First, check the privacy switches to make sure your WiFi is enabled. They are persistant. See [[Pinebook_Pro#Privacy_Switches\|Privacy Switches]]
	* Next, you may have to modify the <code>/etc/NetworkManager/NetworkManager.conf</code> as root user, and replace <code>managed=false</code> with <code>managed=true</code>. Then reboot.		* Next, you may have to modify the <code>/etc/NetworkManager/NetworkManager.conf</code> as root user, and replace <code>managed=false</code> with <code>managed=true</code>. Then reboot.
			* If that doesn't work, and if <code>dmesg \| grep brcmfmac</code> reports missing firmware, you will need to manually add the brcmfmac43455-sdio.* firmware files. This is due to a quiet change in the 2022 hardware revision. This [https://github.com/reMarkable/brcmfmac-firmware repo] has been tested and confirmed to work by no112.
	* For connections that drop and resume too often, it might be due to WiFi power management from earlier OS releases. Later OS releases either removed WiFi power management, or default to full power. (Power management can be turned off via command line with <code>iw dev wlan0 set power_save off</code> or <code>iwconfig wlan0 power off</code>, although it is not persistent through re-boot.)		* For connections that drop and resume too often, it might be due to WiFi power management from earlier OS releases. Later OS releases either removed WiFi power management, or default to full power. (Power management can be turned off via command line with <code>iw dev wlan0 set power_save off</code> or <code>iwconfig wlan0 power off</code>, although it is not persistent through re-boot.)
	* For connections that drop under load on the default Debian, remove <code>iwconfig wlan0 power off</code> in the file <code>/etc/rc.local</code>.		* For connections that drop under load on the default Debian, remove <code>iwconfig wlan0 power off</code> in the file <code>/etc/rc.local</code>.