After updating “plymouth-theme-manjaro” package, I get a black screen instead of the entire startup process!
What should I do?
See if disabling it will fix it, add to the kernel boot line (hit E when grub shows)
plymouth.enable=0 disablehooks=plymouth
If it fixes it it can be made permanent in the grub (ask if you do not know how)
1 Like
What I’d suggest is to remove quiet and splash from the GRUB_CMDLINE (in /etc/default/grub, then update GRUB) and also remove plymouth from the HOOKS= line in /etc/mkinitcpio.conf.
1 Like
No grub or boot menu, missing.
No work “E”.
Black screen, after a while the KDE login screen appears
It’s not even a question of why the hell would a faulty package be included in the updates?
You wrote above you have black screen and now that you boot successfully…anyways, pumping ESC early in the boot will show the grub menu.
Or, one can make the grub menu visible at every boot by changing… 
GRUB_TIMEOUT_STYLE=hidden
… into…
GRUB_TIMEOUT_STYLE=menu
… in the file /etc/default/grub, and then running…
sudo update-grub
Of course, everyone should know this by now, but you know, "n00bses happens, Preciousss". 
3 Likes
Sry but ESC show BIOS/UEFI settings.
In that case, the timing wasn’t right - give it a little more time before spamming ESC.
Since your system does boot, you can also edit /etc/default/grub and remove the “splash” keyword.
And possibly also /etc/mkinitcpio.conf and remove the “plymouth” keyword from the HOOKS line.
sudo mkinitcpio -P
sudo update-grub
That will achieve the same effect - but will be permanent.
Until you edit the words in again …
Did you do a full update or did you just update the plymouth-theme-manjaro package?
2 Likes
Definitely, make these grub changes..
If we’re still in the same boat. What is the output of your:
inxi -Gxxx
(I also have a “black screen” after this update. But it’s just one of them.)
It’s a matter of timing. If like mine, your BIOS displays its own logo as it’s initialising, the time to hit is just after that logo vanishes. If not, unfortunately it’s likely to need some guesswork.
1 Like
Reinstall plymouth-theme-manjaro:
A(z) plymouth-theme-manjaro (2.2-3) reinstall...
....
-> -k /boot/vmlinuz-6.18-x86_64 -g /boot/initramfs-6.18-x86_64.img
==> Starting build: '6.18.4-1-MANJARO'
-> Running build hook: [base]
-> Running build hook: [udev]
-> Running build hook: [autodetect]
-> Running build hook: [microcode]
-> Running build hook: [kms]
-> Running build hook: [modconf]
-> Running build hook: [block]
-> Running build hook: [keyboard]
-> Running build hook: [keymap]
-> Running build hook: [consolefont]
==> WARNING: consolefont: no font found in configuration
-> Running build hook: [plymouth]
-> Running build hook: [resume]
-> Running build hook: [filesystems]
==> ERROR: module not found: 'crc32c_intel'
Error configuring plymouth-theme-manjaro
==> Generating module dependencies
==> Creating zstd-compressed initcpio image: '/boot/initramfs-6.18-x86_64.img'
==> WARNING: errors were encountered during the build. The image may not be complete.
Error a(z) plymouth-theme-manjaro konfigurálásakor
==> Running post hooks
-> Running post hook: [sbctl]
Secureboot key directory doesn't exist, not signing!
==> Post processing done
Error: plymouth-theme-manjaro: the command did not run correctly
The transaction was successfully completed.
2-3 post above the advice to REMOVE the plymouth hook was given, but you didn’t, soooo 
1 Like
Teo Community Assistant
Sorry it wasn’t quite clear, delete from here? /etc/mkinitcpio.conf
HOOKS=(base udev autodetect microcode kms modconf block keyboard keymap consolefont plymouth resume filesystems)
I’m a bit reluctant to take advice, I wouldn’t want to ruin my system.
$ mkinitcpio -P
==> WARNING: consolefont: no font found in configuration
-> Running build hook: [resume]
-> Running build hook: [filesystems]
==> ERROR: module not found: 'crc32c_intel'
==> Generating module dependencies
==> Creating zstd-compressed initcpio image: '/boot/initramfs-6.18-x86_64.img'
==> WARNING: errors were encountered during the build. The image may not be complete.
yes
remove the word “plymouth” from that line:
You can always add it back later - that is just responsible for the eye candy splash screen.
the mkinitcpio -P output is ok
Maybe someone can comment on the crc32c_intel error displayed there.
2 Likes
OK
crc32c-intel is deprecated and the new name is crc32c
to modify?
MODULES=(crc32c-intel)
to
MODULES=(crc32c)
I don’t know whether it is needed at all or what it is for
some hardware acceleration feature, from what I could gather by a bit of googling -
but yes,
use the now “new” correct name of the module in the MODULES array.
… the other one (crc32c-intel) doesn’t exist anymore with newer kernels, hence the error “module not found”
1 Like
Try with MODULES=(crc32c) or remove it completely.
1 Like
Newer kernels have it built in and enabled by default. So you can leave it out.
I forget the version kernel it starts (5.15?), but you can check.
gzip -cd /proc/config.gz | grep CRC32C
CONFIG_CRYPTO_CRC32C=y
CONFIG_LIBCRC32C=y
2 Likes
Tip
When posting terminal output, copy the output and paste it here, wrapped in three (3) backticks, before AND after the pasted text. Like this:
```
pasted text
```
Or three (3) tilde signs, like this:
~~~
pasted text
~~~
This will just cause it to be rendered like this:
Sed
sollicitudin dolor
eget nisl elit id
condimentum
arcu erat varius
cursus sem quis eros.
Instead of like this:
Sed sollicitudin dolor eget nisl elit id condimentum arcu erat varius cursus sem quis eros.
Alternatively, paste the text you wish to format as terminal output, select all pasted text, and click the </> button on the taskbar. This will indent the whole pasted section with one TAB, causing it to render the same way as described above.
Thereby increasing legibility thus making it easier for those trying to provide assistance.
For more information, please see:
As I’m a moderator on the forum, I have taken the liberty of doing this for you, this time.
Additionally
If your language isn’t English, please prepend any and all terminal commands with LC_ALL=C. For example:
LC_ALL=C bluetoothctl
This will just cause the terminal output to be in English, making it easier to understand and debug.
Note that the above text is partially pre-prepared as a general introduction for new forum Users. Please take the time to to understand how it is done and encourage quality responses.
1 Like
This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.