SARPi Project - Slackware ARM on a Raspberry Pi

rpi-update - An easier way to upgrade your Slackware ARM system?

IMPORTANT! This page contains some very significant and seminal information. Please make sure you read it thoroughly and fully understand the implications of what you're doing before attempting to upgrade your Slackware ARM system on the Raspberry Pi using the 'rpi-update' tool.

'rpi-update' is a 3rd-party tool created for Raspbian by Hexxeh which updates/upgrades your Raspberry Pi's boot-firmware, kernel, and kernel modules, using one simple command. This tool also works with Slackware ARM but is not in-line with the "Slackware way". It's very convenient and easy to use, and is available for those who aren't concerned about managing the update/upgrade process manually. 'rpi-update' is available as a seperate download and is not included within Slackware ARM, or any SARPi installer images or packages. Slackware ARM has it's own package management system (pkgtool) but 'rpi-update' circumvents all that and installs every thing for you in one go, 'apt-get -y install' fashion. Which isn't always the best thing to allow because you don't really know what's being installed, or upgraded, or overwritten, or deleted, on your Slackware ARM system. Using 'pkgtool', or 'slackpkg', puts you in total control of your package management on a Slackware system. Whereas, 'rpi-update' takes away that control and does what it's programmed to do, which is; upgrade the boot firmware, kernel, and kernel modules, after backing up any existing files, and say "Yes" to any questions. The upgrade process is entirely autonomous. Things can go wrong when you least expect it, and 'rpi-update' is no exception.

On Slackware ARM, the 'rpi-update' tool should be used WITH CAUTION! The tool itself, when executed, warns you that, "'rpi-update' should only be used if there is a specific reason to do so - for example, if asked to do so by a Raspberry Pi engineer." and most importantly, "DO NOT use 'rpi-update' as as part of the regular update process." See the screenshot below for reference.

It's your choice to use 'rpi-update', or not. Convenience is all well and good, but ignore the warning(s) at your own risk!

An alternative, and better, solution would be to manage/install any upgrades yourself using 'pkgtool', or 'slackpkg'. If required, the SARPi kernel, kernel modules, and boot firmware packages (.txz) are available on the SARPi downloads page and are updated quite often. Compiling a custom kernel is always an available option, if that's your preferred method of upgrading.

NB: If you choose to manage any Slackware packages yourself (i.e. installing, upgrading, removing), and are in need of instructions on how to perform this task, please refer to the Slackbook package management page on the Slackware Documentation Project website.

It goes without saying that automated processes can go wrong when you least expect it. So, it's always a good policy to back things up before you go ahead. If you want to use 'rpi-update' just make sure you have at least ~25MB free space on your /boot partition before running it, to avoid any issues.

** You shouldn't use 'rpi-update' to update Slackware ARM. You should use the manual method. Ultimately, the choice is entirely yours.

NB: Please be aware that the inclusion of, and any related 'rpi-update' content within, this website does not indicate that the SARPi Project condones or endorses the use of it, in any capacity. This is a tool for those who don't know any different/better, and best suited to those who are too lazy to learn or can't be bothered. The SARPi Project does NOT offer support on 'rpi-update' issues. You should submit any 'rpi-update' related questions, or support requests, to Hexxeh.

Installing rpi-update

Type the following command as 'root' user to download and install rpi-update:

root@myrasbox:~# wget -O /usr/bin/rpi-update && chmod +x /usr/bin/rpi-update

As 'root' user you can run rpi-update at any time to upgrade your kernel, kernel modules, and firmware.

The kernel version(s) installed by 'rpi-update' always have a "+" suffix (e.g. 4.4.9-v7+) and these are what you will be installing when you use 'rpi-update' to upgrade. The SARPi Project kernel versions always carry an "-arm" suffix (e.g. 4.4.8-v7-arm) which is what you will use and install with any of the Slackware ARM installers and kernel packages that are available from the SARPi downloads section. This is so you can tell which kernels have been built by the SARPi Project.

If you need to find out which kernel your Slackware ARM system is running you can do so with the 'uname -r' command.

root@myrasbox:~# uname -r

Running rpi-update

You can run 'rpi-update' by typing the following command:

root@myrasbox:~# 'rpi-update'

So go ahead and run it now.

rpi-update then checks your system against any new updates, backs up existing files, and upgrades them accordingly. You are given the option to say yes or no [Y/n] to the upgrade but other than that it's all automatic.

You should see that the system is being updated with the latest firmware, kernel, and kernel modules. In the examples, our system was using kernel 4.4.8-v7-arm and that's been upgraded to 4.4.9-v7+. The kernel version you'll update to will (hopefully) be a lot more recent.

If there were no errors, the update was a success and you are advised that a reboot is needed to activate the new firmware.

Type 'reboot' at the command prompt and press the enter key.

root@myrasbox:~# reboot

After rebooting

After the system has rebooted, at the login prompt enter the name of the normal user that you specified in the previous section of this tutorial (i.e. NOT 'root') and enter the password you've set for this user during the account creation process. Remember that we used 'dave' as an example for our normal user account name. You should enter your own username here.

When you are logged in to your Slackware ARM system as a normal user there may be occasions when you require 'root' access. To change from a normal user to 'root' user type 'su -' at the command prompt:

dave@myrasbox:~# su -

Enter the root user password when prompted. You should now be logged in as root user. This is how you should always change from a normal user to 'root' user on your Slackware ARM system.

When you need to change from root user back to a normal user you should use the 'exit' or 'logout' command, like this:

root@myrasbox:~# exit
root@myrasbox:~# logout

You're now logged in as 'dave'. You will not be prompted for a password when exiting from 'root' user back to a normal user.

NB: Always remember, 'root' user is all powerful on a Linux system and should only be used when abolutely necessary! It is IMPORTANT never to use the 'root' user for doing things that you can do under a normal user account.

Logging in as a normal user is always good policy. Sometimes after an update, logging in remotely (via ssh) as root is not permitted, which is an added security feature. To enable remote login via ssh with 'root' user you'll need to edit settings in the /etc/ssh/sshd_config file and allow it. Installing the SARPi rpi-hacks package (available from the downloads section) will also accomplish this. You can also achieve this by adding a ssh public key in the /root/.ssh/authorized_keys file. This is something we're not going to cover in this tutorial.

You now have the option to Optimise Your System Configuration and customise the system configuration and parameters of your Slackware ARM system.

Otherwise, continue to the the final section of this tutorial... Post-installation information

Updated: 2021-04-06 12:46:18 UTC

Disclaimer: The SARPi Project website is for non-commercial and general information purposes only. The content is provided by Penthux.NET and while we endeavour to keep information up to date and correct, we make no representations or warranties of any kind, express or implied, about the completeness, accuracy, reliability, suitability or availability with respect to the website or any information, software, products, services, or related graphics which is available on the website for any purpose. Any reliance you place on such information is therefore strictly at your own risk. In no event will Penthux.NET be liable for any loss or damage including without limitation, indirect or consequential loss or damage, or any loss or damage whatsoever arising from loss of data or profits arising out of, or in connection with, the use of this website or any of its contents. Through this website you are able to visit other websites which are not under our control. Penthux.NET has no influence over the nature, content or availability of any external URLs. The inclusion of any URLs does not necessarily imply a recommendation or endorsement of any content therein. Every effort is made to ensure the SARPi Project website remains accessible. However, Penthux.NET takes no responsibility for, and will not be liable for, the SARPi Project website being temporarily unavailable due to technical issues beyond our control. Penthux.NET is in no way affiliated with Slackware Linux, Inc, or the Linux Foundation, or the Raspberry Pi Foundation, or any of their members, trustees, partners, or associates.

SARPi Project uses cookies for website traffic & data analysis. [ Cookie Policy ]