Contribute
Register

How to show Z77 correctly in system profiler

Status
Not open for further replies.
todesto

todesto

Joined
Jun 20, 2011
Messages
141
Motherboard
ASUS P8Z77-V LK
CPU
i5-3570K
Graphics
HD6870
Mac
  1. iMac
  2. MacBook Air
  3. MacBook Pro
  4. Mac Pro
Mobile Phone
  1. iOS
Hoping to contribute as I get tons of info from here.

I don't know if it applies to other Z77 series board but at least it worked for me.

I have GA-Z77-DS3H and know many of users with this board SATA controller is shown as unknown AHCI controller.
I know it is purely cosmetic but I wanted to show this correctly.

After running bridgehelper 5.0, my SATA controller showed correctly shown as "intel7series AHCI controller"

After Mountain Lion release, I thought ML would have info for Z series chipset but it didn't as it changed back showing unknown ACHI controller. :(

after doing small research and comparison with Lion kext, I learned by adding a string, it displays correct name!

So it turns out adding

<string>pci8086,1e02</string>
to Intel7SeriesAHCI in S/L/E/AppleAHCIport.kext (show package, then edit info.plist) is the answer.

I have attached edited AppleAHCIport.kext so you can just use kextbeast, run permission, then reboot and it should show correctly.

If your SATA controller shows a name already with Mountain Lion, you don't have to use this.

Anyway, I hope some of you have a use for this.
 

Attachments

  • intel_7_series_ahci-1.jpg
    intel_7_series_ahci-1.jpg
    66.2 KB · Views: 2,026
  • AppleAHCIPort.kext.zip
    54.8 KB · Views: 946
Thanks for the kext! I also see you have the identical setup as me! I am having a heck of a time getting Mountain Lion to boot without KP. Lion worked perfect! Could you please post what you selected in multi beast? No matter what I select I get KP thanks!!!
 
not identical

I have DS3H, you have UD3H. lol

are clean installing it?
if so, my advise is select userDSDT (without DSDT) only and reboot to see if you can boot first. dont select any other kext yet.
if reboot with ML installed hard successfully then install needed kext after.

I had hard time installing Lion as I was getting KP and learned to install like that.

BTW I upgraded from Lion to ML so I really didnt have any problem.
 
z77-ds3h

Thanks mate worked great for me :)
 
KP?
The kext only has one extra string in there. Maybe you should run Kext Wizard for permission before reboot. My kext has been working for many others without a problem.
 
todesto said:
KP?
The kext only has one extra string in there. Maybe you should run Kext Wizard for permission before reboot. My kext has been working for many others without a problem.
Click to expand...

Yes. I did run Kext Wizard. We might have different AppleAHCIport.kext files?
 
The kext is original 10.8 version and I only added the string.
What board do you have?

Never mind, I see in your profile.
 
I don't think it's a good idea to modify a standard apple kext just to do a device injection. Much cleaner just to create a simple injector kext. That way, even if apple updates AppleAHCIPort.kext, the devices will still show up correctly.

Here's how to create a device injector:
  1. Create a folder on your desktop called "AHCISeries7Injector"
  2. In AHCISeries7Injector folder, create a subfolder called "Contents"
  3. Create a new file with the text specified below and save it as "Info.plist" inside the Contents folder
  4. Rename the "AHCISeries7Injector" folder to "AHCISeries7Injector.kext"
  5. The folder icon will change to a kernel extension icon
  6. Use Kext Wizard to install the AHCISeries7Injector.kext
  7. Reboot

If you previously modified your original AppleAHCIPort.kext, you'll want to revert back to the original (you made a backup, didn't you?)

Contents of Info.plist:
Code: 
<?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>CFBundleDevelopmentRegion</key>
    <string>English</string>
    <key>CFBundleIdentifier</key>
    <string>com.corknation.driver.AHCISeries7Injector</string>
    <key>CFBundleInfoDictionaryVersion</key>
    <string>6.0</string>
    <key>CFBundleName</key>
    <string>AHCISeries7Injector Fix</string>
    <key>CFBundlePackageType</key>
    <string>KEXT</string>
    <key>CFBundleSignature</key>
    <string>????</string>
    <key>CFBundleVersion</key>
    <string>1.0.0</string>
    <key>IOKitPersonalities</key>
    <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>
            </array>
            <key>IOProbeScore</key>
            <integer>2000</integer>
            <key>IOProviderClass</key>
            <string>IOPCIDevice</string>
            <key>Vendor Name</key>
            <string>Intel</string>
        </dict>
    </dict>
    <key>OSBundleRequired</key>
    <string>Local-Root</string>
</dict>
</plist>

For those people that would rather just download a file instead of learning how these things actually work, here's a LINK
 
Thanks for the info.
So if you run this injector kext, does it add that new string into AppleAHCIport kext or does it replace the whole info.plist with what you wrote?
I'd like to know before trying this.
 
todesto said:
Thanks for the info.
So if you run this injector kext, does it add that new string into AppleAHCIport kext or does it replace the whole info.plist with what you wrote?
I'd like to know before trying this.
Click to expand...

It adds a new IOKit Personality, which is just a means by which hardware can be matched to a driver (https://developer.apple.com/library...tual/IOKitFundamentals/Matching/Matching.html) . It doesn't replace anything within the AppleAHCIPort kernel extension, which is why i like this type of modification. It leaves the standard Apple kernel extensions alone. Also, when Apple updates these extensions in a future update (like 10.8.1), you won't have to repatch anything.

If you're using a DSDT, you can also inject the correct device id in the DSDT and not need any kernel extension changes.
 
Status
Not open for further replies.
Copyright © 2010 - 2024 tonymacx86 LLC
Back
Top