public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Dan Egli <dan@newideatest.site>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] switching from "refine" to "grub"
Date: Sat, 12 Dec 2020 01:57:40 -0700	[thread overview]
Message-ID: <b11cae7a-1bda-6e46-8acc-ff712695a4d7@newideatest.site> (raw)
In-Reply-To: <20201212083147.6e2b1bc0@digimed.co.uk>

What complexity? I have a couple EFI machines booting via Grub, and they 
work great. I just had to ensure the correct GRUB_TARGET in make.conf 
and then after I had my partitions setup and formatted, I just did 
grub-install --target=x86_64-efi --efi-directory=/boot/EFI and it went 
smooth as silk as long as I didn't have /boot on newer ZFS setup. Even 
ZFS would work if you setup /boot to be a separate dataset and make it 
with absolute minimal options.

On 12/12/2020 1:31 AM, Neil Bothwick wrote:
> On Fri, 11 Dec 2020 07:48:06 -0700, thelma@sys-concept.com wrote:
>
>> I use refine as boot loader but it is giving me a problems.
>> How to switch back to grub 2
>> And remove any refine files from /boot
> I take it you mean refind? It may well be easier to solve the problem
> with refind rather than trying to deal with the overcomplexity of GRUB
> for an EFI system.
>
> I normally use systemd-boot but when I have used refind, it has picked up
> everything it needs to know without a config file. What errors are you
> seeing?
>
>
-- 
Dan Egli
 From my Test Server



  reply	other threads:[~2020-12-12  8:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-11 14:48 [gentoo-user] switching from "refine" to "grub" thelma
2020-12-12  7:03 ` Dan Egli
2020-12-12  8:31 ` Neil Bothwick
2020-12-12  8:57   ` Dan Egli [this message]
2020-12-12 13:39     ` Neil Bothwick

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=b11cae7a-1bda-6e46-8acc-ff712695a4d7@newideatest.site \
    --to=dan@newideatest.site \
    --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