Hi, Fedora people.
It takes my PC approximately 2min 30sec to log in. From power up to having the desktop fully functional. This is what
systemd-analyze blame shows:
I understand very little about what this all means. What can I turn off? How do I do that? The step-by-step approach of any solution will help.
Can you also run
systemd-analyze critical-chain in your terminal?
One thing for certain is that you can disable and mask ModemManager.service.
Hi, man; this is what I got:
└─plymouth-quit.service @30.183s +223ms
└─systemd-user-sessions.service @30.057s +37ms
└─iscsi-shutdown.service @29.963s +582us
└─NetworkManager.service @29.326s +625ms
└─firewalld.service @12.776s +16.545s
└─polkit.service @19.022s +2.634s
└─dbus-broker.service @13.399s +4.544s
└─systemd-update-utmp.service @12.654s +42ms
└─systemd-tmpfiles-setup.service @12.336s +224ms
└─import-state.service @12.126s +207ms
└─lvm2-monitor.service @4.507s +5.591s
This is what
systemd-analyze blame shows me today:
Run these three commands as root:
systemctl stop ModemManager.service
systemctl disable ModemManager.service
systemctl mask ModemManager.service
The first one stops it, the second keeps it from being started at boot and the last makes sure that it can’t be started by some other service or program.
Ok. All three with
Man, you said it was SAFE! Now my PC won’t even boot up! It gets stuck on Fedora’s screen. Now what do I do? What’s the solution?
I damaged my PC! Now it won’t even start!
I’ve been masking those three services for years on numerous computers and there was never a problem.
Maybe something else has happened that is the cause of your problem.
Press ESC key and check why is the boot process stuck.
Man, which terminal am I gonna use those commands on? The PC won’t start!
Not at all?
If that is the case, you have a hardware fault which you need to repair…
I’ll try to describe the situation as best I can: when I turn on my PC, after the screen where it shows the installed kernels (there are usually three), it goes to the screen with the Fedora logo and gets stuck there. It does not start. It does not go past the Fedora screen.
When you get to the list of kernels, you should be able to use your cursor keys to select which kernel to boot. Try selecting the previous kernel, and if that boots, the issue is with the new kernel. If not, there should be a rescue option. That won’t get you a full system with a GUI, but it will allow you to correct whatever went wrong. If my memory’s not playing tricks with you, you’ll end up logged in as root. Try running these three commands:
systemctl unmask plymouth-quit.service
systemctl enable plyouth-quit.service
I picked that one to bring back because it’s the only one that I don’t personally know is safe to get rid of. Let us know if that works or if not, if it changes anything.
Also, try hitting the ESC key when you get at Fedora logo. This way you can see where the boot process stopped.
Ok, this is what ESC shows:
[FAILED] Failed to start Desktop Display Manager.
See ‘systemctl status sddm.service’ for details.
Interesting. I see you’re using KDE, am I right?
Somehow, this doesn’t happen on GNOME and XFCE…
I removed my initial suggestion to mask
systemctl mask plymouth-quit.service