Arch Linux

Kefedric

Member

Registered: 2023-04-01

Posts: 6

[SOLVED] No more USB on boot after update. (autodetect hook issue?)

Hi,

I've setup an arch machine since 6month, was working flawlessly.

I have a full drive encryption with a Yubikey using ykfde hook.

Yesterday I did my weekly arch update.
This morning I boot up and no keyboard input on prompt. (for disk decryption)

It looks like no usb device is recognize at all.

Everything work well in BIOS. (keyboard and all)
Until bootloader everything seems ok.

I can decrypt my disk with a usb live install, so the decrypt part work well it is realy usb that seems to not be recognize this early in the boot process

My boot loader is systemd-boot.

After some digging in /var/log/pacman.log

I came across

[2023-03-31T18:43:15+0000] [ALPM-SCRIPTLET] ==> Building image from preset: /etc/mkinitcpio.d/linux-zen.preset: 'default'
[2023-03-31T18:43:15+0000] [ALPM-SCRIPTLET] -> -k /boot/vmlinuz-linux-zen -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-zen.img --microcode /boot/amd-ucode.img
[2023-03-31T18:43:15+0000] [ALPM-SCRIPTLET] ==> Starting build: '6.2.8-zen1-1-zen'
[2023-03-31T18:43:15+0000] [ALPM-SCRIPTLET] -> Running build hook: [base]
[2023-03-31T18:43:15+0000] [ALPM-SCRIPTLET] -> Running build hook: [udev]
[2023-03-31T18:43:15+0000] [ALPM-SCRIPTLET] -> Running build hook: [autodetect]
[2023-03-31T18:43:15+0000] [ALPM-SCRIPTLET] sort: impossible de lire: '/sys/devices/pci0000:00/0000:00:08.1/0000:08:00.3/usb2/2-2/2-2.2/2-2.2:1.2/ep_02/uevent': Aucun fichier ou dossier de ce type
[2023-03-31T18:43:15+0000] [ALPM-SCRIPTLET] modprobe: ERROR: missing parameters. See -h.
[2023-03-31T18:43:15+0000] [ALPM-SCRIPTLET] -> Running build hook: [keyboard]
[2023-03-31T18:43:15+0000] [ALPM-SCRIPTLET] -> Running build hook: [keymap]
[2023-03-31T18:43:15+0000] [ALPM-SCRIPTLET] -> Running build hook: [modconf]
[2023-03-31T18:43:15+0000] [ALPM-SCRIPTLET] -> Running build hook: [block]
[2023-03-31T18:43:16+0000] [ALPM-SCRIPTLET] -> Running build hook: [ykfde]
[2023-03-31T18:43:16+0000] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: 'qat_4xxx'
[2023-03-31T18:43:16+0000] [ALPM-SCRIPTLET] -> Running build hook: [encrypt]

It Looks like some errors occurred in the [autodetect] hook build.
I translate the error:

impossible to read /sys/devices/pci0000:00/0000:00:08.1/0000:08:00.3/usb2/2-2/2-2.2/2-2.2:1.2/ep_02/uevent no file or folder of this type. 

May this hook be involved for usb working or not at boot ?

Why did it fail, and How to fix this ?

Last edited by Kefedric (2023-04-06 11:17:50)

Kefedric

Member

Registered: 2023-04-01

Posts: 6

Re: [SOLVED] No more USB on boot after update. (autodetect hook issue?)

As I though, It has something to do with mkintcpio because I loaded the system with the initramfs-linux-zen-fallback.img and everything work perfectly.

How can  i troubleshoot this further ?

progandy

Member

Registered: 2012-05-17

Posts: 5,280

Re: [SOLVED] No more USB on boot after update. (autodetect hook issue?)

I suggest you order the keyboard hook before the autodetect one to make sure the autodetection does not remove any keyboard related kernel modules. That may solve your problem, but doesn't tell you why the autodetect hook does not recognize your keyboard anymore if that is the problem..

Last edited by progandy (2023-04-01 19:22:42)

---

| alias CUTF='LANG=en_XX.UTF-8@POSIX ' |

ppascher

Member

Registered: 2019-05-27

Posts: 6

Re: [SOLVED] No more USB on boot after update. (autodetect hook issue?)

Edit: Just ran "mkinitcpio -P" again and my issue is fixed.

Just ran into the same or similar issue. On boot my nvme disks were not found for decryption ( /dev/by-uuid) and my usb keyboard did not work when dropped to root prompt. Disks are detected in UEFI though and keyboard works fine there as well.
Booting from fallback-initramfs and everything works fine.
Last mkinitcpio update also shows in /var/log/pacman.log:

[2023-04-04T10:53:57+0200] [ALPM-SCRIPTLET] sort: cannot read: '/sys/devices/pci0000:00/0000:00:01.2/0000:02:00.0/0000:03:08.0/0000:07:00.1/usb4/4-1/4-1:1.1/ep_81/uevent': No such file or directory
[2023-04-04T10:53:57+0200] [ALPM-SCRIPTLET] modprobe: ERROR: missing parameters. See -h.

Packages upgraded during said update were:

[2023-04-04T10:53:55+0200] [ALPM] upgraded coreutils (9.2-2 -> 9.2-3)
[2023-04-04T10:53:55+0200] [ALPM] upgraded systemd-libs (253.2-1 -> 253.2-2)
[2023-04-04T10:53:56+0200] [ALPM] upgraded systemd (253.2-1 -> 253.2-2)
[2023-04-04T10:53:56+0200] [ALPM] upgraded systemd-sysvcompat (253.2-1 -> 253.2-2)

mkinitcpio hooks:

HOOKS=(consolefont base udev autodetect modconf block keyboard keymap netconf numlock tinyssh encryptssh2 encryptssh filesystems)

Last edited by ppascher (2023-04-04 15:20:18)

Kefedric

Member

Registered: 2023-04-01

Posts: 6

Re: [SOLVED] No more USB on boot after update. (autodetect hook issue?)

Indeed

mkinitcpio -P

fix the issue. (after booting from your fallback-initramfs)

I've opened an issue on mkinitcpio and it kinda look like a known issue.

https://gitlab.archlinux.org/archlinux/ … issues/177

realth000

Member

Registered: 2023-06-23

Posts: 1

Re: [SOLVED] No more USB on boot after update. (autodetect hook issue?)

(I don't know if is appropriate to reply this post after two months)

This error also occurred on my machine.
After

pacman -Syyu

and reboot, systemd failed to mount root disk during boot.
Keyboard also became unusable after select the initrd in grub.

Kernel version:

uname -a
Linux tc130 6.3.9-arch1-1 #1 SMP PREEMPT_DYNAMIC Wed, 21 Jun 2023 20:46:20 +0000 x86_64 GNU/Linux

Systemd is newer than the version "should fixed this issue" said in gitlab link above.

pacman -Qs systemd
local/lib32-systemd 253.5-1
    system and service manager (32-bit)
local/systemd 253.5-2
    system and service manager
local/systemd-libs 253.5-2
    systemd client libraries
local/systemd-sysvcompat 253.5-2
    sysvinit compat for systemd
local/zram-generator 1.1.2-1
    Systemd unit generator for zram devices

By booting from iso, chroot and

mkinitcpio -p linux

can generate a initrd without this issue.

I backed up a initrd image when the error first happened, but today this error lived in both initrd and that backup image, that's weird.

Any way to prevent this error? It is annoying if every time rebuilding initrd may cause a fail to boot.

Maybe the initrd regenerated from the boot disk environment may not be able to enter the system in the future.