You can verify if you are using an efi based system if the following command is successful or not
It is possible to use GPT on BIOS boot but not all system firmware is supporting it.
And there is no advantages nor benefits in doing so.
It is possible to configure a GPT partitioned disk device to be bootable whether you are using efi or bios - the only advantage is that you can move disk between systems that has firmware support GPT.
So being able to create a bios-boot partition like instructed by Calamares does not indicate a missing link.
The fact that your system has intermittent failures point more to hardware issue than an installer issue.
You should be aware that when using encryption on a manually partitioned systerm - how the aforementioned guide shows - it becomes difficult to manually implement suspend and hibernation.
When your power settings include suspend and hibernation settings - this will create weird issues - most likely states where you need to ensure RAM has be cleared - reboot the system twice holding the powerbutton the second time to ensure clearing variables telling the systems NVRAM to resume from hibernation.
Sorry, I’m not following this.
I’m assuming I have to login as root?
“# list boots” not found when I type it in the terminal.
Here’s another thought.
I can login bypassing the splash screen by hitting the Esc key as soon as I enter the encryption password. Then I can edit the grub in etc/default/grub.
Is there anything I can uncomment or delete editing the grub file in order to bypass the splash and then do a “sudo update-grub”?
SOLUTION I am using EFISTUB and it turns out that the new kernel parameters set by efibootmgr weren’t taken into account… Just found out that I have to boot to the UEFI menu and lauch from there once, before the EFI entry is updated with the new parameters… so tried installing Plymouth again, and it now works perfectly
I’m unsure how to translate that into testable steps for Manjaro kde
Yes, I’ve used the Manjaro How-to for changing to systemd-boot that was written by a famous an very active forum member
I made a first trial with the more modern ‘kernel-install’ approach and realized that the error did’nt disapear. Then I used the ‘manual’ way and switched the mkinitcpio hooks from ‘encrypt’ to ‘sd-encrypt’. So my boot procedure completly different now but the splash screen is not activated, jet.
’ This usage of systemd-boot can be deducted from the sd- entries in the HOOKS line.’
Please let me detail that:
Systemd-boot can can decrypt by using the ‘encrypt’ hook. There is no need to change to the ‘sd-boot’ hook. In this case the same decryption skripts are used that are called by grub. But when you change from ‘encrypt’ to ‘sd-encrypt’ then systemd starts the decryption. (I’ve repeated my installation a few times bevore I’ve learned that.)