USRP nirio_zero_copy problem

[flow233-ai]

Hi everyone. I have encountered a problem have not found a solution on the internet so far. The settings is shown as follows:

We use PCIe for the connection between our PC and USRP X310. And the Linux system of PC is Ubuntu 20.04. We use radioconda to install gnuradio 3.8 and UHD 3.15. And the Python version is Python 3.8.

Then we use “uhd_find_devices” and the USRP can be detected. But then we use “uhd_usrp_probe”, the following errors occurred:
Error: RuntimeError: Could not create nirio_zero_copy transport. Unknown error. (Error code -63150)

Cannot find the solutions over Internet. I Wonder if this is a NI RIO driver problem or some other problems.
Many thanks.

[joergho]

Hi @flow233-ai ,

have you followed the instructions from the manual page Linux NI RIO Installation and Usage? You need the NI RIO driver correctly installed for the nirio_zero_copy transport to function.

The latest version of the NI Linux Device Drivers (2024 Q4) is available here: https://www.ni.com/de/support/downloads/drivers/download.ni-linux-device-drivers.html#548386

The download provides the archive NILinux2024Q4DeviceDrivers.zip which contains ni-ubuntu2004-drivers-2024Q4.deb. You need to install it (sudo dpkg -i ni-ubuntu2004-drivers-2024Q4.deb) and then follow the further steps from the "Linux NI RIO Installation and Usage" manual page (starting at the section "Update package information").

Please note: after installation (and each time the X310 is disconnected/reconnected), a reboot of the host PC is required, because the PCIe connection does not support hotswapping, as noted in the manual:

Hot-Plugging and Power-Cycling

The USRP X3x0, NI USRP-294x and NI USRP-295x devices cannot be hot-swapped when connected over PCI Express. Unplugging the PCI Express connection or powering the device should be done only after powering off the host computer.

Regards,
Jörg

[mbr0wn]

This might be a legit bug (even on more recent UHD versions). Can you use Ethernet for the time being? It's rare that PCIe will do anything for you that Ethernet cannot (on the X310, at least).

[flow233-ai]

Hi @flow233-ai ,

have you followed the instructions from the manual page Linux NI RIO Installation and Usage? You need the NI RIO driver correctly installed for the nirio_zero_copy transport to function.

The latest version of the NI Linux Device Drivers (2024 Q4) is available here: https://www.ni.com/de/support/downloads/drivers/download.ni-linux-device-drivers.html#548386

The download provides the archive NILinux2024Q4DeviceDrivers.zip which contains ni-ubuntu2004-drivers-2024Q4.deb. You need to install it (sudo dpkg -i ni-ubuntu2004-drivers-2024Q4.deb) and then follow the further steps from the "Linux NI RIO Installation and Usage" manual page (starting at the section "Update package information").

Please note: after installation (and each time the X310 is disconnected/reconnected), a reboot of the host PC is required, because the PCIe connection does not support hotswapping, as noted in the manual:

Hot-Plugging and Power-Cycling
The USRP X3x0, NI USRP-294x and NI USRP-295x devices cannot be hot-swapped when connected over PCI Express. Unplugging the PCI Express connection or powering the device should be done only after powering off the host computer.

Regards, Jörg

I have tried reinstall the NI RIO Driver. And it failed.
So maybe I would like to use 10 Gigabit network card for connection.

[flow233-ai]

This might be a legit bug (even on more recent UHD versions). Can you use Ethernet for the time being? It's rare that PCIe will do anything for you that Ethernet cannot (on the X310, at least).

Yes. I think I would like to use this method.

[mbr0wn]

Something else you can try (if you want to stick with PCIe) is to use Ubuntu 20.04, which looks like it might be working under some circumstances.

[flow233-ai]

Something else you can try (if you want to stick with PCIe) is to use Ubuntu 20.04, which looks like it might be working under some circumstances.

I‘ve tried with Ubuntu20.04 as mentioned above. But it failed.

[mbr0wn]

OK, that's interesting. Thanks for confirming. I had somehow misread your original report as "24.04".