Samuel Thibault (2026/03/06 01:15 +0100): > Sébastien Hinderer, le ven. 06 mars 2026 01:12:41 +0100, a ecrit: > > Samuel Thibault (2026/03/05 23:54 +0100): > > > Hello, > > > > > > Sebastian Humenda, le lun. 23 févr. 2026 07:15:24 +0100, a ecrit: > > > > Sébastien Hinderer schrieb am 22.02.2026, 19:19 +0100: > > > > >As you may know, it is possible to embed BRLTTY in initramfs, which is > > > > >generally helpful to catch problems happening early during system > > > > >startup. In particular this feature is the one that lets you know when > > > > >the time has come to enter the > > > > >passphrase to decrypt your encrypted hard drive. > > > > > > > > > >I am under the impression that embedding BRLTTY in recent initramfs > > > > >file systems breaks them to the pont that the whole boot becomes > > > > >impossible, the kernel trying to realise an impossible mount. > > > > > > I have tracked it down a bit, and it seems that it's brltty 6.9 which is > > > posing the problem: upgrading all packages but brltty from testing to > > > unstable and running update-initramfs -u keeps the system bootable. > > > Upgrading to brltty 6.8-5 and updating initramfs still keeps the system > > > bootable. It's only when I upgraded to 6.9-1 that I got the issue. > > > > > > Sébastien, can that match your finding? > > > > Well as far as I can remember I just upgraded everything at once as I do > > from time to time > > Ok, so you upgraded brltty to 6.9 at the same time?
Most likely, yes. > > > so I fear it would be hard for me tosay without re-downgrading and > > doing the same tests you did. > > I didn't mean to change your installed version, just to check that this > matches upgrading to 6.9. I'm almost certain it corresponds. Seb.
