Jump to content

27 posts in this topic

Recommended Posts

I have started testing Mavericks DP1 and installed it on spare USB drive. 

Specs:

Supermicro X8DAE

Dual Xeon 5530

Nvidia GTX 570

24GB RAM

 

From Mountain Lion installation I already know that this motherboard won't work properly W/O replacing AppleACPIPlatform and IOPCIFamily kexts (freezing etc.). So, I have installed as usual with -x, installation went smoothly, but when I replace those two kexts and reboot all my HDDs are missing.

In verbose mode I see that com.apple.driver.AHCIPort has failed to load because of some error ..... I suppose that we'll need updated AppleACPIPlatform and IOPCIFamily kexts for Mavericks?

Share this post


Link to post
Share on other sites
Advertisement

No, drives are there before I replace two kexts. After that they are gone.

I've Googled the issue and I found that couple of guys have the same problem, so this is not isolated case.

Share this post


Link to post
Share on other sites

Maybe theres' a way to fix the issues in DSDT so you don't have to replace kexts. If it works ok but crashes after a while maybe there is a hardware conflict somewhere.

You can try disabling as much on board hardware as possible in the BIOS and removing expansion cards as well. If it works better with less hw in use maybe you'll be able to pinpoint where the conflict is.

 

IORegistryExplorer (comes with xcode dev tools) is useful for tracking down IRQ conflicts. By expanding each device in the tree, you can see which IRQ(s) it sits on. On most motherboards, a handful of IRQs are hardcoded for the HPET and other devices. You can remove these and let OS X distribute the IRQs the way it wants, this can help sometimes. You can also do the opposite, force an IRQ for a specific device.

 

I know "IRQ conflicts" sounds like something from the Windows 95 era but it does happen.

I believe this practice was first documented by THe KiNG here: http://www.projectosx.com/forum/index.php?showtopic=564

Share this post


Link to post
Share on other sites

ACHI set in the BIOS? 

Yes, AHCI is set in BIOS but after replacing AppleACPIPlatform and IOPCIFamily kexts, com.apple.driver.AHCIPort won't load.  Safe boot with original kexts work fine and all drives are there. It will even boot regularly but it is painfully slow and unusable (I had same issue after ML)

I suppose that something has to be modified in added kexts, in order to load AHCIPort driver.

 

Maybe theres' a way to fix the issues in DSDT so you don't have to replace kexts. If it works ok but crashes after a while maybe there is a hardware conflict somewhere.

You can try disabling as much on board hardware as possible in the BIOS and removing expansion cards as well. If it works better with less hw in use maybe you'll be able to pinpoint where the conflict is.

 

I suppose that issue can be fixed in DSDT but I have already went through drill with ML .... removing hardware, turning off one CPU, removing HDDs, changing GPUs, multiple BIOS variations - always the same result (extremely slow performance, but W/O crash). At the end only old AppleACPIPlatform and IOPCIFamily kexts (from Netkas) solved the problem.

I have also tried checking IRQ conflicts, and although I know how to fix some things with DSDT (CPU alias, add GPU, orange icon fix, RTC fix, etc.), it is still above my knowledge after all this years :( Anyway I will see how to remove IRQs because I haven't tried that yet.

 

Thank you for your help guys.

Share this post


Link to post
Share on other sites

 

Here is unmodified DSDT and IOreg.

I have updated to DP2 and the problem is still the same.

 

Thank you @Rampage Dev

 

This DSDT has been edited... 

Share this post


Link to post
Share on other sites

I was sure that's raw DSDT extracted on Windows couple months ago when motherboard arrived (I usually do that first on new MB).

Anyway I have booted clean MountainLion and extracted new DSDT.

NEWdsdt.zip

Share this post


Link to post
Share on other sites

I was sure that's raw DSDT extracted on Windows couple months ago when motherboard arrived (I usually do that first on new MB).

Anyway I have booted clean MountainLion and extracted new DSDT.

Install this DSDT and then get a new IOreg with the app here:

 

http://rampagedev.wordpress.com/guides/how-to-use-ioreg/

 

 

DSDT.aml.zip

Share this post


Link to post
Share on other sites

Update:

I have tried removing IRQs from DSDT as in The KiNG's post mentioned above, but the problem is still there.

However I have managed to fix "missing HDDs" issue by using AppleAHCIPort.kext from 10.8.4. It is now loading properly and all HDDs are mounted (Mavericks DP2). Of course this is not perfect solution and we'll need updated IOPCIFamily.kext that will work properly with Mavericks (I see that a lot of people are using IOPCIFamily.kext from Netkas in their ML installations).

Share this post


Link to post
Share on other sites

Same problem with my Dell optiplex 755 cpu core2 E8500 3.16ghz / 8gig of ram /  geforce gt 610 2gig  

this configuration works perfect on ML .

 

I try  to  using AppleAHCIPort.kext from 10.8.4. and no disk  appears ??

Share this post


Link to post
Share on other sites

Same problem with my Dell optiplex 755 cpu core2 E8500 3.16ghz / 8gig of ram /  geforce gt 610 2gig  

this configuration works perfect on ML .

 

I try  to  using AppleAHCIPort.kext from 10.8.4. and no disk  appears ??

Try using this combination of kexts (attached).

kexts.zip

Share this post


Link to post
Share on other sites

Strange, it should work. Have you installed kexts with Kexthelper (S/L/E)? What does it say in verbose mode (com.apple.driver.AHCIPort has failed to load ... or something)? Do you see the drives in safe mode? 


Share this post


Link to post
Share on other sites

Hi sampledi: :)  this is what append when I change the kext I used kexwizard to injected the 3 kext ;

everytime I try to change the kext on S/L/E  I recive this kernel panicoptipl10.jpg

Share this post


Link to post
Share on other sites

Hi,

 

I had the problem of missing SATA hard drives with 10.9 on a Dell Precision 690 which uses an ESB2 SATA controller.  This runs ML very well but on my initial installation attempt with 10.9 DP1 Disk Utility would see no SATA hard drives.  I did manage a successful installation of 10.9 DP1 onto  a USB HDD and also using the onboard LSI SATA/SAS chipset after modifying AppleLSIFusionMPT.kext.

 

Looking with IORegistryExplorer, AppleAHCIPort.kext would attach to the ESB2 SATA but never show any disks.

 

Upgrading to DP2 made no difference, and I spent a while adding "compatible" and "name" flags to the ESB2 SATA entry in my DSDT but to no effect.  Rolling back to the 10.8.4 AppleAHCIPort.kext also didn't help.

 

Upon upgrading to DP3 suddenly the ESB2 HDDs became visible exactly as in ML.  Thus I think that this is probably the consequence of a bug in DP1 and DP2 which Apple have fixed in DP3.

 

I would suggest that anyone with this problem installs on USB and upgrades to DP3 or beyond.  Their SATA drives should then appear and it should be possible to clone the 10.9 installation across.

 

Good Luck,

Share this post


Link to post
Share on other sites

 

 

Hi,

 

I had the problem of missing SATA hard drives with 10.9 on a Dell Precision 690 which uses an ESB2 SATA controller.  This runs ML very well but on my initial installation attempt with 10.9 DP1 Disk Utility would see no SATA hard drives.  I did manage a successful installation of 10.9 DP1 onto  a USB HDD and also using the onboard LSI SATA/SAS chipset after modifying AppleLSIFusionMPT.kext.

 

Looking with IORegistryExplorer, AppleAHCIPort.kext would attach to the ESB2 SATA but never show any disks.

 

Upgrading to DP2 made no difference, and I spent a while adding "compatible" and "name" flags to the ESB2 SATA entry in my DSDT but to no effect.  Rolling back to the 10.8.4 AppleAHCIPort.kext also didn't help.

 

Upon upgrading to DP3 suddenly the ESB2 HDDs became visible exactly as in ML.  Thus I think that this is probably the consequence of a bug in DP1 and DP2 which Apple have fixed in DP3.

 

I would suggest that anyone with this problem installs on USB and upgrades to DP3 or beyond.  Their SATA drives should then appear and it should be possible to clone the 10.9 installation across.

 

Good Luck,

thanks to respond :) I verifie inside the AppleAHCIPort.kext/info.plist (DP1,DP2 AND DP3) ;its a same for the chipset ICH, dont integrated  the ICH9RAHCI

only the ICH8MAHCI :(  :blush:

 

Have look 

 

 

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>BuildMachineOSBuild</key>
<string>13A509</string>
<key>CFBundleDevelopmentRegion</key>
<string>English</string>
<key>CFBundleExecutable</key>
<string>AppleAHCIPort</string>
<key>CFBundleGetInfoString</key>
<string>Version 2.8.5, Copyright 2005-2013, Apple Inc.</string>
<key>CFBundleIdentifier</key>
<string>com.apple.driver.AppleAHCIPort</string>
<key>CFBundleInfoDictionaryVersion</key>
<string>6.0</string>
<key>CFBundleName</key>
<string>AppleAHCI</string>
<key>CFBundlePackageType</key>
<string>KEXT</string>
<key>CFBundleShortVersionString</key>
<string>2.8.5</string>
<key>CFBundleSignature</key>
<string>????</string>
<key>CFBundleVersion</key>
<string>2.8.5</string>
<key>DTCompiler</key>
<string>com.apple.compilers.llvm.clang.1_0</string>
<key>DTPlatformBuild</key>
<string>5A11314p</string>
<key>DTPlatformVersion</key>
<string>GM</string>
<key>DTSDKBuild</key>
<string>13A509</string>
<key>DTSDKName</key>
<string></string>
<key>DTXcode</key>
<string>0500</string>
<key>DTXcodeBuild</key>
<string>5A11314p</string>
<key>IOKitPersonalities</key>
<dict>
<key>GenericAHCI</key>
<dict>
<key>CFBundleIdentifier</key>
<string>com.apple.driver.AppleAHCIPort</string>
<key>Chipset Name</key>
<string>AHCI Controller</string>
<key>IOClass</key>
<string>AppleAHCI</string>
<key>IOPCIClassMatch</key>
<string>0x01060100&0xffffff00</string>
<key>IOPCIPauseCompatible</key>
<true/>
<key>IOPCITunnelCompatible</key>
<true/>
<key>IOProbeScore</key>
<integer>800</integer>
<key>IOProviderClass</key>
<string>IOPCIDevice</string>
<key>Vendor Name</key>
<string>Generic</string>
</dict>
<key>ICH10AHCI</key>
<dict>
<key>CFBundleIdentifier</key>
<string>com.apple.driver.AppleAHCIPort</string>
<key>Chipset Name</key>
<string>ICH10 AHCI</string>
<key>IOClass</key>
<string>AppleAHCI</string>
<key>IOPCIPrimaryMatch</key>
<string>0x3a228086</string>
<key>IOProbeScore</key>
<integer>2000</integer>
<key>IOProviderClass</key>
<string>IOPCIDevice</string>
<key>Vendor Name</key>
<string>Intel</string>
</dict>
<key>ICH6 ESB2 AHCI</key>
<dict>
<key>CFBundleIdentifier</key>
<string>com.apple.driver.AppleAHCIPort</string>
<key>Chipset Name</key>
<string>ESB2 AHCI</string>
<key>IOClass</key>
<string>AppleAHCI</string>
<key>IOPCIPrimaryMatch</key>
<string>0x26818086</string>
<key>IOProbeScore</key>
<integer>2000</integer>
<key>IOProviderClass</key>
<string>IOPCIDevice</string>
<key>Vendor Name</key>
<string>Intel</string>
</dict>
<key>ICH7MAHCI</key>
<dict>
<key>CFBundleIdentifier</key>
<string>com.apple.driver.AppleAHCIPort</string>
<key>Chipset Name</key>
<string>ICH7-M AHCI</string>
<key>IOClass</key>
<string>AppleAHCI</string>
<key>IOPCIPrimaryMatch</key>
<string>0x27c58086</string>
<key>IOProbeScore</key>
<integer>2000</integer>
<key>IOProviderClass</key>
<string>IOPCIDevice</string>
<key>Vendor Name</key>
<string>Intel</string>
</dict>
<key>ICH8MAHCI</key>
<dict>
<key>CFBundleIdentifier</key>
<string>com.apple.driver.AppleAHCIPort</string>
<key>Chipset Name</key>
<string>ICH8-M AHCI</string>
<key>IOClass</key>
<string>AppleICH8AHCI</string>
<key>IOPCIPrimaryMatch</key>
<string>0x28298086</string>
<key>IOProbeScore</key>
<integer>2000</integer>
<key>IOProviderClass</key>
<string>IOPCIDevice</string>
<key>Vendor Name</key>
<string>Intel</string>
</dict>
<key>Intel5SeriesAHCI</key>
<dict>
<key>CFBundleIdentifier</key>
<string>com.apple.driver.AppleAHCIPort</string>
<key>Chipset Name</key>
<string>5 Series Chipset</string>
<key>IOClass</key>
<string>AppleIntelPchSeriesAHCI</string>
<key>IONameMatch</key>
<array>
<string>pci8086,3b29</string>
<string>pci8086,3b22</string>
<string>pci8086,3b2f</string>
</array>
<key>IOProbeScore</key>
<integer>2000</integer>
<key>IOProviderClass</key>
<string>IOPCIDevice</string>
<key>Vendor Name</key>
<string>Intel</string>
</dict>
<key>Intel6SeriesAHCI</key>
<dict>
<key>CFBundleIdentifier</key>
<string>com.apple.driver.AppleAHCIPort</string>
<key>Chipset Name</key>
<string>6 Series Chipset</string>
<key>IOClass</key>
<string>AppleIntelPchSeriesAHCI</string>
<key>IONameMatch</key>
<array>
<string>pci8086,1c02</string>
<string>pci8086,1c03</string>
</array>
<key>IOProbeScore</key>
<integer>2000</integer>
<key>IOProviderClass</key>
<string>IOPCIDevice</string>
<key>Vendor Name</key>
<string>Intel</string>
</dict>
<key>Intel7SeriesAHCI</key>
<dict>
<key>CFBundleIdentifier</key>
<string>com.apple.driver.AppleAHCIPort</string>
<key>Chipset Name</key>
<string>7 Series Chipset</string>
<key>IOClass</key>
<string>AppleIntelPchSeriesAHCI</string>
<key>IONameMatch</key>
<array>
<string>pci8086,1e02</string>
<string>pci8086,1e03</string>
</array>
<key>IOProbeScore</key>
<integer>2000</integer>
<key>IOProviderClass</key>
<string>IOPCIDevice</string>
<key>Vendor Name</key>
<string>Intel</string>
</dict>
<key>Intel8SeriesAHCI</key>
<dict>
<key>CFBundleIdentifier</key>
<string>com.apple.driver.AppleAHCIPort</string>
<key>Chipset Name</key>
<string>8 Series Chipset</string>
<key>IOClass</key>
<string>AppleIntelPchSeriesAHCI</string>
<key>IONameMatch</key>
<array>
<string>pci8086,1d02</string>
<string>pci8086,9c03</string>
<string>pci8086,8c02</string>
<string>pci8086,8c03</string>
</array>
<key>IOProbeScore</key>
<integer>2000</integer>
<key>IOProviderClass</key>
<string>IOPCIDevice</string>
<key>Vendor Name</key>
<string>Intel</string>
</dict>
<key>MCP79AHCI</key>
<dict>
<key>CFBundleIdentifier</key>
<string>com.apple.driver.AppleAHCIPort</string>
<key>Chipset Name</key>
<string>MCP79 AHCI</string>
<key>IOClass</key>
<string>AppleMCP79AHCI</string>
<key>IOPCIPrimaryMatch</key>
<string>0x0ab910de</string>
<key>IOProbeScore</key>
<integer>2000</integer>
<key>IOProviderClass</key>
<string>IOPCIDevice</string>
<key>Vendor Name</key>
<string>NVidia</string>
</dict>
<key>MCP89AHCI</key>
<dict>
<key>CFBundleIdentifier</key>
<string>com.apple.driver.AppleAHCIPort</string>
<key>Chipset Name</key>
<string>MCP89 AHCI</string>
<key>IOClass</key>
<string>AppleMCP89AHCI</string>
<key>IOPCIPrimaryMatch</key>
<string>0x0d8810de</string>
<key>IOProbeScore</key>
<integer>2000</integer>
<key>IOProviderClass</key>
<string>IOPCIDevice</string>
<key>Vendor Name</key>
<string>NVidia</string>
</dict>
</dict>
<key>OSBundleLibraries</key>
<dict>
<key>com.apple.iokit.IOAHCIFamily</key>
<string>1.0.0</string>
<key>com.apple.iokit.IOPCIFamily</key>
<string>1.0.0</string>
<key>com.apple.kpi.bsd</key>
<string>8.0.0</string>
<key>com.apple.kpi.iokit</key>
<string>8.0.0</string>
<key>com.apple.kpi.libkern</key>
<string>8.0.0</string>
<key>com.apple.kpi.mach</key>
<string>8.0.0</string>
</dict>
<key>OSBundleRequired</key>
<string>Local-Root</string>
</dict>
</plist>
 

and see on ML  about this mac 

 

 

212.png112.png
 

My question now is how to injected this chipset 

ICH9RAHCI :P  B)

 

Share this post


Link to post
Share on other sites

Shouldn't the Generic AHCI entry match on class code here?

 

System Profiler detail is often largely cosmetic, although there are SATA injector .kexts for specific chipsets.  In this same Dell Precision 690 I have a Marvell eSATA card which is normally picked up as GenericAHCI but I've injected correct details into a legacy .kext residing in /S/L/E:

 

<key>Marvell 88SE9123</key>
        <dict>
            <key>CFBundleIdentifier</key>
            <string>com.apple.driver.AppleAHCIPort</string>
            <key>Chipset Name</key>
            <string>88SE9123</string>
            <key>IOClass</key>
            <string>AppleAHCI</string>
            <key>IOPCIClassMatch</key>
            <string>0x01060100&0xffffff00</string>
            <key>IOPCIPrimaryMatch</key>
            <string>0x91231b4b</string>
            <key>IOProbeScore</key>
            <integer>15000</integer>
            <key>IOProviderClass</key>
            <string>IOPCIDevice</string>
            <key>Vendor Name</key>
            <string>Marvell</string>
        </dict>
 

I think I'm right in saying that the Info.plist in DP3 AppleAHCIPort.kext and that for DP2 and earlier are identical, however my suspicion is that the binaries may not be - unless the difference is somewhere else in the AHCI disk chain.

 

I no longer have DP2 or DP1 installed to diff and check.

Share this post


Link to post
Share on other sites

yes Iam verifie to my dp3 instalation  hp probook 4530s  and the AppleAHCIPort.kext its same on bolt 10.9  DP  ^_^ 


ok now Iam try to install on EXT hdd  and  after I update to DP 3  do you think when I am plug inside de Dell optiplex 755,  its work ???  :D  B)

Share this post


Link to post
Share on other sites

 

ok now Iam try to install on EXT hdd  and  after I update to DP 3  do you think when I am plug inside de Dell optiplex 755,  its work ???  :D  B)

 

It should do, at least if my experience is anything to go by.  Good Luck

Share this post


Link to post
Share on other sites

It should do, at least if my experience is anything to go by.  Good Luck

look a that  :thumbsup_anim:  :D  :P sans_t10.jpg

 

 

 

   

 I HAVE install the 10.8.4 kext  / IOPCIFamily.kext  / IOAHCIFamily.kext/ AppleAHCIPort.kext/ :thumbsup_anim:  :whistle:  :whistle:  :hysterical:  :yoji:  :moil:

for now AM ok with this 

 

thank you very mutch for your help  pharillion and sampledi :D  B)

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

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By tragediana150
      Hi everyone!
      Long time no see guys!
      As you can see I am not new user of Insanely and do not want to post in incorrect section, but I can not find any similiar topic at all. I,ve searched the forum and the web and I can't find a solution.
      My question is that is there any possibility to install Mavericks 10.9.5 on external drive on the newest Macbook Pro 13 from 2018? I know that the Intel Coffee Lake is new generation of CPU's and there is no drivers in Mavericks system to run this CPU, but I was thinking about it alot and I decided to write here. Because if we can install all the newest OSX, macOS on older machines then maybe we can install older systems on newer builds?
       
      P.S. If I wrote in incorrect topic then please move this thread to the right section, I will be grateful
    • By dannymozzer_
      Hi,
       
      I've been trying to install Mavericks 10.9, I know it's older now, but It's honestly the version I want to use, the specs of the PC are:
      Asus P8H61-MX USB3
      i3-3220
      8GB DDR3 Memory
      GTX 750 ti
      500GB HDD
       
      I've been following this guide: https://www.insanelymac.com/forum/topic/280756-guide-the-all-in-one-guide-to-vanilla-os-x-including-chameleon-dsdt-for-beginners-updated-for-yosemite/
      But, after booting, this is the error screen I get, any guidance on what Kexts, SMBios settings, etc. I need? I can tell I'm probably missing something here.

      Thanks,
      Dan
    • By vin047
      I have a Kingston HyperX Predator PCIE-SSD (model: SHPM2280P2H) matched with an X58 motherboard (legacy bios). The card has a Marvell 88SS9293 controller with an Option ROM which allows it to be detected on my motherboard as a bootable drive - listed as "IDE: Kingston SHPM". As my BIOS is non-UEFI, I assume the Option ROM presents it in IDE mode instead of AHCI.
       
      I use Clover legacy with BiosBlockIO to get around this, and it works well - Clover detects my drive and allows me to install macOS onto it and use it as a boot drive. macOS detects the drive correctly as a SATA AHCI drive. I guess Clover correctly detects (configures?) the Option ROM into AHCI mode and presents it as such to macOS - getting full speed read Read/Write performance. All is well.
       
      Except waking from sleep. When waking from sleep, depending on clover config options + dsdt, I either get an immediate reboot or hang on black screen that requires hard reset. I eventually realised that nothing after entering sleep mode is recorded in the logs, its completely empty until next boot up. This makes me think that on resume from sleep, macOS isn't seeing the drive anymore (hence can't even write to logs). My assumption here is that the Option ROM is presenting/configuring the card in IDE mode, which is not what macOS is expecting.
       
      This post describes the problem: 
       
      and also has a solution: in dsdt, simply write the correct values to 0x40, 0x41, 0x42 (which must be the BAR0 register?) to configure Option ROM to use AHCI mode. But I have no idea what address BAR0 is on the Marvell 88SS9293 - there appears to be no documentation whatsoever on this controller available online!
       
      I managed to dump the ROM using Linux sysfs, but don't have the skills to disassemble/decipher the binary to find the correct addresses. Anyone with such experience able to help?? I've attached the ROM dump and lspci output.
       
      Thanks in advance!
      rom.bin
      lspci_output.txt
    • By PixelLover
      I'm in the middle of my first hackintosh (High Sierra) on my ZenBook Pro UX501VW-US71 laptop using the Vanilla Install. I've tried using different config.plst files and I've gotten the furthest with RehabMan's own (linked here). It hangs at error message IOConsoleUsers: gIOScreenLockState 3, hs 0, bs 0, now 0, sm 0x0.   Can anyone help me figure out what changes to make to the config.plst file for my specific laptop (which is where I assume the problem lies)   System Specs: Intel Skylake Core i7­-6700HQ 2.6 GHz Quad­core
      Intel® HD Graphics 530 Nvidia GTX 960M 2G 15.6" Touch IPS 4K Ultra­-HD display, 3840 x 2160 resolution   Kexts: AppleALC.kext FakeSMC.kext Lilu.kext USBInjectAll.kext WhateverGreen.kext  
×