[gentoo-user] 2 kernel config questions

[gentoo-user] 2 kernel config questions

[Walter Dnes]

  1) If I enable "x86 PAT support" can I drop MTRR support?  They seem
to duplicate function.

  2) I notice that "scsi_wait_scan" *ALWAYS ALWAYS ALWAYS* shows up as
a module when I compile.  Is there a way to compile it in?  It does not
show up as a menu item anywhere.  Even if I manually go into .config
with vim, and change the entry to...

CONFIG_SCSI_WAIT_SCAN=y

it *STILL* builds as a module.  I've de-crapified my kernel, but what it
needs, I prefer to build into the kernel itself.  My bootup menu has 2
entries.  The first (default) is "Production", and the second is
"Experimental".  I do my screwing around with the experimental version.
If it dies during bootup, I can always go back to production, and
restore from a backup copy of .config.  If the experimental kernel runs
OK for a couple of weeks, I promote it to production.

-- 
Walter Dnes <waltdnes@waltdnes.org>

Re: [gentoo-user] 2 kernel config questions

[Volker Armin Hemmann]

On Donnerstag 12 November 2009, Walter Dnes wrote:
>   1) If I enable "x86 PAT support" can I drop MTRR support?  They seem
> to duplicate function.

no

Re: [gentoo-user] 2 kernel config questions

[Duane Griffin]

2009/11/12 Walter Dnes <waltdnes@waltdnes.org>:
>  2) I notice that "scsi_wait_scan" *ALWAYS ALWAYS ALWAYS* shows up as
> a module when I compile.  Is there a way to compile it in?

No, due to the nature of what it does. It is designed to be loaded
after the modules that start probing hardware, to ensure they find the
device holding your root filesystem before booting continues. If your
SCSI drivers are built in, or you don't do async scanning, then you
don't need it.

Take a look at the help for SCSI_SCAN_ASYNC and in the comments by its
entry in drivers/scsi/Kconfig for more info.

Cheers,
Duane.

-- 
"I never could learn to drink that blood and call it wine" - Bob Dylan

Re: [gentoo-user] 2 kernel config questions

[gk]

Am Donnerstag, 12. November 2009 04:03:22 schrieb Walter Dnes:
>   1) If I enable "x86 PAT support" can I drop MTRR support?  They seem
> to duplicate function.
> 
>   2) I notice that "scsi_wait_scan" *ALWAYS ALWAYS ALWAYS* shows up as
> a module when I compile.  Is there a way to compile it in?  It does not
> show up as a menu item anywhere.  Even if I manually go into .config
> with vim, and change the entry to...
> 
> CONFIG_SCSI_WAIT_SCAN=y
> 
> it *STILL* builds as a module.  I've de-crapified my kernel, but what it
> needs, I prefer to build into the kernel itself.  My bootup menu has 2
> entries.  The first (default) is "Production", and the second is
> "Experimental".  I do my screwing around with the experimental version.
> If it dies during bootup, I can always go back to production, and
> restore from a backup copy of .config.  If the experimental kernel runs
> OK for a couple of weeks, I promote it to production.
> 
Hi
I found this patch some time ago, and use it all the time.

Signed-off-by: Bernhard Walle <bwalle[at]suse.de> 
--- 
 drivers/scsi/Kconfig | 11 ++++++++--- 
 1 files changed, 8 insertions(+), 3 deletions(-) 
 
diff --git a/drivers/scsi/Kconfig b/drivers/scsi/Kconfig 
index 403ecad..42b8355 100644 
--- a/drivers/scsi/Kconfig 
+++ b/drivers/scsi/Kconfig 
@@ -257,10 +257,15 @@ config SCSI_SCAN_ASYNC 
 or async on the kernel's command line. 
 
 config SCSI_WAIT_SCAN 
- tristate 
+ tristate "Module to wait until all the async scans are complete" 
 default m 
- depends on SCSI 
- depends on MODULES 
+ depends on SCSI && m 
+ help 
+ This is a simple module to wait until all the async scans are 
+ complete. The idea is to use it in initrd/initramfs scripts. You 
+ modprobe it after all the modprobes of the root SCSI drivers and it 
+ will wait until they have all finished scanning their busses before 
+ allowing the boot to proceed 
 
 menu "SCSI Transports" 
 depends on SCSI 

It's just an example, it will not work as patch. I always change it manual.
So it is marked as module and I can disable it.

Günter