Hangs at starting show plymouth boot screen

By using our site, you acknowledge that you have read and understand our Cookie PolicyPrivacy Policyand our Terms of Service. Super User is a question and answer site for computer enthusiasts and power users.

It only takes a minute to sign up. I have a dell Inspiron laptop with nvidia graphics card, and genuine windows I tried to install ElementaryOS dual boot from bootable pendrive. But when i boot, it is showing only boot log files, i can barely read. At the end it stops at an error msg, 'failed to start: show plymouth bootscreen'.

Then i tried to mannually boot from grub command prompt. I selected kernel and initrd. But now i get a busybox error. So i searched and found i should run fsck command.

But initramfs is showing error: " command not found".

Sign up to join this community. The best answers are voted up and rise to the top. Home Questions Tags Users Unanswered. Ubuntu first boot showing error, 'failed to start: show plymouth boot screen' Ask Question. Asked 2 years, 7 months ago. Active 2 years, 7 months ago.

Viewed 2k times. At the end it stops at an error msg, 'failed to start: show plymouth bootscreen' I tried this with secure boot and fast boot off, also in legacy mode, but output was same.

Please help. No one else seem to have this problem.By using our site, you acknowledge that you have read and understand our Cookie PolicyPrivacy Policyand our Terms of Service. Ask Ubuntu is a question and answer site for Ubuntu users and developers. It only takes a minute to sign up. I was running my xubuntu-machine during the night.

In the morning I wanted to check something out and I noted that the computer does not respond anymore. It didn't even send a signal to my monitor. Anyway, I shut the machine down and restarted it. Generally, my computer seems to work be pretty slowly.

When I enter the grub menu everything takes ages. Another weird issue is that I cannot load a live-system or anything. I prepared a bootable USB to install a new ubuntu system but I end up with a black screen with only a cursor at the top left. I would like to check the CPU, but do not know which onboard-applications I can use As everything takes ages I cannot really install anything, or update anything. In the recovery grub mode I already tried to repair broken packages.

I got an error something like this: Message: 'not running quirks in partialUpgrad mode' Arguments:. My question: - How can I check all my hardware in this case? Ubuntu Community Ask! Sign up to join this community. The best answers are voted up and rise to the top.

Home Questions Tags Users Unanswered. Asked 2 years ago. Active 2 years ago. Viewed 3k times. My observations so far: Generally, my computer seems to work be pretty slowly. It seems to my that it is a HW issue. Henrik Henrik 11 1 1 silver badge 3 3 bronze badges. I still think the fsck option may show and hopefully correct issues you are having with the drive. Thanks so far!Downloads Support Community Development. Help Login Register. Advanced Search.

Unable to diagnose. Results 1 to 8 of 8. Thread: Boot sequence hangs. Join Date Oct Posts 4. Boot sequence hangs. Hi All, We are experiencing a strange problem with our installation of Leap The installation is on an LLVM partition.

The point where our server hangs is marked by a comment. Starting dracut pre-mount hook Starting Reload Configuration from the Real Root We also tried adding a debug option on the grub2 config file during bootup, so it shows more details during the boot sequence.

It spews a lot of details which can neither be piper to a file nor does it save that output to a log file on disc.

Below I have uploaded a screen shot of the output at the point where the boot sequence hangs with the debug option enabled. Any expert advice or suggestions for diagnose or fix what has gone wrong will be greatly appreciated.

Thank you! Re: Boot sequence hangs. I've seen that happen. And then I would reinstall the Nvidia driver. That was back when I was installing it "the hard way". I would guess that you have some kind of video driver problem.

Not knowing your hardware, it's hard to guess beyond that.

hangs at starting show plymouth boot screen

Thanks for the reply. There were no video card drivers that were updated in the recent past, we checked the log files.

One Solution to Ubuntu Hanging on the Boot Splash Screen

We don't believe this is due to any hardware drivers. No hardware was also changed. Any clues how we can make systemd more talkative to reveal more information about what exactly it is trying to find.

Subscribe to RSS

It is hanging earlier than my first reply suggested. I'm not seeing much that's helpful in the output. Join Date Sep Posts 5, After seeing that we can't seem to get any more output, we took the screen shots. Can you boot previous kernel version s?Start-up problems. That moment when — having expected yourself to be getting on with your day's work or entertainment — you find yourself staring at a cryptic error message, or even worse, a blank screen.

No matter how many times you press reset or restart, the same impenetrable barrier blocks your path. So, what can you do? Start-up problems come in all shapes and sizes, and they can be difficult to track down.

There are, however, some sound principles to use that will resolve many errors, and in this tutorial, we're going to look at the tools and techniques required to troubleshoot most start-up problems. You should start by examining how the boot process works. This reveals that the boot process can be split into three broad stages centred around the Grub 2 boot loader: pre-Grub, Grub and post-Grub.

hangs at starting show plymouth boot screen

Knowing this allows you to focus your troubleshooting efforts based on where in the process the error or freeze occurs. Let's start at the beginning. You switch on your PC. If power comes on, but nothing else happens, chances are you've a hardware issue to sort — if you recently poked around the innards of your PC, then check everything is connected correctly. If not, unplug all external devices except your keyboard and try again. If this doesn't work, open the case carefully and disconnect your internal drives too.

If the computer now boots to the splash screen, you can try reconnecting the internal drives and trying again; if you're now able to boot to the login screen, shut down your PC and start reconnecting your external peripherals to see if the problem has cleared itself or can be targeted to a single device, in which case try a different cable, or go online and Google for known boot problems involving that device.

If you're lucky, your motherboard will emit a series of beeps or flashing lights you can use — again by enlisting the help of the internet — to identify the likely problem. This may involve replacing a component or something more drastic.

If you're able to get as far as your PC's splash screen, but then your computer hangs or a 'missing operating system' error message appears, then first think back to any recent changes. Try rebooting again. If this fails, then the problem is likely to be with your hard drive, and so the first places to look are the MBR and Grub. If Grub isn't set to automatically appear when your PC starts, try rebooting while holding the Shift key or tapping Esc to bring up the Grub boot menu to confirm it's not able to even load itself.

Subscribe to RSS

You may get a specific error message or frozen splash screen, or you may just see Grub and nothing else, indicating it can't even find the most basic information required to proceed. If the Grub menu appears, then the issue may lie with its configuration file if things immediately grind to a halt after you select a menu option, but if Linux does start loading before grinding to a halt, the problem will lie with your operating system, in which case skip to the Post-Grub troubleshooting section.

If you're struggling to fix Grub issues by hand, or there's no sign of Grub on your system at all, then you'll need to enlist the services of your rescue media and the Boot-Repair tool, which works with all Debian-based distros, including Ubuntu.

The Boot-Repair tool itself will launch automatically when you boot from a Boot-Repair tool disc, but if you're unable to create it, but have access to a Linux installation disc, use that in a live environment instead, then grab the Boot-Repair tool using the following commands:. It basically provides a convenient and user-friendly graphical front-end to the tools required to fix many problems.

The tool offers a 'Recommended repair' option that promises to fix most frequent problems, or you can click 'Advanced options' to see what it can do and manually select specific fixes without getting your hands dirty in the Terminal.

The step-by-step guide see Tweak Boot-Repair tool Settings later in this guide reveals what repairs and tweaks are possible, but note the tool is context-sensitive, and some options may be greyed out or missing depending on your setup. The tool automatically generates a log of your system and that it attempts to do, which you can then share on the Ubuntu user forums if necessary. Before attempting any advanced tweaks on your own, it pays to try the recommended option first, then ask for help on the forums using the output logs generated — this will ensure you choose the right option and don't cause more damage.

When you press your system's power button, control is initially given to your PC's EFI or BIOS, which starts its various components, performs basic diagnostics tests and attempts to find a bootable device, which is typically the first hard drive. A 'missing operating system' error at this point means you need your rescue disc for diagnostics as something is missing — either in Grub, the MBR or the drive itself.

Once Grub loads successfully it reads a file called menu. Each entry basically identifies the drive, partition and file that contains the Linux kernel, plus RAM disk file used by the kernel as it boots.After rebooting I get the splash screen then I get a couple messages on the screen and it hangs. The messages I get are ones I've seen before and never bothered with becuause they don't cause issues normally.

I still get the messages if I disable splash in the bootloader, and it boots without issue. I'm not sure how to get a log of a previous boot, or if that's even possible.

Any help or advice would be appreciated, thanks in advance! As more information is required I'll edit it in here and post into another comment. What happens if you manually re-build the initramfs with mkinitcpio -p linux? What's your bootloader config? And which bootloader GRUB? Note that for my plymouth default themes, I do not have arch-glow:. If this is a custom theme, we will need those files too. I am diagnosed with bipolar disorder.

As it turns out, what I thought was my greatest weakness is now my greatest strength. Everyday, I make a conscious choice to overcome my challenges and my problems. It's not easy, but its better than the alternative After posting this I removed everything associated with Plymouth from my system and started over, leaving the default theme spinnerwith the same issue.

Before a meeting today I tried to view the boot messages as my laptop was booting with Plymouth, to see where it failed. I hit ESC and it showed me the boot messages and it booted fine i. Plymouth not showing at all, but still being loaded.

I'm wondering if it's an issue with lightdm-plymouth, gonna switch to regular lightdm and try again. Another question that copious Googling hasn't answered yet : is it possible to view previous boot logs? We still dont know which bootloader you are using by the way. I am using systemd-boot too, and that looks fine.

I'm suspecting that you are trying to use a non-existent theme at the moment.Post by i. Privacy Terms. Quick links. If starting the gdm it will get the system stucked.

I hope that you can assist me to recover the OS back to business. Last edited by i. CentOS 6 will die in November - migrate sooner rather than later! Full time Geek, part time moderator. Use the FAQ Luke. Re: starting wait for plymouth boot screen to quit after update Post by i.

I didn't use that because the login screen was not "fitted" to screen size and I changed back to old configuration without looking that more deeper. The upgrade failed from The boot process fails in very begging. This is totally "useless" and only HW -reset will boot the PC.

All other packets version are failing "starting wait for plymouth boot screen to quit after" In journal there are 2 lines EFI: Problem loading in-kernel X. I have run out of ideas a long time ago! Terminal is working at runlevel 3. You;ll likely be stuck at some black screen and will have to reset. Boot into init 3 again and have a look at the log.

From Xorg. I don't know if that's true for CentOS 7 now but it may be worth a bash.Ubuntu Forums Code of Conduct. Last Jump to page: Results 1 to 10 of December 11th, 1. Join Date Jun Beans I had about 2 months worth of updates that had piled up, so I started running all of them.

The process got halfway through, and then errored out. I didn't give it much attention, since this has happened before. I ran updates again, and it again got halfway through, and errored out again.

Again - I didn't really think much of it, I figured I'd just reboot and try again. It had been feeling a bit sluggish anyway.

hangs at starting show plymouth boot screen

Now I'm no longer able to get to the gui. I did a bit of searching, and found most people have reported this as an intermittent error, so I tried a few more times, and it is not intermittent for me. Any ideas??

How to repair Ubuntu if it won't boot

Update: I posted this to reddit as well, and was given some things to try out. Adv Reply. December 11th, 2. Really need to get to a terminal at this point:. December 13th, 3. I got into grub using esc. Wish I had known that earlier. I was also given this as an option. December 13th, 4. Making head way. Ok let's isolate this to the X GUI layer. In this screen arrow down to the line starting with "linux" and across to "quiet splash".

Log in here on this terminal with username and password. Now let's see what the system does when we start the GUI: Code:.


Leave a Reply

Your email address will not be published. Required fields are marked *

1 2