• [6.8.3] no drivers for newer onboard I219-V Intel NICs (s1200)

    Ford Prefect

    By Ford Prefect

      • Minor

    This NIC is becoming very popular in current Motherboards and reports are increasing that the stable version of unraid dos not carry the appropriate driver (while 6.9beta has it (newest e1000e as it seems).

    Myself and others are in the same boat ATM.

     

    Is there a chance to release a backport of the newest driver for unraid 6.8.x, as next stable 6.9.x is not released (yet).

    This will prevent a lot of potential users from purchasing a license, I would guess.

     

    Many thanks in advance!

     

    Edit: added diagnostics for 6.8.3stable and 6.9beta25.

    Also, no local UI on *both* versions with this MB https://www.gigabyte.com/Motherboard/H470M-DS3H-rev-10#kf and Pentium G 6400

     

    Edit 2: I made a diff of the driver versions from 6.8.3 and 6,9beta25.

    Although both drivers do report the same version string, the one from 6.9b25 apparently has support for 8 newer revisons of the NIC.

    There are 18 revisions (V0 - V17) of this chip listed in total 🤯, of which the old version from 6.8.3 supports the first 10 (V0 - V9).

    see: 

    diff -Naur linux-4.19.107-Unraid/drivers/net/ethernet/intel/e1000e/hw.h linux-5.7.8-Unraid/drivers/net/ethernet/intel/e1000e/hw.h
--- linux-4.19.107-Unraid/drivers/net/ethernet/intel/e1000e/hw.h	2020-02-28 16:39:01.000000000 +0100
+++ linux-5.7.8-Unraid/drivers/net/ethernet/intel/e1000e/hw.h	2020-07-09 09:39:40.000000000 +0200
@@ -86,6 +86,22 @@
 #define E1000_DEV_ID_PCH_ICP_I219_V8		0x15E0
 #define E1000_DEV_ID_PCH_ICP_I219_LM9		0x15E1
 #define E1000_DEV_ID_PCH_ICP_I219_V9		0x15E2
+#define E1000_DEV_ID_PCH_CMP_I219_LM10		0x0D4E
+#define E1000_DEV_ID_PCH_CMP_I219_V10		0x0D4F
+#define E1000_DEV_ID_PCH_CMP_I219_LM11		0x0D4C
+#define E1000_DEV_ID_PCH_CMP_I219_V11		0x0D4D
+#define E1000_DEV_ID_PCH_CMP_I219_LM12		0x0D53
+#define E1000_DEV_ID_PCH_CMP_I219_V12		0x0D55
+#define E1000_DEV_ID_PCH_TGP_I219_LM13		0x15FB
+#define E1000_DEV_ID_PCH_TGP_I219_V13		0x15FC
+#define E1000_DEV_ID_PCH_TGP_I219_LM14		0x15F9
+#define E1000_DEV_ID_PCH_TGP_I219_V14		0x15FA
+#define E1000_DEV_ID_PCH_TGP_I219_LM15		0x15F4
+#define E1000_DEV_ID_PCH_TGP_I219_V15		0x15F5
+#define E1000_DEV_ID_PCH_ADP_I219_LM16		0x1A1E
+#define E1000_DEV_ID_PCH_ADP_I219_V16		0x1A1F
+#define E1000_DEV_ID_PCH_ADP_I219_LM17		0x1A1C
+#define E1000_DEV_ID_PCH_ADP_I219_V17		0x1A1D

    6.9b25_tower-diagnostics-20200903-0221.zip 6.8.3stable_tower-diagnostics-20200903-0216.zip

     

    I also compiled a 6.8.3 kernel with the latest version from here: https://sourceforge.net/projects/e1000/files/e1000e stable/3.8.4/ and did a quick test, So I can confirm that the NIC worked fine with it.

     

    I do think this is an issue for returning customers, like myself planing on upgrading an existing rig, but also for new unraid users, bying the newer 10th gen intel technology with intel NICs, suspecting that these would work stable.

    Both groups are now limited to either add an external NIC or move to 6.9beta.

     

    I am tempted to flag this as an urgent matter.

    What do you think?

     

    regards,

    Ford

    Go to reports Stable Releases

    User Feedback

    Recommended Comments

    Taddeusz

    You might post diagnostics. This isn't entirely true? It might depend on the revision. I have an H370M based board with the same controller working. My system devices show: 

    [8086:15bc] 00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection (7) I219-V (rev 10)

     

    Link to comment
    Ford Prefect

    ...OK, how do I do that from the command line?

    in /var/log/ ... demsg and syslog do not even list an ethernet device

    The GUI is not starting locally. I'd have to transport the files via the USB anyway.

    In the link, there is another diagnostics, basically showing the same.

    Edit: got it. 6.9b25 also does not produce a local GUI (Pentium G 6400).

     

     

    Yes, I also think this is a thing with the revision of the onboard NICs, as others - like you - do not have a problem.

    The reason I went for that build in the first place, because I checked.

    The B365M-Pro4 (Socket-1151v2) also has that NIC but the OP there states that it is working, too.

    Edit: mine shows: 

    Ethernet controller [0200]: Intel Corporation Ethernet Connection (11) I219-V [8086:0d4d]

     

    My guess is that at least Socket-1200 boards are affected. But this is the reason why I posted here. I don't think it is a good situation, where the recent hardware is not supported in unraid stable.

    New customers should not be directed/limited to the beta, where that NIC is working. My 2 cents.

    Well, if 6.9stable will arrive "verry" soon(tm), then maybe ;-)

    Edited by Ford Prefect
    updated lspci info for NIC
    Link to comment
    Ford Prefect

    ...see my edit2 in the first post.

    That NIC has now 18 revisions, of which unraid 6.8.3 "only" supports the first 10.

    All newer 10th gen intel platforms with onboard NICs from intel are likely to be affected.

    Edited by Ford Prefect
    • Like 1
    Link to comment
    Sammy1Am

    Stopping by to chime in: I'm attempting to set up Unraid for the first time on an H470M (with an I219-V NIC), and Unraid is unable to load a network driver (and fails to boot into GUI as well).  Going to give the Unraid beta a try and see if that fixes it (as I'm not quite willing to go out of my way to compile my own custom 6.8.3 kernel to get it working).  On the one hand, I'd like to stick with a nice Stable release, but in this case 6.9-beta seems like a fairly low risk so far since it's mostly just a Linux kernel update from what I've read (I mean, at least since I have nothing set up, there's nothing yet to break).

    Edited by Sammy1Am
    Link to comment
    Six8
    On 9/6/2020 at 7:47 PM, Sammy1Am said:

    Stopping by to chime in: I'm attempting to set up Unraid for the first time on an H470M (with an I219-V NIC), and Unraid is unable to load a network driver (and fails to boot into GUI as well).  Going to give the Unraid beta a try and see if that fixes it (as I'm not quite willing to go out of my way to compile my own custom 6.8.3 kernel to get it working).  On the one hand, I'd like to stick with a nice Stable release, but in this case 6.9-beta seems like a fairly low risk so far since it's mostly just a Linux kernel update from what I've read (I mean, at least since I have nothing set up, there's nothing yet to break).

    Did this end up working out for you?

    Link to comment
    Ford Prefect

    ...the 6.9beta works with that NIC but there is no date (other than "soonTM", as usual) for GA release.

    I also compiled a 6.8.3 kernel with a more recent driver (see my first post) which also works, but this is an unsatisfying situation, I think.

    Link to comment
    Nexius2

    How happy I am to have just finishing building my rig to discover it wont work....

    I'm also concerned about this driver problem.

    is there a compatible version available somewhere ?

    Link to comment
    Ford Prefect

    ...not officially, no. I still have the binaries around here, but did not test them thoroughly.

    I have postponed my build at this time, but I also do not think, that the best option is to change this issue to urgent, as there are other options for a new build to get around this (starting from using the beta, ending by adding a working, second NIC)

     

    Edited by Ford Prefect
    Link to comment
    dokuhebi

    +1 to this.  My onboard NIC isn't showing up, and it's putting a stop to my new build.  I haven't yet invested in an unraid server, so if a solution isn't coming soon, I'll probably go to mergerfs/syncraid. 

    Link to comment


    Join the conversation

    You can post now and register later. If you have an account, sign in now to post with your account.
    Note: Your post will require moderator approval before it will be visible.

    Guest
    Add a comment...

    ×   Pasted as rich text.   Restore formatting

      Only 75 emoji are allowed.

    ×   Your link has been automatically embedded.   Display as a link instead

    ×   Your previous content has been restored.   Clear editor

    ×   You cannot paste images directly. Upload or insert images from URL.

    ×

  • Status Definitions

     

    Open = Under consideration.

     

    Solved = The issue has been resolved.

     

    Solved version = The issue has been resolved in the indicated release version.

     

    Closed = Feedback or opinion better posted on our forum for discussion. Also for reports we cannot reproduce or need more information. In this case just add a comment and we will review it again.

     

    Retest = Please retest in latest release.

    Priority Definitions

     

    Minor = Something not working correctly.

     

    Urgent = Server crash, data loss, or other showstopper.

     

    Annoyance = Doesn't affect functionality but should be fixed.

     

    Other = Announcement or other non-issue.