Oliver Jowett
Oliver Jowett
Can you check if your soapysdr-rtlsdr driver is basically functional with SoapySDRUtil? (Install package `soapysdr-tools` if not already there). Should look something like this: ``` $ SoapySDRUtil --args='driver=rtlsdr' --rate=2400000 --direction=rx...
This sounds like you have version skew between the soapysdr/rtlsdr libraries and dump978. please ensure that: a) you have only one version of librtlsdr installed b) you have only one...
If create is called and there are already runtime properties on the node instance pointing to a VM, and that VM still exists, then create should definitely not create a...
BTW, if you have such an "install/repair" workflow, then healing from failures is a bit simpler: tear down (reset) all failed node instances and anything contained within them, then run...
The repair workflow is probably always going to be a superset of the install workflow (consider the "everything fails" case)
and subsequently things like subnet deletion also fail because the server is still present, so they are also leaked.
Sent a copy to the list. It's definitely a bug that the plugin/workflow leak cloud resources, surely?
Try the dev branch? It has some commits around this area that may help.
> fatal error: 'rtl-sdr.h' file not found #include You don't have librtlsdr installed correctly (or you need to set `RTLSDR_PREFIX` appropriately to point at your install)
Most of your questions are probably better addressed by the SoapySDR or individual driver documentation. > What else can I put into --device ? What format should/can it have? See...