You are not logged in.
Pages: 1
Hi all.
I made a fresh archlinux installation and during it my ethernet device was correctly identified, configured, and connected to network.
But after reboot it is not present.
Output of command
ip link
shows only loopback interface lo (same output for commandip a).
Output of command
lspci -v
shows network device:
Intel Corporation Ethernet Connection (2) I218-V
I tried to load the e1000e module but command
modprobe e1000e
shows following error:
modprobe: FATAL: Module e1000e not found in directory /lib/modules/4.11.9-1-ARCH
What should I do?
Thanks
PS: output of command uname -a is 4.11.9-1-ARCH, but folder /lib/modules/4.11.9-1-ARCH doesn't exist.
It exists the folder /lib/modules/4.12.8-2-ARCH instead. Is it correct?
Last edited by lezned (2017-09-01 06:48:30)
Offline
Your kernel was updated when your boot partition was not mounted on /boot.
Mount the boot partition and reinstall your kernel; It should be cached and will not need a NIC. Just use Pacman's -S switch (only)
Reboot, and check that the bootloader is now picking up the correct kernel.
Fix your /etc/fstab to automatically mount the boot partition on /boot.
Extra bonus points: Unmount the boot partition which causes /boot to no longer be a mount point and act like a normal directory. It should be empty when nothing is mounted on it. It probably has a kernel and an initrd in there. Clean them out.
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way
Offline
Not an Installation issue, moving to NC...
Offline
Your kernel was updated when your boot partition was not mounted on /boot.
Mount the boot partition and reinstall your kernel; It should be cached and will not need a NIC. Just use Pacman's -S switch (only)
Reboot, and check that the bootloader is now picking up the correct kernel.
Fix your /etc/fstab to automatically mount the boot partition on /boot.Extra bonus points: Unmount the boot partition which causes /boot to no longer be a mount point and act like a normal directory. It should be empty when nothing is mounted on it. It probably has a kernel and an initrd in there. Clean them out.
Thank you, this solved.
Offline
Please remember to mark your thread as [Solved] by editing your first post and prepending it to the title.
Offline
Pages: 1