From: Stephen Hemminger <stephen@networkplumber.org>
To: "jonathan.ribas@fraudbuster.mobi" <jonathan.ribas@fraudbuster.mobi>
Cc: users@dpdk.org
Subject: Re: [dpdk-users] Issue with i40e on X710: rte_eth_dev_count returns 0, i40e_aq_get_phy_capabilities returns I40E_ERR_UNKNOWN_PHY
Date: Wed, 12 Jul 2017 08:07:26 -0700 [thread overview]
Message-ID: <20170712080726.605cde41@xeon-e3> (raw)
In-Reply-To: <9b28bd6e-2982-acfc-8c5a-2cb1e3ed52c9@fraudbuster.mobi>
On Wed, 12 Jul 2017 15:50:58 +0200
"jonathan.ribas@fraudbuster.mobi" <jonathan.ribas@fraudbuster.mobi> wrote:
> Hi all,
>
> We got a bunch of X710 NIC and cant use them with our custom app.
> As the topic says, rte_eth_dev_count returns 0. And after a quick
> investigation with testpmd, we saw that i40e_aq_get_phy_capabilities
> returns 'I40E_ERR_UNKNOWN_PHY'.
With I40E always make sure and update firmware as first step.
Last I checked, some Intel NIC's do not support 3rd party SFP modules.
next prev parent reply other threads:[~2017-07-12 15:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-12 13:50 jonathan.ribas
2017-07-12 15:07 ` Stephen Hemminger [this message]
2017-07-17 8:58 ` jonathan.ribas
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=20170712080726.605cde41@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=jonathan.ribas@fraudbuster.mobi \
--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).