I don't know how I initially got there, but I kept the old version's .deb archived around when I first encountered the issue, and installed them with dpkg -i afterwards.
And whether shim-signed is installed or not makes no difference, it just affects the defaults grub is using. I always have to make sure "--no-uefi-secure-boot" is used (which is implicitly set if shim-signed is not installed AFAIK). Am Mo., 10. Juni 2019 um 02:51 Uhr schrieb Steve McIntyre <st...@einval.com>: > > Hi Norbert, > > On Sat, May 11, 2019 at 12:00:41PM +0200, Norbert Lange wrote: > >I got newer versions to work by adding the "--no-uefi-secure-boot" switch, > >so apparently uefi-secure-boot is not working for me. > > > >older versions might have defaulted to not using it, > >or I did not have the shim packages installed. > > I'm curious how you got here. Did you install with Recommends > disabled? There's a Recommends: chain from grub-efi-amd64-bin to > grub-efi-amd64-signed to shim-signed which should cause shim-signed to > be installed. > > Does installing shim-signed fix your problem? > > -- > Steve McIntyre, Cambridge, UK. st...@einval.com > You raise the blade, you make the change... You re-arrange me 'til I'm sane... >
