GRUB or Kernel refuse to boot with SATA disk connected.

[lolife.se]

The system boots off the chipset pri/ma IDE disk. The SATA disk is connected to a SiI3512 SATARaid PCI adapter. Right now, whenever I connect the SATA disk, GRUB finds and loads both the kernel and the initrd, and then absolutely *nothing*.

The system boots fine with the SATA adapter clean (no disks connected) so it doesn't seem to be a critical hardware error, right?

The same seem to happen in Annvix 3.0 (currently installed, kernel 2.6.22-something) and Ubuntu Gutsy (tried before, also kernel 2.6.2x-something I believe). Although I don't remember if the symptoms were the exact same, it *did* boot fine in Ubuntu Gusty, if you downgraded the kernel to Feisty kernel (~2.6.16-something I believe). Is something broken in the new kernels?

The system is a somewhat old Socket A (IWill KK266-R) system with a VIA KT133A chipset, and an AthlonXP 1600+ processor. The KT133A's are a bit quirky, yes, but it has been working perfectly fine before with Linux.

Anyone have any ideas, I'm at a complete loss here.

GRUB finds the hda disk where it wants it (hd0), the files it needs, aswell as read them OK. You can also access the SATA disk as (hd1) so the BIOS order seems OK. What happens after the initrd command? The kernel won't even start unzip.

Thankful for any help.

[lolife.se]

Here I've been trying for several days, and of course when I decide to post about it in forums, I find the solution short after.

Running the kernel with the edd=off option solved everything. Go figure.

[oz]

Ok, thanks for returning to share the solution with us, lolife.se!

Don't hesitate to start new threads should you have other questions.