Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #265514
| From | Joel Roth <joelz@pobox.com> |
|---|---|
| Newsgroups | linux.debian.user |
| Subject | Re: Replace Grub with rEFInd [WAS Possibly broken Grub or initrd after updates on Testing] |
| Date | 2024-01-04 19:00 +0100 |
| Message-ID | <HSAaC-Nez-7@gated-at.bofh.it> (permalink) |
| References | (5 earlier) <HRxot-7Cz-5@gated-at.bofh.it> <HSf69-z8U-5@gated-at.bofh.it> <HSrqG-GHK-17@gated-at.bofh.it> <HStC9-HX1-11@gated-at.bofh.it> <HSzxT-N23-9@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
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
Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll 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