I had similar problems when I first started to build my own Linux kernel.

I tracked the problem down to 'tangled up' symbolic links.

I have learnt my lesson now and avoid having any symlinks if at all possible. Also, when building a new kernel, I never do a 'make install'. I always install the kernel image, system.map and modules manually, then I know exactly what is happening.

Toods.

To Toods: You can install modules with make install_modules. It doesn't create any symlinks, just copy modules to /lib/modules/kernel-version.

To NNP: Check that your filesystem support is compiled not as module but into the kernel;
Check that you haven't enabled SATA or SCSI disk support (they shouldn't cause problems. but it's better to check), if you have and IDE disk.
Use Slackware 2.6 kernel config and check additional required options. If it works, you can reduce the number of selected options and finally find what was causing kernel panic.

That's good to know. Is 'make install_modules' the same effectively as 'make modules_install'?.

Toods: I think it was a typo, so yes (damn will i feel silly if it wasnt )

Alien_Hominoid: What do you mean by 'Use Slackware 2.6 kernel config'. Do you mean create a fresh .config file?

Thanks,
NNP

To Toods: Sorry for very stupid previous post. It should be make modules_install. My fault. But it works as I said.

To NNP: ftp://ftp.slackware.com/pub/slackwar...est26.s/config.