I'm trying to build a bare metal EVE server. Unfortunately the supplied driver for Intel's e1000e chip doesn't support the lates I219V chipset.
I've downloaded the required driver source code from Intels webpage, and I've tried to setup a build environment on an EVE-NG VM.
When trying to compile the driver, I get the error message, that the running kernel wants modules to be signed.
As I see it there are only 2 solutions for this:
1) EVE-NG.com will reveal the signing key. This is probably NOT likely for security reasons.
2) EVE-NG will provide a compiled and signed kernel module? Is this possible? Are the kernel module available for download somewhere on EVE-NGs site?
I'm currently using the community version, but I gladly sign up for a pro version, if that is what it take to get access to this module.
Sincerely
Tim
Problem with e1000e Ethernet driver
Moderator: mike
-
- Posts: 344
- Joined: Thu Mar 29, 2018 4:19 pm
Re: Problem with e1000e Ethernet driver
can you show me screenshot in our chat in a direct message of what exactly its telling you. https://www.eve-ng.net/index.php/live-helpdesk/
-
- Posts: 2
- Joined: Thu Jun 22, 2023 9:31 am
Re: Problem with e1000e Ethernet driver
Upon switching from Ubuntu 18.04 to Ubuntu 20.04, I encountered this issue. The motherboard I'm using is the H510M-A PRO (MS-7D22). The Intel Corporation Device 0d4f (version 11) is the onboard Intel Network Adapter. Every time there is a kernel upgrade (3.13.0-63), I have to repeat the process because my Intel NUC is incompatible with the outdated 2.3.2-k driver.
H510M-geometry dash liteA PRO (MS-7D22)
-
- Posts: 344
- Joined: Thu Mar 29, 2018 4:19 pm
Re: Problem with e1000e Ethernet driver
what are you doing exactly ?auctionshrimp wrote: ↑Mon Dec 18, 2023 8:53 amUpon switching from Ubuntu 18.04 to Ubuntu 20.04, I encountered this issue. The motherboard I'm using is the H510M-A PRO (MS-7D22). The Intel Corporation Device 0d4f (version 11) is the onboard Intel Network Adapter. Every time there is a kernel upgrade (3.13.0-63), I have to repeat the process because my Intel NUC is incompatible with the outdated 2.3.2-k driver.