First time poster here.
I'm trying to install a SYBA SD-PEX40054 SATA PCIe card into my motherbard Gigabyte Z87X-UD7-TH.
The PCIe card has 4 SATA ports controlled by a Marvell 88SE9230 chipset.
The motherboard also has 4 ports controlled by the same chipset, along with 6 other Intel-controlled ports.
When the PCIe card is inserted in a slot (I've tried 3 different slots), the boot sequence first goes through the bios of the card (ctrl-M to setup RAID function) and then lands on the splash screen of the motherboard bios where it just hangs. Can't call up boot priority (F12) or the bios menu (DEL) or anything. It just apparently hangs there.
When I unplug the card, enter Gigabyte bios, turn off the Marvell SATA controller, and reboot with the card in, I can successfully get to my OS, see the drives attached to the card, but I lose the 4 internal Marvell ports.
So there is some kind of conflict going on here between the two Marell 9230s that I can't seem to troubleshoot, and it seems to be irrelevant to the OS.
Would anyone here have any experience troubleshooting something like this?
Thank you!
I'm trying to install a SYBA SD-PEX40054 SATA PCIe card into my motherbard Gigabyte Z87X-UD7-TH.
The PCIe card has 4 SATA ports controlled by a Marvell 88SE9230 chipset.
The motherboard also has 4 ports controlled by the same chipset, along with 6 other Intel-controlled ports.
When the PCIe card is inserted in a slot (I've tried 3 different slots), the boot sequence first goes through the bios of the card (ctrl-M to setup RAID function) and then lands on the splash screen of the motherboard bios where it just hangs. Can't call up boot priority (F12) or the bios menu (DEL) or anything. It just apparently hangs there.
When I unplug the card, enter Gigabyte bios, turn off the Marvell SATA controller, and reboot with the card in, I can successfully get to my OS, see the drives attached to the card, but I lose the 4 internal Marvell ports.
So there is some kind of conflict going on here between the two Marell 9230s that I can't seem to troubleshoot, and it seems to be irrelevant to the OS.
Would anyone here have any experience troubleshooting something like this?
Thank you!