> The SATA BIOS in this m/b always assigns the SATA drives to drive > codes 0x80, etc, That is quite common. > When the same kernel is loaded using /dev/sda1 as root, it finishes > initializing devices > and frees the kernel memory used during bootup, then says "unable to > create initial > console" on the first access to the SATA disk. Its a bit hard to tell what is going on. A first thing to try would be to completely turn off CONFIG_IDE. It won't fix the problem (or I'll be amazed if it does) but it will mean that everything that is going on is occuring through the same disk layer. Unable to create initial console implies it mounted a file system with no suitable /dev (eg because your setup expects udev & initrd, or because /dev/sda1 or whatever your root= entry gives isn't actually the right partition) > The 2.6.26.5 kernel has new support for the Intel ICH5 chips (Serial > ATA(prod)... -> > ATA SFF -> Intel ESB, ICH, PIIX4 ...) enabled. Actually it has the same as before but the menu shuffled around Alan -- To unsubscribe from this list: send the line "unsubscribe linux-ide" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
