Jump to content
Sign in to follow this  
Followers 0
thornton.as

Mavericks/Clover GA-Z87N-WIFI Shutdown/Restart and Display Wake issues

28 posts in this topic

Recommended Posts

Hi All;

 

I've been trying to find a resolution to a couple of issues i'm having with a new installation of Mavericks (10.9.4) using the Clover (current Version) bootloader on a GA-Z87N-WIFI board.

 

The system in general is performing well; however when asking the system to shutdown or restart, the OS goes through the process (it seems) then the computer turns off (both at shutdown or restart) and then turns back on again - When the OS loads, it advises it didn't shutdown correctly. Wake on LAN is disabled in the BIOS and disabled via the Energy Saving Preferences.

 

Second issue is with the OS turning the displays off. I had this setting on at 5 mins - at this time the displays turn off, but when wanting to wake the displays up (via normal methods), I get nil response - however, the computer doesn't seem to be frozen.

 

Any idea's would be most helpful.

Thanks in advance!

Share this post


Link to post
Share on other sites
Advertisement

When the OS indicates that it wasn't turned off properly, you should have the option of looking at the log in the report before you decide to send it to Apple or not.  See if you find any information there that might indicate what's happening.

 

I experienced a similar issue with the same MB (a Rev. 2.0 though, not sure which you have) - shutdown/restart would result in a kernel panic right before it shuts down.  Using a patched mach_kernel seems to have resolved it though.

Share this post


Link to post
Share on other sites

When the OS indicates that it wasn't turned off properly, you should have the option of looking at the log in the report before you decide to send it to Apple or not.  See if you find any information there that might indicate what's happening.

 

I experienced a similar issue with the same MB (a Rev. 2.0 though, not sure which you have) - shutdown/restart would result in a kernel panic right before it shuts down.  Using a patched mach_kernel seems to have resolved it though.

Hi GokieKS; Thanks for the quick reply; much appreciate it.

 

I'll follow your suggestions when I return home this afternoon - and report the outcome - hopefully some good news.

Share this post


Link to post
Share on other sites

Hello

 

If system boot normaly isn't necessary patch kernel........

this patch is just for some Desktop haswell versions and all mobile haswell versions.... your is desktop.........

 

What metgod you use to install MV? retail? distro?

Did you use myhack? or what???

Share this post


Link to post
Share on other sites

If system boot normaly isn't necessary patch kernel........

this patch is just for some Desktop haswell versions and all mobile haswell versions.... your is desktop.........

 

See, that's what I thought too, and I didn't have to use a patched mach_kernel on 10.9.3.  But 10.9.4 introduced the KP on shutdown issue, and out of everything I tried, using the patched mach_kernel was what fixed it.  So there might be something more going on, but it fixed the issue for me, at any rate.

Share this post


Link to post
Share on other sites

Hello

 

If system boot normaly isn't necessary patch kernel........

this patch is just for some Desktop haswell versions and all mobile haswell versions.... your is desktop.........

 

What metgod you use to install MV? retail? distro?

Did you use myhack? or what???

Hi PimentelX86;

 

Yes my system boots fine- no issue here and is a Desktop.

 

Install method was retail (App Store download). Used a terminal command to create a USB installer and followed a guide to install Clover as the bootloader for it.

See, that's what I thought too, and I didn't have to use a patched mach_kernel on 10.9.3.  But 10.9.4 introduced the KP on shutdown issue, and out of everything I tried, using the patched mach_kernel was what fixed it.  So there might be something more going on, but it fixed the issue for me, at any rate.

How does one install a patched kernel? I've never done it.

Share this post


Link to post
Share on other sites

Hello

See, that's what I thought too, and I didn't have to use a patched mach_kernel on 10.9.3.  But 10.9.4 introduced the KP on shutdown issue, and out of everything I tried, using the patched mach_kernel was what fixed it.  So there might be something more going on, but it fixed the issue for me, at any rate.

 

Because this i said:
 

If system boot normaly isn't necessary patch kernel........

 

Just if you don't boot(re-booting always) you need apply patch... if not, isn't necessary
 

Install method was retail (App Store download). Used a terminal command to create a USB installer and followed a guide to install Clover as the bootloader for it.

 

Good to hear this... You have Power management?

You adjusted your graphic???

 

put you config.plist in here please

Share this post


Link to post
Share on other sites

Hello

 

 

Because this i said:

 

 

 

Just if you don't boot(re-booting always) you need apply patch... if not, isn't necessary

 

 

 

Good to hear this... You have Power management?

You adjusted your graphic???

 

put you config.plist in here please

I haven't yet setup or configured any power management options - is it necessary? My machine is on 24/7.

I believe that I have full graphics support, i'm using the onboard HDMI ports and have two displays connected. The system reports full graphics acceleration.

 

Standby on the config.plist.

Share this post


Link to post
Share on other sites

How does one install a patched kernel? I've never done it.

 

Basically you delete (or, preferably, rename so that you can restore it if you wanted to) the existing mach_kernel, then copy over the patched one.  I usually would do it in Terminal.  For example, if you SSD is named "SSD", and you extracted the patched kernel to your Downloads folder, this is what you would run:

sudo -s
mv /Volumes/SSD/mach_kernel /Volumes/SSD/mach_kernel_bak
cp ~/Downloads/mach_kernel /Volumes/SSD/mach_kernel

Share this post


Link to post
Share on other sites

Basically you delete (or, preferably, rename so that you can restore it if you wanted to) the existing mach_kernel, then copy over the patched one.  I usually would do it in Terminal.  For example, if you SSD is named "SSD", and you extracted the patched kernel to your Downloads folder, this is what you would run:

 

sudo -s
mv /Volumes/SSD/mach_kernel /Volumes/SSD/mach_kernel_bak
cp ~/Downloads/mach_kernel /Volumes/SSD/mach_kernel

Thanks a million GokieKS.

I haven't yet setup or configured any power management options - is it necessary? My machine is on 24/7.

I believe that I have full graphics support, i'm using the onboard HDMI ports and have two displays connected. The system reports full graphics acceleration.

Standby on the config.plist.

Hello

 

 

Because this i said:

 

 

 

Just if you don't boot(re-booting always) you need apply patch... if not, isn't necessary

 

 

 

Good to hear this... You have Power management?

You adjusted your graphic???

 

put you config.plist in here please

<?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>ACPI</key>
    <dict>
        <key>DSDT</key>
        <dict>
            <key>Debug</key>
            <false/>
            <key>DropOEM_DSM</key>
            <false/>
            <key>Name</key>
            <string>DSDT.aml</string>
            <key>ReuseFFFF</key>
            <false/>
        </dict>
        <key>SSDT</key>
        <dict>
            <key>DropOem</key>
            <false/>
            <key>Generate</key>
            <dict>
                <key>CStates</key>
                <false/>
                <key>PStates</key>
                <false/>
            </dict>
        </dict>
    </dict>
    <key>Boot</key>
    <dict>
        <key>Arguments</key>
        <string>dart=0</string>
        <key>DefaultVolume</key>
        <string>MacHDD</string>
        <key>Legacy</key>
        <string>PBR</string>
        <key>Log</key>
        <true/>
        <key>Secure</key>
        <false/>
        <key>Timeout</key>
        <integer>10</integer>
        <key>XMPDetection</key>
        <false/>
    </dict>
    <key>Devices</key>
    <dict>
        <key>Audio</key>
        <dict>
            <key>Inject</key>
            <string>1</string>
        </dict>
        <key>FakeID</key>
        <dict>
            <key>ATI</key>
            <string>0x0</string>
            <key>IMEI</key>
            <string>0x0</string>
            <key>IntelGFX</key>
            <string>0x0</string>
            <key>LAN</key>
            <string>0x0</string>
            <key>NVidia</key>
            <string>0x0</string>
            <key>SATA</key>
            <string>0x0</string>
            <key>WIFI</key>
            <string>0x0</string>
            <key>XHCI</key>
            <string>0x0</string>
        </dict>
        <key>USB</key>
        <dict>
            <key>FixOwnership</key>
            <false/>
            <key>Inject</key>
            <false/>
        </dict>
    </dict>
    <key>DisableDrivers</key>
    <array>
        <string>Nothing</string>
    </array>
    <key>GUI</key>
    <dict>
        <key>Hide</key>
        <array>
            <string>Windows</string>
            <string>\EFI\BOOT\BOOTX64.EFI</string>
        </array>
        <key>Language</key>
        <string>en:0</string>
        <key>Mouse</key>
        <dict>
            <key>Enabled</key>
            <true/>
            <key>Mirror</key>
            <false/>
            <key>Speed</key>
            <integer>8</integer>
        </dict>
        <key>Scan</key>
        <dict>
            <key>Entries</key>
            <true/>
            <key>Legacy</key>
            <string>First</string>
            <key>Tool</key>
            <true/>
        </dict>
        <key>Theme</key>
        <string></string>
    </dict>
    <key>Graphics</key>
    <dict>
        <key>Inject</key>
        <dict>
            <key>ATI</key>
            <false/>
            <key>Intel</key>
            <true/>
            <key>NVidia</key>
            <false/>
        </dict>
        <key>ig-platform-id</key>
        <string>0D220003</string>
    </dict>
    <key>KernelAndKextPatches</key>
    <dict>
        <key>AppleRTC</key>
        <true/>
        <key>AsusAICPUPM</key>
        <true/>
        <key>KernelPm</key>
        <true/>
        <key>KextsToPatch</key>
        <array>
            <dict>
                <key>Comment</key>
                <string>External icons patch</string>
                <key>Find</key>
                <data>
                RXh0ZXJuYWw=
                </data>
                <key>Name</key>
                <string>AppleAHCIPort</string>
                <key>Replace</key>
                <data>
                SW50ZXJuYWw=
                </data>
            </dict>
        </array>
    </dict>
    <key>RtVariables</key>
    <dict>
        <key>LogEveryBoot</key>
        <string>10</string>
        <key>LogLineCount</key>
        <integer>3000</integer>
        <key>MountEFI</key>
        <string>Yes</string>
    </dict>
    <key>SMBIOS</key>
    <dict>
        <key>BiosReleaseDate</key>
        <string>09/03/2013</string>
        <key>BiosVendor</key>
        <string>Apple Inc.</string>
        <key>BiosVersion</key>
        <string>IM142.88Z.0118.B00.1309031249</string>
        <key>Board-ID</key>
        <string>Mac-27ADBB7B4CEE8E61</string>
        <key>BoardManufacturer</key>
        <string>Apple Inc.</string>
        <key>BoardType</key>
        <integer>10</integer>
        <key>ChassisAssetTag</key>
        <string>iMac-Aluminum</string>
        <key>ChassisManufacturer</key>
        <string>Apple Inc.</string>
        <key>ChassisType</key>
        <string>13</string>
        <key>Family</key>
        <string>iMac</string>
        <key>Manufacturer</key>
        <string>Apple Inc.</string>
        <key>Mobile</key>
        <false/>
        <key>ProductName</key>
        <string>iMac14,2</string>
        <key>SerialNumber</key>
        <string>***REMOVED***</string>
        <key>Trust</key>
        <false/>
        <key>Version</key>
        <string>1.0</string>
    </dict>
    <key>SystemParameters</key>
    <dict>
        <key>InjectKexts</key>
        <string>Detect</string>
        <key>InjectSystemID</key>
        <true/>
    </dict>
</dict>
</plist>

 

Share this post


Link to post
Share on other sites

Hello

See how many p-states you getting.

Download aicpupm: https://www.dropbox.com/s/d2r6fodk92hfc6e/AppleIntelCPUPowerManagementInfo.kext.zip

After onpen console select all mensagers and write AICPUPMI in seach box

See how much states you get

Hi PimentelX86;

Thanks for all your assistance.

 

Your going to have to be patient with me; I am new to this and I may ask a lot of questions.

 

The goal is to replace my config.plist with the one you have attached and to install the cpu power management kext that is also attached. once done, a reboot then in the console app find the word 'AICPUPMI' under All messages.

 

Is this correct so far?

And what would be a positive result (all ok)?

 

Thanks!

Share this post


Link to post
Share on other sites

Hello

 

Yes, copy config.plist that i give to you and overwrite your config.plist....

 

This kext isn't to generate PM, because PM was generated by config.plist... this AICPUPMI is just to show p-states

 

Because anyway haswell CPUs model don't use kext to generate pm, because pm of it is deep in kernel.....

Share this post


Link to post
Share on other sites

Hello

 

Yes, copy config.plist that i give to you and overwrite your config.plist....

 

This kext isn't to generate PM, because PM was generated by config.plist... this AICPUPMI is just to show p-states

 

Because anyway haswell CPUs model don't use kext to generate pm, because pm of it is deep in kernel.....

Hi PimentelX86;

 

Followed steps; updated the config.plist, installed the AppleIntelCPUPowerManagement kext and restarted. Console returning four items:

pm kernel: AICPUPMI: CPU P-States [8 34]

pm kernel: AICPUPMI: CPU P-States [8 32 34]

pm kernel: AICPUPMI: CPU P-States [8 32 34 36]

pm kernel: AICPUPMI: CPU P-States [8 32 34 35 36].

 

No change in issues listed in first post.

Share this post


Link to post
Share on other sites

when performing the test, run Geekbench or NovaBench app, and see the values increasing

 

and about AICPMinfo, is not necessary install, just run in Terminal, put the kext in Desktop, and run this commands:

cd ~/Desktop/
sudo chown -R root:wheel ./AppleIntelCPUPowerManagementInfo.kext
sudo chmod -R 755 ./AppleIntelCPUPowerManagementInfo.kext
sudo kextload ./AppleIntelCPUPowerManagementInfo.kext

Open Console, select All Messages and type AICPUPM in the Filter box, wait for a few minutes

When the steps won’t increase any further, unload the kext by typing this command in Terminal:

sudo kextunload AppleIntelCPUPowerManagementInfo.kext

Share this post


Link to post
Share on other sites

Hello!

 

Have you tried to switch your SMBios to personality of iMac 14,1. It seems to match better with your hardware, because you are using only the internal gfx and Apple has made changes to the gfx management with 10 9.3.

 

Don´t know, if this could really help you. Is just a suggestion to try out and could be quickly done with an as trial configured usb bootstick.

 

Have fun.

Share this post


Link to post
Share on other sites

Hello
 

Have you tried to switch your SMBios to personality of iMac 14,1

 

 

He's using this model...

 

@thornton.as

Try waite 2 minutes to see if you get more P-States.... if not... ry use a other SMbios model... MacBookPro 11,2 and see how much P-States ou get... use Clover Configurator to this job

Share this post


Link to post
Share on other sites

@PimentelX(&

 

Hello!

 

If thorten.as has configured his device as an one with the SMBios of an iMac 14,1 either the digits for the Board ID nor the ones for the  Productname in his posted config.plist are matching with an IMac 14,1. Even in the by you for him posted config.plist, he should try out, they are not set matching with an iMac 14.1.

 

Have fun.

Share this post


Link to post
Share on other sites

Hi All;

Thanks all for your input in trying to help me resolve these issues.

 

I ran into some issues yesterday and wiped my drive so when I return from work this afternoon, I am going to start fresh with a clean install with the following configuration;

 

Mavericks 10.9.4

Clover EFI boot loader - r2747

SMbios of 14,1

Apple Intel CPU Power Management Patch.

 

Please let me know if I'm missing something.

 

Once again thanks to all.

 

PS- not sure if this is helpful, but upon reading the output of the log when the computer restarts after a failed shutdown; it's pointing to the Apple Graphics. I don't have a screenshot, however when I reinstall the OS and if I come across it again; I'll post the info.

Share this post


Link to post
Share on other sites

Hello!

 

Please let us know the result of a new install. The pointing to Apple Graphics could be related with the usage of SMBios of iMac 14,2.

 

And by the way some cpupmstates more or less should not infect the functionality of your system.

I personally don´t understand the hyppe with them. More importent is, to be able to reach the full turbostates  with all cores, when full power is needed. If the system has nothing to work with, they should all fall down to lowest possible definded states. In normal usage not all cores together should push up to highest posssible value. And the most important thing is, to have no KP because of malfunction.

 

Have fun.

Share this post


Link to post
Share on other sites

Hi All;

 

Ok; fresh install - SMBios 14,1 and still at square one...

Kernel panics when requesting a shutdown and/or restarts:

Anonymous UUID:       5DB1E674-0FFE-21F8-96F0-13A4DCB71214

Fri Jul 11 23:21:34 2014
Machine-check capabilities: 0x0000000000000c09
 family: 6 model: 60 stepping: 3 microcode: 9
 signature: 0x306c3
 Intel(R) Core(TM) i5-4570 CPU @ 3.20GHz
 9 error-reporting banks
Processor 2: IA32_MCG_STATUS: 0x0000000000000005
 IA32_MC4_STATUS(0x411): 0xba00000011000402
 IA32_MC4_MISC(0x413):   0x0000000000000000
panic(cpu 2 caller 0xffffff80002dcad9): "Machine Check at 0xffffff7f81933428, registers:\n" "CR0: 0x000000008001003b, CR2: 0x00007fff540a8cf8, CR3: 0x0000000000d47001, CR4: 0x00000000001606e0\n" "RAX: 0x0000000000000020, RBX: 0xffffff7f8197dd80, RCX: 0xffffffffffff0280, RDX: 0x00000000b1030000\n" "RSP: 0xffffff81f2ca3a40, RBP: 0xffffff81f2ca3a40, RSI: 0x00000000000650c0, RDI: 0xffffff802780a000\n" "R8:  0xffffff81e6855078, R9:  0x0000000000000000, R10: 0xffffff81f2ca3850, R11: 0x0000000000000680\n" "R12: 0xffffff802743f480, R13: 0xffffff7f8197dd80, R14: 0x000000000006671c, R15: 0x00000000000005db\n" "RFL: 0x0000000000000286, RIP: 0xffffff7f81933428, CS:  0x0000000000000008, SS:  0x0000000000000010\n" "Error code: 0x0000000000000000\n"@/SourceCache/xnu/xnu-2422.110.17/osfmk/i386/trap_native.c:168
Backtrace (CPU 2), Frame : Return Address
0xffffff81e684de80 : 0xffffff8000222f79 
0xffffff81e684df00 : 0xffffff80002dcad9 
0xffffff81e684e060 : 0xffffff80002f3fef 
0xffffff81f2ca3a40 : 0xffffff7f81962c5d 
0xffffff81f2ca3a90 : 0xffffff7f8193c70a 
0xffffff81f2ca3ad0 : 0xffffff7f81942623 
0xffffff81f2ca3b30 : 0xffffff7f819470a0 
0xffffff81f2ca3b70 : 0xffffff7f8192c6e2 
0xffffff81f2ca3bc0 : 0xffffff7f810e5780 
0xffffff81f2ca3c00 : 0xffffff80006922a1 
0xffffff81f2ca3c60 : 0xffffff80006e3ecb 
0xffffff81f2ca3cd0 : 0xffffff8000692449 
0xffffff81f2ca3d10 : 0xffffff80006db36c 
0xffffff81f2ca3e00 : 0xffffff80006c174a 
0xffffff81f2ca3e30 : 0xffffff80002e0492 
0xffffff81f2ca3e40 : 0xffffff800022e084 
0xffffff81f2ca3e50 : 0xffffff80005de630 
0xffffff81f2ca3ec0 : 0xffffff80005ece98 
0xffffff81f2ca3f50 : 0xffffff8000640a33 
0xffffff81f2ca3fb0 : 0xffffff80002f3f46 
      Kernel Extensions in backtrace:
         com.apple.iokit.IOGraphicsFamily(2.4.1)[75D81741-64C1-3941-ADFA-9D6B6C434EE4]@0xffffff7f810db000->0xffffff7f8111dfff
            dependency: com.apple.iokit.IOPCIFamily(2.9)[4662B11D-2ECA-315D-875C-618C97CDAB2A]@0xffffff7f808be000
         com.apple.driver.AppleIntelFramebufferAzul(8.2.8)[9AEF7957-1707-32C1-97FA-50D896C9B9B9]@0xffffff7f8191b000->0xffffff7f81982fff
            dependency: com.apple.iokit.IOPCIFamily(2.9)[4662B11D-2ECA-315D-875C-618C97CDAB2A]@0xffffff7f808be000
            dependency: com.apple.iokit.IOACPIFamily(1.4)[045D5D6F-AD1E-36DB-A249-A346E2B48E54]@0xffffff7f8105c000
            dependency: com.apple.iokit.IOAcceleratorFamily2(98.22)[0EC64777-94B9-32E3-AC03-A2367895744B]@0xffffff7f8182b000
            dependency: com.apple.iokit.IOReportFamily(23)[EE246983-FE6F-32F3-A5A0-88F3E3CDBA89]@0xffffff7f8104b000
            dependency: com.apple.AppleGraphicsDeviceControl(3.6.22)[91D61DEC-2946-3790-8134-B808C016C4C9]@0xffffff7f81915000
            dependency: com.apple.iokit.IOGraphicsFamily(2.4.1)[75D81741-64C1-3941-ADFA-9D6B6C434EE4]@0xffffff7f810db000

BSD process name corresponding to current thread: launchd
Boot args: dart=0 slide=0 

Mac OS version:
13E28

Kernel version:
Darwin Kernel Version 13.3.0: Tue Jun  3 21:27:35 PDT 2014; root:xnu-2422.110.17~1/RELEASE_X86_64
Kernel UUID: BBFADD17-672B-35A2-9B7F-E4B12213E4B8
System model name: iMac14,1 (Mac-031B6874CF7F642A)

System uptime in nanoseconds: 56491244572
last loaded kext at 8406874750: com.apple.driver.AudioAUUC	1.60 (addr 0xffffff7f8146d000, size 32768)
loaded kexts:
com.highpoint-tech.kext.HighPointRR	4.0.0
com.insanelymac.driver.AppleIntelE1000e	3.0.4
org.netkas.driver.FakeSMC	1123
org.tgwbd.driver.NullCPUPowerManagement	1.0.0d2
com.apple.driver.AudioAUUC	1.60
com.apple.filesystems.msdosfs	1.9
com.apple.filesystems.autofs	3.0
com.apple.driver.AppleUSBCDC	4.2.1b5
com.apple.iokit.IOBluetoothSerialManager	4.2.6f1
com.apple.iokit.BroadcomBluetoothHostControllerUSBTransport	4.2.6f1
com.apple.driver.AppleTyMCEDriver	1.0.2d2
com.apple.driver.AppleGraphicsDevicePolicy	3.6.22
com.apple.driver.AppleUpstreamUserClient	3.5.13
com.apple.driver.AppleMCCSControl	1.2.5
com.apple.driver.AppleHDAHardwareConfigDriver	2.6.1f2
com.apple.driver.AppleHDA	2.6.1f2
com.apple.driver.ACPI_SMC_PlatformPlugin	1.0.0
com.apple.driver.AppleLPC	1.7.0
com.apple.iokit.IOUserEthernet	1.0.0d1
com.apple.Dont_Steal_Mac_OS_X	7.0.0
com.apple.driver.AppleHWAccess	1
com.apple.driver.AppleIntelMCEReporter	104
com.apple.driver.AppleIntelHD5000Graphics	8.2.8
com.apple.driver.AppleIntelFramebufferAzul	8.2.8
com.apple.driver.PioneerSuperDrive	3.4.1
com.apple.iokit.SCSITaskUserClient	3.6.6
com.apple.driver.XsanFilter	404
com.apple.driver.AppleFileSystemDriver	3.0.1
com.apple.AppleFSCompression.AppleFSCompressionTypeDataless	1.0.0d1
com.apple.AppleFSCompression.AppleFSCompressionTypeLZVN	1.0.0d1
com.apple.AppleFSCompression.AppleFSCompressionTypeZlib	1.0.0d1
com.apple.iokit.IOAHCIBlockStorage	2.6.0
com.apple.BootCache	35
com.apple.driver.AppleUSBHub	683.4.0
com.apple.driver.AppleAHCIPort	3.0.5
com.apple.driver.AppleUSBXHCI	683.4.0
com.apple.driver.AppleUSBEHCI	660.4.0
com.apple.driver.AppleACPIButtons	2.0
com.apple.driver.AppleRTC	2.0
com.apple.driver.AppleHPET	1.8
com.apple.driver.AppleSMBIOS	2.1
com.apple.driver.AppleAPIC	1.7
com.apple.nke.applicationfirewall	153
com.apple.security.quarantine	3
com.apple.kext.triggers	1.0
com.apple.iokit.IOSerialFamily	10.0.7
com.apple.iokit.IOBluetoothHostControllerUSBTransport	4.2.6f1
com.apple.driver.AppleGraphicsControl	3.6.22
com.apple.driver.AppleSMBusController	1.0.12d1
com.apple.iokit.IOSMBusFamily	1.1
com.apple.iokit.IOSCSIBlockCommandsDevice	3.6.6
com.apple.driver.DspFuncLib	2.6.1f2
com.apple.vecLib.kext	1.0.0
com.apple.iokit.IOAudioFamily	1.9.7fc2
com.apple.kext.OSvKernDSPLib	1.14
com.apple.driver.IOPlatformPluginLegacy	1.0.0
com.apple.driver.AppleSMBusPCI	1.0.12d1
com.apple.driver.IOPlatformPluginFamily	5.7.1d6
com.apple.iokit.IOBluetoothFamily	4.2.6f1
com.apple.driver.AppleHDAController	2.6.1f2
com.apple.iokit.IOHDAFamily	2.6.1f2
com.apple.driver.AppleSMC	3.1.8
com.apple.iokit.IOSurface	91.1
com.apple.iokit.IONDRVSupport	2.4.1
com.apple.AppleGraphicsDeviceControl	3.6.22
com.apple.iokit.IOAcceleratorFamily2	98.22
com.apple.iokit.IOGraphicsFamily	2.4.1
com.apple.iokit.IOUSBMassStorageClass	3.6.0
com.apple.iokit.IOUSBHIDDriver	660.4.0
com.apple.driver.AppleUSBComposite	656.4.1
com.apple.iokit.IOSCSIMultimediaCommandsDevice	3.6.6
com.apple.iokit.IOBDStorageFamily	1.7
com.apple.iokit.IODVDStorageFamily	1.7.1
com.apple.iokit.IOCDStorageFamily	1.7.1
com.apple.iokit.IOAHCISerialATAPI	2.6.1
com.apple.iokit.IOUSBUserClient	660.4.2
com.apple.iokit.IOSCSIParallelFamily	3.0.0
com.apple.iokit.IOSCSIArchitectureModelFamily	3.6.6
com.apple.iokit.IOAHCIFamily	2.6.5
com.apple.iokit.IONetworkingFamily	3.2
com.apple.iokit.IOUSBFamily	683.4.0
com.apple.driver.AppleEFINVRAM	2.0
com.apple.driver.AppleEFIRuntime	2.0
com.apple.iokit.IOHIDFamily	2.0.0
com.apple.security.sandbox	278.11.1
com.apple.kext.AppleMatch	1.0.0d1
com.apple.security.TMSafetyNet	7
com.apple.driver.AppleKeyStore	2
com.apple.driver.DiskImages	371.1
com.apple.iokit.IOStorageFamily	1.9
com.apple.iokit.IOReportFamily	23
com.apple.driver.AppleFDEKeyStore	28.30
com.apple.driver.AppleACPIPlatform	2.0
com.apple.iokit.IOPCIFamily	2.9
com.apple.iokit.IOACPIFamily	1.4
com.apple.kec.corecrypto	1.0
com.apple.kec.pthread	1
Model: iMac14,1, BootROM IM141.0118.B00, 4 processors, Intel Core i5, 3.20 GHz, 16 GB, SMC 2.14f19
Graphics: Intel HD Graphics 4600, Intel HD Graphics 4600, Built-In
Memory Module: BANK0/DIMM0, 8 GB, DDR3, 1333 MHz, Corsair, CMZ16GX3M2A1600C9
Memory Module: BANK1/DIMM0, 8 GB, DDR3, 1333 MHz, Corsair, CMZ16GX3M2A1600C9
Bluetooth: Version 4.2.6f1 14216, 3 services, 23 devices, 1 incoming serial ports
Network Service: Ethernet, Ethernet, en1
Serial ATA Device: Corsair Force GS, 128.04 GB
Serial ATA Device: Corsair Force GS, 128.04 GB
Serial ATA Device: PIONEER BD-RW   BDR-208D
SCSI Device: SCSI Target Device @ 0
SCSI Device: SCSI Target Device @ 32
USB Device: Hub
USB Device: Hub
USB Device: My Book 1140
USB Device: Photosmart 7520 series
USB Device: Microsoft USB Optical Mouse
USB Device: USB2.0 Hub
USB Device: BCM20702A0
USB Device: 802.11n NIC
USB Device: USB2.0 Hub
USB Device: Wired Keyboard 600
Thunderbolt Bus: 

Any ideas?


When the OS indicates that it wasn't turned off properly, you should have the option of looking at the log in the report before you decide to send it to Apple or not.  See if you find any information there that might indicate what's happening.

 

I experienced a similar issue with the same MB (a Rev. 2.0 though, not sure which you have) - shutdown/restart would result in a kernel panic right before it shuts down.  Using a patched mach_kernel seems to have resolved it though.

 

Hi GokieKS;

 

I have installed patched kernel - no resolve. Thanks for your suggestion though!

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 Reel
      All work 10.10, 10.11, 10,12
      camera not work in 10.13, 10.14
      You need SwitchResX that the screen does not freeze
      Custom resolutions: Back porch - lines change to 2
      UEFI boot moded bios https://github.com/Thiblizz/l502x-modded-bios
       
      For 10.14 you need: HD3000 Fix for Mojave.zip
      Installed in S/L/E 
       
      SMBIOS: MacbookPro 8.3 or MacbookPro 9.1
       
       

       

       
       
    • By glasgood
      CLOVER DUAL BOOT MOJAVE & WINDOWS 10 GUIDE 
       

       
       
      INCLUDES  MBR / LEGACY BIOS  TO  GPT / EFI CONVERSION
      USING MBR2GPT TOOL
       
       
      PREREQUISITE: Two physical discs ( SSD’s or HDD’s )
       
       
       
       
       
      STEP 1 - Clover dual boot configuration 
       
      Open config.plist with Clover Configurator
       
      Boot
       Legacy = PBR Timeout = True ( will remove the Timeout countdown, from Clover boot menu)  

       
      GUI 
      Scan / Custom
       Entries = True  Tool = True  Legacy = False ( removes extra Windows 10 entries )  
      Hide Volume
      - Preboot ( macOS Preboot )
      - Recovery ( macOS Recovery )
       

       
      So at boot you will have two options: boot macOS Mojave or Windows 10 
       
       
       
       
       
       
       
      ————————————————————
       
       
      STEP 2 - Using a drive without Windows 10 installed
       
      Disconnect system drive that contains your macOS Mojave install from computer ( This is so that Windows does not overwrite existing macOS Mojave boot loader )
       
      Proceed with a Windows 10 UEFI install.  
      After installation reconnect macOS Mojave Drive, the Windows installation should now be detected and usable in Clover. 
      If Windows 10 is not detected or able to boot,  then verify you installed Windows 10 as UEFI and not MBR ---->  ( Read step 2 - For a drive with Windows 10 installed )
       
       
      OR
       
       
       
      STEP 2 - Using a drive with Windows 10 already installed
       
      Verify your Windows install is  GPT / UEFI or MBR / Legacy BIOS.   
      If Windows install is GPT UEFI then Windows 10 install is ready to use at Clover boot menu, you should be able to boot into Windows directly from Clover boot screen. 
       

       
       
      But if  Windows drive is detected at Clover boot screen, but when booting Windows you get a black screen with a cursor on the top left,
      then this is most likely because Windows drive is MBR ( Legacy BIOS ).  You can easily convert MBR to GPT using  Windows MBR2GPT tool ( this saves hours work having to reinstall Windows 10 and setting up all your applications again  ) 
       
      If Windows 10 install is MBR / Legacy BIOS  then simply convert to GPT / UEFI  following instructions below ( read video summary and view video )
       
       
      ** To use Windows 10  MBR2GPT tool  you must have Windows 10 version 1703 ( creators update  ) or later and less than 3 partitions on 
      the Windows 10 drive **
       
      Video summary:
       
      Confirm Windows 10 drive is MBR Legacy BIOS ( in Windows Disk Management ) Reboot into Windows PE ( Advanced Startup ) Convert from MBR Legacy BIOS to GPT UEFI ( using commands below ) mbr2gpt /validate mbr2gpt /convert Restart Verify Windows 10 drive has changed to GPT UEFI ( in Windows Disk Management )  
       
       
       
      After conversion Windows 10 is ready to use at the Clover boot menu 
       
       
    • By SepehrM
      I'm trying to install High Sierra 10.13.3 on an ASUS N552VW laptop, and I get stuck after this message:
      "could not recover SATA HDD after 5 attempts, terminating" 
      And some other warnings afterwards.
      Specs:
      CPU: Intel Skylake 6700HQ 2.6GHz
      RAM: 16GB DDR4
      2TB HDD + 128GB SSD
      GPU: Intel HD Graphics 530 + Nvidia GTX960m
      I'm installing using a 16GB USB3 flash drive on one of HDD volumes (UEFI Mode)
       
      I uploaded the verbose log and clover config.plist
      config-new.plist

    • By yehia2amer
      Problem:
      When I Attempt to wake my Machine from sleep, the screen stays black, although the computer is obviously awake !
      This Machine has a 1300W Power Supply So Sleep is Very Useful.
       
      I Tried:
      1) FIX_WAK and FixShutdown as per Clover Wiki.
      2) Although I am using "SAPPHIRE Radeon PULSE RX 580 8GB GDDR5", which Should be completely Supported by Mojave, I Also changed the Part Number to "113-4E353BU-O4E" as per this Guide: http://www.xlr8yourmac.com/archives/feb18/RadeonRX-580_MacPro.html. The GPU is working GREAT without even Clover Inject
      3) Tried to Run this command: disablehibernate.command.zip
      4) Tried darkwake=0 to 10
      5) Disabled wake on USB & Wake on LAN (BIOS)
       
      Logs:
      sudo pmset -g
      System-wide power settings: Currently in use: hibernatemode 0 disksleep 10 womp 0 networkoversleep 0 sleep 0 Sleep On Power Button 1 ttyskeepawake 1 hibernatefile /var/vm/sleepimage autorestart 0 gpuswitch 2 displaysleep 10 pmset -g assertions
      2019-02-19 18:51:04 +0200 Assertion status system-wide: BackgroundTask 1 ApplePushServiceTask 0 UserIsActive 1 PreventUserIdleDisplaySleep 0 PreventSystemSleep 0 ExternalMedia 1 PreventUserIdleSystemSleep 0 NetworkClientActive 0 Listed by owning process: pid 56(powerd): [0x0000001700088000] 00:13:44 ExternalMedia named: "com.apple.powermanagement.externalmediamounted" pid 100(hidd): [0x00000025000980a7] 00:00:00 UserIsActive named: "com.apple.iohideventsystem.queue.tickle.4294968578.17" Timeout will fire in 600 secs Action=TimeoutActionRelease pid 200(mds_stores): [0x0000034e000b8279] 00:00:00 BackgroundTask named: "com.apple.metadata.mds_stores.power" Kernel Assertions: 0x4=USB id=502 level=255 0x4=USB mod=1/1/70, 2:00 AM description=com.apple.usb.externaldevice.1d130000 owner=USB Keyboard id=503 level=255 0x4=USB mod=1/1/70, 2:00 AM description=com.apple.usb.externaldevice.1d120000 owner=Lenovo Optical Mouse Idle sleep preventers: IODisplayWrangler  
      Specs:
      CPU: 2x Xeon E5-2680 v2 2.8GHz Ten Core Processors
      RAM: 128 GB 1333 MHz DDR3 ECC Memory
      GPU: SAPPHIRE Radeon PULSE RX 580 8GB GDDR5
      Chipset: Intel C602
      Audio: Realtek ALC3220 (ALC280) High Definition Audio
      SAS Drive Controllers (RAID): LSI 2308 SATA/SAS 6Gb/s controller with host based RAID 0, 1, 10 (4  
      Network Controller 1: Intel 82579 Gigabit Ethernet controller with Remote Wake UP, PXE and Jumbo frames support
      Network Controller 2: Intel Ethernet Controller I210 
      NEC USB3.0 xHCI Controller: Renesas Electronics uPD720201 & uPD720202
       
      for more info:
       
      Any Help will be appreciated, Thanks !
       
      Send me Yehias-Mac-Pro.zip
    • By RougeOne
      Budget Workstation MacOS 10.14.1 build: z370 AORUS Gaming 5 - i5-8600K - RX 580 - UHD 630
      flawless iGPU/dGPU integration, fast FCPX editing/rendering, great overall performance for ~$1200 / ~£1000
       
      Update: updated WhateverGreen and Lilu, then updated OS to 10.14.3 and everything is fine! Even iMessage, which previously I hadn't been able to make work, is now working - possibly the update flushed the NVRAM?
       
      I'm gonna come straight out and admit it - I used newb tools which are considered taboo on InsanelyMac, and so this isn't so much an installation guide as it is a green flag to anyone considering the same hardware. My first and previous Hackintosh project was just over ten years ago and this site was massively helpful, so this is my (very small) way of giving back.
       
      EFI DIRECTORY
      http://s000.tinyupload.com/index.php?file_id=97606131925137056003
       
      HARDWARE
      CPU: Intel i5-8600K 3.6GHz hexacore (contains UHD 630 iGPU)
      CPU Cooler: be quiet! Pure Rock Slim (no paste needed, and fan facing front)
      Mobo: GIGABYTE z370 AORUS Gaming 5 (WIFI)
      RAM: 1x 8GB CORSAIR Vengeance LPX C16 2666MHz (in first slot)
      GFX Card: Sapphire RX 580 NITRO+ SE
      SATA: used ports 0, 1, 3, 5 (HDD problems when connected to port 4)
      HDD: generic
      DVD Drive: generic
      PSU: EVGA 500W Semi Modular (but you should get 650W!)
      Case: CoolerMaster CM590 III
      Fans: 2x stock case fans (one sucky on front, one blowy on back), 3x be quiet! BL046 120mm fans (two blowy on top, one sucky on front). Airflow near-perfectly balanced.
       
      ADVICE
      With the Clover configuration, you want to pay close attention to all things relating to graphics. There are some specific settings for ACPI, Boot, Devices and Graphics which should be copied exactly in order to get the iGPU and dGPU to work in perfect harmony. For instance, make sure you use ig-platform-id 59120003 rather than 59120000 if you want FCPX to be usable. With the right settings, FCPX will not only run, but run flawlessly.
       
      I was not able to figure out how to make NVRAM/PRAM behave itself, and I got errors when I tried to issue relevant commands. As a result, I could not at first get iMessage to work properly. It worked once on my first installation attempt but not from subsequent attempts. This Clover configuration therefore has no consideration whatsoever toward iMessage reliability - however, iMessage ended up working somehow, anyway - I noticed it after I'd updated to 10.14.3 but this may just have been coincidence.
       
      Onboard WiFi does not work. There is no driver for it. I'm using wired ethernet to a bridge router as it was cheaper than getting a compatible PCI card.
       
      Audio is working well after I installed the z370 audio patch, then the ALC1220 codecs, then AppleALC.
       
      With kexts for generic 3rd party SATA and generic 3rd party eSATA, my HDDs and DVD drive work perfectly well.
       
      Sleep/Wake functions run perfectly. iCloud functions run perfectly. Shutdown leaves the mobo LEDs on, annoyingly.
       
      My USB 3 ports seem to suffer from low power output, and I don't know why.
       
      Overall, this system appears to run about as well under MacOS 10.14 Mojave as it does under Windows 7. I would solidly recommend this build to anyone looking to build a computer for workstation purposes, on a budget.
×