I'm really stumped here. I recently bought an Abit KN8-SLI which has 4 SATA controllers and 2 IDE controllers. No matter what I've tried I simply cannot boot linux(centos or debian) from the PATA controller. The controller is fine because I can boot my old WinXP PATA drive on it. I can boot linux from a second SATA drive but I really need to boot from PATA.
I've tried the following:
#1. WinXP on first SATA(sda), Debian on master PATA(hda) first primary IDE channel. I did a fresh install of Debian and it detected WinXP on the SATA drive and made a grub entry for it and a grub-install but when I boot up I just get a fat ugly error "grub read error".
#2. Centos on master PATA(hda) primary IDE channel, no other drives installed. This drive boots just fine in my old computer on the primary IDE channel but on the Abit I get a DISK FAILURE DEVICE NOT AVAILABLE.
In the BIOS I've tried everything I can think of to get this to work. I have an old WinXP on PATA and it boots just fine so it's not the controller itself. There's something with grub that is causing it to get confused when it boots linux on PATA and I don't know what it is.
Here's the relevant parts of /boot/grub/menu.lst from a fresh debian install using scenario #1.
Code:
title Debian GNU/Linux, kernel 2.6.8-2-386
root (hd0,0)
kernel /boot/vmlinuz-2.6.8-2-386 root=/dev/hda1 ro
initrd /boot/initrd.img-2.6.8-2-386
savedefault
boot
title Debian GNU/Linux, kernel 2.6.8-2-386 (recovery mode)
root (hd0,0)
kernel /boot/vmlinuz-2.6.8-2-386 root=/dev/hda1 ro single
initrd /boot/initrd.img-2.6.8-2-386
savedefault
boot
### END DEBIAN AUTOMAGIC KERNELS LIST
# This is a divider, added to separate the menu items below from the Debian
# ones.
title Other operating systems:
root
# This entry automatically added by the Debian installer for a non-linux OS
# on /dev/sda1
title Windows NT/2000/XP (loader)
root (hd1,0)
savedefault
makeactive
chainloader +1
Thanks for any help you can offer