Enjoy Slackware 15.0!

Welcome to the Slackware Documentation Project

Trace:

Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Next revision 		Previous revision
slackwarearm:inst_sa64_cur_rk3399_pinebookpro [2021/10/26 15:24 (UTC)]
mozes 		slackwarearm:inst_sa64_cur_rk3399_pinebookpro [2021/12/13 11:09 (UTC)]
mozes removed
Line 1: Line 1:
-<note warning>October 2021 - wip - Slackware AArch64 is not yet released !</note>+<note warning>December 2021 - wip - Slackware AArch64 is not yet released !</note>
  
 +<note warning>This document is UNTESTED - it worked, but this author's Pinebook Pro is broken so it's impossible to verify</note>
  
 +<note warning>This has some RockPro64 references within the screenshots - these need updating. However, these are cosmetic only.</note>
  
 ====== Installing Slackware on the Pinebook Pro ====== ====== Installing Slackware on the Pinebook Pro ======
Line 8: Line 10:
 | Document name    | inst_sa64_cur_rk3399_pinebookpro | | Document name    | inst_sa64_cur_rk3399_pinebookpro |
 | Document purpose | Document the installation of Slackware Linux onto the Hardware Model: [[https://www.pine64.org/pinebook-pro/|Pinebook Pro]] | | Document purpose | Document the installation of Slackware Linux onto the Hardware Model: [[https://www.pine64.org/pinebook-pro/|Pinebook Pro]] |
 +| Version          | 1.00, Dec 2021 |
 | Author           | Stuart Winter <mozes@slackware> | | Author           | Stuart Winter <mozes@slackware> |
-| Date             | 25-Oct-2021 | +| Contributors     | Brent Earl | 
-| Version          | 1.00 |+
  
-==== Video Tutorial ==== 
  
-This tutorial is also available in video form. 
  
 ==== Installation Lifecycle ==== ==== Installation Lifecycle ====
  
-The Installation consists of nine distinct stages:+The Installation consists of a number of stages:
  
   - Acquiring all required hardware   - Acquiring all required hardware
Line 44: Line 45:
 | [[https://pine64.com/product/pinebook-pinephone-pinetab-serial-console/?v=0446c16e2e66|Serial console adapter]]| 3.5" audio jack wired version | Optional. This is useful for debugging during development, but its use precludes the ability to enable sound on the laptop. Most users will not use the Serial adapter. | | [[https://pine64.com/product/pinebook-pinephone-pinetab-serial-console/?v=0446c16e2e66|Serial console adapter]]| 3.5" audio jack wired version | Optional. This is useful for debugging during development, but its use precludes the ability to enable sound on the laptop. Most users will not use the Serial adapter. |
 | [[https://pine64.com/product/pinebook-pro-usb-c-docking-deck/|PINEBOOK Pro USB-C Docking Deck]] | The specific model for the Pinebook Pro | Recommended but optional. The Pinebook Pro has no onboard Ethernet, so this is used during the installer (but the installation media can also be stored on a USB stick).  For the Slackware Installer, other USB Ethernet adapters can be used - although this is the only one that has been tested. | | [[https://pine64.com/product/pinebook-pro-usb-c-docking-deck/|PINEBOOK Pro USB-C Docking Deck]] | The specific model for the Pinebook Pro | Recommended but optional. The Pinebook Pro has no onboard Ethernet, so this is used during the installer (but the installation media can also be stored on a USB stick).  For the Slackware Installer, other USB Ethernet adapters can be used - although this is the only one that has been tested. |
 +
 +== Note about the eMMC ==
 +
 +From the factory, your PinebookPro contains an eMMC storage module. 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 should be removed.
 +
  
 === Computing / Network Environment === === Computing / Network Environment ===
Line 50: Line 56:
 ^ Item ^ Specification ^ Notes ^ ^ Item ^ Specification ^ Notes ^
 | Host Computer: an Internet-connected computer running an existing Linux distribution | Preferably a full installation of Slackware x86/64, but any distribution that can provide the required Python environment and HTTP server module. The Host Computer needs approximately **5GB free storage** to download the required software assets.  **You must be able to obtain //root// access to this Host computer**.  | This will be used to download the Slackware distribution from the Internet, and serve the Pinebook Pro client to install Slackware over the LAN (Local Area Network).  | | Host Computer: an Internet-connected computer running an existing Linux distribution | Preferably a full installation of Slackware x86/64, but any distribution that can provide the required Python environment and HTTP server module. The Host Computer needs approximately **5GB free storage** to download the required software assets.  **You must be able to obtain //root// access to this Host computer**.  | This will be used to download the Slackware distribution from the Internet, and serve the Pinebook Pro client to install Slackware over the LAN (Local Area Network).  |
 +| Network DHCP server | Provide an IP address and routing information for the PinebookPro to be able to contact the Linux Host Computer (to download the Slackware tree) and the Internet (to set date via NTP) | This document expects the PinebookPro to be able to obtain an IP address via DHCP over the LAN.  However, you can also manually configure an IP address once the Slackware Installer has booted (note that a lack of DHCP server will stall the Installer by several seconds).  You could also copy the Slackware media to a USB stick and install from there.  This is outside of the scope of this document, however [[https://docs.slackware.com/howtos:network_services:dhcp_server_via_dnsmasq|this document]] describes how to set up a simple DHCP service on Slackware. |
  
 +<note tip>Most home routers equipped with Ethernet ports provide a DHCP server which should suffice for this setup</note>
  
 ===== Hardware Setup ===== ===== Hardware Setup =====
Line 121: Line 129:
  
 {{:slackwarearm:nvme_ribbon_connected_to_mainboard.jpg?400|}} {{:slackwarearm:nvme_ribbon_connected_to_mainboard.jpg?400|}}
 +
 +== Disconnect the battery bypass cable ==
 +
 +The battery bypass cable must be disconnected whilst the battery is attached.
 +
 +{{:slackwarearm:pinebookpro-bypasscable-disconnected.png?400|}}
  
  
 The hardware set up is now complete and should look like this: The hardware set up is now complete and should look like this:
  
-{{:slackwarearm:pinebookpro-complete-emmc-disabled.jpg?400|}}+{{:slackwarearm:pinebookpro-complete-emmc-removed.jpg?400|}}
  
-Note that in this image you can see the eMMC module is //disabled// but is physically present.  As explained above, if you have somewhere safe to keep it, it's recommended to remove the eMMC module to avoid it becoming loose during use. 
  
 Finally, screw the Pinebook Pro's case back together. Finally, screw the Pinebook Pro's case back together.
  
 The hardware setup is complete. The hardware setup is complete.
 +
  
 ===== Software and Network Environment Setup ===== ===== Software and Network Environment Setup =====
Line 196: Line 210:
 The U-Boot Boot Loader that will be installed onto the SPI flash: The U-Boot Boot Loader that will be installed onto the SPI flash:
 <code> <code>
-rsync -PavL $SLKSRV/platform/aarch64/bootware/recovery/rk3399/flash-spi-pinebookpro.img.xz .+rsync -PavL $SLKSRV/slackwarearm/platform/aarch64/bootware/recovery/rk3399/flash-spi-pinebookpro.img.xz . 
 +rsync -PavL $SLKSRV/slackwarearm/platform/aarch64/bootware/recovery/rk3399/flash-spi-pinebookpro.img.xz.asc .
 </code> </code>
  
 //The Bootware (recovery/initialisation) images are approximately 400KBytes in size.// //The Bootware (recovery/initialisation) images are approximately 400KBytes in size.//
  
-The Slackware Linux installer for the RK3399 AArch64 platform:+== Download the Slackware Linux installer for the RK3399 AArch64 platform ==
 <code> <code>
-rsync -PavL $SLKSRV/platform/aarch64/bootware/installer/slackwareaarch64-${SLKVER}/rk3399_generic.sdimg_latest.img.xz .+rsync -PavL $SLKSRV/slackwarearm/platform/aarch64/bootware/installer/slackwareaarch64-${SLKVER}/rk3399_generic.sdimg_latest.img.xz . 
 +rsync -PavL $SLKSRV/slackwarearm/platform/aarch64/bootware/installer/slackwareaarch64-${SLKVER}/rk3399_generic.sdimg_latest.img.xz.asc .
 </code> </code>
  
 //The Slackware Installer images are approximately 300MBytes in size.// //The Slackware Installer images are approximately 300MBytes in size.//
  
 +== Download the Slackware tree verficiation tool ==
 +<code>
 +rsync -PavL $SLKSRV/slackwarearm/platform/all/scripts .
 +</code>
  
-== Verify the assets ==+== Download the Slackware AArch64 tree == 
 + 
 +You will now download the Slackware distribution. This contains all of the software included within Slackware.
  
-Verify the digital signature of the Slackware Installer: 
 <code> <code>
-$ gpg2 --verify rk3399_generic-sdimg_*.img.xz.asc+rsync \ 
 +   --exclude '*/source/*' \ 
 +   --delete -Prlvv \ 
 +   $SLKSRV/slackwarearm/slackwareaarch64-${SLKVER} .
 </code> </code>
  
 +//The Slackware distribution is approximately 4.5GBytes in size.//
 +
 +
 +== Verify the assets ==
  
-Verify the digital signature of the Boot Loader:+Verify the digital signature of the verification tool:
 <code> <code>
-$ gpg2 --verify flash-spi-pinebookpro.img.xz.asc+gpg --verify-files scripts/slacksigchk.sh.asc
 </code> </code>
  
Line 225: Line 253:
  
 <code> <code>
-gpg: assuming signed data in 'rk3399_generic-sdimg_5.14.14_1.img.xz' +gpg: assuming signed data in 'scripts/slacksigchk.sh' 
-gpg: Signature made Mon 25 Oct 2021 06:07:44 PM BST+gpg: Signature made Wed 24 Nov 2021 06:07:44 PM BST
 gpg:                using RSA key F7ABB8691623FC33 gpg:                using RSA key F7ABB8691623FC33
 gpg: Good signature from "Slackware ARM (Slackware ARM Linux Project) <mozes@slackware.com>" [unknown] gpg: Good signature from "Slackware ARM (Slackware ARM Linux Project) <mozes@slackware.com>" [unknown]
Line 234: Line 262:
 </code> </code>
  
-== Download the Slackware AArch64 tree == 
  
-You will now download the Slackware distribution. This contains all of the software included within Slackware.+Verify the Bootware and Slackware tree:
  
 <code> <code>
-rsync \ +chmod 755 scripts/slacksigchk.sh 
-   --exclude '*/source/*' \ +./scripts/slacksigchk.sh slackwareaarch64-${SLKVER}
-   --delete -Prlvv \ +
-   $SLKSRV/slackwareaarch64-${SLKVER} .+
 </code> </code>
  
-//The Slackware distribution is approximately 4.5GBytes in size.//+<note warning>If you see 'BAD signature' you should re-download as it may have become corrupt.  If this doesn't help, drop a note to the [[https://www.linuxquestions.org/questions/slackware-arm-108/|Slackware ARM forum]]</note>
  
 === Write the Initialisation Bootware to the SD Card  === === Write the Initialisation Bootware to the SD Card  ===
  
-Slackware stores the U-Boot Boot Loader firmware within the SPI flash of the Hardware Models that use the RK3399 SoC (including the Pinebook Pro,  RockPro64 et al).+Slackware stores the U-Boot Boot Loader firmware within the SPI flash of the Hardware Models that use the RK3399 SoC (including the Pinebook Pro, RockPro64 et al).
  
 In this step, we'll write the Boot Loader firmware to the same Micro SD card that will later be used to contain the Slackware Installer, and subsequently the Slackware OS' /boot partition. In this step, we'll write the Boot Loader firmware to the same Micro SD card that will later be used to contain the Slackware Installer, and subsequently the Slackware OS' /boot partition.
Line 257: Line 282:
 == Elevate yourself to root == == Elevate yourself to root ==
  
-On your Host computer, obtain root:+On your Host Computer, obtain root:
  
-<note tip>The # prefix indicates that you're using the **root** user</note>+<note tip>The # prefix indicates that you're using the **root** user - it's not to be typed in!</note>
  
 <code> <code>
Line 300: Line 325:
 <note tip>You'll also observe the presence of //sdd// - often the USB adapter itself obtains a block device. You can ignore this as it's 0Bytes.</note> <note tip>You'll also observe the presence of //sdd// - often the USB adapter itself obtains a block device. You can ignore this as it's 0Bytes.</note>
  
-== Write the Bootware Initialisation Image to the Micro SD Card ==+=== Write the Bootware Initialisation Image to the Micro SD Card ===
  
 Still as the **root** user, we'll switch to the directory to which the the Slackware assets have been downloaded (see earlier steps): Still as the **root** user, we'll switch to the directory to which the the Slackware assets have been downloaded (see earlier steps):
Line 314: Line 339:
  
 <code> <code>
 +# dd if=/dev/zero of=/dev/sdc count=2 bs=1M    ## Replace /dev/sdc with the correct block device (presented above by the lsblk tool) on your Host Computer
 # xzcat flash-spi-pinebookpro.img.xz > /dev/sdc  ## Replace /dev/sdc with the correct block device (presented above by the lsblk tool) on your Host Computer # xzcat flash-spi-pinebookpro.img.xz > /dev/sdc  ## Replace /dev/sdc with the correct block device (presented above by the lsblk tool) on your Host Computer
 # sync # sync
 # exit # exit
 </code> </code>
- 
-The Bootware Initialisation image is now ready to boot on the Pinebook Pro. 
-You are ready to move into the Hardware Initialisation setup. 
  
  
Line 339: Line 362:
 In most cases you can simply wait until the process begins. In most cases you can simply wait until the process begins.
  
-Once the process completes, **power off** the Pinebook Pro : //hold the power button for approximately **8 seconds**//.+Once the process completes, //hold the power button for approximately **8 seconds**//.  The PinebookPro will power off. 
  
 === Any issues with installing to SPI flash === === Any issues with installing to SPI flash ===
Line 356: Line 380:
 If this doesn't work, you may need to try a few times.  There are other methods also outlined on the [[https://wiki.pine64.org/wiki/Pinebook_Pro_SPI|Pine64 wiki]]. If this doesn't work, you may need to try a few times.  There are other methods also outlined on the [[https://wiki.pine64.org/wiki/Pinebook_Pro_SPI|Pine64 wiki]].
          
-===== Installation Method: Installing Slackware ===== 
-     
-Write the Slackware Installer to the Micro SD card. 
-Start the HTTP server on the Linux Host Computer 
-Power on the Pinebook Pro 
-Ensure power is connected throughout the installation process. 
  
-Connect the Pinebook Pro docking station (or USB Ethernet adapter if not using the docking station)+===== Write the Slackware Installer image onto the MicroSD card =====
  
-Setting screen font for PineBook Pro in post installation screens+Now that the Boot Loader has been installed to the PinebookPro's SPI flash, we will install the Slackware Installer image onto the same MicroSD card.
  
-*** COLD BOOT - hold down for about 8 seconds after installer+  * Remove the MicroSD card from the PinebookPro 
 +  * Insert the MicroSD card back into the Host Computer (as in the earlier section)
  
-<note warning> Disconnect any USB devices that aren't required for the OS installation</note>+== Elevate yourself to root ==
  
 +On your Host Computer, obtain root:
  
-Start the HTTP server on the Linux Host Computer+<note tip>The # prefix indicates that you're using the **root** user</note>
  
-As your normal (not root) user on your Linux Host Computer, within the 'slackware' directory you created earlier:+<code> 
 +$ su -   ## Note the hyphen - it's required 
 +</code>
  
-== Determine the Linux Host Computer's IP address ==+== Write the Slackware Installer to the Micro SD card ==
  
-We will direct the Slackware Installer to download the packages from your Linux Host Computer, thus require its IP address.+Follow the instructions in the previous section to determine which block device name it occupies. 
 + 
 +<note tip>Typically the block device will remain the same (in this tutorial it's /dev/sdc) but you should verify each time using **lsblk**.</note> 
 + 
 +<note tip>The # prefix indicates that you're using the **root** user - it's not to be typed in!</note> 
 + 
 +Enter the directory into which the Slackware assets were downloaded previously: 
 +<code> 
 +# cd /home/mozes/slackware 
 +# xzcat rk3399_generic.sdimg_latest.img.xz > /dev/sdc ## Replace /dev/sdc with the correct block device 
 +# sync 
 +# exit 
 +</code> 
 + 
 +== Remove the MicroSD card from the Host Computer == 
 + 
 +You may now disconnect the USB adapter from the Host Computer and remove the MicroSD card. 
 + 
 +===== Start the installation media server ===== 
 + 
 +We will direct the Slackware Installer to download the packages from a web server that we'll run temporarily on your Linux Host Computer. 
 + 
 +== Determine the Linux Host Computer's IP address ==
  
 For most basic installations, the following command will provide the correct IP.  If your Linux Host Computer has a more complex setup, you'll need to determine the IP address yourself using //ifconfig// or one of the other tools. For most basic installations, the following command will provide the correct IP.  If your Linux Host Computer has a more complex setup, you'll need to determine the IP address yourself using //ifconfig// or one of the other tools.
Line 384: Line 428:
 <code> <code>
 $ hostname -I $ hostname -I
-192.168.1.15+192.168.1.1
 </code> </code>
  
-In this example, the IP address of the Linux Host Computer is 192.168.1.15+In this example, the IP address of the Linux Host Computer is **192.168.1.1**
  
  
-== Start the HTTP server ==+== Start the HTTP server on the Linux Host Computer ==
  
-On the Linux Host Computer, enter the Slackware distribution tree and start the HTTP web server.+As your normal (not root) user on your Linux Host Computer, we'll enter the Slackware AArch64 directory and start the HTTP web server:
  
 <code> <code>
-$ cd slackwareaarch64-*/+$ cd ~/slackware/slackwareaarch64-*/  
 $ python3 -m http.server $ python3 -m http.server
 </code> </code>
Line 403: Line 447:
 === Installing Slackware === === Installing Slackware ===
  
-The date on your system may be incorrect:+To proceed, you must have: 
 + 
 +  * Assembled the PinebookPro as documented above 
 +  * Connected the Docking station 
 +  * Connected the Ethernet cable, and have a DHCP server serving the network from which the PinebookPro can obtain an IP address 
 +  * Inserted the Micro SD card containing the Slackware Installer into the PinebookPro's MicroSD card slot 
 + 
 +== Begin installation == 
 + 
 +<note warning> Disconnect any USB storage devices that aren't required for the OS installation</note>  
 + 
 +== Power on the PinebookPro == 
 + 
 +Press the Power Button for aproximately two seconds 
 + 
 +After a few seconds, the you will see the following on screen: 
 + 
 +{{:slackwarearm:00-u-boot-bootinginstaller.jpg?400|}} 
 + 
 +It takes several seconds to load and boot the installer, and it may take several seconds more for any further output to appear on the screen. 
 +The process of obtaining an IP address via DHCP can also delay the ability to interact with the Installer. 
 + 
 +Once an IP address has been obtained, you will be presented with a prompt. 
 +Press **ENTER** 
 + 
 +{{:slackwarearm:01-activatevirtualconsole.jpg?400|}} 
 + 
 + 
 +== Set the keymap == 
 + 
 +{{:slackwarearm:02-setkeymap_a.jpg?400|}} 
 + 
 +{{:slackwarearm:03-_setkeymap_b.jpg?400|}} 
 + 
 +{{:slackwarearm:04-setkeymap_c.jpg?400|}} 
 + 
 +== Set the date/time == 
 + 
 +Sync the date from a highly-available NTP server:
  
 <code> <code>
Line 409: Line 491:
 hwclock -w hwclock -w
 </code> </code>
 +
 +
 +{{:slackwarearm:06-ntpdate.jpg?400|}}
 +
 +
 +== Setup disk partitions ==
 +
 +For this installation a basic partitioning scheme will be created.
 +
 +Partition 
 +
 +^ Partition number ^ Device name    ^ Size ^ Purpose ^
 +| 1                | /dev/nvme0n1p1 | 4GB   | Swap |
 +| 2                | /dev/nvme0n2p2 | Rest of storage | OS root ('/') partition |
 +
 +<note tip>/boot will reside on the Micro SD card and is automatically configured by the Slackware Installer</note>
 +
 +Open fdisk against the /dev/nvme0n1 block device (which will be your primary storage, and in these instructions is the NVME you screwed inside the laptop in the previous section).
 +
 +<code>
 +fdisk /dev/nvme0n1
 +</code>
 +
 +
 +
 +Create the Swap partition:
 +
 +{{:slackwarearm:pinebookpro-fdisk-dev-nvme0n1.jpg?400|}}
 +
 +Type 'n' for new partition:
 +
 +Type 'p' for primary partition type:
 +
 +Press ENTER for the 'First sector'
 +
 +Type '+4G' for the 'Last Sector'/size:
 +
 +
 +Change the partition type to 'Swap'.
 +Type 't' then hex code '82':
 +
 +{{:slackwarearm:09_-_fdisk-rpro64.jpg?400|}}
 +
 +Create the partition for the root filesystem ('/'):
 +
 +{{:slackwarearm:pinebookpro-fdisk-partition2-create.jpg?400|}}
 +
 +Type 'n' for new partition.
 +Press ENTER to accept the defaults - this will create partition 2 as the maximum size available.
 +
 +
 +Type 'a' to mark the root partition (number 2) as bootable
 +Type '2' to select partition 2.
 +
 +{{:slackwarearm:11 - fdisk-rpro64.jpg?400|}}
 +
 +Type 'p' to print to view the partition table.
 +
 +{{:slackwarearm:pinebookpro-fdisk-printout.jpg?400|}}
 +
 +Type 'w' to write the partition table:
 +
 +{{:slackwarearm:13 - fdisk-rpro64.jpg?400|}}
 +
 +fdisk will now exit.
 +
 +== Load the Setup menu ==
 +
 +{{:slackwarearm:14-startSlackSetup.jpg?400|}}
 +
 +== Setup Swap partition ==
 +
 +{{:slackwarearm:15-SlackSetup-screen.jpg?400|}}
 +
 +{{:slackwarearm:pinebookpro-swapspace-detected.jpg?400|}}
 +
 +{{:slackwarearm:17-SwapSpace-DefectCheck-rpro64.jpg?400|}}
 +
 +{{:slackwarearm:pinebookpro-swapspace-configured.jpg?400|}}
 +
 +== Select and format the partition for the OS' root file system ==
 +
 +{{:slackwarearm:pinebookpro-selectroot-storagedevice.jpg?400|}}
 +
 +{{:slackwarearm:pinebookpro-formatrootpartition.jpg?400|}}
 +
 +{{:slackwarearm:pinebookpro-selectfs-for-rootfs.jpg?400|}}
 +
 +{{:slackwarearm:pinebookpro-formattingrootpartition.jpg?400|}}
 +
 +== Resize /boot partition to full extent ==
 +
 +The Micro SD card that contains the /boot partition presently occupies approximately 1GB.
 +Most MicroSD cards are several GBs in size.  This option will resize the partition to its full capacity to avoid wasting storage.
 +If you plan on manually adding parttions to this later, you will want to choose 'No' here.
 +
 +<note important>It's important that the Micro SD card is **not** used for heavy read/writes as it'll damage it and will cause your system not to boot.  This option exists simply to avoid wasting space on the MicroSD card.</note>
 +
 +{{:slackwarearm:23-ResizebootFS-ask.jpg?400|}}
 +
 +{{:slackwarearm:24-ResizebootFS-inprogress-rpro64.jpg?400|}}
 +
 +{{:slackwarearm:25-ResizebootFS-complete.jpg?400|}}
 +
 +== Boot Loader Configuration ==
 +
 +The Installer will configure the Boot Loader and the OS' /etc/fstab automatically:
 +
 +{{:slackwarearm:26-UpdatingUBootconfig.jpg?400|}}
 +
 +{{:slackwarearm:27-AddedLinuxpartitions-rpro64.jpg?400|}}
 +
 +Note: the screenshot shows /dev/sda2. This is from the RockPro64 and needs replacing - it will be the NVME block device name.
 +
 +
 +== Select Source Media ==
 +
 +{{:slackwarearm:28-SourceMediaSelection.jpg?400|}}
 +
 +<note tip>The IP address here is the one you determine earlier within these instructions.  The port should always be 8000</note>
  
 Pick option //'5 - Install from FTP/HTTP server'// Pick option //'5 - Install from FTP/HTTP server'//
 <code> <code>
-URL: http://192.168.1.15:8000+URL: http://192.168.1.1:8000
 Directory: / Directory: /
 </code> </code>
  
-== Pre first boot tweaks == 
  
-Updating the Operating System Initial RAM Disk.  [[https://www.youtube.com/watch?v=t3wKXMENTXk|Video tutorial]]. +{{:slackwarearm:29-HTTPinstallationURL.jpg?400|}}
-USing os-initrd-mgr tool. +
-chroot+
  
 +{{:slackwarearm:30-HTTPinstallationDIR.jpg?400|}}
  
-== Post installation tweaks ==+{{:slackwarearm:31-HTTPInstallationDownloadConfirm.jpg?400|}}
  
-LCD brightness+{{:slackwarearm:31-HTTPinstallationDownloadTestResult.jpg?400|}}
  
-For Rock Pro - fAN+{{:slackwarearm:32-HTTPInstallation-PkgProcessing.jpg?400|}}
  
-=== Using the Serial adapter ===+== Package Series Selection ==
  
 +You can now choose the package sets to install.  The recommendation is to install everything.
 +A full Slackware installation will occupy approximately 15GB.
 +
 +<note tip>If you do not plan to use the graphical window manager such as KDE, you should de-select it.</note>
 +
 +{{:slackwarearm:33-PackageSeriesSelection.jpg?400|}}
 +
 +Pick the 'terse' option:
 +
 +{{:slackwarearm:34-SelectingInstallMode.jpg?400|}}
 +
 +The packages will begin installing:
 +
 +{{:slackwarearm:35-PackagesInstalling.jpg?400|}}
 +
 +== Configure the Console Settings ==
 +
 +If you plan on using the UART/'Serial' console, you should select 'No' here.
 +If you plan on exclusively using an HDMI monitor, you should pick 'Yes'.
 +
 +<note tip>This setting can be reset to the default by editing /boot/extlinux/extlinux.conf and removing the 'console=' setting once the OS has booted</note>
 +
 +{{:slackwarearm:35-ConsoleBootSettings-rpro64.jpg?400|}}
 +
 +== Install the Boot Loader to SPI flash ==
 +
 +If this is the first time you have installed Slackware, you must flash the Boot Loader.
 +The initial Boot Loader flash performed earlier in these instructions typically contains an older version of the Boot Loader, where as the version packaged within the Installer contains the latest tested version.
 +
 +{{:slackwarearm:36-InstallingBootLoader-SPIFlash-rpro64.jpg?400|}}
 +
 +{{:slackwarearm:37-InstallingBootLoader-SPIFlash-readytogo.jpg?400|}}
 +
 +{{:slackwarearm:38-InstallingBootLoader-SPIFlash-inprogress-rpro64.jpg?400|}}
 +
 +{{:slackwarearm:39-InstallingBootLoader-SPIFlash-complete.jpg?400|}}
 +
 +== Remove the Slackware Installer from the SD card ==
 +
 +The Micro SD card is transformed from being the Slackware Installer into the Slackware OS's /boot partition.
 +At this stage, if the installation has worked for you (at certain points in the Slackware installer you are past the point of no return) you can delete the Installer.
 +However, if something has gone wrong you can reset the PinebookPro and reboot the installer without having to re-deploy the Slackware Installer image from your Linux Host Computer.
 +
 +Generally you should say 'Yes' here.
 +
 +{{:slackwarearm:40-RemoveSlackInstaller-from-sdcard.jpg?400|}}
 +
 +== Post Installation Configuration ==
 +
 +The Slackware Installer will walk you through the standard Slackware setup.  The on-screen instructions will suffice.
 +
 +{{:slackwarearm:41-LoadGPMatboot.jpg?400|}}
 +
 +{{:slackwarearm:42-ConfigureNetwork.jpg?400|}}
 +
 +{{:slackwarearm:42-ConfigureNetwork-enterhostname-rpro64.jpg?400|}}
 +
 +{{:slackwarearm:42-ConfigureNetwork-enterDomainname.jpg?400|}}
 +
 +
 +{{:slackwarearm:43-ConfigureNetwork-ConnectViaVLAN.jpg?400|}}
 +
 +{{:slackwarearm:44-NetworkIPManagement-NetworkManager.jpg?400|}}
 +
 +{{:slackwarearm:45-ConfigureNetwork-Complete.jpg?400|}}
 +
 +{{:slackwarearm:46-ConfirmServicesToRun.jpg?400|}}
 +
 +
 +== Select a Console Font ==
 +
 +It's recommended for the RockPro64 and Pinebook Pro that a larger console font is configured.
 +
 +{{:slackwarearm:47-ConsoleFontConfig-Yes.jpg?400|}}
 +
 +
 +{{:slackwarearm:48-ConsoleFontConfig-FontChoice.jpg?400|}}
 +
 +The recommended font is 'ter-732b.psf'. This is the font used within the Installer.
 +
 +{{:slackwarearm:49-ConsoleFontConfig-ConfirmChoice.jpg?400|}}
 +
 +== Continue Post Installation Configuration ==
 +
 +{{:slackwarearm:50-HardwareClockSetting.jpg?400|}}
 +
 +{{:slackwarearm:51-TimeZoneConfig-Choose.jpg?400|}}
 +
 +{{:slackwarearm:55-ChooseDefaultVIeditor.jpg?400|}}
 +
 +== Configure GUI Window Manager ==
 +
 +This author recommends using XFCE as it's light weight versus KDE.
 +
 +{{:slackwarearm:56-ChooseWindowManager-xfce-selected.jpg?400|}}
 +
 +== Continue Post Installation Configuration ==
 +
 +{{:slackwarearm:57-rootpassword-asktoset.jpg?400|}}
 +
 +{{:slackwarearm:58-rootpassword-complete.jpg?400|}}
 +
 +== Slackware Setup Complete ==
 +
 +{{:slackwarearm:59-SetupComplete.jpg?400|}}
 +
 +{{:slackwarearm:60-Setupmenu-EXITselected.jpg?400|}}
 +
 +{{:slackwarearm:61-Setupcomplete-Rebooting.jpg?400|}}
 +
 +Generally you'll want to reboot into the OS.
 +
 +However, if you are planning on setting up RAID or need to customise the Operating System Initial RAM Disk, you should select 'Shell'.
 +
 +The Slackware OS will be found within '/mnt'.
 +You can use the 'os-initrd-mgr' tool ([[https://www.youtube.com/watch?v=t3wKXMENTXk|Video tutorial]]).
 +
 +
 +== Booting the Slackware OS ==
 +
 +{{:slackwarearm:62-OSBooting-uboot-rpro64.jpg?400|}}
 +
 +== Login to the Slackware OS ==
 +
 +{{:slackwarearm:63-OSBooted-loginprompt-rpro64.jpg?400|}}
 +
 +You may now login as 'root', using the password you set within the installer.
 +
 +== Quit the HTTP media server ==
 +
 +On your Linux Host Computer, you can return to the HTTP server that we started earlier on.
 +In the terminal window in which you started it, you will see the access logs from the Slackware Installer downloading the packages.
 +
 +Simple press CONTROL+c to quit it.
 +
 +You may now delete the slackwareaarch64 tree, or perhaps keep it around to subsequently update it.
 +
 +
 +===== Post Installation Configuration =====
 +
 +There are a few post-installation configuration tasks to complete.
 +
 +
 +=== Add a plebeian user ===
 +
 +You should add a plebeian (non-root) user using the 'adduser' tool.
 +
 +This is documented [[https://www.slackbook.org/html/essential-sysadmin.html|here]].
 +
 +=== LCD brightness ===
 +
 +The Slackware Installer automatically configures the maximum brightness, but this doesn't carry over to the OS.
 +
 +You may want to add this to /etc/rc.d/rc.local:
 +<code>
 +echo 4000 > /sys/class/backlight/edp-backlight/brightness
 +</code>
 +
 +This may be included within the OS as standard at some point.
 +
 +
 +===== Known bugs =====
 +
 +===== Using the Serial/UART adapter =====
 +
 +This documentation discusses using the RockPro64 without the UART/Serial console.
 +
 +If you'd like to use one, you'll need to adjust the switch that toggles Sound vs UART, and connect the adapter (details in the Hardware requirements section above).
 +
 +You can then connect the USB end of the adapter into your Linux Host Computer, and use the following command.
 +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).
 +
 +<code>
 +screen -T screen-256color /dev/ttyUSB0 115200
 +</code>
  
-     
-     
-====  =====References ==== 
-    https://wiki.pine64.org/wiki/Pinebook_Pro 

In Other Languages
QR Code
QR Code slackwarearm:inst_sa64_cur_rk3399_pinebookpro (generated for current page)