This is merely a historical archive of years 2008-2021, before the migration to mailman3.
A maintained and still updated list archive can be found at https://lists.osmocom.org/hyperkitty/list/op25-dev@lists.osmocom.org/.
'O'Connor, Daniel' darius@dons.net.au [op25-dev] op25-dev at yahoogroups.com> On 29 Nov 2018, at 10:13, 'Trunk Tracker' trunktracker at tampabay.rr.com [op25-dev] <op25-dev at yahoogroups.com> wrote: > > Then I looked in stderr.2 and found this: FYI this is a few bugs and bug fixes ganging up to crash. The first bug was (it is fixed since *2016* - https://github.com/gnuradio/gnuradio/commit/11973c64437683cc99c48eae9eb4db8234f1ac42#diff-6afde48a2246887a22e0cbe0a675e1c8) in GNUradio #528. A work around was added to rtl-sdr (which is the "Trying to fill up.." message) which is at https://github.com/osmocom/gr-osmosdr/blob/5ecfa255d299b9b4842ccd09a02892a853fcd5a7/lib/source_impl.cc#L413 The second bug is p25_demodulator.py crashing because it doesn't detect self.decim is zero. It looks like gr-osmosdr now has the work around removed (since July 2017) - https://github.com/osmocom/gr-osmosdr/commit/ea6b356cfda8a90fa6d727fcc13aae60547962a2 tl;dr: - It didn't find your hardware, check your VM pass through - Update gr-osmosdr to get less confusing errors :) -- Daniel O'Connor "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.osmocom.org/pipermail/op25-dev/attachments/20181129/2a337887/attachment.htm>