Ubuntu 17.04 Zesty not ready?


#1

I just loaded Ubuntu 17.04 (Zesty) and tried the usual
sudo add-apt-repository -y ppa:ettusresearch/uhd
sudo add-apt-repository -y ppa:myriadrf/drivers
sudo add-apt-repository -y ppa:myriadrf/gnuradio
sudo add-apt-repository -y ppa:gqrx/gqrx-sdr and
sudo apt-get update …
The lines are scrolling up and then it displays
Err:21 http://ppa.launchpad.net/ettusresearch/uhd/ubuntu zesty/main i386 Packages
404 Not Found
Err:28 http://ppa.launchpad.net/gqrx/gqrx-sdr/ubuntu zesty/main i386 Packages
404 Not Found
Err:37 http://ppa.launchpad.net/myriadrf/drivers/ubuntu zesty/main amd64 Packages
404 Not Found
Err:44 http://ppa.launchpad.net/myriadrf/gnuradio/ubuntu zesty/main amd64 Packages
404 Not Found
then:
Reading package lists… Done
W: The repository ‘http://ppa.launchpad.net/ettusresearch/uhd/ubuntu zesty Release’ does not have a Release file.
N: Data from such a repository can’t be authenticated and is therefore potentially dangerous to use.
N: See apt-secure(8) manpage for repository creation and user configuration details.
W: The repository ‘http://ppa.launchpad.net/gqrx/gqrx-sdr/ubuntu zesty Release’ does not have a Release file.
N: Data from such a repository can’t be authenticated and is therefore potentially dangerous to use.
N: See apt-secure(8) manpage for repository creation and user configuration details.
W: The repository ‘http://ppa.launchpad.net/myriadrf/drivers/ubuntu zesty Release’ does not have a Release file.
N: Data from such a repository can’t be authenticated and is therefore potentially dangerous to use.
N: See apt-secure(8) manpage for repository creation and user configuration details.
W: The repository ‘http://ppa.launchpad.net/myriadrf/gnuradio/ubuntu zesty Release’ does not have a Release file.
N: Data from such a repository can’t be authenticated and is therefore potentially dangerous to use.
N: See apt-secure(8) manpage for repository creation and user configuration details.
E: Failed to fetch http://ppa.launchpad.net/ettusresearch/uhd/ubuntu/dists/zesty/main/binary-i386/Packages 404 Not Found
E: Failed to fetch http://ppa.launchpad.net/gqrx/gqrx-sdr/ubuntu/dists/zesty/main/binary-i386/Packages 404 Not Found
E: Failed to fetch http://ppa.launchpad.net/myriadrf/drivers/ubuntu/dists/zesty/main/binary-amd64/Packages 404 Not Found
E: Failed to fetch http://ppa.launchpad.net/myriadrf/gnuradio/ubuntu/dists/zesty/main/binary-amd64/Packages 404 Not Found
E: Some index files failed to download. They have been ignored, or old ones used instead.
Is there something I need to do to make these packages get found?

Larry in El Paso


#2

if you take a look here: https://launchpad.net/~myriadrf/+archive/ubuntu/drivers
zesty packages don’t exist yet. you will have to compile everything manually


#3

Thanks, I was afraid of that.

Larry in El Paso


#4

Its that time of the year again. I was just thinking about the new ubuntu release this weekend. I’m looking to tag both SoapySDR and Pothos releases (and a bunch of modules). And I thought it would be nice to do that first rather than upload the current release and do it all over again. Theres also gr-osmosdr updates and Limesuite features to get out. :slight_smile:

@csete How do you feel about starting to go after this w/ me? I was thinking about the following:

  1. upload any dependencies like misc sdr drivers
  2. upload soapysdr and modules to 0.6 ABI
  3. tag and upload limesuite as well
  4. backport gnuradio/rebuild gr-osmosdr

Any idea which packages we need for 1) on this latest release to stay up to date? After that I can probably take care of 2) and 3) by this weekend. And we should be able to split up 4) and some other gr-packages at that point.

Looks like current releases are 17.04, 16.04 (LTS), and 14.04 (LTS). 16.10 is nearly EOL and not worth updating IMHO. I was also thinking about not updating 14.04 (LTS) trusty since we already have the newer LTS 16.04. One recent LTS ubuntu is probably good enough for most people. Interested to hear any thoughts on that though.


#5

Hi Josh,

I see no need to update drivers unless we want to switch to the alternate librtlsdr. I have not tested it, so I don’t have any opinion about it. I’m fine with either.

I will update gr-osmosdr when it is time. My earlier patches are now merged upstream, however, I have got a new patch that fixes rtl_tcp but we should probably wait with that.

I’m fine with gnuradio 3.7.10 that comes with the OS, but you are welcome to upload 3.7.10.1 if you wish. I guess it makes sense to have the same gnuradio on all versions.

Shouldn’t we at least try updating 14.04 and 16.10? I guess it is only soapysdr and gr-osmosdr that needs updating here, perhaps also limesuite.


#6

I upgraded to the latest AMD 8 core cpu, motherboard and a Nvidia 1250 Cuda Core videocard. It won’t run on Ubuntu 16.anything because of the hardware. Windows 7 won’t touch it. It’s Ubuntu 17.04 and Windows 10 or it won’t go. For now, Ubuntu 17.04 or nothing.

Larry in El Paso


#7

Larry,

If everything goes according to plan, it should be available in a week or so.


#8

Thanks for your effort. I miss my GQRX.

Larry in El Paso


#9

Correction: Ubuntu 17.04 already has 3.7.10.1 and I suggest we stick to that. We can backport newer versions when they become available in Debian unstable.

@joshblum I assume you will let me know when SoapySDR and Limesuite is done?


#10

When I try to update software it looks at http://ppa.launchpad.net/myriadrf/drivers/ubuntu , http://ppa.launchpad.net/gqrx/gqrx-sdr/ubuntu , http://ppa.launchpad.net/ettusresearch/uhd/ubuntu , http://ppa.launchpad.net/myriadrf/gnuradio/ubuntu and http://ppa.launchpad.net/bladerf/bladerf/ubuntu. I would be fine not having to check UHD and Blade RF as I don’t have those devices. GQRX and GNUradio are must haves.

Larry in El Paso


#11

Unfortunately, that’s not possible without disabling those drivers, although we will probably have to disable UHD support since I am not aware any fixes for the known crash in gr-osmosdr.


#12

I had a lot of repositories to tag. :stuck_out_tongue: Thats done. I’m going to start uploading packages and working around any issues that come up, pardon my dust. Some repos may be in disarray until this is over.

I will see what happens when I backport gnuradio stuff. I guess its just a matter of scripting to handle the other releases. I just dont like the idea of 4 ubuntu releases to build for. Its just laziness, but I think it should just be current release + latest LTS release :slight_smile:


#13

here is what I get with gqrx -
larry@Remote:~$ gqrx
linux; GNU C++ version 6.2.0 20161027; Boost_106200; UHD_003.009.005-0-unknown

Controlport disabled
No user supplied config file. Using “default.conf”
gr-osmosdr 0.1.4 (0.1.4) gnuradio 3.7.10
built-in source types: file osmosdr fcd rtl rtl_tcp uhd miri hackrf bladerf rfspace airspy soapy redpitaya
FM demod gain: 1.52789
IQ DCR alpha: 1.04166e-05
Using audio backend: auto
BookmarksFile is /home/larry/.config/gqrx/bookmarks.csv
Segmentation fault (core dumped)
larry@Remote:~$ gqrx hackrf
linux; GNU C++ version 6.2.0 20161027; Boost_106200; UHD_003.009.005-0-unknown

Controlport disabled
No user supplied config file. Using “default.conf”
gr-osmosdr 0.1.4 (0.1.4) gnuradio 3.7.10
built-in source types: file osmosdr fcd rtl rtl_tcp uhd miri hackrf bladerf rfspace airspy soapy redpitaya
FM demod gain: 1.52789
IQ DCR alpha: 1.04166e-05
Using audio backend: auto
BookmarksFile is /home/larry/.config/gqrx/bookmarks.csv
Segmentation fault (core dumped)
larry@Remote:~$

This means nothing useful to me. I have removed the ppa.launchpad update links for now.
Suggestions are welcome.

Larry in El Paso


#14

Josh, which “gnuradio stuff” should be backported? We already have gnuradio 3.7.10.1 available in Ubuntu 14.04 - 17.04; does it have to be upgraded?


#15

Larry,

The PPA has not yet been updated so all you get is the packages from Ubuntu, whuich has broken gr-osmosdr. Please wait until we have updated the PPA.


#16

I wrongly assumed that there was at least some package update in 17.04 to backport. I just looked into it. Sorry nevermind.

Though… technically gnuradio (gr-uhd) should be rebuilt to match the UHD from the ettus ppa. Although the gr-osmosdr package just wraps the gr-uhd blocks, it also includes uhd headers and probably links with it. I think they both need rebuilding, but If I recall that might not address the segfault.


#17

SoapySDR is uploaded, The PPA should be publishing modules including limesuite now.


#18

Hi Josh,

Sound great. I am taking care of the rest.

Started updating/backporting GNU Radio and I noticed:

  • 14.04 and 16.04 OK
  • 16.10 already built after the latest UHD update, so no need to rebuild
  • 17.04 same version is already available in Ubuntu repo and UHD PPA not yet available, so I cancelled the build

I will let you know when I have updated the remaining packages.


#19

Ok, I think I’m done.

@wb8lbz_Larry Please try it it now and let us know!


#20

Thanks again for your efforts, all. I’ll give it a spin on my 17.04 fresh install.

Larry in El Paso