On 24/07/2023 22:13, Gary Schafer wrote:
I just upgraded my system from Linux Mint 21.1 to 21.2. My system is
an Intel i7-6700 based desktop with 32 GB of RAM. After loading the OS
and going through my usual routine of loading programs and drivers, I
discovered that I cannot use my USRP B200mini. I tried running a basic
Gnu Radio flowgraph of USRP source to a frequency sink as a quick
test. Right after I started it, it stopped with the statement, "Done
(return code-11)". I'm not certain if this is a Gnu Radio problem,
Mint problem, or USRP problem. I *suspect* it's a Mint / USRP problem.
I've loaded libuhd4.1.0 as well as libuhd-dev and uhd-host. Normally,
that's all that is required.
When I run "uhd_find_devices", I get:
[INFO] [UHD] linux; GNU C++ version 11.2.0; Boost_107400; UHD_4.1.0.5-3
--------------------------------------------------
-- UHD Device 0
--------------------------------------------------
Device Address:
serial: 11160936550978964554
default_input: False
default_output: False
device_id: 4
driver: audio
label: Monitor of GM204 High Definition Audio Controller Digital
Stereo (HDMI 3)
type: soapy
--------------------------------------------------
-- UHD Device 1
--------------------------------------------------
Device Address:
serial: 12015008079946540021
default_input: True
default_output: False
device_id: 0
driver: audio
label: C922 Pro Stream Webcam Analog Stereo
type: soapy
--------------------------------------------------
-- UHD Device 2
--------------------------------------------------
Device Address:
serial: 13719246102091647219
default_input: False
default_output: False
device_id: 3
driver: audio
label: Monitor of Built-in Audio Analog Stereo
type: soapy
--------------------------------------------------
-- UHD Device 3
--------------------------------------------------
Device Address:
serial: 3279479
name: B200mini
product: B200mini
type: b200
Further, when I run uhd_usrp_probe, I get the following:
INFO] [UHD] linux; GNU C++ version 11.2.0; Boost_107400; UHD_4.1.0.5-3
_____________________________________________________
/
| Device: Audio
| _____________________________________________________
| /
| | Mboard: Audio
| | device_id: 0
| | origin: https://github.com/pothosware/SoapyAudio
| |
| | Time sources:
| | Clock sources:
| | Sensors:
| | _____________________________________________________
| | /
| | | RX DSP: 0
| | |
| | | Freq range: 0.000 to 0.000 MHz
| | _____________________________________________________
| | /
| | | RX Dboard: 0
| | | _____________________________________________________
| | | /
| | | | RX Frontend: 0
| | | | Name: SoapyRF
| | | | Antennas: RX
| | | | Sensors:
| | | | Freq range: 0.000 to 6000.000 MHz
| | | | Gain Elements: None
| | | | Bandwidth range: 0.0 to 0.0 step 0.0 Hz
| | | | Connection Type: IQ
| | | | Uses LO offset: No
| | | _____________________________________________________
| | | /
| | | | RX Codec: 0
| | | | Name: SoapyADC
| | | | Gain Elements: None
| | _____________________________________________________
| | /
| | | TX DSP: 0
| | |
| | | Freq range: 0.000 to 0.000 MHz
| | _____________________________________________________
| | /
| | | TX Dboard: 0
| | | _____________________________________________________
| | | /
| | | | TX Frontend: 0
| | | | Name: None
| | | | Antennas:
| | | | Sensors:
| | | | Freq range: 0.000 to 0.000 MHz
| | | | Gain Elements: None
| | | | Bandwidth range: 0.0 to 0.0 step 0.0 Hz
| | | | Connection Type: IQ
| | | | Uses LO offset: No
| | | _____________________________________________________
| | | /
| | | | TX Codec: 0
| | | | Name: None
| | | | Gain Elements: None
This does not seem correct. For example, when running the same command
on another system still running 21.1, I get much more detailed
information about the B200mini. (It also says that it is loading a
firmware image right after starting the command, which does not happen
here.)
If anyone has any ideas, I'm all ears.
Thanks,
Gary
This looks like some confusion in the kernel about USB VID/PID values?
What does "lsusb" produce?
For USB devices, "uhd_find_devices" will look for USB devices with the
correct VID/PID for NI/Ettus devices. In your case, things
seem quite confused. This is likely to be a kernel issue, or maybe
a "libusb" issue. Dunno.
