Weirdly enough, for me it gets loaded when in /etc/modules-load.d but still gives an error 'module not found'.
I'm having the same problem. I'm on a fresh install using Kernel Version 3.10.10-1, I add the module to /etc/modules-load.d/asus_nb_wmi.conf - It loads but complains on boot the the module hasn't been found, however this is the only way I can get it to actually load automatically. If I add it to the modules section of /etc/mkinitcpio.conf it doesn't load.
Without this module my screen brightness doesn't work. Any one have any idea why this might be? The error on boot is quite annoying and I'm interested in learning from this.
]]>I think there is a valid question here; Same thing happened to me.
Upon a default install of arch, the module was auto-loaded without the user touching any configuration files
at some point during kernel updates, the module is no longer auto-loaded
I once ran into a similar issue with a module. It turns out in the kernel update the module now had an extra module it depended on in the new kernel, but not in the old. When updating the kernel with pacman, it builds the initcpio using the modules loaded in the old kernel, so it doesn't realize the other module needs to go with it.
For me the solution was to load the module manually after boot, and then rerun mkinitcpio which now detected the extra module and added to the initcpio automatically.
]]>the user then has to find out what is happening and go add the module to the appropriate config file to force load on boot.
So the larger question is; without config files being taken into consideration, how does the kernel decide what modules to load? f
I know it has something to do with the hardware that it detects, but am unaware if this is something within the RC or systemctl booting system, or if this is part of the kernel.
I'm going to dig around some more on the internet, as i'm sure the answer is out there somewhere.. but if someone that is on this forum happens to read and know the answer, it would be nice to know
thanks
This is the output systemctl status shows:
systemd-modules-load.service - Load Kernel Modules
Loaded: loaded (/usr/lib/systemd/system/systemd-modules-load.service; static)
Active: failed (Result: exit-code) since Sun 2013-05-26 01:11:04 VET; 4min 18s ago
Docs: man:systemd-modules-load.service(8)
man:modules-load.d(5)
Process: 153 ExecStart=/usr/lib/systemd/systemd-modules-load (code=exited, status=1/FAILURE)
and the output that journalctl shows:
-- Logs begin at Fri 2013-02-08 13:10:52 VET, end at Sun 2013-05-26 01:16:49 VET. --
May 26 01:11:04 aghost systemd-modules-load[153]: Failed to insert 'asus_nb_wmi': No such device
Looks like the module is not being located, but I can load the same module after the system boots.
Best regards.
]]>I would be pleased to post more relevant information, could you give some guidelines so I can do it?
Best regards.
]]>Anyway, no one can answer your question with the information you provided. Is there some kind of searching ito the problem that you might have done on your own? Have you gathered any evidence of what is happening? Have you looked through the logs? Have you searched with the google to see if there are others who experience this as well?
In short, you need at least give some kind of info about the situation besides "Its broken, why is it doing this?"
]]>Best regards.
]]>