All of lore.kernel.org
 help / color / mirror / Atom feed
From: Al Patel <alps.oss@gmail.com>
To: "Lu, Wenzhuo" <wenzhuo.lu@intel.com>
Cc: "Yigit, Ferruh" <ferruh.yigit@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: Issue with binding NIC of type 82545EM to dpdk
Date: Wed, 30 Mar 2016 08:59:39 -0400	[thread overview]
Message-ID: <CAF9p441X6yaEhaT3kW0axgiN_RtrS+R+LL96audhBFvbawr-Zw@mail.gmail.com> (raw)
In-Reply-To: <6A0DE07E22DDAD4C9103DF62FEBC09090343FF3E@shsmsx102.ccr.corp.intel.com>

Hi Lu,

I do see the module there, but seems it is built against incorrect kernel
version and thus it is not loading:

# insmod ./dpdk/kmod/igb_uio.ko
insmod: ERROR: could not insert module ./dpdk/kmod/igb_uio.ko: Invalid
module format


dmesg:

[54394.611703] igb_uio: version magic '4.2.3-300.fc23.x86_64 SMP mod_unload
' should be '4.4.6-300.fc23.x86_64 SMP mod_unload '

uname -a:

# uname -a
Linux kube-node1 4.4.6-300.fc23.x86_64 #1 SMP Wed Mar 16 22:10:37 UTC 2016
x86_64 x86_64 x86_64 GNU/Linux


I removed that kernel source and rebuild it - now it is loading and I am
able to find the device to igb_uio and
do see /dev/uio0 created.

I do see the device in dpdk now.

Thanks much.
-a


On Tue, Mar 29, 2016 at 8:51 PM, Lu, Wenzhuo <wenzhuo.lu@intel.com> wrote:

> Hi Al,
>
> > -----Original Message-----
> > From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Al Patel
> > Sent: Wednesday, March 30, 2016 1:14 AM
> > To: Yigit, Ferruh
> > Cc: dev@dpdk.org
> > Subject: Re: [dpdk-dev] Issue with binding NIC of type 82545EM to dpdk
> >
> > Ferruh,
> >
> > On my fedora23, I don't have igb_uio
> >
> > # modprobe igb_uio
> > modprobe: FATAL: Module igb_uio not found in directory
> > /lib/modules/4.4.6-300.fc23.x86_64
> After compiling dpdk, normally you can find igb_uio here,
> dpdk/x86_64-native-linuxapp-gcc/kmod/igb_uio.ko.
> Please refer http://www.dpdk.org/doc/guides/linux_gsg/build_dpdk.html.
>

      reply	other threads:[~2016-03-30 12:59 UTC|newest]

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

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=CAF9p441X6yaEhaT3kW0axgiN_RtrS+R+LL96audhBFvbawr-Zw@mail.gmail.com \
    --to=alps.oss@gmail.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=wenzhuo.lu@intel.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.