You are not logged in.
LightDM won't start / load after upgrading the nvidia-340xx package from 340.107-28 to 340.107-29.
dmesg spits out a couple of these lines:
nvidia: disagrees about version of symbol module_layout
After downgrading the package back to 340.107-29 lightDM is working again.
Please help me fix this or file a bug-report if necessary.
Here is some info. Let me know if you need more.
dmesg: https://ptpb.pw/WX9k
Xorg.0.log: https://ptpb.pw/d5wK
Recent upgrades / updates: https://ptpb.pw/jIrT
systemctl --state=failed
systemctl status lightdm
Last edited by lquidfire (2018-09-19 12:11:03)
Offline
Your loaded kernel is outdated. The module rebuild was against 4.18.8 you are running 4.18.7. This usually happens if one doesn't ensure the /boot partition is properly mounted during an update. Either use a live system chroot or temporarily install the old kernel package and then properly mount the partition and reinstall the linux package..
Online
340.107-29 is built against 4.18.8.arch1-1 but you're booting 4.18.7-arch1-1-ARCH so either you conducted a partial update or forgot to mount the /boot partition.
The pacman.log tail is inconclusive here.
Edit: crap.
Last edited by seth (2018-09-18 13:26:34)
Offline
Thanks. I will have to work on this tomorrow again (home now). I managed to update the kernel to 4.18.8, but still got problems; it seemed that the computer still booting the 4.17 kernel...
The hard drive lay-out is a bit messy, with a separate /boot partition with Grub (from the Debian instal). Arch does not mount that partition, but seems to have its own boot directory, residing in its own root partition.
My idea is that if Arch uses its own boot directory, and updates the kernel therein, and Grub (loaded from a different partition) points to Arch's directory with the 4.18.8 kernel, that all should be fine. No need to update Grub under Debian, since the Arch kernels have generic names. Right?
Offline
4.17 is not recorded by the posted dmesg.
My idea is that we'll have to see the actual grub config in order to make an informed statement on the condition :-P
Offline
Ach, I meant 4.18.7, not 4.17...
But I'll boot into Debian tomorrow to find out what's what, and also post a lay-out of the hard drive while I'm at it. Haven't logged into Debian in many months.
Offline
Cheers V1del and seth.
Problem was solved by loading the right kernel + nvidia versions.
The grub problem was of a different order, but today is a day of victory, as I overcame the fear of GRUB that I had had since the late '90s. It always seemed such an insurmountable thing, to be thrown back to a black screen with large white letters and hardly any options in the grub shell to work with.
It turned out that grub was from a linux installation that isn't even installed anymore. It was a legacy-version of grub as well. I eventually managed to boot into Debian from the grub shell, upgrade to grub2, and wrote my own grub.cfg according to Eschwarz' suggestion here.
Arch is booting fine again now, with new kernel and nvidia.
Offline