phase 2
OP25 Major New OP25 Release - Seeking Beta Testers
- Thread starter KA1RBI
- Start date
- Status
SquadCompanySGT
Member
- Joined
- Mar 13, 2020
- Messages
- 18
Can anyone help me with this problem everytime I try to run rx.py I get
Traceback (most recent call last):
File "./rx.py", line 32, in <module>
import numpy
ImportError: No module named numpy
HELP PLEASE
Traceback (most recent call last):
File "./rx.py", line 32, in <module>
import numpy
ImportError: No module named numpy
HELP PLEASE
Anyone have this running on a RasperryPI 4 on the latest RaspianOS? It is failing for me at this point (I ran the patch prior also).
-- Checking for module 'thrift'
-- Found thrift, version 0.13.0
CMake Error at /usr/lib/arm-linux-gnueabihf/cmake/gnuradio/FindTHRIFT.cmake:70 (GR_PYTHON_CHECK_MODULE):
Unknown CMake command "GR_PYTHON_CHECK_MODULE".
Call Stack (most recent call first):
/usr/share/cmake-3.18/Modules/CMakeFindDependencyMacro.cmake:47 (find_package)
/usr/lib/arm-linux-gnueabihf/cmake/gnuradio/gnuradio-runtimeConfig.cmake:24 (find_dependency)
/usr/lib/arm-linux-gnueabihf/cmake/gnuradio/GnuradioConfig.cmake:54 (include)
op25/gr-op25/CMakeLists.txt:97 (find_package)
-- Checking for module 'thrift'
-- Found thrift, version 0.13.0
CMake Error at /usr/lib/arm-linux-gnueabihf/cmake/gnuradio/FindTHRIFT.cmake:70 (GR_PYTHON_CHECK_MODULE):
Unknown CMake command "GR_PYTHON_CHECK_MODULE".
Call Stack (most recent call first):
/usr/share/cmake-3.18/Modules/CMakeFindDependencyMacro.cmake:47 (find_package)
/usr/lib/arm-linux-gnueabihf/cmake/gnuradio/gnuradio-runtimeConfig.cmake:24 (find_dependency)
/usr/lib/arm-linux-gnueabihf/cmake/gnuradio/GnuradioConfig.cmake:54 (include)
op25/gr-op25/CMakeLists.txt:97 (find_package)
wgbecks
Active Member
The problem you're having is due to the "New" Raspbian October 30, 2021 Release that is based on Debian (11) Bullseye. The good news is that both of the major OP25 repos will install and compile on previous Raspbian Buster releases.
I've spent numerous hours over the past few days wrestling with Raspbian Bullseye and am not having much success. However, I have found that the Boatbod repo will completely install GNU Radio, and successfully build op25 with the exception being that Airspy device support is broken.
Conversely, I have not been able to build the Osmocom repo with cmake bombing out with the exact error message that you have posted.
My advise for the present time would be to locate and download the Raspbian Buster May 7, 2021 image to reflash your SD with and start over.
Last edited:
Thank you, I will go that route instead.
wgbecks
Active Member
I just checked the Raspbian image archives and don't see the Raspbian 2020-05-07 release posted. However, you should be able to download and install the previous Buster release from the 2020-02-14 folder. URL: Index of /raspbian/images/raspbian-2020-02-14 (raspberrypi.org)
If you're new to building op25 on Raspbian, then be sure to edit /etc/apt/sources.list with SU privileges where it's necessary to read the imbedded note telling you to uncomment the third line in the file. Follow-up the edit with sudo apt-get update to refresh the apt repositories then then sudo apt-get upgrade -y that should serve to bring the image up to date before going on to build op25.
If you're new to building op25 on Raspbian, then be sure to edit /etc/apt/sources.list with SU privileges where it's necessary to read the imbedded note telling you to uncomment the third line in the file. Follow-up the edit with sudo apt-get update to refresh the apt repositories then then sudo apt-get upgrade -y that should serve to bring the image up to date before going on to build op25.
wgbecks
Active Member
My bad! That first line should have read: "Raspbian 2021-05-07" and not "Raspbian 2020-05-07".
I found a 2/2021 image and everything installed fine 
boatbod
Member
FWIW I just downloaded Raspbian V11 and was able to install and run boatbod op25 with no errors using both RTL and Airspy on an RPI4. I do have a vague recollection that I had to fix something in the cmake files to fix the "thrift" problem a good while ago when I did some initial compatibility testing with Bullseye. Unfortunately I don't recall exactly what I changed...
I just can't seem to get op25 to install.
Running Ubuntu 21.10.
Can confirm the source repos are enabled.
Gnuradio 3.8.2.0.
I have installed the gr3.8 patch.
The installer works great up to the cmake line, and then it chokes and dies.
This seems to be the error?
Full install log is here.
Any ideas?
Running Ubuntu 21.10.
Can confirm the source repos are enabled.
Gnuradio 3.8.2.0.
I have installed the gr3.8 patch.
The installer works great up to the cmake line, and then it chokes and dies.
This seems to be the error?
Code:
CMake Error at /usr/lib/x86_64-linux-gnu/cmake/gnuradio/FindTHRIFT.cmake:70 (GR_PYTHON_CHECK_MODULE):
Unknown CMake command "GR_PYTHON_CHECK_MODULE".Full install log is here.
Any ideas?
wgbecks
Active Member
It appears from your post that Ubuntu 21.10 is quite likely based upon Debian (11) Bullseye, the same as the new October 30, 2021 release of Raspbian OS for the Raspberry Pi.
At the present time, you'll either have to use an earlier release of Ubuntu or install the Boatbod repo that does compile on Bullseye until such time that the Osmocom team as patched their installer.
Yeah, I think you're right. I was able to install and run the Boatbod fork without a problem just now. Thanks for the helping me make sense of that error!
What attracted me to op25 in the first place was the new web UI, so I guess...I'll just have to wait! Bummer.
boatbod
Member
I haven't tried building it myself, but I do see that Max has pushed some changes for the cmake files. You might try a git pull and full rebuild.
What command should I use to update the Osmocom OP25 branch to the latest? I presume it's NOT the same command used to update the Boatbod branch? Because, I get this error when I use "git pull" :
ken@ken-VirtualBox:~/op25$ git pull
Updating 6764091..13a3bcc
error: Your local changes to the following files would be overwritten by merge:
cmake/Modules/GrSwig.cmake
op25/gr-op25/CMakeLists.txt
op25/gr-op25_repeater/CMakeLists.txt
Please commit your changes or stash them before you merge.
Aborting
ken@ken-VirtualBox:~/op25$
ken@ken-VirtualBox:~/op25$ git pull
Updating 6764091..13a3bcc
error: Your local changes to the following files would be overwritten by merge:
cmake/Modules/GrSwig.cmake
op25/gr-op25/CMakeLists.txt
op25/gr-op25_repeater/CMakeLists.txt
Please commit your changes or stash them before you merge.
Aborting
ken@ken-VirtualBox:~/op25$
boatbod
Member
The issue is caused by the gnuradio 3.8 patch modifying local copies of repository files. Save your config files then try this command sequence:
Code:
cd ~/op25
git checkout .
git pull
rm -rf build/*
cat gr3.8.patch | patch -p1
./install.shKA1RBI
Member
Thanks Bill
Initial reports (including yours) suggest the build problem with debian 11 is fixed now.
Mucking with the cmake build files is scary and there is always the chance of a regression - so as usual please report any anomalies...
Max
I can confirm that the latest commits have fixed the Bullseye issue for me. I was able to run the install script without errors on Ubuntu 21.10 (I did still have to run the gr3.8 patch first) Thank you!
Now I have to figure out how to install Python2 safely alongside Python3 to actually run it, but I'm getting closer!
Now I have to figure out how to install Python2 safely alongside Python3 to actually run it, but I'm getting closer!
boatbod
Member
That won't work. If you are installing on a gnuradio-3.8 system you need to be running op25 using python3 otherwise it's not going to be able to find the op25 libraries.
softwaretech
Member
- Joined
- Nov 14, 2019
- Messages
- 7
An interesting observation that may save some others headaches. During my testing and experiment and prior to installing OP25, I previously installed gnuradio and kept running into issues and errors. After some research, I decided to go ahead and remove/uncheck anything relating to gnuradio. After doing this, cloning a fresh load, and trying the install again, I was finally able to get the install to work more as expected.
- Status