Contribute
Register

ASUS N56V - Hackintosh Yes or No?

Status
Not open for further replies.
I tried changing the SecureBootModel, but that did not help. I also removed the -wegnoegpu argument, but it didn't solve it either. I reverted those changes and am stuck here. Files attached too.
IMG_0525.jpg
 

Attachments

  • OC.zip
    2.3 MB · Views: 52
SPKNout4CHRIST said:
I tried changing the SecureBootModel, but that did not help. I also removed the -wegnoegpu argument, but it didn't solve it either. I reverted those changes and am stuck here. Files attached too.
View attachment 495005
Click to expand...
what is the make and model of your hard drive/nvme?
 
SPKNout4CHRIST said:
It is a WDC WD5000BPVX-00JC3T0
Click to expand...
should be ok

also noticed you have both:
CtlnaAHCIPort.kext
XHCI-unsupported.kext

only one should be used

try XHCI-unsupported.kext first on it's own and then try XHCI-unsupported.kext on it's own
 
Feartech said:
should be ok

also noticed you have both:
CtlnaAHCIPort.kext
XHCI-unsupported.kext

only one should be used

try XHCI-unsupported.kext first on it's own and then try XHCI-unsupported.kext on it's own
Click to expand...
I tried without CtlnaAHCIPort.kext first and it failed almost immediately and said it was missing. I then swapped them and it is stuck at the same spot as the previous screenshot. The files are the same as before, just with XHCI-unsupported.kext removed.
 
SPKNout4CHRIST said:
I tried without CtlnaAHCIPort.kext first and it failed almost immediately and said it was missing. I then swapped them and it is stuck at the same spot as the previous screenshot. The files are the same as before, just with XHCI-unsupported.kext removed.
Click to expand...
also test both 1 at a time again but this time disable nvmefix.kext
 
Feartech said:
also test both 1 at a time again but this time disable nvmefix.kext
Click to expand...
Is there a way to disable it other than removing from the kext folder? I receive the following when I removed it from the folder. This is the same error I received when I removed CtlnaAHCIPort.kext, just referencing that kext instead.
IMG_0526.jpg
 

Attachments

  • OC.zip
    2.3 MB · Views: 47
SPKNout4CHRIST said:
Is there a way to disable it other than removing from the kext folder? I receive the following when I removed it from the folder. This is the same error I received when I removed CtlnaAHCIPort.kext, just referencing that kext instead.View attachment 495011
Click to expand...
yes, in your config.plist, just disable the kext that way:
from:
Code: 
<dict>
                <key>Arch</key>
                <string>Any</string>
                <key>BundlePath</key>
                <string>NVMeFix.kext</string>
                <key>Comment</key>
                <string></string>
                <key>Enabled</key>
                <true/>
                <key>ExecutablePath</key>
                <string>Contents/MacOS/NVMeFix</string>
                <key>MaxKernel</key>
                <string></string>
                <key>MinKernel</key>
                <string></string>
                <key>PlistPath</key>
                <string>Contents/Info.plist</string>
            </dict>

to:
Code: 
<dict>
                <key>Arch</key>
                <string>Any</string>
                <key>BundlePath</key>
                <string>NVMeFix.kext</string>
                <key>Comment</key>
                <string></string>
                <key>Enabled</key>
                <false/>
                <key>ExecutablePath</key>
                <string>Contents/MacOS/NVMeFix</string>
                <key>MaxKernel</key>
                <string></string>
                <key>MinKernel</key>
                <string></string>
                <key>PlistPath</key>
                <string>Contents/Info.plist</string>
            </dict>
 
Feartech said:
yes, in your config.plist, just disable the kext that way:
from:
Code: 
<dict>
                <key>Arch</key>
                <string>Any</string>
                <key>BundlePath</key>
                <string>NVMeFix.kext</string>
                <key>Comment</key>
                <string></string>
                <key>Enabled</key>
                <true/>
                <key>ExecutablePath</key>
                <string>Contents/MacOS/NVMeFix</string>
                <key>MaxKernel</key>
                <string></string>
                <key>MinKernel</key>
                <string></string>
                <key>PlistPath</key>
                <string>Contents/Info.plist</string>
            </dict>

to:
Code: 
<dict>
                <key>Arch</key>
                <string>Any</string>
                <key>BundlePath</key>
                <string>NVMeFix.kext</string>
                <key>Comment</key>
                <string></string>
                <key>Enabled</key>
                <false/>
                <key>ExecutablePath</key>
                <string>Contents/MacOS/NVMeFix</string>
                <key>MaxKernel</key>
                <string></string>
                <key>MinKernel</key>
                <string></string>
                <key>PlistPath</key>
                <string>Contents/Info.plist</string>
            </dict>
Click to expand...
Disabled nvmefix.kext and kept CtlnaAHCIPort.kext, same result. Then disabled nvmefix.kext and kept XHCI-unsupported.kext, same result.
 

Attachments

  • OC.zip
    2.3 MB · Views: 53
Feartech said:
yes, in your config.plist, just disable the kext that way:
from:
Code: 
<dict>
                <key>Arch</key>
                <string>Any</string>
                <key>BundlePath</key>
                <string>NVMeFix.kext</string>
                <key>Comment</key>
                <string></string>
                <key>Enabled</key>
                <true/>
                <key>ExecutablePath</key>
                <string>Contents/MacOS/NVMeFix</string>
                <key>MaxKernel</key>
                <string></string>
                <key>MinKernel</key>
                <string></string>
                <key>PlistPath</key>
                <string>Contents/Info.plist</string>
            </dict>

to:
Code: 
<dict>
                <key>Arch</key>
                <string>Any</string>
                <key>BundlePath</key>
                <string>NVMeFix.kext</string>
                <key>Comment</key>
                <string></string>
                <key>Enabled</key>
                <false/>
                <key>ExecutablePath</key>
                <string>Contents/MacOS/NVMeFix</string>
                <key>MaxKernel</key>
                <string></string>
                <key>MinKernel</key>
                <string></string>
                <key>PlistPath</key>
                <string>Contents/Info.plist</string>
            </dict>
Click to expand...
Is there a log file generated that I can provide with more info? I have attached the one on the root of the thumb drive if that helps.
 

Attachments

  • opencore-2020-11-10-074928.txt
    256 KB · Views: 54
Status
Not open for further replies.
Copyright © 2010 - 2024 tonymacx86 LLC
Back
Top