You are not logged in.
Did you do that from the chroot?
What if you don't chroot? (only "lsblk -f", the posted fstab is fine)
Offline
Yeah the problem was that I was chrooted
http://termbin.com/pz6ur
Offline
├─nvme0n1p1 vfat FAT32 SYSTEM E6D7-7A5C
├─nvme0n1p5 vfat FAT32 MYASUS 9A9B-24B5
Make sure there're no kernel image on those partitions.
When you updated/re-installed the kernel from the chroot, did you arch-chroot into the system or merely "chroot"?
Offline
just chroot, but that was after the fail and I have switched to lts with arch-chroot
p1 is an EFI paritition and p5 is a windows recovery one
Offline
You could theoretically still have shoved the kernel onto them during the installation, notably the EFI one.
Did you also run grub-mkconfig after switching to the lts kernel?
Offline
yes I did run it
Offline
Going over what historically caused issues
pacman -Qikk filesystem
stat /lib64 /usr/lib64
Offline
I don't know how but I was able to boot into lts and standard linux,
but problem now is that even though I enable and start sddm, it does not start it at the next boot
I need to start it by hand
Offline
Ok Ok it was because the default target was multi-user and not graphical
Offline
If I had to bet, my money would be on breaking stuff w/ an update/installation during an improper chroot.
Please always remember to mark resolved threads by editing your initial posts subject - so others will know that there's no task left, but maybe a solution to find.
Thanks.
Offline