Contribute
Register

i5 3570k stuck at x8 (800 MHz)?

Status
Not open for further replies.
Joined
Jul 8, 2011
Messages
11
Motherboard
Asus P8Z77-V LK
CPU
i5 3570k
Graphics
Zotac GTX 550 ti
Mac
  1. 0
Classic Mac
  1. 0
Mobile Phone
  1. iOS
I have an i5 3570k and I am using the iMac 13,2 System Definition.

After attempting to follow this guide: http://www.tonymacx86.com/mavericks...vericks-native-cpu-igpu-power-management.html, generating an SSDT for stock clock speeds and dropping the appropriate tables, I rebooted and was stuck at 800 MHz.

Running SSDTPRgen returns this:

ssdtPRGen.sh v0.9 Copyright (c) 2011-2012 by † RevoGirl
v6.6 Copyright (c) 2013 by † Jeroen
v14.1 Copyright (c) 2013-2014 by Pike R. Alpha
-----------------------------------------------------------
Bugs > https://github.com/Piker-Alpha/ssdtPRGen.sh/issues <

System information: Mac OS X 10.9.5 (13F34)
Brandstring 'Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz'

Scope (_PR_) {220 bytes} with ACPI Processor declarations found in the DSDT (ACPI 1.0 compliant)
Generating ssdt.dsl for a 'iMac13,2' with board-id [Mac-FC02E91DDD3FA6A4]
Ivy Bridge Core i5-3570K processor [0x306A9] setup [0x0603]
With a maximum TDP of 77 Watt, as specified by Intel
Number logical CPU's: 4 (Core Frequency: 3400 MHz)
Number of Turbo States: 4 (3500-3800 MHz)
Number of P-States: 23 (1600-3800 MHz)
Injected C-States for CPU0 (C1,C3,C6)
Injected C-States for CPU1 (C1,C2,C3)
Warning: 'cpu-type' may be set improperly (0x0603 instead of 0x0703)

Intel ACPI Component Architecture
ASL Optimizing Compiler version 20130117-64 [Jan 19 2013]
Copyright (c) 2000 - 2013 Intel Corporation

ASL Input: /Users/timg/Desktop/ssdt.dsl - 250 lines, 7588 bytes, 47 keywords
AML Output: /Users/timg/Desktop/ssdt.aml - 1607 bytes, 16 named objects, 31 executable opcodes

Compilation complete. 0 Errors, 0 Warnings, 0 Remarks, 0 Optimizations

Do you want to copy /Users/timg/Desktop/ssdt.aml to /Extra/ssdt.aml? (y/n)? n
Do you want to open ssdt.dsl (y/n)? n

The only thing that appears out of place is "Warning: 'cpu-type' may be set improperly (0x0603 instead of 0x0703)". Could this be causing the problem?
 
I have also done this using work around 3 with the same results.
 
Status
Not open for further replies.
Back
Top