Contribute
Register

[Solved] SATA controller conflict: Z87X-UD7-TH & Marvel 88SE9230 SATA PCIe card

Status
Not open for further replies.
Joined
Feb 3, 2011
Messages
41
Motherboard
Gigabyte GA-Z87X-UD7 TH
CPU
i7-4770K
Graphics
GTX 760
Mac
  1. MacBook Pro
Classic Mac
  1. Apple
  2. Power Mac
  3. SE
Mobile Phone
  1. iOS
[EDIT: See next post]

I just installed an old Syba SD-PEX40054 PCIe SATA card to try and get some more drives up and running in my rig:

GA-Z87X-UD7-TH running 10.11.6 with Clover.
I believe the card uses the Marvell 88SE9230 Chipset.

On boot, I notice the Gigabyte splash screen flashes up for a second, then the Marvell BIOS splash screen shows the attached drives, and then it goes back to the Gigabyte splash screen where it apparently hangs. I can't seem to do anything - even get into the Gigabyte BIOS.

Clearly a card issue, as it doesn't happen when I pull out the card.

I've tried futzing with the "Other PCI Device ROM Priority" setting to 'Legacy' but no joy.

I've also tried installing the AHCI_3rdParty_SATA.kext in various locations to see if that was the cause, but no joy.

Does anyone have any ideas on how to get this card working?

Thanks in advance!
 
Last edited:
Okay, I've narrowed it down to the Marvel SE889230 Chipset.

As my motherboard has 4 SATA ports that are run with this chipset, there seems to be some kind of conflict.

If I disable the Marvel SATA controller in the MB bios, the rig boots fine and I see drives that are attached to the card. But then I lose the drives connected to the Marvell ports on the motherboard.

Is there any way to get both the ports on the card and the ports on the board to work? Does anybody have experience troubleshooting this kind of chipset conflict?
 
Is the BIOS on both Marvell 88SE9230 controllers enabled? That *might* be where the conflict lies, I've run into a situation in the past where you could have only one controller with an enabled BIOS. Now I'm not sure how you would go about disabling the BIOS on one, but it's a place to start.

This is a long shot, but I found a reference to CPU virtualization interfering with some Marvell chips, so if you have virtualization enabled in your BIOS you might try disabling it (reference: http://lime-technology.com/forum/index.php?topic=43109.0).
 
SOLVED!!

In case anyone stumbles across this needing an answer:

Following info in this thread, I finally was able to create a USB boot drive using Rufus, and using the installed DOS, flashed the firmware of the card to 2.3.0.1058

No more weird, excruciatingly long boot times - yay!
 
how do you load the driver?
 
Status
Not open for further replies.
Back
Top