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 1C6EE46878 for ; Mon, 9 Jun 2025 15:42:45 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id E081840EDF; Mon, 9 Jun 2025 15:42:44 +0200 (CEST) Received: from mail-ed1-f46.google.com (mail-ed1-f46.google.com [209.85.208.46]) by mails.dpdk.org (Postfix) with ESMTP id AE10240EDB for ; Mon, 9 Jun 2025 15:42:42 +0200 (CEST) Received: by mail-ed1-f46.google.com with SMTP id 4fb4d7f45d1cf-6077dea37easo4572664a12.3 for ; Mon, 09 Jun 2025 06:42:42 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1749476562; x=1750081362; 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=omzTMQjitK6mvlELEFL7liUSHPUIig9/WVBDvD+Ox9s=; b=CwRAvE3Ycv8bbi3CqkjkedxSmEXsV4wlV3d1wiQly7tjwDhdImr4gpOcHBbYSK9EOi UCOrCtHxiwHuf6PisU2pA0+6dc3gIrjxt/sAfObTIbxG21Q48cX/i0xU8WLxh9vs3zuI y0t4vLGQwTArOfGRjmgxWCn5sEG6g+MpknC52CIC0ewhc7HhW+YX0GpdJwG10PoneX1w QOV4CDl5sMwT/ro6XW8xqWBJRlxcRAZXnbZ4+lE5sBBb+seWZ1LOxPlYdXgLFyqlmX8Q 8p1C7m5FW0CfINClo4wqD5RrAwWtbcQm02Lv/vwC9YcMh4zFC55uWA2h0pkiQaCri/Mt y8AQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1749476562; x=1750081362; 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=omzTMQjitK6mvlELEFL7liUSHPUIig9/WVBDvD+Ox9s=; b=oxeJHbMBCwa8OOAxhzxNNiTfRr/8xEeXBz1TwTQKObzvExtBVpwPmL7XE9SQYm69NC lIrGJL5QVSB3pErobmD6RAfk7qg5R/5BD0TujhVhhMS3/2TjunCSZz3IqjWNHIx/KjNX Zk1H1VePRLa99tag0Avr+klCptPORHTGGAAT8A4iDoUGwXj1WGXPrYkTda/WrZ4Ye1V6 w3bY8cbySeS9sGgBZ/QMyqMeYZnD3QfxTQdG0uudZ6J3oOEoFgEOzZc8nmAHU6z0LL7y q2my2j0Kmx003/uagddSK9ugNvXgU+ZoX7yuSyHfGL7Q8ey99oUmF9nkRiKEb5d+PAFb M59Q== X-Forwarded-Encrypted: i=1; AJvYcCVcG1VYckKxNDChFC8N8MNFK9ynoISTNOGrQYpP8zvHKbbtNaU+2nxxu8d7NrHHyFN3wz1t+Q==@dpdk.org X-Gm-Message-State: AOJu0Yy5wrTebL5hE79FQG9AMqigEVB1hCVxHVbweg2WP+PndtFgC7yu fazIaRBSgghW2MTrpQDHrt75WYwLbSOPFiE0z26rmYbZmOVomBubc4eebGeWntICypjludBM8CI G95Ag50N1lPkQ3FdtfP76d9vL+gjDVGrbTO17 X-Gm-Gg: ASbGncvInZ0LcAW9tDz6hWyYJYiPMjV7CfiMqacJN98klKAHl4cGj+UU4wW9MRMqqmZ FJ+/IFH+b9lLLfjw6Q6zVe6P1HBTTHfSDl/GrSsVrPMRNCnwtIB/oCtOslUiIEUmy5ZtOGXjWZd CUc6QCFzRJYyU/j0w7TKgk8Ps9BXQ4oj5mUCA6600YyQcD X-Google-Smtp-Source: AGHT+IFFBoaDiRFnGda/NePxEwgZr5lpGMeFCcudcIgVt/uWa7dZRHoDl9eGNKiQoTtIu9vfXPAD08Lxv+nx1oMcOJ0= X-Received: by 2002:a17:906:f58e:b0:ad8:a9fc:8127 with SMTP id a640c23a62f3a-ade1a9c7b43mr1231681466b.41.1749476561758; Mon, 09 Jun 2025 06:42:41 -0700 (PDT) MIME-Version: 1.0 References: <20250605142457.04fff67a@hermes.local> <20250606133105.4b15794a@hermes.local> In-Reply-To: From: Nishant Verma Date: Mon, 9 Jun 2025 09:42:30 -0400 X-Gm-Features: AX0GCFurW_OU7xurRcE8tOCYDLw9LNzrmlhgkGbBHW9-MCI5vrlkyzO-VZecclI Message-ID: Subject: Re: Seeking help to configure DPDK 22 on Ubuntu 22.04.1 - "No probed ethernet devices" To: Aniket singh Cc: Stephen Hemminger , users@dpdk.org Content-Type: multipart/alternative; boundary="00000000000001bdd5063723c12a" 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 --00000000000001bdd5063723c12a Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Aniket, your both NIC's are supported. just do one thing, bootup your server. run this sequence of the command and share. 1) Reboot 2) ip a 3) lspci|grep Ether 4) lsmod | grep vfio 5) ./dpdk-devbind --status 6) ./dpdk-devbind -u 7) ./dpdk-devbind --status 8) ./dpdk-devbind -b vfio-pci Make sure the vfio_pci is loaded if not load that before step 6. Thanks. On Sun, Jun 8, 2025 at 3:07=E2=80=AFPM Aniket singh wrote: > 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 < > stephen@networkplumber.org> 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 officiall= y. >> > >> > https://core.dpdk.org/supported/ >> > >> > >> > Regards, >> > Nishant >> > >> > >> > On Fri, Jun 6, 2025 at 12:27=E2=80=AFPM 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 b= y >> 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, >> 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 guid= e >> 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 support= ed >> > >> 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 >> >> >> --00000000000001bdd5063723c12a Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

Aniket, your b= oth NIC's are supported.=C2=A0
just do one thing, boot= up your server. run this sequence of the command and share.
1) = Reboot
2) ip a
3) lspci|grep Ether=C2=A0
4) lsmod | grep vfio
5)=C2=A0./dpdk-devbind --status
6) ./dpdk-devbind -u <the PCI of 219=C2=A0= =C2=A0>
7)=C2=A0<= span style=3D"color:rgb(7,55,99);font-family:verdana,sans-serif;white-space= :unset">./dpdk-devbind --status
8)=C2=A0./dpdk-devbind -b vfio-pci=C2=A0<the PCI of 219=C2=A0=C2=A0>

Make sure the vfio_pci is loaded if not load= =C2=A0that before=C2=A0step 6.

T= hanks.


On Sun, Jun 8, 2025 at 3:07=E2=80=AFPM Aniket singh &= lt;aniketsi= ngh84646@gmail.com> wrote:
Hi Stephen,

I checked with the ab= ove mentioned method and it seems like the I210 NIC is supported by dpdk. S= till I'm getting the same problem with this NIC as well.
FYI, DPDK-1= 9.11.1 was working with the same NIC.=C2=A0=C2=A0

Thanks= ,
Aniket Singh

On Sat, Jun 7, 2025 at 2:01=E2=80=AFAM Stephen Hemmi= nger <st= ephen@networkplumber.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

--00000000000001bdd5063723c12a--