Multiple "Packages not found"

[YanskYManskY]

Dear all, dear John,

First of all I want to thank you John and all the others for your very inspiring contributions.

Problem:

Upon installing linhpsdr on Ubuntu Mate I stumble across the message : "package not found". Following the README for installing the "Prerequisites for installing the Debian Package" this is concerning installing: sudo apt-get install libpulse sudo apt-get install libsoundio sudo apt-get install libasound2 sudo apt-get install libsoapysdr

So, linhpsdr is not running. At start, showing multiple instanties of ip adresses from the same radio.Upon selectie one and starting the radio, linhpsdr crashes.

I am not an experienced Linux user. I tried endlessly, but cannot find a solution anywhere. What am I doing wrong?

Good health to all!

Kind regards, YanskY

[g0orx]

I have no experience of using Ubuntu Mate. What version are you running and on what computer and radio? Have you tried updating the software? Is it failing on all the libraries or just some of them - maybe a copy of the log. Also a copy of the log when linhpsdr crashes would help identify the problem. Multiple IP addresses for the same radio would indicate that is visible on more than one interface. Usually this is because it is visible on both wired and wireless networks.

-- John

[sq8mvy]

Hi YanskYManskY,

You have provided very little information. The logs that linhpsdr shows are a hint to solve the problems. From your description, I conclude that you still lack libfftw3-3 and the WDSP library - you need to compile it from source

Compile Linhpsdr from sources. The linhpsdr.deb package is a very old version. *-dev library packages and build-essential package are required to compile from source.

[YanskYManskY]

Hi John, thank you. Ubuntu MATE 1.24.0; Release 20.04 LTS (Focal Fossa) 64-bit PC: Intel® Core™ i7-4790K CPU @ 4.00GHz × 8 Memory 16GB

All software fresh installed and all updated.

Installing all okay: sudo apt-get install libfftw3-dev sudo apt-get install libpulse-dev sudo apt-get install libsoundio-dev sudo apt-get install libasound2-dev sudo apt-get install libgtk-3-dev sudo apt-get install libsoapysdr-dev

Librarys failing: sudo apt-get install libpulse sudo apt-get install libsoundio sudo apt-get install libsoapysdr

Copy of the log when installing these 3 librarys:

yansky@yansky-desktop:~$ sudo apt-get install libpulse [sudo] password for yansky: Reading package lists... Done Building dependency tree
Reading state information... Done E: Unable to locate package libpulse

yansky@yansky-desktop:~$ sudo apt-get install libsoundio Reading package lists... Done Building dependency tree
Reading state information... Done E: Unable to locate package libsoundio

yansky@yansky-desktop:~$ sudo apt-get install libsoapysdr Reading package lists... Done Building dependency tree
Reading state information... Done E: Unable to locate package libsoapysdr

Copy of the log when trying to run RadioBerry with Linhpsdr:

yansky@yansky-desktop:~$ sudo linhpsdr Build: 2020-04-18 Beta GTK+ version 3.24.18 sysname: Linux nodename: yansky-desktop release: 5.4.0-26-generic version: #30-Ubuntu SMP Mon Apr 20 16:58:30 UTC 2020 machine: x86_64 opengl: 0 Creating wisdom file: /root/.local/share/linhpsdr/ discovery protocol1_discovery discover: looking for HPSDR devices on lo discover: bound to lo discover_receive_thread discovery: bytes read -1 discovery: recvfrom socket failed for discover_receive_thread: Resource temporarily unavailable discovery: exiting discover_receive_thread discover: exiting discover for lo discover: looking for HPSDR devices on enp0s25 discover: bound to enp0s25 discover_receive_thread discovered: received 60 bytes discovery: found device=6 software_version=40 status=2 address=192.168.8.170 (00:01:02:03:04:05) on enp0s25 discovered: received 60 bytes discovery: found device=6 software_version=40 status=2 address=192.168.8.170 (00:01:02:03:04:05) on enp0s25 discovery: bytes read -1 discovery: recvfrom socket failed for discover_receive_thread: Resource temporarily unavailable discovery: exiting discover_receive_thread discover: exiting discover for enp0s25 discovery found 2 devices discovery: found device=6 software_version=40 status=2 address=192.168.8.170 (00:01:02:03:04:05) on enp0s25 discovery: found device=6 software_version=40 status=2 address=192.168.8.170 (00:01:02:03:04:05) on enp0s25 protocol2_discover: looking for HPSDR devices on enp0s25 protocol2_discover: bound to enp0s25 192.168.8.148 255.255.255.0 protocol2_disovery: thread_id=0x5606c99a9400 protocol2_discover: bytes read -1 protocol2_discover: recvfrom socket failed for discover_receive_thread: Resource temporarily unavailable protocol2_discover: exiting protocol2_discover_receive_thread protocol2_discover: exiting discover for enp0s25 protocol2_discovery found 2 devices discovery: found protocol=0 device=6 software_version=40 status=2 address=192.168.8.170 (00:01:02:03:04:05) on enp0s25 discovery: found protocol=0 device=6 software_version=40 status=2 address=192.168.8.170 (00:01:02:03:04:05) on enp0s25 main: discovery found 2 devices discovered: 0 device=6 adding Hermes Lite discovered: 1 device=6 adding Hermes Lite tree_selection_changed_cb tree_selection_changed_cb: selected=Hermes Lite,1,4.0,192.168.8.170,00:01:02:03:04:05 tree_selection_changed_cb: first=Hermes Lite,1,4.0,192.168.8.170,00:01:02:03:04:05 found 0 starting Linux HPSDR (Beta): Hermes Lite P1 v4.0 192.168.8.170 (00:01:02:03:04:05) on enp0s25 create_radio for Hermes Lite 6 loadProperties: /root/.local/share/linhpsdr/00-01-02-03-04-05.props audio_get_backend_name: ALSA audio: create_audio: USE_SOUNDIO: 3 ALSA ALSA lib pcm_route.c:869:(find_matching_chmap) Found no matching channel map ALSA lib pcm_route.c:869:(find_matching_chmap) Found no matching channel map ALSA lib pcm_route.c:869:(find_matching_chmap) Found no matching channel map Cannot connect to server socket err = No such file or directory Cannot connect to server request channel jack server is not running or cannot be started JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock Cannot connect to server socket err = No such file or directory Cannot connect to server request channel jack server is not running or cannot be started JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock ALSA lib pcm_oss.c:377:(_snd_pcm_oss_open) Unknown field port ALSA lib pcm_oss.c:377:(_snd_pcm_oss_open) Unknown field port ALSA lib pulse.c:242:(pulse_connect) PulseAudio: Unable to connect: Connection refused

ALSA lib pulse.c:242:(pulse_connect) PulseAudio: Unable to connect: Connection refused

ALSA lib pcm_dmix.c:1024:(snd_pcm_dmix_open) The dmix plugin supports only playback stream ALSA lib pcm_dmix.c:1024:(snd_pcm_dmix_open) The dmix plugin supports only playback stream ALSA lib pcm_dsnoop.c:577:(snd_pcm_dsnoop_open) The dsnoop plugin supports only capture stream ALSA lib pcm_dsnoop.c:577:(snd_pcm_dsnoop_open) The dsnoop plugin supports only capture stream ALSA lib pcm_usb_stream.c:508:(_snd_pcm_usb_stream_open) Unknown field hint ALSA lib pcm_dsnoop.c:577:(snd_pcm_dsnoop_open) The dsnoop plugin supports only capture stream ALSA lib pcm_dsnoop.c:577:(snd_pcm_dsnoop_open) The dsnoop plugin supports only capture stream ALSA lib pcm_dsnoop.c:577:(snd_pcm_dsnoop_open) The dsnoop plugin supports only capture stream ALSA lib pcm_dsnoop.c:577:(snd_pcm_dsnoop_open) The dsnoop plugin supports only capture stream ALSA lib pcm_dsnoop.c:577:(snd_pcm_dsnoop_open) The dsnoop plugin supports only capture stream ALSA lib pcm_dsnoop.c:577:(snd_pcm_dsnoop_open) The dsnoop plugin supports only capture stream ALSA lib pcm_usb_stream.c:508:(_snd_pcm_usb_stream_open) Unknown field hint ALSA lib pcm_dmix.c:1024:(snd_pcm_dmix_open) The dmix plugin supports only playback stream ALSA lib pcm_dsnoop.c:577:(snd_pcm_dsnoop_open) The dsnoop plugin supports only capture stream ALSA lib pcm_usb_stream.c:508:(_snd_pcm_usb_stream_open) Unknown field hint n_input_devices=32 create_transmitter: channel=8 transmitter_init_analyzer: width=0 pixels=0 update_timer: fps=3 Segmentation fault yansky@yansky-desktop:~$

Added screenshot Linhpsdrselecting the RadioBerry:

[YanskYManskY]

@ SQ*8MVY: Appreciated.

yansky@yansky-desktop:~$ sudo apt-get install libfftw3-3 Reading package lists... Done Building dependency tree
Reading state information... Done libfftw3-3 is already the newest version (3.3.8-2ubuntu1). 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

WDSP compiling just fine.

Just followd the README. Which source to take and to find where?

[sq8mvy]

Ubuntu has:

• libpulse0 and libpulse-dev
• libsoapysdr0.6 and libsoapysdr-dev
• libsoundio1 and libsoundio-dev

Do not run Linhpsdr with root privileges only as a normal user

[YanskYManskY]

@ Pawel, tnx!

yansky@yansky-desktop:~$ sudo apt-get install libpulse0 Reading package lists... Done Building dependency tree
Reading state information... Done libpulse0 is already the newest version (1:13.99.1-1ubuntu3). 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

yansky@yansky-desktop:~$ sudo apt-get install libpulse-dev Reading package lists... Done Building dependency tree
Reading state information... Done libpulse-dev is already the newest version (1:13.99.1-1ubuntu3). 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

yansky@yansky-desktop:~$ sudo apt-get install libsoapysdr0.6 Reading package lists... Done Building dependency tree
Reading state information... Done E: Unable to locate package libsoapysdr0.6 E: Couldn't find any package by glob 'libsoapysdr0.6' E: Couldn't find any package by regex 'libsoapysdr0.6' yansky@yansky-desktop:~$

[YanskYManskY]

@ Pawel yansky@yansky-desktop:~$ sudo apt-get install libsoapysdr0.6 Reading package lists... Done Building dependency tree
Reading state information... Done E: Unable to locate package libsoapysdr0.6 E: Couldn't find any package by glob 'libsoapysdr0.6' E: Couldn't find any package by regex 'libsoapysdr0.6'

[sq8mvy]

You can have a newer version of the library in the repository - a higher version number Please show what the command returns: apt search libsoapy

[YanskYManskY]

@ Pawel,tnx apreciated :-) yansky@yansky-desktop:~$ apt show libsoapy N: Unable to locate package libsoapy N: Unable to locate package libsoapy E: No packages found

[sq8mvy]

I'm sorry, my typo apt search libsoapy

[YanskYManskY]

:-) yansky@yansky-desktop:~$ apt search libsoapy Sorting... Done Full Text Search... Done libsoapysdr-dev/focal,now 0.7.2-1 amd64 [installed] SoapySDR library development files

libsoapysdr-doc/focal,focal 0.7.2-1 all SoapySDR library development documentation

libsoapysdr0.7/focal,now 0.7.2-1 amd64 [installed,automatic] software defined radio interface library

soapysdr-module-airspy/focal 0.1.2-2build1 amd64 Airspy device support for SoapySDR (default version)

soapysdr-module-all/focal 0.7.2-1 amd64 All device support for default version of SoapySDR (metapackage)

soapysdr-module-audio/focal 0.1.1-2build1 amd64 Audio device support for SoapySDR (default version)

soapysdr-module-bladerf/focal 0.4.1-2build1 amd64 bladeRF device support for SoapySDR (default version)

soapysdr-module-hackrf/focal 0.3.3-3build1 amd64 HackRF device support for SoapySDR (default version)

soapysdr-module-lms7/focal 20.01.0+dfsg-2 amd64 Lime Microsystems LMS7 device support for SoapySDR (default version)

soapysdr-module-mirisdr/focal 0.2.5-3build2 amd64 Mirics SDR device support for SoapySDR (default version)

soapysdr-module-osmosdr/focal 0.2.5-3build2 amd64 OsmoSDR device support for SoapySDR (default version)

soapysdr-module-redpitaya/focal 0.1.1-2build1 amd64 RedPitaya device support for SoapySDR (default version)

soapysdr-module-remote/focal 0.5.1-2build1 amd64 Use SoapySDR devices over network (default client module)

soapysdr-module-rfspace/focal 0.2.5-3build2 amd64 RFSpace device support for SoapySDR (default version)

soapysdr-module-rtlsdr/focal 0.3.0-2build1 amd64 RTL-SDR device support for SoapySDR (default version)

soapysdr-module-uhd/focal 0.3.6-2build2 amd64 UHD device support for SoapySDR (default version)

[sq8mvy]

Ok, you have the libsoapysdr0.7 version already installed I can try to help you through TeamViewer

[YanskYManskY]

@ Pawel; appreciated but I do not yet have TeamVieuwer installed on my fresh install Ubuntu. What are your thoughts, where recedes the problem?

[sq8mvy]

Linhpsdr compiled from sources?

[YanskYManskY]

As per directions from the README Linhpsdr compiled from:

git clone https://github.com/g0orx/linhpsdr.git cd linhpsdr make sudo make install

If not the correct source, can you please point me to the correct source?

[sq8mvy]

Yes, these are valid sources. The problem occurs before initializing protocol1 I don't know what the reason is, that's why my TeamViewer help offer. Radioberry (I know this project) works on RPI. Activate only one interface on RPI - Ethernet or WiFi. Not both at the same time.

[YanskYManskY]

Dear Pawel, most gratefull for your concern.

The thing is that I had this all working correctly in 2019 right after I had finished my RadioBerry project. No problem at all whatsoever.

Only recently I made a fresh install with Ubuntu 18.04 and a fresh compiled RPI and RadioBerry. Maybe somethings changed in te software for compiling the RadioBerry or Linhpsdr or in the combinatoir of the both?

Not to mention all this works perfect with SDRConsole and OpenHPSDR MRx under W10.

But I am very eager to learn Linux so I thought the RadioBerry project and learning the Linhpsdr would be a very good choice to start.

[g0orx]

I have pushed an update to receiver.c that does not change the DSP sample rate for FM but is not necessary for the latest WDSP. I have also fixed the filter display that was not being set correctly.

[m5evt]

I have just created an Ubuntu Mate 20.04 VM. I followed the github instructions, all packages were found and installed and the code compiles fine and runs fine my my HL2.

Could I suggest a fresh git clone and go through all the steps again in a methodical order? You don't need to bother with the "Prerequisites for installing the Debian Package" section.

Also I echo advice from others, do not run linhpsdr as sudo.

Could you post the output from:

ps -e | grep pulse

Can you also confirm you have only have 1 radioberry SDR (and no hermes lite) on your network?

[sq8mvy]

Dear YanskYManskY, I did the test. Clean installation of Ubuntu Mate 20.04 on VirtualBox. According to the guidelines, I installed the packages:

• libfftw3-dev
• libpulse-dev
• libsoundio-dev
• libasound2-dev
• libgtk-3-dev
• libsoapysdr-dev
• automake

Then in order: WDSP compilation and installation, CW support compilation and installation, compilation and installation of Linhpsdr,

No problems running Linhpsdr:

[YanskYManskY]

@ Pawel; looking good, that's how its supposed to look like. Thumbs up! @ m5evt thank you ; yansky@yansky-desktop:~$ sudo ps -e | grep pulse 1575 ? 00:00:00 pulseaudio yansky@yansky-desktop:~$

[YanskYManskY]

@ m5evt; yansky@yansky-desktop:~$ sudo ps -e | grep pulse [sudo] password for yansky: Sorry, try again. [sudo] password for yansky: 1575 ? 00:00:00 pulseaudio yansky@yansky-desktop:~$

[YanskYManskY]

Dear friends, Did all you suggested; fresh install methodically as always. Still, not running. @ m5evt; running only 1 RadioBerry

[YanskYManskY]

Some more info: I'm on a 4 G wireless network connected to a switchbox. From the switchbox running patchcables to the RPI and PC.

[YanskYManskY]

All is working very wel on W10 with SDRConsole and OpenHPSDR MRx

[sq8mvy]

Maybe we'll try differently. To begin, delete the directory ~/.local/share/linhpsdr if it exists.

sudo apt update sudo apt upgrade Next cd linhpsdr make clean remove CWX/CW support in the Makefile file as described in README.md make sudo make install And run linhpsdr

[YanskYManskY]

Hello Pawel; mni tnx fr the effort. Did all that. System started creating FFTW3 wisdom files. linhpsdr showed up with 2 instances of the RadioBerry on the same IP; started radio.....nothing happened :-(

[m5evt]

This may be a bug I have introduced that affects the radioberry. I will fix the radioberry bug, hopefully that resolves this.

[sq8mvy]

Thank you m5evt for the information.

@YanskYManskY A long time ago I launched Radioberry v1 (on EP3C25E144). If I find him, I will check cooperation with Linhpsdr. I couldn't make Linhpsdr act like yours. From this link (my goole drive) https://drive.google.com/open?id=1KazdMMJAZWGgnY2Bc6qZDnCNOJ9bsABE download linhpsdr version before changes from m5evt Compile and see if it starts. It will be known if the mistake was already there or was made in later changes.

[YanskYManskY]

Thank you m5evt and sq8mvy for your hard work and looking in to this matter. Tomorrow I wil try to compile linhpsdr from before changes m5evt. Good night to all, stay healthy! YanskY

[m5evt]

I think I have fixed this. Please try the following:

delete the directory ~/.local/share/linhpsdr if it exists.

Then:

git clone https://github.com/g0orx/linhpsdr.git cd linhpsdr make ./linhpsdr

I think this fixes the problems with the Radioberry. Hopefully this is all your problems fixed.

[YanskYManskY]

Dear m5evt; Sorry to say but not working yet. Started radio, after a few seconds discovery screen dissapears and nothing happening.

Logfile: yansky@yansky-desktop:~/linhpsdr$ ./linhpsdr Build: 2020-04-27 Beta GTK+ version 3.24.18 sysname: Linux nodename: yansky-desktop release: 5.4.0-26-generic version: #30-Ubuntu SMP Mon Apr 20 16:58:30 UTC 2020 machine: x86_64 opengl: 0 discovery protocol1_discovery discover: looking for HPSDR devices on lo discover: bound to lo discover_receive_thread discovery: bytes read -1 discovery: recvfrom socket failed for discover_receive_thread: Resource temporarily unavailable discovery: exiting discover_receive_thread discover: exiting discover for lo discover: looking for HPSDR devices on enp0s25 discover: bound to enp0s25 discover_receive_thread discovered: received 60 bytes 40discovery: found device=6 software_version=40 status=2 address=192.168.8.170 (00:01:02:03:04:05) on enp0s25 discovery: bytes read -1 discovery: recvfrom socket failed for discover_receive_thread: Resource temporarily unavailable discovery: exiting discover_receive_thread discover: exiting discover for enp0s25 discovery found 1 devices discovery: found device=6 software_version=40 status=2 address=192.168.8.170 (00:01:02:03:04:05) on enp0s25 protocol2_discover: looking for HPSDR devices on enp0s25 protocol2_discover: bound to enp0s25 192.168.8.148 255.255.255.0 protocol2_disovery: thread_id=0x56376c5e2760 protocol2_discover: bytes read -1 protocol2_discover: recvfrom socket failed for discover_receive_thread: Resource temporarily unavailable protocol2_discover: exiting protocol2_discover_receive_thread protocol2_discover: exiting discover for enp0s25 protocol2_discovery found 1 devices discovery: found protocol=0 device=6 software_version=40 status=2 address=192.168.8.170 (00:01:02:03:04:05) on enp0s25 main: discovery found 1 devices discovered: 0 device=6 adding Hermes Lite V1 tree_selection_changed_cb tree_selection_changed_cb: selected=Hermes Lite V1,1,4.0,192.168.8.170,00:01:02:03:04:05 tree_selection_changed_cb: first=Hermes Lite V1,1,4.0,192.168.8.170,00:01:02:03:04:05 found 0 starting Linux HPSDR (Beta): Hermes Lite V1 P1 v4.0 192.168.8.170 (00:01:02:03:04:05) on enp0s25 create_radio for Hermes Lite V1 6 loadProperties: /home/yansky/.local/share/linhpsdr/00-01-02-03-04-05.props audio: create_audio: USE_PULSEAUDIO n_input_devices=0 create_transmitter: channel=8 transmitter_init_analyzer: width=0 pixels=0 update_timer: fps=10 Segmentation fault (core dumped)

[m5evt]

Please type:

rm /home/yansky/.local/share/linhpsdr/00-01-02-03-04-05.props

Then run ./linhpsdr and paste the output. Your output above looks like it is reading an already created props file. I would like to see:

loadProperties: version=0.000000 expected version=2.000000 ignoring

just before it says "USE_PULSEAUDIO".

[YanskYManskY]

Dear m5evt;

With your instructions, but not without some fiddling around (some reinstalling etc.) finally I've got it working here. I can't express enough how glad I am and how thankful I am towards you taking the time to help me. I admire your skills!

Much obliged, thanks a million!

[m5evt]

Phew, I was starting to run out of ideas. I think it is strongly recommended (if possible) to upgrade your radioberry to the latest gateware/firmware. I'm afraid I can't help with this as I don't own a radioberry. When upgraded, the radioberry should behave like a Hermes Lite 2 and you will have more enhanced features in linhpsdr and enhanced features on your radioberry.

[YanskYManskY]

@Matthew, The RadioBerry has the latest software, but I did not make the hardware change to get 2 receivers from it. So it's all original. Software is doing well right now, although I must say tthatI find the panadapter to act kind of "nervously". Also I can see some 'ghosting" in the signals. Signals seem to be superimposing on each other for part of a second. I don't know if that's the way the panadapter supposed to act that way. I can find no ways in the SW to change that. Maybe that's still something to be develloped?

[YanskYManskY]

[Papparabsi]

Goodmorning all,

Also I noticed that my colorscheme Linhpsdr differs from the colorscheme Linhpsdr used by Pawe,sq8mvy . Not that it's that important, just wondering why.

YanskY

[sq8mvy]

Hi, I always use the latest version of Linhpsdr. The version I gave the link to is the old version from before the changes. Only available for certain tests for YanskYManskY Like any other program, Linhpsdr is also developing, which can be seen from the number of patches introduced.

[YanskYManskY]

Dear friends, Pawel & Matthew,

All is well now, couldn't be happier :-)

Reinstalled again making use of the Github link in the README. Also, the earlier described "nervousness" of the signals in the panadapter can now be set to satisfaction.

[YanskYManskY]

Something I noticed when setting the "Average" slider for the panadapter. When choosing a higher number for averaging teh panadapter (which is very convenient), also this is influencing the detail of the waterfall. That a pity. Would be nice if this could be set independent from each other. Just my opinion of course.

[sq8mvy]

The waterfall and panadapter data are not separated. Counted and averaged in the WDSP library. The more averaged, the smoother the waterfall and panadapter. You can influence the details of the waterfall (color range) by manually changing the parameters Waterfall high and Waterfall low after turning off Waterfall Automatic