[dpdk-users] Found 0 usable devices
Wiles, Keith
keith.wiles at intel.com
Mon May 21 18:25:56 CEST 2018
On May 21, 2018, at 11:16 AM, Milad Arabi <milad.arabi at gmail.com<mailto:milad.arabi at 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 at intel.com<mailto:keith.wiles at intel.com>> wrote:
> On May 21, 2018, at 4:37 AM, Milad Arabi <milad.arabi at gmail.com<mailto:milad.arabi at 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
More information about the users
mailing list