Cool, thanks heaps QuakeBoy, I think you may actually be onto something with the *'s vs M's as there was a M where 'ATA' support was. I'll play with a few things and let you know.

FYI here is my menu.lst layout (minus the single options):
(doesnt work)
title Debian GNU/Linux, kernel 2.6.27.2
root (hd0,0)
kernel /boot/vmlinuz-2.6.27.2 root=/dev/sda1 ro
savedefault

(works)
title Debian GNU/Linux, kernel 2.6.18-6-686
root (hd0,0)
kernel /boot/vmlinuz-2.6.18-6-686 root=/dev/sda1 ro
initrd /boot/initrd.img-2.6.18-6-686
savedefault

I hope so. Both libata and your controller must be <*> since they are both modules that must be running. I've just always used initrd.

Hmm, I've just looked at this again, and notice the "initrd" in the one that works? I'll bet your config has <m> in one of the disk modules, otherwise that line wouldn't be there.

Woops, double post.

Should I try compiling with initrd then? To be honest im not sure what initrd is. I'll google it

Sooooo I added the initrd location in (it turns out i createded one of those initrd files in /boot/) and now I get:

pivot_root: No such file or directory
/sbin/init: 432: cannot open dev/console: no such file
Kernel panic - not syncing: Attempt to kill init!

Edit:
I suspect this is because I cleared the lib/modules/2.6.24.2 folder, and havent recompiled. Doing that now, will test it. Looks like the initrd in the menu.lst did the trick though - maybe...

Solved. You were on the mark with a few points. I did the following:

1. Performed your method of configuring the menuoptions by copying the old and make oldconfig
2. recompiled to a fresh directory
3. I added the initrd location into the menu.lst
4. I re-made the initrd file

Works perfectly. Thanks!!!

Glad you got it going! Just a couple more comments then.

The initrd is actually an initramfs (initial ram filesystem). If my understanding is correct, then this is a zipped file containing everything the kernel needs to boot, including a copy of the loadable disk module(s). During bootup, it's running off that and has the modules, and since the disks are running it will load them before switching. (Or something vaguely like that, but you get the picture.) OTOH, if you're not using an initrd(initramfs) then you must use the <*> options othewise the disk modules never get loaded.

Also, there are two components to using an initrd. One is the compile string, as you found out. The other is a kernel config option. If either is left out things kind of go wrong.

If you just add "--initrd" to your make string, as below, then it will create the initrd. When you run "dpkg -i" it should install that properly and update your menu.lst file. However, since it sounds like you switched from not using initrd to using it without cleaning menu.lst, dpkg got confused and didn't add the initrd line.

Normally when I remove a kernel and want it completely washed, dried, and removed I use the synaptic manager. But, I believe you still have to remove the directory from /lib/modules for some reason.

Good luck and have fun!

Thanks for that Quakeboy - I've learned alot about Linux so far

Now to figure out how to get these blasted network drivers to work.

Thanks again;
Gareth

Hey guys,
This is my first post here as well. I've had exactly the same problem changing from 2.6.18 to 2.6.27.2, but I've found the changing the configuration to "y" for the SATA controller module works. BTW mine is also Intel ICH7. Thanks Quakerboy02, you're right, it's "y" for ATA_SFF and ATA_PIIX. Now it's seeing the hard drives, all three correctly detected, but the next line is:

No filesystem could mount root, tried: cramfs
Kerel panic - not syncing: VFS: Unable to mount root fs on unknown-block(8,33)

Any ideas on that one? Sorry to get a little of topic. I'm not sure if it's trying to boot the wrong drive, although as Auxientius said, 2.4.18 still boots fine.

Hey Dave,

Have you made the initrd file, and is it referenced in /boot/menu.lst? I found that was my issue.

Oh, and I had to recompile after changing those settings in the .config fle - not sure if you did.

Not sure if that will help - i'm still extremely new at this and to be honest I think I guessed most of my way though!

Gareth

Dave, if you could report your post and ask for it to be made into a new thread I'd be glad to help. Or you could just copy your post to a new thread, I guess. It's really best not to have two different people running problems in a single thread.