From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-yw0-f181.google.com (mail-yw0-f181.google.com [209.85.161.181]) by dpdk.org (Postfix) with ESMTP id C62BE2BE2 for ; Wed, 30 Mar 2016 14:59:39 +0200 (CEST) Received: by mail-yw0-f181.google.com with SMTP id g127so56831306ywf.2 for ; Wed, 30 Mar 2016 05:59:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=nip/SQA+JFkufhduzmhfAXO1/AUG9lwCV9BwAhyM+nI=; b=fH60Z6elG6CBNQWWypyJpAZ2rqkGalF01IxAIuS/dYDBM/snyFonudoGxVwePcxDp7 UeO5MYME7sqXprjCPdhE00pMc7/CXTrseHEvZRQ+J37CevBtzEBF+E8gB1BYXHAMrKUf pw3+8ZKHqxFaaJHBavUgk6RejBXOKDzFPKXlMSuVA9y/yaLoa90W1NNa2KFzVZqg+3X4 Lg7Uldlu1KjQegii3TT9iTkfQC25vXV8+pLPYcHuNSgD40dSnbP8graoRBlM75KA2r2e XDK2XKRAEiOOPx3shURGSc6CiBwpS9Cc8HYtaCMWkdwx2GqJzwvz+N+2sIqUW0b2AawH sBkw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=nip/SQA+JFkufhduzmhfAXO1/AUG9lwCV9BwAhyM+nI=; b=khJ9yScF5jdjGDMYc+kWqL4B07qWOAltA4mx/4XHv6BB9O9dZ8xpNkVkIO8CmeyNnA KPmeW7FrcuN9vzF7MRK8MyVl9Z4sjJOlgpeP2XjVQgQdaNQzRE3PdjR/zLj6XF5Z2v/P Boqyrj37U6EJ1HlrdhMBK9OMHx3S298um4nhSbBWxZlrU07qzfqC/mq1s5hHcqxlqdOW jBQQybyWqXaIt2qGSCaOiW8r99CzAxaTdb6t2LTXGcF0zX1VmmpAH5WqW9LoAMYi3n9b 6ZwKCLy1YkvIlqHi2gkp8iCn5kloiUN82Fl2qqgZpszTlAJKTF2vkE6MsRESVm3wDJSJ 4RNA== X-Gm-Message-State: AD7BkJJrhcF5daX3ex75YH90yi/OCkOtBI35G7LXC/9xsBDnMCtISmEIHwq52LjTQaYRa3JgpknX2LkMXAHaAA== MIME-Version: 1.0 X-Received: by 10.37.86.9 with SMTP id k9mr4072227ybb.119.1459342779284; Wed, 30 Mar 2016 05:59:39 -0700 (PDT) Received: by 10.13.229.194 with HTTP; Wed, 30 Mar 2016 05:59:39 -0700 (PDT) In-Reply-To: <6A0DE07E22DDAD4C9103DF62FEBC09090343FF3E@shsmsx102.ccr.corp.intel.com> References: <56FAACCD.6020909@intel.com> <6A0DE07E22DDAD4C9103DF62FEBC09090343FF3E@shsmsx102.ccr.corp.intel.com> Date: Wed, 30 Mar 2016 08:59:39 -0400 Message-ID: From: Al Patel To: "Lu, Wenzhuo" Cc: "Yigit, Ferruh" , "dev@dpdk.org" Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.15 Subject: Re: [dpdk-dev] Issue with binding NIC of type 82545EM to dpdk X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Mar 2016 12:59:40 -0000 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 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. >