Hi Stephen, 

To add a few comments on persistence - the Live USB image doesn't come with 
persistence configured. Two ways to do this, one of them does NOT work on 
Ubuntu 14.04 (fixed on 15.04 as some forums claim):

1. create a casper-rw file on the fat32 boot partition, format as an ext-3 
internally. Max 4Gb on fat32. Unetbootin does this in one step if you select a 
filesize > 0 during config.
2. create an ext-2/3/ or 4 partition labeled "casper-rw". size is unlimited. 
This does not work on Ubuntu 14.04, it does recognize the partition but escapes 
prematurely during boot

I used Unetbootin for initial setup. 

labeling the partition "home-rw" to save the home dir instead (keeping 
casper-rw FILE for settings only) did not work either. Unless anyone tried and 
succeeded?... 

One last comment - one of the earlier Live SDR versions was on Linux Mint, 
which was better imho; especially with the file permissions being lighter 
(better). In the current, Ubuntu version, I had to switch between root and 
"ubuntu live" to make things work (software center in some cases), using chown 
on other occasions (to run eclipse with pydev for example).  No such issues on 
Mint. Don't make the mistake of creating your own user accounts - this causes 
more issues than it solves..

Ubuntu is fine though, as long as the image is upgraded to 15.04 to make 
persistence work. 

Another option is full install on a USB drive - haven't tried, but with 16Gb 
usb3.0 <$20 it seems like a good idea all around.  It could be upgraded locally 
to >14.04.

Best,
Arik  Landsman


________________________________________
From: [email protected] 
[[email protected]] on behalf of 
[email protected] [[email protected]]
Sent: Sunday, February 14, 2016 12:00 PM
To: [email protected]
Subject: Discuss-gnuradio Digest, Vol 159, Issue 19

Send Discuss-gnuradio mailing list submissions to
        [email protected]

To subscribe or unsubscribe via the World Wide Web, visit
        https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
or, via email, send a message with subject or body 'help' to
        [email protected]

You can reach the person managing the list at
        [email protected]

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Discuss-gnuradio digest..."


Today's Topics:

   1.  GNURadio Live SDR update request (Stephen Berger)
   2. GNU Radio release v3.7.9.1 available (West, Nathan)
   3. Capture peaks in gnu radio (scott tiger)


----------------------------------------------------------------------

Message: 1
Date: Sat, 13 Feb 2016 13:20:21 -0600
From: "Stephen Berger" <[email protected]>
To: <[email protected]>
Cc: [email protected]
Subject: [Discuss-gnuradio]  GNURadio Live SDR update request
Message-ID: <[email protected]>
Content-Type: text/plain; charset="us-ascii"

Jared,



I ran into a similar problem with the Broadcom WiFi adapter on my HP Envy
laptop.  That lead to a second problem which was that although I made the
bootable USB using Unetbootin, selecting persistence the result wasn't
persistent.  I had to go into the USB and in the boot modify the grub.cfg.
I then had to make some additional additions to add the Broadcom driver but
the result was that both problems were solved.



I wonder if the more efficient process wouldn't be to have a thread that
listed these issues and their solutions so that those who have particular
machines can find the modifications they need to make to their USB?







Best Regards,





Stephen Berger

-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
<http://lists.gnu.org/archive/html/discuss-gnuradio/attachments/20160213/ef1097d1/attachment.html>

------------------------------

Message: 2
Date: Sat, 13 Feb 2016 17:43:33 -0500
From: "West, Nathan" <[email protected]>
To: "[email protected]" <[email protected]>
Subject: [Discuss-gnuradio] GNU Radio release v3.7.9.1 available
Message-ID:
        <calkxilljmbrn7uo6ovsxntv89frekgp-knogaj2boquzfdb...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"

GNU Radio release v3.7.9.1 and corresponding live SDR environment is now
available for download:

http://gnuradio.org/releases/gnuradio/gnuradio-3.7.9.1.tar.gz
http://gnuradio.org/releases/gnuradio/gnuradio-3.7.9.1.tar.gz.asc
http://s3-dist.gnuradio.org/ubuntu-14.04.3-desktop-amd64-gnuradio-3.7.9.1.torrent

MD5 sums:

653155499bcefb1478b1963f11841434  gnuradio-3.7.9.1.tar.gz
d712141f1e11584a29566713a58c79a1
ubuntu-14.04.3-desktop-amd64-gnuradio-3.7.9.1.torrent

Contributors

The following list of people directly contributed code to this release. As
an added bonus this is the first contribution for three of these authors!

   - Andrej Rode [email protected]
   - Paul David [email protected]
   - Derek Kozel [email protected]
   - Johannes Schmitz [email protected]
   - Johnathan Corgan [email protected]
   - Marcus M?ller [email protected]
   - Martin Braun [email protected]
   - Philip Balister [email protected]
   - Ron Economos [email protected]
   - Sebastian Koslowski [email protected]
   - Sylvain Munaut [email protected]
   - Tim O'Shea [email protected]
   - Tom Rondeau [email protected]

Closed issues

   - #528 <http://gnuradio.org/redmine/issues/528>
   - #719 <http://gnuradio.org/redmine/issues/719>
   - #768 <http://gnuradio.org/redmine/issues/768>
   - #831 <http://gnuradio.org/redmine/issues/831>
   - #864 <http://gnuradio.org/redmine/issues/864>
   - #868 <http://gnuradio.org/redmine/issues/868>
   - #876 <http://gnuradio.org/redmine/issues/876>
   - #879 <http://gnuradio.org/redmine/issues/879>
   - #882 <http://gnuradio.org/redmine/issues/882>
   - #883 <http://gnuradio.org/redmine/issues/883>

Code

This release includes a number of minor typos and miscellaneous rewording
of error messages. The following sections summarize substantial changes.
GRC

   - the 'Parser errors' menu item wasn't correctly enabled
   - embedded python blocks: message ports are now optionial and show the
   correct label
   - custom run command now accounts for filepaths that need escaping
   - virtual sink/source message connections were dropped when opening a
   flow graph
   - tooltips in block library are truncated if too long
   - not all tooltips in block library were updated after docstring
   extraction finished
   - some expressions were wrongfully marked invalid after opening a flow
   graph
   - move random uniform source from analog to waveform generators in GRC

Scheduler and Runtime fixes

A new unit test is available to test a bug reported on stack overflow where
blocks (such as the delay block) would drop tags. Paul David stepped in
with his first contribution to GNU Radio with a fix.

Fix an issue with flat_flowgraph calculating alignment by misinterpreting
units of write and read indices. This was only apparent when these indices
are non-zero (a flowgraph has stopped and restarted).

Fix exceptions thrown in hier_block2 constructors.

Check d_ninput_items_required for overflow and shut down if overflow is
detected.

Allow hier_block2's to change I/O signature in the constructor, which was
previously allowed by the API, but broken.
gr-blocks

Use unsigned char rather than char in add_const_bb. This was the legacy
behavior with the older add_const_XX and was accidentally replaced with
char when replacing the templated version.

Fix vector length units from bytes to number of items in PDU to tagged
stream and tagged stream to PDU blocks.
gr-filter

Add a check to the rational resampler to stop working after we've operated
on all input items (closed issue #831
<http://gnuradio.org/redmine/issues/831>)

Throw an error when pfb clock sync is given constant taps which results in
a derivative of 0 (calculated as NaN). (closed issue #812
<http://gnuradio.org/redmine/issues/812> and 734). Added a reset_taps
function to externally set taps which should be used in place of set_taps

Fix a memory leak in pfb decimator (closed issue #882
<http://gnuradio.org/redmine/issues/882>)
gr-analog

Maximum Deviation parameter for NBFM transmitter exposed to GRC
gr-digital

Change the constellation receiver to inherit from control_loop publically
rather than the impl to better support the control port interface. (closed
issue #876 <http://gnuradio.org/redmine/issues/876>)
gr-fec

TLC to puncture/depuncture GRC files in gr-fec
gr-zeromq

Major performance and correctness fixes to gr-zeromq
Builds

Fix cross compiling on for 64-bit architectures by not setting DEBIAN,
REDHAT, and SLACKWARE. OOT modules created with modtool should update their
cmake/Modules/GrPlatform.cmake to support cross 64-bit builds.


Nathan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
<http://lists.gnu.org/archive/html/discuss-gnuradio/attachments/20160213/13b19a44/attachment.html>

------------------------------

Message: 3
Date: Sun, 14 Feb 2016 13:24:05 +0100
From: scott tiger <[email protected]>
To: [email protected]
Subject: [Discuss-gnuradio] Capture peaks in gnu radio
Message-ID:
        <CA+Kb_ueDLwnfe3S0qg6mKi0H3mc=tru6vnwkkibj-uwfsil...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"

Hello all,
Is there any suggestion how to capture or save only several peaks
"amplitude and their positions" in the received band.
For example, Using USRP I am receiving 2MHz band but I need to save
automatically only several peaks in different frequencies. These peaks can
be chosen according to their amplitude. How to make gnu radio choose and
save only these peaks and their positions "frequency or time".

Thank you for any help
Best regards
Maksim
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
<http://lists.gnu.org/archive/html/discuss-gnuradio/attachments/20160214/4e59acd2/attachment.html>

------------------------------

_______________________________________________
Discuss-gnuradio mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio


End of Discuss-gnuradio Digest, Vol 159, Issue 19
*************************************************

_______________________________________________
Discuss-gnuradio mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Reply via email to