| Summary: | [FAILED] Failed to start Load legacy module configuration | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Pe Alfa <pealfa> |
| Component: | RPM Packages | Assignee: | Mageia Bug Squad <bugsquad> |
| Status: | RESOLVED DUPLICATE | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | davidwhodgins, ouaurelien, sysadmin-bugs |
| Version: | 8 | ||
| Target Milestone: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | CVE: | ||
| Status comment: | |||
Hi! Is this bug the same? https://bugs.mageia.org/show_bug.cgi?id=19795 Hi, thanks reporting this. And yes, your bug is duplicate. Please add info there, please. *** This bug has been marked as a duplicate of bug 19795 *** Status:
NEW =>
RESOLVED (In reply to Pe Alfa from comment #0) > If I put in /etc/modprobe.preload > # hdaps > failed disappears > Is it a solution? Moving the failing to load modules from being loaded after the initrd switches root to the hard drive to being loaded by the initrd does hide the problem, but it doesn't stop the module from failing to load, or mcc insisting that the module is needed. So it's a workaround, not a solution. It is a valid option for those who encounter this bug until it is fixed. Thanks for pointing it out. CC:
(none) =>
davidwhodgins |
Hi. Another failed at start on Lenovo ideapad Gaming 3-15ARH05 Laptop - Type 82EY. [FAILED] Failed to start Load legacy module configuration I did: (1) systemctl list-units | grep -i failed ● fedora-loadmodules.service loaded failed failed Load legacy module configuration ... (2) systemctl status fedora-loadmodules.service ● fedora-loadmodules.service - Load legacy module configuration Loaded: loaded (/usr/lib/systemd/system/fedora-loadmodules.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Mon 2021-03-08 22:13:57 CET; 23min ago Process: 809 ExecStart=/usr/lib/systemd/fedora-loadmodules (code=exited, status=1/FAILURE) Main PID: 809 (code=exited, status=1/FAILURE) CPU: 8ms mar 08 22:13:57 lenovo systemd[1]: Starting Load legacy module configuration... mar 08 22:13:57 lenovo fedora-loadmodules[810]: Loading modules: nvram evdev hdaps mar 08 22:13:57 lenovo fedora-loadmodules[818]: modprobe: ERROR: could not insert 'hdaps': No such device mar 08 22:13:57 lenovo systemd[1]: fedora-loadmodules.service: Main process exited, code=exited, status=1/FAILURE mar 08 22:13:57 lenovo systemd[1]: fedora-loadmodules.service: Failed with result 'exit-code'. mar 08 22:13:57 lenovo systemd[1]: Failed to start Load legacy module configuration. (3) cat /etc/modprobe.preload ... nvram evdev hdaps (4) If I put in /etc/modprobe.preload # hdaps failed disappears Is it a solution? Thanks Pepe Álvarez