Ok we believe that this issue is now visible because udev is now waiting for devices to settle. This means we wait in the initramfs for the longest running device init. The floppy driver is likely doing the right thing overall. We have a floppy controller in most of these cases and therefore the driver should load. Where they are not initialising quickly, or are missing this is likely correct behaviour and not a problem if we are not synchronous. As we are meant to only have modules required to mount root in the initramfs anyhow, floppy seems like it should not be in there. If it was not in the initramfs we would then load it asynchonously in immediatly after mounting root.
I will prepare a versions of initramfs-tools which excludes floppy so we can test this hypothesis. -- Linux thinks there’s a floppy drive when there’s not. Probing slows down bootup by almost a minute. https://bugs.launchpad.net/bugs/384579 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
