| 1 |
On Nov 11, 2011 11:02 AM, "Nikos Chantziaras" <realnc@×××××.de> wrote: |
| 2 |
> |
| 3 |
> On 11/11/2011 04:16 AM, Walter Dnes wrote: |
| 4 |
>> |
| 5 |
>> On Thu, Nov 10, 2011 at 07:51:04PM +0100, Jarry wrote |
| 6 |
>>> |
| 7 |
>>> Hi, |
| 8 |
>>> during testing I compiled kernel with some modules |
| 9 |
>>> (make&& make modules_install). Now I deactivated |
| 10 |
>>> |
| 11 |
>>> module-support and compiled everything in kernel. |
| 12 |
>> |
| 13 |
>> |
| 14 |
>> On this very same topic, there's one module I can't seem to get rid |
| 15 |
>> of. At the end of every "make", I see stuff like... |
| 16 |
>> |
| 17 |
>> Kernel: arch/x86/boot/bzImage is ready (#2) |
| 18 |
>> Building modules, stage 2. |
| 19 |
>> MODPOST 1 modules |
| 20 |
>> CC drivers/scsi/scsi_wait_scan.mod.o |
| 21 |
>> LD [M] drivers/scsi/scsi_wait_scan.ko |
| 22 |
>> |
| 23 |
>> Then "make modules_install" spits out... |
| 24 |
>> |
| 25 |
>> [i3][root][/usr/src/linux] make modules_install |
| 26 |
>> INSTALL drivers/scsi/scsi_wait_scan.ko |
| 27 |
>> DEPMOD 2.6.39-gentoo-r3 |
| 28 |
>> |
| 29 |
>> *BUT*, it doesn't seem to be running... |
| 30 |
>> |
| 31 |
>> [i3][root][/usr/src/linux] lsmod |
| 32 |
>> Module Size Used by |
| 33 |
>> |
| 34 |
>> I can't seem to find where in the "make menuconfig" process it's |
| 35 |
>> selected. I don't want to edit my .config directly. What gives? |
| 36 |
> |
| 37 |
> |
| 38 |
> This module cannot be disabled. The function of this module is a bit |
| 39 |
special and unlike other modules. Its job is to stall the boot process of |
| 40 |
the kernel until the SCSI drivers have finished scanning all their buses. |
| 41 |
That's the only thing this module does. It's not a driver and does not |
| 42 |
offer any kind of functionality; it's just a "handbrake", and when that job |
| 43 |
is finished (SCSI drivers finished scanning) it's no longer needed. It is |
| 44 |
used by initrd scripts. If you don't use modules in initrd, then this |
| 45 |
module is not used at all. |
| 46 |
> |
| 47 |
> Also, it *needs* to be loaded as a module and can't be built into the |
| 48 |
kernel, since it stalls the boot process as soon as its loaded. It cannot |
| 49 |
be disabled. This is a conscious decision by upstream and not an |
| 50 |
oversight. The rationale is that there's nothing to gain by disabling it |
| 51 |
while it can be vital for people using initrd. |
| 52 |
> |
| 53 |
> So short answer: ignore it. Or simply delete it. |
| 54 |
> |
| 55 |
|
| 56 |
Isn't there a selection in make menuconfig "asynchronous scsi scan" (or |
| 57 |
something like that)? |
| 58 |
|
| 59 |
Rgds, |
Archives