Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #265449

Replace Grub with rEFInd [WAS Possibly broken Grub or initrd after updates on Testing]

Show all headers | View raw

[Multipart message — attachments visible in raw view] - view raw

So, since for whatever reason Grub seems to be broken beyond repair, I 
today tried to just replace it with rEFInd. Installation succeeded 
without any trouble. But when I start my system, rEFInd just asks me if 
I want to boot with fwupd or with the still very broken Grub. Am I 
missing something? Is rEFInd really just something to select between 
different OSs (and not just different distributions like Grub can very 
well do) and then gives the rest over to their bootloaders or am I 
missing something so rEFInd will take over all of Grubs jobs?

On 01.01.24 21:45, Richard Rosner wrote:
>
>
> On 01.01.24 21:20, Richard Rosner wrote:
>>
>> On 01.01.24 20:30, David Wright wrote:
>>> On Mon 01 Jan 2024 at 19:04:20 (+0100), Richard Rosner wrote:
>>>> On 01.01.24 18:13, David Wright wrote:
>>>> I can boot by hand, but since this is all archived anyways and it's
>>>> uneccessarily difficult to find some sort of guide how to even do
>>>> this, it might as well be a documentation for users having such
>>>> troubles in the future.
>>>>
>>>> Also, besides the way that I have no clue how it would have to look
>>>> like to set up a paragraph in the grub.cfg, I simply don't see
>>>> anything wrong with it anyways. So I can't even look at the grub
>>>> settings files grub.cfg is being generated from to check where the
>>>> error lies.
>>> You append the commands that you used to boot manually with into
>>> /etc/grub.d/40_custom, observing the comments there, and also into
>>> grub.cfg itself at the appropriate place (near the bottom). The
>>> former is so that Grub includes it in any new grub.cfg that you
>>> create.
>> Good to know.
> Edit:, never mind. Tried that, it still booted straight to the UEFI 
> BIOS menu after entering my password. At this point, I'm seriously 
> considering slapping rEFInd on it and pray that it picks up on 
> everything automatically and fix the situation. But so should Grub 
> have, besides the fact that I can't even be entirely sure Grub is to 
> blame and not something else.

Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

Re: Possibly broken Grub or initrd after updates on Testing Richard Rosner <richard@rosner-online.de> - 2024-01-01 11:50 +0100
  Re: Possibly broken Grub or initrd after updates on Testing Michael Kjörling <2695bd53d63c@ewoof.net> - 2024-01-01 12:00 +0100
    Re: Possibly broken Grub or initrd after updates on Testing Richard Rosner <richard@rosner-online.de> - 2024-01-01 13:00 +0100
      Re: Possibly broken Grub or initrd after updates on Testing Richard Rosner <richard@rosner-online.de> - 2024-01-01 17:40 +0100
        Re: Possibly broken Grub or initrd after updates on Testing David Wright <deblis@lionunicorn.co.uk> - 2024-01-01 17:50 +0100
          Re: Possibly broken Grub or initrd after updates on Testing Richard Rosner <richard@rosner-online.de> - 2024-01-01 18:00 +0100
            Re: Possibly broken Grub or initrd after updates on Testing David Wright <deblis@lionunicorn.co.uk> - 2024-01-01 18:20 +0100
              Re: Possibly broken Grub or initrd after updates on Testing Richard Rosner <richard@rosner-online.de> - 2024-01-01 19:10 +0100
                Re: Possibly broken Grub or initrd after updates on Testing David Wright <deblis@lionunicorn.co.uk> - 2024-01-01 20:40 +0100
                Re: Possibly broken Grub or initrd after updates on Testing Richard Rosner <richard@rosner-online.de> - 2024-01-01 21:30 +0100
                Re: Possibly broken Grub or initrd after updates on Testing Richard Rosner <richard@rosner-online.de> - 2024-01-01 21:50 +0100
                Replace Grub with rEFInd [WAS Possibly broken Grub or initrd after  updates on Testing] Richard Rosner <richard@rosner-online.de> - 2024-01-03 20:30 +0100
                Re: Replace Grub with rEFInd [WAS Possibly broken Grub or initrd  after updates on Testing] Eddie <eddie.seymour@gmail.com> - 2024-01-03 21:10 +0100
                Re: Possibly broken Grub or initrd after updates on Testing Richard Rosner <richard@rosner-online.de> - 2024-01-03 22:10 +0100
                Re: Possibly broken Grub or initrd after updates on Testing David Wright <deblis@lionunicorn.co.uk> - 2024-01-04 19:10 +0100
                Re: Possibly broken Grub or initrd after updates on Testing Richard Rosner <richard@rosner-online.de> - 2024-01-04 20:00 +0100
                Re: Possibly broken Grub or initrd after updates on Testing David Wright <deblis@lionunicorn.co.uk> - 2024-01-07 18:10 +0100
                Re: Possibly broken Grub or initrd after updates on Testing Richard Rosner <richard@rosner-online.de> - 2024-01-07 19:00 +0100
                Re: Possibly broken Grub or initrd after updates on Testing Richard Rosner <richard@rosner-online.de> - 2024-01-07 19:00 +0100
                Re: Replace Grub with rEFInd [WAS Possibly broken Grub or initrd  after updates on Testing] Jeffrey Walton <noloader@gmail.com> - 2024-01-04 02:20 +0100
                Re: Replace Grub with rEFInd [WAS Possibly broken Grub or initrd  after updates on Testing] Richard Rosner <richard@rosner-online.de> - 2024-01-04 08:50 +0100
                Re: Replace Grub with rEFInd [WAS Possibly broken Grub or initrd  after updates on Testing] Pocket <pocket@columbus.rr.com> - 2024-01-04 12:00 +0100
                Re: Replace Grub with rEFInd [WAS Possibly broken Grub or initrd  after updates on Testing] Jeffrey Walton <noloader@gmail.com> - 2024-01-04 12:00 +0100
                Re: Replace Grub with rEFInd [WAS Possibly broken Grub or initrd after updates on Testing] Richard Rosner <richard@rosner-online.de> - 2024-01-04 13:10 +0100
                Re: Possibly broken Grub or initrd after updates on Testing Richard Rosner <richard@rosner-online.de> - 2024-01-04 08:50 +0100
                Re: Replace Grub with rEFInd [WAS Possibly broken Grub or initrd  after updates on Testing] Timothy M Butterworth <timothy.m.butterworth@gmail.com> - 2024-01-04 08:20 +0100
                Re: Replace Grub with rEFInd [WAS Possibly broken Grub or initrd  after updates on Testing] Joel Roth <joelz@pobox.com> - 2024-01-04 09:40 +0100
                Re: Replace Grub with rEFInd [WAS Possibly broken Grub or initrd  after updates on Testing] Richard Rosner <richard@rosner-online.de> - 2024-01-04 12:00 +0100
                Re: Replace Grub with rEFInd [WAS Possibly broken Grub or initrd  after updates on Testing] Richard Rosner <richard@rosner-online.de> - 2024-01-04 18:20 +0100
                Re: Replace Grub with rEFInd [WAS Possibly broken Grub or initrd  after updates on Testing] Joel Roth <joelz@pobox.com> - 2024-01-04 19:00 +0100
                Re: Replace Grub with rEFInd [WAS Possibly broken Grub or initrd  after updates on Testing] Jeffrey Walton <noloader@gmail.com> - 2024-01-05 00:40 +0100
                Re: Replace Grub with rEFInd [WAS Possibly broken Grub or initrd  after updates on Testing] songbird <songbird@anthive.com> - 2024-01-07 20:50 +0100
                Re: Replace Grub with rEFInd [WAS Possibly broken Grub or initrd  after updates on Testing] Richard Rosner <richard@rosner-online.de> - 2024-01-07 21:00 +0100

csiph-web