© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
73416ba
(Get the code!)
Documentation of the issue seems like a reasonable way forwards, assuming the crc32c module is also pre-installed into the installer initrd and left as a choice for the sysadmin to add it manually.
The first reboot post install would still be affected until adding the module into the the documentation steps could be performed though.
Is there some way to make udev or some other process that is aware of the presence of the affected hardware notify the admin to include the module?
On the other hand this patch really doesn't seem too intrusive as it will only install the module when it is actually needed, this would also create the initrd properly for the first reboot post install.