RE: [gentoo-user] Having Trouble with Wireless Interface

[Hunter Jozwiak]

I got the networking interface to function correct.y now. Thanks all for the
help!

-----Original Message-----
From: Alan McKinnon [mailto:alan.mckinnon@×××××.com] 
Sent: Thursday, May 15, 2014 5:29 AM
To: gentoo-user@l.g.o
Subject: Re: [gentoo-user] Having Trouble with Wireless Interface

On 15/05/2014 10:39, Stroller wrote:
>
> On Wed, 14 May 2014, at 12:36 pm, Alexander Kapshuk
<alexander.kapshuk@×××××.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.


Some modules don't autoload, usually because there's no hardware they drive
and so nothing to probe.

netfilter modules come to mind, as well as VirtualBox. One of the vbox
modules doesn't autoload by just stating VirtualBox, so the easiest is to
put it in /etc/conf.d/modules so it's always available. It's an edge case,
so the vast majority of modules load properly without intervention form us.




--
Alan McKinnon
alan.mckinnon@×××××.com