Wireless bluetooth input devices not usable for LUKS password screen
Hi all, in short, neither wireless keyboard nor mice over bluetooth are working for me when trying to use them to input my password on the encryption login screen. Once wired, it works fine; once past the encryption login, wireless works fine again. It seems to be because bluetooth services are not being started until after the unlocking.
Is there a way to make it so they would work prior? I can connect my KB via cable each time to enter the password, although it's fairly annoying, but I don't currently have wired mice alternatives in case that fails. I can't seem to remember if this problem has always been there since I installed Bazzite or not, as for a while I did not notice it (but I was having issues with my kb's battery so it was often connected during boot anyhow... so who knows)
This does not seem to be Bazzite-specific as during my research I saw some mentions of using dracut or doing some changes to initramfs to try to address this, but those were largely for Ubuntu, and I'm not knowledgeable enough to parse the proper way to proceed here. Thanks in advance for any insights!
2 Replies
seems editing initramfs is the way to go, but I'm as of yet unsure what to add for my non-surface devices
ref https://github.com/linux-surface/linux-surface/wiki/Disk-Encryption
GitHub
Disk Encryption
Linux Kernel for Surface Devices. Contribute to linux-surface/linux-surface development by creating an account on GitHub.
This is not possible in any way that is supported. BT drivers are not loaded at the LUKS decrypt stage
you can't edit initramfs directly, that will be overwritten on your next update
That said, there seems to be a way to make it work:
https://www.reddit.com/r/Fedora/comments/1mn98ks/howto_fedora_silverblue_enable_bluetooth/
This means enabling initramfs generation on rpm-ostree (this is not officially supported)
leave out the fido2
--arg=--add \
--arg=fido2 \ stuff
i can't guarantee nor support doing this, but it might work
it will make updates very slow because of initramfs generation each and every update
and no guarantees this won't brick your entire install