Jump to content
Sign in to follow this  
Followers 0
iEzri

LSI 3ware 9550SX-8LP

2 posts in this topic

Recommended Posts

Hey there guys,

 

i got this LSI 3ware (Escalade) 9550SX(U)-8LP Controller here and i thought about tinkering around with it.

 

Because of the specs of the mainboard i am using, i am not yet sure if i can switch to a different controller card, also hey, i got this one here already... it'd be just awesome to be able to use it. For the moment i have the system running halfway smoothly and it will be still some days until my next task (the gfx card, also not that easy on this mobo...) is up, so i was wondering...

 

Has anyone tried this particular model?

Any chance on info, or that someone got it to work yet?

 

I've seen some threads regarding various alike cards, but then when following their steps it doesn't seem to be fruitful. What i have done so far is to try to get it to work was to look through various posts indicating that installing the codeset 9.5.3 in addition with the AMCC3ware9000.kext (or better said the AMCC3ware900064.kext) would do the trick as it is said that most of the ids are alike.

 

Oh, the id for this particular card is 13c1:1003

 

I'm not quite keen with all this to be honest, but then i tried out osx86 every now and then for some time and achieved most of my selfset goals, but this time it might be a little over my head...

 

So uhm, thanks for your input!

Share this post


Link to post
Share on other sites
Advertisement

I've had my 9650SE working before, to begin with I needed to have it boot in arch=i386 mode since I only had a 32bit driver, but then I got the 64.kext and it worked for 64bit boot up. I have just upgraded to mountain lion but I am having trouble getting the driver to work. Will let you know how I go.

The RAID seems to be working fine on ML, I hope its the same for your 9550SX card.

I just downloaded the Complete_codeset_Mac_9.5.4.iso off lsi.com .

Then I had to copy the setupMac.jar from the packages/installers onto my desktop then run:

sudo java -jar setupMac.jar

Everything then installed fine and I could access the local web admin site by clicking on the shortcut at "/opt/3ware/Connect to 3DM2.webarchive"

Goodluck! :)

Edited by benos

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  
Followers 0

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By valueimagery
      Okay So I have two PCIe controller cards, both 3rd party, unbranded from eBay.
       
      1st runs off the Marvell 88SE92xx chipset.  4 Internal Ports.
      https://www.ebay.com.au/itm/PCI-E-PCI-Express-to-SATA3-0-4Port-SATA-III-6G-Expansion-Controller-Card-Adapter/264029216955?ssPageName=STRK%3AMEBIDX%3AIT&_trksid=p2057872.m2749.l2649
       
      2nd runs off the ASMedia ASM1061 chipset. 2 Internal/ 2 External Ports (selectable by jumpers)
      https://www.ebay.com.au/itm/PCI-E-To-SATA3-PCI-E-SATA3-0-6Gb-s-the-SSD-Asmedia-Chip-Expansion-Card-ASM1061/191572577652?ssPageName=STRK%3AMEBIDX%3AIT&_trksid=p2057872.m2749.l2649
       
      The hack is running stable no issues on 10.4.2 with an i7 8700k ASUS Maximus X Code as iMac 18,3
       
      However, I wanted to add eSATA ports for some older drive enclosures I own, and some extra internal SATA ports as I've used all the SATA ports on the Motherboard.
      The 1st Marvell actually works OOB in Mac OSX.  No kexts needed.  Speeds seem good (350R/400W on an SSD 80R/W on a 5400 HDD)
       
      However, a few things don't seem perfect.
      1) the AHCI version is 1.0.  I imagine this could and should be a newer version? 1.2 or 1.31? If it should be updated, is this something only able to be flashed from a Windows OS?
      2) It can't be used as a boot option.  the Maximus doesn't recognise it as a startup option.  Is this a possible AHCI version firmware issue?  Is booting ever possible from these controllers? 
      3) TRIM was disabled in system profile. I know it automatically worked OOB for my NVME2 drives connected to the motherboard,  But to enable Trim on an SSD 860 EVO I needed to submit the terminal command:
      sudo trimforce enable
       
      Now the second ASMedia controller I haven't been able to get to work.  I've switched the jumpers (not sure which position is the 1,2,3) so I've made it so that one internal and one external will operate to test the card.
       
      System profiler sees the card like all the others as a "Generic AHCI Controller" with AHCI version 1.20 supported.
      However, I cannot get any drive to be recognised in the eSATA ports.  I haven't tested the internal ports as I don't need these.
       
      I've attempted using two kexts (attached) AHCI_3rdParty_eSATA.kext and AHCIPortInjector.kext
      When I use AHCIPortInjector.kext the SATA device is recognised in system profiler as an ASM1062.  However no drive works with this kext.  And reading the chip itself on the card it says ASM1061.  So not sure why it's preferring the 1062 entry over the 1061 since both are present in the kext.
       
      When I use AHCI_3rdParty_eSATA.kext that SATA device is not recognised at all in the system profiler.  It disappears.
       
      I'm not using a custom DSDT for this motherboard and I've attached my config.plist if anyone has some insight on either cards.
       
      Cheers,
      Shark
       
       
       
       
      config-NOSN.plist
      AHCI_3rdParty_eSATA.kext.zip
      AHCIPortInjector.kext.zip
    • By dukzcry
      Here's my driver for LSI MegaRAID SAS family of controllers called SASMegaRAID.kext. This one was requested few times at InsanelyMac and other Mac-related communities.
      Download link https://github.com/dukzcry/osx-goodies/releases or https://www.insanelymac.com/forum/files/file/306-sasmegaraidkext/
      F.A.Q.:
      Q: I can't manage controller via supplied utility
      A: Only monitoring functional is supported, management is done via controller BIOS
      Q: Any chance to make cards based on SAS2208 chip work?
      A: Not currently, the chip belongs to the same family, but it requires a lot of handling different from common handling for supported cards.
      Q: The driver loads but my device doesn't show up anywhere in profiler. What should I do?
      A: Try inverting "PreferMSI" key value. It's under "Settings" dictionary in kext's plist. 
      Q: macOS doesn't see my volumes
      A: Set them as virtual (logical) disks in controller's BIOS. If no luck try "Uncontiguous enumeration.zip" version. See full issue report https://www.insanelymac.com/forum/forums/topic/285197-driver-for-lsi-megaraid-sas-family/?do=findComment&comment=1987665
      Q: Is it possible to push more from my setup?
      A: It may be.
      The plist from "Unsafe settings unlocked.zip" allows tweaking of dangerous options. Before playing with them you need to detach all HDDs with critical data and attach some spare HDD for doing the tweaks. The "MaxSGL" option is number of scatter gather list entries you controller can handle. The "MaxTransferSize" determines the maximum size of data transfer (in bytes) per request your controller can catch. If you set them to some enormously big value then they will be truncated to the max values your hardware can achieve (may still be not safe enough for successful data transfers). "MaxTransferSizePerSegment" does the same but for a single SGL entry (will never be larger than MaxTransferSize). For the tests you need to stick to the system.log and start a transfer of a >= 100gb data. If the settings you set are inappropriate, you'll see the I/O errors.
      Q: My Mac stopped to go sleep after i've loaded your kext.
      A: This is awaited. See https://www.insanelymac.com/forum/forums/topic/285197-driver-for-lsi-megaraid-sas-family/?do=findComment&comment=1986269 Use kext from "Unsafe settings unlocked.zip" and set "AllowSleep" key to true.
      Q: Your driver doesn't work for me. Are there any alternatives?
      A: Yes there is one https://www.insanelymac.com/forum/forums/topic/314799-guide-z820-el-capitan-the-great-guide-sucess/?do=findComment&comment=2556863
      Q: I get "mfiutil: mfi_open: not such file or directory" error
      A: It maybe that unit number of you device is not 0 (which is default). Try the following:
      $ ls /dev/mfi?
      /dev/mfi2
      $ sudo mfiutil -u 2
    • By b31k
      Hello
      My system is
      Asus Z170-P Motherboard
      i5 6600K Processor
      NVIDIA GeForce GTX 1050 Ti 4095 MB
      Be-quiet 500W PSU
      Crucial 16 GB 2400 MHz DDR4

      BIOS:

      xHCI Handoff enable
      Serial Port disable
      SATA AHCI mode
      IOAPIC 24-119 Entries (enable y disable) two mode stuck

      I can not build a robust and stable system, The system Sierra is already installed but when I restart or shut down, I get the error Still waiting for root device error, but after too many reboot ( from 2 times to 9) start correctly or other times leave too minutes, with prohibited symbol and finally starts.
      Once started recognised correctly HDD.
      Also I tried with a new  EVO860 nvme SSD , but I have the same problem.
       
       
      I dont know because sometimes yes sometimes no, the system stuck in this error
      I add some information files and logs.
       
      sudo touch /System/Library/Extensions && sudo kextcache -u /
      kext-dev-mode allowing invalid signature -67030 0xFFFFFFFFFFFEFA2A for kext HackrNVMeFamily-10_12_6.kext
      kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext FakeSMC.kext
      kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext BrcmPatchRAM2.kext
      kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext BrcmFirmwareRepo.kext
        thank you.


       
      Solution by Rehabman;

      Extracting my native/clean DSDT using Clover F4.
      and check with diff DSDT file.

      My SystemMemory addresses in DSDT are mismatched:

      SPEEDY-NUCatched rehabman$ diff ../origin/ ../patched/|grep SystemMemory
      < OperationRegion (GNVS, SystemMemory, 0xC74EC000, 0x06D5)
      > OperationRegion (GNVS, SystemMemory, 0xC74FE000, 0x06D5)
      < OperationRegion (CPSB, SystemMemory, 0xC6CC0F98, 0x10)
      > OperationRegion (CPSB, SystemMemory, 0xC6CD2F98, 0x10)

      and other mistake in OperationRegion(PNVA,SystemMemory,PNVB,PNVL)

      < Name (PNVB, 0xC74F1018)
      > Name(PNVB,0xC7503018)

      My system after too many month , keep stable the still waiting error no appear again, it seems that the problem was with the memory addresses in my DSDT.
×