Installing on Debian, Ubuntu and Raspberry Pi¶
Debian packages give native system integration on Debian-based distributions such as Ubuntu, Linux Mint, and Raspberry Pi OS.
There are two ways to install them:
- Install with one command (recommended)
- Adds the Rimu Systems package repository, then installs the applications. New releases then arrive with your normal system updates, and the correct package for your computer is selected for you.
- Install a downloaded package
- For computers that cannot use the repository, such as a computer without internet access. You download and install each new release yourself.
Both methods need glibc 2.38 or later. See System requirements.
Install with one command¶
-
Open a terminal.
-
Run this command:
-
Enter your password when
sudoasks for it. -
Wait for the
SUCCESSmessage.
The command does these steps:
- It checks that your system can run the applications. If it cannot, the command stops before it changes anything and tells you why.
- It selects the correct package for your computer:
rpion Raspberry Pi OS, otherwiseamd64orarm64. - It installs the
rimusystems-repopackage, which adds the repository and its signing key. On Raspberry Pi OS this package isrimusystems-repo-rpi. - It installs RimuSDR, RimuDAX and RimuCAT.
If you installed an earlier release from a downloaded package, the command upgrades it. You do not need to remove it first, and your settings are kept.
Install only some applications¶
Put the application names at the end of the command:
Read the script before you run it¶
-
Download the script:
-
Read it:
-
Run it:
Set up the repository without the script¶
-
Download the repository package for your system:
-
Install it:
-
Install the applications:
Update¶
New releases arrive with your normal system updates. To update from a terminal:
Install a downloaded package¶
Choose the right package¶
Three builds are available. Find your hardware in this table, then download the file with that suffix.
| Your system | Package | Example |
|---|---|---|
| Intel or AMD 64-bit PC | amd64 |
rimusdr_<version>_amd64.deb |
| Raspberry Pi 4 or Pi 5, running Raspberry Pi OS | rpi |
rimusdr_<version>_rpi.deb |
| Any other ARM64 computer, not running Raspberry Pi OS | arm64 |
rimusdr_<version>_arm64.deb |
The arm64 and rpi packages are not interchangeable
Both packages report the same architecture to the package manager, so apt
installs either one on any ARM64 computer without an error. They are built
against different versions of Qt, and only the matching one runs.
If you install the wrong package, the application fails to start. Remove it, then install the correct package:
On a Raspberry Pi, always use rpi. Use arm64 only on ARM64 hardware that
does not run Raspberry Pi OS.
The one-command install selects the correct package for you.
Install from the command line¶
This is the most reliable method. It works on every Debian-based system, including those where the graphical installer does not.
Install RimuSDR first, then RimuDAX and RimuCAT. apt installs any required
dependencies automatically.
Standard PCs (amd64)¶
cd ~/Downloads
sudo apt install ./rimusdr_<version>_amd64.deb
sudo apt install ./rimudax_<version>_amd64.deb
sudo apt install ./rimucat_<version>_amd64.deb
Raspberry Pi OS (64-bit)¶
cd ~/Downloads
sudo apt install ./rimusdr_<version>_rpi.deb
sudo apt install ./rimudax_<version>_rpi.deb
sudo apt install ./rimucat_<version>_rpi.deb
Other ARM64 Linux (arm64)¶
For ARM64 computers that do not run Raspberry Pi OS, such as ARM64 servers, single-board computers, and ARM64 installations of Ubuntu or Debian.
cd ~/Downloads
sudo apt install ./rimusdr_<version>_arm64.deb
sudo apt install ./rimudax_<version>_arm64.deb
sudo apt install ./rimucat_<version>_arm64.deb
Why apt reports an unsandboxed download
Some systems show a message about the download being performed
"unsandboxed". This happens when you start the installer from a user folder
such as ~/Downloads.
The message is harmless. It does not show a problem with the package, it does not affect security or function, and the installation completes correctly. No action is necessary.
To prevent the message, install from a world-readable directory such as
/tmp with the same command.
Install with the graphical installer¶
-
Download the correct package for your system. See Choose the right package.
-
Save the file in your Downloads folder.
-
Double-click the
.debfile. One of these installers opens:- Ubuntu App Center
- Software Center or Software Installer
- GDebi (Linux Mint)
- Pop!_Shop (Pop!_OS)
- Archive Manager (Debian, Elementary, and some Ubuntu variants)
-
Click Install.
-
Enter your password.
If the file opens as a folder
Some systems do not associate .deb files with an installer. If you see the
package contents instead of an Install button, use the command-line
method above. It works on all systems.
Updates for downloaded packages¶
A downloaded package does not update itself. When a release is announced,
download the new .deb file and install it. This includes packages installed
with Ubuntu App Center, which does not manage updates for them.
To get updates automatically instead, run the one-command install. It upgrades the packages you already have.
Raspberry Pi notes¶
- Supported models
- Raspberry Pi 4 and Raspberry Pi 5. Earlier models are not supported.
- 64-bit operating system
- A 64-bit Raspberry Pi OS is required. The 32-bit version cannot run the package.
Raspberry Pi OS Bookworm is too old
RimuSDR needs glibc 2.38 or later. Raspberry Pi OS Bookworm ships glibc
2.36, so the application does not start on it and reports an error such as
GLIBC_2.38 not found.
Use Raspberry Pi OS based on Debian 13 (Trixie), released in October 2025 or later. To check the release your Pi runs:
After installation¶
- Launch from the menu
- The applications are in your system menu.
- Launch from a terminal
- Run
rimusdr,rimudax, orrimucat. - Updates
- With the one-command install, new releases arrive with your system updates. With a downloaded package, download and install each new release.
- Desktop integration
- Full integration, with icons and file associations.
- Uninstall
- See Uninstalling.
Next, activate your license. See the Activation Guide.