Arch Linux

山猿

Member

Registered: 2023-07-27

Posts: 44

[RESOLVED] File structure to allow mkinitcpio hooks to function?

Hello,

I am attempting to get a runtime hook (mkinitcpio-bluetooth) to work so that I can use my bluetooth keyboard in the GRUB menu.

I have followed the instructions on the github page linked above, and after running makepkg, moved the folder in its entirety to /etc/initcpio/hooks, as per the guidance here. If it is useful, my mkinitcpio.conf file looks like this;

MODULES=()
BINARIES=()
FILES=()
HOOKS=(base udev autodetect keyboard keymap bluetooth consolefont modconf block filesystems fsck)

I have also moved the individual files from within the folder pkg (bluetooth (the install script), bluetooth (the hook file), and org.bluez.conf) into /etc/initcpio/hooks and also tried moving the individual files as follows;

/etc/initcpio/
|
|
↳ /hooks
|   ↳ bluetooth (hook file)
|     org.bluez.conf
|
|
↳ /install
    ↳ bluetooth (install file)

But running the command;

mkinitcpio -P

yields the following log;

==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'default'
==> Using default configuration file: '/etc/mkinitcpio.conf'
  -> -k /boot/vmlinuz-linux -g /boot/initramfs-linux.img --microcode /boot/amd-ucode.img
==> Starting build: '6.7.1-arch1-1'
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [autodetect]
  -> Running build hook: [keyboard]
==> WARNING: Possibly missing firmware for module: 'xhci_pci'
  -> Running build hook: [keymap]
==> ERROR: Hook 'bluetooth' cannot be found
  -> Running build hook: [consolefont]
  -> Running build hook: [modconf]
  -> Running build hook: [block]
  -> Running build hook: [filesystems]
  -> Running build hook: [fsck]
==> Generating module dependencies
==> Creating zstd-compressed initcpio image: '/boot/initramfs-linux.img'
==> WARNING: errors were encountered during the build. The image may not be complete.
==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'fallback'
==> Using default configuration file: '/etc/mkinitcpio.conf'
  -> -k /boot/vmlinuz-linux -g /boot/initramfs-linux-fallback.img -S autodetect --microcode /boot/amd-ucode.img
==> Starting build: '6.7.1-arch1-1'
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [keyboard]
==> WARNING: Possibly missing firmware for module: 'xhci_pci'
  -> Running build hook: [keymap]
==> ERROR: Hook 'bluetooth' cannot be found
  -> Running build hook: [consolefont]
  -> Running build hook: [modconf]
  -> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: 'qed'
==> WARNING: Possibly missing firmware for module: 'wd719x'
==> WARNING: Possibly missing firmware for module: 'aic94xx'
==> WARNING: Possibly missing firmware for module: 'qla2xxx'
==> WARNING: Possibly missing firmware for module: 'qla1280'
==> WARNING: Possibly missing firmware for module: 'bfa'
  -> Running build hook: [filesystems]
  -> Running build hook: [fsck]
==> Generating module dependencies
==> Creating zstd-compressed initcpio image: '/boot/initramfs-linux-fallback.img'
==> WARNING: errors were encountered during the build. The image may not be complete.

Essentially, what I am trying to understand is the following;

1. Where should I place the hook, install file, and bluez conf file for mkinitcpio -P to function successfully
2. Would such a hook permit, assuming it works, the bluetooth keyboard to be utilised in the GRUB menu?

Thank you.

Last edited by 山猿 (2024-01-26 23:55:23)

Scimmia

Fellow

Registered: 2012-09-01

Posts: 13,694

Re: [RESOLVED] File structure to allow mkinitcpio hooks to function?

You build then install the package, you missed that second part. The steps are going to be the same as installing from the AUR, just acquiring different build files, or you can do it from the AUR as well. https://wiki.archlinux.org/title/Arch_U … g_packages

山猿

Member

Registered: 2023-07-27

Posts: 44

Re: [RESOLVED] File structure to allow mkinitcpio hooks to function?

You build then install the package, you missed that second part. The steps are going to be the same as installing from the AUR, just acquiring different build files, or you can do it from the AUR as well. https://wiki.archlinux.org/title/Arch_U … g_packages

Sorry, my mistake on that. I was not aware of this; thank you very much for the link. The issue is now resolved.