Skip to content

SLES 16.0: Fix wording around Secure Boot #57

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
KucharczykL merged 2 commits into from
May 19, 2026
Merged

SLES 16.0: Fix wording around Secure Boot #57

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
76ad83d
SLES 16.0: Fix wording around Secure Boot
KucharczykL May 18, 2026
73624c9
Clarify Secure Boot configuration details
KucharczykL May 19, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions adoc/sles/version160.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -782,9 +782,9 @@ include::../shared.adoc[tag=jscped-15968,leveloffset=+3]
[#bsc-1253242]
==== Secure Boot

If {productname} {this-version} has been installed on IBM z16 or later on an ECKD DASD as boot disk, the configuration parameter `SECURE_BOOT` in `/etc/sysconfig/bootloader` is automatically set to `no`, although the used hardware supports Secure Boot from ECKD DASD.
If {productname} {this-version} has been installed, the configuration parameter `SECURE_BOOT` in `/etc/sysconfig/bootloader` is automatically set to `yes`.

To enable Secure Boot support in this case, change the value for `SECURE_BOOT` in `/etc/sysconfig/bootloader` from `no` to `yes` and run `grub2-zipl-setup`.
Please be aware that a combination of ECKD-DASD disk and Linux One III won't support Secure Boot.


==== In-kernel crypto support
Expand Down
Loading