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

Groups > linux.debian.user > #265386 > unrolled thread

Re: Possibly broken Grub or initrd after updates on Testing

Back to article view | Back to linux.debian.user

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  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

Page 2 of 2 — ← Prev page 1 [2]

#265491 — Re: Replace Grub with rEFInd [WAS Possibly broken Grub or initrd after updates on Testing]

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

Wow, what a bunch of unhelpful comments.

First, if it wasn't for Eddie recommending boot-repair, "broken beyond
repair" in fact was the very fitting term.

Second, have you maybe considered that I've already read the home page of
rEFInd and came to the same conclusion? Besides the fact that the page is
virtually unreadable - both from a visual and a content point of view - I
have yet to find anything indicating what it is actually capable of and
what not. Because as far as I can tell, it should be able to do what I want
it to do.

So please, if you don't have anything to add other than snarky remarks,
just don't answer.

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
>
>

[toc] | [prev] | [next] | [standalone]

#265495 — Re: Replace Grub with rEFInd [WAS Possibly broken Grub or initrd after updates on Testing]

On 1/4/24 02:45, Richard Rosner wrote:
> Wow, what a bunch of unhelpful comments.
> 
> First, if it wasn't for Eddie recommending boot-repair, "broken beyond 
> repair" in fact was the very fitting term.
> 
> Second, have you maybe considered that I've already read the home page 
> of rEFInd and came to the same conclusion? Besides the fact that the 
> page is virtually unreadable - both from a visual and a content point of 
> view - I have yet to find anything indicating what it is actually 
> capable of and what not. Because as far as I can tell, it should be able 
> to do what I want it to do.
> 


Have you looked at this?

https://wiki.archlinux.org/title/REFInd

I don't know if it will help as I do not use REFInd nor have I any 
experience with it.

-- 
Hindi madali ang maging ako

[toc] | [prev] | [next] | [standalone]

#265499 — Re: Replace Grub with rEFInd [WAS Possibly broken Grub or initrd after updates on Testing]

On Thu, Jan 4, 2024 at 2:45 AM Richard Rosner <richard@rosner-online.de> wrote:
>
> Wow, what a bunch of unhelpful comments.
>
> First, if it wasn't for Eddie recommending boot-repair, "broken beyond repair" in fact was the very fitting term.

Here was Eddie's comment" I have had very good results using
"Boot-Repair" software to recover Grub difficulties."

"Broken beyond repair" seems to be context dependent. And it seems to
depend on the user.

> Second, have you maybe considered that I've already read the home page of rEFInd and came to the same conclusion? Besides the fact that the page is virtually unreadable - both from a visual and a content point of view - I have yet to find anything indicating what it is actually capable of and what not. Because as far as I can tell, it should be able to do what I want it to do.

No. You did not state it. And you did not cite something you did not
understand. I think you are full of shit.

> So please, if you don't have anything to add other than snarky remarks, just don't answer.

You mean like: "So, since for whatever reason Grub seems to be broken
beyond repair"?

Jeff

[toc] | [prev] | [next] | [standalone]

#265500 — Re: Replace Grub with rEFInd [WAS Possibly broken Grub or initrd after updates on Testing]

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

You should really re-read the FAQ that was sent in just two days ago...

On January 4, 2024 11:58:28 AM GMT+01:00, Jeffrey Walton <noloader@gmail.com> wrote:
>On Thu, Jan 4, 2024 at 2:45 AM Richard Rosner <richard@rosner-online.de> wrote:
>>
>> Wow, what a bunch of unhelpful comments.
>>
>> First, if it wasn't for Eddie recommending boot-repair, "broken beyond repair" in fact was the very fitting term.
>
>Here was Eddie's comment" I have had very good results using
>"Boot-Repair" software to recover Grub difficulties."
>
>"Broken beyond repair" seems to be context dependent. And it seems to
>depend on the user.
>
>> Second, have you maybe considered that I've already read the home page of rEFInd and came to the same conclusion? Besides the fact that the page is virtually unreadable - both from a visual and a content point of view - I have yet to find anything indicating what it is actually capable of and what not. Because as far as I can tell, it should be able to do what I want it to do.
>
>No. You did not state it. And you did not cite something you did not
>understand. I think you are full of shit.
>
>> So please, if you don't have anything to add other than snarky remarks, just don't answer.
>
>You mean like: "So, since for whatever reason Grub seems to be broken
>beyond repair"?
>
>Jeff
>

[toc] | [prev] | [next] | [standalone]

#265492

[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
>
>

[toc] | [prev] | [next] | [standalone]

#265490 — Re: Replace Grub with rEFInd [WAS Possibly broken Grub or initrd after updates on Testing]

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

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 am not sure what you mean by "broken beyond repair." I have no issues
with Grub on Debian 12 on AMD64. I had no issues with Grub on Debian 11 or
Debian 10 on AMD64 either. I also had no issues upgrading from Debian 11 to
Debian 12. Is it possible that you simply have a corrupted hard drive and
simply need to reinstall from scratch?

You can download a Debian LiveCD for AMD64 from here:
https://cdimage.debian.org/debian-cd/current-live/amd64/bt-hybrid/ you can
then boot with it and mount your drive and copy your home directory to a
USB portable drive. When you reinstall I would create a separate partition
for /home. That way in the future you can always reinstall and just tell
the system to mount the existing /home partition.


> 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.
>
>

-- 
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org/
⠈⠳⣄⠀⠀

[toc] | [prev] | [next] | [standalone]

#265493 — Re: Replace Grub with rEFInd [WAS Possibly broken Grub or initrd after updates on Testing]

On Wed, Jan 03, 2024 at 08:23:29PM +0100, Richard Rosner wrote:
> 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?

I boot my debian-based system with rEFInd.  Grub is not
present. A couple big icons show on the boot screen. The
small print at the bottom mentions hit F2 for more options.
On my system, F2 offers a selection among all kernels
present. 

rEFInd installs into  EFI/refind/ in the EFI partition.
I originally encountered it looking for something to
boot debian on a Intel Mac. It's been trouble-free.




> 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.

-- 
Joel Roth

[toc] | [prev] | [next] | [standalone]

#265496 — Re: Replace Grub with rEFInd [WAS Possibly broken Grub or initrd after updates on Testing]

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

Good to know that it should be possible. But as mentioned, these symbols
only offer me to boot from grub or fwupd. F2 also doesn't show that much
more, it merely gives me the option to boot into the BIOS settings. Maybe
I'll have to completely purge all Grub packages, wipe the existing EFI
partition and then try to install rEFInd. I'll have to check.

On Thu, Jan 4, 2024, 09:29 Joel Roth <joelz@pobox.com> wrote:

> On Wed, Jan 03, 2024 at 08:23:29PM +0100, Richard Rosner wrote:
> > 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?
>
> I boot my debian-based system with rEFInd.  Grub is not
> present. A couple big icons show on the boot screen. The
> small print at the bottom mentions hit F2 for more options.
> On my system, F2 offers a selection among all kernels
> present.
>
> rEFInd installs into  EFI/refind/ in the EFI partition.
> I originally encountered it looking for something to
> boot debian on a Intel Mac. It's been trouble-free.
>
>
>
>
> > 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.
>
> --
> Joel Roth
>
>

[toc] | [prev] | [next] | [standalone]

#265513 — Re: Replace Grub with rEFInd [WAS Possibly broken Grub or initrd after updates on Testing]

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

Well, that was a bust. I accidentally didn't just format the EFI 
partition, but deleted it. So I re-created it with the help of disks and 
gparted (to leave the first 3 MB empty, I remeber that being a fix added 
kinda recently to combat bad BIOS/EFI implementations, since Windows is 
doing the same and nobody could come up with anything better.

Anyways, after installing rEFInd with no grub present, it would boot 
into rEFInd, but that's it. No boot options, nothing under F2. Also, I 
couldn't find anything helpful on the Arch Wiki page for this. In 
theory, it should be as simple as refind-install. So the only reason I 
could guess to be the reason would be that rEFInd might not be capable 
of handling LUKS, which would be quite disappointing. Maybe I'll take a 
look at systemd-boot in the next days, as I don't need any customization 
anyways, and maybe it can handle encryption (or better decryption) 
better than Grub — especially with LUKS2 grub seems a bit unreasonably slow.

On 04.01.24 11:56, Richard Rosner wrote:
> Good to know that it should be possible. But as mentioned, these 
> symbols only offer me to boot from grub or fwupd. F2 also doesn't show 
> that much more, it merely gives me the option to boot into the BIOS 
> settings. Maybe I'll have to completely purge all Grub packages, wipe 
> the existing EFI partition and then try to install rEFInd. I'll have 
> to check.
>
> On Thu, Jan 4, 2024, 09:29 Joel Roth <joelz@pobox.com> wrote:
>
>     On Wed, Jan 03, 2024 at 08:23:29PM +0100, Richard Rosner wrote:
>     > 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?
>
>     I boot my debian-based system with rEFInd.  Grub is not
>     present. A couple big icons show on the boot screen. The
>     small print at the bottom mentions hit F2 for more options.
>     On my system, F2 offers a selection among all kernels
>     present.
>
>     rEFInd installs into  EFI/refind/ in the EFI partition.
>     I originally encountered it looking for something to
>     boot debian on a Intel Mac. It's been trouble-free.
>
>
>
>
>     > 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.
>
>     -- 
>     Joel Roth
>

[toc] | [prev] | [next] | [standalone]

#265514 — Re: Replace Grub with rEFInd [WAS Possibly broken Grub or initrd after updates on Testing]

On Thu, Jan 04, 2024 at 06:19:01PM +0100, Richard Rosner wrote:
> In theory, it should
> be as simple as refind-install. So the only reason I could guess to be the
> reason would be that rEFInd might not be capable of handling LUKS, which
> would be quite disappointing. 

My experiences are with vanilla filesystems only. LUKS
obviously has specific requirements. Perhaps you could try
having a root partition that is unencrypted?

-- 
Joel Roth

[toc] | [prev] | [next] | [standalone]

#265519 — Re: Replace Grub with rEFInd [WAS Possibly broken Grub or initrd after updates on Testing]

On Thu, Jan 4, 2024 at 6:18 PM Joel Roth <joelz@pobox.com> wrote:
>
> On Thu, Jan 04, 2024 at 06:19:01PM +0100, Richard Rosner wrote:
> > In theory, it should
> > be as simple as refind-install. So the only reason I could guess to be the
> > reason would be that rEFInd might not be capable of handling LUKS, which
> > would be quite disappointing.
>
> My experiences are with vanilla filesystems only. LUKS
> obviously has specific requirements. Perhaps you could try
> having a root partition that is unencrypted?

Be careful of that. Someone who is encrypting the filesystem likely
has password protected the firmware, disabled booting from USB sticks,
and disabled the root account so a rescue console cannot be used to
sidestep access restrictions. That is, you don't want to hand out a
passwordless root shell in rescue mode. Also see
<https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=802211>.

Jeff

[toc] | [prev] | [next] | [standalone]

#265624 — Re: Replace Grub with rEFInd [WAS Possibly broken Grub or initrd after updates on Testing]

Richard Rosner wrote:
> 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?

...

  i don't do encryption or raid so i keep things pretty
simple.

  i've been using refind for years without issues.  i also
have grub installed so if either of them breaks the other
is still likely going to work.

  i've also set it up so that each can be reached from the
other through their menus.

  i see you've solved your issue, but i just wanted to 
point out that it works and is ok for people who want to
try it out.


  songbird

[toc] | [prev] | [next] | [standalone]

#265625 — Re: Replace Grub with rEFInd [WAS Possibly broken Grub or initrd after updates on Testing]

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

On 07.01.24 20:33, songbird wrote:
> i see you've solved your issue, but i just wanted to
> point out that it works and is ok for people who want to
> try it out.
Says who?

[toc] | [prev] | [standalone]

Page 2 of 2 — ← Prev page 1 [2]

Back to top | Article view | linux.debian.user

csiph-web