Alexey,
We can not (reliably) map the name "I219V" to a PCIe device.
Use lspci(8) to ascertain the device id#, and then use modinfo(8)
to see if that device ID is listed on one of the "alias" lines.
Finally, given dmesg output that you posted earlier, if the
NVM checksum is bad, it really won't matter if your driver
supports the hardware or not. The driver will not load if
the hardware has been corrupted.
- Don
=====================================================
More info ...
(1) The problem with using the "I219-V" string ...
On this Fedora 22 system:
[nuc01]$ grep I219V /usr/share/hwdata/pci.ids
[nuc01]$
This returns nothing! The string "I219V" isn't valid
for a Fedora 22 device branding string!
[nuc01]$ grep I219-V /usr/share/hwdata/pci.ids
1570 Ethernet Connection I219-V
15b8 Ethernet Connection (2) I219-V
15d6 Ethernet Connection (5) I219-V
15d8 Ethernet Connection (4) I219-V
[nuc01]$
There are four different device ID's associated with this
"I219-V" branding string. This is why you really, really
must supply the device ID to get an answer to your question.
(2) Using modinfo(8) to check a device driver for support for vendor
"8086" (Intel) and device ID "1570", "15b8", "15d6", or "15d8".
The output is many lines long (many device IDs are supported
by 'e1000e'). And, as it turns out, only TWO of the four are
supported in driver installed on my system.
---------
LONG-FORM
---------
[nuc01]$ modinfo e1000e
filename:
/lib/modules/4.4.12-200.fc22.x86_64/kernel/drivers/net/ethernet/intel/e1000e/e1000e.ko.xz
version: 3.2.6-k
license: GPL
description: Intel(R) PRO/1000 Network Driver
author: Intel Corporation, <linux.n...@intel.com>
srcversion: 73DD21C4B96AB714F3916AF
yes!-> alias: pci:v00008086d000015B8sv*sd*bc*sc*i*
alias: pci:v00008086d000015B7sv*sd*bc*sc*i*
yes!-> alias: pci:v00008086d00001570sv*sd*bc*sc*i*
alias: pci:v00008086d0000156Fsv*sd*bc*sc*i*
---<snip>---
alias: pci:v00008086d0000105Fsv*sd*bc*sc*i*
alias: pci:v00008086d0000105Esv*sd*bc*sc*i*
depends: ptp
intree: Y
vermagic: 4.4.12-200.fc22.x86_64 SMP mod_unload
---<snip>---
----------
SHORT-FORM
----------
[nuc01]$ modinfo e1000e| egrep -i '15(70|b8|d[68])'
alias: pci:v00008086d000015B8sv*sd*bc*sc*i*
alias: pci:v00008086d00001570sv*sd*bc*sc*i*
(3) Now, I don't have an "I210-V" available, so I'll just use my
desktop ...
Using lspci(8) to find the PCIe device ID for my Ethernet device ...
[nuc01]$ lspci -nn | grep -i net
00:19.0 Ethernet controller [0200]: Intel Corporation Ethernet
Connection (3) I218-LM [8086:15a2] (rev 03)
Do you see "[8086:15a2]"?
That means the Ethernet device in this NUC has vendor ID "8086"
(Intel) and device ID "15a2" which, using the pci.ids file, maps
to the branding string "Ethernet Connection (3) I218-LM".
Hope this helps
On 07/15/2016 01:53 AM, Alexey Muranov wrote:
> Could you please confirm if e1000e version 3.2.6-k supports I219-V too? This
> is the version provided with Ubuntu 16.04 installation image.
>
> I have checked that my "BIOS" (EFI Setup?) is of the latest available version.
>
> I have also tried to install e1000e 3.3.4 with `modprobe` and
> `update-initramfs`. This
> seemed to work, except that it tainted the kernel (because the new module was
> not signed) and the NVM checksum was still invalid (i guess, naturally?).
>
> I have contacted Intel customer support, but i am not sure if they would
> help. I219-V was not even listed in the contact form.
>
> - Alexey.
>
> On 11 Jul 2016, at 18:02, Alexander Duyck <alexander.du...@gmail.com> wrote:
>
>> So the log more ore less says why the interface isn't loading. The
>> NVM Checksum validation is reporting that the checksum isn't valid.
>> You should check with your laptop manufacturer to see about updating
>> it. Most likely this may be included as part of a BIOS update but
>> your laptop manufacturer could provide you with more details.
>>
>> - Alex
>>
>> On Mon, Jul 11, 2016 at 1:25 AM, Alexey Muranov
>> <alexey.mura...@gmail.com> wrote:
>>> Thanks for looking into it. I've decided to only include the output of
>>> `dmesg | grep e1000e`, please let me know if you need more:
>>>
>>> $ dmesg | grep e1000e
>>> [ 5.643760] e1000e: Intel(R) PRO/1000 Network Driver - 3.2.6-k
>>> [ 5.643761] e1000e: Copyright(c) 1999 - 2015 Intel Corporation.
>>> [ 5.644308] e1000e 0000:00:1f.6: Interrupt Throttling Rate
>>> (ints/sec) set to dynamic conservative mode
>>> [ 5.877838] e1000e 0000:00:1f.6: The NVM Checksum Is Not Valid
>>> [ 5.907340] e1000e: probe of 0000:00:1f.6 failed with error -5
>>>
>>>
>>> - Alexey.
>>>
>>> On 11 Jul 2016, at 01:11, Alexander Duyck <alexander.du...@gmail.com> wrote:
>>>
>>>> It might be useful if you can provide the dmesg output for your system
>>>> after boot. More often then not when a device doesn't load when the
>>>> driver is loaded there is usually something in the error log
>>>> indicating an issue such as an EEPROM problem or whatnot. If you
>>>> could provide that we can probably narrow down the root cause further.
>>>>
>>>> - Alex
>>>>
>>>> On Sun, Jul 10, 2016 at 8:49 AM, Neftin, Sasha <sasha.nef...@intel.com>
>>>> wrote:
>>>>> I have no idea. From your email I can see that you talk about ASUS
>>>>> laptop. I suggest you contact ASUS support too.
>>>>> Also, please, check your BIOS advanced settings: Onboard Devices
>>>>> Configuration - Onboard PCIE LAN - is this option enabled?
>>>>>
>>>>> Skype Meג„¢!
>>>>>
>>>>> -----Original Message-----
>>>>> From: Alexey Muranov [mailto:alexey.mura...@gmail.com]
>>>>> Sent: Sunday, July 10, 2016 3:42 PM
>>>>> To: Neftin, Sasha <sasha.nef...@intel.com>
>>>>> Cc: e1000-devel@lists.sourceforge.net
>>>>> Subject: Re: [E1000-devel] Support for Intel Ethernet Connection I219-V
>>>>>
>>>>> Thank you for the confirmation.
>>>>>
>>>>> Would you know by any chance then why the Ethernet is not recognized when
>>>>> i boot from nixos-graphical-16.03.858.b8d7324-x86_64-linux.iso or
>>>>> ubuntu-gnome-16.04-desktop-amd64.iso ? Are their drivers too old?
>>>>>
>>>>> Here is the output of some commands under Ubuntu:
>>>>>
>>>>> $ lspci -v | grep Ethernet
>>>>> 00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection
>>>>> I219-V (rev 21)
>>>>> Subsystem: ASUSTeK Computer Inc. Ethernet Connection I219-V
>>>>>
>>>>> $ dmesg | grep -i ethernet
>>>>> [ 16.701815] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
>>>>>
>>>>> $ ip addr
>>>>> 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN
>>>>> group default qlen 1
>>>>> link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
>>>>> inet 127.0.0.1/8 scope host lo
>>>>> valid_lft forever preferred_lft forever
>>>>> inet6 ::1/128 scope host
>>>>> valid_lft forever preferred_lft forever
>>>>> 2: wlp1s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state
>>>>> DOWN group default qlen 1000
>>>>> link/ether 44:85:00:2e:f7:93 brd ff:ff:ff:ff:ff:ff
>>>>>
>>>>> Thanks,
>>>>>
>>>>> Alexey.
>>>>>
>>>>> On 10 Jul 2016, at 08:58, Neftin, Sasha <sasha.nef...@intel.com> wrote:
>>>>>
>>>>>> Hello,
>>>>>> 3.3.4 should work with I219-V.
>>>>>> Thanks,
>>>>>> Sasha
>>>>>>
>>>>>> -----Original Message-----
>>>>>> From: Alexey Muranov [mailto:alexey.mura...@gmail.com]
>>>>>> Sent: Sunday, July 10, 2016 12:45 AM
>>>>>> To: e1000-devel@lists.sourceforge.net
>>>>>> Subject: [E1000-devel] Support for Intel Ethernet Connection I219-V
>>>>>>
>>>>>> Hello,
>>>>>>
>>>>>> I have a laptop with Intel Ethernet Connection I219-V. I want to
>>>>>> install Linux on it, but cannot yet get Ethernet to work under Linux. I
>>>>>> believe it is because the driver is missing.
>>>>>>
>>>>>> The version 3.3.4 of e1000e is not documented to support Intel Ethernet
>>>>>> Connection I219-V (it only goes up to I218). Is there any chance that
>>>>>> 3.3.4 will work correctly with I219? Will I219-V be supported in a near
>>>>>> future?
>>>>>>
>>>>>> Thank you,
>>>>>>
>>>>>> Alexey.
------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity planning
reports.http://sdm.link/zohodev2dev
_______________________________________________
E1000-devel mailing list
E1000-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/e1000-devel
To learn more about Intel® Ethernet, visit
http://communities.intel.com/community/wired
