bluetooth keyboard available for luks

[champ]

Hi all,

How can I enable my bluetooth keyboard (Logitech K380) to be able to enter the password for luks encryption?

Once it is unlocked via usb keyboard the bluetooth keyboard works fine.

I am using the Asus ROG Strix x570i which uses Intels AX200 chipset which is combined wifi and bluetooth.

Kernel - Linux 5.4.0-4-amd64 #1 SMP Debian 5.4.19-1 (2020-02-13) x86_64 GNU/Linux

I have looked and looked and am unable to find a solution :/

Any help would be appreciated.

Thanks.

Code: Select all

root /home/champ # cat /etc/initramfs-tools/modules

hid
hidp
btusb
bluetooth
#usbcore
#uhci_hcd
#ehci_hcd
#usbhid
bnep
btbcm
iwlwifi
btintel

Code: Select all

root /home/champ # dmesg | grep -i bluetooth
[    1.226763] Bluetooth: Core ver 2.22
[    1.226769] Bluetooth: HCI device and connection manager initialized
[    1.226773] Bluetooth: HCI socket layer initialized
[    1.226774] Bluetooth: L2CAP socket layer initialized
[    1.226775] Bluetooth: SCO socket layer initialized
[    1.227639] Bluetooth: HIDP (Human Interface Emulation) ver 1.2
[    1.227640] Bluetooth: HIDP socket layer initialized
[    1.240341] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[    1.240342] Bluetooth: BNEP filters: protocol multicast
[    1.240343] Bluetooth: BNEP socket layer initialized
[    1.706858] Bluetooth: hci0: Firmware revision 0.0 build 111 week 53 2019

Code: Select all

root /home/champ # hciconfig -a
hci0:	Type: Primary  Bus: USB
	BD Address: 94:E6:F7:28:39:DE  ACL MTU: 1021:4  SCO MTU: 96:6
	UP RUNNING PSCAN
	RX bytes:1448 acl:0 sco:0 events:97 errors:0
	TX bytes:2903 acl:0 sco:0 commands:97 errors:0
	Features: 0xbf 0xfe 0x0f 0xfe 0xdb 0xff 0x7b 0x87
	Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
	Link policy: RSWITCH SNIFF
	Link mode: SLAVE ACCEPT
	Name: 'theden'
	Class: 0x000104
	Service Classes: Unspecified
	Device Class: Computer, Desktop workstation
	HCI Version:  (0xa)  Revision: 0x100
	LMP Version:  (0xa)  Subversion: 0x100
	Manufacturer: Intel Corp. (2)

Might be of value

Code: Select all

root /home/champ # lsusb
Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 005 Device 002: ID 045e:0053 Microsoft Corp. Optical Mouse
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 003: ID 8087:0029 Intel Corp.
Bus 003 Device 002: ID 0b05:18f3 ASUSTek Computer, Inc. AURA LED Controller
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 1e71:2006 NZXT NZXT USB Device
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

[arzgi]

I don't think there is a keyboard that works but not in luks.

Perhaps you entered wrong password.

I have not used luks, but many Linux programs show nothing when you enter password, no asterisks on anything else, just spaces.

[CwF]

The configuration, modules, firmwares all need to be in the unencrypted boot partition which is a bad idea. This is why the 'unified' receivers work. In order to work with Luks it also needs to be alive at boot and can be used to enter the bios, which a bt kb usually cannot.

[p.H]

I don't know much about Bluetooth support in Linux, but IIUC it needs more than just loading the kernel modules. It requires userland tools and configuration which are provided by bluez, like ip or ifconfig for networking, mdadm for software RAID or cryptsetup for LUKS encryption. However the bluez package does not seem to include any support for initramfs integration.

I don't think there is a keyboard that works but not in luks.

It is not about LUKS, it is about Bluetooth support at early boot.

The configuration, modules, firmwares all need to be in the unencrypted boot partition which is a bad idea

How is that worse that already having all the bootloader, kernel image and initramfs in the unencrypted /boot, which is the default ?

it also needs to be alive at boot and can be used to enter the bios

Not if /boot is unencrypted, which is the default. Bluetooth support will be required only after the kernel is loaded.

[champ]

Thanks for the responses.

So basically what I am hearing is, its a no go unless I use usb keyboard or a unified keyboard :/