I installed the smart link module trying to get my modem working. Never
got it working, so I umerged it. It is still loading the modules on
boot (along with the kernel taint warnings). How do I get rid of the
modules?

Randall

Randall Smith wrote:

Hello Randall, hello Usenet,

> I installed the smart link module trying to get my modem working.
> Never got it working, so I umerged it. It is still loading the
> modules on boot (along with the kernel taint warnings). How do I get
> rid of the modules?

Take a look if the module is being loaded
in /etc/modules.autoload.d/kernel-your.version and remove it from
there, if you find something.
Otherwise there might be an init script which loads the module, so take
a look at the output of "rc-update -s". If you don't find something
special here, you can always do a full text search for the module name
in /etc/init.d/.

HTH,
Stefan.

Thanks for your response Stefan.

It's not autoloading and I didn't find an init script loading it. It is
still /etc/modules.conf. Is this why. Looks like I'm not supposed to
edit it manually. I've run modules-update and that doesn't seem to do
it. Any more ideas?

Randall

Stefan Tittel wrote:
> Randall Smith wrote:
>
> Hello Randall, hello Usenet,
>
>
>>I installed the smart link module trying to get my modem working.
>>Never got it working, so I umerged it. It is still loading the
>>modules on boot (along with the kernel taint warnings). How do I get
>>rid of the modules?
>
>
> Take a look if the module is being loaded
> in /etc/modules.autoload.d/kernel-your.version and remove it from
> there, if you find something.
> Otherwise there might be an init script which loads the module, so take
> a look at the output of "rc-update -s". If you don't find something
> special here, you can always do a full text search for the module name
> in /etc/init.d/.
>
> HTH,
> Stefan.

Randall Smith <randall@tnr.cc> writes:

> Thanks for your response Stefan.
>
> It's not autoloading and I didn't find an init script loading it. It
> is still /etc/modules.conf. Is this why. Looks like I'm not supposed
> to edit it manually. I've run modules-update and that doesn't seem to
> do it. Any more ideas?

modules-update just creates /etc/modules.conf from the config data found
in /etc/modules.d which is a gentoo-only thing as far as I know.

So take a look in the files in /etc/modules.d/ and see if you can find
the name of the problem module. Edit it out of whichever file you find
it in, and then run modules-update again.