public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Peter Humphrey <peter@prh.myzen.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Dual booting with Windows 10
Date: Mon, 24 May 2021 14:11:00 +0100	[thread overview]
Message-ID: <2588375.mvXUDI8C0e@wstn> (raw)
In-Reply-To: <1870789.yKVeVyVuyW@lenovo.localdomain>

On Friday, 21 May 2021 20:06:25 BST Michael wrote:
> On Friday, 21 May 2021 15:42:01 BST peter@prh.myzen.co.uk wrote:
> > Hello list,
> > 
> > Mynew machine has Win-10 installedon /dev/nvme0n1 with the ESP as
> > partition
> > 1. I want to install Gentoo on /dev/nvme1n1. So far I haven't found a way
> > to set up a working boot arrangement. I've tried mounting the ESP on /efi,
> > on /EFI and on /boot/EFI. Efibootmgr seems to write a boot entry in some
> > of
> > those cases, and it's still there after a reboot - but it isn't visible to
> > the BIOS.
> > 
> > Can anyone offer some enlightenment, please?
> 
> If your ESP is on /dev/nvme0n1 and you are using vmlinuz symlinks, you can
> use /boot/EFI as the mountpoint for the ESP VFAT partition.  Your
> kernels/config/ System.map/initrd.img files will go into /boot, which will
> be on the same fs as / on /dev/nvme1, using a fs which supports symlinks.
> 
> The efibootmgr '--loader' option should/could be used to specify the path to
> your bootloader image, or if you are not using a bootloader image to
> chainload your kernel with, point it directly to the path of your kernel;
> e.g.
> 
> efibootmgr --create --disk /dev/nvme0n1 --part 1 --label "gentoo-5.10.27" \
> --loader "\EFI\gentoo\gentoo-5.10.27.efi"
> 
> The BIOS/UEFI menu should be able to list entries of bootable *.efi images,
> as long as they are within the subdirectory of /boot/EFI on the ESP, but if
> you are using a bootloader, then it is the bootloader image which will run
> and chainload your OSs and their kernels.

Thanks Michael. I've finally got it booting, by resorting to the same hack as I 
did on my previous machine.

Using efibootmgr to add a UEFI boot record does create it, but selecting it in 
the BIOS fails and it just drops to the next in line: Windows 10. No 
adjustments to the --create command resulted in a bootable system, so I had to 
run bootctl-install as well and then remove the hex-numbered directory and 
restore my own loader.conf. I spent days wrestling with this.

It's clear that I just don't understand UEFI booting. It sounds simple enough, 
but it clearly isn't. I've read everything I could find on the subject, to no 
avail.

-- 
Regards,
Peter.





  reply	other threads:[~2021-05-24 14:01 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-21 14:42 [gentoo-user] Dual booting with Windows 10 peter
2021-05-21 19:06 ` Michael
2021-05-24 13:11   ` Peter Humphrey [this message]
2021-05-24 15:14     ` Michael
2021-05-25 15:23       ` Peter Humphrey
2021-05-25 16:43         ` antlists
2021-05-25 19:02           ` Peter Humphrey
2021-05-26  4:02             ` Wols Lists
2021-05-27 15:02             ` Sid Spry
2021-05-26 13:49         ` Michael
2021-05-27  8:22           ` Peter Humphrey
2021-05-27 11:01             ` Michael
2021-05-27 11:38               ` Peter Humphrey
  -- strict thread matches above, loose matches on Subject: below --
2017-09-13 22:12 Peter Humphrey
2017-09-14  4:09 ` R0b0t1
2017-09-14  4:36   ` Sam Jorna
2017-09-14  4:43     ` R0b0t1
2017-09-14  5:01       ` Sam Jorna
2017-09-14  8:20   ` Peter Humphrey
2017-09-14 18:51     ` R0b0t1
2017-09-17 14:12       ` Peter Humphrey
2017-09-18  4:17         ` R0b0t1
2017-09-18  7:53           ` Peter Humphrey
2017-09-18 10:52             ` Mick
2017-09-18 11:09               ` Peter Humphrey
2017-09-18 11:17                 ` Mick
2017-09-18 13:06                   ` Peter Humphrey
2017-09-19  4:15             ` R0b0t1
2017-09-19 11:07               ` Peter Humphrey
2017-09-15  1:16 ` Taiidan
2017-09-15  4:04   ` R0b0t1
2017-09-15  9:03     ` Radoje Stojisic
2017-09-16  3:25       ` R0b0t1
2017-09-16  8:46       ` Taiidan

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=2588375.mvXUDI8C0e@wstn \
    --to=peter@prh.myzen.co.uk \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox