[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_rockpro64 [2023/06/19 16:56 (UTC)] – mozes | slackwarearm:inst_sa64_rk3399_rockpro64 [2024/03/19 09:34 (UTC)] (current) – mozes | ||
---|---|---|---|
Line 7: | Line 7: | ||
| Platform | AArch64/ | | Platform | AArch64/ | ||
| Hardware Model |Rock Pro64 | | | Hardware Model |Rock Pro64 | | ||
- | | Document Version | 1.02, Apr 2023 | | + | | Document Version | 1.04, Mar 2024 | |
| Author | Stuart Winter < | | Author | Stuart Winter < | ||
| Contributors | Brenton Earl < | | Contributors | Brenton Earl < | ||
Line 116: | Line 116: | ||
* Connect the CPU fan or heat sink | * Connect the CPU fan or heat sink | ||
+ | |||
+ | |||
+ | <note tip>If you prefer hardware rather than software control for the fan over software, check out [[https:// | ||
+ | |||
+ | |||
* Connect the Wifi & Bluetooth module (optional) | * Connect the Wifi & Bluetooth module (optional) | ||
* Connect the storage (the image shows the USB-to-SATA adapter, but you may use the PCI card). If using the USB adapter, connect it to the **blue USB3.0 port**. | * Connect the storage (the image shows the USB-to-SATA adapter, but you may use the PCI card). If using the USB adapter, connect it to the **blue USB3.0 port**. | ||
Line 425: | Line 430: | ||
{{: | {{: | ||
+ | |||
+ | == Font size == | ||
+ | |||
+ | If you're using a smaller monitor, such as one with a screen size less than 20 inches, it may be necessary to adjust the console font size to ensure that menus and other interface elements fit correctly on the screen. | ||
+ | |||
+ | < | ||
+ | |||
== Set the date/time == | == Set the date/time == | ||
Line 588: | Line 600: | ||
{{: | {{: | ||
- | == 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 612: | Line 612: | ||
<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 == | ||
+ | |||
+ | 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> | ||
+ | |||
+ | {{: | ||
+ | |||
+ | {{: | ||
+ | |||
+ | {{: | ||
+ | |||
== Post Installation Configuration == | == Post Installation Configuration == | ||
The Slackware Installer will walk you through the standard Slackware setup. | The Slackware Installer will walk you through the standard Slackware setup. | ||
+ | |||
{{: | {{: | ||
Line 727: | Line 751: | ||
If your RockPro64 does not have an RTC battery backup, you may wish to configure it to [[https:// | If your RockPro64 does not have an RTC battery backup, you may wish to configure it to [[https:// | ||
- | ===== Managing Slackware on the RockPro64 ===== | + | ====== Managing Slackware on the RockPro64 |
- | == Keeping the Slackware OS up to date == | + | ===== 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 735: | Line 759: | ||
<note tip> | <note tip> | ||
- | === Loading Additional Linux Kernel Modules | + | |
+ | ===== Loading Additional Linux Kernel Modules | ||
+ | |||
+ | Often Kernel modules for discovered hardware will be automatically loaded, but occasionally you will need to manually configure the loading of some modules. | ||
+ | |||
+ | < | ||
+ | / | ||
+ | </ | ||
+ | |||
+ | This file is a shell script that is run as one of the last steps before the OS has fully booted. | ||
+ | |||
+ | Configuration files within the directory ''/ | ||
+ | |||
+ | ===== 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. | ||
- | An example of this would be RTCs (Real Time Clocks). | + | An example of this would be RTCs (Real Time Clocks) |
+ | |||
+ | <note important> | ||
To load Kernel modules during the early boot sequence, read: | To load Kernel modules during the early boot sequence, read: | ||
Line 755: | Line 794: | ||
- | + | ===== Use a graphical login manager | |
- | == Use a graphical login manager == | + | |
If you prefer to use a graphical login manager, you can configure the default runlevel as 4: | If you prefer to use a graphical login manager, you can configure the default runlevel as 4: | ||
Line 766: | Line 804: | ||
</ | </ | ||
- | == Disable KDE Suspend action == | + | ===== Slackware repository partition |
- | + | ||
- | If you are using KDE, you should disable ' | + | |
- | + | ||
- | {{: | + | |
- | + | ||
- | {{: | + | |
- | + | ||
- | Then Apply the settings. | + | |
- | + | ||
- | === Slackware repository partition === | + | |
The Slackware Installer image contains a type '' | The Slackware Installer image contains a type '' | ||
Line 794: | Line 822: | ||
<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 835: | Line 861: | ||
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> | ||
+ | |||
+ | {{: | ||
+ | |||
+ | {{: | ||
+ | |||
+ | {{: | ||
+ | |||