[2024-feb-29] Sad news: Eric Layton aka Nocturnal Slacker aka vtel57 passed away on Feb 26th, shortly after hospitalization. He was one of our Wiki's most prominent admins. He will be missed.

Welcome to the Slackware Documentation Project

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
slackwarearm:inst_sa64_rk3399_pinebookpro [2023/10/23 17:48 (UTC)] – mozesslackwarearm:inst_sa64_rk3399_pinebookpro [2024/03/11 16:19 (UTC)] (current) – Removed KDE suspend action mozes
Line 6: Line 6:
 | Document name    | inst_sa64_cur_rk3399_pinebookpro | | Document name    | inst_sa64_cur_rk3399_pinebookpro |
 | Document purpose | Document the installmaation of Slackware Linux onto the Hardware Model: [[https://www.pine64.org/pinebook-pro/|Pinebook Pro]] | | Document purpose | Document the installmaation of Slackware Linux onto the Hardware Model: [[https://www.pine64.org/pinebook-pro/|Pinebook Pro]] |
-| Version          | 1.02, Sept 2023 |+| Version          | 1.04, Mar 2024 |
 | Author           | Stuart Winter <mozes@slackware> | | Author           | Stuart Winter <mozes@slackware> |
 | Collaborators    | Brenton Earl <el0226@slackware>  (R&D for the initial integration work) | | Collaborators    | Brenton Earl <el0226@slackware>  (R&D for the initial integration work) |
Line 98: Line 98:
 During the development of Slackware AArch64, it was found that the life span of these storage modules is short which makes them inappropriate for housing an Operating System. During the development of Slackware AArch64, it was found that the life span of these storage modules is short which makes them inappropriate for housing an Operating System.
 Whilst it's possible to use eMMC with Slackware, this documented installation process does not provide a supported path and the eMMC must be disabled. Whilst it's possible to use eMMC with Slackware, this documented installation process does not provide a supported path and the eMMC must be disabled.
 +
  
 == Move the eMMC control switch into the **down** position. == == Move the eMMC control switch into the **down** position. ==
Line 105: Line 106:
 To remove it, gently lift it up and out with your fingers. To remove it, gently lift it up and out with your fingers.
 </note> </note>
 +
 +
 +<note important>Newer versions of the Pinebook Pro do not permit disabling the eMMC via the switch, as depicted in the image below.  You must remove the eMMC module this case.</note>
 +
 +{{:slackwarearm:pbpro-emmc-inaccess.png?400|}}
  
 === Ensure Sound is enabled === === Ensure Sound is enabled ===
Line 370: Line 376:
 === Any issues with installing to SPI flash === === Any issues with installing to SPI flash ===
  
-Even if there's an existing distribution that has installed a Boot Loader to the SPI flash, the Slackware Micro SD card Recovery/Initialisation image should boot and work as described above. +The Slackware Micro SD card Recovery/Initialization image typically boots and operates as described, even if a distribution has already installed a Boot Loader onto the SPI flash. However, its success hinges on the configuration of the current SPI flash-embedded Boot Loader. If this Boot Loader isn't set up to boot from the SD card, you might need to circumvent the SPI flash to initiate the SD card boot.
-However, it depends how the boot loader that's currently occupying the SPI flash is configured - it may not boot the SD card. In which case you'll need to bypass the SPI flash.+
  
 +<note>The Pinebook Pro has an immutable first stage Boot Loader which, when the SPI flash doesn't contain an executable Boot Loader, will attempt to boot from the SD card.</note>
  
 == Bypass SPI flash - method 1 == == Bypass SPI flash - method 1 ==
Line 391: Line 397:
  
 This is also described in one of the [[https://youtu.be/knOqICIOwdM?t=2727|Slackware ARM Vlog episodes.]] This is also described in one of the [[https://youtu.be/knOqICIOwdM?t=2727|Slackware ARM Vlog episodes.]]
 +
 +== Bypass SPI flash - method 3 ==
 +
 +If you encounter difficulties launching the Slackware Boot Loader flashing tool and find that the pre-installed Linux distribution keeps booting, an option is to clear the SPI flash using that Linux distribution.
 +
 +Obtain 'root' on the Linux distribution:
 +
 +<code>
 +$ dd if=/dev/zero of=/dev/mtd0 bs=1M count=3
 +</code>
 +
 +Now insert the Slackware Boot Loader flashing SD card and reboot.
  
 == Bypass SPI flash - more information == == Bypass SPI flash - more information ==
Line 760: Line 778:
 {{:slackwarearm:60-Setupmenu-EXITselected.jpg?400|}} {{:slackwarearm:60-Setupmenu-EXITselected.jpg?400|}}
  
 +
 +<note warning>Some Pinebook Pro models encounter an issue where the MMC (SD card) interface fails to come online after a reboot. To resolve this, it's advisable to **power off** the machine rather than relying solely on a reboot.</note>
  
 {{:slackwarearm:61-Setupcomplete-Rebooting.jpg?400|}} {{:slackwarearm:61-Setupcomplete-Rebooting.jpg?400|}}
Line 839: Line 859:
 </code> </code>
  
- 
-== Disable KDE Suspend action == 
- 
-If you are using KDE, you should disable 'Suspend' within KDE's System Settings: 
- 
-{{:slackwarearm:slackarm-kdesystemsettings.png?400|}} 
- 
-{{:slackwarearm:slackarm-kde-powersettings.png?400|}} 
- 
-Then Apply the settings. 
  
 ====== Managing Slackware on the Pinebook Pro ====== ====== Managing Slackware on the Pinebook Pro ======
Line 1017: Line 1027:
 <note tip>This assumes that there are no other similar adapters occupying ''/dev/ttyUSB0''.  If so, you will need to adjust the device name accordingly (e.g. perhaps ''/dev/ttyUSB1'').</note> <note tip>This assumes that there are no other similar adapters occupying ''/dev/ttyUSB0''.  If so, you will need to adjust the device name accordingly (e.g. perhaps ''/dev/ttyUSB1'').</note>
  
 +
 +=== Boot from NVME rather than from uSD card ===
 +
 +The Slackware AArch64 installation is set to boot from the Micro SD card due to its high portability across various hardware models. Nevertheless, if your preference is to exclusively utilize the NVME, please refer to [[https://www.linuxquestions.org/questions/slackware-arm-108/pinebook-pro-boot-from-nvme-drop-requirement-for-booting-from-usd-card-4175732356/|this post]] for guidance.
 +
 +<note important>While booting from NVME offers the advantage of freeing up the SD Card slot, it's essential to note that encountering boot issues could pose recovery challenges. Unlike SD cards, which allow easy diagnosis and fixing by inserting them into another machine, troubleshooting NVME boot problems can be more complex.</note>
  
 ===== Known Limitations / Bugs ===== ===== Known Limitations / Bugs =====
Line 1056: Line 1072:
  
 https://forum.manjaro.org/t/hibernate-on-pinebook-pro/18045 https://forum.manjaro.org/t/hibernate-on-pinebook-pro/18045
- 
-=== Boot from NVME - drop requirement for booting from uSD card === 
- 
-The Slackware AArch64 installation boots from the Micro SD card because it's the most portable method (across Hardware Models). 
-However, it'd be ideal if the Pinebook Pro could boot from a partition on the NVME. 
- 
-This requires //mainline// U-Boot to support it (no patches!), and some work on the installer to support it. 
-Notes: 
-* Need to consider how the installer handles 'SLKboot' (SD card). Do we need to rename it to SLKinst and handle renaming it again to SLKboot on the PbPro and all other HWMs? Possibly not. Needs more thought 
- 
  
  

Trace:

slackwarearm:inst_sa64_rk3399_pinebookpro ()