You are not logged in.
Update: See below...
I recently rebooted after a pacman -Syu.
Since doing this I can't connect to a network (so no full logs sorry). Or start X
The fatal error in X is
open card /dev/dri/card0 no such file or directory
Screen 0 deleted because of no matching configuration session
...
Screen found, but none have a usable configurationIf I try to connect to a network I find that only the loopback (lo) device is visible (from ip link)
lspci -v gives network controllers Qualcomm ... with no kernal driver field (as I think I'd expect to be there?)
If I try to load the alx module manually I get:
modprobe: FATAL: Module Alx no found in directory /lib/modules/4.17.2-1-ARCH However the alx module (I think) is here under /lib/modules/4.17.3-1-ARCH/kernal/drivers/net/ethernet/atheros/alx
So I think modprobe is looking in the wrong place (It is thinking we are a version beind). Normally I would try and fix this by reinstalling linux or something but without finctioning ethernet devices that's not happening.
So... Any ideas?
[Update]
The problem seems to be that the systemd-modules-load is failing
Error is
Failed to lookup ailias 'crypto_user': Function not implimentedNormally I would reinstall the kernel but I don't have network access.
Trying to run mkinitcpio gives
/lib/modules/4.17.2-1-ARCH is not a valid kernal module directory.How do I get it to use 4.17.3-1-ARCH (the installed kernel)?
For Clarity:
Running Kernal (uname -r) is 4.17.2-1-ARCH
Installed Kernal (pacman -Q linux) is 4.17.3-1-ARCH
This is the source of the issue.
Last edited by KylieGS (2018-07-08 14:11:22)
Offline
What is the output of the following?
pacman -Q linux
uname -aOffline
What is the output of the following?
pacman -Q linux uname -a
Non-matching, hence why I'm trying to update the kernel
Offline
You didn't have your /boot partition mounted when doing the update. As you are unlikely to be able to mount it due to the same problem, you should use a live usb properly mount all relevant partitions (including /boot , however you might want to remove the incorrect /boot directory on your root partition before doing so), chroot in and update your system. Properly define your /boot partition in your fstab so you don't have to do this again.
Offline
You didn't have your /boot partition mounted when doing the update. As you are unlikely to be able to mount it due to the same problem, you should use a live usb properly mount all relevant partitions (including /boot , however you might want to remove the incorrect /boot directory on your root partition before doing so), chroot in and update your system. Properly define your /boot partition in your fstab so you don't have to do this again.
The uuid was miscopied into the fstab. I can mount /boot just fine(don't ask why this piece of hardware is working above all else). Problem is I left my live boot usb at home (I have a spare but it looks like I forgot to finish the setup of it). Is there a way to replace the kernal (since it's apparently installed) from the system?
Last edited by KylieGS (2018-07-08 14:01:09)
Offline
Downgrade to 4.17.2-1 from the package cache so the modules match then mount /boot then upgrade the kernel then unmount /boot and clean anything left in /boot.
Offline
Good Plan. Marking Solved
Offline