That is correct, yeah. Wouldnt do you any harm to backup your ESP
beforehand, though it's unlikely to be more than a precaution

On Sun, 10 Apr 2022 at 10:13, Adam Carter <adamcarter3@gmail.com> wrote:

I'm assuming that windows will modify the EFI configuration and i will need to boot, say, a minimal cd image to run efibootmgr to set it back, then add a Windows entry to the grub config.

Is that correct? Anything else i should be concerned about?

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

I'm assuming that windows will modify the EFI configuration and i will need
to boot, say, a minimal cd image to run efibootmgr to set it back, then add
a Windows entry to the grub config.

Is that correct? Anything else i should be concerned about?

<div dir="ltr">I&#39;m assuming that windows will modify the EFI configuration and i will need to boot, say, a minimal cd image to run efibootmgr to set it back, then add a Windows entry to the grub config.<br><br>Is that correct? Anything else i should
be concerned about?</div>

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On 10/04/2022 01:30, Miles Malone wrote:

That is correct, yeah. Wouldnt do you any harm to backup your ESP
beforehand, though it's unlikely to be more than a precaution

On Sun, 10 Apr 2022 at 10:13, Adam Carter <adamcarter3@gmail.com> wrote:

I'm assuming that windows will modify the EFI configuration and i will need to boot, say, a minimal cd image to run efibootmgr to set it back, then add a Windows entry to the grub config.

Is that correct? Anything else i should be concerned about?

iirc (and I'm about to do it again), Windows just makes itself default,
and sets boot timeout to 0.

So no I wouldn't bother modifying grub - just set the EFI timeout to,
say, 5 secs. You then choose between Windows and grub, and then let grub
sort out the linux side for you.

I notice you're using a second drive, though. At least linux is on drive
0, with a decent EFI partition. I had another system with linux on drive
1. Windows made the EFI partition on drive 0 tiny, and I never worked
out how to chain the two EFI partitions together. Couldn't put grub on
drive 0, the partition was too small.

So, yes. In theory it's easy. In practice...?

Cheers,
Wol

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

iirc (and I'm about to do it again), Windows just makes itself default,
and sets boot timeout to 0.

So no I wouldn't bother modifying grub - just set the EFI timeout to,
say, 5 secs. You then choose between Windows and grub, and then let grub
sort out the linux side for you.

Ok, will do.

I notice you're using a second drive, though. At least linux is on drive
0, with a decent EFI partition. I had another system with linux on drive
1. Windows made the EFI partition on drive 0 tiny, and I never worked
out how to chain the two EFI partitions together. Couldn't put grub on
drive 0, the partition was too small.

Actually the free drive is nvme0n1... I was running out of space on that
device so added nvme1n1 and moved Gentoo to that drive. On nvme1n1
partition 1 is 1gig for both EFI and /boot (with a minimal .iso available
via grub as a rescue option if needed).

With regards to windows making a tiny EFI partition on drive 0, i dont
think I understand the issue. I'm thinking I can either;
1. Use the EFI boot loader to choose between Windows and Linux, as you
mention above, with the small downside of having two boot loaders/timeouts,
or
2. Use EFI to default to grub on the second drive with a very short timer
(so its like its not even there) and put an entry for Windows in the grub config

I will probably try #1 first, then update the grub config to boot windows
and confirm that works, then change to #2.

Let me know if i'm misunderstanding anything.

Thanks!

<div dir="ltr"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
iirc (and I&#39;m about to do it again), Windows just makes itself default, <br>
and sets boot timeout to 0.<br>

So no I wouldn&#39;t bother modifying grub - just set the EFI timeout to, <br> say, 5 secs. You then choose between Windows and grub, and then let grub <br> sort out the linux side for you.<br></blockquote><div><br></div><div>Ok, will do. <br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">

I notice you&#39;re using a second drive, though. At least linux is on drive <br>
0, with a decent EFI partition. I had another system with linux on drive <br> 1. Windows made the EFI partition on drive 0 tiny, and I never worked <br>
out how to chain the two EFI partitions together. Couldn&#39;t put grub on <br> drive 0, the partition was too small.<br></blockquote><div><br></div><div>Actually the free drive is nvme0n1... I was running out of space on that device so added nvme1n1 and moved Gentoo to that drive. On nvme1n1 partition 1 is 1gig for both EFI and /
boot (with a minimal .iso available via grub as a rescue option if needed).</div><div><br></div><div>With regards to windows making a tiny EFI partition on drive 0, i dont think I understand the issue. I&#39;m thinking I can either;</div><div>1. Use the
EFI boot loader to choose between Windows and Linux, as you mention above, with the small downside of having two boot loaders/timeouts, or<br></div><div>2. Use EFI to default to grub on the second drive with a very short timer (so its like its not even
there) and put an entry for Windows in the grub config<br></div><div><br></div>I will probably try #1 first, then update the grub config to boot windows and confirm that works, then change to #2.<br></div><div class="gmail_quote"><br></div><div class="
gmail_quote">Let me know if i&#39;m misunderstanding anything.</div><div class="gmail_quote"><br></div><div class="gmail_quote">Thanks!<br></div></div>

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

FYI, the windows installer added an entry to the EFI boot loader (as
Boot0000), but left Gentoo as the active entry;

# efibootmgr
BootCurrent: 0003
Timeout: 15 seconds
BootOrder: 0003,0000,0008,0007,0001,0002
Boot0000* Windows Boot Manager
Boot0001* Hard Drive
Boot0002* Network Card
Boot0003* 980GrubEFI
Boot0007* USB HDD
Boot0008* UEFI: Patriot Memory PMAP, Partition 1

<div dir="ltr"><div>FYI, the windows installer added an entry to the EFI boot loader (as Boot0000), but left Gentoo as the active entry;</div><div><br></div><div># efibootmgr <br>BootCurrent: 0003<br>Timeout: 15 seconds<br>BootOrder: 0003,0000,0008,0007,
0001,0002<br>Boot0000* Windows Boot Manager<br>Boot0001* Hard Drive<br>Boot0002* Network Card<br>Boot0003* 980GrubEFI<br>Boot0007* USB HDD<br>Boot0008* UEFI:  Patriot Memory PMAP, Partition 1<br></div></div>

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

From my experience with UEFI systems: Windows no longer messes your boot completely (it just sets up the default entry to BCD loader) and you can
just select linux loader from the startup menu. So you don't really need to have a minimal cd image. Just switch default boot entry back to grub in
UEFI setup, boot back to your installed system and update grub config.
I was having another problem though: if you already have an EFI partition
and it's small then windows installer will try to create another one, but
then it fails after copying files since it's unable to decide which
partition it should use. Should be fine if you're using an empty drive or
if you don't have an EFI partition on that drive. But if you have - I
suggest you make it larger.

On Sun, Apr 10, 2022 at 4:14 AM Adam Carter <adamcarter3@gmail.com> wrote:

I'm assuming that windows will modify the EFI configuration and i will
need to boot, say, a minimal cd image to run efibootmgr to set it back,
then add a Windows entry to the grub config.

Is that correct? Anything else i should be concerned about?

--
Sergey Filatov (raxp)
Telegram: @raxpyraxp

<div dir="ltr"><div>From my experience with UEFI systems: Windows no longer messes your boot completely (it just sets up the default entry to BCD loader) and you can just select linux loader from the startup menu. So you don&#39;t really need to have a
minimal cd image. Just switch default boot entry back to grub in UEFI setup, boot back to your installed system and update grub config.<br></div><div>I was having another problem though: if you already have an EFI partition and it&#39;s small then
windows installer will try to create another one, but then it fails after copying files since it&#39;s unable to decide which partition it should use. Should be fine if you&#39;re using an empty drive or if you don&#39;t have an EFI partition on that
drive. But if you have - I suggest you make it larger.<br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Sun, Apr 10, 2022 at 4:14 AM Adam Carter &lt;<a href="mailto:adamcarter3@gmail.com">adamcarter3@gmail.com</a>&gt;
wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">I&#39;m assuming that windows will modify the EFI configuration and i will need to boot, say, a
minimal cd image to run efibootmgr to set it back, then add a Windows entry to the grub config.<br><br>Is that correct? Anything else i should be concerned about?</div>
</blockquote></div><br clear="all"><br>-- <br><div dir="ltr" class="gmail_signature">Sergey Filatov (raxp)<br>Telegram: @raxpyraxp</div>

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)