From: Alexander Kapshuk <alexander.kapshuk@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Having Trouble with Wireless Interface
Date: Fri, 16 May 2014 16:37:36 +0300 [thread overview]
Message-ID: <537614A0.6090506@gmail.com> (raw)
In-Reply-To: <201405152050.13159.michaelkintzios@gmail.com>
On 05/15/2014 10:50 PM, Mick wrote:
> On Thursday 15 May 2014 14:24:57 Alexander Kapshuk wrote:
>> On 05/15/2014 11:39 AM, Stroller wrote:
>>> On Wed, 14 May 2014, at 12:36 pm, Alexander Kapshuk
> <alexander.kapshuk@gmail.com> 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.
> I understand it is udev magic which probes the hardware and it fetches the
> corresponding module from the kernel, as long as it has been compiled.
> Incidentally, I noticed that I now have this running on my system:
>
> /lib/systemd/systemd-udevd --daemon
>
Understood. Thanks. I too have systemd-udevd running now that you
mention it.
next prev parent reply other threads:[~2014-05-16 13:35 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-12 19:31 [gentoo-user] Having Trouble with Wireless Interface Hunter Jozwiak
2014-05-13 5:32 ` the
2014-05-13 11:00 ` Alexander Kapshuk
2014-05-13 11:45 ` Hunter Jozwiak
2014-05-13 12:19 ` Alexander Kapshuk
2014-05-13 13:25 ` Hunter Jozwiak
2014-05-13 13:53 ` Alexander Kapshuk
2014-05-13 14:53 ` Alexander Kapshuk
2014-05-14 9:41 ` Stroller
2014-05-14 11:36 ` Alexander Kapshuk
2014-05-15 8:39 ` Stroller
2014-05-15 9:29 ` Alan McKinnon
2014-05-15 11:30 ` Hunter Jozwiak
2014-05-15 17:25 ` Stroller
2014-05-15 13:24 ` Alexander Kapshuk
2014-05-15 19:50 ` Mick
2014-05-16 13:37 ` Alexander Kapshuk [this message]
2014-05-18 1:05 ` [gentoo-user] " Jonathan Callen
2014-05-21 17:56 ` Alexander Kapshuk
2014-05-21 19:29 ` Mick
2014-05-22 3:34 ` Jonathan Callen
2014-05-22 16:37 ` Alexander Kapshuk
2014-05-14 19:29 ` [gentoo-user] " Mick
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=537614A0.6090506@gmail.com \
--to=alexander.kapshuk@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox