Control: tag -1 serious On Thu, May 21, 2026 at 10:52:49PM +0200, Michael Biebl wrote: >Hi Steve > >Am 21.05.26 um 19:53 schrieb Steve McIntyre: >> On Thu, May 21, 2026 at 07:05:34PM +0200, Michael Biebl wrote: >> > >> > I have a dual boot system with Windows 11 and Debian Sid. >> > >> > Grub is setup to generate a boot entry for Windows (via 30_os-prober). >> > >> > This has worked fine so far. >> > >> > Since the upgrade of shim-signed from 1.47 to 1.50, I can no longer boot >> > Windows. After selecting the boot entry, grub just "hangs" and does >> > nothing. >> >> Argh. What hardware is this on, please? > >It's a framework 13, AMD 7040
Cool. >> Shim does have built-in debug here, which might help. From userland >> could you please try >> >> $ mokutil --set-verbosity true >> >> and see if anything obvious shows up? Warning: it is *very* verbose >> here. > >You did not exaggerate. I got walls of text for about a minute or so (Can I >capture this output somehow)? There isn't any way, really. We end up grabbing video if we have to, or serial output if that's possible (which doesn't happen on most real hardware). >After grub had finally loaded, I selected the Windows boot entry. > >What you see in the attached screen shot is what happened next. > >At this point, the boot process stops. I can reset the machine via >CTRL+ALT+DELETE. ACK, thanks! I'm annoyed with myself - my own test machine was working fine for booting through to Windows here. But I still had trixie's grub packages installed. Argh. I've just upgraded and retested here and I see the same issue. So you're not alone and this is not hardware/firmware specific. I've just set this bug to be RC; let's stop this from migrating until we've had a chance to work out what's happening. -- Steve McIntyre, Cambridge, UK. [email protected] Is there anybody out there?
