Bug 1827940 - Networkdevice e1000e (I219-V - Intel NUC10i7FNH ) is not recognized on Fedora 31
Summary: Networkdevice e1000e (I219-V - Intel NUC10i7FNH ) is not recognized on Fedora 31
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 31
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-04-25 18:38 UTC by remoe
Modified: 2020-11-24 17:19 UTC (History)
18 users (show)

Fixed In Version:
Doc Type: ---
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-11-24 17:19:29 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description remoe 2020-04-25 18:38:16 UTC
1. Please describe the problem:

I've installed Fedora 31 Server Edition on Intel NUC10i7FNH. Fedora doesn't recognize the ethernet network device I219-V. Fedora has an old e1000e driver installed. The newest Intel driver 3.8 works. It is available here https://downloadcenter.intel.com/download/15817/Intel-Network-Adapter-Driver-for-PCIe-Intel-Gigabit-Ethernet-Network-Connections-Under-Linux- .

The installation of this driver fails because the SPECS of the RPM has a wrong dependency "fileutils". This package is removed in Fedora and replaced with "coreutils". But the package can install with "rpm -Uvh --nodeps e1000e-3.8.4-1.x86_64.rpm".

2. What is the Version-Release number of the kernel:

5.6.6-200.fc31.x86_64

3. Did it work previously in Fedora? If so, what kernel version did the issue
   *first* appear?  Old kernels are available for download at
   https://koji.fedoraproject.org/koji/packageinfo?packageID=8 :

5.6.6-200.fc31.x86_64

4. Can you reproduce this issue? If so, please provide the steps to reproduce
   the issue below:

ifconfig doesn't not show the network device

5. Does this problem occur with the latest Rawhide kernel? To install the
   Rawhide kernel, run ``sudo dnf install fedora-repos-rawhide`` followed by
   ``sudo dnf update --enablerepo=rawhide kernel``:


6. Are you running any modules that not shipped with directly Fedora's kernel?:

no

7. Please attach the kernel logs. You can get the complete kernel log
   for a boot with ``journalctl --no-hostname -k > dmesg.txt``. If the
   issue occurred on a previous boot, use the journalctl ``-b`` flag.

Comment 1 Steve 2020-04-27 01:23:41 UTC
"... Intel NUC10i7FNH. Fedora doesn't recognize the ethernet network device I219-V."

Thanks for your report. There are a lot of versions of the "I219-V", so could you post the vendor/id for the device:

$ lspci -nn

From the kernel source code:

$ git branch --list HEAD
* (HEAD detached at v5.6.6)

$ git grep I219_V drivers/net/ethernet/intel/e1000e/hw.h
drivers/net/ethernet/intel/e1000e/hw.h:#define E1000_DEV_ID_PCH_SPT_I219_V              0x1570  /* SPT PCH */
drivers/net/ethernet/intel/e1000e/hw.h:#define E1000_DEV_ID_PCH_SPT_I219_V2             0x15B8  /* SPT-H PCH */
drivers/net/ethernet/intel/e1000e/hw.h:#define E1000_DEV_ID_PCH_SPT_I219_V4             0x15D8
drivers/net/ethernet/intel/e1000e/hw.h:#define E1000_DEV_ID_PCH_SPT_I219_V5             0x15D6
drivers/net/ethernet/intel/e1000e/hw.h:#define E1000_DEV_ID_PCH_CNP_I219_V6             0x15BE
drivers/net/ethernet/intel/e1000e/hw.h:#define E1000_DEV_ID_PCH_CNP_I219_V7             0x15BC
drivers/net/ethernet/intel/e1000e/hw.h:#define E1000_DEV_ID_PCH_ICP_I219_V8             0x15E0
drivers/net/ethernet/intel/e1000e/hw.h:#define E1000_DEV_ID_PCH_ICP_I219_V9             0x15E2
drivers/net/ethernet/intel/e1000e/hw.h:#define E1000_DEV_ID_PCH_CMP_I219_V10            0x0D4F
drivers/net/ethernet/intel/e1000e/hw.h:#define E1000_DEV_ID_PCH_CMP_I219_V11            0x0D4D
drivers/net/ethernet/intel/e1000e/hw.h:#define E1000_DEV_ID_PCH_CMP_I219_V12            0x0D55
drivers/net/ethernet/intel/e1000e/hw.h:#define E1000_DEV_ID_PCH_TGP_I219_V13            0x15FC
drivers/net/ethernet/intel/e1000e/hw.h:#define E1000_DEV_ID_PCH_TGP_I219_V14            0x15FA

Comment 2 Steve 2020-04-27 01:33:35 UTC
The version of hw.h in the tarball you cited does indeed have ids for V15, V16, and V17 that are not in kernel v5.6.6:

$ grep I219_V /tmp/e1000e-3.8.4/src/hw.h 
#define E1000_DEV_ID_PCH_SPT_I219_V		0x1570	/* Sunrise Point PCH */
#define E1000_DEV_ID_PCH_SPT_I219_V2		0x15B8	/* Sunrise Point-H PCH */
#define E1000_DEV_ID_PCH_SPT_I219_V4		0x15D8
#define E1000_DEV_ID_PCH_SPT_I219_V5		0x15D6
#define E1000_DEV_ID_PCH_CNP_I219_V6		0x15BE
#define E1000_DEV_ID_PCH_CNP_I219_V7		0x15BC
#define E1000_DEV_ID_PCH_ICP_I219_V8		0x15E0
#define E1000_DEV_ID_PCH_ICP_I219_V9		0x15E2
#define E1000_DEV_ID_PCH_CMP_I219_V10		0x0D4F
#define E1000_DEV_ID_PCH_CMP_I219_V11		0x0D4D
#define E1000_DEV_ID_PCH_CMP_I219_V12		0x0D55
#define E1000_DEV_ID_PCH_TGP_I219_V13		0x15FC
#define E1000_DEV_ID_PCH_TGP_I219_V14		0x15FA
#define E1000_DEV_ID_PCH_TGP_I219_V15		0x15F5
#define E1000_DEV_ID_PCH_ADL_I219_V16		0x1A1F
#define E1000_DEV_ID_PCH_ADL_I219_V17		0x1A1D

Comment 3 Steve 2020-04-27 01:59:18 UTC
You could try this Fedora rawhide kernel, which should have the newer ids:

kernel-5.7.0-0.rc2.20200422git18bf34080c4c.1.fc33 
https://bodhi.fedoraproject.org/updates/FEDORA-2020-dc6f11f474

You can see the upstream commits here:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/log/drivers/net/ethernet/intel/e1000e/hw.h

==
$ git branch --list HEAD
* (HEAD detached at v5.7-rc2)

$ git grep I219_V drivers/net/ethernet/intel/e1000e/hw.h
...
drivers/net/ethernet/intel/e1000e/hw.h:#define E1000_DEV_ID_PCH_TGP_I219_V14            0x15FA
drivers/net/ethernet/intel/e1000e/hw.h:#define E1000_DEV_ID_PCH_TGP_I219_V15            0x15F5
drivers/net/ethernet/intel/e1000e/hw.h:#define E1000_DEV_ID_PCH_ADP_I219_V16            0x1A1F
drivers/net/ethernet/intel/e1000e/hw.h:#define E1000_DEV_ID_PCH_ADP_I219_V17            0x1A1D

Comment 4 Steve 2020-04-27 03:24:38 UTC
> Fedora has an old e1000e driver installed.

Fedora kernels follow upstream kernels very closely.

The problem with the e1000e driver you are reporting occurs because the upstream stable kernel doesn't have the commits that update the driver.

There are two upstream kernel git repos through which changes flow:

mainline: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/
stable:   https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/

Commits first go into mainline and then into stable. And Fedora release kernels follow stable, so there is a chain:

mainline -> stable -> Fedora

(Pre-release Fedora kernels, aka "rawhide" kernels, follow mainline.)

You can find Fedora kernels on Bodhi:

https://bodhi.fedoraproject.org/updates/?packages=kernel

Comment 5 Ben Cotton 2020-11-03 17:10:10 UTC
This message is a reminder that Fedora 31 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 31 on 2020-11-24.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '31'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 31 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 6 Ben Cotton 2020-11-24 17:19:29 UTC
Fedora 31 changed to end-of-life (EOL) status on 2020-11-24. Fedora 31 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.