From: Aniket singh <aniketsingh84646@gmail.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: Nishant Verma <vnish11@gmail.com>,
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: Mon, 9 Jun 2025 00:37:44 +0530 [thread overview]
Message-ID: <CALTb98XjNbbHty7rxaiZ4YiksYWyA7+dXg_Z7vbtqemcifkOtw@mail.gmail.com> (raw)
In-Reply-To: <20250606133105.4b15794a@hermes.local>
[-- Attachment #1: Type: text/plain, Size: 3168 bytes --]
Hi Stephen,
I checked with the above mentioned method and it seems like the I210 NIC is
supported by dpdk. Still I'm getting the same problem with this NIC as well.
FYI, DPDK-19.11.1 was working with the same NIC.
Thanks,
Aniket Singh
On Sat, Jun 7, 2025 at 2:01 AM Stephen Hemminger <stephen@networkplumber.org>
wrote:
> On Fri, 6 Jun 2025 12:52:28 -0400
> Nishant Verma <vnish11@gmail.com> wrote:
>
> > If your NIC is not part of this, then yes it's NOT SUPPORTED officially.
> >
> > https://core.dpdk.org/supported/
> >
> >
> > Regards,
> > Nishant
> >
> >
> > On Fri, Jun 6, 2025 at 12:27 PM Aniket singh <aniketsingh84646@gmail.com
> >
> > wrote:
> >
> > > Hi Stephen,
> > >
> > > I did rebind the NIC's to vfio-pci using the
> > > dpdk-devbind.py script.
> > >
> > > Does that mean both the NICs (I219-LM and I1210) are not supported by
> DPDK?
> > >
> > > Thanks,
> > > Aniket Singh
> > >
> > > On Fri, 6 Jun 2025 at 2:55 AM, Stephen Hemminger <
> > > stephen@networkplumber.org> wrote:
> > >
> > >> 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.
> > >>
> > >>
>
> Use lspci to find the PCI id vendor then look at the source is the
> definitive answer.
> $ sudo ethtool -i enp87s0
> ...
> bus-info: 0000:57:00.0
>
> $ lspci -s 0000:57:00 -n
> 57:00.0 0200: 8086:125c (rev 04)
>
> drivers/net $ git grep 125C
> intel/e1000/base/e1000_hw.h:#define E1000_DEV_ID_I226_V
> 0x125C
> $ git grep ID_I226_V
> intel/e1000/base/e1000_api.c: case E1000_DEV_ID_I226_V:
> intel/e1000/base/e1000_hw.h:#define E1000_DEV_ID_I226_V
> 0x125C
> intel/e1000/igc_ethdev.c: { RTE_PCI_DEVICE(IGC_INTEL_VENDOR_ID,
> E1000_DEV_ID_I226_V) }, <<< yes
>
>
>
[-- Attachment #2: Type: text/html, Size: 4676 bytes --]
prev parent reply other threads:[~2025-06-08 19:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-05 17:53 Aniket singh
2025-06-05 21:24 ` Stephen Hemminger
2025-06-06 16:17 ` Aniket singh
2025-06-06 16:52 ` Nishant Verma
2025-06-06 20:31 ` Stephen Hemminger
2025-06-08 19:07 ` Aniket singh [this message]
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=CALTb98XjNbbHty7rxaiZ4YiksYWyA7+dXg_Z7vbtqemcifkOtw@mail.gmail.com \
--to=aniketsingh84646@gmail.com \
--cc=navaneetyvn.211cs234@nitk.edu.in \
--cc=stephen@networkplumber.org \
--cc=users@dpdk.org \
--cc=vnish11@gmail.com \
/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).