DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Al Patel <alps.oss@gmail.com>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] Issue with binding NIC of type 82545EM to dpdk
Date: Tue, 29 Mar 2016 17:26:53 +0100	[thread overview]
Message-ID: <56FAACCD.6020909@intel.com> (raw)
In-Reply-To: <CAF9p440ikVd4bsOemwow-dMrK_LGXaDODrPqS_3r60cyTbhGDA@mail.gmail.com>

On 3/29/2016 3:11 PM, Al Patel wrote:
> Hi,
> 
> I am having an issue with binding a nic of type 82545EM to dpdk. I am using
> a
> fedoracore23 VM on MAC with VMFusion.
> 
> ./dpdk_nic_bind.py -b uio_pci_generic 0000:02:02.0
> Error: bind failed for 0000:02:02.0 - Cannot bind to driver uio_pci_generic
> Error: unbind failed for 0000:02:02.0 - Cannot open
> /sys/bus/pci/drivers//unbind
> 
> it is unbound from e1000, repeating the command:
> 
> ./dpdk_nic_bind.py -b uio_pci_generic 0000:02:02.0
> Error: bind failed for 0000:02:02.0 - Cannot bind to driver uio_pci_generic
> 
> I repeated the same test on a ubuntu vm running on Virtualbox with
> NIC type 82450EM
> 
> In this case, the device is able to bind successfully to uio_pci_generic
> driver.
> 
> There is a igb_uio module that present. The device cannot be bound to the
> igb_uio
> driver.

Hi Al,

You are trying to bind to the driver "uio_pci_generic" not to the
"igb_uio", is it typo? If not, can you please double check if
"uio_pci_generic" module inserted.
Or bind device to "igb_uio":
"./dpdk_nic_bind.py -b igb_uio 0000:02:02.0"

Regards,
ferruh

  reply	other threads:[~2016-03-29 16:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-29 14:11 Al Patel
2016-03-29 16:26 ` Ferruh Yigit [this message]
2016-03-29 17:14   ` Al Patel
2016-03-30  0:51     ` Lu, Wenzhuo
2016-03-30 12:59       ` Al Patel

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=56FAACCD.6020909@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=alps.oss@gmail.com \
    --cc=dev@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).