I could not load FC2 or FC3 on this machine because the atp870u.o module in early 2.6 kernels for some reason did not see the hard drive with the FC1 install, that was attached to this card.
Now, I tried to boot FC4's installer on this box, and lo-and-behold, atp870u.o has been fixed (my thanks to the whoever is the nameless soul that fixed this module), but there's now an anaconda-specific issue.
FC1's anaconda loaded aic7xxx first, then atp870u. That matched the order the cards are initialized by BIOS at power-on. aic7xxx's boot drive was /dev/sda, and atp870u's hard drive, with FC1, was /dev/sdb, as it should.
But now, FC4's anaconda loads atp870u's first, then aic7xxx; with the end result is that the drives mappings are reversed, sda swapped places with sdb.
What's the magic voodoo incantation to get FC4's anaconda to load aic7xxx first, then atp870u? I'm using the ol' "use-grub-to-load-pxeboot" trick to start the installer.
Attachment:
pgpwvHsJGrM4i.pgp
Description: PGP signature
