On 01/19/2012 08:36 PM, jdmcdaniel3 wrote:
> My issue is the same old thing that comes up when you insist on
> installing the nVIDIA driver. Mostly they work, but ever so often they
> do not. Since there is a newer driver version, it most likely will be
> updated to work in the future. But in the end, the loss is mine wanting
> to use their driver with every released kernel version.
Since kernel 3.1, nouveau works with my nVidia adapter, and I do not need any
further acceleration. Besides, a tainted kernel would not work for me at all in
my kernel testing.
> While I have got your attention, I have a question. Have you ever used
> any of these in creating your kernel configuration?
> make localmodconfig
> make localyesconfig
> chmod +x ./scripts/kconfig/streamline_config.pl ; ./scripts/kconfig/streamline_config.pl> ./config_strip ; mv ./config_strip ./.config
> Anyone of the above configs can cause the kernel compiles to drop to a
> 1/4 of normal, but any module not presently loaded, is excluded and not
> useable later it would seem. Don’t have that thumb drive plugged in?
> Can’t use it later then perhaps. So any comment you might have on this
> subject is very important to me.
As far as I can tell, options 1 & 3 are the same thing. Why there is a Perl
script to do that I don’t know. Option 2 does the same thing, but compiles
everything into the kernel, rather than a module.
perl scripts/kconfig/streamline_config.pl > ./config_str
would avoid the need to do the chmod step.
The intent of those commands is to eliminate any modules not currently in use by
the kernel, and they do eliminate anything not loaded when they are run. I never
build the full 2000+ modules of a distribution kernel. My current .config has
been tailored to generate 519 modules. There are probably a few that are not
needed, but getting rid of them is more trouble that it is worth. A full kernel
build on a 2.0 GHz, dual-core AMD laptop that has a 7200 rpm hard drive and 3 GB
RAM takes a little over 20 minutes using the -j4 switch on the make.
If there is a module that you know you will need later, you can always modprobe
it before you generate the .config. In the case of the thumb drive, plug it in
once. Any needed modules will be loaded, and they will stay loaded. “modprobe
-r” or rmmod are the only ways to unload any module.
For several slow machines on which I do testing, including a 1.6 GHz netbook,
and an ancient laptop with a 450 MHz AMD K6 cpu, I use my desktop with a 3.5 GHz
dual core CPU, 4 GB of RAM, and 10,000 rpm disks to cross-compile the 32-bit
kernels on a 64-bit system. The source tree is exported via NFS, and the only
thing the target host does is the ‘make modules_install install’ step. On that
K6, that takes about as long as the compile. If I get full access, I use -j6 there.
I hope this answers your questions.