From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wi0-f196.google.com (mail-wi0-f196.google.com [209.85.212.196]) by dpdk.org (Postfix) with ESMTP id E838CB0AC for ; Wed, 14 May 2014 17:44:39 +0200 (CEST) Received: by mail-wi0-f196.google.com with SMTP id f8so1203142wiw.7 for ; Wed, 14 May 2014 08:44:47 -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:content-type; bh=uGf0hyoNwPCbqOns+CZbws/1WAxJFkRh64P+M38OnEs=; b=Zd/nKwdBkqi/rUmctR2HbgokuRP0nhF/sQkIpwaEq3lWz5LZPXU39wSZpoaCIQq54c gSoZDmNqzeNQjb2uTHu9pvjN+pUL+PDRI05A9E4dAJf1iQFAtFVpIcK2OAt5deTs595D N4W4fXzyfdYR/V9xJp64Mtm5pUfRjDtNkP4c1f26YGjuV39NvRNWL8khHpfM3Y+q2b/2 PYJDnJWLSqKqTKr6Kn5nOpgL8CFVgP32HjMLo6uPNm50XLonT3qvSChI4Y0yOv1oxGJ9 b3SwQUUtHJ0eOJM/f+GfDB38E/huDQCyeXEi34xBrfi5kwcJdc6h92I1aWXP02awb3Un c1zQ== MIME-Version: 1.0 X-Received: by 10.180.187.111 with SMTP id fr15mr26707823wic.57.1400082287576; Wed, 14 May 2014 08:44:47 -0700 (PDT) Received: by 10.194.164.5 with HTTP; Wed, 14 May 2014 08:44:47 -0700 (PDT) In-Reply-To: References: <1490308.sncVW4PuBc@xps13> Date: Wed, 14 May 2014 18:44:47 +0300 Message-ID: From: Helmut Sim To: Thomas Monjalon Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.15 Cc: dev@dpdk.org Subject: Re: [dpdk-dev] fail to bind '82541GI Gigabit Ethernet Controller' to IGB_UIO driver 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, 14 May 2014 15:44:40 -0000 Hi Thomas, I made the required change in order to support the 82541GI chipset and I was able to bind it successfully to the igb_uio ==> thank for your advise. however i am stll not able to bind the 82575EB... although it looks like it is already supported ;( I see there is a 82575EB_COPPER and a 82575EB_FIBER_SERDES, how can i tell if mine is one of them? it is a Dual Port PCI-E X4 Gigabit Server Adapter 575T ( http://www.winyao.com/en/product_view_20_117.html). Thanks On Wed, May 14, 2014 at 5:53 PM, Helmut Sim wrote: > Thanks Thomas for your quick answer. > > Meantime I tried a different device, which is supported according to the > rule you mentioned. > it is a 82575EB but i got the exact same behavior. > > # grep 'RTE_PCI_DEV_ID_DECL.*82575' > lib/librte_eal/common/include/rte_pci_dev_ids.h > RTE_PCI_DEV_ID_DECL_IGB(PCI_VENDOR_ID_INTEL, E1000_DEV_ID_82575EB_COPPER) > RTE_PCI_DEV_ID_DECL_IGB(PCI_VENDOR_ID_INTEL, > E1000_DEV_ID_82575EB_FIBER_SERDES) > RTE_PCI_DEV_ID_DECL_IGB(PCI_VENDOR_ID_INTEL, > E1000_DEV_ID_82575GB_QUAD_COPPER) > > > # ./tools/pci_unbind.py --status > > Network devices using IGB_UIO driver > ==================================== > > > Network devices using kernel driver > =================================== > 0000:01:00.0 '82575EB Gigabit Network Connection' if=p1p1 drv=igb > unused= > 0000:01:00.1 '82575EB Gigabit Network Connection' if=p1p2 drv=igb > unused= > 0000:03:00.0 'RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller' > if=eth0 drv=r8169 unused= *Active* > 0000:06:0c.0 '82541GI Gigabit Ethernet Controller' if=p3p1 drv=e1000 > unused= *Active* > 0000:06:0d.0 '82541GI Gigabit Ethernet Controller' if=rename6 drv=e1000 > unused= > > Other network devices > ===================== > > > # ./tools/pci_unbind.py --bind=igb_uio 01:00.0 > Error: bind failed for 0000:01:00.0 - Cannot bind to driver igb_uio > (/sys/bus/pci/drivers/igb_uio/bind) > Error: unbind failed for 0000:01:00.0 - Cannot open > /sys/bus/pci/drivers//unbind > > > # ./tools/pci_unbind.py --status > > Network devices using IGB_UIO driver > ==================================== > > > Network devices using kernel driver > =================================== > 0000:01:00.1 '82575EB Gigabit Network Connection' if=p1p2 drv=igb > unused= > 0000:03:00.0 'RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller' > if=eth0 drv=r8169 unused= *Active* > 0000:06:0c.0 '82541GI Gigabit Ethernet Controller' if=p3p1 drv=e1000 > unused= *Active* > 0000:06:0d.0 '82541GI Gigabit Ethernet Controller' if=rename6 drv=e1000 > unused= > > Other network devices > ===================== > 0000:01:00.0 '82575EB Gigabit Network Connection' unused= > > # > > I guess something is wrong with my environment. > BTW I am running as a root. > > and this is the objcts under the driver: > # ls -l /sys/bus/pci/drivers/igb_uio/ > total 0 > --w------- 1 root root 4096 May 14 17:40 bind > lrwxrwxrwx 1 root root 0 May 14 17:48 module -> > ../../../../module/igb_uio > --w------- 1 root root 4096 May 14 17:48 new_id > --w------- 1 root root 4096 May 14 17:48 remove_id > --w------- 1 root root 4096 May 14 17:39 uevent > --w------- 1 root root 4096 May 14 17:48 unbind > > > Thanks! > > > > > On Wed, May 14, 2014 at 5:45 PM, Thomas Monjalon < > thomas.monjalon@6wind.com> wrote: > >> Hi, >> >> 2014-05-14 17:27, Helmut Sim: >> > unlike previous cases I went over in this forum, this NIC supposed to be >> > supported (or maybe i read it incorrectly???): >> > >> > # cat lib/librte_eal/common/include/rte_pci_dev_ids.h | grep 82541GI >> > #define E1000_DEV_ID_82541GI 0x1076 >> > #define E1000_DEV_ID_82541GI_LF 0x107C >> > #define E1000_DEV_ID_82541GI_MOBILE 0x1077 >> >> This device is known but not supported. >> >> You should use >> # grep 'RTE_PCI_DEV_ID_DECL.*8254' >> lib/librte_eal/common/include/rte_pci_dev_ids.h >> RTE_PCI_DEV_ID_DECL_EM(PCI_VENDOR_ID_INTEL, E1000_DEV_ID_82540EM) >> RTE_PCI_DEV_ID_DECL_EM(PCI_VENDOR_ID_INTEL, >> E1000_DEV_ID_82545EM_COPPER) >> RTE_PCI_DEV_ID_DECL_EM(PCI_VENDOR_ID_INTEL, >> E1000_DEV_ID_82545EM_FIBER) >> RTE_PCI_DEV_ID_DECL_EM(PCI_VENDOR_ID_INTEL, >> E1000_DEV_ID_82546EB_COPPER) >> RTE_PCI_DEV_ID_DECL_EM(PCI_VENDOR_ID_INTEL, >> E1000_DEV_ID_82546EB_FIBER) >> RTE_PCI_DEV_ID_DECL_EM(PCI_VENDOR_ID_INTEL, >> E1000_DEV_ID_82546EB_QUAD_COPPER) >> >> The dedicated page for this information is: >> http://dpdk.org/doc/nics >> >> You should try to enable this device in the code and see what happens. >> Maybe that its support is straightforward. >> >> Thanks for reporting >> -- >> Thomas >> > > > > On Wed, May 14, 2014 at 5:45 PM, Thomas Monjalon < > thomas.monjalon@6wind.com> wrote: > >> Hi, >> >> 2014-05-14 17:27, Helmut Sim: >> > unlike previous cases I went over in this forum, this NIC supposed to be >> > supported (or maybe i read it incorrectly???): >> > >> > # cat lib/librte_eal/common/include/rte_pci_dev_ids.h | grep 82541GI >> > #define E1000_DEV_ID_82541GI 0x1076 >> > #define E1000_DEV_ID_82541GI_LF 0x107C >> > #define E1000_DEV_ID_82541GI_MOBILE 0x1077 >> >> This device is known but not supported. >> >> You should use >> # grep 'RTE_PCI_DEV_ID_DECL.*8254' >> lib/librte_eal/common/include/rte_pci_dev_ids.h >> RTE_PCI_DEV_ID_DECL_EM(PCI_VENDOR_ID_INTEL, E1000_DEV_ID_82540EM) >> RTE_PCI_DEV_ID_DECL_EM(PCI_VENDOR_ID_INTEL, >> E1000_DEV_ID_82545EM_COPPER) >> RTE_PCI_DEV_ID_DECL_EM(PCI_VENDOR_ID_INTEL, >> E1000_DEV_ID_82545EM_FIBER) >> RTE_PCI_DEV_ID_DECL_EM(PCI_VENDOR_ID_INTEL, >> E1000_DEV_ID_82546EB_COPPER) >> RTE_PCI_DEV_ID_DECL_EM(PCI_VENDOR_ID_INTEL, >> E1000_DEV_ID_82546EB_FIBER) >> RTE_PCI_DEV_ID_DECL_EM(PCI_VENDOR_ID_INTEL, >> E1000_DEV_ID_82546EB_QUAD_COPPER) >> >> The dedicated page for this information is: >> http://dpdk.org/doc/nics >> >> You should try to enable this device in the code and see what happens. >> Maybe that its support is straightforward. >> >> Thanks for reporting >> -- >> Thomas >> > >