From 76ad83db8c48306bc2eab188dbf003add29173c2 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Luk=C3=A1=C5=A1=20Kucharczyk?= Date: Mon, 18 May 2026 18:11:57 +0200 Subject: [PATCH 1/2] SLES 16.0: Fix wording around Secure Boot --- adoc/sles/version160.adoc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/adoc/sles/version160.adoc b/adoc/sles/version160.adoc index 7d6efb1..16e7aa9 100644 --- a/adoc/sles/version160.adoc +++ b/adoc/sles/version160.adoc @@ -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`, although the used hardware supports Secure Boot from ECKD DASD. -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 From 73624c9f1fcc9a402eb3650615a8816bfa12d87b Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Luk=C3=A1=C5=A1=20Kucharczyk?= Date: Tue, 19 May 2026 10:20:28 +0200 Subject: [PATCH 2/2] Clarify Secure Boot configuration details Removed mention of ECKD DASD support for Secure Boot. --- adoc/sles/version160.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/adoc/sles/version160.adoc b/adoc/sles/version160.adoc index 16e7aa9..6df4502 100644 --- a/adoc/sles/version160.adoc +++ b/adoc/sles/version160.adoc @@ -782,7 +782,7 @@ include::../shared.adoc[tag=jscped-15968,leveloffset=+3] [#bsc-1253242] ==== Secure Boot -If {productname} {this-version} has been installed, the configuration parameter `SECURE_BOOT` in `/etc/sysconfig/bootloader` is automatically set to `yes`, 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`. Please be aware that a combination of ECKD-DASD disk and Linux One III won't support Secure Boot.