considering if I should downgrade to Ubuntu 20…
A new Lime Suite release has been tagged on GitHub and packages are in the works, which should now include building for 22.04.
thanks!
I am posting the text of the error message that led me here in case it helps lead someone else here.
~$ sudo add-apt-repository -y ppa:myriadrf/drivers
Repository: 'deb https://ppa.launchpadcontent.net/myriadrf/drivers/ubuntu/ jammy main'
Description:
This PPA contains various SDR hardware drivers and is maintained by the Myriad-RF Packaging project.
For more details see: https://myriadrf.org/projects/packaging/
More info: https://launchpad.net/~myriadrf/+archive/ubuntu/drivers
Adding repository.
Adding deb entry to /etc/apt/sources.list.d/myriadrf-ubuntu-drivers-jammy.list
Adding disabled deb-src entry to /etc/apt/sources.list.d/myriadrf-ubuntu-drivers-jammy.list
Adding key to /etc/apt/trusted.gpg.d/myriadrf-ubuntu-drivers.gpg with fingerprint 11FC2E68126782B43762694F22C627172ECB91FE
Hit:1 http://us.archive.ubuntu.com/ubuntu jammy InRelease
Hit:2 http://us.archive.ubuntu.com/ubuntu jammy-updates InRelease
Hit:3 http://us.archive.ubuntu.com/ubuntu jammy-backports InRelease
Get:4 http://security.ubuntu.com/ubuntu jammy-security InRelease [110 kB]
Ign:5 https://ppa.launchpadcontent.net/myriadrf/drivers/ubuntu jammy InRelease
Err:6 https://ppa.launchpadcontent.net/myriadrf/drivers/ubuntu jammy Release
404 Not Found [IP: 185.125.190.52 443]
Get:7 http://security.ubuntu.com/ubuntu jammy-security/main amd64 DEP-11 Metadata [13.0 kB]
Get:8 http://security.ubuntu.com/ubuntu jammy-security/universe amd64 DEP-11 Metadata [12.4 kB]
Reading package lists... Done
E: The repository 'https://ppa.launchpadcontent.net/myriadrf/drivers/ubuntu jammy Release' does not have a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
~$ sudo apt update
Hit:1 http://us.archive.ubuntu.com/ubuntu jammy InRelease
Hit:2 http://us.archive.ubuntu.com/ubuntu jammy-updates InRelease
Hit:3 http://security.ubuntu.com/ubuntu jammy-security InRelease
Hit:4 http://us.archive.ubuntu.com/ubuntu jammy-backports InRelease
Ign:5 https://ppa.launchpadcontent.net/myriadrf/drivers/ubuntu jammy InRelease
Err:6 https://ppa.launchpadcontent.net/myriadrf/drivers/ubuntu jammy Release
404 Not Found [IP: 2620:2d:4000:1::3e 443]
Reading package lists... Done
E: The repository 'https://ppa.launchpadcontent.net/myriadrf/drivers/ubuntu jammy Release' does not have a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 22.04.1 LTS
Release: 22.04
Codename: jammy
Reviewing the ppa supported distributions only supports up to bionic at this time. Jammy is not yet included.
If you try again you should now get the latest Lime Suite (22.09.1) for jammy. It’s also available for focal and bionic.
hello
will there be ubuntu 24.04 noble build on PPA ?
Today (14/Jan/2026) on Ubuntu 22.04 I’m getting:
$ sudo add-apt-repository -y ppa:myriadrf/drivers
Repository: ‘deb Index of /myriadrf/drivers/ubuntu jammy main’
Description:
This PPA contains various SDR hardware drivers and is maintained by the Myriad-RF Packaging project.
For more details see: Packaging – MyriadRF
More info: https://launchpad.net/~myriadrf/+archive/ubuntu/drivers
Adding repository.
Found existing deb entry in /etc/apt/sources.list.d/myriadrf-ubuntu-drivers-jammy.list
Adding deb entry to /etc/apt/sources.list.d/myriadrf-ubuntu-drivers-jammy.list
Found existing deb-src entry in /etc/apt/sources.list.d/myriadrf-ubuntu-drivers-jammy.list
Adding disabled deb-src entry to /etc/apt/sources.list.d/myriadrf-ubuntu-drivers-jammy.list
Adding key to /etc/apt/trusted.gpg.d/myriadrf-ubuntu-drivers.gpg with fingerprint 11FC2E68126782B43762694F22C627172ECB91FE
Ign:1 Index of /myriadrf/drivers/ubuntu jammy InRelease
Hit:2 Index of /ubuntu jammy InRelease
Hit:3 http://us.archive.ubuntu.com/ubuntu jammy InRelease
Hit:4 http://us.archive.ubuntu.com/ubuntu jammy-updates InRelease
Hit:5 http://us.archive.ubuntu.com/ubuntu jammy-backports InRelease
Hit:6 http://us.archive.ubuntu.com/ubuntu jammy-security InRelease
Ign:1 Index of /myriadrf/drivers/ubuntu jammy InRelease
Ign:1 Index of /myriadrf/drivers/ubuntu jammy InRelease
Err:1 Index of /myriadrf/drivers/ubuntu jammy InRelease
Could not handshake: Error in the pull function. [IP: 10.46.133.5 3129]
Reading package lists… Done
W: Failed to fetch https://ppa.launchpadcontent.net/myriadrf/drivers/ubuntu/dists/jammy/InRelease Could not handshake: Error in the pull function. [IP: 10.46.133.5 3129]
W: Some index files failed to download. They have been ignored, or old ones used instead.
Any suggestions?
We need to make a new release of classic Lime Suite and at which point we will package for more recent Ubuntu versions. In the meantime are you able to build from source?
I can give it a go. Is there any chance of confusion due to having a partial install present already?
Not if all you did is try to install from the PPA and this failed. Just make sure that you don’t have any packages installed — e.g. ‘dpkg -l | grep lime’ — and if you do, remove them. Then build and install from source.
Somewhat off-topic, but I’ve just flashed an new PR5 and then (yes there is a typo!):
mkdir ~/LibLimSuite
cd ~/LibLimSuite
git clone GitHub - myriadrf/LimeSuite: Driver and GUI for LMS7002M-based SDR platforms
cd LimeSuite
git checkout stable
mkdir builddir
cd builddir
cmake ../
make -j2
#sudo make install
#sudo ldconfig
#cd LimeSuite/udev-rules
#sudo ./install.sh
resulting error is:
…/LimeSuite/src/lms7002m_mcu/MCU_File.cpp: In member function ‘void MCU_File::ReadHex(long unsigned int)’:
…/LimeSuite/src/lms7002m_mcu/MCU_File.cpp:340:21: error: ‘uint8_t’ was not declared in this scope
340 | uint8_t i = 0;
| ^~~~~~~
…/LimeSuite/src/lms7002m_mcu/MCU_File.cpp:4:1: note: ‘uint8_t’ is defined in header ‘’; this is probably fixable by adding ‘#include ’
3 | #include
+++ |+#include
4 |
…/LimeSuite/src/lms7002m_mcu/MCU_File.cpp:341:26: error: ‘i’ was not declared in this scope
341 | for (i = 0; uint8_t(i + 3) < count; ++i)
| ^
…/LimeSuite/src/lms7002m_mcu/MCU_File.cpp:346:28: error: ‘i’ was not declared in this scope
346 | header[i] = 0;
| ^
…/LimeSuite/src/lms7002m_mcu/MCU_File.cpp:382:30: error: ‘uint8_t’ was not declared in this scope
382 | for (i = uint8_t(type - ‘1’); uint8_t(i + 3) < count; ++i)
| ^~~~~~~
…/LimeSuite/src/lms7002m_mcu/MCU_File.cpp:382:30: note: ‘uint8_t’ is defined in header ‘’; this is probably fixable by adding ‘#include ’
make[2]: *** [src/CMakeFiles/LimeSuite.dir/build.make:121: src/CMakeFiles/LimeSuite.dir/lms7002m_mcu/MCU_File.cpp.o] Error 1
