I recently installed latest software update but it doesn’t boot normally.
It boots to ALT+F1 screen and when I press ALT+F7 to go to login screen there is just bunch of messages which starts with it stucks on that screen:
What should I do?
Boot the previous kernel (select it in “Advanced Options” in the boot menu), and wait for the next kernel update (or install 4.14.13 from Kernel:stable).
If you have Teamviewer installed, uninstall or disable it, and 4.14.12 might boot too.
I exactly did what you said actually. Kernel 4.14.9-1-default wasn’t booting and I kept using 4.14.8-1 for a while. Today I updated it to 4.14.12-1 and now I can’t go back to 4.14.8-1 which is the only kernel that works.
Well, that’s bad.
And your problems are not related to the recent security fixes then either.
Unfortunately your screenshots give absolutely no clue what may be wrong.
What display manager and graphics card are you using?
Does the system boot to a text mode if you add ‘3’ or ‘1’ to the kernel boot options? (press ‘e’ at the boot menu and append that at the end of the line starting with “linux” or “linuxefi”)
If yes, try to switch the display manager to xdm with “sudo update-alternatives --config default-displaymanager”, and see if the system boots to graphics mode then.
Also try to boot with “nomodeset” maybe.
I tried changing it to xdm and booting with nomodeset but nothing changed
How exactly did you change to xdm if you cannot boot?
If you read my post it says it boots to alt+f1 screen and when I press alt+f7 the screen on the imgur link appears. So I can run terminal commands.
So does that mean you DO get a text mode login prompt when booting?
Just the graphical session doesn’t start and if you switch to VT-7 (i.e. press Alt+F7) there are just text messages, no login screen?
In that case, please provide the output of “systemctl get-default”.
Ok I ran the “systemctl get-default” command and the output is “graphical.target”
That looks fine.
So the system does boot to a text mode login prompt?
What does “sudo systemctl status display-manager” say?
OK, the display-manager.service is started, but if I interpret the output correctly, GDM failed to start the greeter (because of “too many files open”? :).
As I already suggested, run “sudo update-alternatives --config default-displaymanager” and set xdm as default. Do you get a login screen then?
If not, please post the output of systemctl again.
I know you said you did that already, but I’m not sure you did it correctly. (the default is gdm currently at least)
Hm, I see nothing wrong there, it seems to start fine.
Maybe it’s running on a different VT than VT-7 for some reason?
Try (Ctrl+)Alt+F2 to (Ctrl+)Alt+F9 and see if you find a login screen anywhere else.
What happens if you run “systemctl restart display-manager”?
Nope, it is on the alt+F7.
Ok so I ran the “systemctl restart display-manager” command and output changed to this
https://imgur.com/Y4lDKXA
I thought your problem is that it’s not there? 
So please check the other VTs if the login screen is on a different one maybe.
Ok so I ran the “systemctl restart display-manager” command and output changed to this
https://imgur.com/Y4lDKXA
Actually I was mostly interested if the login screen show up then.
The output hasn’t changed much, except that the status says “Inactive (dead)” now. I’m not sure if that really indicates a problem, as I see nothing wrong in the rest of the output.
Another thing I would try is to disable the plymouth splash screen, with the “plymouth.enable=0” boot option. Maybe it interferes somehow.
Also, does startx work? (as root)
If not, there’s a problem with X itself, and that of course would make the displaymanager not start either as a consequence.
Ok, I think we’re reaching the bottom of the problem…
It says:
(EE) Fatal server error:
(EE) no screens found
And I notice that X loads a custom /etc/X11/xorg.conf .
Rename that (but not /etc/X11/xorg.conf.d/ !), and see if it helps.
If not, it would probably be good to see the full log file, /var/log/Xorg.0.log .
PS: do you maybe use the nvidia driver?
That (384.xx at least) indeed stopped working with kernel 4.14.9 until the new version 384.111 got released/added to the repo recently.
Updating the driver to the latest version should fix your problem then.
On Sun 14 Jan 2018 03:26:01 PM CST, wolfi323 wrote:
PS: do you maybe use the nvidia driver?
That indeed stopped working with kernel 4.14.9 until the new version
387.111 got released/added to the repo recently.
Updating the driver to the latest version should fix your problem then.
Hi
I do, the old one though 340.104, needed to rebuild and install after
the latest updates to 20180110 for GDM to work…
–
Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
openSUSE Leap 42.3|GNOME 3.20.2|4.4.104-39-default
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below… Thanks!