On 05/15/2014 11:39 AM, Stroller wrote: > On Wed, 14 May 2014, at 12:36 pm, Alexander Kapshuk > <[email protected]> wrote: >>>> … >>>> If you like to check if RTL8192CE is enabled in your kernel's .config >>>> file. If it isn't, you probably want to compile it as a module, and then >>>> add rtl8192ce to /etc/conf.d/modules as well. >>> Am pretty sure there's no need to add this one to /etc/conf.d/modules - IME >>> it'll just be found and loaded automagically by the kernel. >> Thanks for pointing that out. I wasn't aware of that. As I mentioned in >> my previous post, I do not use genkernel myself. > Neither do I - for this reason I found it a little frustrating trying to help > in a recent thread, myself. > > However, I'm pretty sure that loadable kernel modules behave the same whether > your kernel is built "by hand" or by genkernel - if you have modules listed > in /etc/conf.d/modules then I have to wonder if you really need them there. > > I haven't used that file for years, and I prefer to compile everything as a > module, too. > > Stroller. > > That's interesting. I wasn't aware of that either.
So far, I've just been following the instructions given in the handbook, section 7.d, which do recommend explicitly specifying the kernel modules to be loaded at boot time in /etc/conf.d/modules. How does the kernel know then what modules to load at boot time, if it doesn't rely on /etc/conf.d/modules to supply the list of modules to be loaded? Does it use udev, or some other mechanism for that? Thanks.
