Arch Linux

jokerttt

Member

Registered: 2020-03-29

Posts: 11

Enabling Bluetooth during boot

Hello,

I encrypted my /home directory with dm-crypt and now there is a password request at boot. My Logitech K380 Bluetooth keyboard doesn't connect until Xfce is loaded. Google search comes up with this AUR and this link to GitHub link . I followed all steps described but still can't get my Bluetooth module up during boot.

I am running MSI Z390 GAMING EDGE AC with Intel Corp. Bluetooth 9460/9560 Jefferson Peak (JfP) on board.

lsusb output:

Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 248a:8514 Maxxter Wireless Receiver
Bus 001 Device 003: ID 1462:1720 Micro Star International MYSTIC LIGHT 
Bus 001 Device 011: ID 148f:7601 Ralink Technology, Corp. MT7601U Wireless Adapter
Bus 001 Device 005: ID 0bda:8812 Realtek Semiconductor Corp. RTL8812AU 802.11a/b/g/n/ac 2T2R DB WLAN Adapter
Bus 001 Device 002: ID 2109:2817 VIA Labs, Inc. USB2.0 Hub             
Bus 001 Device 010: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson Peak (JfP)
Bus 001 Device 009: ID 05e3:0608 Genesys Logic, Inc. Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

lsmod | grep btusb output:

btusb                  65536  0
btrtl                  28672  1 btusb
btbcm                  24576  1 btusb
btintel                45056  1 btusb
bluetooth             749568  33 btrtl,hidp,btintel,btbcm,bnep,btusb

sudo dmesg | grep Bluetooth output:

[    0.927027] Bluetooth: Core ver 2.22
[    0.927035] Bluetooth: HCI device and connection manager initialized
[    0.927037] Bluetooth: HCI socket layer initialized
[    0.927038] Bluetooth: L2CAP socket layer initialized
[    0.927039] Bluetooth: SCO socket layer initialized
[    0.929628] Bluetooth: HIDP (Human Interface Emulation) ver 1.2
[    0.929630] Bluetooth: HIDP socket layer initialized
[    0.932006] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[    0.932007] Bluetooth: BNEP filters: protocol multicast
[    0.932008] Bluetooth: BNEP socket layer initialized
[    3.633070] Bluetooth: hci0: Found device firmware: intel/ibt-17-16-1.sfi
[    3.633100] Bluetooth: hci0: Boot Address: 0x40800
[    3.633100] Bluetooth: hci0: Firmware Version: 207-35.21
[    3.633101] Bluetooth: hci0: Firmware already loaded

As well here my mkinitcpio.conf

# vim:set ft=sh
# MODULES
# The following modules are loaded before any boot hooks are
# run.  Advanced users may wish to specify all system modules
# in this array.  For instance:
#     MODULES=(piix ide_disk reiserfs)
MODULES=(usbhid xhci_hcd hci hidp bnep)

# BINARIES
# This setting includes any additional binaries a given user may
# wish into the CPIO image.  This is run last, so it may be used to
# override the actual binaries included by a given hook
# BINARIES are dependency parsed, so you may safely ignore libraries
BINARIES=()

# FILES
# This setting is similar to BINARIES above, however, files are added
# as-is and are not parsed in any way.  This is useful for config files.
FILES=(/usr/lib/firmware/intel/ibt-17-16-1.sfi)

# HOOKS
# This is the most important setting in this file.  The HOOKS control the
# modules and scripts added to the image, and what happens at boot time.
# Order is important, and it is recommended that you do not change the
# order in which HOOKS are added.  Run 'mkinitcpio -H <hook name>' for
# help on a given hook.
# 'base' is _required_ unless you know precisely what you are doing.
# 'udev' is _required_ in order to automatically load modules
# 'filesystems' is _required_ unless you specify your fs modules in MODULES
# Examples:
##   This setup specifies all modules in the MODULES setting above.
##   No raid, lvm2, or encrypted root is needed.
#    HOOKS=(base)
#
##   This setup will autodetect all modules for your system and should
##   work as a sane default
#    HOOKS=(base udev autodetect block filesystems)
#
##   This setup will generate a 'full' image which supports most systems.
##   No autodetection is done.
#    HOOKS=(base udev block filesystems)
#
##   This setup assembles a pata mdadm array with an encrypted root FS.
##   Note: See 'mkinitcpio -H mdadm' for more information on raid devices.
#    HOOKS=(base udev block mdadm encrypt filesystems)
#
##   This setup loads an lvm2 volume group on a usb device.
#    HOOKS=(base udev block lvm2 filesystems)
#
##   NOTE: If you have /usr on a separate partition, you MUST include the
#    usr, fsck and shutdown hooks.
HOOKS=(base udev autodetect modconf block filesystems keyboard bluetooth encrypt fsck)

# COMPRESSION
# Use this to compress the initramfs image. By default, zstd compression
# is used. Use 'cat' to create an uncompressed image.
#COMPRESSION="zstd"
#COMPRESSION="gzip"
#COMPRESSION="bzip2"
#COMPRESSION="lzma"
#COMPRESSION="xz"
#COMPRESSION="lzop"
#COMPRESSION="lz4"

# COMPRESSION_OPTIONS
# Additional options for the compressor
#COMPRESSION_OPTIONS=()

Used firmware for my Bluetooth adapter is included in the files sections. Maybe there are some modules is missing?

Tétrapyle

Member

Registered: 2014-01-03

Posts: 61

Re: Enabling Bluetooth during boot

Hey,
It’s not about HID versus HCI before the actual boot, right ?
When I used to have a Bluetooth keyboard, I had to tap on it quite early during the boot process so that it would be ready at login time. Otherwise, I would have had to wait for quite some time for it to connect.