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

2024-01-07 Thread Richard Rosner
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?

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

2024-01-07 Thread songbird
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

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

2024-01-04 Thread Jeffrey Walton
On Thu, Jan 4, 2024 at 6:18 PM Joel Roth 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

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

2024-01-04 Thread Joel Roth
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

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

2024-01-04 Thread Richard Rosner
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

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

2024-01-04 Thread Richard Rosner
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 wrote: >On Thu, Jan 4, 2024 at 2:45 AM Richard Rosner wrote: >> >> Wow, what a bunch of unhelpful comments. >> >> First, if it wasn't for Eddie recommending

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

2024-01-04 Thread Jeffrey Walton
On Thu, Jan 4, 2024 at 2:45 AM 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. Here was Eddie's comment" I have had very good results using "Boot-Repair"

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

2024-01-04 Thread Richard Rosner
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

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

2024-01-04 Thread Pocket
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

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

2024-01-04 Thread Joel Roth
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 >

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

2024-01-03 Thread Richard Rosner
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

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

2024-01-03 Thread Timothy M Butterworth
On Wed, Jan 3, 2024 at 2:24 PM Richard Rosner 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

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

2024-01-03 Thread Jeffrey Walton
On Wed, Jan 3, 2024 at 2:24 PM Richard Rosner 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

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

2024-01-03 Thread Eddie
I have had very good results using "Boot-Repair" software to recover Grub difficulties. Eddie On 1/3/24 14:23, 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.

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

2024-01-03 Thread Richard Rosner
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