[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.
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
slackwarearm:inst_sa64_rk3399_pinebookpro [2023/06/19 17:30 (UTC)] – mozes | slackwarearm:inst_sa64_rk3399_pinebookpro [2024/03/11 16:19 (UTC)] (current) – Removed KDE suspend action mozes | ||
---|---|---|---|
Line 5: | Line 5: | ||
^ ^ ^ | ^ ^ ^ | ||
| Document name | inst_sa64_cur_rk3399_pinebookpro | | | Document name | inst_sa64_cur_rk3399_pinebookpro | | ||
- | | Document purpose | Document the installation | + | | Document purpose | Document the installmaation |
- | | Version | + | | Version |
| Author | | Author | ||
| Collaborators | | Collaborators | ||
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 important> | ||
+ | |||
+ | {{: | ||
=== 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' | + | The Slackware Micro SD card Recovery/Initialization |
- | However, | + | |
+ | < | ||
== Bypass SPI flash - method 1 == | == Bypass SPI flash - method 1 == | ||
Line 389: | Line 395: | ||
[[https:// | [[https:// | ||
+ | |||
+ | This is also described in one of the [[https:// | ||
+ | |||
+ | == 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 ' | ||
+ | |||
+ | < | ||
+ | $ dd if=/ | ||
+ | </ | ||
+ | |||
+ | Now insert the Slackware Boot Loader flashing SD card and reboot. | ||
== Bypass SPI flash - more information == | == Bypass SPI flash - more information == | ||
Line 659: | Line 679: | ||
<note tip>This setting can be adjusted later by editing ''/ | <note tip>This setting can be adjusted later by editing ''/ | ||
- | == 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. | ||
- | |||
- | {{: | ||
- | |||
- | {{: | ||
- | |||
- | {{: | ||
- | |||
- | {{: | ||
== Remove the Slackware Installer from the SD card == | == Remove the Slackware Installer from the SD card == | ||
Line 684: | Line 692: | ||
<note tip>You may be tempted to retain the Slackware Installer, but note that the Installer contains Linux Kernel modules for the Kernel that the Installer was originally shipped with. This means that as soon as you upgrade the Slackware Kernel package, the Installer will fail to boot. The option to retain the Installer is present purely because on a number of occasions, this author only realised that the installation was incorrectly performed upon completion, and needed to reinstall. | <note tip>You may be tempted to retain the Slackware Installer, but note that the Installer contains Linux Kernel modules for the Kernel that the Installer was originally shipped with. This means that as soon as you upgrade the Slackware Kernel package, the Installer will fail to boot. The option to retain the Installer is present purely because on a number of occasions, this author only realised that the installation was incorrectly performed upon completion, and needed to reinstall. | ||
+ | |||
+ | == 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 most recent version. | ||
+ | |||
+ | When an upgrade is required, in most cases you'll see a screen like this which provides information about the currently installed Boot Loader and the newer version available: | ||
+ | |||
+ | {{: | ||
+ | |||
+ | |||
+ | If the installed Boot Loader matches the currently available version, you will be advised that flashing is unnecessary. | ||
+ | |||
+ | {{: | ||
+ | |||
+ | If you proceed with flashing, the work flow looks like this and takes approximately two minutes to complete. | ||
+ | <note important> | ||
+ | |||
+ | {{: | ||
+ | |||
+ | {{: | ||
+ | |||
+ | {{: | ||
Line 747: | Line 778: | ||
{{: | {{: | ||
+ | |||
+ | <note warning> | ||
{{: | {{: | ||
Line 827: | Line 860: | ||
- | == Disable KDE Suspend action | + | ====== Managing Slackware on the Pinebook Pro ====== |
- | If you are using KDE, you should disable ' | + | ===== Keeping the Slackware OS up to date ===== |
- | + | ||
- | {{: | + | |
- | + | ||
- | {{: | + | |
- | + | ||
- | Then Apply the settings. | + | |
- | + | ||
- | ===== Managing Slackware on the Pinebook Pro ===== | + | |
- | + | ||
- | === Keeping the Slackware OS up to date === | + | |
One of the preferred tools to keep your system up to date is [[slackware: | One of the preferred tools to keep your system up to date is [[slackware: | ||
Line 846: | Line 869: | ||
- | + | ===== Loading Additional Linux Kernel Modules within the OS Proper | |
- | + | ||
- | === Loading Additional Linux Kernel Modules within the OS Proper === | + | |
Often Kernel modules for discovered hardware will be automatically loaded, but occasionally you will need to manually configure the loading of some modules. | Often Kernel modules for discovered hardware will be automatically loaded, but occasionally you will need to manually configure the loading of some modules. | ||
Line 861: | Line 882: | ||
- | === Loading Additional Linux Kernel Modules early in the boot sequence === | + | ===== Loading Additional Linux Kernel Modules early in the boot sequence |
There are a number of peripherals that may require Kernel modules loading early on in the boot sequence. | There are a number of peripherals that may require Kernel modules loading early on in the boot sequence. | ||
Line 882: | Line 903: | ||
You can also add shell code here to initialise a peripheral - writing something to the peripheral' | You can also add shell code here to initialise a peripheral - writing something to the peripheral' | ||
- | === Slackware repository partition === | + | ===== Slackware repository partition |
The Slackware Installer image contains a type '' | The Slackware Installer image contains a type '' | ||
Line 900: | Line 921: | ||
<note tip>Most users simply leave the partition alone, as it causes no issues.</ | <note tip>Most users simply leave the partition alone, as it causes no issues.</ | ||
- | === Customising the Slackware Linux Kernel === | + | ===== Customising the Slackware Linux Kernel |
If you'd like to customise the Linux Kernel, the easiest way is to follow the [[slackwarearm: | If you'd like to customise the Linux Kernel, the easiest way is to follow the [[slackwarearm: | ||
- | === Reducing Boot Time === | + | ===== Reducing Boot Time ===== |
Slackware ARM ships with a generic OS InitRD (Operating System Initial RAM Disk - the environment that prepares the machine to boot the Operating System Proper), so as to support a wide range of Hardware Models. | Slackware ARM ships with a generic OS InitRD (Operating System Initial RAM Disk - the environment that prepares the machine to boot the Operating System Proper), so as to support a wide range of Hardware Models. | ||
Line 935: | Line 956: | ||
- | === Suspend to RAM === | + | ===== Suspend to RAM ===== |
To suspend, in a console its fast to test by running " | To suspend, in a console its fast to test by running " | ||
Line 948: | Line 969: | ||
The best way to add new software is to [[slackwarearm: | The best way to add new software is to [[slackwarearm: | ||
+ | |||
+ | |||
+ | ===== Managing the Boot Loader firmware ===== | ||
+ | |||
+ | During the Slackware installation process, you are offered the opportunity to flash the Boot Loader to the SPI flash. Occasionally, | ||
+ | |||
+ | Slackware provides a package '' | ||
+ | |||
+ | |||
+ | === Upgrading the Boot Loader firmware === | ||
+ | |||
+ | - Upgrade to the latest available version of the package '' | ||
+ | - As root, run the '' | ||
+ | |||
+ | In this example we'll run the Boot Loader management tool as the '' | ||
+ | < | ||
+ | $ su -c ' | ||
+ | </ | ||
+ | |||
+ | When an upgrade is required, in most cases you'll see a screen like this which provides information about the currently installed Boot Loader and the newer version available: | ||
+ | |||
+ | |||
+ | {{: | ||
+ | |||
+ | If you've wiped the Boot Loader from SPI flash or have installed a non-Slackware firmware build, you will see a screen like this where the existing installed Boot Loader is unrecognised: | ||
+ | |||
+ | |||
+ | {{: | ||
+ | |||
+ | If the installed Boot Loader matches the currently available version, you will be advised that flashing is unnecessary. | ||
+ | |||
+ | {{: | ||
+ | |||
+ | If you proceed with flashing, the work flow looks like this and takes approximately two minutes to complete. | ||
+ | <note important> | ||
+ | |||
+ | {{: | ||
+ | |||
+ | {{: | ||
+ | |||
+ | {{: | ||
Line 965: | Line 1027: | ||
<note tip>This assumes that there are no other similar adapters occupying ''/ | <note tip>This assumes that there are no other similar adapters occupying ''/ | ||
+ | |||
+ | === 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, | ||
+ | |||
+ | <note important> | ||
===== Known Limitations / Bugs ===== | ===== Known Limitations / Bugs ===== | ||
Line 978: | Line 1046: | ||
- | === Exploring === | + | ===== Exploring |
- | == Hibernate == | + | === Hibernate |
The ARM Trusted Firmware firmware does not support the deep sleep / hibernate functions yet. | The ARM Trusted Firmware firmware does not support the deep sleep / hibernate functions yet. | ||
Line 1004: | Line 1072: | ||
https:// | https:// | ||
- | |||
- | == 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 // | ||
- | Notes: | ||
- | * Need to consider how the installer handles ' | ||
- | |||