Re: WARNING: potential breakage of the initramfs-brltty feature

Samuel Thibault (2026/03/06 01:11 +0100):
> Samuel Thibault, le ven. 06 mars 2026 00:49:58 +0100, a ecrit:
> > Samuel Thibault, le ven. 06 mars 2026 00:20:39 +0100, a ecrit:
> > > Samuel Thibault, le jeu. 05 mars 2026 23:54:17 +0100, a ecrit:
> > > > 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
> > >
> > > I actually meant from stable to unstable.
> > >
> > > Even just installing brltty 6.9 from unstable or testing and leaving the
> > > rest from stable brings the issue that we had seen with Sébastien:
> > >
> > > mount: mounting /dev on /root/dev failed: Invalid argument
> > > mount: mounting /dev on /root/dev failed: Invalid argument
> > > mount: mounting /run on /root/run failed: Invalid argument
> > > mount: mounting /sys on /root/sys failed: Invalid argument
> > > mount: mounting /proc on /root/proc failed: Invalid argument
> > > run-init: error moving root: Invalid argument
> > >
> > > Perhaps we should force-disable initramfs integration in the brltty
> > > debian package for now?
> >
> > Unsurprisingly, the trixie-backports version has the same issue.
>
> The upstream change
>
> "Missing special devices are now created within an isolated file
> system."
>
> looked related, I tried reverting the corresponding upstream commit
> f16d75072983aff137bed84524c49eac271e089d "Create special devices within
> a private area.", it seems to fix the issue in my tests, I'm uploading a
> version 6.9-3 with it.

Thank you so much, Samuel!!

Seb.