Re: anyone booting debian with secure boot enabled? And/or from GPT partitions?
On 7/14/2015 5:45 PM, Joel Rees wrote:
Last I heard, debian was not participating in any of the initiatives
to get officially microsoft-signed signatures for kernels. I've been
out of the community for a few months, so I haven't kept up with this,
but quick searches don't reveal a change in policy.
(And I am definitely not arguing for a change in policy, for anyone
who might misread me.)
I have a netbook that allows secure boot to be disabled. As long as I
don't need to boot MSWindows, I just disable secure boot. (I don't
perceive any real advantage in Microsoft's implementation, anyway.)
Windows can be a bit odd with the boot stuff at times, but generally it
doesn't have an
issue booting when the secure boot setting is changed, but some times it
seems to, so
YMMV.
It does have an issue switching between legacy and UEFI boot modes. So
if your laptop
maker did not give you separate options to enable/disable secure boot
and switch between
UEFI/legacy, they didn't do you any favors there.
To confuse the issue even more, they may call the option to turn legacy
mode on and off
CSM (Compatibility Support Module), not as straight forward as legacy,
but at least named for what
it is, unlike my MSI desktop board which puts some of these options in
a "Windows boot options"
section worded in a way that leaves you a little unsure even if you
think you know what the
options should do relative to the terminology the should/would normally
be used.
I don't have dual boot set up at the moment, my old windows install was
already broken, now
that I upgraded my system and changed to a UEFI boot I need to reinstall.
Being that I'm on a desktop system, I install Linux on one hard drive
and Windows on another,
leaving my Linux hard drive unplugged during the Windows install.
It's been a long time since I dual booted with Linux and Windows both on
a single hard drive.
Starting with Vista there were issues with some updates if Windows did
not control the MBR,
if I remember right these all had to do with bitlocker encryption stuff
being updated and wanting
to verify stuff in the MBR during the update, so probably not an issue
if you had the basic/home
premium versions of Windows since those versions did not do bitlocker
encryption. Whenenver
I hit one of these updates I would go into the BIOS and put the Windows
drive first in the boot order.
Probably also not an issue if your hard drives are GPT initialized using
EFI boot.
If you need to access files in the Windows partition from Linux, you may
need to turn hibernation
off in Windows 8. If you get complaints about hibernation/fastboot when
you try to mount the
Windows partition in Linux you need to boot into Windows, open a command
window with
administrator rights and issue the command:
powercfg /hibernate off
Later, Seeker
Reply to: