On 08/08/2019 09:44, Martin Gregorie wrote:
> On Thu, 08 Aug 2019 06:06:13 +0100, David Taylor wrote:
>
>> I've been using the Airspy ADS-B decoder on a model 2B with an early OS
>> (Jessie?) for some time, without problems.  The software is described
>> here:
>>
>> https://airspy.com/quickstart/
>>     => Using the ADSB decoder in embedded ARM boards
>>
>> As an experiment, I tried a new SD card with the latest Buster OS, but
>> the program no longer works correctly.  The program does run, but
>> doesn't function - i.e. it doesn't produce decodes of aircraft.  Perhaps
>> it cannot connect to the USB device, but it doesn't issue any error
>> message (I know!).
>>
>> Are there any things I should set in Buster to allow an Airspy device to
>> work?  Any issues with e.g. the RTL-SDR sticks (this is a different
>> device).  Any issues with Buster on a model 2B?
>>
>> I have asked the developer but he's currently busy with a major new
>> product launch.  I'm not quite how to debug this!
>
> Obvious question: is there anything relevant in the logs?
>
> Related point: Buster seems to make rather more use of logging than
> Stretch and predecessors, so you might want to see if the logrotate and
> logwatch packages are installed: I did an in-situ upgrade from Stretch to
> Buster which did not install them, so I added them manually. Then again
> I'm used to having these packages installed on my bigger Fedora boxes and
> I have also modified /etc/aliases so root's mail for every host on my LAN
> gets redirected to my normal login on the laptop that I usually work
> from.

Martin,

Thanks for that suggestion.  dmesg showed just the existence of the USB
device, and that looked correct.  That's really the only log inspection
command I've used.  Should I be looking elsewhere?

--
Cheers,
David
Web: http://www.satsignal.eu

--- SoupGate-Win32 v1.05