You are not logged in.
Pages: 1
I updated my system and rebooted only to find my network interfaces gone.
uname -r
4.20.0-arch1-1-ARCHip link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00lspci -k
00:00.0 Host bridge: Intel Corporation 3rd Gen Core processor DRAM Controller (rev 09)
Subsystem: Lenovo 3rd Gen Core processor DRAM Controller
lspci: Unable to load libkmod resources: error -12
...A number of devices including the network controller, ethernet controller, and communication controller do not have the line identifying the driver in use.
pacman -Q kmod
kmod 26-3The files libkmod.so, libkmod.so.2, and libkmod.so.2.3.4 are all present in /lib. I'm also unable to connect to X server, so graphics aren't available either. Any help is appreciated. Thanks.
Mike
Offline
If you updated your system, your kernel would be a lot more recent than 4.20.0
Paste your full pacman.log
Offline
…and "pacman -Qs linux", you might simply have forgotton to mount the boot partition for the update…
Offline
I'm having trouble posting the pacman log. I have no network connectivity and the system is not recognizing a usb stick when I plug it in. Is there any way to do a system rollback without an internet connection?
Offline
Stop. look at the output of mount | grep boot.
Does it return anything? If it does, does it report that your boot partition is mounted on /boot?
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
The shortest way to ruin a country is to give power to demagogues.— Dionysius of Halicarnassus
---
How to Ask Questions the Smart Way
Offline
No output from mount | grep boot
Offline
So, the problem is that your boot *PARTITION* is not mounted anywhere. Including /boot.
At issue is, when you updated the kernel, all of the new stuff was written to /boot; the kernel, initrd, etc... If your boot partition had been mounted there, as it is supposed to be, the boot partition would have been updated when you updated. Since it was not mounted, all the new stuff is in the /boot directory of your root partition is full of stuff that does not matter.
In the mean time, the ancient kernel on the boot partition (which did not get updated) is used by your boot loader to start your system; when it boots, it cannot find its modules that tell it how to talk to your hardware, because (wait for it) they were removed when you updated your kernel -- the one that got written to /boot rather than to your unmounted boot partition (which should have been on /boot.) When you rebooted, the kernel was the one on your boot partition that did not get updated. Therefore, this kernel has no clue how to talk to any hardware that requires a kernel module -- Its modules now longer exist; they have been replaced by the new ones.
Fix this by:
Mounting the boot partition on /boot. Reinstall the kernel (sudo pacman -Syu linux)
Fix your /etc/fstab to mount the boot partition on /boot so this does not happen again.
Reboot to prove this works.
Extra bonus points: Unmount the boot partition from /boot, and clean out all the old cruft from /boot that should not be there in the first place.
Last edited by ewaller (2020-02-29 03:24:10)
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
The shortest way to ruin a country is to give power to demagogues.— Dionysius of Halicarnassus
---
How to Ask Questions the Smart Way
Offline
Pages: 1