DPDK usage discussions
 help / color / mirror / Atom feed
From: Gerry Wan <gerryw@stanford.edu>
To: users@dpdk.org
Subject: [dpdk-users] Building mlx5 with rdma-core/OFED
Date: Sun, 1 Aug 2021 17:23:10 -0700	[thread overview]
Message-ID: <CAAcwi39okk1x7LMxxCHYh-Boh6RKXLZVepGhz0c+KjFXr_5xJg@mail.gmail.com> (raw)

I recently tried to reinstall MLX OFED 5.2-2.2.0.0 on my bare metal machine
Ubuntu 20.04 (previously using the command ./mlnxofedinstall --dpdk
--upstream-libs --with-mft --with-kernel-mft). However, it now fails with
the message

Checking SW Requirements...
Removing old packages...
Uninstalling the previous version of MLNX_OFED_LINUX
Installing new packages Installing mft-4.16.1...
Installing ofed-scripts-5.2...
Installing mstflint-4.15.0...
Installing mlnx-ofed-kernel-utils-5.2...
Installing mlnx-ofed-kernel-dkms-5.2...
Failed to install mlnx-ofed-kernel-dkms DEB
Collecting debug info...
See /tmp/MLNX_OFED_LINUX.9221.logs/mlnx-ofed-kernel-dkms.debinstall.log

It appears that my kernel version got upgraded to 5.4.0-80-generic which I
think may be the issue. I've also tried to install using
 --add-kernel-support --kernel 5.4.0-80-generic, with no luck.

The DPDK website says that rdma-core is now recommended over OFED, but the
documentation for how to use it isn't very clear to me. I've tried to
install it via

apt-get install rdma-core

as well as running the quick start script listed here:
https://github.com/linux-rdma/rdma-core, but DPDK installation still fails
with

../drivers/common/mlx5/linux/mlx5_glue.h:15:10: fatal error:
infiniband/mlx5dv.h: No such file or directory
   15 | #include <infiniband/mlx5dv.h>

Any advice on getting the mlx5 drivers to work again would be helpful!

             reply	other threads:[~2021-08-02  0:23 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-02  0:23 Gerry Wan [this message]
2021-08-02 13:24 ` PATRICK KEROULAS
2021-08-02 18:35   ` Gerry Wan
2021-08-02 19:59     ` PATRICK KEROULAS
2021-08-02 20:18       ` Gerry Wan
2021-08-03 14:23         ` PATRICK KEROULAS
2021-08-13  7:02           ` Gerry Wan

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAAcwi39okk1x7LMxxCHYh-Boh6RKXLZVepGhz0c+KjFXr_5xJg@mail.gmail.com \
    --to=gerryw@stanford.edu \
    --cc=users@dpdk.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).