[SOLVED] Latest kernel version (4.10.13-1) causes LightDM not to start

Venom · 2017-05-01 09:02:34

Hi, I've just updated the kernel to the latest version found here (https://www.archlinux.org/packages/core/x86_64/linux/) and the system now won't boot.
I've set up verbose systemd's booting output and every single stage is flagged as OK but for some reason the system hangs right when LightDM is supposed to show up. The last line of output is "Accounts Service started" or something similar.
The package itself is now flagged as out of date for some reason. The initramfs image generation completed without issues. What am I supposed to do now? I know how to mount the partitions (/ and /home are separate), arch-chroot and fix what I can but I just don't know where to look.
Should I perhaps downgrade the kernel version or wait for a stable update, whenever that may be? Just wish I had some sort of a snapshot system set up, that would make things easier.

Thank you in advance.

Last edited by Venom (2017-05-01 16:43:08)

loqs · 2017-05-01 09:11:16

You can not switch to another tty with Ctrl+Alt+F2? If not you could Systemd#Change_default_target_to_boot_into to multi-user.target.
Alternatively you could chroot in as you suggested. Either way you gain access to a functioning terminal for the system inspect the journal and you can also disable lightdm.

blast beat · 2017-05-01 09:16:48

Had the same problem so I downgraded kernel from tty2 and everything is ok. I'll lock linux package update for a few days just to be on a safe side.

loqs · 2017-05-01 10:42:05

@blast beat what did the journal for a boot under 4.10.13 show the cause to be on your system?

blast beat · 2017-05-01 11:07:54

loqs wrote:

@blast beat what did the journal for a boot under 4.10.13 show the cause to be on your system?

Don't know, haven't checked. I needed computer ASAP, so this was quickest solution.

jasonwryan · 2017-05-01 16:21:02

So, your "system isn't broken", lightdm just won't start... Read your journal. And edit your thread title to one that actually reflects your issue: https://wiki.archlinux.org/index.php/Co … ow_to_post

Moving to Newbie Corner

Venom · 2017-05-01 16:42:39

So the problem was in fact with the nvidia proprietary drivers, I've just updated them and all is once again well.
Here is proof (relevant output from the systemd logs):

May 01 18:27:20 Luka-PC kernel: nvidia: disagrees about version of symbol module_layout
May 01 18:27:20 Luka-PC systemd[1]: lightdm.service: Main process exited, code=exited, status=1/FAILURE
May 01 18:27:20 Luka-PC systemd[1]: lightdm.service: Unit entered failed state.
May 01 18:27:20 Luka-PC systemd[1]: lightdm.service: Failed with result 'exit-code'.
May 01 18:27:21 Luka-PC systemd[1]: lightdm.service: Service hold-off time over, scheduling restart.
May 01 18:27:21 Luka-PC systemd[1]: Stopped Light Display Manager.
May 01 18:27:21 Luka-PC systemd[1]: Starting Light Display Manager...
May 01 18:27:21 Luka-PC systemd[1]: Started Light Display Manager.
May 01 18:27:21 Luka-PC acpid[346]: client 406[0:0] has disconnected
May 01 18:27:21 Luka-PC acpid[346]: client connected from 429[0:0]
May 01 18:27:21 Luka-PC acpid[346]: 1 client rule loaded
May 01 18:27:21 Luka-PC kernel: nvidia: disagrees about version of symbol module_layout
May 01 18:27:21 Luka-PC systemd[1]: lightdm.service: Main process exited, code=exited, status=1/FAILURE
May 01 18:27:21 Luka-PC systemd[1]: lightdm.service: Unit entered failed state.
May 01 18:27:21 Luka-PC systemd[1]: lightdm.service: Failed with result 'exit-code'.
May 01 18:27:21 Luka-PC systemd[1]: lightdm.service: Service hold-off time over, scheduling restart.
May 01 18:27:21 Luka-PC systemd[1]: Stopped Light Display Manager.
May 01 18:27:21 Luka-PC systemd[1]: Starting Light Display Manager...
May 01 18:27:21 Luka-PC systemd[1]: Started Light Display Manager.
May 01 18:27:21 Luka-PC acpid[346]: client 429[0:0] has disconnected
May 01 18:27:21 Luka-PC acpid[346]: client connected from 438[0:0]
May 01 18:27:21 Luka-PC acpid[346]: 1 client rule loaded
May 01 18:27:21 Luka-PC kernel: nvidia: disagrees about version of symbol module_layout
May 01 18:27:22 Luka-PC systemd[1]: lightdm.service: Main process exited, code=exited, status=1/FAILURE
May 01 18:27:22 Luka-PC systemd[1]: lightdm.service: Unit entered failed state.
May 01 18:27:22 Luka-PC systemd[1]: lightdm.service: Failed with result 'exit-code'.
May 01 18:27:22 Luka-PC systemd[1]: lightdm.service: Service hold-off time over, scheduling restart.
May 01 18:27:22 Luka-PC systemd[1]: Stopped Light Display Manager.
May 01 18:27:22 Luka-PC systemd[1]: Starting Light Display Manager...
May 01 18:27:22 Luka-PC systemd[1]: Started Light Display Manager.
May 01 18:27:22 Luka-PC acpid[346]: client 438[0:0] has disconnected
May 01 18:27:22 Luka-PC acpid[346]: client connected from 447[0:0]
May 01 18:27:22 Luka-PC acpid[346]: 1 client rule loaded
May 01 18:27:22 Luka-PC kernel: nvidia: disagrees about version of symbol module_layout
May 01 18:27:22 Luka-PC systemd[1]: lightdm.service: Main process exited, code=exited, status=1/FAILURE
May 01 18:27:22 Luka-PC systemd[1]: lightdm.service: Unit entered failed state.
May 01 18:27:22 Luka-PC systemd[1]: lightdm.service: Failed with result 'exit-code'.
May 01 18:27:23 Luka-PC systemd[1]: lightdm.service: Service hold-off time over, scheduling restart.
May 01 18:27:23 Luka-PC systemd[1]: Stopped Light Display Manager.
May 01 18:27:23 Luka-PC systemd[1]: Starting Light Display Manager...
May 01 18:27:23 Luka-PC systemd[1]: Started Light Display Manager.
May 01 18:27:23 Luka-PC acpid[346]: client 447[0:0] has disconnected
May 01 18:27:23 Luka-PC acpid[346]: client connected from 456[0:0]
May 01 18:27:23 Luka-PC acpid[346]: 1 client rule loaded
May 01 18:27:23 Luka-PC kernel: nvidia: disagrees about version of symbol module_layout
May 01 18:27:23 Luka-PC systemd[1]: lightdm.service: Main process exited, code=exited, status=1/FAILURE
May 01 18:27:23 Luka-PC systemd[1]: lightdm.service: Unit entered failed state.
May 01 18:27:23 Luka-PC systemd[1]: lightdm.service: Failed with result 'exit-code'.
May 01 18:27:23 Luka-PC systemd[1]: lightdm.service: Service hold-off time over, scheduling restart.
May 01 18:27:23 Luka-PC systemd[1]: Stopped Light Display Manager.
May 01 18:27:23 Luka-PC systemd[1]: lightdm.service: Start request repeated too quickly.
May 01 18:27:23 Luka-PC systemd[1]: Failed to start Light Display Manager.
May 01 18:27:23 Luka-PC systemd[1]: lightdm.service: Unit entered failed state.
May 01 18:27:23 Luka-PC systemd[1]: lightdm.service: Failed with result 'exit-code'.
May 01 18:27:20 Luka-PC kernel: nvidia: disagrees about version of symbol module_layout
May 01 18:27:20 Luka-PC systemd[1]: lightdm.service: Main process exited, code=exited, status=1/FAILURE
May 01 18:27:20 Luka-PC systemd[1]: lightdm.service: Unit entered failed state.
May 01 18:27:20 Luka-PC systemd[1]: lightdm.service: Failed with result 'exit-code'.
May 01 18:27:21 Luka-PC systemd[1]: lightdm.service: Service hold-off time over, scheduling restart.
May 01 18:27:21 Luka-PC systemd[1]: Stopped Light Display Manager.
May 01 18:27:21 Luka-PC systemd[1]: Starting Light Display Manager...
May 01 18:27:21 Luka-PC systemd[1]: Started Light Display Manager.
May 01 18:27:21 Luka-PC acpid[346]: client 406[0:0] has disconnected
May 01 18:27:21 Luka-PC acpid[346]: client connected from 429[0:0]
May 01 18:27:21 Luka-PC acpid[346]: 1 client rule loaded
May 01 18:27:21 Luka-PC kernel: nvidia: disagrees about version of symbol module_layout
May 01 18:27:21 Luka-PC systemd[1]: lightdm.service: Main process exited, code=exited, status=1/FAILURE
May 01 18:27:21 Luka-PC systemd[1]: lightdm.service: Unit entered failed state.
May 01 18:27:21 Luka-PC systemd[1]: lightdm.service: Failed with result 'exit-code'.
May 01 18:27:21 Luka-PC systemd[1]: lightdm.service: Service hold-off time over, scheduling restart.
May 01 18:27:21 Luka-PC systemd[1]: Stopped Light Display Manager.
May 01 18:27:21 Luka-PC systemd[1]: Starting Light Display Manager...
May 01 18:27:21 Luka-PC systemd[1]: Started Light Display Manager.
May 01 18:27:21 Luka-PC acpid[346]: client 429[0:0] has disconnected
May 01 18:27:21 Luka-PC acpid[346]: client connected from 438[0:0]
May 01 18:27:21 Luka-PC acpid[346]: 1 client rule loaded
May 01 18:27:21 Luka-PC kernel: nvidia: disagrees about version of symbol module_layout
May 01 18:27:22 Luka-PC systemd[1]: lightdm.service: Main process exited, code=exited, status=1/FAILURE
May 01 18:27:22 Luka-PC systemd[1]: lightdm.service: Unit entered failed state.
May 01 18:27:22 Luka-PC systemd[1]: lightdm.service: Failed with result 'exit-code'.
May 01 18:27:22 Luka-PC systemd[1]: lightdm.service: Service hold-off time over, scheduling restart.
May 01 18:27:22 Luka-PC systemd[1]: Stopped Light Display Manager.
May 01 18:27:22 Luka-PC systemd[1]: Starting Light Display Manager...
May 01 18:27:22 Luka-PC systemd[1]: Started Light Display Manager.
May 01 18:27:22 Luka-PC acpid[346]: client 438[0:0] has disconnected
May 01 18:27:22 Luka-PC acpid[346]: client connected from 447[0:0]
May 01 18:27:22 Luka-PC acpid[346]: 1 client rule loaded
May 01 18:27:22 Luka-PC kernel: nvidia: disagrees about version of symbol module_layout
May 01 18:27:22 Luka-PC systemd[1]: lightdm.service: Main process exited, code=exited, status=1/FAILURE
May 01 18:27:22 Luka-PC systemd[1]: lightdm.service: Unit entered failed state.
May 01 18:27:22 Luka-PC systemd[1]: lightdm.service: Failed with result 'exit-code'.
May 01 18:27:23 Luka-PC systemd[1]: lightdm.service: Service hold-off time over, scheduling restart.
May 01 18:27:23 Luka-PC systemd[1]: Stopped Light Display Manager.
May 01 18:27:23 Luka-PC systemd[1]: Starting Light Display Manager...
May 01 18:27:23 Luka-PC systemd[1]: Started Light Display Manager.
May 01 18:27:23 Luka-PC acpid[346]: client 447[0:0] has disconnected
May 01 18:27:23 Luka-PC acpid[346]: client connected from 456[0:0]
May 01 18:27:23 Luka-PC acpid[346]: 1 client rule loaded
May 01 18:27:23 Luka-PC kernel: nvidia: disagrees about version of symbol module_layout
May 01 18:27:23 Luka-PC systemd[1]: lightdm.service: Main process exited, code=exited, status=1/FAILURE
May 01 18:27:23 Luka-PC systemd[1]: lightdm.service: Unit entered failed state.
May 01 18:27:23 Luka-PC systemd[1]: lightdm.service: Failed with result 'exit-code'.
May 01 18:27:23 Luka-PC systemd[1]: lightdm.service: Service hold-off time over, scheduling restart.
May 01 18:27:23 Luka-PC systemd[1]: Stopped Light Display Manager.
May 01 18:27:23 Luka-PC systemd[1]: lightdm.service: Start request repeated too quickly.
May 01 18:27:23 Luka-PC systemd[1]: Failed to start Light Display Manager.
May 01 18:27:23 Luka-PC systemd[1]: lightdm.service: Unit entered failed state.
May 01 18:27:23 Luka-PC systemd[1]: lightdm.service: Failed with result 'exit-code'.

Seems like a bunch of severe ABI breakage problems concerning the older version of nvidia drivers.
I guess it doesn't even matter now. Cheers!

@jasonwryan: The thread title is now edited and marked as SOLVED. Sorry for the initially ambiguous title.

mrunion · 2017-05-01 18:48:43

Are you doing partial upgrades? If so, that's a no-no. If not, I assume the nVidia drivers didn't update when you updated the Kernel because of your mirror not being up-to-date or something?

Venom · 2017-05-01 18:54:06

mrunion wrote:

Are you doing partial upgrades? If so, that's a no-no. If not, I assume the nVidia drivers didn't update when you updated the Kernel because of your mirror not being up-to-date or something?

I use reflector every once in a while (on a weekly basis, usually) and run pacman -Syu --force afterwards.
Mind you, this is the first time I've seen this happen in three years since I've been using Arch so it's not a big problem. Either way, I really ought to use snapshots of some kind (probably gonna use btrfs's built-in features, on my next install).

Last edited by Venom (2017-05-01 19:01:46)

jasonwryan · 2017-05-01 19:02:22

Venom wrote:

and run pacman -Syu --force afterwards.

Don't do this. --force should be used circumspectly, and on individual packages to fix issues, not thoughtlessly like this.

Venom · 2017-05-01 19:08:11

jasonwryan wrote:

Don't do this. --force should be used circumspectly, and on individual packages to fix issues, not thoughtlessly like this.

Thanks, I'll keep your advice in mind. It's just that I've seen some other guys use it without issues (on another forum) so I just went with it.
Monkey see, monkey do - I guess

Last edited by Venom (2017-05-01 19:08:44)

bealer · 2017-05-02 16:27:32

Same sort of issue for me. It's not actually related to Lightdm, rather X not being able to start. "startx" from a different tty should confirm the issue.

In my case (using intel) it looks like the kernel has updated, but graphics modules are still the older ones or something is referencing the older module. I'm still learning/understanding.

Jumping onto a different tty and doing a "sudo pacman -U /var/cache/pacman/pkg/linux-4.10.11-1-x86_64.pkg.tar.xz" to downgrade got my display back.

loqs · 2017-05-02 17:07:16

@bealer if nvidia 378.13-6 is not on a mirror you are using by now that mirror is not syncing properly. Which mirror(s) are not providing that package? I suggest you change mirrors.

mrunion · 2017-05-03 19:19:44

bealer wrote:

In my case (using intel) it looks like the kernel has updated, but graphics modules are still the older ones or something is referencing the older module.

Are you using a UEFI system? If so, is the proper /boot mounted when you upgrade the Kernel. This sounds like the problem where you are upgrading the Kernel without the (proper) /boot mounted.

bealer · 2017-05-04 09:08:05

mrunion wrote:

bealer wrote:
In my case (using intel) it looks like the kernel has updated, but graphics modules are still the older ones or something is referencing the older module.
Are you using a UEFI system? If so, is the proper /boot mounted when you upgrade the Kernel. This sounds like the problem where you are upgrading the Kernel without the (proper) /boot mounted.

Ah damn. Yeah... ignore my comment, human error! Just remembered a while back I had been messing with the boot partition. It wasn't mounted when upgrading, so the iniramfs images etc... weren't being updated.

u2piksnib · 2017-05-14 01:16:50

Hey everyone.. I'm having the same Lightdm issues.. tried the ctl/alt/f2 and tried starting enabling/starting service with systemd.. to no avail.. I've searched the forum here, and used google.. it was driving me crazy.. but i needed a computer now (like someone else said..) so i went with a different distro.. but here's my all around question..

If I downgrade the kernel.. will that fix the problem per 2 of the posts here? Is that the actual problem.. the newest kernel 4.10.13? is causing this issue?

Just wondering.. because once you go arch.. it's really annoying to use any other distro.. (not bashing any other distro) just saying..

and IF this is the issue.. and any longer than me arch users/moderators see this.. any idea how/when this will be fixed.. because if I upgrade the kernel (as I've also read on here and google) will it cause the same issue?

Thanks.. hope I didn't type in circles..

Arch Linux

#1 2017-05-01 09:02:34

[SOLVED] Latest kernel version (4.10.13-1) causes LightDM not to start

#2 2017-05-01 09:11:16

Re: [SOLVED] Latest kernel version (4.10.13-1) causes LightDM not to start

#3 2017-05-01 09:16:48

Re: [SOLVED] Latest kernel version (4.10.13-1) causes LightDM not to start

#4 2017-05-01 10:42:05

Re: [SOLVED] Latest kernel version (4.10.13-1) causes LightDM not to start

#5 2017-05-01 11:07:54

Re: [SOLVED] Latest kernel version (4.10.13-1) causes LightDM not to start

#6 2017-05-01 16:21:02

Re: [SOLVED] Latest kernel version (4.10.13-1) causes LightDM not to start

#7 2017-05-01 16:42:39

Re: [SOLVED] Latest kernel version (4.10.13-1) causes LightDM not to start

#8 2017-05-01 18:48:43

Re: [SOLVED] Latest kernel version (4.10.13-1) causes LightDM not to start

#9 2017-05-01 18:54:06

Re: [SOLVED] Latest kernel version (4.10.13-1) causes LightDM not to start

#10 2017-05-01 19:02:22

Re: [SOLVED] Latest kernel version (4.10.13-1) causes LightDM not to start

#11 2017-05-01 19:08:11

Re: [SOLVED] Latest kernel version (4.10.13-1) causes LightDM not to start

#12 2017-05-02 16:27:32

Re: [SOLVED] Latest kernel version (4.10.13-1) causes LightDM not to start

#13 2017-05-02 17:07:16

Re: [SOLVED] Latest kernel version (4.10.13-1) causes LightDM not to start

#14 2017-05-03 19:19:44

Re: [SOLVED] Latest kernel version (4.10.13-1) causes LightDM not to start

#15 2017-05-04 09:08:05

Re: [SOLVED] Latest kernel version (4.10.13-1) causes LightDM not to start

#16 2017-05-14 01:16:50

Re: [SOLVED] Latest kernel version (4.10.13-1) causes LightDM not to start

Board footer