[prev in list] [next in list] [prev in thread] [next in thread] 

List:       gentoo-user
Subject:    [gentoo-user] Re: how to get rid of kernel modules?
From:       Nikos Chantziaras <realnc () arcor ! de>
Date:       2011-11-12 2:50:29
Message-ID: j9kmth$32u$1 () dough ! gmane ! org
[Download RAW message or body]

On 11/11/2011 08:14 AM, Pandu Poluan wrote:
>
> On Nov 11, 2011 11:02 AM, "Nikos Chantziaras" <realnc@arcor.de
> <mailto:realnc@arcor.de>> wrote:
>  >
>  > On 11/11/2011 04:16 AM, Walter Dnes wrote:
>  >>
>  >> On Thu, Nov 10, 2011 at 07:51:04PM +0100, Jarry wrote
>  >>>
>  >>> Hi,
>  >>> during testing I compiled kernel with some modules
>  >>> (make&&  make modules_install). Now I deactivated
>  >>>
>  >>> module-support and compiled everything in kernel.
>  >>
>  >>
>  >>   On this very same topic, there's one module I can't seem to get rid
>  >> of.  At the end of every "make", I see stuff like...
>  >>
>  >> Kernel: arch/x86/boot/bzImage is ready  (#2)
>  >>   Building modules, stage 2.
>  >>   MODPOST 1 modules
>  >>   CC      drivers/scsi/scsi_wait_scan.mod.o
>  >>   LD [M]  drivers/scsi/scsi_wait_scan.ko
>  >>
>  >> Then "make modules_install" spits out...
>  >>
>  >> [i3][root][/usr/src/linux] make modules_install
>  >>   INSTALL drivers/scsi/scsi_wait_scan.ko
>  >>   DEPMOD  2.6.39-gentoo-r3
>  >>
>  >> *BUT*, it doesn't seem to be running...
>  >>
>  >> [i3][root][/usr/src/linux] lsmod
>  >> Module                  Size  Used by
>  >>
>  >>   I can't seem to find where in the "make menuconfig" process it's
>  >> selected.  I don't want to edit my .config directly.  What gives?
>  >
>  >
>  > This module cannot be disabled.  The function of this module is a bit
> special and unlike other modules.  Its job is to stall the boot process
> of the kernel until the SCSI drivers have finished scanning all their
> buses.  That's the only thing this module does.  It's not a driver and
> does not offer any kind of functionality; it's just a "handbrake", and
> when that job is finished (SCSI drivers finished scanning) it's no
> longer needed.  It is used by initrd scripts.  If you don't use modules
> in initrd, then this module is not used at all.
>  >
>  > Also, it *needs* to be loaded as a module and can't be built into the
> kernel, since it stalls the boot process as soon as its loaded.  It
> cannot be disabled.  This is a conscious decision by upstream and not an
> oversight.  The rationale is that there's nothing to gain by disabling
> it while it can be vital for people using initrd.
>  >
>  > So short answer: ignore it.  Or simply delete it.
>  >
>
> Isn't there a selection in make menuconfig "asynchronous scsi scan" (or
> something like that)?

There is.  But scsi_wait_scan.ko will still be built.


[prev in list] [next in list] [prev in thread] [next in thread]