You are not logged in.
During a system upgrade yesterday my filesystem package was upgraded to version 2016.11-3. Today another system upgrade included btrfs-progs, which triggered mkinitcpio to run. The output was:
==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'default'
-> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
==> Starting build: 4.8.10-1-ARCH
-> Running build hook: [base]
==> ERROR: file not found: `/usr/lib/modprobe.d/usb-load-ehci-first.conf'
-> Running build hook: [udev]
-> Running build hook: [autodetect]
-> Running build hook: [modconf]
-> Running build hook: [block]
-> Running build hook: [filesystems]
-> Running build hook: [keyboard]
-> Running build hook: [fsck]
==> Generating module dependencies
==> Creating gzip-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'
-> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-fallback.
==> Starting build: 4.8.10-1-ARCH
-> Running build hook: [base]
==> ERROR: file not found: `/usr/lib/modprobe.d/usb-load-ehci-first.conf'
-> Running build hook: [udev]
-> Running build hook: [modconf]
-> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: wd719x
==> WARNING: Possibly missing firmware for module: aic94xx
-> Running build hook: [filesystems]
-> Running build hook: [keyboard]
-> Running build hook: [fsck]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: /boot/initramfs-linux-fallback.img
==> WARNING: errors were encountered during the build. The image may not be complete.This line had me worried:
==> ERROR: file not found: `/usr/lib/modprobe.d/usb-load-ehci-first.conf'The file in question is referenced in /usr/lib/initcpio/install/base which is owned by mkinitcpio. I naturally enough checked what package is supposed to provide the missing file, and that is the filesystem package. However, the filesystem package in testing does not provide this file.
The system boots up without issues, and my journal does not complain about anything either so I can't see any problems caused by this. I am just not sure if this change is intended or not. Should I file a bugreport to the filesystem package about the missing file?
Last edited by Daerandin (2016-11-27 13:12:35)
Offline
Offline
I didn't see that, I suppose I should conduct better searches before posting. I'll mark this as solved based on that bug report.
Offline