Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 12 Sep 2017 09:45:08 +0100
From:      Matthew Seaman <matthew@FreeBSD.org>
To:        freebsd-questions@freebsd.org
Subject:   Re: Need help
Message-ID:  <7f054774-5538-6884-fb5d-be155456d081@freebsd.org>
In-Reply-To: <alpine.BSF.2.00.1709121013410.59850@pochta.canmos.ru>
References:  <alpine.BSF.2.00.1709121013410.59850@pochta.canmos.ru>

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help
On 12/09/17 08:32, Igor V. Ruzanov wrote:
> Hello, FreeBSD colleagues!
> 
> I have modern network card Intel i350T2V2 (peripheral dual gigabit port
> NIC). And as far as i know all Intel cards should be normally detected
> by the system. But with this NIC i have some troubles:
> - the system sees the card as some ethernet device but cannot find
> proper (igb) driver:
> pcib6: <ACPI PCI-PCI bridge> irq 47 at device 3.2 on pci0
> pci6: <ACPI PCI bus> on pcib6
> pci6: <network, ethernet> at device 0.0 (no driver attached)
> pci6: <network, ethernet> at device 0.1 (no driver attached)
> - its from dmesg log.
> 
> Fnd `pciconf -lcvb' says:
> none75@pci0:6:0:0:      class=0x020000 card=0x00008086 chip=0x151f8086
> rev=0x01 hdr=0x00
>     vendor     = 'Intel Corporation'
>     class      = network
>     subclass   = ethernet
>     bar   [10] = type Memory, range 32, base 0x91920000, size 131072,
> enabled
>     bar   [18] = type I/O Port, range 32, base 0x2020, size 32, enabled
>     bar   [1c] = type Memory, range 32, base 0x919c4000, size 16384,
> enabled
>     cap 01[40] = powerspec 3  supports D0 D3  current D0
>     cap 05[50] = MSI supports 1 message, 64 bit, vector masks
>     cap 11[70] = MSI-X supports 10 messages
>                  Table in map 0x1c[0x0], PBA in map 0x1c[0x2000]
>     cap 10[a0] = PCI-Express 2 endpoint max data 256(512) FLR RO NS link
> x4(x4)
>                  speed 5.0(5.0) ASPM disabled(L0s/L1)
>     ecap 0001[100] = AER 2 0 fatal 0 non-fatal 1 corrected
>     ecap 000e[150] = ARI 1
>     ecap 0010[160] = SRIOV 1
>     ecap 0017[1a0] = TPH Requester 1
>     ecap 0018[1c0] = LTR 1
>     ecap 000d[1d0] = ACS 1
> none76@pci0:6:0:1:      class=0x020000 card=0x00008086 chip=0x151f8086
> rev=0x01 hdr=0x00
>     vendor     = 'Intel Corporation'
>     class      = network
>     subclass   = ethernet
>     bar   [10] = type Memory, range 32, base 0x91900000, size 131072,
> enabled
>     bar   [18] = type I/O Port, range 32, base 0x2000, size 32, enabled
>     bar   [1c] = type Memory, range 32, base 0x919c0000, size 16384,
> enabled
>     cap 01[40] = powerspec 3  supports D0 D3  current D0
>     cap 05[50] = MSI supports 1 message, 64 bit, vector masks
>     cap 11[70] = MSI-X supports 10 messages
>                  Table in map 0x1c[0x0], PBA in map 0x1c[0x2000]
>     cap 10[a0] = PCI-Express 2 endpoint max data 256(512) FLR RO NS link
> x4(x4)
>                  speed 5.0(5.0) ASPM disabled(L0s/L1)
>     ecap 0001[100] = AER 2 0 fatal 0 non-fatal 1 corrected
>     ecap 000e[150] = ARI 1
>     ecap 0010[160] = SRIOV 1
>     ecap 0017[1a0] = TPH Requester 1
>     ecap 000d[1d0] = ACS 1
> 
> My server is:
> - system is FreeBSD-10.3-RELEASE-p20
> - motherboard: Intel S2600WT (dual CPU socket board)
> - one CPU installed
> 
> Maybe someone has experience with this inetl NIC? As seen from pciconf
> output the NIC has a set of VFs (Virtual Functions) needed in
> virtualization environments. And chip id is 0x151F8086 - the id that
> igb-driver does not know about. Maybe i need some preconfiguration of
> this card? Or this device is not compatible with non-virtualization
> systems like usual physical server?
> 
> Big thanks in advance!

Pretty much all Intel NICs should be supported.  i350 certainly should
use the igb(4) driver.

Can you try booting a more recent version of FreeBSD from a memstick
image and see if the NIC is properly detected there?  If that works,
then upgrading should solve your problems.  (11.1 probably your best
bet, but there's also 10.4 in the late stages of the release process.)

Beyond that I suggest taking your question to the freebsd-net@ list as
you're likely to come to the attention of the people who write the
drivers there.

	Cheers,

	Matthew




Want to link to this message? Use this URL: <http://docs.FreeBSD.org/cgi/mid.cgi?7f054774-5538-6884-fb5d-be155456d081>