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 Simon's InsaneMac
      Hi, I'm kind of lost when scrolling to Clover Configurator, so I decided to use an EFI from the web and just configure the most basic stuff. But that sadly didn't work, im always getting the attached screen IMG_0054.HEIC (and I don't know whether all the errors are listed, as I can't scroll). 
      Anyways I thought it'd be better to do a custom setup. Can anyone give me some help with what to choose in the settings? Here's my rig:
      i7 8700k
      Asus z370-G (Rog Strix)
      gtx 1060 6gb
      samsung ssd (SATA)
      WD hard drive
       
      Your help would be much appreciated!
    • By kylon
      A big thanks to wegface for teaching me a lot of things.
       
       
      Tested on Catalina 10.15.4 and Clover EFI 5104 (Catalina Patcher)
       
      Not Working:
      - realtek sd card reader (pm me if you have a fix)
       
      Notes:
      **CPU patches are disabled, if you are using a locked BIOS you must enable them**
       
      Clover EFI:
      - Install it in UEFI Mode and change your hdd partition table to GPT.
      - You will be able to install ANY OS in EFI mode, even if this pc does not support EFI at all! (No guide available for this)
       
      You will need:
      My unlocked BIOS (OPTIONAL) (here) Latest Clover config from CCE Bank (here) (asus k53sj-kylon) Rehabman Voodoo PS2 Controller (here) acidanthera AppleALC (here) acidanthera Lilu (here) acidanthera VirtualSMC (here) acidanthera SMCBatteryManager (here) acidanthera SMCLightSensor (here) acidanthera WhateverGreen (here) Mieze Realtek RTL8111 (here)
    • By Poirot
      I have a Vanilla Catalina issue….with a different twist.  Installation/upgrade went fine, just took a loooooooong time as I was working from a cloned Mojave external USB hard drive.  Boots just fine, and all my apps seem happy.  Here lies the twist....Sleep/wake.  It will sleep and stay asleep just fine.  The issue is with waking up:

      Under Clover with FakeSMC, it would wake, but not accept my password. ??????  Ok, its clover....
      Under Clover 0.5.5 with VitrualSMC, it would wake, but with no video signal/crash.  Again, its clover...
      Under OpenCore 0.5.5 with VirtualSMC, it would wake, but with no video signal/crash, and no crash log.
      Under OpenCore 0.5.5 with FakeSMC, it sleeps, it wakes,....and accepts my password!!!!   Only once.  The next time it went to sleep, it would wake, but not accept my password.  HUH??????
       
      Kinda strange.  For the most part I have just stuck with Mojave.  I was waiting for the next build of OC, but I may just use OC builder myself and see if the latest solves any issue, as I see there have been quite a few updates to the project.  In the mean time…..suggestions?  I have attached an image of the efi.
       
      Specs:
      Gigabyte Z390 Aorus Xtreme
      Intel 9900K, stuck @ 4.9Ghz
      Sapphire RX590 Nitro+
      Corsair AX1200i
      32GB Corsair Dominator Ram
      Lian Li 011 Dynamic XL
       
      Poirot

    • By kevpatts
      Hey all,
       
      This is the opposite of a lot of other peoples problems!
       
      For me USB ports (ASRock Z390 Phantom mITX) work for USB devices all the time. USB3 devices don't work when I boot until AFTER I sleep and then wake again; then everything works fine.
       
      Any idea how to get them working straight after boot/login?
       
      Kev
    • By Krustif
      Hello.
       
      Last week I had an intempestive shutdown and couldn't start again ( error allocationpages 0X000.... type2). By mistake I upgraded the bios and had to downgrade it again.
      It solve the error allocationpages 0X000 problem.
      and I can reboot with my system SSD (I worked with for 2 years with any problem since the error allocationpages 0X000)
      but now I cannot shutdown. (See attachment) It seems I had a problem with the NVMe implantation but I don't know how to resolve it.
      I didn't change any configuration. I just format the NVM after my (error allocationpages 0X000).  I had this NVMe SSD before and it is not the disk system.
       
      mid-Solved

      Now, system shutdown but not the computer.
       
      Thank you
       
       
       
       
       
       
       
      Asus Deluxe X299
      X7820
      Ram Corsair 4X16
      GeForce GTX  1070 Ti
      SSD Crucial 1T  (system)
      SSD Crucial 500 (backup system)
      Samsung 970 ( M2-2 socket 3)
       
       

      config.plist
      iMac Pro de christophe.ioreg.zip
×