Closed andreoua closed 5 years ago
I figured it out as soon I posted the issue. Leaving it here in case some else comes across this issue as well.
The root cause appears to have been the USB controller option selected in VirtualBox. I had initially had it at USB1.1 and then at USB 3.0. I didn't work under either option. Once I changed it to USB 2.0 it worked flawlessly.
When executing any type of scan it will begin and remain at the first frequency it tries. For example if I execute:
It will go through the init steps and remain at
I compiled it on a fresh Debian 9 install running inside VBox on Win10.