the frequency can,t load even if i changed it

louis3e

New Member
Joined
Jun 25, 2024
Messages
8
Reaction score
0
Credits
72
i got this on kali linux and ubuntu 24.4 [64 bit] in oracle vm virtualbox

the frequency can,t load even
if i changed it

──(ss8㉿kali)-[~]
└─$ grgsm_livemon
gr-osmosdr 0.2.0.0 (0.2.0) gnuradio 3.10.10.0
built-in source types: file fcd rtl rtl_tcp rfspace redpitaya
Using device #0 RTLSDRBlog Blog V4 SN: 00000001
Found Rafael Micro R828D tuner
RTL-SDR Blog V4 Detected
Exact sample rate is: 2000000.052982 Hz


please how i fix this admin
 

Attachments

  • rrrrrrrr.PNG
    rrrrrrrr.PNG
    151 KB · Views: 29
  • Capture2222222.PNG
    Capture2222222.PNG
    109.8 KB · Views: 28
  • rtrtrtrtttt.PNG
    rtrtrtrtttt.PNG
    352 KB · Views: 29


Looks like you need to upgrade the Osmocom driver - you can get it here - https://github.com/osmocom/rtl-sdr - but you will have to build it - also see this wiki - https://osmocom.org/projects/rtl-sdr/wiki - the Wiki tells you how to build it and what prerequisites you need

You can check the Synaptic Package Manager and search gr-osmosdr it may be newer and might work - it is in Debian repos v0.2.4-1 also from what I see on your photo you have v0.2.0 - I do not know if it is in Kali repos or not - the latest version is 2.0.2 according to - https://github.com/osmocom/rtl-sdr/tags

see this thread for more details if you want - https://www.linux.org/threads/mesa-...screenfailed-to-load-driver-zink.50534/page-2
 
Last edited:
i have build it
still on gr-osmosdr 0.2.0.0
how can i upgrade the Osmocom driver
 

Attachments

  • 1111111.PNG
    1111111.PNG
    339.2 KB · Views: 18
i have build it
still on gr-osmosdr 0.2.0.0
how can i upgrade the Osmocom driver
See my post #2 - "You can check the Synaptic Package Manager and search gr-osmosdr it may be newer and might work - it is in Debian repos v0.2.4-1 also from what I see on your photo you have v0.2.0"
 
Last edited:
Open Synaptic Package Manager in the Search box type in gr-osmosdr

1.png


click search when it finds it right click the file and select "Mark for Installation" then click "Apply"

I think you have gr-osmodsr instead of gr-osmosdr - type error - my bad
 
Last edited:
is installed already and i still got the same version gr-osmosdr 0.2.0.0
 

Attachments

  • 1111111111111111111111111.PNG
    1111111111111111111111111.PNG
    121.4 KB · Views: 16
is installed already and i still got the same version gr-osmosdr 0.2.0.0
did you uninstall/remove the old one first? sometimes it may cause problem if the old driver does not get overwritten correctly so it is better to remove the old before installing the new especially if you built the old driver and the new driver installs somewhere else
 
did you uninstall/remove the old one first? sometimes it may cause problem if the old driver does not get overwritten correctly so it is better to remove the old before installing the new especially if you built the old driver and the new driver installs somewhere else
yes
 
the problem is that
Again when i run grgsm_livemon can,t get any frequency load
but i need got something like this in terminal

grgsm_livemon

15 06 21 00 01 f0 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b
25 06 21 00 05 f4 f8 68 03 26 23 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b
49 06 1b 95 cc 02 f8 02 01 9c c8 03 1e 57 a5 01 79 00 00 1c 13 2b 2b
 
i got this

┌──(ss9㉿kali)-[~]
└─$ grgsm_scanner --debug
CPU Features: SSE2+ SSE4.1+ AVX+ FMA-
Using avx for xtrxdsp_iq16_sc32
Using avx for xtrxdsp_iq8_ic16
Using avx for xtrxdsp_iq16_ic16i
Using avx for xtrxdsp_iq8_ic8i
Using avx for xtrxdsp_sc32i_iq16
Using avx for xtrxdsp_iq8_sc32
Using avx for xtrxdsp_iq8_sc32i
Using avx for xtrxdsp_iq16_sc32i
Using avx for xtrxdsp_sc32_iq16
Using avx for xtrxdsp_ic16i_iq16

Try scan CCCH on 975-1023 arfcn`s:
Scanning: 0.00% done..
Args=
[INFO] [UHD] linux; GNU C++ version 13.2.0; Boost_108300; UHD_4.6.0.0+ds1-6
libusb: warning [libusb_exit] device 2.1 still referenced
libusb: warning [libusb_exit] device 1.3 still referenced
libusb: warning [libusb_exit] device 1.2 still referenced
libusb: warning [libusb_exit] device 1.1 still referenced
Found Rafael Micro R828D tuner
RTL-SDR Blog V4 Detected
Traceback (most recent call last):
File "/usr/bin/grgsm_scanner", line 797, in <module>
main()
File "/usr/bin/grgsm_scanner", line 792, in main
do_scan(options.samp_rate, options.band, options.speed,
File "/usr/bin/grgsm_scanner", line 590, in do_scan
scanner = wideband_scanner(rec_len=30 - speed,
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/bin/grgsm_scanner", line 444, in init
str(gsm.device.get_default_args(args)))
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/lib/python3/dist-packages/gnuradio/gsm/device.py", line 53, in get_default_args
devices = get_all_args("nofake")
^^^^^^^^^^^^^^^^^^^^^^
File "/usr/lib/python3/dist-packages/gnuradio/gsm/device.py", line 43, in get_all_args
return list(map(lambda dev: dev.to_string(), exclude(get_devices(hint))))
^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/lib/python3/dist-packages/gnuradio/gsm/device.py", line 40, in exclude
return [dev for dev in devices if not match(dev, filters)]
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/lib/python3/dist-packages/gnuradio/gsm/device.py", line 40, in <listcomp>
return [dev for dev in devices if not match(dev, filters)]
^^^^^^^^^^^^^^^^^^^
File "/usr/lib/python3/dist-packages/gnuradio/gsm/device.py", line 33, in match
if (k not in dev or dev[k] != v):
^^^^^^^^^^^^
TypeError: argument of type 'osmosdr.osmosdr_python.device_t' is not iterable
 

Attachments

  • 1121.PNG
    1121.PNG
    269.9 KB · Views: 13
Looks to me at some point you have installed the gr-gsm package from the apt repository as well, the package places its executables in /usr/bin/. The make install commands put the executable files in /usr/local/bin/ by default and you have not specified any options to cmake when you built it
 
okay
how can i build together correct
 

Attachments

  • 1112233.PNG
    1112233.PNG
    246.7 KB · Views: 15
  • 121212.PNG
    121212.PNG
    251.9 KB · Views: 14
If for any other reason you need cmake to be in /usr/bin. you can create a symbolic link in that directory: You need to specify the options in CMake when you build it to put it the correct place

CMake forum is here for help - https://discourse.cmake.org/ then click on Usage

The easiest way I have found is to just use Synaptic Package Manager and remove all of gr-osmosdr related software and reinstall only from the Synaptic Package Manager - right click and select "Mark for complete removal"
 
Last edited:

Members online


Top