Originally filed here: https://github.com/dracutdevs/dracut/issues/1521 Description: - as soon as I pair my Bluetooth devices and regenerate the initramfs it does not boot anymore - hanging at Starting... Switch Root Setup: - LUKS encrypted system - dracut 054-12.git20210521.fc34 Expected behavior: - boot process should be successful Bluetooth devices: - lspci: 02:00.0 Network controller: Intel Corporation Wi-Fi 6 AX200 (rev 1a) - lsusb: Bus 003 Device 003: ID 8087:0029 Intel Corp. AX200 Bluetooth - Thinkpad BT keyboard with trackpoint - Logitech MX Master mouse Workaround: - as soon as I omit the bluetooth module from dracut and regenerate the initramfs the boot process succeeds Could this be related with https://bugzilla.redhat.com/show_bug.cgi?id=1963424 ?
I confirm the issue. I've attached is "lsinitrd /boot/initramfs-$(uname -r).img" results as advised by @javierm on #fedora-dev Each initramfs made with a different dracut: dracut053.log dracut054.log For now the problem is somewhat unnoticeable because dracut was pushed before the kernel updates. As long the users start to receive kernel updates they will have systems with broken boot. I've also commented on the bodhi release here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-b4fb378d55 I've also have attached Bluetooth devices. Workaround for me was to downgrade to dracut 0.53
Created attachment 1787872 [details] initramfs generated with dracut 053 This initramfs works
Created attachment 1787873 [details] initramfs generated with dracut 054 this one doesn't work
This also applies for dracut 055-1.fc34
Same problem here: Updated to dracut-054-12.git20210521.fc34.x86_64 and later to a new kernel and I have keyboard + mouse connected via bluetooth, . At first reboot system stuck for long time at "Switch Root" and when move over abrtd, avahi-daemon, bluetooth, dbus, NetworkManager, rtkit-daemon, systemd-machined are in failed state. Restarting them bring the system back to its full capabilities, but is bad experience for end-user. If any log may be useful, let me know
Related bugs (may be duplicates): https://bugzilla.redhat.com/show_bug.cgi?id=1965859 https://bugzilla.redhat.com/show_bug.cgi?id=1964879
*** Bug 1968699 has been marked as a duplicate of this bug. ***
yeah, I think these are all the same thing. *** This bug has been marked as a duplicate of bug 1964879 ***