As I know now, I’ve been (and still am) bitten by a bug in the amdgpu driver, see here: https://gitlab.freedesktop.org/drm/amd/-/issues/4749
Well, before I messed around with the kernel parameters, without making a backup. So the whole line of optional kernel parameters now is
security=selinux selinux=1
Before there was
resume=...
and more. Hibernate no longer works.
Well, I thought, maybe there is a script which I can call that gets the usual parameters back?
@cookie170 Hi, if Secure Boot is enabled, no hibernate only suspend. What does inxi -Ixxx show for hibernate?
hibernate: platform
Thank you, I switched in BIOS secure boot off and hibernate is back and it works, so somehow the linux kernel knows where the swap partition is, even without resume=/dev/disk in the optional kernel parameters.
However, how do I recreate the mostly empty line of optional kernel boot parameters?
It is better to show then to tell. Thus for the parameters of the present running kernel:
cat /proc/cmdline
@cookie170 what @hcvv has asked for. Then to add you use update-bootloader --add-option some_option then once you have added, then update-bootloader --config to complete. If you want to remove an option, then use --del-option and update the config.
I’m flabbergastet. In Yast / System / Bootloader / Kernel-Parameter there are only the two selinux parameters. But obviously there are more:
cat /proc/cmdline
BOOT_IMAGE=/opensuse-tumbleweed/6.19.7-1-default/ linux-2508a0261559570ccd3719c662339710288c296b splash=silent resume=/dev/disk/by-uuid/fe69d327-b6d3-47b3-91f1-3c7d1863f68d quiet security=selinux selinux=1 mitigations=auto root=UUID=ebfefc77-ee23-4dca-b4e1-f47f2f53b333 systemd.machine_id=582b8ffb6c1e4284a492d4594f7049fd
OK, so editing the kernel-parameters in Yast does not change anything.
And I tried
update-bootloader --del-option mitigations=off
and then
update-bootloader --config
– to no avail, mitigations still there, when I rebooted.
update-bootloader --show
grub2-bls
This is so strange. Thank you for your help!
For #1 and #2 , I’m going to take a wild guess on this … it is possible I’m misunderstanding.
When using YaST for configuring the Kernel-related stuff, there are ALSO Checkboxes that (represent) result in actual kernel parameter text entries.
For example, I think there is a “Mitigations” Checkbox (though my memory might be bad) which results (if Checkbox is selected) in the “mitigations=auto” kernel command line entry.
So, you wont see the text in YaST Kernel Command line entry, but the Checkbox is checked … but when you do a
“# cat /proc/cmdline”, it will show up in the output.
As long as you do not help us by showing what we asked for, there is nothing to thank us for.
Yast still work on grub-efi, but with the grub-bls it’s not supported.
Sorry, but I did so!
What does cat /etc/kernel/cmdline show?
The way to adjust boot parameters for GRUB2-BLS specifically:
Edit /etc/kernel/cmdline
and issue:
sudo sdbootutil update-all-entries
@marel update-bootloader should work fine, does here on grub2-bls