At a guess, you didn't compile the mptbase driver into your custom 2.6.14?

well at the end of the kernel build i did a make modules and a make modules_install and nothing complained.

any other ideas??

thanks

On Tue, 23 May 2006 at 2:22pm, Tom Brown wrote

...

At a guess, you didn't compile the mptbase driver into your custom 2.6.14?

well at the end of the kernel build i did a make modules and a make modules_install and nothing complained.

Not building a module won't make the build process complain -- it'll just assume you didn't want it. What does 'grep -A10 Fusion .config' say?

On Tue, 23 May 2006 at 2:34pm, Tom Brown wrote

...

Not building a module won't make the build process complain -- it'll just assume you didn't want it. What does 'grep -A10 Fusion .config' say?

OK i see

grep -A10 Fusion .config # Fusion MPT device support # CONFIG_FUSION=y CONFIG_FUSION_SPI=y CONFIG_FUSION_FC=y CONFIG_FUSION_SAS=m CONFIG_FUSION_MAX_SGE=128 CONFIG_FUSION_CTL=y

You built support into the kernel (y), rather than as a module. That's fine if you want it that way, but then you don't need the correpsonding entry in /etc/modprobe.conf.

Tom Brown wrote:

...

You built support into the kernel (y), rather than as a module. That's fine if you want it that way, but then you don't need the correpsonding entry in /etc/modprobe.conf.

OK thanks i understand this now - previously i have done a make menuconfig but this time i just edited the .config file as i was advised to do it that way.

Using just the .config if i want to build something as a module rather than into the kernel when it comes to that section of the .config file do i just

CONFIG_FUSION=n

for example?

I think you mean m, not n.

I have learnt the hard way that there are many scripts in a redhat system that break if you try to compile code as built-in, but RH initially compiled it as a module.

The mkinitrd script has a few options for modules vs built-in, but they are of limited flexibiity.

Yes i did mean m sorry - although i have an interesting thing going on and i don't think i'm going mad... I change that option in config to be a 'm' rather than a 'y' and then run my kernel make. After the make i look at the .config file and that option has changed back to a 'y' ?? Can anyone tell me the reason that happens please

figured it all out now

thanks!