Boot stuck at “Started TLP system startup/shutdown.” [closed]












2














OS: KDE Neon 5.14 based on Ubuntu 18.04
Kernel version: 4.15.0-42-generic



I tried booting from an older kernel version from the grub menu, still the system won't boot. It shows a long list of messages and doesn't proceed after the message



Started TLP system startup/shutdown.



Kernel was updated a few days ago. However, there was no problem booting after the update. I cannot identify what is causing this issue. Does it have something to do with the graphics driver?



Update: Running startx from the command line solved the issue. However, I would like to know what caused this issue.



Update 2: After reboot, the GRUB file is not found and system doesn't boot. I tried running the boot-repait utility and it fixed the grub. However the system boots into a black screen with a white blinking cursor, and does not show the login screen even after waiting for an hour.










share|improve this question















closed as too broad by G-Man, Rui F Ribeiro, schily, RalfFriedl, GAD3R Dec 12 at 7:23


Please edit the question to limit it to a specific problem with enough detail to identify an adequate answer. Avoid asking multiple distinct questions at once. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.















  • How did you get to a prompt where you could run startx if the boot process gets stuck? Please can you clarify -- in your question.
    – roaima
    Dec 11 at 22:24










  • I opened the prompt with Ctrl+Alt+F3
    – kJd47
    Dec 13 at 6:29










  • So it did boot - at least to a login prompt?
    – roaima
    Dec 13 at 7:20










  • It is presently showing just a blank screen with a blinking cursor. However, I am able to access the login prompt at this stage.
    – kJd47
    Dec 13 at 9:54


















2














OS: KDE Neon 5.14 based on Ubuntu 18.04
Kernel version: 4.15.0-42-generic



I tried booting from an older kernel version from the grub menu, still the system won't boot. It shows a long list of messages and doesn't proceed after the message



Started TLP system startup/shutdown.



Kernel was updated a few days ago. However, there was no problem booting after the update. I cannot identify what is causing this issue. Does it have something to do with the graphics driver?



Update: Running startx from the command line solved the issue. However, I would like to know what caused this issue.



Update 2: After reboot, the GRUB file is not found and system doesn't boot. I tried running the boot-repait utility and it fixed the grub. However the system boots into a black screen with a white blinking cursor, and does not show the login screen even after waiting for an hour.










share|improve this question















closed as too broad by G-Man, Rui F Ribeiro, schily, RalfFriedl, GAD3R Dec 12 at 7:23


Please edit the question to limit it to a specific problem with enough detail to identify an adequate answer. Avoid asking multiple distinct questions at once. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.















  • How did you get to a prompt where you could run startx if the boot process gets stuck? Please can you clarify -- in your question.
    – roaima
    Dec 11 at 22:24










  • I opened the prompt with Ctrl+Alt+F3
    – kJd47
    Dec 13 at 6:29










  • So it did boot - at least to a login prompt?
    – roaima
    Dec 13 at 7:20










  • It is presently showing just a blank screen with a blinking cursor. However, I am able to access the login prompt at this stage.
    – kJd47
    Dec 13 at 9:54
















2












2








2







OS: KDE Neon 5.14 based on Ubuntu 18.04
Kernel version: 4.15.0-42-generic



I tried booting from an older kernel version from the grub menu, still the system won't boot. It shows a long list of messages and doesn't proceed after the message



Started TLP system startup/shutdown.



Kernel was updated a few days ago. However, there was no problem booting after the update. I cannot identify what is causing this issue. Does it have something to do with the graphics driver?



Update: Running startx from the command line solved the issue. However, I would like to know what caused this issue.



Update 2: After reboot, the GRUB file is not found and system doesn't boot. I tried running the boot-repait utility and it fixed the grub. However the system boots into a black screen with a white blinking cursor, and does not show the login screen even after waiting for an hour.










share|improve this question















OS: KDE Neon 5.14 based on Ubuntu 18.04
Kernel version: 4.15.0-42-generic



I tried booting from an older kernel version from the grub menu, still the system won't boot. It shows a long list of messages and doesn't proceed after the message



Started TLP system startup/shutdown.



Kernel was updated a few days ago. However, there was no problem booting after the update. I cannot identify what is causing this issue. Does it have something to do with the graphics driver?



Update: Running startx from the command line solved the issue. However, I would like to know what caused this issue.



Update 2: After reboot, the GRUB file is not found and system doesn't boot. I tried running the boot-repait utility and it fixed the grub. However the system boots into a black screen with a white blinking cursor, and does not show the login screen even after waiting for an hour.







boot startup kde-neon






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Dec 13 at 6:31

























asked Dec 11 at 7:37









kJd47

113




113




closed as too broad by G-Man, Rui F Ribeiro, schily, RalfFriedl, GAD3R Dec 12 at 7:23


Please edit the question to limit it to a specific problem with enough detail to identify an adequate answer. Avoid asking multiple distinct questions at once. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.






closed as too broad by G-Man, Rui F Ribeiro, schily, RalfFriedl, GAD3R Dec 12 at 7:23


Please edit the question to limit it to a specific problem with enough detail to identify an adequate answer. Avoid asking multiple distinct questions at once. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.














  • How did you get to a prompt where you could run startx if the boot process gets stuck? Please can you clarify -- in your question.
    – roaima
    Dec 11 at 22:24










  • I opened the prompt with Ctrl+Alt+F3
    – kJd47
    Dec 13 at 6:29










  • So it did boot - at least to a login prompt?
    – roaima
    Dec 13 at 7:20










  • It is presently showing just a blank screen with a blinking cursor. However, I am able to access the login prompt at this stage.
    – kJd47
    Dec 13 at 9:54




















  • How did you get to a prompt where you could run startx if the boot process gets stuck? Please can you clarify -- in your question.
    – roaima
    Dec 11 at 22:24










  • I opened the prompt with Ctrl+Alt+F3
    – kJd47
    Dec 13 at 6:29










  • So it did boot - at least to a login prompt?
    – roaima
    Dec 13 at 7:20










  • It is presently showing just a blank screen with a blinking cursor. However, I am able to access the login prompt at this stage.
    – kJd47
    Dec 13 at 9:54


















How did you get to a prompt where you could run startx if the boot process gets stuck? Please can you clarify -- in your question.
– roaima
Dec 11 at 22:24




How did you get to a prompt where you could run startx if the boot process gets stuck? Please can you clarify -- in your question.
– roaima
Dec 11 at 22:24












I opened the prompt with Ctrl+Alt+F3
– kJd47
Dec 13 at 6:29




I opened the prompt with Ctrl+Alt+F3
– kJd47
Dec 13 at 6:29












So it did boot - at least to a login prompt?
– roaima
Dec 13 at 7:20




So it did boot - at least to a login prompt?
– roaima
Dec 13 at 7:20












It is presently showing just a blank screen with a blinking cursor. However, I am able to access the login prompt at this stage.
– kJd47
Dec 13 at 9:54






It is presently showing just a blank screen with a blinking cursor. However, I am able to access the login prompt at this stage.
– kJd47
Dec 13 at 9:54

















active

oldest

votes






















active

oldest

votes













active

oldest

votes









active

oldest

votes






active

oldest

votes

Popular posts from this blog

List directoties down one level, excluding some named directories and files

list processes belonging to a network namespace

list systemd RuntimeDirectory mounts