On 21 Mar 2008, at 15:00, Dale wrote:
...
I'm not sure what this is but it keeps setting it as a module. I tried removing it by setting it to " is not set" but it puts it back to module when I compile the kernel.

I'm not convinced that all the other posters are fully grokking your problem (some of them may be; heck, I could be wrong, and they all may be).

I suspect that this is caused because CONFIG_SCSI_WAIT_SCAN depends upon some other kernel option, and because you have that compiled in as a module. Thus the dependencies of the "parent" are forced to be modular.

I wouldn't disable CONFIG_MODULES, because as I understand it that prevents you having any modules at all, and builds a completely monolithic kernel. I used to be of the monolithic school of kernel building, but feel that I have seen the error of my ways and that modules are generally a Good Thing (tm).

I would compile-into-the-kernel (what's the right word for "compile a driver not-as-a-module"? compile statically?) all SCSI options, and see if that fixes. If so you can subsequently modularise bit by bit until you understand what's going on.

(PS: you say you don't know what it is - why do you care if it's modular or not?)

Stroller.
--
[email protected] mailing list

Reply via email to