From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 0E0374684F for ; Sun, 8 Jun 2025 21:07:59 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 997FA4026B; Sun, 8 Jun 2025 21:07:58 +0200 (CEST) Received: from mail-lj1-f179.google.com (mail-lj1-f179.google.com [209.85.208.179]) by mails.dpdk.org (Postfix) with ESMTP id 5160D40269 for ; Sun, 8 Jun 2025 21:07:57 +0200 (CEST) Received: by mail-lj1-f179.google.com with SMTP id 38308e7fff4ca-32a72cb7e4dso34341601fa.0 for ; Sun, 08 Jun 2025 12:07:57 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1749409676; x=1750014476; darn=dpdk.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=pOkW1CRbgpy9J/yuW6me4vgW5tgvrFAEYkNLlQEvdlQ=; b=WS2GbGljsKZUTP5KCAVU3sjMfOlYrG+1n0PoJANXjuPC9BBW89A1SrrYqSpnMbCMTq rH3jqJmjnqo6rnKuPWt77yxFw4cFTwBzrIJTFpCw9kIyUrkNgw4VhIgpObx1jnYjHSEh MvtUTJ9EEYF1NVRSO6vsO6nUFC5kggYJN9LoZ243lHxsfLFsupBjvblD8CpWx5WOYVdR r8+ZUgf7oVvcowyHGsbri+H40iCdoFkA9Qr0aIiiDIf0xPQyXkxgAT56jFFyfMPpRZK3 sLd8+IEB+V3RzDXbQbkpolXXiku5G54uKjX4MpE8WbKD/6Ug85fLsJ5+Vjx47L7tqdOQ VAbA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1749409676; x=1750014476; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=pOkW1CRbgpy9J/yuW6me4vgW5tgvrFAEYkNLlQEvdlQ=; b=afm3As7U7RsA/RpV3LnKLQ0SXNSms9R0/9fRVb/jXMFlWJpoBDJA89E26syxbQHlPP 6KIpYQ4fqDQEc5Or7ud+zBBPXveYYjTxtMmKQaqKW6YVQqTRNYxavDkcuXw26PsJQeAH t374i7wsE5kqy9mqp9hFw9Pee/Tra1SA7au/6tKD4bFv6UT+K8GZUccEFjyhT3zPfBr2 LnXSb8bS/1qRT/V36MTHKIw0Q9+fk3gt/muCXIhZ2fsxQJAUeqR/qbCaPROsGrWro+5g 1NTV+fHCqxdIQ7Fspt3yhZ55j2tidxR9tnWREm2fbdBJdZsBeytrWJt+UpYz1wsK74Zr g9cA== X-Forwarded-Encrypted: i=1; AJvYcCXsQ06j3jdLa4hfOAk0uwh3uWsCtlsQGMRODpmu6uYRu8qPpzyn4POohsbKbkmim2dtlDCx1w==@dpdk.org X-Gm-Message-State: AOJu0YyLdTIRBAwWgEZaF31TWQsZOr0HieCy7lzpLvrcF54r0ThcsJst wjR92WQbmDYswXJNLjxjdtZ6BblZPuivUBpEhm95DCWnp4PBE9Vq6LuzWMh140niqNjMfdaEVgn N4pejVRdycCQcDzJ9i1jvUisE1XQHeFE= X-Gm-Gg: ASbGncvVoj+PnQfIsr9g2m1oXefV+rfkZksf0d1XEB8Oo5YVxWcwWg3xpFJlOG2cZqS W6AwgdN+dH6ekXcqUZeHjeIw7tfkvfy/9o6ZdI/wvovU2y2MlNmESAbGyMNk3oKJxIRWNLlSaLn lELOlMOJTQ8ziohV6gCJGmgfAewvGSBECRJETP4LFwmJY= X-Google-Smtp-Source: AGHT+IFicEYVo/xtqhUMDB7M+7SSY34rkt+BVkyvFGV+sPBTVtH86TCsxG99+MyAdetURzPdGh/w6oCLiH745Z8PwKw= X-Received: by 2002:a2e:b892:0:b0:32a:826a:c9d9 with SMTP id 38308e7fff4ca-32adfc55051mr26994411fa.5.1749409676125; Sun, 08 Jun 2025 12:07:56 -0700 (PDT) MIME-Version: 1.0 References: <20250605142457.04fff67a@hermes.local> <20250606133105.4b15794a@hermes.local> In-Reply-To: <20250606133105.4b15794a@hermes.local> From: Aniket singh Date: Mon, 9 Jun 2025 00:37:44 +0530 X-Gm-Features: AX0GCFush7ifpwkcV5zLxc5quyk4TGUj0Glk-oFEt4W0xS-NdICiIcLmEPPmOJ0 Message-ID: Subject: Re: Seeking help to configure DPDK 22 on Ubuntu 22.04.1 - "No probed ethernet devices" To: Stephen Hemminger Cc: Nishant Verma , users@dpdk.org, navaneetyvn.211cs234@nitk.edu.in Content-Type: multipart/alternative; boundary="0000000000004fe97b0637142efe" X-BeenThere: users@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK usage discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: users-bounces@dpdk.org --0000000000004fe97b0637142efe Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable 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=E2=80=AFAM Stephen Hemminger wrote: > On Fri, 6 Jun 2025 12:52:28 -0400 > Nishant Verma 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=E2=80=AFPM Aniket singh > > > 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=E2=80=AFAM, Stephen Hemminger < > > > stephen@networkplumber.org> wrote: > > > > > >> On Thu, 5 Jun 2025 23:23:39 +0530 > > >> Aniket singh 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, includi= ng > > >> > 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 supporte= d > > >> 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 > > > --0000000000004fe97b0637142efe Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi Stephen,

I checked with the above mentioned meth= od and it seems like the I210 NIC is supported by dpdk. Still I'm getti= ng the same problem with this NIC as well.
FYI, DPDK-19.11.1 was working= with the same NIC.=C2=A0=C2=A0

Thanks,
Aniket Singh<= /div>

On Sat, Jun 7, 2025 at 2:01=E2=80=AFAM Stephen H= emminger <stephen@networkp= lumber.org> wrote:
On Fri, 6 Jun 2025 12:52:28 -0400
Nishant Verma <vn= ish11@gmail.com> wrote:

> If your NIC is not part of this, then yes it's NOT SUPPORTED offic= ially.
>
> https://core.dpdk.org/supported/
>
>
> Regards,
> Nishant
>
>
> On Fri, Jun 6, 2025 at 12:27=E2=80=AFPM Aniket singh <aniketsingh84646@gmail.c= om>
> wrote:
>
> > Hi=C2=A0 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 supporte= d by DPDK?
> >
> > Thanks,
> > Aniket Singh
> >
> > On Fri, 6 Jun 2025 at 2:55=E2=80=AFAM, Stephen Hemminger <=C2= =A0
> > s= tephen@networkplumber.org> wrote:=C2=A0
> >=C2=A0
> >> On Thu, 5 Jun 2025 23:23:39 +0530
> >> Aniket singh <aniketsingh84646@gmail.com> wrote:
> >>=C2=A0
> >> > Hi Everyone,
> >> >
> >> > I'm trying to configure DPDK 22 on Ubuntu 22.04.3 LT= S and I'm facing an
> >> > issue when running the testpmd application.
> >> >
> >> > Whenever I execute:
> >> >
> >> >=C2=A0 =C2=A0 =C2=A0sudo ./dpdk-testpmd
> >> >
> >> > I get the following error:
> >> >
> >> >=C2=A0 =C2=A0 =C2=A0testpmd: No probed ethernet devices > >> >
> >> > I've followed the setup steps from the DPDK document= ation, including
> >> > hugepages allocation and binding NICs with vfio-pci, but= still=C2=A0
> >> encountering=C2=A0
> >> > the same issue.
> >> >
> >> > Could someone please help point out what might be missin= g 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 Ethe= rnet Connection
> >> > (17) I219-LM (rev 11)
> >> > 0000:01:00.0 Ethernet controller: Intel Corporation I210= Gigabit Network
> >> > Connection (rev 03)
> >> >=C2=A0
> >>
> >> 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 s= upported
> >> 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.
> >>
> >>=C2=A0

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=C2=A0 =C2=A0 =C2=A0= =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A00x125C
=C2=A0$ git grep ID_I226_V
intel/e1000/base/e1000_api.c:=C2=A0 =C2=A0case E1000_DEV_ID_I226_V:
intel/e1000/base/e1000_hw.h:#define E1000_DEV_ID_I226_V=C2=A0 =C2=A0 =C2=A0= =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A00x125C
intel/e1000/igc_ethdev.c:=C2=A0 =C2=A0 =C2=A0 =C2=A0{ RTE_PCI_DEVICE(IGC_IN= TEL_VENDOR_ID, E1000_DEV_ID_I226_V)=C2=A0 },=C2=A0 =C2=A0<<< yes

--0000000000004fe97b0637142efe--