The result is that the systemd-modules-load.service fails to load, and user sees messages like this on console (possibly other fallout).
| [[32m OK [0m] Started Nameserver information manager.
| resolvconf.service
| [ 4.808918] systemd[1]: systemd-modules-load.service: main process exited, code=exited, status=1/FAILURE
| [[1;31mFAILED[[ 4.810826] systemd[1]: Failed to start Load Kernel Modules.
| 0m] Failed to st[ 4.811754] systemd[1]: Unit systemd-modules-load.service entered failed state.
| art Load Kernel [ 4.812820] systemd[1]: systemd-modules-load.service failed.
| Modules.
| See "systemctl status systemd-modules-load.service" for details.
Ideally there would be a way to say "load this if it exists", or some other way that failed module loads could be marked as non-fatal.
That said, as Martin reports, the acpiphp module is no longer present in vivid (3.19.0-7-generic).
For reference:
utopic:
$ find /lib/modules -iname "*acpi*" -type f
/lib/modules/3.16.0-31-generic/kernel/drivers/acpi/acpi_ipmi.ko
/lib/modules/3.16.0-31-generic/kernel/drivers/acpi/acpi_pad.ko
/lib/modules/3.16.0-31-generic/kernel/drivers/acpi/acpi_extlog.ko
$ find /lib/modules -iname "*acpi*" -type f
/lib/modules/3.13.0-46-generic/kernel/drivers/acpi/acpi_pad.ko
/lib/modules/3.13.0-46-generic/kernel/drivers/acpi/acpi_ipmi.ko
/lib/modules/3.13.0-46-generic/kernel/drivers/acpi/acpi_extlog.ko
So we've been rid of acpiphp.ko since at least 14.04.
as reported by pitti under bug 450463, the cloud-images have the following in /etc/modules:
| # LP: #450463
| acpiphp
That is written by http:// bazaar. launchpad. net/~ubuntu- on-ec2/ vmbuilder/ automated- ec2-builds/ view/head: /vmbuilder- cloudimg- fixes
The result is that the systemd- modules- load.service fails to load, and user sees messages like this on console (possibly other fallout).
| [[32m OK [0m] Started Nameserver information manager. modules- load.service: main process exited, code=exited, status=1/FAILURE modules- load.service entered failed state. modules- load.service failed. modules- load.service" for details.
| resolvconf.service
| [ 4.808918] systemd[1]: systemd-
| [[1;31mFAILED[[ 4.810826] systemd[1]: Failed to start Load Kernel Modules.
| 0m] Failed to st[ 4.811754] systemd[1]: Unit systemd-
| art Load Kernel [ 4.812820] systemd[1]: systemd-
| Modules.
| See "systemctl status systemd-
Ideally there would be a way to say "load this if it exists", or some other way that failed module loads could be marked as non-fatal.
That said, as Martin reports, the acpiphp module is no longer present in vivid (3.19.0-7-generic).
For reference: 3.16.0- 31-generic/ kernel/ drivers/ acpi/acpi_ ipmi.ko 3.16.0- 31-generic/ kernel/ drivers/ acpi/acpi_ pad.ko 3.16.0- 31-generic/ kernel/ drivers/ acpi/acpi_ extlog. ko
utopic:
$ find /lib/modules -iname "*acpi*" -type f
/lib/modules/
/lib/modules/
/lib/modules/
$ find /lib/modules -iname "*acpi*" -type f 3.13.0- 46-generic/ kernel/ drivers/ acpi/acpi_ pad.ko 3.13.0- 46-generic/ kernel/ drivers/ acpi/acpi_ ipmi.ko 3.13.0- 46-generic/ kernel/ drivers/ acpi/acpi_ extlog. ko
/lib/modules/
/lib/modules/
/lib/modules/
So we've been rid of acpiphp.ko since at least 14.04.