From: Stephen Hemminger <stephen@networkplumber.org>
To: Aniket singh <aniketsingh84646@gmail.com>
Cc: users@dpdk.org, navaneetyvn.211cs234@nitk.edu.in
Subject: Re: Seeking help to configure DPDK 22 on Ubuntu 22.04.1 - "No probed ethernet devices"
Date: Thu, 5 Jun 2025 14:24:57 -0700 [thread overview]
Message-ID: <20250605142457.04fff67a@hermes.local> (raw)
In-Reply-To: <CALTb98V2Dp+=+qXcKhzXmJcjoq-Az++gsFM0cp1oF-bzNDHXWw@mail.gmail.com>
On Thu, 5 Jun 2025 23:23:39 +0530
Aniket singh <aniketsingh84646@gmail.com> wrote:
> Hi Everyone,
>
> I'm trying to configure DPDK 22 on Ubuntu 22.04.3 LTS and I'm facing an
> issue when running the testpmd application.
>
> Whenever I execute:
>
> sudo ./dpdk-testpmd
>
> I get the following error:
>
> testpmd: No probed ethernet devices
>
> I've followed the setup steps from the DPDK documentation, including
> hugepages allocation and binding NICs with vfio-pci, but still encountering
> the same issue.
>
> Could someone please help point out what might be missing or guide me on
> how to properly configure DPDK on this version of Ubuntu?
>
> I have tried on both these NICs:
> 0000:00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection
> (17) I219-LM (rev 11)
> 0000:01:00.0 Ethernet controller: Intel Corporation I210 Gigabit Network
> Connection (rev 03)
>
You have to rebind the NIC's to vfio-pci to allow use by DPDK.
Did you look at dpdk-devbind.py script?
Also, some of the on board Ethernet controllers are not yet supported
by DPDK. They fall under the igb driver, but the PCI id's are not listed.
Needs backport from BSD or Linux driver for that.
next prev parent reply other threads:[~2025-06-05 21:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-05 17:53 Aniket singh
2025-06-05 21:24 ` Stephen Hemminger [this message]
2025-06-06 16:17 ` Aniket singh
2025-06-06 16:52 ` Nishant Verma
2025-06-06 20:31 ` Stephen Hemminger
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=20250605142457.04fff67a@hermes.local \
--to=stephen@networkplumber.org \
--cc=aniketsingh84646@gmail.com \
--cc=navaneetyvn.211cs234@nitk.edu.in \
--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).