[Assist] Module e1000 not found (can't load Ethernet card kernel module)

Freemor freemor at freemor.ca
Mon Jun 22 07:34:59 GMT 2020


On Mon, Jun 22, 2020 at 06:29:19AM +0200, brskinzdenuncia at tuta.io wrote:
> I successfully installed Parabola for the first time in my virtual machine.
> The only issue is that I don't have internet access. I read through the
> Network configuration entry
> <https://wiki.archlinux.org/index.php/Network_configuration/Ethernet#Device_driver>
> in the Arch Wiki, and found out that my Ethernet card wasn't being
> recognized. After booting into my newly installed Parabola system, I ran
> lspci -v and noted that my Ethernet kernel module is e1000 (it's an Intel
> card, apparently it's this one
> <https://downloadcenter.intel.com/download/15817/Intel-Network-Adapter-Driver-for-PCIe-Intel-Gigabit-Ethernet-Network-Connections-Under-Linux-?wapkw=e1000>),
> then I ran dmesg | grep e1000, and as expected nothing showed up, so I
> assumed it wasn't loaded. Then, as this Arch Wiki entry
> <https://wiki.archlinux.org/index.php/Kernel_module#Manual_module_handling>
> suggested, I ran modprobe e1000, but it gave me the following errors:
> 
> modprobe: FATAL: Module e1000 not found in directory
> /lib/modules/5.4.12-gnu-1
> 
> At first I thought of downloading the module directly from Intel's website,
> but it requires that I make install it, and when I tried it I got a lot of
> different errors. But then I realized that perhaps compiling it wasn't
> necessary, the rationale being that within the Parabola live installation ISO
> I had stable Ethernet connection, so I tried the dmesg | grep e1000 command
> while within the live Parabola and it returned the following:
> 
> [        4.031943] e1000: Intel(R) PRO/1000 Network Driver - version
> 7.3.21-k8-NAPI[        4.031943] e1000: Copyright (c) 1999-2006 Intel
> Corporation.  [        4.415594] e1000 0000:00:03.0 eth0: (PCI:33MHz:32-bit)
> 08:00:27:d4:6d:4d [        4.415598] e1000 0000:00:03.0 eth0: Intel(R)
> PRO/1000 Network Connection [        7.046096] e1000 0000:00:03.0 enp0s3:
> renamed from eth0 [       10.162081] e1000: enp0s3 NIC Link is Up 1000 Mbps
> Full Duplex, Flow Control: RX I know that drivers in general are a pain in
> the ***, since these drivers are (I think?) proprietary. But noticing that
> the live ISO had internet access gave me hope.
> 
> Any help is greatly appreciated, I hope I gave sufficient information for
> debugging. Thanks in advance!

> _______________________________________________ Assist mailing list
> Assist at lists.parabola.nu https://lists.parabola.nu/mailman/listinfo/assist

This sounds like an issue that I have run into occasionally in situations where
I pacman -Suy but then don't reboot. 

If pacman -Suy pulls in a new kernel the system will be unable to find modules
as they'll now be living in /lib/modules/<new kernel ver> but the system will
still be trying to look in /lib/modules/<kernel ver>. 

ls /lib/modules/ 

and check that /lib/modules/5.4.12-gnu-1 matches the installed kernel not just
the current running kernel. If /lib/modules/<kernel ver> is newer then waht 
uname -a reports then a reboot may fix the issue. If they are out of sync and
you have done a reboot then something else has caused them to be out of sync
and reporting the values of 

uname -a 

and 

ls /lib/modules/

may help to debug the issue.


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <https://lists.parabola.nu/pipermail/assist/attachments/20200622/08ad00cf/attachment.sig>


More information about the Assist mailing list