Sometimes the hook stops on the keymap step and I have to stop the install with Ctrl + C. This does not happen always but just sometimes. Can I somehow provide more information about this?
(1/1) checking keys in keyring [---------------------------------------------------] 100%
(1/1) checking package integrity [---------------------------------------------------] 100%
(1/1) loading package files [---------------------------------------------------] 100%
(1/1) checking for file conflicts [---------------------------------------------------] 100%
(1/1) checking available disk space [---------------------------------------------------] 100%
:: Running pre-transaction hooks...
(1/1) Saving Linux kernel modules...
:: Processing package changes...
(1/1) reinstalling linux [---------------------------------------------------] 100%
:: Running post-transaction hooks...
(1/6) Restoring Linux kernel modules...
++ uname -r
+ KVER=6.5.6-arch2-1
+ test -e /usr/lib/modules/backup/6.5.6-arch2-1
+ rsync -AHXal --ignore-existing /usr/lib/modules/backup/6.5.6-arch2-1 /usr/lib/modules/
+ rm -rf /usr/lib/modules/backup
(2/6) Arming ConditionNeedsUpdate...
(3/6) Updating module dependencies...
(4/6) Updating linux initcpios...
==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'default'
==> Using configuration file: '/etc/mkinitcpio.conf'
-> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
==> Starting build: '6.5.7-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]
^C
Interrupt signal received
Sometimes the hook stops on the keymap step and I have to stop the install with Ctrl + C. This does not happen always but just sometimes. Can I somehow provide more information about this?