Advertisement
Not a member of Pastebin yet?
Sign Up,
it unlocks many cool features!
- [root@localhost ~]# systemctl status fedora-loadmodules.service
- ● fedora-loadmodules.service - Load legacy module configuration
- Loaded: loaded (/usr/lib/systemd/system/fedora-loadmodules.service; static)
- Active: failed (Result: exit-code) since Wed 2016-01-13 16:56:58 MST; 18min ago
- Process: 647 ExecStart=/lib/systemd/fedora-loadmodules (code=exited, status=1/FAILURE)
- Main PID: 647 (code=exited, status=1/FAILURE)
- Jan 13 16:56:50 localhost.localdomain systemd[1]: fedora-loadmodules.service: main process exited, code=exited, stat...ILURE
- Jan 13 16:56:50 localhost.localdomain systemd[1]: Failed to start Load legacy module configuration.
- Jan 13 16:56:50 localhost.localdomain systemd[1]: Unit fedora-loadmodules.service entered failed state.
- Jan 13 16:56:50 localhost.localdomain systemd[1]: fedora-loadmodules.service failed.
- Jan 13 16:56:58 localhost.localdomain systemd[1]: fedora-loadmodules.service: main process exited, code=exited, stat...ILURE
- Jan 13 16:56:58 localhost.localdomain systemd[1]: Failed to start Load legacy module configuration.
- Jan 13 16:56:58 localhost.localdomain systemd[1]: Unit fedora-loadmodules.service entered failed state.
- Jan 13 16:56:58 localhost.localdomain systemd[1]: fedora-loadmodules.service failed.
- Jan 13 16:57:06 localhost.localdomain fedora-loadmodules[647]: Loading modules: nvram evdev hdaps acpi-cpufreq cpufre...mand
- Jan 13 16:57:06 localhost.localdomain fedora-loadmodules[647]: modprobe: ERROR: could not insert 'hdaps': No such device
- Hint: Some lines were ellipsized, use -l to show in full.
- [root@localhost ~]#
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement