<html><head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body>
<p>Package: grub-efi-amd64</p>
<p><br>
</p>
<p>Summary: The defect occurs on a bullseye.rc1 install ; </p>
<p> install went normally using bullseye rc1; booting the
installed system fails<br>
</p>
<p> the UEFI boot sequence on a system that doesn't support
secure boot fails trying to access owner MOK</p>
<p><br>
</p>
<p><br>
</p>
<p>Hello Debian bullseye boot sequence team,</p>
<p>I dont have a screen grab and the message only stayed up a few
seconds.</p>
<p>The system is a Dell Precision T1200 E3, 16GB of memory, SSD,
installing off CDROM to an encrypted LVM with dedicated /boot and
encrypted LVM partitions.</p>
<p>The bullseye system was installed using the bullseye rc1 system
for an amd64 target.</p>
<p>Installation went normally; the difficulty lies when attempting
to boot the installed system off the ssd.</p>
<p>Again, the boot time error message that briefly showed on the
screen is that the MOK machine owner key could not be accessed.</p>
<p>I found a workaround using a previously installed Buster 10.9
system with a similar configuration:</p>
<p> a) boot Buster 10.9 dvd in recovery mode</p>
<p> b) rewrite the SSD bootstrap so the Buster 10.9 system boots</p>
<p> c) reboot into Buster 10.9</p>
<p> to diagnose what was going on I ran : <tt class="backtick">mokutil --disable-validation</tt></p>
<p><tt class="backtick"> the error message returned was 'this
system does not support secure boot'<br>
</tt></p>
<p> d) update buster /etc/grub.d/40_custom so it has the
bullseye rc1 boot stanza</p>
<p> e) update grub</p>
<p> f) shutdown the system</p>
<p> g) boot the buster grub and select the bullseye 11 rc1 boot
stanza present in 40_custom<br>
</p>
bullseye rc1 now runs
<p><br>
</p>
</body>
</html>