DPDK usage discussions
 help / color / mirror / Atom feed
From: "Wiles, Keith" <keith.wiles@intel.com>
To: Milad Arabi <milad.arabi@gmail.com>
Cc: "users@dpdk.org" <users@dpdk.org>
Subject: Re: [dpdk-users] Found 0 usable devices
Date: Mon, 21 May 2018 17:07:33 +0000	[thread overview]
Message-ID: <B3AB9BBE-5B93-4B7A-A466-A33E9987099E@intel.com> (raw)
In-Reply-To: <CACbyiE8PVpVC6ZtGsMZcsrTSnRvDGhuTaMDyHT5veOThtU7ePQ@mail.gmail.com>



> On May 21, 2018, at 11:41 AM, Milad Arabi <milad.arabi@gmail.com> wrote:
> 
> Since I do not know anything about Eng-Sample NIC then no it's not. It is the original Intel network card pass through to CentOS from VMware.
> Do you think maybe the VMware cause this issue?

Could be, guess its back to google for passthru NICs in VMWare or how to set the NIC MAC address  in VMWare.

> 
> On Mon, May 21, 2018 at 8:55 PM, Wiles, Keith <keith.wiles@intel.com> wrote:
> 
> 
>> On May 21, 2018, at 11:16 AM, Milad Arabi <milad.arabi@gmail.com> wrote:
>> 
>> Hi Keith
>> Thank you for your reply.
>> Could you please check my output at:
>> https://asciinema.org/a/182678
>> 
>> I get this error:
>> PMD: eth_ixgbe_dev_init(): The EEPROM checksum is not valid: -1
> 
> Normally that means this is a Eng-Sample NIC, is it?
> 
> If it is then we have to find someone to program the EPROM to setup the NIC.
> 
> That is about all I know.
> 
>> 
>> any comment would be appreciated
>> 
>> 
>> On Mon, May 21, 2018 at 5:26 PM, Wiles, Keith <keith.wiles@intel.com> wrote:
>> 
>> 
>> > On May 21, 2018, at 4:37 AM, Milad Arabi <milad.arabi@gmail.com> wrote:
>> > 
>> > Hi there
>> > I try to with dpdk 17.08 on centos7.5 with other library,but I got this:
>> > 
>> >> [INFO]  Initializing DPDK. This will take a few seconds...
>> >> EAL: Detected 16 lcore(s)
>> >> EAL: Probing VFIO support...
>> >> EAL: PCI device 0000:0b:00.0 on NUMA socket -1
>> >> EAL:   Invalid NUMA socket, default to 0
>> >> EAL:   probe driver: 15ad:7b0 net_vmxnet3
>> >> EAL: PCI device 0000:13:00.0 on NUMA socket 1
>> >> EAL:   probe driver: 8086:10fb net_ixgbe
>> >> EAL: PCI device 0000:13:00.1 on NUMA socket -1
>> >> EAL:   Invalid NUMA socket, default to 0
>> >> EAL:   probe driver: 8086:10fb net_ixgbe
>> >> *[INFO]  Found 0 usable devices:*
>> > 
>> > 
>> > are these errors come from dpdk? and how I can solve this problem?
>> 
>> Did you use the dpdk-devbind.py tool in dpdk to bind the device to allow DPDK to use the device?
>> 
>> Also you may have to insmod the igb_uio.ko for pci_uio_generic modules in the kernel?
>> 
>> > 
>> > # ethtool -i ens224f1
>> >> driver: ixgbe
>> >> version: 5.3.7
>> >> firmware-version: 0x80000835, 1.949.0
>> >> expansion-rom-version:
>> >> bus-info: 0000:13:00.1
>> >> supports-statistics: yes
>> >> supports-test: yes
>> >> supports-eeprom-access: yes
>> >> supports-register-dump: yes
>> >> supports-priv-flags: yes
>> 
>> Regards,
>> Keith
>> 
>> 
> 
> Regards,
> Keith
> 
> 

Regards,
Keith

  parent reply	other threads:[~2018-05-21 17:07 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-21  9:37 Milad Arabi
2018-05-21 12:56 ` Wiles, Keith
2018-05-21 16:16   ` Milad Arabi
2018-05-21 16:25     ` Wiles, Keith
2018-05-21 16:41       ` Milad Arabi
2018-05-21 17:05         ` Wiles, Keith
2018-05-21 17:07         ` Wiles, Keith [this message]
2018-05-21 17:10           ` Milad Arabi

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=B3AB9BBE-5B93-4B7A-A466-A33E9987099E@intel.com \
    --to=keith.wiles@intel.com \
    --cc=milad.arabi@gmail.com \
    --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).