Arch Linux User Repository

Do yourself a favor and add

omit_dracutmodules+=" brltty "

to /etc/dracut.conf.d/yourconf.conf if you are not blind.

Qemu's newly added brltty dependency broke my encrypted ZFS completely and I could not boot due to dracut-pre-mount.service not completing.

Might do the same to LUKS.

my self had issues with systemd-shutdown with that i added rd.brltty=0 in kernel line and added something in cmdline but im not sure atleast shutdown time gone

@merlock Thanks, I read the conversation you linked. But as far as I can tell these files dracut complains about have pretty much always resided at /usr/share/brltty/Input/, so it's not as if something changed between 6.1 and 6.2 with the brltty package adding dracut as an optional dependency; it's just that the brltty-lsinc binary in 6.2 is now looking for these files at /etc/brltty/Input/ and is failing to find them, while in 6.1 it apparently looks for them in the correct place and silently succeeds.

So it still seems to me that either the brltty-lsinc binary has been misconfigured, or that these files had been intended to be moved from /usr to /etc during the update from 6.1 to 6.2, but for some reason the maintainer failed to do so (somewhat more doubtful as the files are read-only).

@Nocifer:

See https://lists.archlinux.org/pipermail/arch-general/2021-January/048534.html

Hello,

As of today I've been getting errors on system boot and shutdown that can be traced back to dracut and brltty. Trying to rebuild my initramfs resulted in the following:

dracut: *** Including module: brltty ***
brltty-lsinc: missing file
brltty-lsinc: cannot open file: /etc/brltty/Input/al/*.ktb: No such file or directory
brltty-lsinc: cannot open file: /etc/brltty/Input/bm/*.ktb: No such file or directory
brltty-lsinc: cannot open file: /etc/brltty/Input/bn/*.ktb: No such file or directory
brltty-lsinc: cannot open file: /etc/brltty/Input/cn/*.ktb: No such file or directory
brltty-lsinc: cannot open file: /etc/brltty/Input/eu/*.ktb: No such file or directory
brltty-lsinc: cannot open file: /etc/brltty/Input/fs/*.ktb: No such file or directory
brltty-lsinc: cannot open file: /etc/brltty/Input/hd/*.ktb: No such file or directory
brltty-lsinc: cannot open file: /etc/brltty/Input/hm/*.ktb: No such file or directory
brltty-lsinc: cannot open file: /etc/brltty/Input/ht/*.ktb: No such file or directory
brltty-lsinc: cannot open file: /etc/brltty/Input/hw/*.ktb: No such file or directory
brltty-lsinc: cannot open file: /etc/brltty/Input/ic/*.ktb: No such file or directory
brltty-lsinc: cannot open file: /etc/brltty/Input/mt/*.ktb: No such file or directory
brltty-lsinc: cannot open file: /etc/brltty/Input/pg/*.ktb: No such file or directory
brltty-lsinc: cannot open file: /etc/brltty/Input/pm/*.ktb: No such file or directory
brltty-lsinc: cannot open file: /etc/brltty/Input/sk/*.ktb: No such file or directory
brltty-lsinc: cannot open file: /etc/brltty/Input/vo/*.ktb: No such file or directory
brltty-lsinc: cannot open file: /etc/brltty/Input/md/*.ktb: No such file or directory
brltty-lsinc: cannot open file: /etc/brltty/Input/mm/*.ktb: No such file or directory

This is due to the brltty package's update to version 6.2; downgrading to 6.1 fixes the problem.

I know the dracut-hook package has absolutely nothing to do with either the problem itself or its solution, but seeing as I don't really know the nitty-gritty internals of dracut, and also that brltty's 6.2 update supposedly brings the Arch version closer to upstream, I'm not really sure what to report this as: a brltty package bug (probably not if the change was deliberate in order to sync with upstream), a dracut package bug, or a dracut upstream bug?

EDIT: Hmmm, on the other hand this brltty-lsinc binary that dracut calls is owned by the brltty package, so now I'm thinking it's probably a brltty bug after all; maybe the binary was compiled with the wrong paths, because all those files can actually be found at /usr/share/brltty/Input/ instead.

I've reported it as a brltty package bug.

The commands create images with microcode images embedded. intel-ucode and amd-ucode should be added as targets.

Please change line 33 of dracut-install to

dracut -f --hostonly --no-hostonly-cmdline "/boot/initramfs-${kernel}.img" --kver "${version}"

and line 35 to

dracut -f "/boot/initramfs-${kernel}-fallback.img" --kver "${version}"

Currently both commands create the same fallback image.

Oh, that was the hint to what I was missing. I also have kernel-modules-hook ( https://aur.archlinux.org/packages/kernel-modules-hook/ ) installed but it does a plain copy of the modules directory. I have just tested, and both versions of the modules have the pkgbase file existing, despite the error message. It seems like these two packages are not compatible, are they?

Yeah, but it looks like you have two versions 5.8.5 and 5.8.10.

Just the plain standard linux package from the core repo, nothing fancy. See the edited comment, the pkgbase actually does exist, so I do not understand the error message.