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?
On 07.01.24 18:07, David Wright wrote:
On Sat 06 Jan 2024 at 20:04:57 (+0100), Richard Rosner wrote:
I just tried out systemd-boot. What I noticed, it doesn't ask for my
decryption password to decrypt both my LUKS2 encrypted root and swap
partition. This kinda defeats the purpose of encrypted
On 04.01.24 19:49, Richard Rosner wrote:
On 04.01.24 19:02, David Wright wrote:
Could you post the new grub.cfg file, so that people running testing,
and following along the thread later, can see how boot-repair fixed it?
Cheers,
David.
Let's hope the mailing list let's this go through
On 07.01.24 18:07, David Wright wrote:
I compared your new grub.cfg with mine (suitably decimated and edited)
and the significant differences are very few; extra modules are loaded:
cryptodisk, luks2, gcry_rijndael, gcry_rijndael and gcry_sha256.
Myset root='hd0,gpt5' is replaced by
set
I just tried out systemd-boot. What I noticed, it doesn't ask for my
decryption password to decrypt both my LUKS2 encrypted root and swap
partition. This kinda defeats the purpose of encrypted drives. How do I
have systemd-boot forget and never again remember my credentials?
For the
On 04.01.24 19:02, David Wright wrote:
Could you post the new grub.cfg file, so that people running testing,
and following along the thread later, can see how boot-repair fixed it?
Cheers,
David.
Let's hope the mailing list let's this go through.
Keep in mind, this is based on the
(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
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
partition and then try to install rEFInd. I'll have to check.
On Thu, Jan 4, 2024, 09:29 Joel Roth 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 repl
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 wrote:
> On Wed, Jan 3, 2024 at 2:24 PM Richard Rosner
> wrote:
> >
> > So, since for whatever reason Grub
other than snarky remarks,
just don't answer.
On Thu, Jan 4, 2024, 02:12 Jeffrey Walton wrote:
> 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 gue
l together.
On 03.01.24 21:04, Eddie wrote:
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
? 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
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
(also LUKS1).
For me it looks like the grub.cfg has everything it needs to work.
On 01.01.24 18:13, David Wright wrote:
On Mon 01 Jan 2024 at 17:55:29 (+0100), Richard Rosner wrote:
On January 1, 2024 5:43:12 PM GMT+01:00, David Wright
wrote:
Like this?
└─sda6
Yes, exactly. Is there a way to show that from inside Grub? Lsblk and blkid
aren't available there?
On January 1, 2024 5:43:12 PM GMT+01:00, David Wright
wrote:
>Like this?
>
> └─sda6 8:60 406.2G 0 part
>
terminal where you
can just look inside /dev/mapper and see the true path that needs to be entered.
Question is, how do I repair the boot process so I don't have to boot by hand
every time?
On January 1, 2024 12:52:40 PM GMT+01:00, Richard Rosner
wrote:
>I do not see an answer to my questions.
I do not see an answer to my questions.
> On Jan 1, 2024, at 11:52, Michael Kjörling <2695bd53d...@ewoof.net> wrote:
>
> On 1 Jan 2024 11:46 +0100, from rich...@rosner-online.de (Richard Rosner):
>> I'm not sure what you meant with "rescue mode", but I've reins
; wrote:
>
> On 1 Jan 2024 09:16 +0100, from rich...@rosner-online.de (Richard Rosner):
>> could you please check if you received either of my two tries to get
>> this answer through the mailing list?
>
> I did not. Maybe they are held for moderation due to size?
>
>
. For a fraction of a
second it shows something about slot 0 open, that's it.
> On Dec 29, 2023, at 20:37, Richard Rosner wrote:
>
> As far as I can tell, /boot and /boot/grub are the same filesystem. After
> all, I didn't really do anything custom. Just your default LUKS
Hey, I have quite the strange issue. After updating a bunch of packages today
[1], mostly related to systemd, gstreamer and udev, and restarting my device,
it no longer boots. I have an encrypted system. So I do get asked for my
decryption password as usual, but a few seconds later, instead of
22 matches
Mail list logo
