Uninstalled plymouth, new issues found

English Applications
#1

Using GNOME desktop environment.

So I finally got rid of plymouth by doing this:

zypper rm libply* plymouth*
zypper al libply4 libply-boot-client4 libply-splash-core4 libply-splash-graphics4 plymouth plymouth-branding-openSUSE plymouth-dracut plymouth-plugin-label-ft plymouth-plugin-script plymouth-scripts
mkinitrd

(Not sure if I could also have just done “zypper al libply* plymouth*”; could someone please clarify if possible?)

After rebooting, past the Grub screen, I see the very usual two “USB port overcurrent state” console lines I always have had after Grub screen and just before plymouth. But that’s it. All the booting logs I got -showing all processes and services being started- when hitting Esc key during plymouth screen are gone. Hitting Esc key now does nothing obviously. Just the USB overcurrent lines until I get the message “Welcome to openSUSE box” and shortly after the graphic login screen.

I really thought by removing plymouth I’d just get directly all those system messages without having to hit Esc, but now it turns they’re all gone as well! Were those messages actually part of plymouth?

On the other hand, though, I noticed some messages do appear now when system is shutting down. However the very first one is always “[FAILED] Unmounting /var/log”.

Any help about all this?

Thanks again.

#2

Go into the Yast Bootloader.

Middle tab, change the boot command. Take all the other options off the end, put just this after resume=(disk/partition info, is probably a uuid)

 splash=verbose showopts
#3

Just one minor warning. This settings will slow down startup speed. I wanted verbose mode in the past and I was wondering why everyone keep saying that openSUSE boots fast when it wasn’t true. Until I reverted settings to default a saw that boot could be fast.

#4

Hi
The [Failed] unmounting is normal as it’s still writing to the journal, can be ignored as further on umounting completes…

#5

Thanks all very much.

Indeed I kind of felt that booting speed seems slightly faster, but I didn’t want to mention it since I don’t have solid numbers and this could have been just a subjective guess…

So uninstalling plymouth actually turns those boot splash verbose messages off by default? Was it expected?

Needless to say I have never ever messed with Yast Bootloader stuff, thus I have no way to know how it was configured prior to plymouth removal.

#6

Well, I have not noticed any slowdown on mine. Maybe something to do with the graphic card you have, or monitor, output to the monitor is too slow?

But, no problem here, boots plenty fast on my 10-yr-old machines, verbose on or off.

#7

I have removed plymouth in the past. But, after experimenting, I ended up reinstalling it. But I did change the grub boot line by removing “splash=silent”. So plymouth remains installed, but sits quietly in the background not doing much.

And I do see lots of messages on the boot screen.

#8

Excuse me, if possible I’d want to know if this doubt could still have a reply…

Thanks again.

#9

Did you run:

mkinitrd

as root after removing Plymouth?

When I have removed plymouth, I have seen lots of logging to the screen during bootup. But some of that is set in the “initrd”, so if you didn’t rebuild that you might be getting mixed results.

#10

Of course I did. See my first post for the commands I used (all run as root user).

#11

Then I don’t know why you are seeing that.

It has been a while since I last tried disabling plymouth (probably two years), so I don’t have recent experience. I’ve just found it more congenial to keep plymouth installed, but tell it to not display its splash screen.

#12

On Mon 16 Jul 2018 08:56:03 PM CDT, F style wrote:

Using GNOME desktop environment.

So I finally got rid of plymouth by doing this:

Code:

zypper rm libply* plymouth*
zypper al libply4 libply-boot-client4 libply-splash-core4
libply-splash-graphics4 plymouth plymouth-branding-openSUSE
plymouth-dracut plymouth-plugin-label-ft plymouth-plugin-script
plymouth-scripts mkinitrd --------------------

(Not sure if I could also have just done “zypper al libply* plymouth*”;
could someone please clarify if possible?)
<snip>

Hi
You are fine with what you ran, here is the plymouth stuff I have
removed and locked (as well as rebuilt initrd)


zypper ll

5  | libply-boot-client4        | package | (any)
6  | libply-splash-core4        | package | (any)
7  | libply-splash-graphics4    | package | (any)
8  | libply4                    | package | (any)
9  | plymouth                   | package | (any)
10 | plymouth-branding-openSUSE | package | (any)
11 | plymouth-dracut            | package | (any)
12 | plymouth-plugin-label      | package | (any)
13 | plymouth-plugin-label-ft   | package | (any)
14 | plymouth-plugin-script     | package | (any)
15 | plymouth-plugin-two-step   | package | (any)
16 | plymouth-scripts           | package | (any)

The above is on my Tumbleweed system, I do the same on all my
systems…

–
Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
SLES 15 | GNOME Shell 3.26.2 | 4.12.14-23-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!

#13

… as do I. I like the boot-up info flying by, and I like the less overhead.

#14

By chance, could someone help understanding why I’m no longer seeing the starting processes and services logs?
Could plymouth uninstalling actually turn those “boot splash verbose” messages off by default?
As I also mentioned, I have no clue of how it was configured prior to plymouth removal.

Thanks.

#15

Hi
Yup, bootup to gnome desktop is less that 25 seconds…lol If really want to see the boot, just user journalctl… just add the systemd-journal group to my user and all is good

#16

One of the first things I did when I installed 15.0 was to delete all of Plymouth. Then I just tabooed Plymouth itself and left all of the other stuff untouched. Is it recommended that I taboo all the things listed up thread, in addition to plymouth itself, ie


5  | libply-boot-client4        | package | (any)
6  | libply-splash-core4        | package | (any)
7  | libply-splash-graphics4    | package | (any)
8  | libply4                    | package | (any)
9  | plymouth                   | package | (any)
10 | plymouth-branding-openSUSE | package | (any)
11 | plymouth-dracut            | package | (any)
12 | plymouth-plugin-label      | package | (any)
13 | plymouth-plugin-label-ft   | package | (any)
14 | plymouth-plugin-script     | package | (any)
15 | plymouth-plugin-two-step   | package | (any)
16 | plymouth-scripts           | package | (any)
#17

Dependencies should not in general need a taboo. Since they should only get installed if the dependent code is installed. But YMMV

#18

Thank you.

#19

Ok, so in Yast Bootloader options I had something like this:

resume=(disk/partition) splash=silent quiet showopts

So just replaced the quiet options with “verbose”.

Boot logs seemed to be back… apparently. It’s definitely different from plymouth’s Esc key logs. There are much more lines besides the usual [OK] ones, logs roll much faster making it difficult to read, font size is slightly smaller…
Though booting time didn’t feel different…

Did plymouth actually ship its own “logs”?
And, as mentioned before, I don’t know how bootloader options were configured prior to plymouth removal. Could someone confirm?

Thanks.

#20

From original 42.3 installation, I had:

resume=/dev/nwr2wdc2/swap splash=silent quiet showopts

I later changed that to

resume=/dev/nwr2wdc2/swap quiet showopts

And note that “/dev/nwr2wdc2/swap” is just the swap logical volume from my encrypted LVM. Generally, “resume=” should designate the swap file system.