Difference between revisions of "Pinebook Pro Troubleshooting Guide"

Jump to navigation Jump to search
m
(→‎WiFi issues: Added WiFi antenna cable loose fix.)
(22 intermediate revisions by 6 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=


== New from the factory - Pinebook Pro won't boot / power on ==
== New from the factory - Pinebook Pro won't boot / power on ==
* Some Pinebook Pros came from the factory with the eMMC switch in the disabled position. It should be switched towards the back / hinge to enable the eMMC.<br>
* Some Pinebook Pros came from the factory with the eMMC switch in the disabled position. It should be switched towards the back / hinge to enable the eMMC.
* The eMMC may have come loose during shipment. [https://wiki.pine64.org/index.php/Pinebook_Pro_Main_Page#Accessing_the_Internals_-_Disassembly_and_Reassembly Openthe back and verify that the eMMC is firmly seated.<br>
* 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 bootable SD card and see if your Pinebook Pro boots. If so, you can then 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 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 61: Line 61:


== WiFi issues ==
== WiFi issues ==
* First, check the privacy switches to make sure your WiFi is enabled. They are persistant. See [[Pinebook_Pro_Main_Page#Privacy_Switches|Privacy Switches]]
* 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.
* 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.)
Line 68: Line 68:
* After re-enabling WiFi via the privacy switch, you have to reboot to restore function. There is a work around for the default Debian, (and may work with others);
* After re-enabling WiFi via the privacy switch, you have to reboot to restore function. There is a work around for the default Debian, (and may work with others);
&nbsp; &nbsp; &nbsp; &nbsp; <code>sudo tee /sys/bus/platform/drivers/dwmmc_rockchip/{un,}bind <<< 'fe310000.dwmmc'</code>
&nbsp; &nbsp; &nbsp; &nbsp; <code>sudo tee /sys/bus/platform/drivers/dwmmc_rockchip/{un,}bind <<< 'fe310000.dwmmc'</code>
* On extremely rare occasions, the WiFi antenna connection is loose. To fix, simply open up the bottom, re-connect the WiFi antenna cable.<br>This may show up as any of the following symptoms:
* On extremely rare occasions, the WiFi antenna connection is loose. To fix, simply open up the bottom, re-connect the WiFi antenna cable. This may show up as any of the following symptoms:
** Can't connect to any network, but the network manager software sees the WiFi device, (so it has not been disabled by the Privacy Switch)
** Can't connect to any network, but the network manager software sees the WiFi device, (so it has not been disabled by the Privacy Switch)
** Very limited range, meaning you can make a connection if the Pinebook Pro is next to the WiFi router. But not the next room.
** Very limited range, meaning you can make a connection if the Pinebook Pro is next to the WiFi router. But not the next room.
Line 74: Line 74:


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


= Sound issues =


=Sound=
== Sound issues ==
* Many reports of no sound are due to the OS, incorrect settings, or other software problems (eg. PulseAudio). So first test to see if it is a software or hardware problem, by trying another OS via SD card.  (For example, if Debian is installed on the eMMC, try Ubuntu on SD.)  
* Many reports of no sound are due to the OS, incorrect settings, or other software problems (eg. PulseAudio). So first test to see if it is a software or hardware problem, by trying another OS via SD card.  (For example, if Debian is installed on the eMMC, try Ubuntu on SD.)  
* If you cannot get sound from the headphone jack, but can get sound from the speakers, then the headphone / UART console switch may be set to the UART mode. You can open the back and check the position of the switch. If set to UART mode, switch it to headphone mode. See the parts layout for the location and correct position of the switch.
* If you cannot get sound from the headphone jack, but can get sound from the speakers, then the headphone / UART console switch may be set to the UART mode. You can open the back and check the position of the switch. If set to UART mode, switch it to headphone mode. See the parts layout for the location and correct position of the switch.
Line 89: 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.
= 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&nbsp;GT/s) speed for the PCI Express link used by the NVMe SSD, reducing it down to Gen1 speed (2.5&nbsp;GT/s).  However, Linux distributions that use Linux kernels older than version 5.12 still configure the PCI Express link to run at Gen2 speed, which requires [https://forum.pine64.org/showthread.php?tid=11683 manual reconfiguration] to Gen1 speed in case system instability is experienced.  See also this [https://patchwork.kernel.org/project/linux-rockchip/patch/20200423150510.6216-1-pgwipeout@gmail.com/ related discussion]. This issue does not affect distros with recent (newer than May 2021) kernels such as Manjaro ARM which seem to work with no modifications.
Some PineBook Pro users have reported issues with the default settings for the APST (Autonomous Powe State Transition) power saving, which cause an NVMe drive to disappear from the system or lock up after a certain period of time.  Please see [https://forum.pine64.org/showthread.php?tid=11337&pid=87711#pid87711 this forum thread] for further information.
= Keyboard and trackpad =


== Random Duplicated Key-Presses ==


=Keyboard And Trackpad=
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 102: Line 121:
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 ==
* See this [https://gitlab.manjaro.org/manjaro-arm/packages/community/pinebookpro-post-install/blob/master/10-usb-kbd.hwdb /etc/udev/hwdb.d/10-usb-kbd.hwdb] for some key mapping tweaks
* See this [https://gitlab.manjaro.org/manjaro-arm/packages/community/pinebookpro-post-install/blob/master/10-usb-kbd.hwdb /etc/udev/hwdb.d/10-usb-kbd.hwdb] for some key mapping tweaks


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


= USB docks & USB C alternate mode video =
= USB docks & USB C alternate mode video =
Line 134: Line 152:


== After changing builtin LCD resolution, blank screen ==
== After changing builtin LCD resolution, blank screen ==
Some people find that the text or icons are too small, so they attempt to change the resolution of the built-in display. Afterwards, the display is blank.<br>
Some people find that the text or icons are too small, so they attempt to change the resolution of the built-in display. Afterwards, the display is blank.  
Use the following to fix when logged into a text console as yourself, (Control-Alt-F1 through F6). After listing the resolutions, select the native resolution, (1920x1080 aka 1080p).  
Use the following to fix when logged into a text console as yourself, pressing Control-Alt-F1 through F6. After listing the resolutions, select the native resolution, (1920x1080 aka 1080p).
 
<pre>export DISPLAY=:0.0
<pre>export DISPLAY=:0.0
xrandr -q
xrandr -q
xrandr -s [resolution]</pre>
xrandr -s [resolution]</pre>
Once your resolution is restored, try using the Tweak app to set scaling, instead.<br>
 
<br>
Once the screen resolution is restored, try using the software settings to configure the desired screen scaling.
 
If the above fix did not work, you can try this:
If the above fix did not work, you can try this:
* Using a text console, (Control-Alt-F1), login with your normal user ID
* Using a text console, (Control-Alt-F1), login with your normal user ID
Line 146: Line 166:
* Change the "width" value to "1920"
* Change the "width" value to "1920"
* Change the "height" value to "1080"
* Change the "height" value to "1080"
* If there is more than one monitor configuration listed, edit that one too.<br>Be careful to make no other changes. If needed, exit without saving and re-edit.
* If there is more than one monitor configuration listed, edit that one too. Be careful to make no other changes. If needed, exit without saving and re-edit.
* Save the file and exit.
* Save the file and exit.
* Login using the GUI and test
* Login using the GUI and test
* If you are still loggied in via the GUI, you will have to reboot using <code>sudo shutdown -r now</code><br>After the reboot, you should be able to login to the GUI login and have the resolution back to normal.
* If you are still loggied in via the GUI, you will have to reboot using <code>sudo shutdown -r now</code>. After the reboot, you should be able to login to the GUI login and have the resolution back to normal.
When you have restored usability to your Pinebook Pro's graphical screen, see this section on improving readability and usability:<br>
 
[[Pinebook_Pro#Improving_readability|Improving readability]]
After restoring the usability of your Pinebook Pro's graphical screen, also see [[Pinebook Pro#Improving readability|this section]] on improving readability and usability.


=Outer Shell=
=Outer Shell=
Line 160: Line 180:
* USB ports
* USB ports
* Top side, around the corners
* Top side, around the corners
This seems to apply to the first batches in 2019. Later versions of the keyboard and trackpad have used better plastic. With replacements now in the Pine64 Store, it's possible to simply order a replacement.<br>
 
<br>
This seems to apply to the first batches in 2019. Later versions of the keyboard and trackpad have used better plastic. With replacements now in the Pine64 Store, it's possible to simply order a replacement.
 
There have been a few reports of cracks in the plastic around the LCD display, but these appear to be less common. There are replacement LCDs with top cases available in the Pine64 Store.
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