Difference between revisions of "Pinebook Pro Troubleshooting Guide"

Jump to navigation Jump to search
m
(6 intermediate revisions by 4 users not shown)
Line 15: Line 15:
=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://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=
Line 23: Line 23:
* 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 create a [[Pinebook_Pro#Pinebook_Pro_images|bootable 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 [[NOOB|create]] a bootable [[Pinebook_Pro#Pinebook_Pro_images|SD card]] and see if your Pinebook Pro [[Pinebook_Pro#Boot_sequence_details|boots]]. If so, you can then [[NOOB|write]] an OS image to the eMMC.


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


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


Line 88: Line 88:
* See [https://gitlab.manjaro.org/manjaro-arm/packages/community/pinebookpro-audio manjaro-arm/pinebookpro-audio] for how to handle 3.5mm jack plug/unplug events with ACPID.
* See [https://gitlab.manjaro.org/manjaro-arm/packages/community/pinebookpro-audio manjaro-arm/pinebookpro-audio] for how to handle 3.5mm jack plug/unplug events with ACPID.
* Serveral users have reported that one internal speaker had reversed polarity. Thus, sound from the speakers is like an echo effect.
* Serveral users have reported that one internal speaker had reversed polarity. Thus, sound from the speakers is like an echo effect.
** Their is a software fix using alsamixer and then enable either "R invert" or "L invert", however, now the headphones have incorrect audio.
** There is a software fix using alsamixer and then enable either "R invert" or "L invert", however, now the headphones have incorrect audio.
** The permanent fix is to re-wire one speaker, though this requires soldering small wires.
** The permanent fix is to re-wire one speaker, though this requires soldering small wires.
* Sound playback may be affected by the "mirroring" between the right and left channels, which results in distorted sound image.  The root cause is the [https://linux.die.net/man/1/alsamixer ALSA mixer] setting named "DAC Stereo Enhancement", which needs to be changed to 0% to fix this issue.  Please see [https://forum.pine64.org/showthread.php?tid=12631&pid=87372#pid87372 this forum post] for further information.
* Sound playback may be affected by the "mirroring" between the right and left channels, which results in distorted sound image.  The root cause is the [https://linux.die.net/man/1/alsamixer ALSA mixer] setting named "DAC Stereo Enhancement", which needs to be changed to 0% to fix this issue.  Please see [https://forum.pine64.org/showthread.php?tid=12631&pid=87372#pid87372 this forum post] for further information.
Line 94: Line 94:
= 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, as of December 17, 2020, Linux distributions that use mainline Linux kernel still configure the PCI Express link to run at Gen2 speed, which requires [https://forum.pine64.org/showthread.php?tid=11683 manual reconfiguration] to Gen1 speed in case system instability is experienced.  See also this [https://patchwork.kernel.org/project/linux-rockchip/patch/20200423150510.6216-1-pgwipeout@gmail.com/ related discussion].
Many PineBook Pro users have reported issues with NVMe SSD drives, including random Linux lockups and crashes.  Some of these issues are related to the [https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=712fa1777207 RK3399's errata] that disables Gen2 (5 GT/s) speed for the PCI Express link used by the NVMe SSD, reducing it down to Gen1 speed (2.5 GT/s).  However, Linux distributions that use Linux kernels older than version 5.12 still configure the PCI Express link to run at Gen2 speed, which requires [https://forum.pine64.org/showthread.php?tid=11683 manual reconfiguration] to Gen1 speed in case system instability is experienced.  See also this [https://patchwork.kernel.org/project/linux-rockchip/patch/20200423150510.6216-1-pgwipeout@gmail.com/ related discussion]. This issue does not affect distros with recent (newer than May 2021) kernels such as Manjaro ARM which seem to work with no modifications.


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


= Keyboard and trackpad =
= Keyboard and trackpad =
== Random Duplicated Key-Presses ==
Whether caused by an error in the Hailuck Keyboard firmware, or a physical defect in the membrane, the Pinebook Pro keyboard may randomly register some key-presses twice. The solution to this problem is trivial. Simply run the following command:
<code>xkbset bouncekeys 20</code>
If this return the following error:
<code>bash: xkbset: command not found</code>
Or some other similar error, you will need to install the command. It can most likely be found in your distro's repository.
You may substitute some other value for 20 -- this number denoting the time in milliseconds during which successive, duplicate key-presses will be rejected -- with any value of your choice. If you are still receiving duplicates, consider increasing the number -- perhaps by half. If you are consistently writing "aple", try decreasing this number -- perhaps by 25%.


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


== ANSI Fn + F keys wrong for F9, F10, F11 and F12 ==
== ANSI Fn + F keys wrong for F9, F10, F11 and F12 ==
Line 171: Line 185:
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.


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

edits

Navigation menu