| 1 |
On 05/15/2014 10:50 PM, Mick wrote: |
| 2 |
> On Thursday 15 May 2014 14:24:57 Alexander Kapshuk wrote: |
| 3 |
>> On 05/15/2014 11:39 AM, Stroller wrote: |
| 4 |
>>> On Wed, 14 May 2014, at 12:36 pm, Alexander Kapshuk |
| 5 |
> <alexander.kapshuk@×××××.com> wrote: |
| 6 |
>>>>>> … |
| 7 |
>>>>>> If you like to check if RTL8192CE is enabled in your kernel's .config |
| 8 |
>>>>>> file. If it isn't, you probably want to compile it as a module, and |
| 9 |
>>>>>> then add rtl8192ce to /etc/conf.d/modules as well. |
| 10 |
>>>>> Am pretty sure there's no need to add this one to /etc/conf.d/modules - |
| 11 |
>>>>> IME it'll just be found and loaded automagically by the kernel. |
| 12 |
>>>> Thanks for pointing that out. I wasn't aware of that. As I mentioned in |
| 13 |
>>>> my previous post, I do not use genkernel myself. |
| 14 |
>>> Neither do I - for this reason I found it a little frustrating trying to |
| 15 |
>>> help in a recent thread, myself. |
| 16 |
>>> |
| 17 |
>>> However, I'm pretty sure that loadable kernel modules behave the same |
| 18 |
>>> whether your kernel is built "by hand" or by genkernel - if you have |
| 19 |
>>> modules listed in /etc/conf.d/modules then I have to wonder if you |
| 20 |
>>> really need them there. |
| 21 |
>>> |
| 22 |
>>> I haven't used that file for years, and I prefer to compile everything as |
| 23 |
>>> a module, too. |
| 24 |
>>> |
| 25 |
>>> Stroller. |
| 26 |
>> That's interesting. I wasn't aware of that either. |
| 27 |
>> |
| 28 |
>> So far, I've just been following the instructions given in the handbook, |
| 29 |
>> section 7.d, which do recommend explicitly specifying the kernel modules |
| 30 |
>> to be loaded at boot time in /etc/conf.d/modules. |
| 31 |
>> |
| 32 |
>> How does the kernel know then what modules to load at boot time, if it |
| 33 |
>> doesn't rely on /etc/conf.d/modules to supply the list of modules to be |
| 34 |
>> loaded? |
| 35 |
>> |
| 36 |
>> Does it use udev, or some other mechanism for that? |
| 37 |
>> |
| 38 |
>> Thanks. |
| 39 |
> I understand it is udev magic which probes the hardware and it fetches the |
| 40 |
> corresponding module from the kernel, as long as it has been compiled. |
| 41 |
> Incidentally, I noticed that I now have this running on my system: |
| 42 |
> |
| 43 |
> /lib/systemd/systemd-udevd --daemon |
| 44 |
> |
| 45 |
Understood. Thanks. I too have systemd-udevd running now that you |
| 46 |
mention it. |
Archives