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

Groups > linux.debian.user > #265492

Re: Possibly broken Grub or initrd after updates on Testing

Show all headers | View raw

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

I have kept the referral to the old problem in the topic for a reason. Been
there, done that. I'm not entirely sure how, but boot-repair was the only
thing that was able to fix Grub. Before that I've reinstalled it countless
times, thanks.

But since this is very much not an answer to the question at hand, but to
the original question - and as such an entirely different topic - I'm
rewriting this to the old topic too.

On Thu, Jan 4, 2024, 02:12 Jeffrey Walton <noloader@gmail.com> wrote:

> On Wed, Jan 3, 2024 at 2:24 PM Richard Rosner <richard@rosner-online.de>
> wrote:
> >
> > So, since for whatever reason Grub seems to be broken beyond repair,
>
> I seriously doubt this is the case. I'm guessing the problem lies
> elsewhere.
>
> > 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?
>
> The rEFInd website is at <https://www.rodsbooks.com/refind/>. I'm
> guessing you have not taken time to read about it based on your
> questions.
>
> Jeff
>
>

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